Page tree
Skip to end of metadata
Go to start of metadata

Mark your calendar for the Track Orientation call

A webinar will be hosted on Tuesday, September 3rd at 9am Central to share further participation information about this track. Here's the conference call info:


Click this link to join.

Join by phone 
Tap to call in from a mobile device (attendees only) 
404-397-1525 US Toll 
877-309-8689 US Toll Free 
Global call-in numbers  |  Toll-free calling restrictions  
 
Join from a video system or application
Dial 809213663@epic.webex.com 
You can also dial 173.243.2.68 and enter your meeting number.  
 

Join using Microsoft Lync or Microsoft Skype for Business

Dial 809213663.epic@lync.webex.com

Justification and Objectives

The Imaging Integration working group is sponsoring a project to create a new context synchronization profile called FHIRcast (FHIR-I and CDS are co-sponsors). We're working within the RIS/PACS community to standardize FHIRcast as the common, lightweight application synchronization standard. We are finishing ballot resolution for our STU1 ballot and defining the scope of an STU2. This connectathon is important to flesh out our implementation of websockets for STU2, as well as support basic connectivity and testing of the to-be-published STU1 spec and to explore how to enable exchange of discrete, draft, image measurements.

This track will prototype this workflow synchronization with FHIR as the underlying content data model according to the specification: https://fhircast.org

This track will use any version of FHIR.


Dedicated Zulip chat stream for this track

Previous FHIRcast Connectathons

Submitting WG/Project/Implementer Group

Imaging Integration, FHIR-I, CDS

People

Proposed Track Lead

Isaac Vetter

Expected participants

Sectra, Epic, maybe Nuance, Visage, Agfa, Philips.

We usually end up with 6 or so participants. 

Related tracks

Subscriptions.

Technical Information

System Roles

Checkout our reference implementation and other opensource FHIRcast projects at: https://github.com/fhircast .

Hub

The Hub manages users' sessions, accepts subscriptions, is responsible for notifications and is closely aligned with the SMART server and FHIR server.

  • Must accept new subscriptions.
  • Must verify subscribed callback urls.
  • Must POST notifications to subscribed callback urls.
  • Must accept context change requests from subscribers and respond with a valid HTTP status.
  • May support websockets as described in our wiki.

Subscriber

Subscribes to a user's session topic on the hub, receives and processes event notifications.


Scenarios

Subscriber creates new subscription; hub respond with 202

:Action: Subscriber POSTs WebSub subscription request to hub for a specific hub.topic and hub.events.
:Precondition: Subscriber must know hub base url, hub.topic (session identifier) and supported events. Use ''Patient.open'', ''Patient.close'' for events for connectathon.
:Success Criteria: Hub persists subscription.
:Bonus point: Subscribe via websocket.

Subscriber is notified of user session change per subscription

:Action: Hub/Publisher POSTs notification to subscriber for a subscribed event and topic/session.
:Precondition: Subscriber subscribes correctly, see previous scenario.
:Success Criteria: Subscriber responds with 2xx code.
:Bonus point: Subscriber validates X-Hub-Signature.
:Bonus point: Notify client via established websocket connection.

Subscriber requests user session change 

:Action: Subscriber POSTs context change request to Hub's topic url.
:Precondition: Subscriber subscribes correctly, see initial scenario.
:Success Criteria: Hub responds with 2xx code.
:Bonus point: Hub accepts context change and broadcasts corresponding notification.
:Bonus point: Hub rejects context change and subscriber handles synchronization failure.

Subscriber communicates discrete, draft measurement

:Action: Subscriber POSTs ''Observation.open'' change request to Hub's topic url where ''Observation.category=imaging'', ''Observation.status=preliminary''.
:Precondition: Subscriber subscribes correctly, see initial scenario.
:Success Criteria: Hub responds with 2xx code.
:Bonus point: Hub accepts context change and broadcasts corresponding notification.

Subscriber is notified of topic/session id, hub url during SMART app EHR launch from Hub

:Action: Subscribing client launches from Hub, according to SMART EHR launch.
:Precondition: n/a
:Success Criteria: Subscriber requests fhircast scope and receives hub base url and hub.topic in SMART launch and performs scenario #1.

Subscriber is notified of topic/session id, hub url during SMART app standalone launch

:Action: Subscribing client initiates SMART standalone launch using Hub's OAuth2 server, according to SMART EHR launch.
:Precondition: n/a
:Success Criteria: Subscriber requests fhircast scope and receives hub base url and hub.topic in SMART launch and performs scenario #1.
:Bonus point: Subscriber evalutes multiple returned sessions and chooses between them.

Security & Privacy Considerations

  • No labels