<?xml version="1.0" encoding="UTF-8"?>
<archetype xmlns="http://schemas.openehr.org/v1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <original_language>
    <terminology_id>
      <value>ISO_639-1</value>
    </terminology_id>
    <code_string>en</code_string>
  </original_language>
  <is_controlled>false</is_controlled>
  <description>
    <original_author id="date">2021-04-14</original_author>
    <original_author id="name">Heather Leslie</original_author>
    <original_author id="organisation">Atomica Informatics</original_author>
    <original_author id="email">heather.leslie@atomicainformatics.com</original_author>
    <other_contributors>Dag Aarhus, Vestre Viken HF, Norway</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Astrid Askeland, Dips AS, Norway</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Keisha Barwise, MOHW/IDB HSSP Project, Jamaica</other_contributors>
    <other_contributors>itai Basel, Private, Israel</other_contributors>
    <other_contributors>SB Bhattacharyya, Bhattacharyyas Clinical Records Research &amp; Informatics LLP, India</other_contributors>
    <other_contributors>Yexuan Cheng, 浙江大学, China</other_contributors>
    <other_contributors>Candice de Lisser, Ministry of Health and Wellness, Jamaica</other_contributors>
    <other_contributors>Ludvig Eek Hofmann, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Valborg Ellingsen, Haraldsplass Diakonale sykehus, Norway</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Martin Grundberg, Cambio Healthcare Systems, Sweden</other_contributors>
    <other_contributors>Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Rebecka Hansson, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Anca Heyd, DIPS ASA, Norway</other_contributors>
    <other_contributors>Roar Holm, Helse Vest IKT A/S, Norway</other_contributors>
    <other_contributors>Joost Holslag, Nedap, Netherlands</other_contributors>
    <other_contributors>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Gunnar Jårvik, Helse Vest IKT AS, Norway</other_contributors>
    <other_contributors>Gunn-Lisbeth Kleiven, Oslo universitetssykehus HF, Norway</other_contributors>
    <other_contributors>Kanika Kuwelker, Helse Vest IKT, Norway</other_contributors>
    <other_contributors>Jörgen Kuylenstierna, eWeave AB, Sweden</other_contributors>
    <other_contributors>Liv Laugen, ​Oslo University Hospital, Norway, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway</other_contributors>
    <other_contributors>Mikael Nyström, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Erik Skjemstad, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>Natalia Strauch, Medizinische Hochschule Hannover, Germany</other_contributors>
    <other_contributors>Norwegian Review Summary, Norwegian Public Hospitals, Norway</other_contributors>
    <other_contributors>Nyree Taylor, Ocean Health Systems, Australia</other_contributors>
    <other_contributors>Tesfay Teame, Bærum kommune, Norway</other_contributors>
    <other_contributors>Anders Thurin, VGR, Sweden</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <lifecycle_state>published</lifecycle_state>
    <other_details id="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/.</other_details>
    <other_details id="custodian_organisation">openEHR Foundation</other_details>
    <other_details id="references">Health Care Client Identification - AS 5017-2006. New South Wales (AU): Standards Australia; 2006.&#xD;
&#xD;
Health Care Provider Identification - AS 4846-2006. New South Wales (AU): Standards Australia; 2006.&#xD;
&#xD;
Health informatics — Identification of subjects of health care - ISO/TS 22220:2007. Geneva: International Organization for Standardization; 2007.&#xD;
&#xD;
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.</other_details>
    <other_details id="original_namespace">org.openehr</other_details>
    <other_details id="original_publisher">openEHR Foundation</other_details>
    <other_details id="custodian_namespace">org.openehr</other_details>
    <other_details id="MD5-CAM-1.0.1">CD21C16BEF470E3B1A24F31D027D3F0B</other_details>
    <other_details id="build_uid">8c7cbe6a-27d2-4889-aecc-186c4fc52428</other_details>
    <other_details id="revision">1.0.5</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Darstellung von Informationen zu einer Person, wie sie bekannt sind oder im Rahmen der klinischen Dokumentation verstanden werden.</purpose>
      <keywords>Anbieter, Dienstleister, Betreuer, Personal, medizinisches Fachpersonal, Verwandter, Angehöriger, Hausarzt, Zeuge, Freund, Nachbar, Kind, Familie, Geschwister, Elternteil, Einzelperson</keywords>
      <use>Der Archetyp wird verwendet, um Informationen zur einer Person darzustellen, wie sie bekannt sind oder im Rahmen der klinischen Dokumentation verstanden werden, oft ad hoc oder wenn die Verwendung von einem formellen demografischen Register oder einem Index nicht angemessen oder nicht möglich ist.&#xD;
Beispiele beinhalten:&#xD;
- der Inhaber einer Patientenverfügung unter Verwendung des SLOT „Inhaber der Kopie“ innerhalb des Archetyps EVALUATION.advance_care_directive;&#xD;
- die Rolle und Kontaktdaten eines benannten Ansprechpartners in einer Organisation, unter Verwendung des SLOT „Kontaktperson“ innerhalb des Archetyps CLUSTER.organisation;&#xD;
- Angaben zu einem Verwandten in einer Familienanamnese unter Verwendung des SLOT „Angaben zum Familienmitglied“ innerhalb des Archetyps openEHR-EHR-EVALUATION.family_history;&#xD;
- der Name der Person, die eine Laborprobe von einem Patienten entnommen hat, unter Verwendung der „Angaben zum Probennehmer“ innerhalb des Archetyps CLUSTER.specimen oder&#xD;
- ein Zeuge eines Sturzes oder Unfalls, unter Verwendung des SLOT "Zeuge" innerhalb des Archetyps CLUSTER.health_event.&#xD;
&#xD;
In den meisten einfachen Anwendungsfällen reicht das unstrukturierte Element „Name“ innerhalb des Archetyps CLUSTER.person aus, um den Namen einer Person als Teil einer Gesundheitsakte darzustellen. In Fällen, in denen ein strukturierter Name für klinische Aufzeichnungszwecke erforderlich oder wünschenswert ist, verschachteln Sie diesen Archetyp jedoch im SLOT „Name strukturiert“ im Archetyp CLUSTER.person. Wenn der Archetyp CLUSTER.structured_name in den SLOT „Name strukturiert“ eingebettet ist, können beliebige oder alle Datenelemente als Textzeichenfolge kombiniert und im Element „Name“ dargestellt werden, solange sie konsistent sind.&#xD;
&#xD;
Dieser Archetyp könnte auch stellvertretend für formale demografische Daten verwendet werden, wenn ein Template mit Domänenexperten überprüft wird – beispielsweise eine Bewertung, bei der Prüfer erwarten würden, dass die Details einer Person oben im Bewertungsformular angezeigt werden.</use>
      <misuse>Der Archetyp darf nicht verwendet werden, um das formelle Identifikationsmanagement darzustellen oder zu ersetzen oder um ein offizielles demografisches Register oder einen Index zu führen. Verwenden Sie zu diesem Zweck einen formellen Master Patient Index oder Health Provider Index oder Archetypen, die auf dem demografischen Informationsmodell von openEHR basieren.&#xD;
&#xD;
Darf nicht verwendet werden, um den Patienten, die Teilnehmer oder den Verfasser der Akte und ähnliche Datenelemente darzustellen, die formal in der Patientenakte unter Verwendung der Referenzmodellattribute dargestellt werden sollten.&#xD;
&#xD;
Darf nicht verwendet werden, um das Geburtsdatum einer Person darzustellen – verwenden Sie zu diesem Zweck das Datenelement „Geburtsdatum“ im Archetyp EVALUATION.birth_summary.&#xD;
&#xD;
Darf nicht verwendet werden, um biometrische Details oder Biomarker über eine Person darzustellen – verwenden Sie zu diesem Zweck einen speziellen ENTRY-Archetyp.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-pt</code_string>
      </language>
      <purpose>Para registar detalhes sobre uma pessoa tal como são conhecidos ou compreendidos aquando da documentação clínica.</purpose>
      <keywords>prestador de cuidados, cuidador, funcionário, profissional de saúde, familiar, familiar mais próximo, testemunha, amigo, vizinho, criança, família, irmão, pai, indivíduo</keywords>
      <use>Utilizado para registar detalhes de uma pessoa conforme são conhecidos ou compreendidos aquando da documentação clínica, frequentemente ad hoc ou quando não é apropriado ou possível usar um registo demográfico ou índice formal. Exemplos incluem:&#xD;
- o detentor da cópia de um registo de cuidados avançados, utilizando o SLOT 'Copyholder' dentro do arquétipo EVALUATION.advance_care_directive;&#xD;
- o papel e detalhes de contacto de uma pessoa designada dentro de uma organização, utilizando o SLOT 'Contact person' dentro do arquétipo CLUSTER.organisation;&#xD;
- detalhes sobre um familiar num registo de histórico familiar, utilizando o SLOT 'Family member details' dentro do arquétipo openEHR-EHR-EVALUATION.family_history;&#xD;
- o nome da pessoa que recolheu uma amostra laboratorial de um paciente, utilizando os 'Specimen collector details' dentro do arquétipo CLUSTER.specimen; ou&#xD;
- uma testemunha de uma queda ou acidente, utilizando o SLOT 'Witness' dentro do arquétipo CLUSTER.health_event.&#xD;
&#xD;
Na maioria dos casos simples de registo clínico, o elemento não estruturado 'Name' dentro do arquétipo CLUSTER.person será suficiente para registar o nome de uma pessoa como parte de um registo de saúde. No entanto, em circunstâncias em que um nome estruturado é necessário ou desejável para fins de registo clínico, incorpore este arquétipo dentro do SLOT 'Structured name' no arquétipo CLUSTER.person. Se o arquétipo CLUSTER.structured_name estiver incorporado dentro do SLOT 'Structured name', todos ou alguns dos elementos de dados podem ser combinados como uma string de texto e representados no elemento 'Name', desde que sejam consistentes.&#xD;
&#xD;
Este arquétipo também poderia ser utilizado como um proxy para dados demográficos formais ao rever um template com especialistas do domínio - por exemplo, uma avaliação onde os revisores esperariam ver os detalhes de uma pessoa no topo do formulário de avaliação.</use>
      <misuse>Não deve ser utilizado para representar ou substituir a gestão formal de identificação ou para efeitos de manutenção de um registo ou índice demográfico oficial. Utilize um Master Patient Index formal ou Health Provider Index para este fim, ou arquétipos baseados no Demographic Information Model do openEHR.&#xD;
&#xD;
Não deve ser utilizado para representar o sujeito do cuidado, participantes ou autor do registo e elementos de dados semelhantes que devem ser representados formalmente no registo de saúde utilizando os atributos do Reference Model.&#xD;
&#xD;
Não deve ser utilizado para registar a data de nascimento de um indivíduo - utilize o elemento de dados 'Date of birth' dentro do EVALUATION.birth_summary para este fim.&#xD;
&#xD;
Não deve ser utilizado para registar detalhes biométricos ou biomarcadores sobre um indivíduo - utilize um arquétipo ENTRY específico para este fim.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Används för att registrera information om en person som behöver representeras i patientjournalen.</purpose>
      <keywords>Leverantör, vårdare, vårdgivare, personal, vårdpersonal, släkting, anhöriga, läkare, vittne, vän, granne, barn, familj, syskon, förälder, individ</keywords>
      <use>Används för att registrera uppgifter om en person i den elektroniska journalen, när det inte är lämpligt eller möjligt att använda ett formellt demografiskt register eller index. Exempelvis:&#xD;
- Namn och kontaktuppgifter för en person som innehar en fysisk kopia av ett dokument om framtida behandlingsval eller behandlingsreservationer; exempelvis 'Copyholder'-attributet i arketypen EVALUATION.advance_care_directive;&#xD;
- Namn och kontaktuppgifter för en vårdgivare i en remiss;&#xD;
- Namn, roll och kontaktuppgifter för en medlem av ett vårdgivarteam;&#xD;
- Rollen och kontaktuppgifterna för en namngiven kontaktperson inom en organisation;&#xD;
- uppgifter om en släkting i en släkthistoria; eller&#xD;
- ett vittne till ett epileptisk anfall.&#xD;
&#xD;
I de flesta vanliga användningsfallen där ett namn måste inkluderas i en journal räcker det med fritextinmatning inom elementet 'Ostrukturerat namn'. I situationer när det krävs mer detaljerade detaljer om en eller flera namnkomponenter, använd de ytterligare strukturerade dataelementen i arketypen CLUSTER.structured_name. I denna arketyp finns en SLOT kapslade i "Structured name" . Om arketypen CLUSTER.structured name är kapslad i 'Structured name' SLOT, kan något eller alla av de strukturerade namnelementen sammanfogas och representeras i elementet 'Ostrukturerat namn'.&#xD;
&#xD;
Denna arketyp kan också användas som en proxy för formella demografiska data när man granskar en mall med domänexperter – till exempel en bedömning där granskare förväntar sig att se patientens uppgifter högst upp i bedömningsformuläret.</use>
      <misuse>Får inte användas för att representera eller ersätta formell identifieringshantering eller i syfte att upprätthålla ett officiellt demografiskt register eller index. Använd ett formellt Master Patient Index eller Vårdgivare Index för detta ändamål, eller arketyper baserade på openEHR Demographic Information Model.&#xD;
&#xD;
Får inte användas för att representera patienten, deltagare eller författare till journalen och liknande dataelement som bör representeras formellt i journalen med hjälp av Referensmodellens attribut.&#xD;
&#xD;
Får inte användas för att registrera en individs födelsedatum - använd istället dataelementet "Födelsedatum" i EVALUATION.birth_summary för detta ändamål&#xD;
&#xD;
Får inte användas för att registrera biometriska detaljer eller biomarkörer om en individ - använd en specifik ENTRY-arketyp för detta ändamål.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere detaljer om en person i en pasientjournal.</purpose>
      <keywords>tjenesteyter, omsorgsperson, helsepersonell, slektning, pårørende, vitne, venn, nabo, barn, familie, søsken, forelder, arbeidsgiver, rekvirent, henviser, ektefelle, verge, samboer, kjæreste</keywords>
      <use>Brukes for å registrere detaljer om en person i en pasientjournal, når det ikke er ønskelig eller mulig å bruke et formelt demografisk register eller indeks.&#xD;
&#xD;
For eksempel:&#xD;
- navn og kontaktdetaljer til en person som har en kopi av et fremtidig behandlingsvalg, i SLOTet "Kopiholder" i arketypen EVALUATION.advance_care_directive (Fremtidig behandlingsvalg).&#xD;
- navn og kontaktdetaljer til en omsorgsperson eller helsepersonell i en organisasjon, i SLOTet "Kontaktperson" i arketypen CLUSTER.organisation (Organisasjon).&#xD;
- detaljer om en slektning i en familieanamnese, I SLOTet "Detaljer om familiemedlem" i arketypen EVALUATION.family_history (Familieanamnese).&#xD;
- navnet på en person som gjennomførte prøvetakning på en pasient, i SLOTet "Detaljer om prøvetaker" i arketypen CLUSTER.specimen (Prøvemateriale).&#xD;
- et vitne til et fall eller en ulykke, i SLOTet "Witness" i arketypen CLUSTER.health_event.&#xD;
&#xD;
I de mest vanlige brukscasene der navn skal registreres i pasientjournalen, vil dataelementet "Navn" i denne arketypen være tilstrekkelig. I tilfeller der det er nødvendig eller ønskelig med detaljer om en eller flere navnekomponenter, bruk arketypen CLUSTER.structured_name i SLOTet "Strukturert navn" i denne arketypen. &#xD;
Om det er gjort, kan noen eller alle de strukturerte navnelementene slås sammen av programvaren man benytter, og lagres i dataelementet "Navn".&#xD;
&#xD;
Denne arketypen kan også brukes som en midlertidig erstatning for formelle demografiske data når man gjennomgår et templat med domeneeksperter - for eksempel en vurdering der man i templatet forventer å se detaljer om en person på toppen av vurderingsskjema.</use>
      <misuse>Brukes ikke til å representere eller erstatte de formelle demografiske opplysninger for formell identitetsforvaltning eller for å opprettholde et demografisk register eller en indeks. Bruk et formelt pasientregister, helsepersonellregister eller arketyper basert på openEHR demografisk informasjonsmodell til dette formålet.&#xD;
&#xD;
Brukes ikke for å representere pasient, deltakere eller forfatter av skjema eller lignende, som skal representeres formelt i pasientjournalen. Bruk attributter fra Referansemodellen for dette formålet.&#xD;
&#xD;
Brukes ikke for å registrere fødselsdato for individet - bruk dataelementet "Fødselsdato" i arketypen EVALUATION.birth_summary for dette formålet.&#xD;
&#xD;
Brukes ikke for å registrere detaljer om biometri eller biomarkører for personen - bruk en spesifikk ENTRY-arketype for dette formålet.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>el</code_string>
      </language>
      <purpose>*To record details about a person as they are known or understood in the course of clinical documentation.(en)</purpose>
      <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:&#xD;
- the copyholder of an advanced care record, using the 'Copyholder' SLOT within the EVALUATION.advance_care_directive archetype;&#xD;
- the role and contact details of a named contact person within an organisation, using the 'Contact person' SLOT within the CLUSTER.organisation archetype;&#xD;
- details about a relative in a family history record, using the 'Family member details' SLOT within the openEHR-EHR-EVALUATION.family_history archetype; &#xD;
- the name of the person who collected a laboratory specimen from a patient, using the 'Specimen collector details' within the CLUSTER.specimen archetype; or&#xD;
- a witness to a fall or accident, using the 'Witness' SLOT within the CLUSTER.health_event archetype.&#xD;
&#xD;
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.&#xD;
&#xD;
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.(en)</use>
      <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.&#xD;
&#xD;
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.&#xD;
&#xD;
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&#xD;
&#xD;
Not to be used to record biometric detail or biomarkers about an individual - use a specific ENTRY archetype for this purpose.(en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record details about a person as they are known or understood in the course of clinical documentation.</purpose>
      <keywords>provider, carer, staff, healthcare professional, relative, next-of-kin, practitioner, witness, friend, neighbour, child, family, sibling, parent, individual</keywords>
      <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:&#xD;
- the copyholder of an advanced care record, using the 'Copyholder' SLOT within the EVALUATION.advance_care_directive archetype;&#xD;
- the role and contact details of a named contact person within an organisation, using the 'Contact person' SLOT within the CLUSTER.organisation archetype;&#xD;
- details about a relative in a family history record, using the 'Family member details' SLOT within the openEHR-EHR-EVALUATION.family_history archetype; &#xD;
- the name of the person who collected a laboratory specimen from a patient, using the 'Specimen collector details' within the CLUSTER.specimen archetype; or&#xD;
- a witness to a fall or accident, using the 'Witness' SLOT within the CLUSTER.health_event archetype.&#xD;
&#xD;
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.&#xD;
&#xD;
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.</use>
      <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.&#xD;
&#xD;
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.&#xD;
&#xD;
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&#xD;
&#xD;
Not to be used to record biometric detail or biomarkers about an individual - use a specific ENTRY archetype for this purpose.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fr</code_string>
      </language>
      <purpose>Pour enregistrer les informations relatives à une personne telles qu'elles sont connues ou entendues dans le cadre de la documentation clinique.</purpose>
      <keywords>prestataire de soins, aidant, membre du personnel, professionnel de santé, proche, parent, praticien, témoin, ami, voisin, enfant, famille, frère, sœur, parent, personne</keywords>
      <use>À utiliser pour enregistrer les informations relatives à une personne telles qu’elles sont connues ou entendues dans le cadre de la documentation clinique, souvent de manière ponctuelle ou lorsqu’il n’est pas approprié ou possible d’utiliser un registre ou un index démographique officiel. Exemples :&#xD;
- le détenteur d’une directive anticipée de soins, en utilisant le SLOT « Copyholder » au sein de l’archétype EVALUATION.advance_care_directive ;&#xD;
- le rôle et les coordonnées d’une personne de contact désignée au sein d’une organisation, en utilisant le SLOT « Contact person » de l’archétype CLUSTER.organisation ;&#xD;
- les informations concernant un proche dans un dossier d’antécédents familiaux, en utilisant le SLOT « Family member details » de l’archétype openEHR-EHR-EVALUATION.family_history ; &#xD;
- le nom de la personne ayant prélevé un échantillon de laboratoire sur un patient, à l’aide du SLOT « Specimen collector details » de l’archétype CLUSTER.specimen ; ou&#xD;
- un témoin d’une chute ou d’un accident, à l’aide du SLOT « Witness » de l’archétype CLUSTER.health_event.&#xD;
&#xD;
Dans la plupart des cas d’utilisation simples de la documentation clinique, l’élément non structuré « Name » de l’archétype CLUSTER.person suffira pour enregistrer le nom d’une personne dans un dossier médical. Toutefois, dans les cas où un nom structuré est nécessaire ou souhaitable à des fins de documentation clinique, imbriquez l’archétype CLUSTER.structured_name dans le SLOT « Structured name ».&#xD;
&#xD;
Cet archétype pourrait également servir de substitut aux données démographiques formelles lors de la révision d’un modèle avec des experts du domaine — par exemple, dans le cadre d’une évaluation où les évaluateurs s’attendent à voir les coordonnées d’une personne en haut du formulaire d’évaluation.</use>
      <misuse>À ne pas utiliser pour enregister la gestion formelle de l’identification, ni à des fins de tenue d’un registre ou d’un index démographique officiel. Utilisez un index principal des patients (Master Patient Index) ou un index des prestataires de soins (Health Provider Index) officiel à cette fin, ou encore des archétypes basés sur le modèle d’informations démographiques openEHR.&#xD;
&#xD;
À ne pas utiliser pour représenter le sujet des soins, les participants ou l’auteur du dossier, ni des éléments de données similaires qui doivent être représentés formellement dans le dossier de santé à l’aide des attributs du modèle de référence.&#xD;
&#xD;
À ne pas utiliser pour enregister la date de naissance d’une personne – utilisez l’élément de données « Date of birth » au sein de l'archétype EVALUATION.birth_summary à cette fin.&#xD;
&#xD;
À ne pas utiliser pour enregistrer des données biométriques ou des biomarqueurs concernant une personne – utilisez un archétype ENTRY spécifique à cette fin.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>zh</code_string>
      </language>
      <purpose>*To record details about a person as they are known or understood in the course of clinical documentation. (en)</purpose>
      <keywords>*provider, carer, staff, healthcare professional, relative, next-of-kin, practitioner, witness, friend, neighbour, child, family, sibling, parent, individual (en)</keywords>
      <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:&#xD;
- the copyholder of an advanced care record, using the 'Copyholder' SLOT within the EVALUATION.advance_care_directive archetype;&#xD;
- the role and contact details of a named contact person within an organisation, using the 'Contact person' SLOT within the CLUSTER.organisation archetype;&#xD;
- details about a relative in a family history record, using the 'Family member details' SLOT within the openEHR-EHR-EVALUATION.family_history archetype; &#xD;
- the name of the person who collected a laboratory specimen from a patient, using the 'Specimen collector details' within the CLUSTER.specimen archetype; or&#xD;
- a witness to a fall or accident, using the 'Witness' SLOT within the CLUSTER.health_event archetype.&#xD;
&#xD;
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.&#xD;
&#xD;
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. (en)</use>
      <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.&#xD;
&#xD;
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.&#xD;
&#xD;
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&#xD;
&#xD;
Not to be used to record biometric detail or biomarkers about an individual - use a specific ENTRY archetype for this purpose. (en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Para registrar detalles sobre una persona tal y como se conocen o entienden en el curso de la documentación clínica.</purpose>
      <keywords>proveedor, cuidador, personal, profesional sanitario, familiar, pariente cercano, profesional, testigo, amigo, vecino, niño, familia, hermano, padre, individuo</keywords>
      <use>Utilizar para registrar los detalles de una persona tal y como se conocen o entienden en el curso de la documentación clínica, a menudo ad hoc o cuando no es apropiado o posible utilizar un registro o índice demográfico formal. Algunos ejemplos son:&#xD;
- El nombre y los datos de contacto de una persona que posee una copia física de un documento de voluntades anticipadas, usando el slot 'Encargado de la copia' en el arquetipo EVALUATION.advance_care_directive;&#xD;
- La función y los datos de una persona de contacto nombrada dentro de una organización, utilizando el SLOT "Persona de contacto" dentro del arquetipo CLUSTER.organisation;&#xD;
- Los datos de un pariente en un registro de historia familiar, utilizando el SLOT 'Family member details' dentro del arquetipo openEHR-EHR-EVALUATION.family_history;&#xD;
- El nombre de la persona que recogió una muestra de laboratorio de un paciente, utilizando los "detalles del recolector de muestras" dentro del arquetipo CLUSTER.specimen; o&#xD;
- Un testigo de una caída o accidente, utilizando el SLOT "Testigo" dentro del arquetipo CLUSTER.health_event.&#xD;
&#xD;
En la mayoría de los casos de uso de registros clínicos sencillos, el elemento no estructurado "Nombre" dentro del arquetipo CLUSTER.person será suficiente para registrar el nombre de una persona como parte de un registro sanitario. Sin embargo, en circunstancias en las que sea necesario o deseable un nombre estructurado para fines de registro clínico, incluya este arquetipo dentro del SLOT 'Nombre estructurado' en el arquetipo CLUSTER.person. Si el arquetipo CLUSTER.structured_name se incluye dentro del SLOT 'Structured name', cualquiera de los elementos de datos, o todos ellos, pueden combinarse juntos como una cadena de texto y representarse en el elemento 'Nombre' siempre que sean coherentes.&#xD;
&#xD;
Este arquetipo también puede utilizarse como sustituto de los datos demográficos formales cuando se revise una plantilla con expertos del dominio - por ejemplo, una evaluación en la que los revisores esperarían ver los datos del paciente en la parte superior del formulario.</use>
      <misuse>No debe utilizarse para representar o sustituir la gestión de la identificación formal ni para mantener un registro o índice demográfico oficial. Utilice para ello un Índice Maestro de Pacientes o un Índice de Proveedores de Salud formales o arquetipos basados en el Modelo de Información Demográfico de openEHR.&#xD;
&#xD;
No debe utilizarse para representar el sujeto de la atención, los participantes o el autor del registro y elementos de datos similares que deberían representarse formalmente en el registro sanitario utilizando los atributos del Modelo de Referencia.&#xD;
&#xD;
No debe utilizarse para registrar la fecha de nacimiento de un individuo: utilice el elemento de datos "Fecha de nacimiento" dentro de EVALUATION.birth_summary para este fin&#xD;
&#xD;
No debe utilizarse para registrar detalles biométricos o biomarcadores sobre un individuo - utilice un arquetipo de ENTRY específico para este fin.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Natalia Strauch, Alina Rehberg</author>
    <author id="organisation">Medizinische Hochschule Hannover</author>
    <author id="email">Strauch.Natalia@mh-hannover.de, rehberg.alina@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-pt</code_string>
    </language>
    <author id="name">Beatriz Soares</author>
    <author id="organisation">Promptly Health</author>
    <author id="email">beatriz.soares@promptlyhealth.com</author>
    <accreditation>Beatriz Soares, Promptly Health, Portugal</accreditation>
    <other_details id="other_contributors">Alex Anguelov, Promptly Health, Portugal&#xD;
Diogo Neto, Promptly Health, Portugal</other_details>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Elham Gholami, Erik Sundvall</author>
    <author id="organisation">Region Stockholm</author>
    <author id="email">erik.sundvall@regionstockholm.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Liv Laugen, John Tore Valand, Vebjørn Arntzen, Kanika Kuwelker</author>
    <author id="organisation">​Oslo University Hospital, Norway, Helse Bergen, Helse Vest IKT</author>
    <author id="email">liv.laugen@ous-hf.no, john.tore.valand@helse-bergen.no, john.tore.valand@helse-vest-ikt.no, varntzen@ous-hf.no, kanika.kuwelker@helse-vest-ikt.no</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>el</code_string>
    </language>
    <author id="name">Erasmia Partafylla</author>
    <author id="organisation">Sigmasoft</author>
    <author id="email">c.partafylla@sigmasoft.gr</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fr</code_string>
    </language>
    <author id="name">Jonas Bucher</author>
    <author id="organisation">Cistec AG</author>
    <author id="email">jonas.bucher@cistec.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>zh</code_string>
    </language>
    <author id="name">Yexuan Cheng</author>
    <author id="organisation">浙江大学</author>
    <author id="email">3160100913@zju.edu.cn</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es</code_string>
    </language>
    <author id="name">Diego Bosca</author>
    <author id="organisation">VeraTech for Health</author>
    <author id="email">yampeku@veratech.es</author>
    <accreditation>Native speaker. First Certificate in English</accreditation>
  </translations>
  <uid>
    <value>3f7fbe34-4e64-4c02-8d1a-402f7b0f57ce</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-CLUSTER.person.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>CLUSTER</rm_type_name>
    <occurrences>
      <lower_included>true</lower_included>
      <upper_included>true</upper_included>
      <lower_unbounded>false</lower_unbounded>
      <upper_unbounded>false</upper_unbounded>
      <lower>1</lower>
      <upper>1</upper>
    </occurrences>
    <node_id>at0000</node_id>
    <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
      <rm_attribute_name>items</rm_attribute_name>
      <existence>
        <lower_included>true</lower_included>
        <upper_included>true</upper_included>
        <lower_unbounded>false</lower_unbounded>
        <upper_unbounded>false</upper_unbounded>
        <lower>1</lower>
        <upper>1</upper>
      </existence>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0001</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0011</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </attributes>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0002</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.structured_name(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
          <expression xsi:type="EXPR_BINARY_OPERATOR">
            <type>Boolean</type>
            <operator>2007</operator>
            <precedence_overridden>false</precedence_overridden>
            <left_operand xsi:type="EXPR_LEAF">
              <type>String</type>
              <item xsi:type="xsd:string">archetype_id/value</item>
              <reference_type>attribute</reference_type>
            </left_operand>
            <right_operand xsi:type="EXPR_LEAF">
              <type>C_STRING</type>
              <item xsi:type="C_STRING">
                <pattern>openEHR-EHR-CLUSTER\.structured_name(-[a-zA-Z0-9_]+)*\.v1</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0003</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_IDENTIFIER</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0004</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </attributes>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0005</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.address(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
          <expression xsi:type="EXPR_BINARY_OPERATOR">
            <type>Boolean</type>
            <operator>2007</operator>
            <precedence_overridden>false</precedence_overridden>
            <left_operand xsi:type="EXPR_LEAF">
              <type>String</type>
              <item xsi:type="xsd:string">archetype_id/value</item>
              <reference_type>attribute</reference_type>
            </left_operand>
            <right_operand xsi:type="EXPR_LEAF">
              <type>C_STRING</type>
              <item xsi:type="C_STRING">
                <pattern>openEHR-EHR-CLUSTER\.address(-[a-zA-Z0-9_]+)*\.v1</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0006</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.electronic_communication(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
          <expression xsi:type="EXPR_BINARY_OPERATOR">
            <type>Boolean</type>
            <operator>2007</operator>
            <precedence_overridden>false</precedence_overridden>
            <left_operand xsi:type="EXPR_LEAF">
              <type>String</type>
              <item xsi:type="xsd:string">archetype_id/value</item>
              <reference_type>attribute</reference_type>
            </left_operand>
            <right_operand xsi:type="EXPR_LEAF">
              <type>C_STRING</type>
              <item xsi:type="C_STRING">
                <pattern>openEHR-EHR-CLUSTER\.electronic_communication(-[a-zA-Z0-9_]+)*\.v1</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0007</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.organisation(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
          <expression xsi:type="EXPR_BINARY_OPERATOR">
            <type>Boolean</type>
            <operator>2007</operator>
            <precedence_overridden>false</precedence_overridden>
            <left_operand xsi:type="EXPR_LEAF">
              <type>String</type>
              <item xsi:type="xsd:string">archetype_id/value</item>
              <reference_type>attribute</reference_type>
            </left_operand>
            <right_operand xsi:type="EXPR_LEAF">
              <type>C_STRING</type>
              <item xsi:type="C_STRING">
                <pattern>openEHR-EHR-CLUSTER\.organisation(-[a-zA-Z0-9_]+)*\.v1</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0008</node_id>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0009</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.media_file(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
          <expression xsi:type="EXPR_BINARY_OPERATOR">
            <type>Boolean</type>
            <operator>2007</operator>
            <precedence_overridden>false</precedence_overridden>
            <left_operand xsi:type="EXPR_LEAF">
              <type>String</type>
              <item xsi:type="xsd:string">archetype_id/value</item>
              <reference_type>attribute</reference_type>
            </left_operand>
            <right_operand xsi:type="EXPR_LEAF">
              <type>C_STRING</type>
              <item xsi:type="C_STRING">
                <pattern>openEHR-EHR-CLUSTER\.media_file(-[a-zA-Z0-9_]+)*\.v1</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0010</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </attributes>
      </children>
      <cardinality>
        <is_ordered>false</is_ordered>
        <is_unique>false</is_unique>
        <interval>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>1</lower>
        </interval>
      </cardinality>
    </attributes>
  </definition>
  <ontology>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Person</items>
        <items id="description">An individual human being.</items>
      </items>
      <items code="at0001">
        <items id="text">Name</items>
        <items id="description">The unstructured name for the individual.</items>
        <items id="comment">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'.</items>
      </items>
      <items code="at0002">
        <items id="text">Structured name</items>
        <items id="description">Alternative representation of an individual's complete name by separation into discrete, structured components.</items>
        <items id="comment">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.</items>
      </items>
      <items code="at0003">
        <items id="text">Identifier</items>
        <items id="description">Identifier associated with the individual.</items>
        <items id="comment">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.</items>
      </items>
      <items code="at0004">
        <items id="text">Role</items>
        <items id="description">The relationship or role of the individual to the subject of the health record.</items>
        <items id="comment">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.</items>
      </items>
      <items code="at0005">
        <items id="text">Address</items>
        <items id="description">Details about an address for the individual.</items>
      </items>
      <items code="at0008">
        <items id="text">Additional details</items>
        <items id="description">Additional details about the individual.</items>
      </items>
      <items code="at0010">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the individual not captured in other fields.</items>
      </items>
      <items code="at0007">
        <items id="text">Organisation</items>
        <items id="description">Details about the organisational context for the individual.</items>
        <items id="comment">For example: identifying the business or community organisation associated with the 'Role' of the individual.</items>
      </items>
      <items code="at0006">
        <items id="text">Electronic communication</items>
        <items id="description">Details about one or more types of electronic communication for the individual.</items>
      </items>
      <items code="at0009">
        <items id="text">Photo</items>
        <items id="description">Photograph of the individual.</items>
      </items>
      <items code="at0011">
        <items id="text">Label</items>
        <items id="description">A label for the individual.</items>
        <items id="comment">For example: 'Neighbour in the house with the red door'.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Person</items>
        <items id="description">Et identifisert menneske.</items>
      </items>
      <items code="at0001">
        <items id="text">Navn</items>
        <items id="description">Ustrukturert navn for personen.</items>
        <items id="comment">Innholdet i dette elementet kan være en sammenstilling av en eller flere komponenter fra arketypen CLUSTER.structured_name. For eksempel: "John Markham", "Professor Sir John Markham", "John Markham Jnr MP".</items>
      </items>
      <items code="at0002">
        <items id="text">Strukturert navn</items>
        <items id="description">Alternativ representasjon av det fullstendige navnet til en person ved å splitte det opp i strukturerte enkeltkomponenter.</items>
        <items id="comment">Et utvalg av eller alle de strukturerte navneelementene kan kombineres til en tekststreng og representeres i dataelementet "Navn" i denne arketypen.</items>
      </items>
      <items code="at0003">
        <items id="text">Identifikator</items>
        <items id="description">Identifikator for personen.</items>
        <items id="comment">Forekomster for dette dataelementet er satt til 0..* for å tillatte registrering av mer enn én Identifikator. Legg merke til at DV_IDENTIFIER-datatypen inneholder flere underkomponenter for å registrere ID-verdi, type, utsteder og tilordnet. For eksempel: personnummer, førerkort eller passnummer.</items>
      </items>
      <items code="at0004">
        <items id="text">Rolle</items>
        <items id="description">Relasjonen eller rollen personen har til individet som pasientjournalen omhandler.</items>
        <items id="comment">For eksempel: kopiinnhaver av et fremtidig behandlingsvalg, kontaktperson i en organisasjon, slektning, prøvetaker eller et vitne til et fall eller ulykke. Hvis personen som beskrives i denne arketypen er pasienten, er dette dataelementet unødvendig.</items>
      </items>
      <items code="at0005">
        <items id="text">Adresse</items>
        <items id="description">Detaljer om en persons adresse.</items>
      </items>
      <items code="at0006">
        <items id="text">Elektronisk kommunikasjon</items>
        <items id="description">Detaljer om en eller flere typer elektronisk kommunikasjon.</items>
      </items>
      <items code="at0007">
        <items id="text">Organisasjon</items>
        <items id="description">Detaljer om organisasjonstilknytning for personen.</items>
        <items id="comment">For eksempel: Identifisere virksomheten eller samfunnsorganisasjonen knyttet til rollen til personen.</items>
      </items>
      <items code="at0008">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Ytterligere detaljer om personen.</items>
      </items>
      <items code="at0009">
        <items id="text">Bilde</items>
        <items id="description">Bilde av personen.</items>
      </items>
      <items code="at0010">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om personen som ikke er registrert i andre felt.</items>
      </items>
      <items code="at0011">
        <items id="text">Betegnelse</items>
        <items id="description">En betegnelse (label) for personen.</items>
        <items id="comment">For eksempel: "Naboen i huset med den rød døren".</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Person</items>
        <items id="description">Ein identifizierter Mensch.</items>
      </items>
      <items code="at0001">
        <items id="text">Name</items>
        <items id="description">Der unstrukturierte Name der Person.</items>
        <items id="comment">Der Inhalt dieses Datenelements kann aus einer oder mehreren Komponenten vom CLUSTER.structured_name abgeleitet werden, die zusammen als ein Textstring kombiniert werden. Zum Beispiel: „John Markham“, „Professor Sir John Markham“, „John Markham Jnr MP“.</items>
      </items>
      <items code="at0002">
        <items id="text">Name strukturiert</items>
        <items id="description">Alternative Darstellung des vollständigen Namens der Person durch Trennung in diskrete, strukturierte Komponenten.</items>
        <items id="comment">Es können beliebige oder alle strukturierte Elemente des Namens als Textzeichenfolge kombiniert und im Datenelement „Name“ präsentieren werden.</items>
      </items>
      <items code="at0003">
        <items id="text">Identifikator</items>
        <items id="description">Mit der Person verbundener Identifikator.</items>
        <items id="comment">Kardinalität für dieses Datenelement wird auf 0..* gesetzt, damit mehr als einer Identifikator dargestellt werden kann. Beachten Sie, dass der DV_IDENTIFIER-Datentyp mehrere Unterkomponenten zum Aufzeichnen des ID-Werts, -Typs, -Ausstellers und -Zuweisers enthält. Zum Beispiel - Sozialversicherungsnummer, Führerschein oder Passnummer.</items>
      </items>
      <items code="at0004">
        <items id="text">Rolle</items>
        <items id="description">Die Beziehung oder die Rolle der Person zur Person in der elektronischen Gesundheitsakte.</items>
        <items id="comment">Zum Beispiel - der Inhaber einer Patientenverfügung, Kontaktperson in einer Organisation, Verwandter in einem Eintrag zur Familienananese, Probenabnehmer oder Zeuge eines Sturzes oder Unfalls. Wenn die anhand dieses Archetyps beschriebene Person der/die Patient/in der Gesundheitsakte ist, dann ist dieses Datenelement redundant.</items>
      </items>
      <items code="at0005">
        <items id="text">Adresse</items>
        <items id="description">Angaben zu einer Adresse der Person.</items>
      </items>
      <items code="at0006">
        <items id="text">Elektronische Kommunikation</items>
        <items id="description">Angaben zu einer oder mehreren Arten der elektronischen Kommunikation für die Person.</items>
      </items>
      <items code="at0007">
        <items id="text">Organisation</items>
        <items id="description">Angaben über den organisatorischen Kontext für die Person.</items>
        <items id="comment">Zum Beispiel: Identifizierung des Unternehmens oder der Gemeinschaftsorganisation, die mit der „Rolle“ der Person assoziiert ist.</items>
      </items>
      <items code="at0008">
        <items id="text">Zusätzliche Angaben</items>
        <items id="description">Weitere Angaben zur Person.</items>
      </items>
      <items code="at0009">
        <items id="text">Foto</items>
        <items id="description">Foto der Person.</items>
      </items>
      <items code="at0010">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Beschreibung zu der Person, die in anderen Bereichen nicht erfasst wird.</items>
      </items>
      <items code="at0011">
        <items id="text">Bezeichnung</items>
        <items id="description">Bezeichnung der Person.</items>
        <items id="comment">Zum Beispiel: „Nachbar im Haus mit der roten Tür“.</items>
      </items>
    </term_definitions>
    <term_definitions language="zh">
      <items code="at0000">
        <items id="text">人</items>
        <items id="description">*An individual human being. (en)</items>
      </items>
      <items code="at0001">
        <items id="text">*Name (en)</items>
        <items id="description">*The unstructured name for the individual. (en)</items>
        <items id="comment">*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'. (en)</items>
      </items>
      <items code="at0002">
        <items id="text">结构化姓名</items>
        <items id="description">*Alternative representation of an individual's complete name by separation into discrete, structured components. (en)</items>
        <items id="comment">*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. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">标识符</items>
        <items id="description">*Identifier associated with the person. (en)</items>
        <items id="comment">*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. (en)</items>
      </items>
      <items code="at0004">
        <items id="text">角色</items>
        <items id="description">*The relationship or role of the individual to the subject of the health record (en)</items>
        <items id="comment">*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. (en)</items>
      </items>
      <items code="at0005">
        <items id="text">地址</items>
        <items id="description">*Details about an address for the individual. (en)</items>
      </items>
      <items code="at0008">
        <items id="text">其他详细信息</items>
        <items id="description">有关此人的其他详细信息。</items>
      </items>
      <items code="at0010">
        <items id="text">*Comment (en)</items>
        <items id="description">*Additional narrative about the individual not captured in other fields. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">*Organisation (en)</items>
        <items id="description">*Details about the organisational context for the individual. (en)</items>
        <items id="comment">*For example: identifying the business or community organisation associated with the 'Role' of the individual. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">*Electronic communication (en)</items>
        <items id="description">*Details about one or more types of electronic communication for the individual. (en)</items>
      </items>
      <items code="at0009">
        <items id="text">*Photo (en)</items>
        <items id="description">*Photograph of the individual. (en)</items>
      </items>
      <items code="at0011">
        <items id="text">*Label (en)</items>
        <items id="description">*A label for the individual. (en)</items>
        <items id="comment">*For example: 'Neighbour in the house with the red door'. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Person</items>
        <items id="description">En mänsklig individ.</items>
      </items>
      <items code="at0001">
        <items id="text">Namn</items>
        <items id="description">Individens namn i ostrukturerad form.</items>
        <items id="comment">Innehållet i detta dataelement kan exempelvis skapas genom en sammanslagning av en eller flera komponenter från CLUSTER.structured_name. Till exempel: 'John Markham', 'Professor Sir John Markham', 'John Markham Jnr MP'</items>
      </items>
      <items code="at0002">
        <items id="text">Strukturerat namn</items>
        <items id="description">Alternativ representation av en individs fullständiga namn genom uppdelning i enskilda komponenter.</items>
        <items id="comment">Några eller alla strukturerade namnelement kan kombineras som en textsträng och representeras i dataelementet 'Namn' i denna arketyp.</items>
      </items>
      <items code="at0003">
        <items id="text">Identifierare</items>
        <items id="description">Identifierare förknippad med personen.</items>
        <items id="comment">Förekomster för detta dataelement är satt till 0..* för att tillåta att mer än en identifierare kan registreras. Observera att DV_IDENTIFIER-datatypen innehåller flera underkomponenter för registrering av ID-värde, typ, utfärdare och tilldelad. Till exempel - personnummer; körkort; eller passnummer.</items>
      </items>
      <items code="at0004">
        <items id="text">Roll</items>
        <items id="description">Personens relation eller roll till individen eller patienten.</items>
        <items id="comment">Exempelvis: Person som har en fysisk kopia av patientens önskemål om vård i händelse av att patienten inte längre kan kommunicera; kontaktperson i en organisation; en släkting i en familjehistorik; provtagare; vittne till en fallolycka.&#xD;
&#xD;
Om individen som beskrivs med denna arketyp är den som själva journalen gäller, då är detta dataelement redundant/överflödigt.</items>
      </items>
      <items code="at0005">
        <items id="text">Adress</items>
        <items id="description">Detaljer om en adress för personen.</items>
      </items>
      <items code="at0006">
        <items id="text">Elektronisk kommunikation</items>
        <items id="description">Detaljer om en eller flera specifika typer av elektronisk kommunikation för personen.</items>
      </items>
      <items code="at0007">
        <items id="text">Organisation</items>
        <items id="description">Detaljer om det organisatoriska sammanhanget/kopplingen för denna person.</items>
        <items id="comment">Exempelvis: Företaget eller organisationen som är kopplad till individens "roll".</items>
      </items>
      <items code="at0008">
        <items id="text">Ytterligare detaljer</items>
        <items id="description">Ytterligare information om personen.</items>
      </items>
      <items code="at0009">
        <items id="text">Foto</items>
        <items id="description">Fotografi på individen.</items>
      </items>
      <items code="at0010">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligare information om personen som inte rean beskrivits i andra fält.</items>
      </items>
      <items code="at0011">
        <items id="text">Beskrivning</items>
        <items id="description">Identifierande beskrivning av en person</items>
        <items id="comment">Exempelvis: 'Granne i huset med den röda dörren'.</items>
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Persona</items>
        <items id="description">Un ser humano individual</items>
      </items>
      <items code="at0001">
        <items id="text">Nombre</items>
        <items id="description">El nombre no estructurado del individuo</items>
        <items id="comment">El contenido de este elemento de datos puede derivarse de uno o más componentes de CLUSTER.structured_name combinados como una cadena de texto. Por ejemplo: "John Markham", "Professor Sir John Markham", "John Markham Jnr MP".</items>
      </items>
      <items code="at0002">
        <items id="text">Nombre estructurado</items>
        <items id="description">Una representación alternativa del nombre completo del individuo separado en componentes estructurados</items>
        <items id="comment">Cualquiera de los elementos del nombre estructurado, o todos ellos, pueden combinarse como una cadena de texto y utilizarse en el elemento de datos "Nombre" de este arquetipo.</items>
      </items>
      <items code="at0003">
        <items id="text">Identificador</items>
        <items id="description">Identificador asociado con el individuo</items>
        <items id="comment">Las ocurrencias de este elemento de datos se establecen en 0..* para permitir que se registre más de un identificador. Obsérvese que el tipo de datos DV_IDENTIFIER contiene múltiples subcomponentes para registrar el valor del identificador, el tipo, el emisor y el asignador. Por ejemplo, el número de la seguridad social, el del carnet de conducir o el del pasaporte.</items>
      </items>
      <items code="at0004">
        <items id="text">Rol</items>
        <items id="description">La relación o rol del individuo con el sujeto al que pertenece el registro de salud</items>
        <items id="comment">Por ejemplo: el encargado de guardar la copia física del documento de voluntades anticipadas; la persona de contacto en una organización; el pariente en una entrada de historia familiar; el recolector de muestras; o el testigo de una caída o accidente. Si la persona que se describe mediante este arquetipo es el sujeto de la historia clínica, estos datos son redundantes.</items>
      </items>
      <items code="at0005">
        <items id="text">Dirección</items>
        <items id="description">Detalles sobre la dirección de un individuo</items>
      </items>
      <items code="at0006">
        <items id="text">Comunicación electrónica</items>
        <items id="description">Detalles sobre uno o más tipos de comunicación electrónica del individuo.</items>
      </items>
      <items code="at0007">
        <items id="text">Organización</items>
        <items id="description">Detalles sobre el contexto organizacional del individuo</items>
        <items id="comment">Por ejemplo: identificar la empresa u organización comunitaria asociada al 'rol' del individuo.</items>
      </items>
      <items code="at0008">
        <items id="text">Detalles adicionales</items>
        <items id="description">Detalles adicionales sobre el individuo.</items>
      </items>
      <items code="at0009">
        <items id="text">Foto</items>
        <items id="description">Fotografía del individuo</items>
      </items>
      <items code="at0010">
        <items id="text">Comentario</items>
        <items id="description">Información narrativa adicional sobre el individuo no capturada en otros campos.</items>
      </items>
      <items code="at0011">
        <items id="text">Etiqueta</items>
        <items id="description">Una etiqueta para el individuo</items>
        <items id="comment">Por ejemplo: 'Vecino de la casa con la puerta roja'</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-pt">
      <items code="at0000">
        <items id="text">Pessoa</items>
        <items id="description">Um ser humano individual.</items>
      </items>
      <items code="at0001">
        <items id="text">Nome</items>
        <items id="description">O nome informal do indivíduo.</items>
        <items id="comment">O conteúdo deste elemento de dados pode ser derivado de um ou mais componentes de CLUSTER.structured_name combinados numa string de texto. Por exemplo: 'John Markham', 'Professor Sir John Markham', 'John Markham Jnr MP'.</items>
      </items>
      <items code="at0002">
        <items id="text">Nome formal</items>
        <items id="description">Representação alternativa do nome completo de um indivíduo por meio da separação em componentes estruturados e discretos.</items>
        <items id="comment">Qualquer ou todos os elementos de nome estruturados podem ser combinados numa string de texto e representados no elemento de dados 'Name' neste arquétipo.</items>
      </items>
      <items code="at0003">
        <items id="text">Identificador</items>
        <items id="description">Identificador associado ao indivíduo.</items>
        <items id="comment">As ocorrências para este elemento de dados estão definidas como 0..* para permitir que mais do que um Identificador seja registado. Note que o tipo de dados DV_IDENTIFIER contém vários sub-componentes para registrar o valor do ID, tipo, emissor e atribuição. Por exemplo - número de segurança social; carta de condução; ou número de passaporte.</items>
      </items>
      <items code="at0004">
        <items id="text">Papel</items>
        <items id="description">A relação ou papel do indivíduo em relação ao sujeito do registo de saúde.</items>
        <items id="comment">Por exemplo - o detentor de uma cópia de um registo de cuidados avançados; pessoa de contacto numa organização; familiar num registo de histórico familiar; coletor de espécimes; ou testemunha de uma queda ou acidente. Se o indivíduo descrito usando este arquétipo é o sujeito do registo de saúde, então este elemento de dados é redundante.</items>
      </items>
      <items code="at0005">
        <items id="text">Morada</items>
        <items id="description">Detalhes sobre a morada do indivíduo.</items>
      </items>
      <items code="at0006">
        <items id="text">Comunicação eletrónica</items>
        <items id="description">Detalhes sobre um ou mais tipos de comunicação eletrónica para o indivíduo.</items>
      </items>
      <items code="at0007">
        <items id="text">Organização</items>
        <items id="description">Detalhes sobre o contexto organizacional do indivíduo.</items>
        <items id="comment">Por exemplo: identificando o negócio ou organização comunitária associada ao 'Role' do indivíduo.</items>
      </items>
      <items code="at0008">
        <items id="text">Detalhes adicionais</items>
        <items id="description">Detalhes adicionais sobre o indivíduo</items>
      </items>
      <items code="at0009">
        <items id="text">Fotografia</items>
        <items id="description">Fotografia do indivíduo</items>
      </items>
      <items code="at0010">
        <items id="text">Comentário</items>
        <items id="description">Informação adicional acerca do indivíduo, que não pode ser extraída a partir de outros campos.</items>
      </items>
      <items code="at0011">
        <items id="text">Rótulo</items>
        <items id="description">Um rótulo para o indivíduo.</items>
        <items id="comment">Por exemplo: 'Vizinho da casa com a porta vermelha'.</items>
      </items>
    </term_definitions>
    <term_definitions language="el">
      <items code="at0000">
        <items id="text">Άτομο</items>
        <items id="description">Ένας μεμονωμένος άνθρωπος.</items>
      </items>
      <items code="at0001">
        <items id="text">Όνομα</items>
        <items id="description">Το μη δομημένο όνομα για το άτομο.</items>
      </items>
      <items code="at0002">
        <items id="text">Ολόκληρο όνομα</items>
        <items id="description">Εναλλακτική αναπαράσταση του πλήρους ονόματος ενός ατόμου με διαχωρισμό σε διακριτά, δομημένα στοιχεία.</items>
      </items>
      <items code="at0003">
        <items id="text">Αναγνωριστικό</items>
        <items id="description">Αναγνωριστικό που σχετίζεται με το άτομο.</items>
        <items id="comment">Οι εμφανίσεις για αυτό το στοιχείο δεδομένων έχουν οριστεί σε 0..* για να επιτρέπεται η καταγραφή περισσότερων του ενός αναγνωριστικών. Σημειώστε ότι ο τύπος δεδομένων DV_IDENTIFIER περιέχει πολλαπλά υποστοιχεία για την καταγραφή της τιμής, του τύπου, του εκδότη και του εκχωρημένου αναγνωριστικού. Για παράδειγμα - αριθμός κοινωνικής ασφάλισης. άδεια οδήγησης; ή τον αριθμό διαβατηρίου.</items>
      </items>
      <items code="at0004">
        <items id="text">Ρόλος</items>
        <items id="description">Η σχέση ή ο ρόλος του ατόμου με το αντικείμενο του φακέλου υγείας.</items>
        <items id="comment">Για παράδειγμα - ο κάτοχος ενός αρχείου προκαταρκτικής φροντίδας. πρόσωπο επικοινωνίας σε έναν οργανισμό· συγγενής σε καταχώριση οικογενειακού ιστορικού. συλλέκτης δειγμάτων? ή μάρτυρας πτώσης ή ατυχήματος. Εάν το άτομο που περιγράφεται χρησιμοποιώντας αυτό το αρχέτυπο αποτελεί αντικείμενο του μητρώου υγείας, τότε αυτό το στοιχείο δεδομένων είναι περιττό.</items>
      </items>
      <items code="at0005">
        <items id="text">Διεύθυνση</items>
        <items id="description">Λεπτομέρειες σχετικά με μια διεύθυνση για το άτομο.</items>
      </items>
      <items code="at0006">
        <items id="text">Στοιχεία ηλεκτρονικής επικοινωνίας</items>
        <items id="description">Λεπτομέρειες σχετικά με έναν ή περισσότερους τύπους ηλεκτρονικής επικοινωνίας για το άτομο.</items>
      </items>
      <items code="at0007">
        <items id="text">Οργανισμός</items>
        <items id="description">Λεπτομέρειες σχετικά με το οργανωτικό πλαίσιο για το άτομο.</items>
        <items id="comment">Για παράδειγμα: προσδιορισμός της επιχείρησης ή της κοινοτικής οργάνωσης που σχετίζεται με τον «Ρόλο» του ατόμου.</items>
      </items>
      <items code="at0008">
        <items id="text">Επιπλέον πληροφορίες</items>
        <items id="description">Πρόσθετες λεπτομέρειες για το άτομο.</items>
      </items>
      <items code="at0009">
        <items id="text">Φωτογραφία</items>
        <items id="description">Φωτογραφία του ατόμου.</items>
      </items>
      <items code="at0010">
        <items id="text">Σχόλιο</items>
        <items id="description">Πρόσθετη αφήγηση για το άτομο που δεν έχει αποτυπωθεί σε άλλα πεδία.</items>
      </items>
      <items code="at0011">
        <items id="text">Ετικέτα</items>
        <items id="description">Μια ετικέτα για το άτομο.</items>
      </items>
    </term_definitions>
    <term_definitions language="fr">
      <items code="at0000">
        <items id="text">Personne</items>
        <items id="description">Un être humain en tant qu'individu.</items>
      </items>
      <items code="at0001">
        <items id="text">Nom</items>
        <items id="description">Nom non structuré de la personne.</items>
        <items id="comment">Le contenu de cet élément de données peut être dérivé d’un ou plusieurs composants du CLUSTER.structured_name combinés sous la forme d’une chaîne de caractères. Par exemple : « John Markham », « Professeur Sir John Markham », « John Markham Jnr, député ».</items>
      </items>
      <items code="at0002">
        <items id="text">Nom structuré</items>
        <items id="description">Représentation alternative du nom complet d'une personne, par décomposition en éléments distincts et structurés.</items>
        <items id="comment">Tout ou partie des éléments structurés du nom peuvent être combinés sous forme de chaîne de caractères et représentés dans l'élément de données « Nom » de cet archétype.</items>
      </items>
      <items code="at0003">
        <items id="text">Identifiant</items>
        <items id="description">Identifiant associé à la personne.</items>
        <items id="comment">Le nombre d'occurrences pour cet élément de données est défini à 0..* afin de permettre l'enregistrement de plusieurs identifiants. Notez que le type de données DV_IDENTIFIER contient plusieurs sous-composants permettant d'enregistrer la valeur de l'identifiant, son type, son émetteur et son attribution. Par exemple : numéro de sécurité sociale, permis de conduire ou numéro de passeport.</items>
      </items>
      <items code="at0004">
        <items id="text">Rôle</items>
        <items id="description">La relation ou le rôle de la personne par rapport au sujet du dossier médical.</items>
        <items id="comment">Par exemple : le détenteur d’un dossier de soins anticipés ; la personne de contact au sein d’une organisation ; un proche mentionné dans une entrée relative aux antécédents familiaux ; la personne chargée du prélèvement d’échantillons ; ou un témoin d’une chute ou d’un accident. Si la personne décrite à l’aide de cet archétype est le sujet du dossier médical, cet élément de données est alors redondant.</items>
      </items>
      <items code="at0005">
        <items id="text">Adresse</items>
        <items id="description">Informations relatives à l'adresse de la personne.</items>
      </items>
      <items code="at0008">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails supplémentaires sur la personne.</items>
      </items>
      <items code="at0010">
        <items id="text">Commentaire</items>
        <items id="description">Informations supplémentaires sur la personne qui ne figurent pas dans les autres champs.</items>
      </items>
      <items code="at0007">
        <items id="text">Organisation</items>
        <items id="description">Informations relatives au contexte organisationnel de la personne.</items>
        <items id="comment">Par exemple : identifiant l'entreprise ou l'organisation communautaire associée au « rôle » de la personne.</items>
      </items>
      <items code="at0006">
        <items id="text">Communication électronique</items>
        <items id="description">Informations relatives à un ou plusieurs types de communication électronique concernant cette personne.</items>
      </items>
      <items code="at0009">
        <items id="text">Photo</items>
        <items id="description">Photographie de la personne.</items>
      </items>
      <items code="at0011">
        <items id="text">Étiquette</items>
        <items id="description">Une désignation de la personne.</items>
        <items id="comment">Par exemple : « Voisin de la maison à la porte rouge ».</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
