eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 3.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions
Official URL: http://ehealth.sundhed.dk/vs/ehealth-usage-context-type | Version: 3.3.0 | |||
Active as of 2020-11-20 | Computable Name: eHealthUsageContextType |
eHealth Usage Context types.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet ehealth-usage-context-type
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/usage-context-type
http://ehealth.sundhed.dk/cs/ehealth-usage-context-type
Generated Narrative: ValueSet
Expansion based on:
This value set contains 14 concepts
Code | System | Display | Definition |
gender | http://terminology.hl7.org/CodeSystem/usage-context-type | Gender | The gender of the patient for which this artifact/element applies. For this context type, appropriate values can be found in the http://hl7.org/fhir/ValueSet/administrative-gender value set. |
age | http://terminology.hl7.org/CodeSystem/usage-context-type | Age Range | The age of the patients for which this artifact/element applies. For this context type, the value could be a range that specifies the applicable ages or a code from an appropriate value set such as the MeSH value set http://terminology.hl7.org/ValueSet/v3-AgeGroupObservationValue. |
focus | http://terminology.hl7.org/CodeSystem/usage-context-type | Clinical Focus | The clinical concept(s) addressed by the artifact/element. For example, disease, diagnostic test interpretation, medication ordering as in http://hl7.org/fhir/ValueSet/condition-code. |
user | http://terminology.hl7.org/CodeSystem/usage-context-type | User Type | The clinical specialty of the context in which the patient is being treated - For example, PCP, Patient, Cardiologist, Behavioral Professional, Oral Health Professional, Prescriber, etc... taken from a specialty value set such as the NUCC Health Care provider taxonomy value set http://hl7.org/fhir/ValueSet/provider-taxonomy that is relevant to this artifact/element. |
workflow | http://terminology.hl7.org/CodeSystem/usage-context-type | Workflow Setting | The settings in which the artifact/element is intended for use. For example, admission, pre-op, etc. For example, the ActEncounterCode value set http://terminology.hl7.org/ValueSet/v3-ActEncounterCode. |
task | http://terminology.hl7.org/CodeSystem/usage-context-type | Workflow Task | The context for the clinical task(s) represented by this artifact/element. For example, this could be any task context represented by the HL7 ActTaskCode value set http://terminology.hl7.org/ValueSet/v3-ActTaskCode. General categories include: order entry, patient documentation and patient information review. |
venue | http://terminology.hl7.org/CodeSystem/usage-context-type | Clinical Venue | The venue in which an artifact/element could be used. For example, Outpatient, Inpatient, Home, Nursing home. The code value may originate from the HL7 ServiceDeliveryLocationRoleType value set (http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType). |
species | http://terminology.hl7.org/CodeSystem/usage-context-type | Species | The species to which an artifact/element applies. For example, SNOMED - 387961004 | Kingdom Animalia (organism). |
program | http://terminology.hl7.org/CodeSystem/usage-context-type | Program | A program/project of work for which this artifact/element is applicable. |
jurisdiction | http://terminology.hl7.org/CodeSystem/usage-context-type | Jurisdiction | A country, state, territory or other geographic or geopolicital area for which this artifact/element is applicable. |
activity | http://ehealth.sundhed.dk/cs/ehealth-usage-context-type | activity type | The type of activity in which it is relevant to use a module/element having this use context (see http://hl7.org/fhir/metadatatypes.html#UsageContext). For this context type, the value should be a code taken from the http://ehealth.sundhed.dk/vs/activitydefinition-code value set |
supports | http://ehealth.sundhed.dk/cs/ehealth-usage-context-type | supports | The type of activity supported by a module/element having this use context (see http://hl7.org/fhir/metadatatypes.html#UsageContext). For this context type, the value should be a code taken from the http://ehealth.sundhed.dk/vs/activitydefinition-code value set |
range | http://ehealth.sundhed.dk/cs/ehealth-usage-context-type | range | The type of reference range with which it is relevant to use a module/element having this use context (see http://hl7.org/fhir/metadatatypes.html#UsageContext). For this context type, the value should be a code taken from the http://ehealth.sundhed.dk/vs/reference-range-type value set |
questionnaire-related | http://ehealth.sundhed.dk/cs/ehealth-usage-context-type | questionnaire related | The type of questionnaire element with which it is relevant to use a coded values/id registries having this use context (see http://hl7.org/fhir/metadatatypes.html#UsageContext). For this context type, the value should be a code taken from the http://ehealth.sundhed.dk/vs/questionnaire-elements value set |
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 |