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.
• COW/FOE Updates
  
  • Focusing on potassium workflow 
  • Need to pick up several items that are missing on the COW/FOE call next week (e.g., DiagnosticReport.basedOn) and other issues around Specimen (for the Specimen call).
• 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

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

Andrea Pitkus, PhD, MLS(ASCP)CE, FAMIA. UW-Madison to Everyone (Aug 4, 2023, 1:43 PM)
https://www.ecfr.gov/current/title-42/part-493#p-493.1105(a)(6)
https://www.ecfr.gov/current/title-42/part-493#p-493.1274(e)(6)
(k)Click to open paragraph tools When errors in the reported patient test results are detected, the laboratory must do the following: 

(1) Promptly notify the authorized person ordering the test and, if applicable, the individual using the test results of reporting errors. 

(2) Issue corrected reports promptly to the authorized person ordering the test and, if applicable, the individual using the test results. 

(3) Maintain duplicates of the original report, as well as the corrected report.

Andrea Pitkus, PhD, MLS(ASCP)CE, FAMIA. UW-Madison to Everyone (Aug 4, 2023, 1:49 PM)
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.

Follow-up Next time: