ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

SubscriptionStatus

The current status of a FHIR Subscription: events emitted, last sequence numbers, status. The notification payload type=handshake / heartbeat / event-notification.

Purpose

SubscriptionStatus is the notification body sent by the FHIR server to subscribers via WebSocket, REST hook, email or message. It indicates the current subscription status (initial handshake, liveness heartbeat, event notification, query-event) and carries the resources tied to the triggering event. It is the modern (R4B/R5) counterpart of the historical FHIR R4 Subscription.

Key elements

FieldTypeCardinalityRole
statuscode0..1`requested`, `active`, `error`, `off`, `entered-in-error`.
typecode1..1`handshake`, `heartbeat`, `event-notification`, `query-status`, `query-event`.
eventsSinceSubscriptionStartinteger640..1Total events since start.
notificationEventBackboneElement[]0..*List of conveyed events.
subscriptionReference(Subscription)1..1Linked Subscription.
topiccanonical(SubscriptionTopic)0..1Subscribed topic.
errorCodeableConcept[]0..*Detected errors.

JSON example

json subscriptionstatus-example.json
{
  "resourceType": "SubscriptionStatus",
  "id": "example-event-notif",
  "status": "active",
  "type": "event-notification",
  "eventsSinceSubscriptionStart": 247,
  "notificationEvent": [{
    "eventNumber": 247,
    "timestamp": "2026-05-15T17:30:00+00:00",
    "focus": {
      "reference": "Encounter/encounter-001"
    }
  }],
  "subscription": {
    "reference": "Subscription/example-sub-001"
  },
  "topic": "https://example.org/fhir/SubscriptionTopic/admission-discharge"
}

Common pitfalls

  • Type=event-notification without notificationEvent: empty payload.
  • EventsSinceSubscriptionStart non-monotonic: server has lost events.
  • Status='error' without error: impossible to diagnose.