This page is part of the FUT Infrastructure (v3.3.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/resolved-timing-type | Version: 3.3.0 | |||
Active as of 2021-02-26 | Computable Name: ResolvedTimingType |
Value set for resolved timing type.
References
Generated Narrative: ValueSet resolved-timing-type
http://ehealth.sundhed.dk/cs/resolved-timing-type
Generated Narrative: ValueSet
Expansion based on codesystem Resolved Timing Type v3.3.0 (CodeSystem)
This value set contains 4 concepts
Code | System | Display | Definition |
Resolved | http://ehealth.sundhed.dk/cs/resolved-timing-type | Resolved | Resolved |
Unresolved | http://ehealth.sundhed.dk/cs/resolved-timing-type | Unresolved | Unresolved |
Adhoc | http://ehealth.sundhed.dk/cs/resolved-timing-type | Adhoc | Adhoc |
Extra | http://ehealth.sundhed.dk/cs/resolved-timing-type | Extra | Extra |
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 |