This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201809 FHIRcast"

From HL7Wiki
Jump to navigation Jump to search
m (add coordination call info.)
m (→‎Hub: support bidirectional)
Line 54: Line 54:
 
* Must verify subscribed callback urls.
 
* Must verify subscribed callback urls.
 
* Must POST notifications to subscribed callback urls.
 
* Must POST notifications to subscribed callback urls.
 +
* Must accept context change requests from subscribers and respond with a valid HTTP status.
  
 
===Subscriber===
 
===Subscriber===

Revision as of 15:12, 21 August 2018


FHIRcast

Dedicated Zulip chat stream for this track.

Previous FHIRcast Connectathons

Submitting WG/Project/Implementer Group

Imaging Integration, FHIR-I, CDS

Justification

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 identify a common, lightweight application synchronization standard.

This track will prototype this workflow synchronization using a webhooks pattern with FHIR as the underlying content data model according to the draft FHIRcast specification.

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities

Isaac Vetter

Track planning, coordination teleconference info

Thursday, September 20, 2018 - 9:00 am - 10:00 am Central

Webex meeting - Click the link to open the meeting in webex.

  • Meeting number (access code): 806 981 149
  • Meeting password: iNAPZCE3 

Join from a video system or application

  • Dial 806981149@epic.webex.com 
  • You can also dial 173.243.2.68 and enter your meeting number.  

  Join by phone 

  • 404-397-1525 US Toll
  • 877-309-8689 US Toll Free 

FHIR version

STU3

Expected participants

Sectra, Epic, Siemens, Agfa, <your name here!>

Roles

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.

Subscriber

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

  • Must request subscription to topic and events on hub url.
  • Must respond to url verification.
  • Must accept event notification.

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 open-patient-chart, close-patient-chart for events for connectathon.
Success Criteria: Hub persists subscription.
Bonus point: n/a

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*10: Subscriber changes its UI to match the patient-chart-open event.

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

Action: Subscribing client launches from Hub, according to SMART EHR launch.
Precondition: n/a
Success Criteria: Subscriber receives hub base url and hub.topic in SMART launch and performs scenario #1.
Bonus point*100: Subscriber launches using SMART standalone launch.