Skip to end of metadata
Go to start of metadata

Date:   

Facilitator:  @

Note Taker: @ 

Attendees

Present

Name

Affiliation


Mayo Clinic

Nick Radov Co-chair

United Healthcare

Isaac Vetter  Co-chair

Epic

Epic

Phillips

Nuance Communications

Siemens

Altarum     

David QuiEpic

Siemens

Nuance Communications

Vernetzt, LLC



Canon

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


Isaac's outage: 3/16 - 4/10. Need to identify someone to lead the InM FHIRcast call. 

Hey Nick Radov , are you able to join the InM FHIRcast call for these three weeks? 

  • Isaac to ensure Bas is technically able to start zoom call. 


Bas': FHIR-37120 - additional calls continuing




Gino: FHIR-37285, PR: Pull requests · HL7/fhircast-docs (github.com)


Prepped jiras:




Prepped jiras:




Oustanding:

  • https://jira.hl7.org/browse/FHIR-37317
    • 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:



Methodology



Management

 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?


 Adjournment
 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
Loading...
Refresh


Action items

  •