Skip to content

Subscription Profile

Canonical../StructureDefinition/nexus-emr-core-subscription
Statusdraft (experimental) · 1.26.0
BaseSubscription (constraint)
SourceFSH · 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.

TypedFhir API / TypeScript

The typed accessor surface Subscription exposes for Subscription — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.

class Subscription extends ClinicalResourcegenerated source

Accessor Type Access Notes
$effectiveDate FuzzyDate | undefined read-only The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f…
$display string | undefined read-only The resource's human headline — a coded concept's label, else a title / name, else undefined.
status string | undefined read/write requested | active | error | off
end FuzzyDate | undefined read/write When the subscription expires
reason string | undefined read/write Why this subscription exists
criteria string | undefined read/write The search expression selecting resources to notify on
channel Json | undefined read/write How notifications are delivered