FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

4.3.2.50 CodeSystem http://terminology.hl7.org/CodeSystem/usage-context-type

Clinical Decision Support icon Work Group Maturity Level: 5Trial Use Use Context: Not yet ready for Production use, Not yet ready for Production use

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/usage-context-type
Version:5.0.0-cibuild
Name:UsageContextType
Title:UsageContextType
Status:draft
Definition:

A code that specifies a type of context being specified by a usage context.

Committee:Clinical Decision Support icon Work Group
OID:2.16.840.1.113883.4.642.1.1068 (for OID based terminology systems)
Flags:Experimental, CaseSensitive, Complete
All codes ValueSet:UsageContextType

This Code system is used in the following value sets:

  • ValueSet: UsageContextType icon (A code that specifies a type of context being specified by a usage context.)
  • ValueSet: UsageContextType (A code that specifies a type of context being specified by a usage context.)

This code system http://terminology.hl7.org/CodeSystem/usage-context-type defines the following codes:

CodeDisplayDefinitionCopy
gender GenderThe gender of the patient. For this context type, appropriate values can be found in the http://hl7.org/fhir/ValueSet/administrative-gender value set.btn btn
age Age RangeThe age of the patient. 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.btn btn
focus Clinical FocusThe clinical concept(s) addressed by the artifact. For example, disease, diagnostic test interpretation, medication ordering as in http://hl7.org/fhir/ValueSet/condition-code.btn btn
user User TypeThe 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.btn btn
workflow Workflow SettingThe settings in which the artifact is intended for use. For example, admission, pre-op, etc. For example, the ActEncounterCode value set http://terminology.hl7.org/ValueSet/v3-ActEncounterCode.btn btn
task Workflow TaskThe context for the clinical task(s) represented by this artifact. 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.btn btn
venue Clinical VenueThe venue in which an artifact 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).btn btn
species SpeciesThe species to which an artifact applies. For example, SNOMED - 387961004 | Kingdom Animalia (organism).btn btn
program ProgramA program/project of work for which this artifact is applicable.btn btn
agreement-scope Agreement AcopeDescribes the level and scope of agreement within the artifact. Appropriate values can be found in the usage-context-agreement-scope value set.btn btn

 

See the full registry of code systems defined as part of FHIR.


Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code