Difference between revisions of "201805 FHIRcast"
Isaacvetter (talk | contribs) |
Isaacvetter (talk | contribs) |
||
| Line 35: | Line 35: | ||
==Expected participants== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
| − | Sectra, Epic, | + | Sectra, Epic, Siemens |
==Roles== | ==Roles== | ||
Revision as of 21:27, 3 April 2018
FHIRcast
Dedicated Zulip chat stream for this track.
Previous FHIRcast Connectathons
- 201801 FHIR Subscriptions, January 2018, New Orleans, LA
- 201709 FHIR Subscriptions, September 2017, San Diego, CA
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.
Following implementer feedback at the January Connectathon, we altered the draft spec from a new UserSession FHIR resource and FHIR Subscriptions. This track is an important step in validating and advancing the maturity of the new interactions and resources associated with both FHIRcast. This updated specification is under active review in the community.
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
FHIR version
STU3
Expected participants
Sectra, Epic, Siemens
Roles
Workflow system
The Workflow system manages user's sessions, accepts subscriptions and is responsible for notifications.
- todo
Subscribing client
Subscribes to user's session and gets updates.
- todo
Scenarios
Create Subscription via SMART launch
- Action: Subscribing client launches from .
- Precondition: n/a
- Success Criteria: Subscribing client POSTs new subscription resource to FHIR server. FHIR Server persists active subscription resource. Subscribing client can read newly created Subscription.
- Bonus point: Subscribing client updates Subscription instance's status element to _off_ once the subscription is no longer needed. FHIR server respects this setting.
REST Hook with payload of "payload": "application/fhir+json"
- Action: FHIR Server notifies Subscribing client by pushing a FHIR resource to the endpoint identified in the subscription resource instance.
- Precondition: Create FHIR Subscription scenario
- Success Criteria: FHIR server pushes FHIR payload of relevant resource using REST Hook when the subscribed event occurs in the FHIR server..
- Bonus point: n/a
FHIRcast
- Action: FHIR Server notifies Subscribing client by pushing a FHIR resource to the endpoint identified in the subscription resource instance.
- Precondition: Previous two scenarios; FHIR Server publishes workflow-type EventDefinition named "patient-chart-open" as described by FHIRcast.
- Success Criteria: FHIR server pushes UserSession using REST Hook when the subscribed event occurs in the FHIR server. Subscribing client changes its UI to match the patient-chart-open event.
- Bonus point: FHIR Server detects error scenario and reacts according to its own configuration.
