This page is part of the Subscriptions R5 Backport (v1.0.0: STU 1) based on FHIR v4.3.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
This Bundle provides an example of an empty
notification. This Bundle
is typical of what may be posted to a notification endpoint (e.g., a listening HTTP server, etc.).
Bundle notification-empty 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
Resource "b21e4fae-ce73-45cb-8e37-1e203362b2ae"
status: ACTIVE
type: EVENTNOTIFICATION
eventsSinceSubscriptionStart: 2
NotificationEvents
- EventNumber Timestamp * 2 May 29, 2020 4:44:13 PM subscription: https://example.org/fhir/r4/Subscription/admission
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.
Since this is an empty
notification and does not include additional entries, no additional constraints are imposed by Bundle
requirements.