Subscriptions R5 Backport
1.2.0-ballot - ballot International flag

This page is part of the Subscriptions R5 Backport (v1.2.0-ballot: STU 1.2 Ballot 1) based on FHIR (HL7® FHIR® Standard) v4.3.0. The current version which supersedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions

Example Bundle: R4 Notification: Full Resource

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

Bundle r4-notification-full-resource of type history

Entry 1 - fullUrl = urn:uuid:2d5afc69-6ef2-420f-a8d1-8500c99eb96c

Request:

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

Response:

200

Resource Parameters:

Parameters

subscriptionhttps://example.org/fhir/Subscription/admission
topichttp://hl7.org/SubscriptionTopic/admission
statusactive
typeevent-notification
events-since-subscription-start2
notification-event
 event-number2
 timestamp2020-05-29 11:44:13-0500
 focushttps://example.org/fhir/Encounter/86009987-eabe-42bf-8c02-b112b18cb616

Entry 2 - fullUrl = https://example.org/fhir/Encounter/86009987-eabe-42bf-8c02-b112b18cb616

Request:

POST Encounter

Response:

201

Resource Encounter:

Not done yet

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.