DK MedCom Terminology
1.8.0 - release
DK MedCom Terminology
1.8.0 - release
DK MedCom Terminology, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 1.8.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-medcom-terminology/ and changes regularly. See the Directory of published versions
| Official URL: http://medcomfhir.dk/ig/terminology/ValueSet/medcom-careCommunication-requestPriority | Version: 1.8.0 | |||
| Active as of 2022-09-01 | Computable Name: MedComCareCommunicationRequestPriority | |||
ValueSet containg priority codes for care communication messages
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet medcom-careCommunication-requestPriority
http://hl7.org/fhir/request-priority| Code | Display | Definition |
| routine | Routine | The request has normal priority. |
| asap | ASAP | The request should be actioned as soon as possible - higher priority than urgent. |
Generated Narrative: ValueSet
Expansion based on codesystem RequestPriority v4.0.1 (CodeSystem)
This value set contains 2 concepts
| Code | System | Display | Definition |
| routine | http://hl7.org/fhir/request-priority | Routine | The request has normal priority. |
| asap | http://hl7.org/fhir/request-priority | ASAP | The request should be actioned as soon as possible - higher priority than urgent. |
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 |