Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions

Patient Administration icon Work GroupMaturity Level: 0 Trial UseSecurity Category: Patient Compartments: Encounter, Patient

Detailed Descriptions for the elements in the EncounterHistory resource.

EncounterHistory
Element IdEncounterHistory
Definition

A record of significant events/milestones key data throughout the history of an Encounter, often tracked for specific purposes such as billing.

Short DisplayA record of significant events/milestones key data throughout the history of an Encounter
Cardinality0..*
TypeDomainResource
Summaryfalse
EncounterHistory.encounter
Element IdEncounterHistory.encounter
Definition

The Encounter associated with this set of historic values.

Short DisplayThe Encounter associated with this set of historic values
Cardinality0..1
TypeReference(Encounter)
HierarchyThis reference is part of a strict Hierarchy
Summaryfalse
Comments

This is also used for associating a child's encounter back to the mother's encounter.

Refer to the Notes section in the Patient resource for further details.

EncounterHistory.identifier
Element IdEncounterHistory.identifier
Definition

Identifier(s) by which this encounter is known.

Short DisplayIdentifier(s) by which this encounter is known
NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Summarytrue
EncounterHistory.status
Element IdEncounterHistory.status
Definition

planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown.

Short Displayplanned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown
Cardinality1..1
Terminology BindingEncounter Status (Required)
Typecode
Is Modifiertrue (Reason: This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)
Summarytrue
Comments

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

EncounterHistory.class
Element IdEncounterHistory.class
Definition

Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.

Short DisplayClassification of patient encounter
Cardinality1..1
Terminology BindingActEncounterCode icon (Extensible)
TypeCodeableConcept
Summarytrue
EncounterHistory.type
Element IdEncounterHistory.type
Definition

Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).

Short DisplaySpecific type of encounter
Cardinality0..*
Terminology BindingEncounter Type (Example)
TypeCodeableConcept
Summarytrue
Comments

Since there are many ways to further classify encounters, this element is 0..*.

EncounterHistory.serviceType
Element IdEncounterHistory.serviceType
Definition

Broad categorization of the service that is to be provided (e.g. cardiology).

Short DisplaySpecific type of service
Cardinality0..*
Terminology BindingService Type (Example)
TypeCodeableReference(HealthcareService)
Summarytrue
EncounterHistory.subject
Element IdEncounterHistory.subject
Definition

The patient or group related to this encounter. In some use-cases the patient MAY not be present, such as a case meeting about a patient between several practitioners or a careteam.

Short DisplayThe patient or group related to this encounter
Cardinality0..1
TypeReference(Patient | Group)
Alternate Namespatient
Summarytrue
Comments

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

EncounterHistory.subjectStatus
Element IdEncounterHistory.subjectStatus
Definition

The subjectStatus value can be used to track the patient's status within the encounter. It details whether the patient has arrived or departed, has been triaged or is currently in a waiting status.

Short DisplayThe current status of the subject in relation to the Encounter
Cardinality0..1
Terminology BindingEncounter Subject Status (Example)
TypeCodeableConcept
Summaryfalse
EncounterHistory.actualPeriod
Element IdEncounterHistory.actualPeriod
Definition

The start and end time associated with this set of values associated with the encounter, may be different to the planned times for various reasons.

Short DisplayThe actual start and end time associated with this set of values associated with the encounter
Cardinality0..1
TypePeriod
Summaryfalse
EncounterHistory.plannedStartDate
Element IdEncounterHistory.plannedStartDate
Definition

The planned start date/time (or admission date) of the encounter.

Short DisplayThe planned start date/time (or admission date) of the encounter
Cardinality0..1
TypedateTime
Summaryfalse
EncounterHistory.plannedEndDate
Element IdEncounterHistory.plannedEndDate
Definition

The planned end date/time (or discharge date) of the encounter.

Short DisplayThe planned end date/time (or discharge date) of the encounter
Cardinality0..1
TypedateTime
Summaryfalse
EncounterHistory.length
Element IdEncounterHistory.length
Definition

Actual quantity of time the encounter lasted. This excludes the time during leaves of absence.

When missing it is the time in between the start and end values.

Short DisplayActual quantity of time the encounter lasted (less time absent)
Cardinality0..1
TypeDuration
Summaryfalse
Comments

If the precision on these values is low (e.g. to the day only) then this may be considered was an all day (or multi-day) encounter, unless the duration is included, where that amount of time occurred sometime during the interval.

May differ from the time in Encounter.period due to leave of absence(s).

EncounterHistory.location
Element IdEncounterHistory.location
Definition

The location of the patient at this point in the encounter, the multiple cardinality permits de-normalizing the levels of the location hierarchy, such as site/ward/room/bed.

Short DisplayLocation of the patient at this point in the encounter
Cardinality0..*
Summaryfalse
Comments

Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".

EncounterHistory.location.location
Element IdEncounterHistory.location.location
Definition

The location where the encounter takes place.

Short DisplayLocation the encounter takes place
Cardinality1..1
TypeReference(Location)
Summaryfalse
EncounterHistory.location.form
Element IdEncounterHistory.location.form
Definition

This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.

Short DisplayThe physical type of the location (usually the level in the location hierarchy - bed, room, ward, virtual etc.)
Cardinality0..1
Terminology BindingLocation Form (Example)
TypeCodeableConcept
Summaryfalse
Comments

This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query.

There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.