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

Connectathon Agenda

Official hours of FHIRcast Connectathon track (zoom will be open during this time):

  • Thursday, May 14, 2020: 9am ET – 6pm EST
  • Friday, May 15, 2020: 9am ET – 6pm ET with wrap-up from 6-630pm ET

Touchpoints

Touchpoints will be held on this zoom line at the following times (All ET)

Submitting WG/Project/Implementer Group: Infrastructure & Messaging, Imaging Integration

Justification and Objectives

FHIRcast provides modern, simple, application context synchronization. We're working within the RIS/PACS community and beyond to standardize FHIRcast as the common, lightweight standard. We are finishing ballot resolution for our STU2 ballot. This connectathon is important to support basic connectivity and testing of the STU2 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.

Related tracks

Subscriptions (for websockets?)

Proposed Track Lead

Isaac Vetter - isaac@epic.com

Expected participants

Expecting around 6 or so participants. 

Track Orientation

A webinar will be hosted on Tuesday, April 28th at 10am Central to share further participation information about this track.

See slides from coordination call.

Questions, help and chat on zulip!

https://chat.fhir.org/#narrow/stream/179271-FHIRcast/topic/May.202020.20FHIRcast.20virtual.20connectathon


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 the spec. 

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.

  • No labels