Subscriptions R5 Backport
1.0.0 - Standard for Trial Use International flag

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

Example Bundle: Backported Notification: Error

This Bundle provides an example of an error notification. This Bundle is typical of what may be posted to a notification endpoint (e.g., a listening HTTP server, etc.) in the event of a processing error on the server.

Bundle notification-error of type history

Entry 1 - Full URL = urn:uuid:2efd9e8b-e894-4460-97f1-1d0c09daeb10

Request:

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

Response:

200

Resource SubscriptionStatus:

Generated Narrative

Resource "2efd9e8b-e894-4460-97f1-1d0c09daeb10"

status: ERROR

type: QUERYSTATUS

eventsSinceSubscriptionStart: 10

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

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

error: No response (Subscription Error Codes#no-response)

Notes:

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 error notification and does not include additional entries, no additional constraints are imposed by Bundle requirements.