R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). 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

4.3.1.500 Value Set http://hl7.org/fhir/ValueSet/subscription-channel-type

FHIR Infrastructure Work Group Maturity Level: 3Trial 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
Name:SubscriptionChannelType
Definition:

The type of method used to execute a subscription.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.500 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


This value set includes codes from the following code systems:

 

This expansion generated 03 Apr 2018


This value set contains 5 concepts

Expansion based on http://hl7.org/fhir/subscription-channel-type version 3.3.0

All codes from system http://hl7.org/fhir/subscription-channel-type

CodeDisplayDefinition
rest-hookRest HookThe 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.
websocketWebsocketThe 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.
emailEmailThe channel is executed by sending an email to the email addressed in the URI (which must be a mailto:).
smsSMSThe channel is executed by sending an SMS message to the phone number identified in the URL (tel:).
messageMessageThe 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:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code