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 notification-full-resource of type history

Entry 1 - Full URL = urn:uuid:b21e4fae-ce73-45cb-8e37-1e203362b2ae

Request:

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

Response:

200

Resource SubscriptionStatus:

Generated Narrative

status: ACTIVE

type: EVENTNOTIFICATION

eventsSinceSubscriptionStart: 2

eventsInNotification: 1

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

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

Entry 2 - Full URL = https://example.org/fhir/r4/Encounter/551683b3-1477-41d1-b58e-32fe8b0047b0

Request:

POST Encounter

Response:

201

Resource Encounter:

Not done yet

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.