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.
Elements / Differential
What this profile constrains beyond Subscription. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.
| Element | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Subscription | Nexus EMR Subscription Core (R4 criteria-based) Invariants: subscription-deliverable |
|||
| meta | 0..1 | Meta | ||
| source | S | 0..1 | uri | Identifies EMR instance & pipeline version the resource came from i |
| text | S | 0..1 | Narrative | Narrative i |
| status | S | 1..1 | code | i |
| end | S | 0..1 | instant | When the subscription expires i |
| reason | S | 1..1 | string | Why this subscription exists i |
| criteria | S | 1..1 | string | The search expression selecting resources to notify on i |
| channel | S | 1..1 | BackboneElement | How notifications are delivered |
| type | S | 1..1 | code | |
| endpoint | S | 0..1 | url | Where notifications are sent i |
| payload | S | 0..1 | code | MIME type of the notification body; absent means id-only notification i |
| header | S | 0..* | string | Headers sent with the notification (e.g. authorization) i |