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: July 07, 2023

Time: 1PM ET

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


Marti Velezis, Dan Rutz, JD Nolen, Kathy Walsh, Andrea Pitkus, Pam Banning, Hans Buitendijk, Riki Merrick, Craig Newman, Ralf Herzog

Chair: Hans Buitendijk

Scribe: Hans Buitendijk

  • Quorum (Co-Chair + 4) Met 


Meeting Resources

JIRA Dashboards:

JIRA Grouping Tags:

  • 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  

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  

New Rule on Race/Ethnicity from OMB/CDC


  • Follow-up date  
  • Need to follow-up with AMA representative

Update from FHIR Clinical Order Workflow call

Meeting Notes

    • The IG uses homogenous, but other text would imply a catalog can have a variety of content.
    • If that is the intent, then it would have to be discussed and get further clarifying text.  That could be
    • Motion to accept the update as proposed.  JD Nolen, Marti Velezis
      • Against: 0; Abstain: 2; In Favor: 6
  • FHIR-32154 - Getting issue details... STATUS
    • We recognize that the Observation.status and DiagnosticStatus of preliminary may seem the same, but cannot be defined the same.  How exactly it is going to be defined is not clear yet as that depends on how the panel discussion unfolds that aims to resolve how a more complex, multi-tiered panel is expected to be represented in DiagnosticReport and Observation, particularly considering that sub-branches of a multi-tiered panel could be ordered as part of the larger panel, or individually.
    • The Observation.status must definition and notes must be clear on whether it:
      • describes the status of that individual instance only
      • the status of that instance inclusive of the summary of the .hasMember observations
      • or that we need a status for one AND the other.
    • In the panel discussion we must understand how one can order, i.e., does it yield one or multiple ServiceRequest instances for a complex, multi-tiered panel, as well as how the representation varies if a sub-panel is reported as an Observation when ordered as part of a complex, multi-tiered panel while as a DiagnosticReport when ordered on its own.
    • Until we have that resolved, this JIRA should stay open to understand what the "with mod" would encompass as part of an overall "non-persuasive" as the statuses would in any approach reflect something different and need to be defined/clarified separately (while being aligned on clarity).
  • See May WGM carry-over FHIR JIRA Tickets below - Not discussed

JIRA Triage

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:

Next Meeting: July 14, 2023

Chat History

Andrea Pitkus to Everyone (Jul 7, 2023, 1:38 PM)
Pam, Kathy, also thinking of interpretations in panels where some results are complete and others are not and interdependicies
Also calculated results are interdependent too.  Ca may be done, but not creat and you wouldn't report ca/crea ratio without both.
Andrea Pitkus to Everyone (Jul 7, 2023, 1:48 PM)
are they separate assays/results/observations?
TO correctly reflect panels, the service request panel order would be linked ot observations in DR

The service request panel order would be linked ot observations in DR
The observations/results of a panel would be based upon the Serv Req.  Hct based upon CBC,
Andrea Pitkus to Everyone (Jul 7, 2023, 1:59 PM)
we're not quite there in the COW examples ;)
Are there examples where in your test directory they have the sample reports

Follow-up Next time: 

  • V2.9 JIRA
    • This addressed JIRA v2-25518 where V2Mgmt agreed to adjust the name of RFR.2 and allow for both HL70001 and HL70828 to be used.
    • Various concerns were raised on:
      • the name change to still include administrative sex as the purpose is very much in context of the relevant sex for clinical use - how to interpret the result
      • the choice of tables still leaves ambiguity on the meaning as HL70001 allows for values that are not appropriate, while HL70828 is not widely used (yet)
      • the ordering provider may not include a specific value according to the soon to be included new segments to convey the sex for clinical use, so what should a PID-8 value be mapped to when OM2 / the lab used HL70828 for the reference ranges.
    • We cannot assume a transition will be immediate so that ordering provider and lab are all aligned on the same value set.
    • An alternative that was discussed with V2Mgmt is to add RFR.8 to better support a transition.
    • Other than concerns with the resolution, no clear alternative was provided.
    • V2Mgmt will meet July 7 where anybody is welcome to help resolve. 
  • DeviceAssociation - Impact Assessment - for July 14, 2023