Subscriptions R5 Backport - Local Development build (v0.1.0). 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
status: ACTIVE
type: EVENTNOTIFICATION
eventsSinceSubscriptionStart: 2
eventsInNotification: 1
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.