View source for 201701 Resource Subscription Track

[http://wiki.hl7.org/index.php?title=Category:201701_FHIR_Connectathon_Track_Proposals Return to January 2017 Proposals]
[[Category:201701_FHIR_Connectathon_Track_Proposals|Jan 2017 Proposals]]
__NOTOC__
=FHIR Resource Subscription Track=

==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
[http://www.hl7.org/Special/committees/fiwg/index.cfm  FHIR Management Group (FMG)] (Proposed)

[http://hspconsortium.org Healthcare Services Platform Consortium (HSPC)] (Proposed)

==Justification==
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
Proper workflow management and information orchestration is critical for any diverse and complex interoperable health IT ecosystem. A critical component of enabling effective workflow is the ability to receive updates on particular pieces of information of interest. 
For example, if a patient has a number of tests run during a specific encounter the results of those tests may not be immediately available. A provider that is interested in those results when they arrive could subscribe for notifications about the creation or updating of Observation resources that are associated with that encounter. Another example is where a provider may be interested in getting notifications on the progress of a specific patient’s condition.

FHIR currently provides a couple of different methods to do this:
* [http://build.fhir.org/subscription.html Subscription] – This enables a client to subscribe to notifications about updates to resources of interest.
* [http://build.fhir.org/http.html#history History Interaction] – A client can poll a server for the history of a particular resource, type of resource or all resources that have been created, updated, or deleted since a specified time.

===About the Methods===

====Subscription====
As part of the Workflow Module, the FHIR specification includes capabilities for a client to subscribe to receive notifications to resources that have been created or updated. The Subscription resource is used to define a push based subscription from a server to another system through a number of defined “channels”. The subscription includes criteria in the form of a search string that, when a resource is created or updated that match it, trigger a notification from the server through the channel specified in the original subscription request. Depending on the subscription request and channel, the notification may take the form of a simple reference, either to the search string or matching resource, or may include the content of the matching resources. One limitation of this approach is that the match criteria is run on the new version of the resource, which means that deletions do not cause notifications to be sent. Likewise, a notification will also not be sent if the new version does not meet the search criteria, even if the previous version did. This could cause a system to no longer receive notifications on resources that it had previously received notifications for.

====History Interaction====
The FHIR RESTful API Framework identifies a number of interactions that are available if a server chooses to support them. One such interaction is the history interaction, which can be used to retrieve the history of a particular resource, type of resource or all resources that have been created, updated, or deleted. Used in conjunction with its available parameters, a client system wishing to know what resources have been created/updated/deleted, can intermittently perform a history request including the _since parameter. 
 

The purpose of this track is to gain more implementer experience with workflows needing some sort of synchronization or resource updates using the  Subscription resource and history interaction polling method.  This track can be used to juxtapose the two methods for possible assessment to develop further guidance on which method to use under which cases and identify areas where more definition may be needed in the specification and help move the subscription resource to a higher maturity level.


==Proposed Track Lead==
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
See [[Connectathon_Track_Lead_Responsibilities]]

*[mailto:CoreySpears@infor.com Corey Spears] (Skype ID: javachance)
*[mailto:simone.heckmann@health-comm.de Simone Heckmann]

==Expected participants==
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
*[http://www.infor.com Infor]
*[http://health-comm.de Health-Comm GmbH]
*[http://fhir3.healthintersections.com.au/ Health Intersections]
*[http://http://hapifhir.io HAPI] (Proposed)
*[http://hspconsortium.org Healthcare Services Platform Consortium (HSPC)] (Proposed)

Please sign up!

If you're working on a server, please complete the [https://docs.google.com/a/healthedatainc.com/spreadsheets/d/1WVL09ge7SXE-Og6k3oVqWH9dcRexq76uIpGjJOBO4rQ/edit?usp=sharing "servers" tab of the Signup Spreadsheet] **This time around you'll need to update the `status` flag to indicate whether you've begun work (or completed work), so clients will know when to start testing.** You'll also share details about how a developer can obtain OAuth client credentials (`client_id` for public apps, or a `client_id` and `client_secret` for confidential apps) as well as user login credentials. You might consider simply sharing a set of fixed credentials in this spreadsheet, or else directing users to a web page where they can complete self-service registration. If absolutely necessary, you can ask developers to e-mail you directly.

If you're working on a client, please complete the [https://docs.google.com/a/healthedatainc.com/spreadsheets/d/1WVL09ge7SXE-Og6k3oVqWH9dcRexq76uIpGjJOBO4rQ/edit?usp=sharing "clients" tab of the Sprint 4 Spreadsheet]. You'll also need to update the `status` flag to indicate whether you've begun work (or completed work).


==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
===Subscription===
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
====FHIR Subscription Client====
<!-- Provide a description of the capabilities this role will have within the connectathon -->
Enable creating, updating, and deleting of subscription resources that include a search string criteria.

====FHIR Server, Subscription====
<!-- Provide a description of the capabilities this role will have within the connectathon -->
Support the receiving and processing of subscription resources and provide notifications for resources through the requested channel (if the channel is supported).

====Subscription Notification Receiver====
<!-- Provide a description of the capabilities this role will have within the connectathon -->
Receive notifications from the server over the channel identified in the subscription resource. Query for the resource information if not provided in the notification payload. (NOTE: The notification receiver may, but does not have to, be the same as the subscription client, particularly considering the receiver may be a mobile device (SMS) or secure emailing system)

===History Interaction===
====FHIR History Poling Client====
<!-- Provide a description of the capabilities this role will have within the connectathon -->
A client that polls a server for the history of a particular resource, type of resource or all resources that have been created, updated, or deleted since a specified time. 

====FHIR Server, History====
<!-- Provide a description of the capabilities this role will have within the connectathon -->
Support the history interaction providing a bundle with the matching resources.


==Scenarios==
<!-- What will be the actions performed by participants? -->
===Dedicated [https://chat.fhir.org/#narrow/stream/implementers/topic/201701.20Resource.20Subscription.20Track Zulip chat stream] for this track.===


<!--:Action: Who does what?  (Use the role names listed above when referring to the participants -->
<!--:Precondition: <!-- What setup is required prior to executing this step? -->
<!--:Success Criteria: <!-- How will the participants know if the test was successful? -->
<!--:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->

=== 1. Create an Active Subscription ===
:'''Action''': The client creates and submits a Subscription Resource for an Observation resource  where "criteria": "/Observation?name=http://loinc.org|1975-2" (Bilirubin). Be sure that the chosen channel is one supported by the FHIR Server.
:'''Precondition''': There is a FHIR Server that supports Subscription for the Resource being subscribed to and the notification channel requested is also supported.
:'''Success Criteria''': The Subscription resource is accepted by the FHIR Server.
:'''Bonus point''': Attempt to register a Subscription resource for a channel that the FHIR Server does not support
:'''Bonus point''': Subscribe to notifications where the bilirubin value is above 1.0 mg/dL.

=== 2. Search for Active Subscriptions ===
:'''Action''': The client searches for all active subscriptions on the FHIR Server
:'''Precondition''': One or more matching Subscription resource(s) exist on the FHIR Server
:'''Success Criteria''': All active subscriptions are returned in a bundle
:'''Bonus point''': The client searches for active subscriptions registered to a specific channel (url that was provided when the client created a subscription in Scenario 1)

=== 3. Delete a Subscription ===
:'''Action''': The client deletes an existing subscription resource.
:'''Precondition''': The subscription resource already exists on the FHIR server.
:'''Success Criteria''': The subscription service is deleted from the FHIR Server 
:'''Bonus point''': The client deletes all Subscription resources registered to a particular channel

=== 4. Receive a Subscription Notification ===
:'''Action''': The FHIR Server has a resource matching a subscription criteria added and the notification is received by the client identified in the registered channel. Use the example in Scenarios 1 (Bilirubin)
:'''Precondition''': A matching subscription is registered on the FHIR Server and the registered notification channel is prepared to receive the notification
:'''Success Criteria''': The client on the registered notification channel receives the notification 
:'''Bonus point''': Update the Bilirubin Observation resource with a value of 1.4 mg/dL, and the client receives a notification for the high bilirubin observation subscription 

=== 5. Retrieve a History Content Bundle for Observations ===
:'''Action''': The client makes a history request for all Observations that have been created since a certain date
:'''Precondition''': Observation resources exist on the FHIR Server
:'''Success Criteria''': The Observation resources are returned by the server
:'''Bonus point''': The client makes a history request for all bilirubin Observations.

<!-- Provide a description of each task -->

==TestScript(s)==
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested.  
These should be committed to SVN under trunk/connectathons/[connectathon]
-->
The supporting TestScripts and corresponding fixtures will be committed to the FHIR SVN.

==Help Links==
[http://build.fhir.org/subscription.html Subscription Resource Definition]