<?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">2007-04-19</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>Tomas Alme, DIPS ASA, Norway</other_contributors>
    <other_contributors>Nadim Anani, Karolinska Institutet, Sweden</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway</other_contributors>
    <other_contributors>Koray Atalag, University of Auckland, New Zealand</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Lars Bitsch-Larsen, Haukeland University hospital, Norway</other_contributors>
    <other_contributors>Sergio Carmona, Chile</other_contributors>
    <other_contributors>Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway</other_contributors>
    <other_contributors>Beatriz de Faria Leão, Brazil</other_contributors>
    <other_contributors>Shahla Foozonkhah, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Einar Fosse, UNN HF, Norwegian Centre for Integrated Care and Telemedicine, Norway</other_contributors>
    <other_contributors>Sebastian Garde, Ocean Informatics, Germany</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Anne Gunn Haugland, Helse Bergen HF, Norway</other_contributors>
    <other_contributors>Andreas Hering, Helse Bergen HF, Haukeland universitetssjukehus, Norway</other_contributors>
    <other_contributors>Omer Hotomaroglu, Turkey</other_contributors>
    <other_contributors>Lars Ivar Mehlum, Helse Bergen HF, Norway</other_contributors>
    <other_contributors>Sundaresan Jagannathan, Scottish NHS, United Kingdom</other_contributors>
    <other_contributors>Lars Morgan Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Hallvard Lærum, Norwegian Directorate of e-health, Norway</other_contributors>
    <other_contributors>Rose Mari Eikås, Helse Bergen, Norway</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Rune Pedersen, Universitetssykehuset i Nord Norge, Norway</other_contributors>
    <other_contributors>John Tore Valand, Haukeland Universitetssjukehus, Norway (Editor, Translation Editor)</other_contributors>
    <other_contributors>Jon Tysdahl, Furst medlab AS, Norway</other_contributors>
    <lifecycle_state>published</lifecycle_state>
    <other_details id="licence">This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.</other_details>
    <other_details id="custodian_organisation">openEHR Foundation</other_details>
    <other_details id="references">openEHR Foundation. openEHR wiki: Reason for Encounter or Chief Complaint [Internet]. 2008 Feb 13 [cited 2012 Jun 17];  Available at http://www.openehr.org/wiki/display/healthmod/Reason+for+encounter+or+Chief+complaint.</other_details>
    <other_details id="current_contact">Heather Leslie, Atomica Informatics&lt;heather.leslie@atomicainformatics.com&gt;</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">7313AC9D1C12B94659774834BEB899AE</other_details>
    <other_details id="build_uid">200b5651-e637-4e72-a7d5-69e45c719d40</other_details>
    <other_details id="revision">1.0.3</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Darstellung des Grundes bzw. der Gründe für die Initierung jeglicher Art von Begegnung oder Kontakt zwischen einem Gesundheitsdienstleister und der betreuten Person.</purpose>
      <keywords>Vorstellung</keywords>
      <keywords>vorgestellte Krankheit</keywords>
      <keywords>Beschwerde</keywords>
      <keywords>Grund</keywords>
      <keywords>Begegnung</keywords>
      <keywords>Kontakt</keywords>
      <keywords>Grund für die Begegnung</keywords>
      <keywords>Grund für den Kontakt</keywords>
      <keywords>Visite</keywords>
      <keywords>Grund der Visite</keywords>
      <use>Zur Darstellung des Grundes oder der Gründe für die Initierung jeglicher Art von Begegnungen oder Kontakten zwischen einem Gesundheitsdienstleister und der betreuten Person aufzuzeichnen. Der Grund kann ein klinischer, sozialer oder administrativer Zwecke sein.&#xD;
&#xD;
"Grund der Begegnung" ist eine in der klinischen Medizin gebräuchliche Formulierung. Der Begriff wird jedoch häufig auf zwei Arten verwendet - eine bezieht sich auf eine Verwaltungskategorie für die Gesundheitsversorgung und die andere spiegelt klinische oder soziale Probleme wieder, die Menschen motivieren die Gesundheitsversorgung aufzusuchen.&#xD;
&#xD;
Um die Phrasen und die Absicht zu verdeutlichen, enthält dieser Archetyp zwei Datenelemente:&#xD;
- Der erste Datenelement "Kontakttyp", um den administrativen Typ gewünschten oder erforderlichen Gesundheitsversorgung einzuteilen - zum Beispiel die Art des Besuchs wie Notfall, präoperative Einschätzung, routinemäßige vorgeburtliche Visite oder Wahlleistung. Dieses Datenelement spiegelt die administrative Kategorie der Versorgung wider. Die Verwendung des Ausdrucks "Kontaktart" anstelle von "Grund der Begegnung" oder "Grund des Besuchs" spiegelt den zunehmenden Trend zu alternativen Methoden der Gesundheitsversorgung wider, die möglicherweise nicht zu einem persönlichen Kontakt zwischen dem Leistungserbringer und dem Patienten innerhalb eines Behandlungszimmers führen.&#xD;
- Die zweite Datenelement "Vorstellung einer Beschwerde", um die klinischen Gründe für den Kontakt im Gesundheitswesen zu dokumentieren. "Hauptbeschwerde" gilt als Synonym für "Vorstellung einer Beschwerde". Diese sind hauptsächlich dazu bestimmt, die wahrgenommenen Probleme oder Symptome des Patienten zu erfassen, die dazu geführt haben, dass sie Gesundheitsberatung suchen. Beispiele für Probleme oder Symptome sind: "Wunsch nach Raucherentwöhnung", wie Stress, Kurzatmigkeit, genetische Beratung oder Bauchschmerzen. Zeichen wie ein gestörter Bewusstseinszustand können hier ebenfalls erfasst werden, beispielsweise durch paramedizinisches Personal im Falle eines bewusstlosen Patienten.</use>
      <misuse>Nicht zur Darstellung bestimmter Details der Geschichte des Patienten oder der Geschichte der Symptome aufzuzeichnen. Verwenden Sie hierzu den Archetype OBSERVATION.story, um die Erzählung und die zugehörigen geschachtelten CLUSTER-Archetypen für strukturierten Inhalt zu erfassen, z.B. CLUSTER.symptom, CLUSTER.event und CLUSTER.issue.&#xD;
&#xD;
Nicht zur Darstellung bestimmter Diagnosedetails, die zusätzlich zu einem Grund für die Begegnung erforderlich sein können, verwendet werden. Zum Beispiel um eine präoperative Diagnose im Rahmen einer stationären Aufnahme zu erfassen. Verwenden Sie den Archetyp EVALUATION.problem_diagnosis für diesen Zweck.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere årsak eller årsaker til kontakten mellom helsepersonell og individ.</purpose>
      <keywords>kontaktårsak</keywords>
      <keywords>årsak</keywords>
      <keywords>besøk</keywords>
      <keywords>årsak for besøk</keywords>
      <keywords>problemstilling</keywords>
      <keywords>konsultasjonsårsak</keywords>
      <keywords>innleggelsesårsak</keywords>
      <keywords>henvisningsgrunn</keywords>
      <keywords>henvisningsårsak</keywords>
      <keywords>henvendelse</keywords>
      <use>For å registrere årsak eller årsaker til kontakten mellom helsepersonell og individ. Årsak kan være klinisk, sosial eller administrativ.&#xD;
&#xD;
Kontaktårsak er et vanlig uttrykk som brukes i klinisk medisin, begrepet brukes oftest på to måter - en som refererer til en administrativ kategori for levering av helsetjenester og en som gjenspeiler det kliniske eller sosiale behovet for å søke helsetjenester. &#xD;
&#xD;
Arketypen inneholder to dataelementer:&#xD;
&#xD;
- "Administrativ kontaktårsak" brukes for å dokumentere den administrative delen av helsehjelpen som oppsøkes eller behøves, for eksempel konsultasjonstype, øyeblikkelig hjelp, preoperativ vurdering, svangerskapskontroll eller elektiv innleggelse. Dataelementet reflekterer en administrativ kategorisering av helsehjelpen. Valg av ordet kontaktårsak viser at det er en økt trend mot alternative måter for utføring av helsetjenester som ikke må ende opp med ansikt til ansikt kontakt mellom helsepersonell og pasient i konsultasjonsrommet.&#xD;
&#xD;
-"Klinisk kontaktårsak" brukes for å dokumentere kliniske årsaker for kontakten. Hovedproblemstilling blir regnet som et synonym for "Klinisk kontaktårsak". Formålet er å registrere individets oppfatning av problemer og symptomer som har vært utløsende faktor for at en søker hjelp fra helsevesenet, for eksempel ønske om å slutte å røyke, stress, kortpusthet eller magesmerter. Sykdomstegn som "nedsatt bevissthet" kan også registreres her, for eksempel når prehospitalt personell møter en bevisstløs person.</use>
      <misuse>Skal ikke benyttes for å registrere spesifikke detaljer om pasientens sykehistorie eller forløp av symptomer. Bruk OBSERVATION.story å registrere den fritekstlige delen og de relaterte nøstede CLUSTER-arketypene for strukturert innhold f.eks CLUSTER.symptom, CLUSTER.event og CLUSTER.issue. &#xD;
&#xD;
Skal ikke benyttes for å registrere bestemte detaljer om diagnoser som kan være nødvendig i tillegg til "Kontaktårsak" f.eks innleggelse eller preoperativ diagnose som en del av en innleggelse i sykehus for utførelse av en prosedyre. Bruk EVALUATION.problem_diagnosis for dette formålet.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Para gravar a(s) razão(ões) do início de qualquer tipo de contato de saúde entre um profissional de saúde e um paciente.</purpose>
      <keywords>apresentação</keywords>
      <keywords>queixa apresentada</keywords>
      <keywords>motivo para o encontro</keywords>
      <keywords>motivo</keywords>
      <keywords>queixa principal</keywords>
      <keywords>visita</keywords>
      <keywords>motivo para a visita</keywords>
      <use>Para gravar a(s) razão(ões) do início de qualquer tipo de contato de saúde entre um profissional de saúde e um paciente. &#xD;
&#xD;
Motivo para o encontro é um frase comum em medicina clínica, entretanto o termo é frequentemente usado de duas maneiras comuns - Uma refere-se à categoria administrativa para provisão de cuidado em saúde e a outra que reflete o gatilho clínico para buscar cuidado em saúde. &#xD;
&#xD;
Num esforço para esclarecer as frases e intenções, este arquétipo contém dois elementos de dados:&#xD;
- O primeiro, "Motivo para o contato", para documentar o tipo administrativo de cuidado em saúde procurado ou exigido - por exemplo o tipo de consulta, cuidado emergencial, risco cirúrgico, visita pré-natal de rotina ou adminissão eletiva. Este elemento de dado reflete a categoria administrativa da provisão do cuidado. O uso da frase "Motivo para o contato" ao invés de "Razão para o encontro" ou "Razão para visita" reflete uma tendência crescente em relação a métodos alternativos de provisão de cuidado em saúde que podem não resultar em um contato pessoal entre o profissional de saúde e o paciente dentro de um consultório.&#xD;
- O segundo, "Problema apresentado", para documentar as razões clínicas do contato em saúde. O objetivo destes é principalmente para capturar os problemas ou sintomas observados pelo paciente que o levaram a procurar orientação em saúde, como o desejo de parar de fumar, estresse, falta de ar ou dor abdominal. Sinais como estado de consciência alterado também podem ser capturados aqui, por exemplo por paramédicos com pacientes inconscientes.</use>
      <misuse>Não deve ser usado para gravar detalhes específicos e da estória do paciente ou seus sintomas. Use OBSERVATION.story para capturar a narrativa e arquétipos CLUSTER relacionados para conteúdo estruturado p.e. CLUSTER.symptom, CLUSTER.event and CLUSTER.issue.&#xD;
&#xD;
Não deve ser usado para gravar detalhes específicos de diagnósticos que podem ser necessários além do motivo para o encontro p.e. diagnóstico de admissão ou pré-operatório como parte de uma admissão para um procedimento hospitalar. Use EVALUATION.problem_diagnosis (e especializações relacionadas) para este propósito.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>el</code_string>
      </language>
      <purpose>Για την καταγραφή του λόγου ή των λόγων για την έναρξη οποιουδήποτε είδους συνάντησης ή επαφής υγειονομικής περίθαλψης από το άτομο που αποτελεί αντικείμενο φροντίδας.</purpose>
      <keywords>παρουσίαση</keywords>
      <keywords>Υποβολή καταγγελίας</keywords>
      <keywords>Λόγος συνάντησης</keywords>
      <keywords>λόγος</keywords>
      <keywords>Κύριο παράπονο</keywords>
      <keywords>επισκέπτομαι</keywords>
      <keywords>Λόγος επίσκεψης</keywords>
      <use>*Use to record the reason, or reasons, for initiation of any type of healthcare encounter or contact between a healthcare provider and the individual who is the subject of care. The reason may be for clinical, social or administrative purposes.&#xD;
&#xD;
Reason for Encounter is a common phrase used in clinical medicine, however the term is often used in two common ways - one that refers to an administrative category for provision of healthcare and the other that reflects clinical or social problems that motivate individuals to seek healthcare.&#xD;
&#xD;
In an effort to clarify the phrases and intent, this archetype contains two data elements:&#xD;
- The first, 'Contact type', to document the administrative type of healthcare sought or required - for example the type of consultation, emergency care, pre-operative assessment, routine antenatal visit or elective admission. This data element reflects the administrative category of care provision. Use of the phrase 'Contact type', rather than 'Reason for encounter' or 'Reason for visit' reflects the increasing trend towards alternative methods of healthcare provision that may not result in face-to-face contact between the healthcare provider and patient within a consulting room.&#xD;
- The second, 'Presenting problem', to document the clinical reasons for healthcare contact. Chief complaint is regarded as a synonym for 'Presenting problem'. These are intended mainly to capture the patient's perceived issues or symptoms which have triggered them to seek healthcare advice, such as desire to quit smoking, stress, shortness of breath, genetic counselling or abdominal pain. Signs such as impaired conscious state may also be captured here, for example by paramedical staff with an unconscious patient.(en)</use>
      <misuse>*Not to be used to record specific details of the patient's story or history of symptoms. Use OBSERVATION.story to capture the narrative and the related nested CLUSTER archetypes for structured content eg CLUSTER.symptom, CLUSTER.event and CLUSTER.issue.&#xD;
&#xD;
Not to be used to record specific diagnosis details that may be required in addition to a Reason for Encounter. For example, to record a Pre-operative Diagnosis as part of admission for a hospital procedure. Use the EVALUATION.problem_diagnosis 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 the reason, or reasons, for initiation of any type of healthcare encounter or contact by the individual who is the subject of care.</purpose>
      <keywords>presentation</keywords>
      <keywords>presenting complaint</keywords>
      <keywords>reason for encounter</keywords>
      <keywords>reason</keywords>
      <keywords>chief complaint</keywords>
      <keywords>visit</keywords>
      <keywords>reason for visit</keywords>
      <use>Use to record the reason, or reasons, for initiation of any type of healthcare encounter or contact between a healthcare provider and the individual who is the subject of care. The reason may be for clinical, social or administrative purposes.&#xD;
&#xD;
Reason for Encounter is a common phrase used in clinical medicine, however the term is often used in two common ways - one that refers to an administrative category for provision of healthcare and the other that reflects clinical or social problems that motivate individuals to seek healthcare.&#xD;
&#xD;
In an effort to clarify the phrases and intent, this archetype contains two data elements:&#xD;
- The first, 'Contact type', to document the administrative type of healthcare sought or required - for example the type of consultation, emergency care, pre-operative assessment, routine antenatal visit or elective admission. This data element reflects the administrative category of care provision. Use of the phrase 'Contact type', rather than 'Reason for encounter' or 'Reason for visit' reflects the increasing trend towards alternative methods of healthcare provision that may not result in face-to-face contact between the healthcare provider and patient within a consulting room.&#xD;
- The second, 'Presenting problem', to document the clinical reasons for healthcare contact. Chief complaint is regarded as a synonym for 'Presenting problem'. These are intended mainly to capture the patient's perceived issues or symptoms which have triggered them to seek healthcare advice, such as desire to quit smoking, stress, shortness of breath, genetic counselling or abdominal pain. Signs such as impaired conscious state may also be captured here, for example by paramedical staff with an unconscious patient.</use>
      <misuse>Not to be used to record specific details of the patient's story or history of symptoms. Use OBSERVATION.story to capture the narrative and the related nested CLUSTER archetypes for structured content eg CLUSTER.symptom, CLUSTER.event and CLUSTER.issue.&#xD;
&#xD;
Not to be used to record specific diagnosis details that may be required in addition to a Reason for Encounter. For example, to record a Pre-operative Diagnosis as part of admission for a hospital procedure. Use the EVALUATION.problem_diagnosis archetype for this purpose.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Registrar los motivos de un paciente para iniciar un encuentro o contacto con un proveedor de salud.</purpose>
      <keywords>problema</keywords>
      <keywords>síntoma</keywords>
      <keywords>razón</keywords>
      <keywords>motivo de consulta</keywords>
      <keywords>visita</keywords>
      <keywords>consulta</keywords>
      <use>Utilizar para registrar los motivos de un paciente para iniciar un encuentro o contacto con un proveedor de salud. El motivo tener un propósito clínico, social o administrativo.&#xD;
&#xD;
El arquetipo incluye dos elementos principales:&#xD;
&#xD;
- Motivo de consulta: para registrar el dato administrativo relacionado al tipo de asistencia médica buscada por el paciente.&#xD;
- Problema presentado: para registrar los problemas o síntomas que el paciente percibe, y que lo motivan a buscar asistencia médica. También se pueden registrar datos como el estado de conciencia de un paciente, por ejemplo por personal paramédico atendiendo a un paciente inconsciente.</use>
      <misuse>No se debe utilizar para registrar detalles específicos sobre la historia de síntomas del paciente. Para eso utilizar el arquetipo OBSERVATION.story.&#xD;
&#xD;
No debe ser utilizado para registrar diagnósticos. Para eso utilizar el arquetipo EVALUATION.problem_diagnosis.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ca</code_string>
      </language>
      <purpose>Registrar la raó, o raons, d'inici de qualsevol tipus de trobada o contacte assistencial per part del pacient que és objecte d'atenció.</purpose>
      <keywords>presentació</keywords>
      <keywords>presentació</keywords>
      <keywords>de</keywords>
      <keywords>la</keywords>
      <keywords>reclamació</keywords>
      <keywords>motiu</keywords>
      <keywords>de</keywords>
      <keywords>trobada</keywords>
      <keywords>raó</keywords>
      <keywords>queixa</keywords>
      <keywords>principal</keywords>
      <keywords>visita</keywords>
      <keywords>motiu</keywords>
      <keywords>de</keywords>
      <keywords>visita</keywords>
      <use>S'utilitza per registrar la raó, o raons, per iniciar qualsevol tipus de trobada o contacte sanitari entre un proveïdor sanitari i la persona que és objecte d'atenció. El motiu pot ser per a finalitats clíniques, socials o administratives.&#xD;
&#xD;
La raó de trobar-se és una frase comuna utilitzada en medicina clínica, però el terme s'utilitza sovint de dues maneres comunes: una que es refereix a una categoria administrativa per a la provisió d'assistència sanitària i l'altra que reflecteix els problemes clínics o socials que motiven els individus a buscar assistència sanitària.&#xD;
&#xD;
En un esforç per aclarir les frases i la intenció, aquest arquetip conté dos elements de dades:&#xD;
- El primer, 'tipus de contacte', per documentar el tipus administratiu d'atenció sanitària buscat o requerit - per exemple el tipus de consulta, atenció d'emergència, avaluació preoperatòria, visita prenatal rutinària o admissió optativa. Aquest element de dades reflecteix la categoria administrativa de prestació d'atenció. L'ús de la frase "tipus de contacte", en lloc de "motiu de trobada" o "motiu de visita" reflecteix la tendència creixent cap a mètodes alternatius de prestació sanitària que poden no donar lloc al contacte presencial entre el proveïdor d'atenció sanitària i el pacient dins d'una sala de consulta.&#xD;
- El segon, 'Presenting problem', per documentar les raons clíniques del contacte sanitari. La queixa principal es considera un sinònim de "problema de presentació". Aquests estan destinats principalment a captar els problemes o símptomes percebuts del pacient que els han desencadenat a buscar consell sanitari, com el desig de deixar de fumar, l'estrès, la falta d'aire, l'assessorament genètic o el dolor abdominal. També es poden capturar signes com ara un estat conscient afectat, per exemple per personal paramèdic amb un pacient inconscient.</use>
      <misuse>No s'ha d'utilitzar per registrar detalls específics de la història o història dels símptomes del pacient. Utilitzeu OBSERVATION.story per capturar la narrativa i els arquetips de CLÚSTER niats relacionats per al contingut estructurat, p. ex. CLUSTER.symptom, CLUSTER.event i CLUSTER.issue.&#xD;
&#xD;
No s'ha d'utilitzar per registrar detalls de diagnòstic específics que es poden requerir a més d'una raó per trobar-se. Per exemple, registrar un diagnòstic preoperatori com a part de l'ingrés per a un procediment hospitalari. Utilitzar l'arquetip EVALUATION.problem.diagnosis per a aquesta finalitat.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Anneka Sargeant</author>
    <author id="organisation">Medizinische Informatik, UMG</author>
    <author id="email">anneka.sargeant@med.uni-goettingen.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Lars Bitsch-Larsen og John Tore Valand</author>
    <author id="organisation">Haukeland University Hospital</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-br</code_string>
    </language>
    <author id="name">Fernanda Maia Ewerton</author>
    <author id="organisation">Core Consulting</author>
    <author id="email">fernanda.maiaewerton@gmail.com</author>
    <accreditation>Hospital Alemão Oswaldo Cruz (HAOC)</accreditation>
  </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>es</code_string>
    </language>
    <author id="name">Pablo Pazos</author>
    <author id="organisation">CaboLabs</author>
    <accreditation>Computer Engineer</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ca</code_string>
    </language>
    <author id="name">TRADCREA - Clara Calleja Vega</author>
    <author id="organisation">CatSalut. Servei Català de la Salut.</author>
    <author id="email">ccalleja@catsalut.cat</author>
  </translations>
  <uid>
    <value>3d268aac-eeb5-4f95-b1a8-1d4dec5d0ae7</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-EVALUATION.reason_for_encounter.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>EVALUATION</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_SINGLE_ATTRIBUTE">
      <rm_attribute_name>data</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>ITEM_TREE</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>at0001</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>0</lower>
            <upper>1</upper>
          </existence>
          <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>at0002</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>
              <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>
          <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>0</lower>
            </interval>
          </cardinality>
        </attributes>
      </children>
    </attributes>
  </definition>
  <ontology>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Reason for encounter</items>
        <items id="description">The reason for initiation of any healthcare encounter or contact by the individual who is the subject of care.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Contact type</items>
        <items id="description">Identification of the type, or administrative category, of healthcare sought or required by the subject of care.</items>
        <items id="comment">Coding of the 'Contact type' with a terminology is desirable, where possible. Examples include: pre-employment medical, routine antenatal visit, women's health check, pre-operative assessment, or annual medical check-up.</items>
      </items>
      <items code="at0004">
        <items id="text">Presenting problem</items>
        <items id="description">Identification of the clinical or social problem motivating the subject of care to seeking healthcare.</items>
        <items id="comment">Coding of the 'Presenting problem' with a terminology is desirable, where possible. Clinical or social reasons for seeking healthcare can include health issues, symptoms or physical signs. Examples: health issues - desire to quit smoking, domestic violence; symptoms - abdominal pain, shortness of breath; physical signs - an altered conscious state. 'Chief complaint' may be used as a valid synonym for 'Presenting problem' in templates.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Motivo para o encontro</items>
        <items id="description">O motivo de início de qualquer encontro em saúde ou contato pelo indivíduo que é sujeito do cuidado.</items>
      </items>
      <items code="at0001">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tipo de contato</items>
        <items id="description">Identificação do tipo, ou categoria administrativa, ou cuidado em saúde procurado ou exigido pelo sujeito do cuidado.</items>
        <items id="comment">Codificação do "tipo de contato" com uma terminologia é desejável, quando possível. Exemplos incluem: Exame pré-admissional, visita pré-natal de rotina, saúde da mulher, risco cirúrgico, ou avaliação médica anual.</items>
      </items>
      <items code="at0004">
        <items id="text">Problema apresentado</items>
        <items id="description">Identificação do problema clínico ou social que motiva o sujeito do cuidado a procurar cuidado em saúde.</items>
        <items id="comment">Codificação do "Problema apresentado" com uma terminologia é desejável, quando possível. Razões clínicas ou sociais na busca de cuidado em saúde podem incluir problemas de saúde, sintomas ou sinais físicos. Exemplos: problemas de saúde - desejo de parar de fumar, violência doméstica; sintomas - dor abdominal, falta de ar; sinais físicos - um estado de consciência alterado. "Queixa principal" pode ser usada como um sinônimo válido para "Problema apresentado" nos modelos.</items>
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Motivo de consulta</items>
        <items id="description">Motivo del paciente por el cual se inició un encuentro clínico o contacto.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tipo de contacto</items>
        <items id="description">Identificación del tipo o categoría administrativa por la cuál el paciente busca asistencia médica.</items>
        <items id="comment">Es deseable la codificación del 'Tipo de contacto' mediante una terminología. Algunos ejemplos incluyen: control previo al empleo, visita prenatal de rutina, control de salud femenino, evaluación preoperatoria, o control médico anual.</items>
      </items>
      <items code="at0004">
        <items id="text">Problema presentado</items>
        <items id="description">Problema o síntoma reportado por el paciente, que da inicio a la consulta médica</items>
        <items id="comment">Es desable la codificación del 'Problema presentado' mediante una terminología. Motivos clínicos o sociales para buscar atención médica pueden incluir estos problemas, síntomas o signos físicos: deseo de dejar de fumar, violencia doméstica, dolor abdominal, problemas al respirar, alteración del estado de conciencia. En una plantilla, 'Problema principal' puede usarse como sinónimo al 'Problema presentado'.</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Grund für den Kontakt</items>
        <items id="description">Der Grund für die Initiierung eines Arztbesuchs durch den Patienten.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Kontakt Typ</items>
        <items id="description">Identifizierung des Typs oder der Verwaltungskategorie des Gesundheitswesens, der von dem Pflegebedürftigen gesucht oder benötigt wird.</items>
        <items id="comment">Die Kodierung des "Kontakttyps" sollte, wenn möglich, mit einer Terminologie erfolgen. Beispiele hierfür sind: vorbereitende Untersuchungen, routinemäßiger vorgeburtlicher Vorsorgetermin, Gesundheitscheck für Frauen.</items>
      </items>
      <items code="at0004">
        <items id="text">Hauptbeschwerde</items>
        <items id="description">Identifikation des klinischen oder sozialen Problems, welches den Patienten motiviert die medizinische Versorgung aufzusuchen.</items>
        <items id="comment">Die Kodierung der "Problemdarstellung" sollte, wenn möglich, mit einer Terminologie erfolgen. Klinische oder soziale Gründe für das Aufsuchen der Gesundheitsversorgung können u.a. Gesundheitsprobleme, Symptome oder andere körperliche Anzeichen sein. &#xD;
Beispiele: Gesundheitsfragen - Wunsch, mit dem Rauchen aufzuhören, häusliche Gewalt; Symptome - Bauchschmerzen, Kurzatmigkeit; körperliche Zeichen - ein veränderter Bewusstseinszustand. "Hauptbeschwerde" kann als gültiges Synonym für "Problemdarstellung" in den Vorlagen verwendet werden.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Kontaktårsak</items>
        <items id="description">For å registrere årsaken til kontakt mellom helsepersonell og individet.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Administrativ kontaktårsak</items>
        <items id="description">Type eller administrativ kategori av helsetjenester som er årsak til at individet oppsøker eller behøver helsetjenester.</items>
        <items id="comment">Koding av "kontaktårsak" med en terminologi foretrekkes når mulig. Eksempler: Helsesjekk før ansettelse, svangerskapskontroll, gynekologisk undersøkelse, preoperativ undersøkelse eller årlig medisinsk kontroll.</items>
      </items>
      <items code="at0004">
        <items id="text">Klinisk kontaktårsak</items>
        <items id="description">Klinisk eller sosial årsak til at individet oppsøker helsevesenet.</items>
        <items id="comment">Koding av "Klinisk problemstilling" med en terminologi foretrekkes når mulig. Kliniske årsaker kan omfatte helseproblemer, symptomer, eller fysiske sykdomstegn. Eksempler: Helseproblemer - ønske om å slutte å røyke eller vold i hjemmet, symptomer - magesmerter eller kortpusthet, fysiske sykdomstegn - endret bevissthetsnivå. "Hovedproblemstilling" kan bli benyttet som et synonym for "Klinisk kontaktårsak" i templater.</items>
      </items>
    </term_definitions>
    <term_definitions language="ca">
      <items code="at0000">
        <items id="text">Motiu de la visita</items>
        <items id="description">El motiu d'inici de qualsevol trobada o contacte assistencial per part del pacient que és objecte d'atenció.</items>
      </items>
      <items code="at0001">
        <items id="text">Abre</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tipus de contacte</items>
        <items id="description">Identificació del tipus, o categoria administrativa, d'assistència sanitària buscada o requerida pel pacient.</items>
        <items id="comment">És desitjable, quan sigui possible, la codificació del "tipus de contacte" amb una terminologia. Els exemples inclouen: atenció mèdica prèvia a l'ocupació, visita prenatal rutinària, revisió mèdica de la dona, avaluació preoperatòria o revisió mèdica anual.</items>
      </items>
      <items code="at0004">
        <items id="text">El problema està present</items>
        <items id="description">Identificació del problema clínic o social que motiva el subjecte assistencial a la recerca d'atenció sanitària.</items>
        <items id="comment">És desitjable, en la mesura que sigui possible, la codificació del "problema de preparació" amb una terminologia. Les raons clíniques o socials per buscar atenció sanitària poden incloure problemes de salut, símptomes o signes físics. Exemples: problemes de salut - desig de deixar de fumar, violència domèstica; símptomes - dolor abdominal, falta d'alè; signes físics - un estat conscient alterat. «Chief complaint» es pot utilitzar com a sinònim vàlid per a «Presenting problem» a les plantilles.</items>
      </items>
    </term_definitions>
    <term_definitions language="el">
      <items code="at0000">
        <items id="text">Eπαφή Yγειονομικής Περίθαλψης</items>
        <items id="description">Ο λόγος για την έναρξη οποιασδήποτε συνάντησης ή επαφής υγειονομικής περίθαλψης από το άτομο που αποτελεί αντικείμενο φροντίδας.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Τύπος επαφής</items>
        <items id="description">Προσδιορισμός του είδους ή της διοικητικής κατηγορίας της υγειονομικής περίθαλψης που αναζητά ή απαιτεί το υποκείμενο της περίθαλψης.</items>
        <items id="comment">Η κωδικοποίηση του «τύπου επαφής» με ορολογία είναι επιθυμητή, όπου είναι δυνατόν. Παραδείγματα περιλαμβάνουν: ιατρική πριν από την πρόσληψη, προγεννητική επίσκεψη ρουτίνας, έλεγχο υγείας των γυναικών, προεγχειρητική αξιολόγηση ή ετήσιο ιατρικό έλεγχο.</items>
      </items>
      <items code="at0004">
        <items id="text">Παρουσίαση προβλήματος</items>
        <items id="description">Προσδιορισμός του κλινικού ή κοινωνικού προβλήματος που παρακινεί το υποκείμενο της περίθαλψης να αναζητήσει υγειονομική περίθαλψη.</items>
        <items id="comment">Η κωδικοποίηση του «Παρουσιαζόμενου προβλήματος» με μια ορολογία είναι επιθυμητή, όπου είναι δυνατόν. Οι κλινικοί ή κοινωνικοί λόγοι για την αναζήτηση υγειονομικής περίθαλψης μπορεί να περιλαμβάνουν προβλήματα υγείας, συμπτώματα ή σωματικά σημεία. Παραδείγματα: θέματα υγείας - επιθυμία διακοπής του καπνίσματος, ενδοοικογενειακή βία. συμπτώματα - κοιλιακό άλγος, δύσπνοια, φυσικά σημάδια - μια αλλαγμένη συνειδητή κατάσταση. Ο όρος «κύρια καταγγελία» μπορεί να χρησιμοποιηθεί ως έγκυρο συνώνυμο του όρου «παρουσίαση προβλήματος» στα υποδείγματα.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
