ANSI Anti-Trust Policy:  Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).

Update from FHIR Lab Workflow call

• Reviewed FHIR COW IG and made updates to the IG Proposal
• Discussed in scope and out of scope
• Concerns with including medication orders - there are several projects in place in OUS that may be overlapping - needs further discussion
• Need to differentiate from FHIR Order Exchanges (FOE) scope - administrative scope
• Need to understand jurisdictional differences in the scope – i.e., where are the variations that need to be in scope and out of scope

Meeting Notes

• Craig's random question of the week: 
  • Where does the phone number of the lab go in V2 message if they need to contact the lab about the results
    • Name, Address, Medical Director
  • OBX, OBR, ORC - could not find XTN datatypes for the lab phone number; the callback number is available
  • XAD - has text string you could use (but not ideal)
  • Should the phone number be at the time of the result or current phone number?
  • Example 1: NTE after OBR
  • Example 2: Not all results have phone number, but use NTEs for other performing lab/contact information NTEs after OBX
  • Long-term - v2 JIRA to add phone number to NTX in OBX or PRT with other performing organization if you use for phone number; Add it to a datatype that cannot repeat?  PRT was to enable the flexibility for backwards compatibility. Note: not all implementations have PRT.
  • Need to check LRI for PRT after OBX - Look at 23, 24, 25
    • PRT is in LOI for Copies To instead of OBR-28.
  • COW should enable telecon info for performing organization
  • Action item: Craig Newman will create a JIRA to resume this discussion.
    • V2-25520 - for future reference.
• Dan's random question of the week
  • Is there an example of communicating a new label for the specimen? (i.e., excluding a reprint).  Use case: workflow OUS 
    • US has SOP/workflow that should handle this
    • Need additional information about the question – what scenarios this will be needed
    • Coming from another lab - are the Accession numbers reassigned in new lab; 
    • Paper requisitions may be transferred to labels - and relabeling would need to be done for automated lab systems; 
    • Andrea Pitkus to Everyone (Apr 28, 2023, 10:52 AM)
      Specimen labeling, including patient name or unique patient identifier and, when appropriate, specimen source.

    • The procedure manual must include the following when applicable to the test procedure: (1) Requirements for patient preparation; specimen collection, labeling, storage, preservation, transportation, processing, and referral; and criteria for specimen acceptability and rejection as described in § 493.1242.

• Meeting Schedule: 
  • Cancel Friday, May 5, 2023 (travel to WGM) and May 12, 2023 (WGM)
  • Next meeting May 19, 2023
    • ONC - NPRM - draft comments
  • Reminder: LIVD call will start May 4, 2023 at 2PM EDT and thereafter -  May 18 (canx), restart June 1 biweekly for a short period of time to finish updates to the LIVD IG

-----------Adjourned meeting  2PM EDT ----------------

Next Meeting: May 19, 2023

DID NOT DISCUSS today

V2 Lab JIRAs (link)

Add JIRAs for Next time – related to Lab

FHIR Lab JIRA (link)

Add JIRAs for Next time – related to Lab