| ARCHETYPE ID | openEHR-EHR-COMPOSITION.encounter.v1 |
|---|---|
| Concept | Encounter |
| Description | Interaction, contact or care event between a subject of care and healthcare provider(s). |
| Use | Use as a generic document-level container for recording details of a single interaction, contact or care event between a subject of care and healthcare provider(s). The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. Even though unconstrained for clinical content, specification of COMPOSITION.Encounter provides significant value by allowing for explicit querying of all Encounters within a patient record. The Context component contains an optional 'Extension' SLOT that can be used in template design to:
Typical examples are a clinic visit, a nursing observation or a telemedicine consultation. |
| Misuse | Not to be used to record details about an entire episode of care. Not to be used to carry persistent, summarised patient information, such as a problem list or medication summary. Not to be used to represent the report of a diagnostic service, such as imaging or laboratory testing. Not to be used to represent the FHIR resource of the same name - there is a mismatch scope and intent. |
| Purpose | To record the document level details of a single interaction, contact or care event between a subject of care and healthcare provider(s) for the provision of healthcare service(s). This can be either a face-to-face or remote interaction. |
| References | TC 251, European Committee for Standardization: EN 13940-1:2007 Health informatics - System of concepts to support continuity of care - Part 1: Basic concepts. |
| Copyright | © openEHR Foundation |
| Authors | Author name: Thomas Beale Organisation: Ocean Informatics, UK Email: thomas.beale@oceaninformatics.com Date originally authored: 2005-10-10 |
| Other Details Language | Author name: Thomas Beale Organisation: Ocean Informatics, UK Email: thomas.beale@oceaninformatics.com Date originally authored: 2005-10-10 |
| Other Details (Language Independent) |
|
| Keywords | encounter, contact, visit, care event |
| Lifecycle | published |
| UID | 52fa2b9c-ed55-4821-a300-1150fb382c05 |
| Language used | en |
| Citeable Identifier | 1013.1.120 |
| Revision Number | 1.0.12 |
| context | |
| Extension | Extension: Additional information required to extend the model with local content or to align with other reference models or formalisms. For example: local information requirements; or additional metadata to align with FHIR. Include: All not explicitly excluded archetypes |
| data | |
| Category | |
| null |
|
| Other contributors | Tomas Alme, DIPS, Norway Nadim Anani, Karolinska Institutet, Sweden Koray Atalag, University of Auckland, New Zealand Silje Bakke, Bergen Hospital Trust, Norway Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor) Steve Bentley, Allscripts, United Kingdom Rong Chen, Cambio Healthcare Systems, Sweden Stephen Chu, Queensland Health, Australia Shahla Foozonkhah, Ocean Informatics, Australia Konstantinos Kalliamvakos, Cambio Healthcare Systems, Sweden Lars Karlsen, DIPS ASA, Norway Lars Morgan Karlsen, DIPS ASA, Norway Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Luis Marco Ruiz, Norwegian Center for Integrated Care and Telemedicine, Norway Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor) Pablo Pazos, CaboLabs.com Health Informatics, Uruguay |
| Translators |
|