Difference between revisions of "201801 FHIR Subscriptions"
Isaacvetter (talk | contribs) (Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
Isaacvetter (talk | contribs) |
||
| Line 2: | Line 2: | ||
[[Category:201801_FHIR_Connectathon_Track_Proposals|Jan 2018 Proposals]] | [[Category:201801_FHIR_Connectathon_Track_Proposals|Jan 2018 Proposals]] | ||
__NOTOC__ | __NOTOC__ | ||
| − | = | + | =FHIR Subscriptions= |
| + | |||
| + | '''Dedicated [https://chat.fhir.org/#narrow/stream/subscriptions/subject/Jan.20Connectathon.20track Zulip chat stream] for this track.''' | ||
| + | |||
| + | |||
| + | '''Previous Care Plan Connectathons''' | ||
| + | * [[201709 FHIR Subscriptions]], September 2017, San Diego, CA | ||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| − | + | Imaging Integration, FHIR-I, CDS | |
==Justification== | ==Justification== | ||
| − | + | The Imaging Integration is sponsoring a [https://docs.google.com/document/d/165BU5ZmUyuwxz4kg2dtjRWkNM7o4u2PrdcIKSxP94Ts/edit?usp=drive_web project] to create a new context synchronization profile using FHIR Subscriptions called [https://fhircast.org FHIRcast] (FHIR-I and CDS are co-sponsors). | |
| + | |||
| + | This track is an important step in advancing the maturity of the interactions and resources associated with both FHIRcast and FHIR Subscriptions in general. | ||
| + | |||
| + | The subscription pub/sub pattern enables FHIR clients to retrieve data from a server without performing a more expensive periodic polling queries. This model also enables workflow event-based notifications that could keep two applications data in sync, but also synchronize their context. We're working within the RIS/PACS community to identify a common, lightweight application synchronization standard. | ||
| + | |||
| + | This track will attempt to prototype this event-based concept on top of the existing FHIR Subscription REST hook and criteria element and prototype this workflow synchronization using FHIR Subscriptions according to the draft [https://fhircast.org FHIRcast specification]. | ||
| + | |||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
| Line 16: | Line 29: | ||
==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 --> | ||
| + | Agfa, Applicadia, Agfa | ||
==Roles== | ==Roles== | ||
Revision as of 15:39, 17 October 2017
FHIR Subscriptions
Dedicated Zulip chat stream for this track.
Previous Care Plan Connectathons
- 201709 FHIR Subscriptions, September 2017, San Diego, CA
Submitting WG/Project/Implementer Group
Imaging Integration, FHIR-I, CDS
Justification
The Imaging Integration is sponsoring a project to create a new context synchronization profile using FHIR Subscriptions called FHIRcast (FHIR-I and CDS are co-sponsors).
This track is an important step in advancing the maturity of the interactions and resources associated with both FHIRcast and FHIR Subscriptions in general.
The subscription pub/sub pattern enables FHIR clients to retrieve data from a server without performing a more expensive periodic polling queries. This model also enables workflow event-based notifications that could keep two applications data in sync, but also synchronize their context. We're working within the RIS/PACS community to identify a common, lightweight application synchronization standard.
This track will attempt to prototype this event-based concept on top of the existing FHIR Subscription REST hook and criteria element and prototype this workflow synchronization using FHIR Subscriptions according to the draft FHIRcast specification.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
Expected participants
Agfa, Applicadia, Agfa
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
