Subscription Profile

Canonical	../StructureDefinition/nexus-emr-core-subscription
Status	draft (experimental) · 1.26.0
Base	Subscription (constraint)
Source	FSH · JSON

Nexus EMR profile for Subscription (R4 criteria-based) -- server-side push notification registration managed by the subscription manager service. Infrastructure and a data-egress security surface: no effective date, and R4 gives it no identifier element. First pass; note the R5 redesign migration path.

Examples

FHIR Gateway Observation Change

The gateway's change-notification subscription for Observation. channel.payload is deliberately absent, so this is an id-only notification and authorization stays enforced at the read

Subscription/sub-observation-change-webhook — claims conformance to Subscription Profile

{
  "resourceType": "Subscription",
  "id": "sub-observation-change-webhook",
  "meta": {
    "profile": [
      "../StructureDefinition/nexus-emr-core-subscription"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<div xmlns='http://www.w3.org/1999/xhtml'><p>The FHIR Gateway's change-notification subscription for Observation, delivered to the gateway's own per-resource-type webhook.</p><p>Note channel.payload is deliberately ABSENT: this is an id-only notification, so the receiver must fetch the resource and authorization stays enforced at the read. A payload here would push record content to the endpoint directly.</p></div>"
  },
  "status": "active",
  "reason": "FHIR Gateway change tracking: notify the gateway when an Observation is created or updated on the backing FHIR server, so downstream caches and the patient chart can be invalidated.",
  "criteria": "Observation?_lastUpdated=gt2025-01-01",
  "end": "2026-01-01T00:00:00Z",
  "channel": {
    "type": "rest-hook",
    "endpoint": "https://gateway.apps.health/webhook/Observation",
    "header": [
      "X-Nexus-Subscription-Source: fhir-gateway"
    ]
  }
}