This page is part of the FHIR Specification (v4.5.0: R5 Preview #3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
FHIR Infrastructure Work Group | Maturity Level: 0 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/subscription-channel-type |
Version: | 4.5.0 |
Name: | SubscriptionChannelType |
Title: | Subscription Channel Type |
Definition: | Core-defined FHIR channel types allowed for use in Subscriptions. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.3.500 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://terminology.hl7.org/CodeSystem/subscription-channel-type
This expansion generated 20 Aug 2020
This value set contains 5 concepts
Expansion based on SubscriptionChannel Type Codes v4.2.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/subscription-channel-type
Code | Display | Definition |
rest-hook | Rest Hook | The channel is executed by making a post to the URI. If a payload is included, the URL is interpreted as the service base, and an update (PUT) is made. |
websocket | Websocket | The channel is executed by sending a packet across a web socket connection maintained by the client. The URL identifies the websocket, and the client binds to this URL. |
The channel is executed by sending an email to the email addressed in the URI (which must be a mailto:). | ||
sms | SMS | The channel is executed by sending an SMS message to the phone number identified in the URL (tel:). |
message | Message | The channel is executed by sending a message (e.g. a Bundle with a MessageHeader resource etc.) to the application identified in the URI. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |