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

Extensions defined as part of this Implementation Guide

Name Definition
AnatomicalOrientation

AnatomicalOrientation of the body location, if needed to distinguish from a similar location in another orientation. The orientation element 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).

Annotation

An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.

BasedOn

The proposal, order, or plan that is partly or wholly fulfilled by this item.

CareContext

The encounter or episode of care

Category

The general type or class of this item.

Code

The main type identifier for a lab, procedure, condition, etc., usually drawn from a controlled vocabulary.

Comparator

A code indicated if the value represents an upper or lower bound

Condition

A condition that is or may be present in a subject. ‘Condition’ is interpreted broadly and could be a disorder, abnormality, problem, injury, complaint, functionality, illness, disease, ailment, sickness, affliction, upset, difficulty, disorder, symptom, worry, or trouble. The Observation-based class, ConditionAbsent, should be used to describe conditions that are not present or negative findings. This profiled Condition uses the BodyLocation structure that includes not only a code, but optional laterality, direction, and relation to landmark(s).

DiagnosisCode

Codes for a diagnosis.

Dosage

The dosage of the medication. The data structure is flexible and can describe a dosage prescribed, administered, or reported.

Employer

A person or organization that hires the services of another.

EncounterDiagnosis

A diagnosis, which is a disease or injury determined to be present through evaluation of patient history, examination, and/or review of laboratory data. This element is not a stand-alone representation of the condition that was diagnosed, but is meant to be used as an sub-structure in a resource, such as Encounter.

ExpectedPerformanceTime

When an action should be done. If the action is a series or recurs (e.g. daily blood sugar testing in the morning) then a Timing can be used to describe the periodicity.

ExpectedPerformer

Who this request is being addressed to.

ExpectedPerformerType

What type of party should carry out the testing.

Identifier

Business identifier or external id for this resource.

LandmarkLocation

The body location of the landmark, specified by a location code and optional laterality and orientation.

LandmarkToBodyLocationDirection

The direction from the landmark to the body location of interest, given as a clockface direction or anatomical direction.

LandmarkToBodyLocationDistance

How far the body location of interest is from the given landmark.

LandmarkType

The type of feature that constitutes the landmark, particularly if the landmark is an acquired body structure or physical object.

Laterality

Body side of the body location, if needed to distinguish from a similar location on the other side of the body.

The laterality element 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).

MedicationCodeOrReference

A choice of a medication code or reference.

Method

The technique used to carry out an action, for example, the specific imaging technical or assessment vehicle.

Number

A decimal value.

OccurrenceTimeOrPeriod

The point or period of time when the event takes place. Times can be precise (dateTime) or approximate (date). If a time period is used, and the start date or dateTime is missing, the start of the period is not known. If the end date or dateTime is missing, it means that the period is ongoing.

OnBehalfOf

The party represented by the actual participant.

Organization

A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.

Organization type is restricted to 0..1 in FHIR DSTU2, similarly restricted here. Other required attributes come from STU 3 mapping to us-core-organization.

PartOf

The larger entity that the asserted item is a portion of. For example, an organization part of a larger organization, or an encounter with a hospitalist might be part of a larger hospitalization encounter.

Participant

An entity (usually a Practitioner, Patient, or Organization but potentially a device or other entity) that participates in a healthcare task or activity. The participant is not necessarily the performer, and the role (ParticipationType), the ParticipationPeriod, and other details of the participation are by the Participation structure.

Participation

Record of someone or something involvement in an activity or event.

ParticipationPeriod

The point in time or span of time the participant is involved.

ParticipationType

The role played by the participant engaged in the action, for example, as the attending physician, surgical assistant, etc.

PriorityCode

An indication of the importance of an action relative to other actions.

PriorityRank

The priority of the procedure, as a number (1 being the highest priority)

ReasonCode

The explanation or justification for the current item or action, as a code. Reason is a string or CodeableConcept in DSTU2 but in later versions only a CodeableConcept.

ReasonReference

The justification, as reference to a condition or observation.

RelationToLandmark

The relationship between a landmark that helps determine a body location and the body location itself. The location relative to a landmark is specified by:

  • Specifying the location and type of landmark using a body site code and optional laterality/orientation,
  • Specifying the direction from the landmark to the body location, and
  • Specifying the distance from the landmark to the body location.

The RelationToLandmark element 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).

RequestIntent

Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.

Requester

The person or organization originating this referral

StatementDateTime

The point in time when the statement was created.

Status

A state that relates to the workflow or interpretation of this resource. Certain status values can modify the meaning of the resource, for example, entered-in-error. When a boolean value is used, Status of true indicates the record is active, false means inactive.

StatusHistory

List of past encounter statuses

SubjectOfRecord

The subject of a clinical statement, often called the Patient or the Subject. The SubjectOfRecord typically identifies the clinical record in which this statement is contained. If the statement should be in John Doe’s patient record, then John Doe is the subject of record. When there is no patient, the SubjectOfRecord can also be a location, group, or other entity that statement pertains to. For example, observations concerning a hospital ward would have a Location as the SubjectOfRecord.

Note that the word ‘Subject’ is used here in the sense of a person or entity subjected to observations or actions, not subject as in a conceptual topic, like heart disease.

TimePeriod

A period of time defined by a start and end time, date, or year. If the start date/time is missing, the start of the period is not known. If the end date/time is missing, it means that the period is ongoing.

Type

A code describing the item at a greater level of detail.

Units

The unit of measure of the quantity.