Skip to end of metadata
Go to start of metadata






Ralf HerzogRoche
JD NolenChildren's Mercy Hospital
Jose Costa Teixeira
Smita Hastak
Freida HallQuest Diagnostics
Rob HausamHausam Consulting
Andrea PitkusUW
Kathy WalshLabCorp
Susan MatneyIntermountain
Hans BuitendijkCerner
Lorraine ConstableConstable Consulting
Nathan Davis
Rik Smithies

Chair:Hans Buitendijk

Scribe: Hans Buitendijk


  • Minutes 
    • 2020-09-21-25 
      • Missing administration quarter
      • Links to be completed.  Co-chairs need to check
    • 2020-10-15 - Motion to accept the minutes.  Rob Hausam, Ralf Herzog
      • Against:0; Abstain: 2; In Favor: 11
  • Administrivia:
  • Inventory into Build
    • FHIR-29208 - Getting issue details... STATUS   Motion to start a draft resource for Inventory Status Report into FHIR R5 Build  Jose, Lorraine
      • Against: 0; Abstain: 5; In Favor: 8
  • OO-BR&R Topics
    • DiagnosticReport - Dispositions and votes are in the JIRA.
    • Process (or organization/person) for regulatory inspection use case focused updates. - Not discussed
    • FMG update
    • Monday, October 26 – 3-4pm ET continues with  Substance/SubstanceDefinition/PackagedProductDefinition

  • v2 Change Requests
    • New Message Format for Inventory Update Message
      • Double Check the rules on backward compatibility of creating a group.  If not allowed, will need to create a new message. - Hans Buitendijk: Check on compatibility rules.
      • Clarified that ROL was deprecated.
      • Per Chapter 2, Section 2.8.2, d):
      • The repeatability of a message constituent MAY be changed. A sending system SHOULD be able to send the modified message constituent; the receiver, regardless of its version level, SHOULD be able to understand the message. Note that if a non-repeating message constituent is made repeating, information sent in the new repetitions could be lost to the recipient who is not expecting them.

        If HL7 has given, or will give, semantic meaning to the first instance, to allow backward compatibility, the first instance of the repeating constituent SHALL have the same meaning as the non-repeating constituent had in the prior version of HL7. In this way, a receiving application that interprets the message based upon the prior standard would continue to find the same intent communicated in the message.

        If HL7 has not given, and will/can not give, semantic meaning to the first instance, and one or more implementation-applied business rules exist to select one of several occurrences to populate a non-repeating constituent, those same rules SHOULD be applied when a newer version of the standard allows for repetition of the constituent. By applying the prior business rules to determine the first occurrence of a repeating constituent, a receiving application that interprets the message based upon the prior standard would continue to find the same intent communicated in the message.


        That implies we can add an {} group to an existing message structure.

    • Identify the “original” Specimen/Container ID in addition to the parent Specimen/Container ID
      • An alternate approach is to link grandchild to child to parent.
      • Should we have a preferred sequence?  Challenge is that generally, v2 does not want to rely on sequence of componentry in repeats.
      • Ralf Herzog : check with Ulrike Merrick

  • Project updates - Not discussed
    • Nutrition
      • Met this week (9/30/2020)
      • Reviewed updating DAM scope, aligning with MCC E care plans (PC is sponsoring) 
      • Meeting
        • Every other Wednesday 2-3 ET
      • Project page link: Nutrition
    • Specimen DAM
    • FHIR - OO on FHIR
      • No meeting next week
      • Meeting
        • Every Tuesday 2 - 3 PM ET
      • Project page link: FHIR
      • IHE needs to update Volume IV to reflect CMS vocabulary.
      • Also needs to consider alternative use of ORU to clarify how OBX could be used, plus mapping to FT1.
      • CDSM connection is still proprietary, interest to get CDS Hooks/Standards.
      • Change to the name of the LOINC Code. 
    • CIMI/Concept Modeling - NO UPDATE
      • Co-chair will meet to discuss the future of the group – Lorraine will check what’s up
      • Need to sort out Post-Acute Orders vs. DME (as in NIB).
      • Check with Bob Dieterle.  Needed before publication.
      • Project Page Link: DME Project
    • Healthcare Product: Device/DeviceDefinition/UDI
      • UDI DAM in ballot recon
      • 17 items in discussion 
      • BR&R - meeting October 12th on substance, substance definition, package products definition  
      • Resource Proposal Updates
      • Meeting: Every Monday 3 -4 PM ET
    • V2+  NO UPDATE
      • Still need to look at open tickets and message structure issues (debate continues) 
      • Meetings:
        • Every other Friday, 9-10am ET
      • Project Page Link: V2+
    • V2-to-FHIR 

    • US Realm Lab (eDOS/LOI/LRI) 
      • Frieda updating documents for publication 
    • Product Grid – no update, is not needed this cycle
      • Possible review at WGM  
      • Co-chair meeting to re-group.
      • Need to still review the status of our standards in the product grid:
        • Status definitions - Riki to follow up to see where those are in the grid - here are the ones given to TSC:
          • active, planned use or in use, future maintenance release
            • stable, in use, generate feedback, not active
            • review, not updated in foreseeable future
            • deprecated - deprecated - no further work planned - if not already using, it is not recommended to be implemented