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:  May 26, 2023

Time: 10AM ET

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

Attendees: Marti Velezis (Sonrisa / FDA), JD Nolen (Mercy Children's Hospital), Dave Hill (Mitre), KathyWalsh (Labcorp), Matt Elrod, Riki Merrick (Vernetzt, LLC / APHL), Michael Lingenfelter (CDC), Scott Fradkin (Flexion), John King (Flexion), Andrea Pitkus (UW), Ralf HErzog (Roche), Brian Handspicker, Rob Hausam (Hausam Consulting, Maria D. Moen

Chair: JD Nolen

Scribe: Riki Merrick

  • Quorum Met 


  • IG Proposal
  • Workflow Topics
    • Device Association Impact Assessment related to WorkflowResources:
    • Updates from BPM+
    • Other updates relevant to workflow
  • JIRA Tickets 
  • AOB?

Meeting Resources

PSS: PSS-2101

IG Proposal: Clinical Order Workflow (COW)

JIRA Tickets: OO Workflow JIRAs

JIRA Grouping Tag:

  • OO-COW - to indicate when the JIRA Ticket should be reviewed by the OO Clinical Order Workflow SMEs, especially when the issue is not assigned to the Resource owner.

Background Materials


  • JIRA Tickets
    • PACIO Topic - re: Service Request (David Hill )
      • Use of US Core Service Request vs Consent for Treatment to express patient advance care preferences as part of the PACIO Advance Directives Interoperability IG.
      • Originally used goal for preferences, but then decided to use observations
      • At WGM had more discussion and going back
        • Preference = what, without how to do it = use goal
        • when explicit about how = use ServiceRequest
        • but then were told to use Consent for treatment
        • what codes are in consent.purpose?
          • ADD LINK (V3 purposeOfUse)
        • problem is that the use case is hypothetical
        • is this similar to transport (documentation of vs. actually making this happen)
          • use task to operationalize it
        • For discussion slides from Dave Hill
        • We think ServiceRequest is not a good fit
        • Next steps:
          • use consent (and maybe ServiceRequest) and model the different advanced directives they want to cover to see how well it fits
  • IG proposal:
    • Updates made to the Clinical Order Workflow (COW) IG Proposal which is still in the "pending' state.
    • Action item from 4/28: Please review the IG proposal and make any comments on the proposal with any related IGs and/or additional use cases
      • No comments added to that meeting page with suggestions
      • Need to determine when the IG proposal will be submitted
      • Leave the ? after Immunization / medication – take out pharmacy related references
      • Does inventory fit into “clinical” order?, though the same principal should also apply to inventory, but those are not clinical
      • Add BPM+ to involved parties
      • Add SDOH Clinical Care IG and Gravity project code extensions as content source
      • Examples:
        • Ordering DME post hospitalization
        • Ordering medically appropriate home delivered-meals post hospitalization
      • Next steps:
        • Review and bring back next week

Next meeting: June 2, 2023

JIRA Backlog (time permitting)

Chat history