An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

Identifier(s) by which this encounter is known.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

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

The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.

The current status is always found in the current version of the resource, not the status history.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

The time that the episode was in the specified status.

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

The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient.

inpatient | outpatient | ambulatory | emergency +.

The time that the episode was in the specified class.

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

Indicates the urgency of the encounter.

The patient ro or group present at the encounter.

While the encounter is always about the patient, the patient may 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).

Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).

The referral request this encounter satisfies (incoming referral). (e.g. incoming referral or procedure request).

The list of people responsible The list of people responsible for providing the service.

Role of participant in encounter.

The participant type indicates how an individual partitipates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.

The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.

Persons involved in the encounter other than the patient.

The appointment that scheduled this encounter.

The start and end time of the encounter.

If not (yet) known, the end of the Period may be omitted.

Quantity of time the encounter lasted. This excludes the time during leaves of absence.

May differ from the time the Encounter.period lasted because of leave of absence.

Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

The list of diagnosis relevant to this encounter.

Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).

Ranking of the diagnosis (for each role type).

The set of accounts that may be used for billing for this Encounter.

The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.

Details about the admission to a healthcare service.

An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.

The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.

Pre-admission identifier.

The location location/organization from which the patient came before admission.

From where patient was admitted (physician referral, transfer).

Whether this hospitalization is a readmission and why if known.

Diet preferences reported by the patient.

Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter.

For example a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).

Special courtesies (VIP, board member).

Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.

Location Location/organization to which the patient is discharged.

Category or kind of location after discharge.

List of locations where the patient has been during this encounter.

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

The location where the encounter takes place.

The status of the participants' presence at the specified location during the period specified. If the participant is is no longer at the location, then the period will have an end date/time.

When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.

Time period during which the patient was present at the location.

An The organization that is in charge of maintaining the information of primarily responsible for this Encounter (e.g. who maintains the report or the master service catalog item, etc.). Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different. This MAY not different, such as if the actor performing the services was from an external organization (which may be not billed seperately) for an external consultation. Refer to the Service Delivery Location's Organization. example bundle showing an abbreviated set of Encounters for a colonoscopy.

Another Encounter of which this encounter is a part of (administratively or in time).

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.