Subscriptions R5 Backport
1.2.0-ballot - ballot International flag

Subscriptions R5 Backport, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-subscription-backport-ig/ and changes regularly. See the Directory of published versions

Example Bundle: R4B Notification: Id Only

This Bundle provides an example of an id-only notification. This Bundle is typical of what may be posted to a notification endpoint (e.g., a listening HTTP server, etc.).

Bundle r4b-notification-id-only of type history

Entry 1 - fullUrl = urn:uuid:3dd3c88d-1f7c-40ce-bf41-6b0d8186c311

Request:

GET https://example.org/fhir/Subscription/admission/$status

Response:

200

Resource SubscriptionStatus:

Generated Narrative: SubscriptionStatus

ResourceSubscriptionStatus "3dd3c88d-1f7c-40ce-bf41-6b0d8186c311"

status: ACTIVE

type: EVENTNOTIFICATION

eventsSinceSubscriptionStart: 2

NotificationEvents

-EventNumberTimestampFocus
*2May 29, 2020, 4:44:13 PMhttps://example.org/fhir/Encounter/86009987-eabe-42bf-8c02-b112b18cb616

subscription: https://example.org/fhir/Subscription/admission

topic: http://hl7.org/SubscriptionTopic/admission

Notes:

In order to satisfy the requirements of a history Bundle (specifically bdl-3 and bdl-4), note that Bundle.entry.request must exist.

For the status resource (entry[0]), the request is filled out to match a request to the $status operation.

For additional entries, the request SHOULD be filled out in a way that makes sense given the subscription (e.g., a POST or PUT operation on the resource). However, a server MAY choose to simply include a GET to the relevant resource instead.