0.1.0 - ci-build
igeMedicationat - Local Development build (v0.1.0). See the Directory of published versions
Summary
Defining URL: | https://termpub.gesundheit.gv.at:443/TermBrowser/gui/main/main.zul?loadType=ValueSet&loadName=ELGA_Einnahmezeitpunkte |
Version: | 0.1.0 |
Name: | ELGATimingEventsDrugAdministration |
Title: | ELGA Timing Events Drug Administration |
Status: | Active as of 2019-11-01 09:29:23+1100 |
Definition: | ELGA ValueSet for timing of drug administration. |
Publisher: | HL7 Austria |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-TimingEvent
Code | Display | Definition |
ACD | ACD | before lunch (from lat. ante cibus diurnus) |
ACM | ACM | before breakfast (from lat. ante cibus matutinus) |
ACV | ACV | before dinner (from lat. ante cibus vespertinus) |
HS | HS | **Description:** Prior to beginning a regular period of extended sleep (this would exclude naps). Note that this might occur at different times of day depending on a person's regular sleep schedule. |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
UNK | Unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |
This value set contains 5 concepts
Expansion based on:
Code | System | Display | Definition |
ACD | http://terminology.hl7.org/CodeSystem/v3-TimingEvent | ACD | before lunch (from lat. ante cibus diurnus) |
ACM | http://terminology.hl7.org/CodeSystem/v3-TimingEvent | ACM | before breakfast (from lat. ante cibus matutinus) |
ACV | http://terminology.hl7.org/CodeSystem/v3-TimingEvent | ACV | before dinner (from lat. ante cibus vespertinus) |
HS | http://terminology.hl7.org/CodeSystem/v3-TimingEvent | HS | Description: Prior to beginning a regular period of extended sleep (this would exclude naps). Note that this might occur at different times of day depending on a person's regular sleep schedule. |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Unknown | **Description:**A proper value is applicable, but not known. Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:
|
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 |
Source | 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 |