eHealth Infrastructure - Local Development build (v2022.1). See the Directory of published versions
Summary
Defining URL: | http://ehealth.sundhed.dk/vs/resolved-timing-type |
Version: | 2022.1 |
Name: | ResolvedTimingType |
Title: | Resolved Timing Type |
Status: | Experimental as of 2/26/21, 12:00 AM |
Definition: | Value set for resolved timing type. |
Publisher: | Systematic | Trifork |
Source Resource: | XML / JSON / Turtle |
References
http://ehealth.sundhed.dk/cs/resolved-timing-type
This value set contains 3 concepts
Expansion based on Resolved Timing Type v2022.1 (CodeSystem)
All codes in this table are from the system http://ehealth.sundhed.dk/cs/resolved-timing-type
Code | Display | Definition |
Resolved | Resolved | Resolved |
Unresolved | Unresolved | Unresolved |
Adhoc | Adhoc | Adhoc |
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 |