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. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities.

Identifier(s) by which this encounter is known.

The current state of the encounter (not the state of the patient within the encounter - that is subjectState).

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

The status history permits the encounter resource to contain the status history without needing A granular, workflows specific set of statuses that apply to read through the historical versions encounter.

The Note that Encounters have complex lifecycles, and may have multiple concurrent business statuses that are differentiated based on type. This property should only be used for current status is always found business statuses. Historical businessStatuses should be captured in EncounterHistory to avoid the current version of the resource, not the status history. Encounter resource becoming so large as to be difficult to process.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +. The current business status.

Concepts representing classification The kind of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. workflow the status is tracking.

For example, if an Encounter started as an emergency visit, but was upgraded to an inpatient admission, the Encounter may have two businessStatus codes, one with a type of "emergency", and one with a type of "inpatient".

The class history permits the tracking of the encounters transitions without needing to go through date/time when the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions 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 kind of discharge from emergency to inpatient. entered this business 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 time that Indicates the episode was in urgency of the specified class. encounter.

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.

Different use-cases are likely to have different permitted transitions between states, such as an Emergency department could use arrived when the patient first presents, then triaged once has been assessed by a nurse, then receiving-care once treatment begins, however other sectors may use a different set of these values, or their own custom set in place of this example valueset provided.

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 request this encounter satisfies (e.g. incoming referral or procedure request).

The group(s) of individuals, organizations that are allocated to participate in this encounter. The participants backbone will record the actuals of when these individuals participated during the encounter.

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.

The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the colonoscopy example on the Encounter examples tab.

The list of people responsible for providing the service.

Any Patient or Group present in the participation.actor must also be the subject, though the subject may be absent from the participation.actor for cases where the patient (or group) is not present, such as during a case review conference.

Role of participant in encounter.

The participant type indicates how an individual actor participates 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 Person involved in the encounter other than encounter, the patient. patient/group is also included here to indicate that the patient was actually participating in the encounter. Not including the patient here covers use cases such as a case meeting between practitioners about a patient - non contact times.

For planning purposes, Appointments may include a CareTeam participant to indicate that one specific person from the CareTeam will be assigned, but that assignment might not happen until the Encounter begins. Hence CareTeam is not included in Encounter.participant, as the specific individual should be assigned and represented as a Practitioner or other person resource.

Similarly, Location can be included in Appointment.participant to assist with planning. However, the patient location is tracked on the Encounter in the Encounter.location property to allow for additional metadata and history to be recorded.

The role of the participant can be used to declare what the actor will be doing in the scope of this encounter participation.

If the individual is not specified during planning, then it is expected that the individual will be filled in at a later stage prior to the encounter commencing.

The appointment that scheduled this encounter.

Connection details of a virtual service (e.g. conference call).

There are two types of virtual meetings that often exist:

• a persistent, virtual meeting room that can only be used for a single purpose at a time,
• and a dynamic virtual meeting room that is generated on demand for a specific purpose.

Implementers may consider using Location.virtualService for persistent meeting rooms.

If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail can be applied to the Encounter.participant BackboneElement.

The actual start and end time of the encounter.

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

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

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

Quantity 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 the in Encounter.period lasted because of due to leave of absence. absence(s).

The list of medical reasons that are expected to be addressed during the episode of care.

Reason The reason communicates what medical problem the patient has that should be addressed during the episode of care. This reason could be patient reported complaint, a clinical indication that was determined in a previous encounter takes place, expressed or episode of care, or some planned care such as an immunization recommendation. In the case where you have a code. For admissions, this primary reason, but are expecting to also address other problems, you can be used list the primary reason with a use code of 'Chief Complaint', while the other problems being addressed would have a use code of 'Reason for Visit'.

Examples:

• pregnancy would use HealthcareService or a coded admission diagnosis. coding as the reason
• patient home monitoring could use Condition as the reason

What the reason value should be used as e.g. Chief Complaint, Health Concern, Health Maintenance (including screening).

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

The list of diagnosis relevant to this encounter.

Also note that for the purpose of billing, the diagnoses are recorded in the account where they can be ranked appropriately for how the invoicing/claiming documentation needs to be prepared.

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

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

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.

Also note that the Encounter.account properties are meant to represent long-running or perpetual accounts. For short-lived, episodic accounts, see Account.covers.

Details about Diet preferences reported by the admission to a healthcare service. patient.

Pre-admission identifier. 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).

The location/organization from which Any special requests that have been made for this encounter, such as the patient came before admission. provision of specific equipment or other things.

From where Special courtesies that may be provided to the patient was admitted (physician referral, transfer). during the encounter (VIP, board member, professional courtesy).

Although the specialCourtesy property can contain values like VIP, the purpose of this field is intended to be used for flagging additional benefits that might occur for the patient during the encounter.

It could include things like the patient is to have a private room, special room features, receive a friendly visit from hospital adminisitration, or should be briefed on treatment by senior staff during the stay.

It is not specifically intended to be used for securing the specific record - that is the purpose of the security meta tag, and where appropriate, both fields could be used.

Whether this hospitalization is Details about the stay during which a readmission and why if known. healthcare service is provided.

This does not describe the event of admitting the patient, but rather any information that is relevant from the time of admittance until the time of discharge.

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 admission record.

Diet preferences reported by the patient. Pre-admission identifier.

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

Special courtesies (VIP, board member). From where patient was admitted (physician referral, transfer).

Any special requests Indicates that have been made for this hospitalization encounter, such as encounter is directly related to a prior admission, often because the provision of specific equipment or other things. conditions addressed in the prior admission were not fully addressed.

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" such as "client's home" and an encounter.class = "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 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.

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.

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