· Nov 2, 2016

Healthshare FHIR Subscriptions

Hello All,

   Having a recent project to create a FHIR repository, I want to know (as looking at the code) if HealthShare FHIR implementaton supports subscriptions?.  I know it records the subscriptions ok, BUT does it handle sending the subscription out (based on the tags) to an endpoint (i.e. when a new FHIR request commits data that would trigger the subscription) ?, I'm 50% it doesn't, but would rather find out for sure before shoe horning something in.



Discussion (9)0
Log in or sign up to continue

Correct, out of the box HealthConnect's FHIR server doesn't offer any post-processing of Subscription resources. This is something we will offer in the future as the solution matures however, it is still possible to hook into the existing FHIR server to build a subscription processing engine. You are not the first person to ask about this and we are working on a  quick write-up on where/how to implement that processing.

Matthew Spielman, Product Manager
HealthShare Information Exchange, Personal Community
InterSystems Corporation

FHIR subscriptions are still immature FHIR technology, but much progress has been made. Early next year FHIR will add more mature resources to support FHIR subscriptions with FHIR R5. FHIR subscriptions are on our roadmap for next year after R5 is released. In the meantime, you can build a production and implement custom logic that can duplicate some of this functionality.

The FHIR subscription architecture will change in FHIR R5.  The SubscriptionTopic Resource exists in FHIR R 5.0.0 snapshot but did not exist in R4.  Therefore it has maturity level 0.  Advancement of maturity level is a prescribed processs which requires use in connectathons as well as in production (once to level 3).  FHIR Subscription Resource is maturity level 2.  Maturity level does not relate so much to whether a Resource is implementable as it does to whether the Resource is likely to change.