This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201809 FHIR Subscriptions"
Jump to navigation
Jump to search
Isaacvetter (talk | contribs) (Created page with " Sept 2018 Proposals __NOTOC__ =FHIR Subscriptions= '''Dedicated [https://chat.fhir.org/#narrow/stream/subscriptions/sub...") |
|||
| Line 56: | Line 56: | ||
:Success Criteria: FHIR server pushes FHIR payload of relevant resource using REST Hook when the subscribed event occurs in the FHIR server.. | :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 | :Bonus point: n/a | ||
| + | |||
| + | ==Notes== | ||
| + | Please discuss/explore this tracker issue: [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14646] | ||
Revision as of 20:46, 27 August 2018
FHIR Subscriptions
Dedicated Zulip chat stream for this track.
Previous Subscriptions Connectathons
- 201709 FHIR Subscriptions, September 2017, San Diego, CA
- 201801 FHIR Subscriptions, January 2018
Submitting WG/Project/Implementer Group
FHIR-I
Justification
This track is an important step in advancing the maturity of the interactions and resources associated with FHIR Subscriptions.
The subscription pub/sub pattern enables FHIR clients to retrieve data from a server without performing a more expensive periodic polling queries.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
FHIR version
STU3
Expected participants
Cerner, <your name here!>
Roles
FHIR Server
The FHIR Server supports the Subscription resource and pushing relevant FHIR resources to client.
- Must expose a Subscriptions resource supporting read, create and update.
- Must also act as a FHIR client to send notifications.
Subscribing client
Subscribes to FHIR server and gets updates.
- Must create a Subscriptions instance on external FHIR server.
- Must expose an endpoint to accept notifications.
Scenarios
Create FHIR Subscription
- Action: Subscribing client creates a Subscription instance on FHIR Server.
- 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
Notes
Please discuss/explore this tracker issue: [1]
