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

Entry 1 - fullUrl = urn:uuid:7bd91d26-c951-4520-9ac6-67f41bfbe897

Request:

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

Response:

200

Resource Parameters:

Parameters

subscription	https://example.org/fhir/Subscription/admission
topic	http://hl7.org/SubscriptionTopic/admission
status	active
type	event-notification
events-since-subscription-start	2
notification-event
event-number	2
timestamp	2020-05-29 11:44:13-0500
focus	https://example.org/fhir/Encounter/86009987-eabe-42bf-8c02-b112b18cb616
additional-context	https://example.org/fhir/Patient/1599eb66-431a-447c-a3de-6897fe9ae9a1

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

Request:

POST Encounter

Response:

201

Resource Encounter:

Not done yet

Entry 3 - fullUrl = https://example.org/fhir/Patient/1599eb66-431a-447c-a3de-6897fe9ae9a1

Request:

GET Patient/1599eb66-431a-447c-a3de-6897fe9ae9a1

Response:

200

Resource Patient:

Example Patient null, DoB:

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.