eHealth Infrastructure
2.5.0 - release

eHealth Infrastructure - Local Development build (v2.5.0). See the Directory of published versions

ValueSet: Resolved Timing Type (Experimental)

Official URL: http://ehealth.sundhed.dk/vs/resolved-timing-type Version: 2.5.0
Active as of 2021-02-26 Computable Name: ResolvedTimingType

Value set for resolved timing type.

References

Logical Definition (CLD)

 

Expansion

This value set contains 3 concepts

Expansion based on Resolved Timing Type v2.5.0 (CodeSystem)

CodeSystemDisplayDefinition
  Resolvedhttp://ehealth.sundhed.dk/cs/resolved-timing-typeResolved

Resolved

  Unresolvedhttp://ehealth.sundhed.dk/cs/resolved-timing-typeUnresolved

Unresolved

  Adhochttp://ehealth.sundhed.dk/cs/resolved-timing-typeAdhoc

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