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).

Meeting Notes

• CPT-PLA
  
  • Hans, Nancy, and Kathy will draft a proposal on where to relocate the reference in ISA in a better context, and then review in this group before submitting with PAC input on process.
  • The recommendation to ONC will be drafted here: OO Lab and CPT PLA - Orders & Observations - Confluence (hl7.org) in the ONC Recommendation section.
  • 8/4 - Reminder: We are not planning re-discuss the topic, rather to establish a crisp recommendation on where to represent CPT-PLA instead of its current location with a focused rationale.
  • 8/11: Revised the OO Lab and CPT PLA confluence page with changes to include:
    • Updated Option 1 
      • need to follow-up as noted - re: IVD Vendors or just labs
    • Updated Option 2
      • Representing Laboratory Test Procedure Performed
  • Revisit the recommendation on August 25, 2023
• ISA Comments - Due October 6, 2023
  • Consider any other Lab specific updates that would be good to include in ISA (vocabulary, messages, FHIR, etc.)
  • Revisit the recommendation on August 25, 2023
• COW/FOE Updates
  
  • Reviewed Potassium workflow
  • Need to determine how Specimen information is updated in various scenarios
  • Bob will be there next week 

-------------Meeting Adjourned at 2:04PM EDT---------------

--------Backlog of Topics---------

• 8/18 - ObservationDefinition.qualifiedInterval.condition 
  • Zulip chat: https://chat.fhir.org/#narrow/stream/179256-Orders-and-Observation-WG/topic/ObservationDefinition.2EqualifiedInterval.2Econdition
  • Rahul Agarwal will attend to discuss.
• DiagnosticReport.status
  
  • Zulip chat: https://chat.fhir.org/#narrow/stream/179256-Orders-and-Observation-WG/topic/DiagnosticReport.20statuses.20and.20CLIA.20requirements.3F

  • Status in FHIR: http://hl7.org/implement/standards/fhir/codesystem-diagnostic-report-status.html

  • v2-FHIR Mapping Spreadsheet: HL7 Concept Map: ResultStatus[Non-Queries] - Google Sheets
  • 8/4 - Summarized the discussion from OO Main call and ran out of time. 
    • See links in Chat below
    • Still need a bit of clarification
    • Reviewed CAP Checklist from 2023
      • Corrected/correction - A change in a previously issued clinical pathology test report intended to correct an
        inaccuracy, including changes in test results, patient identification, reference intervals, interpretation, or other
        content.
•  Micro
  • Craig's v2 micro question: https://confluence.hl7.org/pages/viewpage.action?pageId=161080303#id-20230518Main-Subject:"v2discretemicroquestion"-Listservemessage(fromCraig)
  • The OBX-30 Observation Sub-Type Enhancements - Orders & Observations - Confluence (hl7.org) was created, and as it was created identified that various values were actually deleted, and examples were available for most but not all sub-types.
  • We reviewed the current wording and examples and updated the page with suggested adjustments (in red for text not in the published version and strikethrough where text is suggested to be removed)
  • Craig updated the example (Micro Example) using only the active/new values.
  • Open questions for next week:
    • Any other updates to the definitions/descriptions to clarify?
    • Any examples that would primarily be using MOD?
    • Any examples that could use either use MID or MOD?  We discussed PCR, but that raised questions whether is actually confusing and would require further explanation as for some it would never be used with MID.
    • Andrea had suggested that a more complex example she described would be helpful, but a volunteer to create that has not yet been identified.
    • No update
• Panel/Micro and discoverable Observations in FIHR
  • Hans/Fran to create an initial proposal, focusing on the micro scenario, on how to approach this in FHIR / FHIR US Core.
    • No update

• Other JIRAs from Triage Inventory - Not discussed

V2 Lab JIRAs (link)

The following JIRA Tickets need to be reviewed by the Lab members as carry over from May 2023 WGM:

• V2-25376 - As soon as Dan has proposal.

FHIR Lab JIRA (link)

The following JIRA Tickets need to be reviewed by the Lab members as carry over from May 2023 WGM:

• FHIR-32406
• FHIR-32405
• FHIR-33041
• FHIR-34205
• FHIR- 32154 - Pending outcome of DiagnosticReport/Observation/Panel discussions

Chat History

Ana.Szarfman@fda.hhs.gov to Everyone (Aug 11, 2023, 1:25 PM)
How can we assure and how can we test that an order message reaches all necessary recipients without being corrupted or ignored?

Andrea Pitkus, PhD, MLS(ASCP)CE, FAMIA. UW-Madison to Everyone (Aug 11, 2023, 1:30 PM)
https://www.ama-assn.org/system/files/cpt-pla-codes-long.pdf
Abbott AlinityTM m STI Assay, Abbott Molecular, Inc

Ana.Szarfman@fda.hhs.gov to Everyone (Aug 11, 2023, 1:51 PM)
How can we make these transmissions, machine readable?

Follow-up Next time: