v2+ Vocabulary
0.3.0 - Working Draft to present the concept ideas (FO)
v2+ Vocabulary
0.3.0 - Working Draft to present the concept ideas (FO)
v2+ Vocabulary - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://terminology.hl7.org/v2plusvocab/ValueSet/hl7VSmessageWaitingPriorityV100 | Version: 1.0.0 | |||
| Active as of 2025-08-05 | Computable Name: Hl7VSmessageWaitingPriorityV100 | |||
| Other Identifiers: OID:2.16.840.1.113883.21.356 | ||||
Copyright/Legal: HL7 Inc., 2024 |
||||
Value Set of codes that specify how important the most important waiting mesasge is. For example, if there are 3 low priority messages, 1 medium priority message and 1 high priority message, the message waiting priority would be "high", because
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/v2plusvocab/CodeSystem/messageWaitingPriorityV100
Expansion performed internally based on codesystem Message Waiting Priority (2.6 - 1.0.0) v1.0.0 (CodeSystem)
This value set contains 3 concepts
| Code | System | Display (en-US) | Definition |
| H | http://terminology.hl7.org/v2plusvocab/CodeSystem/messageWaitingPriorityV100 | High | High |
| L | http://terminology.hl7.org/v2plusvocab/CodeSystem/messageWaitingPriorityV100 | Low | Low |
| M | http://terminology.hl7.org/v2plusvocab/CodeSystem/messageWaitingPriorityV100 | Medium | Medium |
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 |
| System | 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 |