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: June 30, 2023

Time: 1PM ET

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


JD Nolen, Rob Hausam, Marti Velezis, Dan Rutz, Andrea Pitkus, Kathy Walsh, Ralf Herzog, Sheryl Taylor, Alex Mays, Sara Armson, Joellen Carter, Hans Buitendijk

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

  • Reviewed JIRA and ran into a scope challenge
  • JIRA FHIR-39619 raises questions about Task ownership, not only the attribute, but also workgroup.
  • Workgroup ownership to be addressed between now and September workgroup meeting.
  • JIRA to be progressed by COW/FOE project team.

Meeting Notes

  • 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. 
  • See Craig's v2 micro question:"v2discretemicroquestion"-Listservemessage(fromCraig)
    • Considering whether to use a similar approach to susceptibilities and use OBX-30 Observation Sub-Type.
    • Attached is the sample Craig created for review: Micro Example
    • Will discuss next week.

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 7, 2023

Chat History