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: August 8, 2023

Time: 2-3 PM ET

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


Marti Velezis (Sonrisa / FD), Elliot Silver (ResMed), Ed Heierman (Abbott / IICC), Rob Hausam (Hausam Consulting), Kathy Walsh (Labcorp), Hans Buitendijk (Oracle), David Barwin, Riki Merrick (Vernetzt, LLC / APHL)

Co-chair: Hans Buitendijk

Scribe: Riki Merrick

  • Quorum (Co-Chair + 2) Met 


    • Review of Spreadsheet
    • Question about sequence diagrams / search criteria etc
    • Ballot in January
    • JIRAs Triage
  • Other?

Meeting Resources

LIVD Mapping spreadsheet

Meeting Minutes

Previous Meeting Notes


  • Outstanding discussion on the LIVD Spreadsheet / template
  • LOINC mapping tab
    • Each row for a map has a publication version as well as a LOINC version
  • Translates into the LIVD template
    • TestCodeConceptMap
      • Publication version ID
        • value is identifier.value and identifier system (= publisher name)
        • in example have 3 different conceptMaps – one for each mapping timepoint
      • LOINC version ID
        • Have created a group of target for the code system, that shows the targetVersion
      • group.source the combination with should be unique
        • list of observationDefinitons as code system cannot be done in FHIRR5, but may be coming back in R6 (@Rob H??)
        • we need to link to the observationDefinition to be able to pull in the reference ID as well as well as the vendor Analyte code
        • other choice would be to create a code systems for observationDefinitions – assume we have the same amount of entries – can still get all the identifiers and codes and now you have the group.element.code is actually an ID, = implicit code system, which Terminology Infrastructure doesn’t like
        • we could in theory still even put different codes with descriptions, but only if they are true equivalents
        • Hans will delete the display column and will make an explanation what goes into the code element

Next call time

  • Ed is out 8/24 – 9/8
  • Can we use 8/15 same time again for LIVD – OO on FHIR will be ok to have a break
  • Can then use to have 8/22 as a back up, if needed
  • Hans will update the call calendar and also create a calendar invite to send to Ed

JIRA Triage

  • LIVD IG - Stale Tickets that are Waiting for Input; need to address these and/or reject the request if they are no longer relevant.

T Key Summary Assignee Reporter P Status Resolution Created Updated Due

From Chat

<add chat here>

Call Adjourned at....

Next Meeting: 

Next Time: 

<Add any overflow items here>