Subscriptions R5 Backport
1.2.0-ballot - ballot

Subscriptions R5 Backport, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-subscription-backport-ig/ and changes regularly. See the Directory of published versions

## Example Bundle: R4B 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 r4b-notification-error of type history

Entry 1 - fullUrl = urn:uuid:190faedc-eb83-4073-b189-55e6a49a11dd

Request:

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

Response:

    200

Resource SubscriptionStatus:

> Generated Narrative: SubscriptionStatus

> ResourceSubscriptionStatus "190faedc-eb83-4073-b189-55e6a49a11dd"

> status: ERROR

> type: QUERYSTATUS

> eventsSinceSubscriptionStart: 3

> subscription: https://example.org/fhir/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.