This Bundle provides an example of an full-resource notification that includes a related resource (e.g., the triggering resource of Encounter and the related Patient). This Bundle is typical of what may be posted to a notification endpoint (e.g., a listening HTTP server, etc.).

Bundle notification-multi-resource of type history

Entry 1 - Full URL = urn:uuid:babce097-c165-4b54-b7d1-0301b8a095d3

Request:

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

Response:

200

Resource Parameters:

Parameters

subscription	https://example.org/fhir/r4/Subscription/admission
topic	http://hl7.org/SubscriptionTopic/admission
type	event-notification
status	active
events-since-subscription-start	310
events-in-notification	1

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

Entry 3 - Full URL = https://example.org/fhir/r4/Patient/46db3334-dbf5-43f3-868f-93ae0883cce1

Request:

GET Patient/46db3334-dbf5-43f3-868f-93ae0883cce1

Response:

200

Resource Patient:

Exception generating narrative: null

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.