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

The Encounter associated with this set of historic values.

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.

Identifier(s) by which this encounter is known.

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

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

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

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

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

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

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.

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).

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.

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.

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

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

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.

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).

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.

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".

The location where the encounter takes place.

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

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.