Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 Details

Date:September 1, 2023

Time: 1PM ET

Coordinates:  Join Zoom meeting: | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)


Ralf Herzog (Roche), Hans Buitendijk (Oracle), JD Nolen (Mercy Children’s Hospital), Andrea Pitkus (UW), Sara Armson (ONC), Nancy Spector (AMA), Daniel Golson (JMC), Marti Velezi (Sonrisa / FDA), Kathy Walsh (Labcorp), Rob Hausam (Hausam Consulting),  Shawn Cleary ()

Chair: Hans Buitendijk

Scribe: Hans Buitendijk, Riki Merrick

  •  Quorum (Co-Chair + 4) Met 


  • Standing Topics 
    • eSignature Update
    • Race/Ethnicity Code changes
    • COW/FOE updates
  • PLA CPT codes
  • ISA Comments
  • USCDI Comments
  • Copy from prior notes:
    • ObservationDefinition.qualifiedInterval.condition
    • DiagnosticReport.status
    • Other JIRAs form Triage Inventory below
    • Other agenda items?

Meeting Resources

JIRA Dashboards:

JIRA Grouping Tags:

Handy Tip

A grouping tag is a way for the working group to track tickets related to a product or project.  This tag can be added in the JIRA "Grouping" field to add it to the OO Lab project team's filter of open issues.

  • OO-Lab - to indicate when the JIRA Ticket should be reviewed by the OO Lab SMEs, especially when the issue is not assigned to the Resource owner.

Meeting Minutes

Previous Meeting Notes

Standing Topics

eSignature Update

  •  Follow-up date

No updates today

eSignature Update

2023-02-24 OO - LAB/LIVD

From Chat (2023-06-23 LAB)  Andrea Pitkus:  Regarding e-sig, I came across this CLIA doc (see #5):

New Rule on Race/Ethnicity from OMB/CDC

  •  Follow-up date  

No updates today

New Rule on Race/Ethnicity from OMB/CDC

COW/FOE Update

  • Finished simple Potassium workflow – without transport
  • Still need to consider how to do updates of final reports

Link to Minutes:

2023-09-01 OO FHIR COW

Special Topics


  • OO Lab and CPT PLA
    • The 2 bullets seem to properly distinguish between LOINC and CPT PLA codes
    • Need to have terminology pages
      • Kathy + Andrea prefer to have separate pages for LOINC update (under existing Laboratory Ordered Test) and CPT PLA (a new page under Procedures) in the ISA
      • The second page option does not represent the AMA perspective
      • Nancy + Rob + Hans prefer same page on the “Laboratory Test Ordered”, as more pages creates more confusion than is helpful
    • The PLA codes are also used for billing – so may be also to the Administrative?
      • That is not currently covering any vocabulary standards as part of that group
      • CPT / ICD – all of those are listed in their respective domains
    • We will provide both perspectives, since as HL7 community we should comment, since the clarification is important rather than not commenting at all
    • Individual folks can also submit their comments for the recommendation of their choice
    • Also update to remove the reference to ORC-16, since that is NOT using LOINC or CPT PLA or other codes, as it represents the reason for the order, not the order itself
    • Comments on the ISA are entered by the submission system in the order of receipt – however the full HL7 PAC comment will not be on this page
    • For the ORC-16 may be better for ONC to make that clarification
    • It is helpful to ONC to get supportive comments
    • How are changes that we are proposing helping implementers understand them
    • Motion to submit the italicized comment to the HL7 PAC – Riki Merrick, Marti Velezis, no further discussion, against:2, abstain: 1, in favor: 7
      • For completeness, the text is:
      • Currently, the ONC ISA represents CPT-PLA as an available vocabulary for laboratory orders in the Representing Laboratory Test Ordered | Interoperability Standards Advisory (ISA) ( section in Section I: Vocabulary/Code Set/Terminology Standards and Implementation Specifications | Interoperability Standards Advisory (ISA) (  This placement is raising concerns as it could be interpreted as appropriate for use when ordering a lab test, yet the consensus of the HL7 OO workgroup is that CPT-PLA is not intended for actual ordering lab tests, rather focused on reporting lab tests ordered for reimbursement purposes in certain situations. See for further context.

        When mapping a laboratory test order, the preferred encoding is a LOINC(R) code.  The current language in the ISA is not making this distinction, thus could lead the reader to believe that CPT-PLA is an appropriate alternative to LOINC codes for placing orders for lab tests.  We suggest that either the existing Representing Laboratory Test Ordered is updated as follows:

        • Update the Limitations, Dependencies, and Preconditions for Consideration to replace the current language with:
          1. LOINC codes are used to provide the clinical concept that the test ordered represents enabling consistent interpretation across systems and organizations regardless of an internal code specific to a laboratory that is typically used to actually order a test.  The LOINC code used as part of the order may not be the same LOINC code as the one for the performed test when the performed test code is more specific in one of the LOINC parts (e.g., method or system) or when the order combines multiple tests into a panel.  
          2. CPT-PLA classifies/encodes lab tests ordered for the relevant internal and reimbursement processes that require conveyance of the clinical information contained in the CPT-PLA code. CPT-PLA codes identify the specifics of the procedure used to perform the test as developed by a particular laboratory or in vitro diagnostics (IVD) vendor.

        Alternatively, some would suggest that ONC should consider adding a new page instead, preferably under Procedures to be named Representing Laboratory Test Procedures where the existing Representing Laboratory Test Ordered only includes references to LOINC with the limitation suggested per (1) above, while the new Representing Laboratory Test Procedures pages would focus on the CPT-PLA encoding using the suggested limitation text per (2) above.

        Lastly, considering the confusion that the comments referencing ORC-16.  We suggest that ONC adds a statement on the page in response to various comments referencing ORC-16 to state:

        • References in the comments on the use of ORC-16 do not accurately reflect the use of that field.  We refer the reader to the HL7 implementation guides for laboratory orders clarifying that ORC-16 represents the reason for the order, not a code such as LOINC, SNOMED, or CPT-PLA.  Further guidance on how and when to communicate LOINC and/or CPT-PLA codes would be identified in that guide as well.

        While HL7 could submit a comment to this end, we believe that having this clarification by ONC would be more clear.  If ONC believes that HL7 should make that comment instead of or in addition to ONC's statement directly on this page, please let us know.

ISA Comments

Merge with CPT-PLA comments

  • .See above

Interoperability Standards Advisory (ISA).

USCDI feedback

  • The ONC comment deadline is September 20, 2023 - due to Ticia by Sep 13
  • USCDI Information (Including USCDI v4) 

    ONC July 2023 Health IT Standards Bulletin (additional information) 

    ONC signaled it is particularly interested in feedback on the following: 

    USCDI Prioritization Criteria • Represent important additions to previous USCDI versions • Address and mitigate health and healthcare inequities and disparities • Address the needs of underserved communities • Address behavioral health integration with primary care and other physical care • Address public health interoperability needs of reporting, investigation, and emergency response • Require modest standards or implementation guide development • Require modest developmental burden on health IT products • Create modest implementation burden on providers and health systems • Result in modest cumulative lift for all new data elements combined. In addition, comments on interoperability of diagnostic imaging data and the ability to identify and track unique health concerns of veterans of military service are of highlighted interest.

Chat History:

  • Andrea Pitkus 1:13 PM
    • I think there is a high risk of error with keeping both on the same page. Separate pages will help keep them distinct
    • My understanding is the second page already exists.
  • Andrea Pitkus 1:22 PM
    • Especially since Nancy has focused on the procedure info the PLA offer

JIRA Triage Inventory

V2 Lab JIRAs (link)

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

FHIR Lab JIRA (link)

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

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

  • Other JIRAs from Triage Inventory - Not discussed