This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
FHIR Infrastructure Work Group | Maturity Level: 3 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/subscription-channel-type
|
Version: 6.0.0-ballot2 | |||
active as of 2024-10-02 | Computable Name: SubscriptionChannelType | |||
Flags: | OID: 2.16.840.1.113883.4.642.3.500 |
This value set is used in the following places:
Core-defined FHIR channel types allowed for use in Subscriptions.
Generated Narrative: ValueSet subscription-channel-type
Last updated: 2024-10-02T17:31:51.554Z
Profile: Shareable ValueSet
http://terminology.hl7.org/CodeSystem/subscription-channel-type
This expansion generated 02 Oct 2024
Generated Narrative: ValueSet
Last updated: 2024-10-02T17:31:51.554Z
Profile: Shareable ValueSet
Expansion based on codesystem SubscriptionChannel Type Codes v1.0.1 (CodeSystem)
This value set contains 4 concepts
Code | System | Display | Definition |
rest-hook | http://terminology.hl7.org/CodeSystem/subscription-channel-type | Rest Hook | The channel is executed by making a POST to the URI with the selected payload and MIME type. |
websocket | http://terminology.hl7.org/CodeSystem/subscription-channel-type | 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. |
http://terminology.hl7.org/CodeSystem/subscription-channel-type | The channel is executed by sending an email to the email addressed in the URI (which must be a mailto:). | ||
message | http://terminology.hl7.org/CodeSystem/subscription-channel-type | 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 |