Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Maintenance Plan:

FHIR-I


Short Description:

...

This guide defines a standard method of back-porting the R5 subscriptions API to R4 implementations as to bridge for pre-adopting R5 Subscriptions prior to adoption of the R5 FHIR standard.


Long Description:

In R5, subscriptions are broken into a 1) topic, which defines the resource(s) for the subscription and the events on which they happen, and 2) a subscription, which is the registration of a communication channel optionally with some additional filtering.  This guide defines a standard method of back-porting the R5 subscriptions API to R4 implementations as to bridge to adoption of Subscriptions prior to adoption of the R5 FHIR standard.

Its defines the actors and transactions as well as basic error handling by clients and servers for subscriptions using REST Hooks and e-mail. 

...

Tentative ( Da Vinci, Public Health)  --TBD



Content sources:

FHIR R5

...

Subscription Resources


Example Scenarios:

1) Subscription to Encounter by patient
query context is already part of the focal resource (Encounter.patient)
can express criteria in FHIR (Encounter?patient=)
unlocks "New data notifications for patient apps" use case
building block for provider-facing access

...