HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.1 (Standard for Trial Use)

HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.1 (Standard for Trial Use) - Local Development build (v1.1.0). See the Directory of published versions

Local value sets used in this Implementation Guide

Name Definition
AnatomicalDirectionVS

Terms that specify anatomical direction.

AnatomicalOrientationVS

Terms that specify anatomical orientation. The orientation value set is part of BodyLocation, a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

  • Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
  • Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
  • Relation to landmark: The location relative to a landmark is specified by:
    1. Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
    2. Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

CarePlanChangeReasonVS

Reasons that a care plan was changed. Similar to TreatmentTerminationReasonVS

LandmarkTypeVS

The type of feature that constitutes the landmark, for example, particularly if the landmark is an acquired body structure or physical object. The landmark type value set is part of BodyLocation, a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

  • Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
  • Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
  • Relation to landmark: The location relative to a landmark is specified by:
    1. Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
    2. Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

ResearchSubjectTerminationReasonVS

The reason for a research subject leaving a research study.

SettingVS

What type of place is found at a given location. More than one descriptor may be applicable.

StudyArmTypeVS

The role of each arm in the clinical trial.

FHIR is currently unable to handle values from NCI Thesaurus, so no values are listed in the Expansion, below. The values ARE in the downloads. For convenience, here is a listing of values in this value set: NCIT#C94487 ‘Intervention Group’ NCIT#C68609 ‘Active Comparator’ NCIT#C49648 ‘Placebo Control’ NCIT#C116527 ‘Sham Intervention’

TreatmentIntentVS

The purpose of a treatment. The value set includes ‘curative’ and ‘palliative’. Curative is defined as any treatment meant to reduce or control a disease process, even if a ‘cure’ is not anticipated. Palliative includes treatments meant to reduce symptoms and side effects, such as antiemetics.

TreatmentTerminationReasonVS

Values used to describe the reasons for stopping a treatment. Includes code for ‘treatment completed’ as well as codes for unplanned (early) stoppage. Applies to medications and other treatments that take place over a period of time, such as radiation treatments.

UnitsOfLengthVS

Units of measure related to length or distance.

YesNoVS

Value set indicating yes or no (values drawn from Snomed CT), equivalent to LL361-7.

External value sets used in this Implementation Guide

Name Definition
CommonLanguages

This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)

CommonUCUMCodesForDuration

Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes

CompositionAttestationMode

The way in which a person authenticated a composition.

CompositionStatus

The workflow/clinical status of the composition.

Currencies

Currency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html)

DataAbsentReason

Used to specify why the normally expected content of the data element is missing.

DaysOfWeek

The days of the week.

DiagnosisRole

This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.

DocumentClassValueSet

This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests.

DocumentRelationshipType

The type of relationship between documents.

DocumentSectionCodes

Document section codes (LOINC codes used in CCDA sections).

EventTiming

Real world event relating to the schedule.

FHIRDocumentTypeCodes

FHIR Document Codes - all LOINC codes where scale type = ‘DOC’.

Identifier Type Codes

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

IdentifierUse

Identifies the purpose for this identifier, if known .

LOINCCodes

This value set includes all LOINC codes

Laterality

Laterality: SNOMED-CT concepts for ‘left’, ‘right’, and ‘bilateral’

ListEmptyReasons

General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).

ListMode

The processing mode that applies to this list.

ListOrderCodes

Base values for the order of the items in a list resource.

ObservationCategoryCodes

Observation Category codes.

ObservationInterpretationCodes

A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed.

Notes:

This is being communicated in v2.x in OBX-8 (Observation Interpretation), in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR in Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version.

ObservationMethods

Observation Method codes from SNOMED CT where concept is-a 272394005 (Technique (qualifier value)) or is-a 129264002 (Action (qualifier value)) or is-a 386053000 (Evaluation procedure(procedure))

ObservationReferenceRangeAppliesToCodes

This value set defines a set of codes that can be used to indicate the particular target population the reference range applies to.

ObservationReferenceRangeMeaningCodes

This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population.

ObservationStatus

Codes providing the status of an observation.

ProcedurePerformerRoleCodes

This example value set defines the set of codes that can be used to indicate a role of a procedure performer.

QuantityComparator

How the Quantity should be understood and represented.

QuantityComparator

How the Quantity should be understood and represented.

SNOMEDCTBodyStructures

This value set includes all codes from SNOMED CT where concept is-a 442083009 (Anatomical or acquired body site (body structure)).

TimingAbbreviation

Code for a known / defined timing pattern.

UnitsOfTime

A unit of time (units from UCUM).

http://terminology.hl7.org/CodeSystem/v3-WorkClassificationODH
http://terminology.hl7.org/ValueSet/v3-ActCode
http://terminology.hl7.org/ValueSet/v3-ConfidentialityClassification
http://terminology.hl7.org/ValueSet/v3-WorkScheduleODH
http://terminology.hl7.org/ValueSet/v3-employmentStatusODH
https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7186
https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7187
https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7613