This page is part of the Subscriptions R5 Backport (v0.1.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://hl7.org/fhir/uv/subscriptions-backport/ValueSet/backport-notification-type-value-set |
Version: | 0.1.0 |
Name: | BackportNotificationTypeValueSet |
Title: | R5 Subscription Notification Type Value Set |
Status: | Active as of 2020-12-16T17:37:01+00:00 |
Definition: | Codes to represent types of notification bundles. |
Publisher: | HL7 FHIR Infrastructure WG |
Source Resource: | XML / JSON / Turtle |
References
http://hl7.org/fhir/uv/subscriptions-backport/CodeSystem/backport-notification-type-code-system
This value set contains 4 concepts
Expansion based on R5 Subscription Notification Type Code System v0.1.0 (CodeSystem)
All codes from system http://hl7.org/fhir/uv/subscriptions-backport/CodeSystem/backport-notification-type-code-system
Code | Display | Definition |
handshake | Handshake | The notification is being sent as part of the setup or verification of a communications channel. |
heartbeat | Heartbeat | The notification is being sent because there has not been a notification generated over an extended period of time. |
event-notification | Event Notification | The notification is being sent due to an event for the subscriber. |
query-status | Query Status | The notification is being sent due to a client request or query for Subscription status. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |