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: March 17, 2023

Time: 10AM ET

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

Attendees: Ralf Herzog (Roche), Marti Velezis (Sonrisa / FDA), Rob Hausam (Hausam Consulting), Scott Fradkin (Flexion), Ana Szarfman (FDA), Kathy Walsh (Labcorp), Kayla Perkins, Michael Lingenfelder (CDC), Gelu Comanescu (CDC), Annie Raval (CDC), Dan Rutz (Epic), Brian Handspiker, Riki Merrick (Vernetzt, LLC / APHL)

Chair: Ralf Herzog

Scribe: Riki Merrick 

  • Quorum (Co-chair +2) Met 


  • Workflow Topics
  • JIRA Tickets 
  • AOB?

Meeting Resources

PSS: PSS-2101

IG Proposal: Clinical Order Workflow (COW)

JIRA Tickets: OO Workflow JIRAs

Background Materials


JIRA Backlog

Clinical Order Workflow

  • IG
  • Continue Workflow discussion (i.e., Lab order slides)
    • What is the level of this project – could or should?
      • Standard guidance for dealing with orders = implementation orders
      • NICTIZ is trying to move lab integrations to FHIR by 2025 – this project needs to be should, else it will be mute, if we don’t come ut with something folks should use
    • ServiceRequest may need a FillerOrderNumber, but internally they may not need to persist it on their end, but need to be able to communicate that ID, if we cannot do that in the task
    • FHIR is just the communication layer, it does not prescribe the internal data structure
    • There is a need for businessIdentifer, do we also need a businessStatus on ServiceRequest?
    • We should make sure we have a clear description of the relationship between the business statuses of the order and the results – until the order is completed
    • Placer Service Request – communicate the request to the filler and then the filler creates their Service Request linked via task – how is the update exchange
    • Do we need to support the messaging paradigm
    • Where is the authorization to perform?
      • It is carried in the ServiceRequest
        • Result of the initial serviceRequest may result in additional referrals to other services- but we need to track that those ServiceRequests are linked to that original ServiceRequest
      • Task is the mechanism to identify who is going to track the mechanical deals of the fulfillment of the action authorized in the ServiceRequest