IHE Lab Meeting Minutes 01/27/2012

From IHE Wiki
Jump to navigation Jump to search


  • Mary KENNEDY (College of American Pathologists, IHE Lab Domain Secretary) mkenned@cap.org
  • Jim HARRISON (UVA); james.harrison@virginia.edu
  • Ron RANAURO (College of American Pathologists); rranaur@cap.org
  • JDL NOLEN; jdlnolen@gmail.com
  • Bill CASTELLANI; wcastellani@hmc.psu.edu
  • Laurecia DAILEY-EVANS (Sunquest); laurecia.dailey-evans@sunquestinfo.com
  • Tim POLSINELLI (Epic); tpolsine@epic.com
  • Brian JACKSON (ARUP Lab); brian.jackson@aruplab.com
  • Jim SORACE; james.sorace@hhs.gov
  • Pawan SINGH (Sunquest); pawan.singh@sunquestinfo.com
  • Victory BRODSKY; vib9020@med.cornell.edu
  • John GILBERTSON (Partners); jrgilbertson@partners.org
  • Constantin FRIEDMAN; cof9014@nyp.org
  • Doug DESHAZO; douglas.deshazo@acs-inc.com


  1. Welcome and Introductions; Presentation Slides
  2. Overview (see http://wiki.ihe.net/index.php?title=LCC_Long_Proposal_-_wiki Link here)
    • Problem: Current lab order/result workflow doesn’t allow for communication related to order modification, recommendations, or clarification; or result verification or interpretation
    1. These things are done today outside of the system in separate workflows, and they are normally not documented electronically
    2. This limits laboratory-based decision support and process improvement based on documented testing issues
    • Solution: create an in-system (LIS and EHR) mechanism for communication and documentation of issues related to orders and results
    1. This will provide a pathway for the expression of laboratory expertise in the clinical setting, benefitting patients and healthcare process optimization
    2. It will more closely integrate the laboratory with the patient care team
    3. It will allow automation of some interactions to improve efficiency
    • Use Cases
    1. Order modifications
    2. Order fulfillment (post-result actions such as verification and interpretation)
    • Initial goal is balloting at end of 2012 or beginning of 2013 with initial Connectathon Winter 2013. If there are significant HL7 change dependencies, balloting in IHE may be pushed back a year to allow for this work.
  3. HL7 Dependencies Evaluation
    • Starting point for order modification: HL7 2.51 OML 21 with XO or XX control codes (see chapter 4 of the HL7 spec)
    • Starting point for results verification: HL7 2.51, follow up order with special action code, needs reference to previous order/result, may need some vocabulary development to define reasons for additional work
    • Any new definitions, elements and messages would yield change proposals for version 2.9, with the necessary features then “pre-adopted” back to 2.51.
    • Availability of HL7 specifications to LCC workgroup members, special permission for access can be obtained if necessary
  4. Tasks
    • Use case validation (by Feb 14)
    • HL7 2.51 message review (preliminary assessment by Feb 28)

Next call:

Next regularly scheduled IHE lab call will be held on Tuesday, January 31 at 9:00-10:00 AM (Eastern, New York)