| ARCHETYPE ID | openEHR-EHR-CLUSTER.person.v1 |
|---|---|
| Concept | Person |
| Description | An individual human being. |
| Use | Use to record details of a person as they are known or understood in the course of clinical documentation, often ad hoc or when it is not appropriate or possible to use a formal demographic register or index. Examples include:
In most simple clinical recording use cases, the unstructured 'Name' element within the CLUSTER.person archetype will be sufficient to record the name of a person as part of a health record. However, in circumstances where a structured name is necessary or desirable for clinical recording purposes, nest this archetype within the 'Structured name' SLOT in CLUSTER.person archetype. If the CLUSTER.structured_name archetype is nested within the 'Structured name' SLOT, any or all of the data elements can be combined together as a text string and represented in the 'Name' element, as long as they are consistent. This archetype could also be used as a proxy for formal demographic data when reviewing a template with domain experts - for example, an assessment where reviewers would expect to see a person's details at the top of the assessment form. |
| Misuse | Not to be used to represent or replace formal identification management or for the purposes of maintaining an official demographic register or index. Use a formal Master Patient Index or Health Provider Index for this purpose, or archetypes based on the openEHR Demographic Information Model. Not to be used to represent the subject of care, participants or author of the record and similar data elements that should be represented formally in the health record using the Reference Model attributes. Not to be used to record the date of birth of an individual - use the 'Date of birth' data element within the EVALUATION.birth_summary for this purpose Not to be used to record biometric detail or biomarkers about an individual - use a specific ENTRY archetype for this purpose. |
| Purpose | To record details about a person as they are known or understood in the course of clinical documentation. |
| References | Health Care Client Identification - AS 5017-2006. New South Wales (AU): Standards Australia; 2006. Health Care Provider Identification - AS 4846-2006. New South Wales (AU): Standards Australia; 2006. Health informatics — Identification of subjects of health care - ISO/TS 22220:2007. Geneva: International Organization for Standardization; 2007. HL7 FHIR Resource - Person v4.0.1: R4 [Internet]. Health Level Seven International; [accessed 2021 05 04]. Available from: http://hl7.org/fhir/2021May/person.html. |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2021-04-14 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2021-04-14 |
| Other Details (Language Independent) |
|
| Keywords | provider, carer, staff, healthcare professional, relative, next-of-kin, practitioner, witness, friend, neighbour, child, family, sibling, parent, individual |
| Lifecycle | published |
| UID | 3f7fbe34-4e64-4c02-8d1a-402f7b0f57ce |
| Language used | en |
| Citeable Identifier | 1246.145.1615 |
| Revision Number | 1.0.3 |
| items | |
| Name | Name: The unstructured name for the individual. The content of this data element may be derived from one or more components from CLUSTER.structured_name combined together as a text string. For example: 'John Markham', 'Professor Sir John Markham', 'John Markham Jnr MP'. |
| Label | Label: A label for the individual. For example: 'Neighbour in the house with the red door'. |
| Structured name | Structured name: Alternative representation of an individual's complete name by separation into discrete, structured components. Any or all of the structured name elements can be combined together as a text string and represented in the 'Name' data element in this archetype. Include: openEHR-EHR-CLUSTER.structured_ |
| Identifier | Identifier: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. Choice of:
|
| Role | Role: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Address | Address: Details about an address for the individual. Include: openEHR-EHR-CLUSTER.address.v1 and specialisations |
| Electronic communication | Electronic communication: Details about one or more types of electronic communication for the individual. Include: openEHR-EHR-CLUSTER.electronic_ |
| Organisation | Organisation: Details about the organisational context for the individual. For example: identifying the business or community organisation associated with the 'Role' of the individual. Include: openEHR-EHR-CLUSTER.organisation.v1 and specialisations |
| Additional details | Additional details: Additional details about the individual. |
| Photo | Photo: Photograph of the individual. Include: openEHR-EHR-CLUSTER.media_ |
| Comment | Comment: Additional narrative about the individual not captured in other fields. |
| Other contributors | Dag Aarhus, Vestre Viken HF, Norway Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor) Astrid Askeland, Dips AS, Norway Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor) Keisha Barwise, MOHW/IDB HSSP Project, Jamaica itai Basel, Private, Israel SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India Yexuan Cheng, 浙江大学, China Candice de Lisser, Ministry of Health and Wellness, Jamaica Ludvig Eek Hofmann, Cambio Healthcare Systems AB, Sweden Valborg Ellingsen, Haraldsplass Diakonale sykehus, Norway Heather Grain, Llewelyn Grain Informatics, Australia Martin Grundberg, Cambio Healthcare Systems, Sweden Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway (openEHR Editor) Rebecka Hansson, Cambio Healthcare Systems AB, Sweden Anca Heyd, DIPS ASA, Norway Roar Holm, Helse Vest IKT A/S, Norway Joost Holslag, Nedap, Netherlands Evelyn Hovenga, EJSH Consulting, Australia Gunnar Jårvik, Helse Vest IKT AS, Norway Gunn-Lisbeth Kleiven, Oslo universitetssykehus HF, Norway Kanika Kuwelker, Helse Vest IKT, Norway Jörgen Kuylenstierna, eWeave AB, Sweden Liv Laugen, Oslo University Hospital, Norway, Norway (openEHR Editor) Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway Mikael Nyström, Cambio Healthcare Systems AB, Sweden Erik Skjemstad, Helse Nord RHF, Norway Natalia Strauch, Medizinische Hochschule Hannover, Germany Norwegian Review Summary, Norwegian Public Hospitals, Norway Nyree Taylor, Ocean Health Systems, Australia Tesfay Teame, Bærum kommune, Norway Anders Thurin, VGR, Sweden John Tore Valand, Helse Bergen, Norway (openEHR Editor) Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor) |
| Translators |
|