This page is part of the FUT Infrastructure (v3.2.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://ehealth.sundhed.dk/vs/priority | Version: 3.2.0 | |||
Active as of 2023-02-27 | Computable Name: Priority |
Practitioner roles
References
Generated Narrative: ValueSet ehealth-priority
http://ehealth.sundhed.dk/cs/priority
Generated Narrative: ValueSet
Expansion based on codesystem Priority v3.2.0 (CodeSystem)
This value set contains 4 concepts
Code | System | Display | Definition |
routine | http://ehealth.sundhed.dk/cs/priority | Routine | The request has normal priority. |
urgent | http://ehealth.sundhed.dk/cs/priority | Urgent | The request should be actioned promptly - higher priority than routine. |
asap | http://ehealth.sundhed.dk/cs/priority | ASAP | The request should be actioned as soon as possible - higher priority than urgent. |
stat | http://ehealth.sundhed.dk/cs/priority | STAT | The request should be actioned immediately - highest possible priority. E.g. an emergency. |
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 |