Skip to end of metadata
Go to start of metadata


Facilitator:  @

Note Taker: @ 





Mayo Clinic

Nick Radov Co-chair

United Healthcare

Isaac Vetter  Co-chair




Nuance Communications



David QuiEpic


Nuance Communications

Vernetzt, LLC


Create Decision from template

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).

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Decision Link(if not child)
ManagementQuorum reached (co-chair + 2) Yes/No

Management Minute Approval

Paul goes first. [FHIR-39545] Hubs should be agnostic towards events they pass - Jira (

Timeboxed to 10 minutes: End by 9:17a Central


  • loadPriors - load and hang the specified study as a prior in an existing CAM.
    • Eric: Imagingstudy-update could support this. 
  • getMeasurements - get all the measurements for specified study/series. 
    • GetCurrentContext would return measurements if they've been contributed to the session via an update. 
    • otherwise FHIR server
  • showMessage - Show a message dialog with provided information.
  • copySelectedViewportContentToClipboard - Requests the application to copy the content of the selected viewport to clipboard.

MethodologyPRs: Pull requests · HL7/fhircast-docs (

Bas': FHIR-37120 - additional calls continuing

Prepped jiras:

Finish on next call: [FHIR-36082] event key names and including resource references - Jira (

  • "legacy events deviate from ... "


    • Applications mustn't receive information for which they are not authorized. It's incumbent upon the Hub to enforce authorization. 
      • For example, a subscriber without authorization to access Observation resources, shouldn't receive Observations as part of a DxReport-update event.
      • This is interestingly mitigated because FHIRcast's typical use-case is that the same user is using the various apps. 

Outstanding jiras:

Next agenda

  • Fyi - Isaac's outage
  • Gino's PR
  • SubIGs strategy:
    • The FHIRcast spec is the "base spec" and we will instruct/encourage the creation of use-case specific subIGs
      • IHE creates the collaborative report creation via content sharing IG
      • We need to create the simple "SMART app gets context sync" use-case IG
    • What guidance to give for when to create a subIG?
      • subIGs have FHIR profiles, base doesn't?
    • Could we put FHIRcast into base FHIR?
      • base FHIR is updated less frequently (iav: really, is that actually true?)
      • Perhaps R6 is the last big update?

Management Next agenda

 Adjourned at

Supporting Documents

Outline Reference

Supporting Document

Minute Approval
FHIRCast Jira not done

T Key Summary Assignee Reporter P Status Resolution Created Updated Due

Action items