| ARCHETYPE ID | openEHR-EHR-CLUSTER.encounter_details.v0 |
|---|
| Concept | Encounter details |
|---|
| Description | Details about an encounter. |
|---|
| Use | Use to record details about an encounter between a patient and healthcare services.
Within the context of this archetype, encounter is interpreted broadly, and includes any contact between a patient and healthcare services that needs to be recorded. This includes, but is not limited to, visits to a general practitioner, outpatient treatment, inpatient treatment, admission to an emergency room, hospital at home or mental health appointments.
As a result, both the concept and the data elements have been given very generic names. It is expected that these names will not be appropriate in all jurisdictions or use cases, and will need to be renamed in templates to better fit the specific context.
The Sub-episode Slot is designed to accept recursive elements of this cluster in order to model sub-encounters as needed. For instance, one instance of this cluster could be used to record a hospitalization, and a sub-episode used to record admission to the emergency room, while a different episode could be used to record a transfer to a different department. These cluster can be further sub-divided as needed to record specific encounters as needed.
Source, Source category, Destination and Destination category are intended to provide alternatives to one another in regarding where the patient came from and where they departed to. Source category and Destination category are intended to give broad indications of the source and destination, while the Source and Destination slots are intended to identify specific organisations and/or locations. |
|---|
| Misuse | Not to be used for planning future encounter. At the time of authoring it is not yet determined which archetype should be used for this purpose. |
|---|
| Purpose | To record details about an encounter between a patient and healthcare services. |
|---|
| References | |
|---|
| Copyright | © openEHR Foundation |
|---|
| Authors | Author name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2022-06-13
|
|---|
| Other Details Language | Author name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2022-06-13
|
|---|
| Other Details (Language Independent) | - Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
- Custodian Organisation: openEHR Foundation
- References:
- Original Namespace: org.openehr
- Original Publisher: openEHR Foundation
- Custodian Namespace: org.openehr
- MD5-CAM-1.0.1: 922DC591626640BA904282CD5180A0C3
- Build Uid: dbc7bd56-6b0b-4b53-a924-16a1239ab339
- Revision: 0.0.1-alpha
|
|---|
| Keywords | admission, discharge, transfer, separation, visit, stay, hospitalization, inpatient, death, care episode |
|---|
| Lifecycle | in_development |
|---|
| UID | 8aae2b01-f970-4a25-a0a9-8da12f9bf2f2 |
|---|
| Language used | en |
|---|
| Citeable Identifier | 1013.1.6366 |
|---|
| Revision Number | 0.0.1-alpha |
|---|
| items | |
|---|
| Encounter ID | Encounter ID: An identifier for the encounter.
Choice of:
 Identifier
 Text
|
|---|
| Source | Source: The location/organization the patient was prior to the encounter.
Include:
openEHR-EHR-CLUSTER.organisation.v1 or
openEHR-EHR-CLUSTER.address.v1 |
|---|
| Source category | Source category: The type of location the patient was prior to the encounter.
Coding with a terminology is desirable, where possible. For example: home, nursing home, incident site |
|---|
| Reason | Reason: The reason for the encounter.
Coding with an external terminology is preferred, where possible. For example: diagnosis, elective surgery, or childbirth. |
|---|
| Location | Location: The physical location where the encounter took place.
Coding with an external terminology is preferred, where possible. For example: doctor's office, emergency room, clinic. |
|---|
| Structured location | Structured location: Structured details about where the encounter took place.
Include:
openEHR-EHR-CLUSTER.organisation.v1 or
openEHR-EHR-CLUSTER.address.v1 |
|---|
| Start | Start: The date/date-time when the encounter started.
For example: admitted to inpatient facility, transferred to different ward. |
|---|
| Sub-episode | Sub-episode: Details about a sub-episode that consitutes part of the original encounter.
This slot is intended to be used to add details about sub-episodes using nested instances of this archetype. Examples of sub-episodes can be transfers to different department or room/bed changes.
Include:
openEHR-EHR-CLUSTER.inpatient_episode_details.v0 |
|---|
| Destination | Destination: Location/organization to which the patient went to following the encounter.
Include:
openEHR-EHR-CLUSTER.organisation.v1 or
openEHR-EHR-CLUSTER.address.v1 |
|---|
| Destination category | Destination category: The type of location to which the patient went to following the encounter.
Coding with a terminology is desirable, where possible. For example: home, nursing home, other healthcare facility |
|---|
| End | End: The date/date-time when the encounter ended. |
|---|
| Additional details | Additional details: Further details about the encounter.
Include:
All not explicitly excluded archetypes |
|---|
| Comment | Comment: Additional narrative about the encounter not captured in other fields. |
|---|
| Other contributors | |
|---|
| Translators | Norwegian Bokmål: Martin Milde, Helse Vest IKT, martin.milde@helse-vest-ikt.no
|
|---|