<?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-02-20</original_author>
    <original_author id="name">Tony Shannon</original_author>
    <original_author id="organisation">UK NHS, Connecting for Health</original_author>
    <original_author id="email">tony.shannon@nhs.net</original_author>
    <other_contributors>Grethe Almenning, Bergen kommune, Norway</other_contributors>
    <other_contributors>Tomas Alme, DIPS, Norway</other_contributors>
    <other_contributors>Erling Are Hole, Helse Bergen, Norway</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>Rong Chen, Cambio Healthcare Systems, Sweden</other_contributors>
    <other_contributors>Stephen Chu, Queensland Health, Australia</other_contributors>
    <other_contributors>Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway</other_contributors>
    <other_contributors>Arild Faxvaag, NTNU, Norway</other_contributors>
    <other_contributors>Kåre Flø, DIPS ASA, Norway</other_contributors>
    <other_contributors>Einar Fosse, National Centre for Integrated Care and Telemedicine, Norway</other_contributors>
    <other_contributors>Samuel Frade, Marand, Portugal</other_contributors>
    <other_contributors>Sebastian Garde, Ocean Informatics, Germany</other_contributors>
    <other_contributors>Mikkel Gaup Grønmo, FSE, Helse Nord, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Yves Genevier, Privantis SA, Switzerland</other_contributors>
    <other_contributors>Gyri Gradek, Senter for medisinsk genetikk og molekylærmedisin, Haukeland Universitetssykehus, Norway</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Dag Hanoa, Oslo universitetssykehus, Norway</other_contributors>
    <other_contributors>Knut Harboe, Stavanger Universitetssjukehus, Norway</other_contributors>
    <other_contributors>Sam Heard, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Kristian Heldal, Telemark Hospital Trust, Norway</other_contributors>
    <other_contributors>Andreas Hering, Helse Bergen HF, Haukeland universitetssjukehus, Norway</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>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Lars Ivar Mehlum, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Tom Jarl Jakobsen, Helse Bergen, Norway</other_contributors>
    <other_contributors>Hanne Joensen, Helse Bergen HUS, Norway</other_contributors>
    <other_contributors>Gunnar Jårvik, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Lars Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Lars Morgan Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Goran Karlstrom, County Of Värmland, Sweden</other_contributors>
    <other_contributors>Shinji Kobayashi, NPO openEHR Japan, Japan</other_contributors>
    <other_contributors>Nils Kolstrup, Skansen Legekontor og Nasjonalt Senter for samhandling og telemedisin, Norway</other_contributors>
    <other_contributors>Elisabeth Kvile, Fysioterapiavdelingen, Haukeland Universitets Sykehus, Norway</other_contributors>
    <other_contributors>Siri Laronningen, Kreftregisteret, Norway</other_contributors>
    <other_contributors>Sabine Leh, Haukeland University Hospital, Department of Pathology, 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>alberto maldonado, UPV, Spain</other_contributors>
    <other_contributors>Luis Marco Ruiz, Norwegian Center for Integrated Care and Telemedicine, Norway</other_contributors>
    <other_contributors>Siv Marie Lien, DIPS ASA, Norway</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom</other_contributors>
    <other_contributors>Bjoern Naess, DIPS ASA, Norway</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Anne Pauline Anderssen, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>Magne Rekdal, DIPS AS, Norway</other_contributors>
    <other_contributors>Tanja Riise, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil</other_contributors>
    <other_contributors>Thomas Schopf, University Hospital of North-Norway, Norway</other_contributors>
    <other_contributors>Anoop Shah, University College London, United Kingdom</other_contributors>
    <other_contributors>Hildegunn Siv Aase, Helse Bergen, Norway</other_contributors>
    <other_contributors>Arild Stangeland, Helse Bergen, Norway</other_contributors>
    <other_contributors>Norwegian Review Summary, Norwegian Public Hospitals, Norway</other_contributors>
    <other_contributors>Line Sæle, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Line Sørensen, Helse Bergen, Norway</other_contributors>
    <other_contributors>Nils Thomas Songstad, UNN HF, BUK, Barneavdelingen., Norway</other_contributors>
    <other_contributors>Rowan Thomas, St. Vincent's Hospital Melbourne, Australia</other_contributors>
    <other_contributors>Lene Thoresen, St. Olavs Hospital, Norway</other_contributors>
    <other_contributors>Jon Tysdahl, Furst medlab AS, Norway</other_contributors>
    <other_contributors>Till Uhlig, Nasjonal kompetansetjeneste for revmatologisk rehabilitering, Revmatologisk avd. , Diakonhjemmet Sykehus, Oslo, Norway</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway</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">Common Terminology Criteria for Adverse Events (CTCAE) [Internet]. National Cancer Institute, USA. Available from: http://ctep.cancer.gov/protocolDevelopment/electronic_applications/ctc.htm (accessed 2015-07-13).</other_details>
    <other_details id="current_contact">Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com</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">4789CB0E45553BBEB04AC84B4B4DB431</other_details>
    <other_details id="build_uid">087f421e-090e-4181-8ebf-7c16e787621f</other_details>
    <other_details id="ip_acknowledgements">This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyrighted material of the International Health Terminology Standards Development Organisation (IHTSDO). Where an implementation of this artefact makes use of SNOMED CT content, the implementer must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed or info@snomed.org.</other_details>
    <other_details id="revision">2.1.5</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Darstellung von Details über eine einzelne Episode eines berichteten Symptoms oder Krankheitsanzeichens einschließlich des Kontexts. Details zu früheren Episoden sollen, wenn angemessen, nicht aufgeführt werden.</purpose>
      <keywords>Beschwerde</keywords>
      <keywords>Symptom</keywords>
      <keywords>Störung</keywords>
      <keywords>Problem</keywords>
      <keywords>vorlegende Beschwerde</keywords>
      <keywords>vorlegendes Symptom</keywords>
      <keywords>Zeichen</keywords>
      <keywords>Anzeichen</keywords>
      <keywords>Krankheitsanzeichen</keywords>
      <use>Zu Verwenden, um Details über eine einzelne Episode eines Symptoms oder eines berichteten Krankheitsanzeichens einer Person zu dokumentieren, wie es von der Person, dem Elternteil, dem Betreuer oder einer anderen Partei berichtet wurde. Es kann von einem Arzt als Teil einer Krankengeschichte dokumentiert werden, oder wie es dem Arzt berichtet wurde/wie er es beobachtet hat, oder als Teil eines selbst aufgezeichneten klinischen Fragebogens oder einer persönlichen Gesundheitsakte. Eine vollständige Kranken- oder Patientengeschichet kann mehrere Episoden eines identifizierten Symptoms/Krankheitsanzeichens, mit variierendem Detaillierungsgrad, sowie mehrere Symptome/Krankheitsanzeichen beinhalten.&#xD;
&#xD;
Dieser Archetyp wurde entwickelt, um das positive Vorhandensein des Symptoms oder Krankheitsanzeichens als Teil der Anamneseerhebung mit OBSERVATION.story oder in Verbindung mit einer positiven Reaktion auf OBSERVATION.symptom_sign_screening darzustellen.&#xD;
&#xD;
Im reinsten Sinne sind Symptome subjektive Beobachtungen einer körperlichen oder geistigen Störung und Krankheitsanzeichen sind objektive Beobachtungen dieser Störung, wie sie von einer Person erlebt und dem Dokumentierenden von derselben Person oder einer anderen Partei berichtet werden. Aus dieser Logik folgt, dass zwei Archetypen benötigt werden, um die Krankengeschichte aufzuzeichnen - einen für berichtete Symptome und einen weiteren für berichtete Krankheitsanzeichen. Für die Praxis ist dies ungeeignet, da es die Eingabe klinischer Daten in eines der beiden Modelle erfordert, was den Modellierern und denen, die die Daten eingeben, erheblichen Mehraufwand verursacht. Darüber hinaus gibt es oft Überschneidungen von klinischen Konzepten - z.B. ist vorangegangenes Erbrechen oder sind Blutungen als Symptom oder berichtetes Krankheitsanzeichen zu kategorisieren? Als Antwort darauf wurde dieser Archetyp speziell entwickelt, um ein einziges Informationsmodell zu erproben, das es ermöglicht, das gesamte Spektrum von klar identifizierbaren Symptomen bis hin zu berichteten Krankheitsanzeichen bei der Dokumentation einer Krankengeschichte zu erfassen.&#xD;
&#xD;
Dieser Archetyp wurde als generisches Muster für alle Symptome und Krankheitsanzeichen entwickelt. Der Slot "Spezifische Details" kann verwendet werden, um den Archetyp um zusätzliche, spezifische Datenelemente für komplexere Symptome oder Krankheitsanzeichen zu erweitern. &#xD;
&#xD;
Dieser Archetyp wurde speziell für die Verwendung im Slot "Strukturiertes Detail" innerhalb des Archetyps OBSERVATION.story entwickelt, kann aber auch in anderen OBSERVATION- oder CLUSTER-Archetypen und in den Slots "Assoziierte Symptome/Krankheitsanzeichen" oder "Vorangegangene Episoden" in anderen Instanzen dieses CLUSTER.symptom_sign Archetyps verwendet werden.</use>
      <misuse>Den Archetyp nicht verwenden, um Antworten auf Screening-Fragebögen über das Vorhandensein oder Nichtvorhandensein bestimmter Symptome abzufragen – verwenden Sie für diesen Zweck den Archetyp OBSERVATION.symptom_sign_screening. Dieser CLUSTER.symptom_sign kann jedoch im SLOT „Screening-Details“ im Archetyp OBSERVATION.symptom_sign_screening verschachtelt werden, wenn es notwendig ist, den Fragebogen zu erweitern, indem Details zu Symptomen oder Anzeichen aufgezeichnet werden.&#xD;
&#xD;
Den Archetyp nicht verwenden, um darzustellen, dass ein Symptom oder Anzeichen explizit als nicht vorhanden gemeldet wurde – verwenden Sie CLUSTER.exclusion_symptom_sign mit Bedacht für bestimmte Zwecke, bei denen der Overhead der Aufzeichnung auf diese Weise die zusätzliche Komplexität rechtfertigt.&#xD;
&#xD;
Nicht zur Erfassung objektiver Befunde im Rahmen einer körperlichen Untersuchung verwenden - verwenden Sie zu diesem Zweck OBSERVATION.exam und mit Untersuchung verwandte CLUSTER-Archetypen.&#xD;
&#xD;
Nicht für Diagnosen und Probleme, die Teil einer bestehenden Problemliste sind, verwenden - verwenden Sie EVALUATION.problem_diagnosis.&#xD;
&#xD;
Nicht zur Darstellung einer formalen und wiederholbaren Schweregradskala wie VAS oder NRS verwenden. Verwenden Sie zu diesem Zweck geeignete OBSERVATION-Archetypen.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Att dokumentera detaljer för en enskild förekomst av ett symtom eller tecken, inklusive relevanta omständigheter om tidigare förekomster men inga detaljer om dessa.</purpose>
      <keywords>klagomål</keywords>
      <keywords>symptom</keywords>
      <keywords>symtom</keywords>
      <keywords>störning</keywords>
      <keywords>besvär</keywords>
      <keywords>problem</keywords>
      <keywords>obehag</keywords>
      <keywords>tecken</keywords>
      <use>Används för att registrera en enskild episod av ett symtom eller tecken, rapporterat av individen själv eller annan part. Uppgifterna kan registreras av vårdpersonal utifrån det som rapporterats eller observerats, eller av individen själv som en del av egenrapporterad data.&#xD;
&#xD;
Symtom är individens subjektiva upplevelser av fysisk eller psykisk påverkan, medan tecken är objektivt observerbara fynd. Eftersom gränsen mellan rapporterade symtom och tecken ofta är otydlig har denna arketyp utformats för att stödja registrering av hela spektrumet, från tydligt subjektiva symtom till rapporterade eller observerade tecken, i en gemensam informationsmodell.&#xD;
&#xD;
Används generellt för registrera alla symtom och tecken.&#xD;
&#xD;
Används huvudsakligen för att registrera förekomst av ett symtom eller tecken i SLOT "Structured details" i arketypen OBSERVATION.story eller tillsammans med ett svar i OBSERVATION.symptom_sign_screening. Kan även användas i andra OBSERVATION- eller CLUSTER-arketyper.&#xD;
&#xD;
Används i SLOT för "Associerade symtom/tecken" eller "Tidigare episoder" i denna arketyp. Kan vid behov utökas med specifika detaljer i SLOT för "Specifika detaljer", särskilt för mer komplexa symtom eller tecken. Flera instanser kan användas för att beskriva upprepade episoder och varierande detaljnivå i en klinisk berättelse.</use>
      <misuse>Ska inte användas för screeningfrågor, använd istället OBSERVATION.symptom_sign_screening. Dock kan denna arketyp nästlas i SLOT för "additional details" i arketypen OBSERVATION.symptom_sign_screening för att registera detaljer om symtom och tecken.&#xD;
&#xD;
Ska inte användas för att registrera frånvaro av specifika symtom och tecken. Använd istället CLUSTER.exclusion_symptom_sign.&#xD;
&#xD;
Ska inte användas för objektiva fynd vid fysisk undersökning. Använd istället OBSERVATION.exam och relaterade CLUSTER-arketyper.&#xD;
&#xD;
Ska inte användas för diagnoser och problem i kvarstående problemlista. Använd istället EVALUATION.problem_diagnosis.&#xD;
&#xD;
Ska inte användas för standardiserade skattningsskalor (t.ex. VAS, NRS). Använd istället relevant OBSERVATION-arketyp.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fi</code_string>
      </language>
      <purpose>*To record details about a single episode of a reported symptom or sign including context, but not details, of previous episodes if appropriate.(en)</purpose>
      <keywords>*complaint(en)</keywords>
      <keywords>*symptom(en)</keywords>
      <keywords>*disturbance(en)</keywords>
      <keywords>*problem(en)</keywords>
      <keywords>*discomfort(en)</keywords>
      <keywords>*presenting complaint(en)</keywords>
      <keywords>*presenting symptom(en)</keywords>
      <keywords>*sign(en)</keywords>
      <use>*Use to record details about a single episode of a symptom or reported sign in an individual, as reported by the individual, parent, care-giver or other party. It may be recorded by a clinician as part of a clinical history record as reported to them, observed by the clinician or self-recorded as part of a clinical questionnaire or personal health record. A complete clinical history or patient story may include varying level of details about multiple episodes of an identified symptom or reported sign, as well as multiple symptoms/signs.&#xD;
&#xD;
This archetype has been designed to record the positive presence of the symptom or sign as part of history taking using OBSERVATION.story, or in conjunction with a positive response to OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
In the purest sense, symptoms are subjective observations of a physical or mental disturbance and signs are objective observations of the same, as experienced by an individual and reported to the history taker by the same individual or another party. From this logic it follows that we will need two archetypes to record clinical history - one for reported symptoms and another for reported signs. In reality this is impractical as it will require clinical data entry into either one of these models which adds signficant overheads to modellers and those entering data. In addition, there is often overlap in clinical concepts - for example, is previous vomiting or bleeding to be categorised as a symptom or reported sign? In response, this archetype has been specifically designed to provide a single information model that allows for recording of the entire continuum between clearly identifiable symptoms and reported signs.&#xD;
&#xD;
This archetype has been intended to be used as a generic pattern for all symptoms and reported signs. The 'Specific details' SLOT can be used to extend the archetype to include additional, specific data elements for more complex symptoms or signs. &#xD;
&#xD;
This archetype has been specifically designed to be used in the 'Structured detail' SLOT within the OBSERVATION.story archetype, but can also be used within other OBSERVATION or CLUSTER archetypes and in the 'Associated symptom/sign' or 'Previous episode' SLOT within other instances of this CLUSTER.symptom_sign archetype. (en)</use>
      <misuse>*Not to be used to record screening questionnaire responses about the presence or absence of specific symptoms - use the OBSERVATION.symptom_sign_screening archetype for this purpose. However, this CLUSTER.symptom_sign archetype may be nested within the 'Screening details' SLOT in the OBSERVATION.symptom_sign_screening archetype if it is necessary to extend the questionnaire by recording details about symptom or sign.&#xD;
&#xD;
Not to be used to record that a symptom or sign was explicitly reported as not present - use CLUSTER.exclusion_symptom_sign carefully for specific purposes where the overheads of recording in this way warrant the additional complexity.&#xD;
&#xD;
Not to be used for recording objective findings as part of a physical examination - use OBSERVATION.exam and related examination CLUSTER archetypes for this purpose.&#xD;
&#xD;
Not to be used for diagnoses and problems that form part of a persisting Problem List - use EVALUATION.problem_diagnosis.&#xD;
&#xD;
Not to be used to record a formal and repeatable severity scale such as VAS or NRS. Use appropriate OBSERVATION archetypes for this purpose. (en)</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 enkeltepisode av et rapportert symptom eller sykdomstegn. Dette kan omfatte kontekst, men ikke detaljer, om tidligere episoder av symptomet/sykdomstegnet.</purpose>
      <keywords>lidelse</keywords>
      <keywords>plage</keywords>
      <keywords>problem</keywords>
      <keywords>ubehag</keywords>
      <keywords>symptom</keywords>
      <keywords>sykdomstegn</keywords>
      <keywords>lyte</keywords>
      <keywords>skavank</keywords>
      <use>For å registrere detaljer om en enkeltepisode av et rapportert symptom eller sykdomstegn hos et individ, som redegjort av personen selv, foreldre, omsorgsperson eller andre parter. Registrering kan skje i forbindelse med opptak av anamnese, eller som en selvregistrering som en del av et klinisk spørreskjema eller personlig journal. En fullstendig klinisk anamnese eller pasientanamnese kan inneholde beskrivelser med ulikt detaljnivå om flere episoder knyttet til samme symptom eller sykdomstegn, og vil også kunne inneholde flere ulike symptomer eller sykdomstegn.&#xD;
&#xD;
Denne arketypen er laget for å registrere positiv tilstedeværelse av et symptom eller sykdomstegn som en del av anamneseopptak ved å bruke OBSERVATION.story-arketypen, eller i sammenheng med et positivt svar i arketypen OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
I egentlig forstand er symptomer subjektive opplevelser av en fysisk eller mental forstyrrelse mens sykdomstegn er objektive observasjoner av det samme, som er erfart av et individ og rapportert til en kliniker av individet eller av andre. Fra denne logikken følger at det burde være to arketyper til å registrere klinisk anamnese; en for rapporterte symptomer og en for rapporterte sykdomstegn. I virkeligheten er dette upraktisk og vil kreve registrering av kliniske data i enten den ene eller den andre av disse modellene. I praksis vil dette øke kompleksitet og tidsbruk knyttet til modellering og registrering av data. I tillegg overlapper ofte de kliniske konseptene, for eksempel: Vil tidligere oppkast eller blødning kategoriseres som et symptom eller som et rapportert sykdomstegn?&#xD;
Som svar på dette er arketypen laget for å tillate registrering av hele kontinuumet mellom tydelig definerte symptomer og rapporterte sykdomstegn.&#xD;
&#xD;
Arketypen er designet for å gi et generisk rammeverk for alle symptomer og rapporterte sykdomstegn. SLOTet "Spesifikke detaljer" kan brukes for å utvide arketypen med ytterligere spesifikke dataelementer for komplekse symptomer eller sykdomstegn.&#xD;
&#xD;
Arketypen skal settes inn i "Detaljer"-SLOTet i OBSERVATION.story-arketypen men kan også brukes i en hvilken som helst OBSERVATION eller CLUSTER-arketype. Arketypen kan også gjenbrukes i andre instanser av CLUSTER.symptom_sign-arketypen i SLOTene "Assosierte symptomer" eller "Tidligere detaljer".</use>
      <misuse>Brukes ikke for å registrere spørreskjema-spørsmål om tilstedeværelsen eller fraværet av spesifikke symptomer eller sykdomstegn. Bruk OBSERVATION.symptom_sign_screening til dette formålet. Imidlertid kan denne CLUSTER.symptom_sign arketypen brukes i SLOTet "Ytterligere detaljer" i OBSERVATION.symptom_sign_screening dersom man ønsker å utvide spørreskjemaet med detaljer om et symptom eller sykdomstegn.&#xD;
&#xD;
Brukes ikke til eksplisitt registrering av at et symptom eller sykdomstegn ikke er tilstede. Bruk CLUSTER.exclusion_symptom_sign varsomt da det øker tidsbruk ved registrering og tilfører økt kompleksitet.&#xD;
&#xD;
Brukes ikke til registrering av objektive funn som en del av en fysisk undersøkelse. Bruk OBSERVATION.exam og relaterte CLUSTER.exam-arketyper for dette formålet.&#xD;
&#xD;
Brukes ikke til registrering av problemer og diagnoser som en del av en persistent problemliste, til dette brukes EVALUATION.problem_diagnosis.&#xD;
&#xD;
Brukes ikke til å registrere en formell og repeterbar alvorlighetsgradering som VAS eller NRS. Bruk passende OBSERVATION-arketyper til dette formålet.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Registrar detalhes sobre um episódio único de um sinal ou sintoma relatado incluindo contexto, mas não detalhes, de episódios prévios se apropriado.</purpose>
      <keywords>queixa</keywords>
      <keywords>sintoma</keywords>
      <keywords>distúrbio</keywords>
      <keywords>problema</keywords>
      <keywords>desconforto</keywords>
      <keywords>queixa atual</keywords>
      <keywords>sintoma atual</keywords>
      <keywords>sinal</keywords>
      <use>*Use to record details about a single episode of a symptom or reported sign in an individual, as reported by the individual, parent, care-giver or other party. It may be recorded by a clinician as part of a clinical history record as reported to them, observed by the clinician or self-recorded as part of a clinical questionnaire or personal health record. A complete clinical history or patient story may include varying level of details about multiple episodes of an identified symptom or reported sign, as well as multiple symptoms/signs.&#xD;
&#xD;
This archetype has been designed to record the positive presence of the symptom or sign as part of history taking using OBSERVATION.story, or in conjunction with a positive response to OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
In the purest sense, symptoms are subjective observations of a physical or mental disturbance and signs are objective observations of the same, as experienced by an individual and reported to the history taker by the same individual or another party. From this logic it follows that we will need two archetypes to record clinical history - one for reported symptoms and another for reported signs. In reality this is impractical as it will require clinical data entry into either one of these models which adds signficant overheads to modellers and those entering data. In addition, there is often overlap in clinical concepts - for example, is previous vomiting or bleeding to be categorised as a symptom or reported sign? In response, this archetype has been specifically designed to provide a single information model that allows for recording of the entire continuum between clearly identifiable symptoms and reported signs.&#xD;
&#xD;
This archetype has been intended to be used as a generic pattern for all symptoms and reported signs. The 'Specific details' SLOT can be used to extend the archetype to include additional, specific data elements for more complex symptoms or signs. &#xD;
&#xD;
This archetype has been specifically designed to be used in the 'Structured detail' SLOT within the OBSERVATION.story archetype, but can also be used within other OBSERVATION or CLUSTER archetypes and in the 'Associated symptom/sign' or 'Previous episode' SLOT within other instances of this CLUSTER.symptom_sign archetype. (en)</use>
      <misuse>*Not to be used to record screening questionnaire responses about the presence or absence of specific symptoms - use the OBSERVATION.symptom_sign_screening archetype for this purpose. However, this CLUSTER.symptom_sign archetype may be nested within the 'Screening details' SLOT in the OBSERVATION.symptom_sign_screening archetype if it is necessary to extend the questionnaire by recording details about symptom or sign.&#xD;
&#xD;
Not to be used to record that a symptom or sign was explicitly reported as not present - use CLUSTER.exclusion_symptom_sign carefully for specific purposes where the overheads of recording in this way warrant the additional complexity.&#xD;
&#xD;
Not to be used for recording objective findings as part of a physical examination - use OBSERVATION.exam and related examination CLUSTER archetypes for this purpose.&#xD;
&#xD;
Not to be used for diagnoses and problems that form part of a persisting Problem List - use EVALUATION.problem_diagnosis.&#xD;
&#xD;
Not to be used to record a formal and repeatable severity scale such as VAS or NRS. Use appropriate OBSERVATION archetypes for this purpose. (en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ja</code_string>
      </language>
      <purpose>報告された症状または徴候の単一のエピソードについて詳細に記録するため。必要に応じて過去のエピソードの（詳細ではない）文脈を含める。</purpose>
      <keywords>訴え</keywords>
      <keywords>症状</keywords>
      <keywords>変調</keywords>
      <keywords>プロブレム</keywords>
      <keywords>不快</keywords>
      <keywords>主訴</keywords>
      <keywords>受診時の症状</keywords>
      <keywords>徴候</keywords>
      <keywords>症候</keywords>
      <keywords>自覚症状</keywords>
      <use>本人、親、介護者、その他の関係者から報告された症状や徴候について、単一のエピソードを詳細に記録するために用いる。医療従事者が聴取した内容や自ら観察した内容を病歴として記録する場合にも、本人が問診票や個人健康記録に記入する場合にも使用できる。病歴全体や患者の語りには、複数の異なる症状・徴候だけでなく、同じ症状・徴候に関する複数のエピソードが含まれることがあり、それぞれの記述の詳しさも異なる。&#xD;
&#xD;
本archetypeは、症状や徴候がある場合に、その内容を詳しく記録するために設計されている。OBSERVATION.storyを用いた病歴聴取の一部として、またはOBSERVATION.symptom_sign_screeningでの「症状・徴候あり」という回答と組み合わせて使用する。&#xD;
&#xD;
厳密には、症状は心身の変調に関する主観的な観察に基づくものであり、徴候は客観的な観察に基づくものである。いずれも本人が経験したこととして、本人または他者から病歴の聴取者に伝えられる。この区別に従えば、病歴の記録には、報告された症状を記録するarchetypeと、報告された徴候を記録するarchetypeの二つが必要になる。しかし、実際には、臨床データをどちらのモデルに入力するかを判断して使い分けなければならず、モデルの設計者とデータの入力者の双方に大きな負担が生じるため、現実的ではない。また、症状と徴候には、明確に区別しにくい臨床概念もある。例えば、過去に起きた嘔吐や出血は、症状と報告された徴候のどちらに分類すべきだろうか。そこで本archetypeは、明らかな症状から報告された徴候まで、両者の境界に位置するものも含めて、一つの情報モデルで記録できるように設計されている。&#xD;
&#xD;
本archetypeは、あらゆる症状や報告された徴候を記録するための汎用的なモデルとして用いることを想定している。より複雑な症状や徴候を扱う場合には、「詳細記録」SLOTを用いて、それぞれに特有のデータエレメントを追加し、archetypeを拡張できる。 &#xD;
&#xD;
本archetypeは、OBSERVATION.story archetypeの「構造化された詳細記録」SLOTで使用することを想定して設計されている。他のOBSERVATIONやCLUSTER archetype内でも使用でき、同じCLUSTER.symptom_sign archetypeの別のインスタンスにある「随伴症状・徴候」SLOTや「過去のエピソード」SLOTにも組み込むことができる。</use>
      <misuse>特定の症状の有無を尋ねるスクリーニング問診票への回答は、本archetypeではなく、OBSERVATION.symptom_sign_screening archetypeを用いて記録する。ただし、症状や徴候について詳しく記録できるように問診票を拡張する必要がある場合には、OBSERVATION.symptom_sign_screening archetypeの「スクリーニングの詳細」SLOTに、本CLUSTER.symptom_sign archetypeを組み込むことができる。&#xD;
&#xD;
症状や徴候がないと明確に伝えられたことを記録する場合には、本archetypeではなく、CLUSTER.exclusion_symptom_signを用いる。ただし、記録の負担や複雑さが増すことを考慮し、それに見合う必要性がある用途に限って慎重に使用する。&#xD;
&#xD;
身体診察で得られた客観的所見は、本archetypeではなく、OBSERVATION.examと関連する診察用のCLUSTER archetypeを用いて記録する。&#xD;
&#xD;
継続的に管理するプロブレムリストに含まれる診断やプロブレムは、本archetypeではなく、EVALUATION.problem_diagnosisを用いて記録する。&#xD;
&#xD;
VASやNRSなど、所定の方法で繰り返し評価できる重症度尺度による評価結果は、本archetypeではなく、適切なOBSERVATION archetypeを用いて記録する。</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 single episode of a reported symptom or sign including context, but not details, of previous episodes if appropriate.</purpose>
      <keywords>complaint</keywords>
      <keywords>symptom</keywords>
      <keywords>disturbance</keywords>
      <keywords>problem</keywords>
      <keywords>discomfort</keywords>
      <keywords>presenting complaint</keywords>
      <keywords>presenting symptom</keywords>
      <keywords>sign</keywords>
      <use>Use to record details about a single episode of a symptom or reported sign in an individual, as reported by the individual, parent, care-giver or other party. It may be recorded by a clinician as part of a clinical history record as reported to them, observed by the clinician or self-recorded as part of a clinical questionnaire or personal health record. A complete clinical history or patient story may include varying level of details about multiple episodes of an identified symptom or reported sign, as well as multiple symptoms/signs.&#xD;
&#xD;
This archetype has been designed to record the positive presence of the symptom or sign as part of history taking using OBSERVATION.story, or in conjunction with a positive response to OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
In the purest sense, symptoms are subjective observations of a physical or mental disturbance and signs are objective observations of the same, as experienced by an individual and reported to the history taker by the same individual or another party. From this logic it follows that we will need two archetypes to record clinical history - one for reported symptoms and another for reported signs. In reality this is impractical as it will require clinical data entry into either one of these models which adds signficant overheads to modellers and those entering data. In addition, there is often overlap in clinical concepts - for example, is previous vomiting or bleeding to be categorised as a symptom or reported sign? In response, this archetype has been specifically designed to provide a single information model that allows for recording of the entire continuum between clearly identifiable symptoms and reported signs.&#xD;
&#xD;
This archetype has been intended to be used as a generic pattern for all symptoms and reported signs. The 'Specific details' SLOT can be used to extend the archetype to include additional, specific data elements for more complex symptoms or signs. &#xD;
&#xD;
This archetype has been specifically designed to be used in the 'Structured detail' SLOT within the OBSERVATION.story archetype, but can also be used within other OBSERVATION or CLUSTER archetypes and in the 'Associated symptom/sign' or 'Previous episode' SLOT within other instances of this CLUSTER.symptom_sign archetype.</use>
      <misuse>Not to be used to record screening questionnaire responses about the presence or absence of specific symptoms - use the OBSERVATION.symptom_sign_screening archetype for this purpose. However, this CLUSTER.symptom_sign archetype may be nested within the 'Screening details' SLOT in the OBSERVATION.symptom_sign_screening archetype if it is necessary to extend the questionnaire by recording details about symptom or sign.&#xD;
&#xD;
Not to be used to record that a symptom or sign was explicitly reported as not present - use CLUSTER.exclusion_symptom_sign carefully for specific purposes where the overheads of recording in this way warrant the additional complexity.&#xD;
&#xD;
Not to be used for recording objective findings as part of a physical examination - use OBSERVATION.exam and related examination CLUSTER archetypes for this purpose.&#xD;
&#xD;
Not to be used for diagnoses and problems that form part of a persisting Problem List - use EVALUATION.problem_diagnosis.&#xD;
&#xD;
Not to be used to record a formal and repeatable severity scale such as VAS or NRS. Use appropriate OBSERVATION archetypes for this purpose.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ar-sy</code_string>
      </language>
      <purpose>*To record detail about a symptom - either self-recorded by an individual or recorded on the behalf of a patient by a clinician. A complete patient history may include varying level of details about a variety of symptoms.(en)</purpose>
      <use>*Use to record details about a single episode of a symptom or reported sign in an individual, as reported by the individual, parent, care-giver or other party. It may be recorded by a clinician as part of a clinical history record as reported to them, observed by the clinician or self-recorded as part of a clinical questionnaire or personal health record. A complete clinical history or patient story may include varying level of details about multiple episodes of an identified symptom or reported sign, as well as multiple symptoms/signs.&#xD;
&#xD;
This archetype has been designed to record the positive presence of the symptom or sign as part of history taking using OBSERVATION.story, or in conjunction with a positive response to OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
In the purest sense, symptoms are subjective observations of a physical or mental disturbance and signs are objective observations of the same, as experienced by an individual and reported to the history taker by the same individual or another party. From this logic it follows that we will need two archetypes to record clinical history - one for reported symptoms and another for reported signs. In reality this is impractical as it will require clinical data entry into either one of these models which adds signficant overheads to modellers and those entering data. In addition, there is often overlap in clinical concepts - for example, is previous vomiting or bleeding to be categorised as a symptom or reported sign? In response, this archetype has been specifically designed to provide a single information model that allows for recording of the entire continuum between clearly identifiable symptoms and reported signs.&#xD;
&#xD;
This archetype has been intended to be used as a generic pattern for all symptoms and reported signs. The 'Specific details' SLOT can be used to extend the archetype to include additional, specific data elements for more complex symptoms or signs. &#xD;
&#xD;
This archetype has been specifically designed to be used in the 'Structured detail' SLOT within the OBSERVATION.story archetype, but can also be used within other OBSERVATION or CLUSTER archetypes and in the 'Associated symptom/sign' or 'Previous episode' SLOT within other instances of this CLUSTER.symptom_sign archetype. (en)</use>
      <misuse>*Not to be used to record screening questionnaire responses about the presence or absence of specific symptoms - use the OBSERVATION.symptom_sign_screening archetype for this purpose. However, this CLUSTER.symptom_sign archetype may be nested within the 'Screening details' SLOT in the OBSERVATION.symptom_sign_screening archetype if it is necessary to extend the questionnaire by recording details about symptom or sign.&#xD;
&#xD;
Not to be used to record that a symptom or sign was explicitly reported as not present - use CLUSTER.exclusion_symptom_sign carefully for specific purposes where the overheads of recording in this way warrant the additional complexity.&#xD;
&#xD;
Not to be used for recording objective findings as part of a physical examination - use OBSERVATION.exam and related examination CLUSTER archetypes for this purpose.&#xD;
&#xD;
Not to be used for diagnoses and problems that form part of a persisting Problem List - use EVALUATION.problem_diagnosis.&#xD;
&#xD;
Not to be used to record a formal and repeatable severity scale such as VAS or NRS. Use appropriate OBSERVATION archetypes for this purpose. (en)</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nl</code_string>
      </language>
      <purpose>*To record details about a single episode of a reported symptom or sign including context, but not details, of previous episodes if appropriate.(en)</purpose>
      <keywords>*complaint(en)</keywords>
      <keywords>*symptom(en)</keywords>
      <keywords>*disturbance(en)</keywords>
      <keywords>*problem(en)</keywords>
      <keywords>*discomfort(en)</keywords>
      <keywords>*presenting complaint(en)</keywords>
      <keywords>*presenting symptom(en)</keywords>
      <keywords>*sign(en)</keywords>
      <use>*Use to record details about a single episode of a symptom or reported sign in an individual, as reported by the individual, parent, care-giver or other party. It may be recorded by a clinician as part of a clinical history record as reported to them, observed by the clinician or self-recorded as part of a clinical questionnaire or personal health record. A complete clinical history or patient story may include varying level of details about multiple episodes of an identified symptom or reported sign, as well as multiple symptoms/signs.&#xD;
&#xD;
This archetype has been designed to record the positive presence of the symptom or sign as part of history taking using OBSERVATION.story, or in conjunction with a positive response to OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
In the purest sense, symptoms are subjective observations of a physical or mental disturbance and signs are objective observations of the same, as experienced by an individual and reported to the history taker by the same individual or another party. From this logic it follows that we will need two archetypes to record clinical history - one for reported symptoms and another for reported signs. In reality this is impractical as it will require clinical data entry into either one of these models which adds signficant overheads to modellers and those entering data. In addition, there is often overlap in clinical concepts - for example, is previous vomiting or bleeding to be categorised as a symptom or reported sign? In response, this archetype has been specifically designed to provide a single information model that allows for recording of the entire continuum between clearly identifiable symptoms and reported signs.&#xD;
&#xD;
This archetype has been intended to be used as a generic pattern for all symptoms and reported signs. The 'Specific details' SLOT can be used to extend the archetype to include additional, specific data elements for more complex symptoms or signs. &#xD;
&#xD;
This archetype has been specifically designed to be used in the 'Structured detail' SLOT within the OBSERVATION.story archetype, but can also be used within other OBSERVATION or CLUSTER archetypes and in the 'Associated symptom/sign' or 'Previous episode' SLOT within other instances of this CLUSTER.symptom_sign archetype.(en)</use>
      <misuse>*Not to be used to record screening questionnaire responses about the presence or absence of specific symptoms - use the OBSERVATION.symptom_sign_screening archetype for this purpose. However, this CLUSTER.symptom_sign archetype may be nested within the 'Screening details' SLOT in the OBSERVATION.symptom_sign_screening archetype if it is necessary to extend the questionnaire by recording details about symptom or sign.&#xD;
&#xD;
Not to be used to record that a symptom or sign was explicitly reported as not present - use CLUSTER.exclusion_symptom_sign carefully for specific purposes where the overheads of recording in this way warrant the additional complexity.&#xD;
&#xD;
Not to be used for recording objective findings as part of a physical examination - use OBSERVATION.exam and related examination CLUSTER archetypes for this purpose.&#xD;
&#xD;
Not to be used for diagnoses and problems that form part of a persisting Problem List - use EVALUATION.problem_diagnosis.&#xD;
&#xD;
Not to be used to record a formal and repeatable severity scale such as VAS or NRS. Use appropriate OBSERVATION archetypes for this purpose.(en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ca</code_string>
      </language>
      <purpose>Registrar dades sobre un únic episodi d’un símptoma o signe notificat, incloent-hi el context, però no les dades, d’episodis anteriors si fos necessari.</purpose>
      <keywords>malaltia</keywords>
      <keywords>símptoma</keywords>
      <keywords>alteració</keywords>
      <keywords>problema</keywords>
      <keywords>malestar</keywords>
      <keywords>motiu de consulta</keywords>
      <keywords>símptoma de presentació</keywords>
      <keywords>signe</keywords>
      <use>Informació rebuda del pacient, el progenitor, cuidador o un tercer. Utilitzar per a registrar dades sobre un únic episodi d’un símptoma o signe notificat en un pacient. El pot registrar un metge com a part d’un registre d’història clínica com se’ls ha informat, observat pel metge o autodiagnosticat com a part d’un qüestionari clínic o història clínica personal. Una història clínica o història del pacient completa pot incloure diversos nivells de detalls sobre episodis múltiples d’un símptoma identificat o signe notificat, així com múltiples símptomes/signes.&#xD;
&#xD;
Aquest arquetip s’ha dissenyat per a registrar la presència positiva del símptoma o signe com a part de l’anamnesi utilitzant OVSERVATION.story o conjuntament amb una resposta positiva a OBSERVATION.symptom_sign_screening.&#xD;
&#xD;
En el sentit més pur, els símptomes són observacions subjectives d’una alteració física o mental i els signes són observacions objectives de la mateixa cosa, que experimenta un pacient i que es comunica a l’encarregat de la història per part de la mateixa persona o d’un tercer. D’aquesta lògica es pot deduir que faran falta dos arquetips per a registrar la història clínica – un per a símptomes notificats i l’altre per a signes notificats. En la pràctica, fer això és poc pràctic, ja que es requerirà que s’introdueixin dades clíniques en qualsevol d’aquests models, la qual cosa afegeix una càrrega significativa als modeladors i a aquells encarregats d’introduir dades. Addicionalment, els conceptes clínics sovint es superposen – per exemple, es classifica el vòmit o la sagnia prèvia com a símptoma o com a signe notificat? En resposta, aquest arquetip s’ha dissenyat específicament per a proveir un únic model d’informació que permet que es registri tot l’espectre que es troba entre els símptomes clarament identificables i els signes notificats.&#xD;
&#xD;
Es pretén que aquest arquetip s’utilitzi com un patró genèric per a tots els símptomes i signes notificats. El SLOT «Dades específiques» es pot utilitzar per ampliar l’arquetip perquè aquest inclogui elements de dades específics addicionals per a símptomes o signes més complexos.&#xD;
&#xD;
Aquest arquetip s’ha dissenyat específicament perquè s’utilitzi dins del SLOT «Dades estructurades», que es troba dins de l’arquetip OBSERVATION.story, però també es pot utilitzar dins d’altres arquetips de tipus OBSERVATION o CLUSTER, així com dins del SLOT «Símptoma/signe associat» o «Episodi previ» dins d’altres exemples d’aquest CLUSTER.symptom_sign archetype.</use>
      <misuse>No utilitzar per a registrar respostes d’un qüestionari de cribratge sobre la presència o absència de símptomes específics – utilitzar l’arquetip OBSERVATION.symptom_sign_screening per aquest objectiu. No obstant això, aquest arquetip CLUSTER.symptom_sign es pot situar dins del SLOT «Dades de cribratge» de l’arquetip OBSERVATION.symptom_sign_screening si és necessari ampliar el qüestionari mitjançant el registre de dades sobre símptomes o signes.&#xD;
&#xD;
No utilitzar per a registrar que un símptoma o signe es notificà explícitament com absent – utilitzar CLUSTER.exclusion_symptom_sign per a finalitats específiques amb compte quan la càrrega de registrar d’aquesta manera justifiqui la complexitat addicional.&#xD;
&#xD;
No utilitzar per a registrar observacions objectives com a part d’un examen físic – utilitzar OBSERVATION.exam i arquetips d’examen de tipus CLUSTER relacionats per aquest objectiu.&#xD;
&#xD;
No utilitzar per a diagnosis i problemes que formen part d’una Llista de Problemes persistent – utilitzar EVALUATION.problem_diagnosis.&#xD;
&#xD;
No utilitzar per a registrar una escala de gravetat formal i repetible com l’EVA (Escala Visual Analògica) o l’Escala Numèrica del Dolor (NRS, per les sigles en anglès). Utilitzar arquetips de tipus OBSERVATION adequats per aquest objectiu.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Sebastian Garde, Kim Sommer, Natalia Strauch, Alina Rehberg</author>
    <author id="organisation">University of Heidelberg, Central Queensland University, 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>fi</code_string>
    </language>
    <author id="name">Kalle Vuorinen</author>
    <author id="organisation">Tieto Healthcare &amp; Welfare Oy</author>
    <author id="email">kalle.vuorinen@tieto.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Kirsi Poikela; Erik Sundvall, Jörgen Kuylenstierna, Åsa Skagerhult, Per Nemirovski, Manna Vosta</author>
    <author id="organisation">Tieto Sweden AB; Karolinska Institutet, Karolinska University Hospital, Region Stockholm + Linköping University, Karolinska Institutet + Karolinska University Hospital, Region Stockholm + Linköping University, eWeave AB, Region Östergötland + Region Uppsala, B3 HealthTech, Västra Götalandsregionen</author>
    <author id="email">ext.kirsi.poikela@tieto.com, erik.sundvall@regionstockholm.se, jorgen.kuylenstierna@solvikshalsan.se, asa.skagerhult@regionostergotland.se, per.pertoft.nemirovski@regionuppsala.se, per.nemirovski@b3.se, manna.vosta@regionstockholm.se, asa.skagerhult@vgregion.se</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, Silje Ljosland Bakke, John Tore Valand, Kanika Kuwelker</author>
    <author id="organisation">Haukeland University Hospital of Bergen, Norway, Helse Vest IKT AS</author>
    <author id="email">lbla@helse-bergen.no, silje.ljosland.bakke@helse-vest-ikt.no, john.tore.valand@helse-vest-ikt.no, kanika.kuwelker@helse-vest-ikt.no</author>
    <accreditation>MD, DEAA, MBA, spec in anesthesia, spec in tropical medicine.</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-br</code_string>
    </language>
    <author id="name">Vladimir Pizzo</author>
    <author id="organisation">Hospital Sirio Libanes - Brazil</author>
    <author id="email">vladimir.pizzo@hsl.org.br</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ja</code_string>
    </language>
    <author id="name">Shinji KOBAYASHI</author>
    <author id="organisation">NPO openEHR Japan</author>
    <author id="email">skoba@moss.gr.jp</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ar-sy</code_string>
    </language>
    <author id="name">Mona Saleh</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nl</code_string>
    </language>
    <author id="name">Joost Holslag</author>
    <author id="organisation">Nedap, Joost Holslag Geneeskunde &amp; Advies</author>
    <author id="email">joost.holslag@nedap.com, info@joostholslag.nl</author>
    <accreditation>MD</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ca</code_string>
    </language>
    <author id="name">Manuel José Zafra Doménech</author>
    <author id="organisation">TRADCREA, S.L.</author>
    <author id="email">mzafra@tradcrea.com</author>
    <other_details id="other_contributors">Servei Català de la Salut</other_details>
  </translations>
  <uid>
    <value>88c7d677-fa69-498f-aec2-976c53d15a6f</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-CLUSTER.symptom_sign.v2</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>1</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>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0151</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>at0147</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_circle(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v2/}</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\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_circle(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v2</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
        <excludes>
          <string_expression>archetype_id/value matches {/.*/}</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>.*</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </excludes>
      </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>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>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0175</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_CODED_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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</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_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</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 />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0176</code_list>
                <code_list>at0178</code_list>
                <code_list>at0177</code_list>
              </children>
            </attributes>
          </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>at0186</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_CODED_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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</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_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</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 />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0187</code_list>
                <code_list>at0188</code_list>
              </children>
            </attributes>
          </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>at0152</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_DATE_TIME</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_INTERVAL&lt;DV_DATE_TIME&gt;</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>at0164</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>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_DURATION</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_INTERVAL&lt;DV_DURATION&gt;</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>at0200</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_DATE_TIME</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>at0028</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_DURATION</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 />
            <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>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_PRIMITIVE_OBJECT">
                <rm_type_name>DV_DURATION</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 />
                <item xsi:type="C_DURATION">
                  <range>
                    <lower_included>true</lower_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>true</upper_unbounded>
                    <lower>PT0S</lower>
                  </range>
                </item>
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_INTERVAL&lt;DV_DURATION&gt;</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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>lower</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_DURATION</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 />
                <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>1</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_PRIMITIVE_OBJECT">
                    <rm_type_name>DV_DURATION</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 />
                    <item xsi:type="C_DURATION">
                      <range>
                        <lower_included>true</lower_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>true</upper_unbounded>
                        <lower>PT0S</lower>
                      </range>
                    </item>
                  </children>
                </attributes>
              </children>
            </attributes>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>upper</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_DURATION</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 />
                <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>1</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_PRIMITIVE_OBJECT">
                    <rm_type_name>DV_DURATION</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 />
                    <item xsi:type="C_DURATION">
                      <range>
                        <lower_included>true</lower_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>true</upper_unbounded>
                        <lower>PT0S</lower>
                      </range>
                    </item>
                  </children>
                </attributes>
              </children>
            </attributes>
          </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>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0021</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_CODED_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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</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_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</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 />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0023</code_list>
                <code_list>at0024</code_list>
                <code_list>at0025</code_list>
              </children>
            </attributes>
          </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="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>at0198</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.severity_rating_scale(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.severity_rating_scale(-[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\.severity_rating_scale(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.severity_rating_scale(-[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>at0189</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>at0180</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_CODED_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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</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_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</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 />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0183</code_list>
                <code_list>at0182</code_list>
                <code_list>at0181</code_list>
                <code_list>at0184</code_list>
              </children>
            </attributes>
          </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>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </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_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>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>at0018</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>at0019</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>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0197</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.health_event(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2/}</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\.health_event(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2</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>at0017</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_CODED_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 />
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>defining_code</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_CODE_PHRASE">
                    <rm_type_name>CODE_PHRASE</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 />
                    <terminology_id>
                      <value>local</value>
                    </terminology_id>
                    <code_list>at0159</code_list>
                    <code_list>at0156</code_list>
                    <code_list>at0158</code_list>
                  </children>
                </attributes>
              </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>at0056</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>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <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>at0165</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>at0170</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>at0154</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.health_event(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2/}</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\.health_event(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2</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>at0171</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_DURATION</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>at0185</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>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <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>at0190</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>at0193</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>at0194</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.health_event(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2/}</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\.health_event(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2</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>at0195</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_DURATION</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>at0196</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>
      </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>at0155</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>at0037</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>at0153</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/.*/}</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>.*</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>at0161</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_DATE_TIME</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>at0057</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>at0031</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_COUNT</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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>magnitude</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_PRIMITIVE_OBJECT">
                <rm_type_name>INTEGER</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 />
                <item xsi:type="C_INTEGER">
                  <range>
                    <lower_included>true</lower_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>true</upper_unbounded>
                    <lower>0</lower>
                  </range>
                </item>
              </children>
            </attributes>
          </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>at0146</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2/}</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\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2</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>at0063</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2/}</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\.symptom_sign(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.symptom_sign(-[a-zA-Z0-9_]+)*\.v2</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>at0163</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="ar-sy">
      <items code="at0000">
        <items id="text">*Symptom/Sign(en)</items>
        <items id="description">*Reported observation of a physical or mental disturbance in an individual.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">*Symptom/Sign name(en)</items>
        <items id="description">*The name of the reported symptom or sign.(en)</items>
        <items id="comment">*Symptom name should be coded with a terminology, where possible.(en)</items>
      </items>
      <items code="at0002">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the reported symptom or sign.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">*Pattern(en)</items>
        <items id="description">*Narrative description about the pattern of the symptom or sign during this episode.(en)</items>
        <items id="comment">*For example: pain could be described as constant or colicky.(en)</items>
      </items>
      <items code="at0017">
        <items id="text">*Effect(en)</items>
        <items id="description">*Perceived effect of the modifying factor on the symptom or sign.(en)</items>
      </items>
      <items code="at0018">
        <items id="text">*Modifying factor(en)</items>
        <items id="description">*Detail about how a specific factor effects the identified symptom or sign during this episode.(en)</items>
      </items>
      <items code="at0019">
        <items id="text">*Factor(en)</items>
        <items id="description">*Name of the modifying factor.(en)</items>
        <items id="comment">*Examples of modifying factor: lying on multiple pillows, eating or administration of a specific medication.(en)</items>
      </items>
      <items code="at0021">
        <items id="text">*Severity category(en)</items>
        <items id="description">*Category representing the overall severity of the symptom or sign.(en)</items>
        <items id="comment">*Defining values such as mild, moderate or severe in such a way that is applicable to multiple symptoms or signs plus allows multiple users to interpret and record them consistently is not easy. Some organisations extend the value set further with inclusion of additional values such as 'Trivial' and 'Very severe', and/or 'Mild-Moderate' and 'Moderate-Severe', adds to the definitional difficulty and may also worsen inter-recorder reliability issues. Use of 'Life-threatening' and 'Fatal' is also often considered as part of this value set, although from a pure point of view it may actually reflect an outcome rather than a severity. In view of the above, keeping to a well-defined but smaller list is preferred and so the mild/moderate/severe value set is offered, however the choice of other text allows for other value sets to be included at this data element in a template. (en)</items>
      </items>
      <items code="at0023">
        <items id="text">*Mild(en)</items>
        <items id="description">*The intensity of the symptom or sign does not cause interference with normal activity.(en)</items>
      </items>
      <items code="at0024">
        <items id="text">*Moderate(en)</items>
        <items id="description">*The intensity of the symptom or sign causes interference with normal activity.(en)</items>
      </items>
      <items code="at0025">
        <items id="text">*Severe(en)</items>
        <items id="description">*The intensity of the symptom or sign causes prevents normal activity.(en)</items>
      </items>
      <items code="at0028">
        <items id="text">*Episode duration (en)</items>
        <items id="description">*The duration of this episode of the symptom or sign since initial onset. (en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Date/time of resolution' are used in systems, this data element may be calculated, or alternatively, be considered redundant in this scenario. The text data type is used for recording preset duration intervals such as '0-7 days, 1-2 weeks, 2 weeks or more'. (en)</items>
      </items>
      <items code="at0031">
        <items id="text">*Number of previous episodes(en)</items>
        <items id="description">*The number of times this symptom or sign has previously occurred.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Episode description(en)</items>
        <items id="description">*Narrative description about the course of the symptom or sign during this episode.(en)</items>
        <items id="comment">*For example: a text description of the immediate onset of the symptom, activities that worsened or relieved the symptom, whether it is improving or worsening and how it resolved over weeks.(en)</items>
      </items>
      <items code="at0056">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description of the effect of the modifying factor on the symptom or sign.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">*Description of previous episodes(en)</items>
        <items id="description">*Narrative description of any or all previous episodes.(en)</items>
        <items id="comment">*For example: frequency/periodicity - per hour, day, week, month, year; and regularity. May include a comparison to this episode.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Associated symptom/sign(en)</items>
        <items id="description">*Structured details about any associated symptoms or signs that are concurrent.(en)</items>
        <items id="comment">*In linked clinical systems, it is possible that associated symptoms or signs are already recorded within the EHR. Systems can allow the clinician to LINK to relevant associated symptoms/signs. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent associated symptoms/signs.(en)</items>
      </items>
      <items code="at0146">
        <items id="text">*Previous episodes(en)</items>
        <items id="description">*Structured details of the symptom or sign during a previous episode.(en)</items>
        <items id="comment">*In linked clinical systems, it is possible that previous episodes are already recorded within the EHR. Systems can allow the clinician to LINK to relevant previous episodes. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent previous episodes. It is recommended that new instances of the Symptom archetype inserted in this SLOT represent one or many previous episodes to this Symptom instance only.(en)</items>
      </items>
      <items code="at0147">
        <items id="text">*Structured body site(en)</items>
        <items id="description">*Structured body site where the symptom or sign was reported.(en)</items>
        <items id="comment">*If the anatomical location is included in the Symptom name via precoordinated codes, use of this SLOT becomes redundant. If the anatomical location is recorded using the 'Body site' data element, then use of CLUSTER archetypes in this SLOT is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.(en)</items>
      </items>
      <items code="at0151">
        <items id="text">*Body site(en)</items>
        <items id="description">*Simple body site where the symptom or sign was reported.(en)</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple body sites to be separated out in a template if desired. This allows for representation of clinical scenarios where a symptom or sign needs to be recorded in multiple locations or identifying both the originating and distal site in pain radiation, but where all of the other attributes such as impact and duration are identical. If the requirements for recording the body site are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the Detailed anatomical location' SLOT in this archetype. &#xD;
If the anatomical location is included in the Symptom name via precoordinated codes, this data element becomes redundant.  If the anatomical location is recorded using the 'Structured body site' SLOT, then use of this data element is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.(en)</items>
      </items>
      <items code="at0152">
        <items id="text">*Onset date/time(en)</items>
        <items id="description">*The onset for this episode of the symptom or sign.(en)</items>
        <items id="comment">*While partial dates are permitted, the exact date and time of onset can be recorded, if appropriate. If this is a recurring symptom, this date is used to represent the most recent date or onset of exacerbation, relevant to the clinical presentation. If this is the first instance of this symptom, this date is used to represent the first ever start of symptoms.(en)</items>
      </items>
      <items code="at0153">
        <items id="text">*Specific details(en)</items>
        <items id="description">*Specific data elements that are additionally required to record as unique attributes of the identified symptom or sign.(en)</items>
        <items id="comment">*For example: CTCAE grading.(en)</items>
      </items>
      <items code="at0154">
        <items id="text">*Factor detail(en)</items>
        <items id="description">*Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0155">
        <items id="text">*Impact(en)</items>
        <items id="description">*Description of the impact of this symptom or sign.(en)</items>
        <items id="comment">*Assessment of impact could consider the severity, duration and frequency of the symptom as well as the type of impact including, but not limited to, functional, social and emotional impact. Occurrences of this data element are set to 0..* to allow multiple types of impact to be separated out in a template if desired. Examples for functional impact from hearing loss may include: 'Difficulty Hearing in Quiet Environment'; 'Difficulty Hearing the TV or Radio'; 'Difficulty Hearing Group Conversation'; and 'Difficulty Hearing on Phone'.(en)</items>
      </items>
      <items code="at0156">
        <items id="text">*No effect(en)</items>
        <items id="description">*Presence of the factor has no impact on the symptom or sign.(en)</items>
      </items>
      <items code="at0158">
        <items id="text">*Worsens(en)</items>
        <items id="description">*Presence of the factor exaccerbates severity or impact of the symptom or sign.(en)</items>
      </items>
      <items code="at0159">
        <items id="text">*Relieves(en)</items>
        <items id="description">*Presence of the factor reduces the severity or impact of the symptom or sign.(en)</items>
      </items>
      <items code="at0161">
        <items id="text">*Resolution date/time(en)</items>
        <items id="description">*The timing of the cessation of this episode of the symptom or sign.(en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Duration' are used in systems, this data element may be calculated, or alternatively, considered redundant. While partial dates are permitted, the exact date and time of resolution can be recorded, if appropriate.(en)</items>
      </items>
      <items code="at0163">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the symptom or sign not captured in other fields.(en)</items>
      </items>
      <items code="at0164">
        <items id="text">*Onset timing (en)</items>
        <items id="description">*Timing of the onset and development of the symptom or sign. (en)</items>
        <items id="comment">*The type of the onset can be coded with a terminology, if desired. For example: gradual; or sudden.(en)</items>
      </items>
      <items code="at0165">
        <items id="text">*Precipitating factor (en)</items>
        <items id="description">*Details about specified factors that are associated with the precipitation of the symptom or sign. (en)</items>
        <items id="comment">*For example: lying down leads to heartburn; or walking up a hill leads to claudication. (en)</items>
      </items>
      <items code="at0170">
        <items id="text">*Factor(en)</items>
        <items id="description">*Name of the health event, symptom, reported sign or other factor.(en)</items>
        <items id="comment">*For example: onset of another symptom; lying down; or walking up a hill. (en)</items>
      </items>
      <items code="at0171">
        <items id="text">*Time interval(en)</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and onset of the symptom or sign. (en)</items>
      </items>
      <items code="at0175">
        <items id="text">*Episodicity(en)</items>
        <items id="description">*Category of this epsiode for the identified symptom or sign.(en)</items>
      </items>
      <items code="at0176">
        <items id="text">*New(en)</items>
        <items id="description">*This is the first ever  episode of the symptom or sign.(en)</items>
      </items>
      <items code="at0177">
        <items id="text">*Reoccurrence(en)</items>
        <items id="description">*This is a second or subsequent discrete episode of the symptom or sign, where each previous episode has completely resolved.(en)</items>
      </items>
      <items code="at0178">
        <items id="text">*Ongoing(en)</items>
        <items id="description">*This symptom or sign is continuously present, effectively a single, ongoing episode.(en)</items>
      </items>
      <items code="at0180">
        <items id="text">*Progression(en)</items>
        <items id="description">*Description progression of the symptom or sign at the time of reporting.(en)</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple types of progression to be separated out in a template if desired - for example, severity or frequency. The Text data type is added as an option, to support other value sets than the ones included in the archetype. (en)</items>
      </items>
      <items code="at0181">
        <items id="text">*Improving(en)</items>
        <items id="description">*The severity of the symptom or sign has improved overall during this episode.(en)</items>
      </items>
      <items code="at0182">
        <items id="text">*Unchanged(en)</items>
        <items id="description">*The severity of the symptom or sign has not changed overall during this episode.(en)</items>
      </items>
      <items code="at0183">
        <items id="text">*Worsening(en)</items>
        <items id="description">*The severity of the symptom or sign has worsened overall during this episode.(en)</items>
      </items>
      <items code="at0184">
        <items id="text">*Resolved(en)</items>
        <items id="description">*The severity of the symptom or sign has resolved.(en)</items>
      </items>
      <items code="at0185">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the effect of the factor on the identified symptom or sign.(en)</items>
      </items>
      <items code="at0186">
        <items id="text">*Occurrence (en)</items>
        <items id="description">*Type of occurrence for this symptom or sign? (en)</items>
      </items>
      <items code="at0187">
        <items id="text">*First occurrence (en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign. (en)</items>
      </items>
      <items code="at0188">
        <items id="text">*Recurrence (en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign. (en)</items>
      </items>
      <items code="at0189">
        <items id="text">*Character (en)</items>
        <items id="description">*Word or short phrase describing the nature of the symptom or sign. (en)</items>
        <items id="comment">*For example: pain could be described as 'gnawing', 'burning', or 'like an electric shock'; a headache could be 'throbbing' or 'constant'. Coding with an external terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0190">
        <items id="text">*Resolving factor (en)</items>
        <items id="description">*Details about specified factors that are associated with the resolution of the symptom or sign. (en)</items>
        <items id="comment">*For example: upright posture stops heartburn; or resting stops claudication. (en)</items>
      </items>
      <items code="at0193">
        <items id="text">*Factor(en)</items>
        <items id="description">*Name of the health event, symptom, reported sign or other factor.(en)</items>
        <items id="comment">*For example: upright posture; or resting. (en)</items>
      </items>
      <items code="at0194">
        <items id="text">*Factor detail(en)</items>
        <items id="description">*Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0195">
        <items id="text">*Time interval(en)</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and resolution of the symptom or sign. (en)</items>
      </items>
      <items code="at0196">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the effect of the factor on the identified symptom or sign.(en)</items>
      </items>
      <items code="at0197">
        <items id="text">*Factor detail(en)</items>
        <items id="description">*Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0198">
        <items id="text">*Severity rating (en)</items>
        <items id="description">*Numerical rating scale representing the overall severity of the symptom or sign. (en)</items>
        <items id="comment">*Symptom severity can be rated by the individual by recording a score for example from 0 (ie symptom not present) to 10 (ie symptom is as severe as the individual can imagine). (en)</items>
      </items>
      <items code="at0200">
        <items id="text">*Nadir (en)</items>
        <items id="description">*Date/time when a monophasic, progressive symptom or sign reached its' maximal intensity or functional impact. (en)</items>
        <items id="comment">*For example: the date when neurological signs in Guillain-Barre disease was at its worst. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Symptom/Sign</items>
        <items id="description">Reported observation of a physical or mental disturbance in an individual.</items>
      </items>
      <items code="at0001">
        <items id="text">Symptom/Sign name</items>
        <items id="description">The name of the reported symptom or sign.</items>
        <items id="comment">Symptom name should be coded with a terminology, where possible.</items>
      </items>
      <items code="at0002">
        <items id="text">Description</items>
        <items id="description">Narrative description about the reported symptom or sign.</items>
      </items>
      <items code="at0003">
        <items id="text">Pattern</items>
        <items id="description">Narrative description about the pattern of the symptom or sign during this episode.</items>
        <items id="comment">For example: pain could be described as constant or intermittent.</items>
      </items>
      <items code="at0017">
        <items id="text">Effect</items>
        <items id="description">Perceived effect of the modifying factor on the symptom or sign.</items>
      </items>
      <items code="at0018">
        <items id="text">Modifying factor</items>
        <items id="description">Detail about how a specific factor effects the identified symptom or sign during this episode.</items>
      </items>
      <items code="at0019">
        <items id="text">Factor</items>
        <items id="description">Name of the modifying factor.</items>
        <items id="comment">Examples of modifying factor: lying on multiple pillows, eating or administration of a specific medication.</items>
      </items>
      <items code="at0021">
        <items id="text">Severity category</items>
        <items id="description">Category representing the overall severity of the symptom or sign.</items>
        <items id="comment">Defining values such as mild, moderate or severe in such a way that is applicable to multiple symptoms or signs plus allows multiple users to interpret and record them consistently is not easy. Some organisations extend the value set further with inclusion of additional values such as 'Trivial' and 'Very severe', and/or 'Mild-Moderate' and 'Moderate-Severe', adds to the definitional difficulty and may also worsen inter-recorder reliability issues. Use of 'Life-threatening' and 'Fatal' is also often considered as part of this value set, although from a pure point of view it may actually reflect an outcome rather than a severity. In view of the above, keeping to a well-defined but smaller list is preferred and so the mild/moderate/severe value set is offered, however the choice of other text allows for other value sets to be included at this data element in a template.</items>
      </items>
      <items code="at0023">
        <items id="text">Mild</items>
        <items id="description">The intensity of the symptom or sign does not cause interference with normal activity.</items>
      </items>
      <items code="at0024">
        <items id="text">Moderate</items>
        <items id="description">The intensity of the symptom or sign causes interference with normal activity.</items>
      </items>
      <items code="at0025">
        <items id="text">Severe</items>
        <items id="description">The intensity of the symptom or sign causes prevents normal activity.</items>
      </items>
      <items code="at0028">
        <items id="text">Episode duration</items>
        <items id="description">The duration of this episode of the symptom or sign since initial onset.</items>
        <items id="comment">If 'Date/time of onset' and 'Date/time of resolution' are used in systems, this data element may be calculated, or alternatively, be considered redundant in this scenario. The text data type is used for recording preset duration intervals such as '0-7 days, 1-2 weeks, 2 weeks or more'.</items>
      </items>
      <items code="at0031">
        <items id="text">Number of previous episodes</items>
        <items id="description">The number of times this symptom or sign has previously occurred.</items>
      </items>
      <items code="at0037">
        <items id="text">Episode description</items>
        <items id="description">Narrative description about the course of the symptom or sign during this episode.</items>
        <items id="comment">For example: a text description of the immediate onset of the symptom, activities that worsened or relieved the symptom, whether it is improving or worsening and how it resolved over weeks.</items>
      </items>
      <items code="at0056">
        <items id="text">Description</items>
        <items id="description">Narrative description of the effect of the modifying factor on the symptom or sign.</items>
      </items>
      <items code="at0057">
        <items id="text">Description of previous episodes</items>
        <items id="description">Narrative description of any or all previous episodes.</items>
        <items id="comment">For example: frequency/periodicity - per hour, day, week, month, year; and regularity. May include a comparison to this episode.</items>
      </items>
      <items code="at0063">
        <items id="text">Associated symptom/sign</items>
        <items id="description">Structured details about any associated symptoms or signs that are concurrent.</items>
        <items id="comment">In linked clinical systems, it is possible that associated symptoms or signs are already recorded within the EHR. Systems can allow the clinician to LINK to relevant associated symptoms/signs. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent associated symptoms/signs.</items>
      </items>
      <items code="at0146">
        <items id="text">Previous episodes</items>
        <items id="description">Structured details of the symptom or sign during a previous episode.</items>
        <items id="comment">In linked clinical systems, it is possible that previous episodes are already recorded within the EHR. Systems can allow the clinician to LINK to relevant previous episodes. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent previous episodes. It is recommended that new instances of the Symptom archetype inserted in this SLOT represent one or many previous episodes to this Symptom instance only.</items>
      </items>
      <items code="at0147">
        <items id="text">Structured body site</items>
        <items id="description">Structured body site where the symptom or sign was reported.</items>
        <items id="comment">If the anatomical location is included in the Symptom name via precoordinated codes, use of this SLOT becomes redundant. If the anatomical location is recorded using the 'Body site' data element, then use of CLUSTER archetypes in this SLOT is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.</items>
      </items>
      <items code="at0151">
        <items id="text">Body site</items>
        <items id="description">Simple body site where the symptom or sign was reported.</items>
        <items id="comment">Occurrences of this data element are set to 0..* to allow multiple body sites to be separated out in a template if desired. This allows for representation of clinical scenarios where a symptom or sign needs to be recorded in multiple locations or identifying both the originating and distal site in pain radiation, but where all of the other attributes such as impact and duration are identical. If the requirements for recording the body site are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the Detailed anatomical location' SLOT in this archetype. &#xD;
If the anatomical location is included in the Symptom name via precoordinated codes, this data element becomes redundant. If the anatomical location is recorded using the 'Structured body site' SLOT, then use of this data element is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.</items>
      </items>
      <items code="at0152">
        <items id="text">Episode onset</items>
        <items id="description">The onset for this episode of the symptom or sign.</items>
        <items id="comment">While partial dates are permitted, the exact date and time of onset can be recorded, if appropriate. If this symptom or sign is experienced for the first time or is a re-occurrence, this date is used to represent the onset of this episode. If this symptom or sign is ongoing, this data element may be redundant if it has been recorded previously.</items>
      </items>
      <items code="at0153">
        <items id="text">Specific details</items>
        <items id="description">Specific data elements that are additionally required to record as unique attributes of the identified symptom or sign.</items>
        <items id="comment">For example: CTCAE grading.</items>
      </items>
      <items code="at0154">
        <items id="text">Factor detail</items>
        <items id="description">Structured detail about the factor associated with the identified symptom or sign.</items>
      </items>
      <items code="at0155">
        <items id="text">Impact</items>
        <items id="description">Description of the impact of this symptom or sign.</items>
        <items id="comment">Assessment of impact could consider the severity, duration and frequency of the symptom as well as the type of impact including, but not limited to, functional, social and emotional impact. Occurrences of this data element are set to 0..* to allow multiple types of impact to be separated out in a template if desired. Examples for functional impact from hearing loss may include: 'Difficulty Hearing in Quiet Environment'; 'Difficulty Hearing the TV or Radio'; 'Difficulty Hearing Group Conversation'; and 'Difficulty Hearing on Phone'.</items>
      </items>
      <items code="at0156">
        <items id="text">No effect</items>
        <items id="description">The factor has no impact on the symptom or sign.</items>
      </items>
      <items code="at0158">
        <items id="text">Worsens</items>
        <items id="description">The factor increases the severity or impact of the symptom or sign.</items>
      </items>
      <items code="at0159">
        <items id="text">Relieves</items>
        <items id="description">The factor decreases the severity or impact of the symptom or sign, but does not fully resolve it.</items>
      </items>
      <items code="at0161">
        <items id="text">Resolution date/time</items>
        <items id="description">The timing of the cessation of this episode of the symptom or sign.</items>
        <items id="comment">If 'Date/time of onset' and 'Duration' are used in systems, this data element may be calculated, or alternatively, considered redundant. While partial dates are permitted, the exact date and time of resolution can be recorded, if appropriate.</items>
      </items>
      <items code="at0163">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the symptom or sign not captured in other fields.</items>
      </items>
      <items code="at0164">
        <items id="text">Onset timing</items>
        <items id="description">Timing of the onset and development of the symptom or sign.</items>
        <items id="comment">The type of the onset can be coded with a terminology, if desired. For example: gradual; or sudden.</items>
      </items>
      <items code="at0165">
        <items id="text">Precipitating factor</items>
        <items id="description">Details about specified factors that are associated with the precipitation of the symptom or sign.</items>
        <items id="comment">For example: lying down leads to heartburn; or walking up a hill leads to claudication.</items>
      </items>
      <items code="at0170">
        <items id="text">Factor</items>
        <items id="description">Name of the health event, symptom, reported sign or other factor.</items>
        <items id="comment">For example: onset of another symptom; lying down; or walking up a hill.</items>
      </items>
      <items code="at0171">
        <items id="text">Time interval</items>
        <items id="description">The interval of time between the occurrence or onset of the factor and onset of the symptom or sign.</items>
      </items>
      <items code="at0175">
        <items id="text">Episodicity</items>
        <items id="description">Category of this episode for the identified symptom or sign.</items>
      </items>
      <items code="at0176">
        <items id="text">New</items>
        <items id="description">A new episode of the symptom or sign - either the first ever occurrence or a reoccurrence where the previous episode had completely resolved.</items>
      </items>
      <items code="at0177">
        <items id="text">Indeterminate</items>
        <items id="description">It is not possible to determine if this occurrence of the symptom or sign is new or ongoing.</items>
      </items>
      <items code="at0178">
        <items id="text">Ongoing</items>
        <items id="description">This symptom or sign is ongoing, effectively a single, continuous episode.</items>
      </items>
      <items code="at0180">
        <items id="text">Progression</items>
        <items id="description">Description progression of the symptom or sign at the time of reporting.</items>
        <items id="comment">Occurrences of this data element are set to 0..* to allow multiple types of progression to be separated out in a template if desired - for example, severity or frequency. The Text data type is added as an option, to support other value sets than the ones included in the archetype.</items>
      </items>
      <items code="at0181">
        <items id="text">Improving</items>
        <items id="description">The severity of the symptom or sign has improved overall during this episode.</items>
      </items>
      <items code="at0182">
        <items id="text">Unchanged</items>
        <items id="description">The severity of the symptom or sign has not changed overall during this episode.</items>
      </items>
      <items code="at0183">
        <items id="text">Worsening</items>
        <items id="description">The severity of the symptom or sign has worsened overall during this episode.</items>
      </items>
      <items code="at0184">
        <items id="text">Resolved</items>
        <items id="description">The severity of the symptom or sign has resolved.</items>
      </items>
      <items code="at0185">
        <items id="text">Description</items>
        <items id="description">Narrative description about the effect of the factor on the identified symptom or sign.</items>
      </items>
      <items code="at0186">
        <items id="text">Occurrence</items>
        <items id="description">Type of occurrence for this symptom or sign?</items>
      </items>
      <items code="at0187">
        <items id="text">First occurrence</items>
        <items id="description">This is the first ever occurrence of this symptom or sign.</items>
      </items>
      <items code="at0188">
        <items id="text">Recurrence</items>
        <items id="description">New occurrence of the same symptom or sign after a previous episode was resolved.</items>
      </items>
      <items code="at0189">
        <items id="text">Character</items>
        <items id="description">Word or short phrase describing the nature of the symptom or sign.</items>
        <items id="comment">For example: pain could be described as 'gnawing', 'burning', or 'like an electric shock'; a headache could be 'throbbing' or 'constant'. Coding with an external terminology is preferred, where possible.</items>
      </items>
      <items code="at0190">
        <items id="text">Resolving factor</items>
        <items id="description">Details about specified factors that are associated with the resolution of the symptom or sign.</items>
        <items id="comment">For example: upright posture stops heartburn; or resting stops claudication.</items>
      </items>
      <items code="at0193">
        <items id="text">Factor</items>
        <items id="description">Name of the health event, symptom, reported sign or other factor.</items>
        <items id="comment">For example: upright posture; or resting.</items>
      </items>
      <items code="at0194">
        <items id="text">Factor detail</items>
        <items id="description">Structured detail about the factor associated with the identified symptom or sign.</items>
      </items>
      <items code="at0195">
        <items id="text">Time interval</items>
        <items id="description">The interval of time between the occurrence or onset of the factor and resolution of the symptom or sign.</items>
      </items>
      <items code="at0196">
        <items id="text">Description</items>
        <items id="description">Narrative description about the effect of the factor on the identified symptom or sign.</items>
      </items>
      <items code="at0197">
        <items id="text">Factor detail</items>
        <items id="description">Structured detail about the factor associated with the identified symptom or sign.</items>
      </items>
      <items code="at0198">
        <items id="text">Severity rating</items>
        <items id="description">Numerical rating scale representing the overall severity of the symptom or sign.</items>
        <items id="comment">Symptom severity can be rated by the individual by recording a score for example from 0 (ie symptom not present) to 10 (ie symptom is as severe as the individual can imagine).</items>
      </items>
      <items code="at0200">
        <items id="text">Nadir</items>
        <items id="description">Date/time when a monophasic, progressive symptom or sign reached its' maximal intensity or functional impact.</items>
        <items id="comment">For example: the date when neurological signs in Guillain-Barre disease was at its worst.</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Symptom/Krankheitsanzeichen</items>
        <items id="description">Berichtete Beobachtung einer körperlichen oder psychischen Störung bei einer Person.</items>
      </items>
      <items code="at0001">
        <items id="text">Name des Symptoms/Krankheitsanzeichens</items>
        <items id="description">Der Name des berichteten Symptoms/Krankheitsanzeichens.</items>
        <items id="comment">Der Name des Symptoms sollte, wenn möglich, mit einer Terminologie kodiert werden.</items>
      </items>
      <items code="at0002">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung des festgestellten Symptoms/Krankheitsanzeichens.</items>
      </items>
      <items code="at0003">
        <items id="text">Muster</items>
        <items id="description">Beschreibung des Musters des Symptoms/Krankheitsanzeichens während dieser Episode.</items>
        <items id="comment">Zum Beispiel: Schmerzen können als konstant oder periodisch beschrieben werden.</items>
      </items>
      <items code="at0017">
        <items id="text">Einfluss</items>
        <items id="description">Wahrgenommene Auswirkung des Faktors auf das Symptom/Krankheitsanzeichen.</items>
      </items>
      <items code="at0018">
        <items id="text">Einflussfaktor</items>
        <items id="description">Nähere Informationen zur Art und Weise der Beeinflussung des identifizierten Symptoms/Krankheitsanzeichens durch einen bestimmten Faktor während dieser Episode.</items>
      </items>
      <items code="at0019">
        <items id="text">Faktor</items>
        <items id="description">Name des Einflussfaktors.</items>
        <items id="comment">Beispiele für Einflussfaktoren: Liegen auf mehreren Kissen, Essen oder Verabreichung eines bestimmten Medikaments.</items>
      </items>
      <items code="at0021">
        <items id="text">Schweregrad</items>
        <items id="description">Kategorie, die den allgemeinen Schweregrad des Symptoms/Krankheitsanzeichens beschreibt.</items>
        <items id="comment">Es ist nicht einfach, Werte wie leicht, mittel oder schwer so zu definieren, dass sie auf mehrere Symptome oder Anzeichen anwendbar sind und von mehreren Benutzern konsistent interpretiert und erfasst werden können. Einige Organisationen erweitern den Wertesatz weiter, indem sie zusätzliche Werte wie z.B. "trivial", "sehr stark", "leicht-moderat" oder "moderat-schwer", miteinbeziehen, was die Definitionsschwierigkeiten erhöht und auch die Zuverlässigkeit von Aufzeichnungen von verschiedenen Protokollanten verschlechtern kann. Die Verwendung von „lebensbedrohlich“ und „tödlich“ wird ebenfalls oft als Teil dieses Wertesatzes angesehen, obwohl es rein betrachtet eher ein Ergebnis als einen Schweregrad widerspiegeln kann. In Anbetracht dessen wird die Einhaltung einer gut definierten, aber kürzeren Liste bevorzugt, so dass der Wertesatz "leicht/moderat/schwer" angeboten wird. Die Wahl eines anderen Textes wird durch die Aufnahme anderer Wertebereiche für dieses Datenelement im Template ermöglicht.</items>
      </items>
      <items code="at0023">
        <items id="text">Leicht</items>
        <items id="description">Die Intensität des Symptoms/Krankheitsanzeichens führt zu keiner Beeinträchtigung der normalen Aktivität.</items>
      </items>
      <items code="at0024">
        <items id="text">Moderat</items>
        <items id="description">Die Intensität des Symptoms/Krankheitsanzeichens führt zu einer Beeinträchtigung der normalen Aktivität.</items>
      </items>
      <items code="at0025">
        <items id="text">Schwer</items>
        <items id="description">Die Intensität des Symptoms/Krankheitsanzeichens verhindert eine normale Aktivität.</items>
      </items>
      <items code="at0028">
        <items id="text">Episodendauer</items>
        <items id="description">Die Dauer dieser Episode des Symptoms oder Anzeichens seit dem ersten Auftreten.</items>
        <items id="comment">Wenn in Systemen "Beginn der Episode" und "Zeitpunkt des Rückgangs" verwendet werden, kann dieses Datenelement berechnet oder alternativ in diesem Szenario als redundant angesehen werden. Der Datentyp "Text" wird zur Darstellung prädefinierten Dauerintervalle wie „0–7 Tage, 1–2 Wochen, 2 Wochen oder mehr“ verwendet.</items>
      </items>
      <items code="at0031">
        <items id="text">Anzahl vorangegangener Episoden</items>
        <items id="description">Die Anzahl, wie oft das Symptom/Krankheitsanzeichen bereits aufgetreten ist.</items>
      </items>
      <items code="at0037">
        <items id="text">Beschreibung der Episode</items>
        <items id="description">Beschreibung des Verlaufs des Symptoms/Krankheitsanzeichens während dieser Episode.</items>
        <items id="comment">Zum Beispiel: eine Beschreibung des unmittelbaren Auftretens des Symptoms, Aktivitäten, die das Symptom verschlimmert oder gelindert haben, ob es sich verbessert oder verschlechtert hat und wie es über Wochen zurückging.</items>
      </items>
      <items code="at0056">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung des Einflusses des Faktors auf das Symptom/Krankheitsanzeichen.</items>
      </items>
      <items code="at0057">
        <items id="text">Beschreibung vorangegangener Episoden</items>
        <items id="description">Beschreibung einer oder aller früheren Episoden.</items>
        <items id="comment">Zum Beispiel: Häufigkeit/Periodizität - pro Stunde, Tag, Woche, Monat, Jahr; und Regelmäßigkeit. Kann einen Vergleich zu dieser Episode beinhalten.</items>
      </items>
      <items code="at0063">
        <items id="text">Assoziierte Symptome/Krankheitsanzeichen</items>
        <items id="description">Strukturierte Details über alle assoziierten Symptome/Krankheitsanzeichen, die gleichzeitig auftreten.</items>
        <items id="comment">In vernetzten klinischen Systemen ist es möglich, dass verbundene Symptome/Krankheitsanzeichen bereits in der elektronischen Gesundheitsakte (engl. Electronic Health Record - EHR) erfasst wurden. Die Systeme können es dem Arzt ermöglichen, auf relevante in Zusammenhang stehende Symptomen/Krankheitsanzeichen zu verweisen. In einem System oder einer Nachricht ohne eine Verlinkung zu bestehenden Daten oder bei einem neuen Patienten können zusätzliche Instanzen des Symptom-Archetyps hier aufgenommen werden, um damit verbundene Symptome/Krankheitsanzeichen darzustellen.</items>
      </items>
      <items code="at0146">
        <items id="text">Vorangegangene Episoden</items>
        <items id="description">Strukturierte Details des Symptoms/Befundes während einer früheren Episode.</items>
        <items id="comment">In vernetzten klinischen Systemen ist es möglich, dass vorangegangene Episoden bereits in der elektronischen Gesundheitsakte (engl. Electronic Health Record - EHR) erfasst wurden. Die Systeme können es dem Arzt ermöglichen, auf relevante vorangegangene Episoden zu verweisen. In einem System oder einer Nachricht ohne eine Verlinkung zu bestehenden Daten oder bei einem neuen Patienten können zusätzliche Instanzen des Symptom-Archetyps aufgenommen werden, um frühere Episoden darzustellen. Es wird empfohlen, dass neue Instanzen des Symptom-Archetyps, die in diesen Slot eingefügt werden, eine oder mehrere vorangegangene Episoden dieser Symptom-Instanz darstellen.</items>
      </items>
      <items code="at0147">
        <items id="text">Spezifische anatomische Lokalisation</items>
        <items id="description">Spezifische anatomische Lokalisation des Symptoms/Krankheitsanzeichens.</items>
        <items id="comment">Wenn die anatomische Lokalisation über vordefinierte Codes in den Symptomnamen aufgenommen wird, wird die Verwendung dieses Slots überflüssig. Wenn die anatomische Lokalisation mit dem Datenelement "Anatomische Lokalisation" erfasst wird, ist die Verwendung von CLUSTER-Archetypen in diesem Slot nicht erlaubt - erfassen Sie entweder die grobe "Anatomische Lokalisation" oder die "Spezifische anatomische Lokalisation", nicht beides.</items>
      </items>
      <items code="at0151">
        <items id="text">Anatomische Lokalisation</items>
        <items id="description">Anatomische Lokalisation des Symptoms/Anzeichens.</items>
        <items id="comment">Das Auftreten dieses Datenelements wird auf 0...* gesetzt, um bei Bedarf mehrere Körperstellen im Template voneinander zu trennen. Dies ermöglicht die Darstellung klinischer Szenarien, in denen ein Symptom/Krankheitsanzeichen an mehreren Stellen erfasst werden muss oder in denen sowohl die ursprüngliche als auch die distale Stelle bei der Schmerzausbreitung identifiziert werden, aber alle anderen Attribute wie Wirkung und Dauer identisch sind. Wenn die Anforderungen an die Erfassung der Lokalisation zur Laufzeit durch die Anwendung festgelegt werden oder komplexere Modellierungen wie z.B. relative Positionen erforderlich sind, verwenden Sie CLUSTER.anatomical_location oder CLUSTER.relative_location innerhalb des Slots "Spezifische anatomische Lokalisation" in diesem Archetyp. &#xD;
Wird die anatomische Lokalisation über vordefinierte Codes in den Symptomnamen aufgenommen, wird dieses Datenelement redundant. Wenn die anatomische Lokalisation mit dem Slot "Spezifische anatomische Lokalisation" erfasst wird, ist die Verwendung dieses Datenelements nicht erlaubt - erfassen Sie entweder die grobe "Anatomische Lokalisation" oder die "Spezifische anatomische Lokalisation", nicht beides.</items>
      </items>
      <items code="at0152">
        <items id="text">Beginn der Episode</items>
        <items id="description">Der Beginn der Episode dieses Symptoms/Krankheitsanzeichens.</items>
        <items id="comment">Teil-Datumsangaben sind zulässig, gegebenenfalls kann aber auch das genaue Datum und die genaue Uhrzeit des Beginns erfasst werden. Wenn das Symptom/Krankheitsanzeichen zum ersten Mal auftritt oder ein Wiederauftreten vorliegt, wird dieses Datum verwendet, um den Beginn dieser Episode darzustellen. Wenn das Symptom/Krankheitsanzeichen andauernd ist, kann dieses Datenelement redundant sein, wenn es zuvor bereits erfasst wurde.</items>
      </items>
      <items code="at0153">
        <items id="text">Spezifische Details</items>
        <items id="description">Spezifische Datenelemente, die zusätzlich erforderlich sind, um eindeutige Attribute des identifizierten Symptoms/Krankheitsanzeichens zu erfassen.</items>
        <items id="comment">Zum Beispiel: CTCAE Einteilung.</items>
      </items>
      <items code="at0154">
        <items id="text">Detail zum Faktor</items>
        <items id="description">Strukturiertes Detail über den Faktor, der mit dem identifizierten Symptom/Krankheitsanzeichen in Verbindung steht.</items>
      </items>
      <items code="at0155">
        <items id="text">Auswirkungen</items>
        <items id="description">Beschreibung der Auswirkung des Symptoms/Krankheitsanzeichens.</items>
        <items id="comment">Die Bewertung der Auswirkung könnte die Schwere, Dauer und Häufigkeit des Symptoms sowie die Art der Auswirkungen berücksichtigen, einschließlich (aber nicht beschränkt auf) funktionelle, soziale und emotionale Auswirkungen. Das Auftreten dieses Datenelements wird auf 0...* gesetzt, damit bei Bedarf mehrere Arten von Auswirkungen in einem Template getrennt voneinander erfasst werden können. Beispiele für funktionelle Auswirkungen von Hörverlust können sein: "Schwierigkeiten beim Hören in ruhiger Umgebung"; "Schwierigkeiten beim Hören von TV oder Radio"; "Schwierigkeiten beim Hören von Gruppengesprächen"; und "Schwierigkeiten beim Hören am Telefon".</items>
      </items>
      <items code="at0156">
        <items id="text">Keinen Einfluss</items>
        <items id="description">Der Faktor hat keinen Einfluss auf das Symptom/Krankheitsanzeichen.</items>
      </items>
      <items code="at0158">
        <items id="text">Verschlechterung</items>
        <items id="description">Der Faktor erhöht den Schweregrad oder die Folgen des Symptoms/Krankheitsanzeichens.</items>
      </items>
      <items code="at0159">
        <items id="text">Linderung</items>
        <items id="description">Der Faktor verringert den Schweregrad oder den Einfluss des Symptoms/Krankheitsanzeichens, bringt es aber nicht vollständig zum Abklingen.</items>
      </items>
      <items code="at0161">
        <items id="text">Zeitpunkt des Rückgangs</items>
        <items id="description">Der Endzeitpunkt dieser Episode des Symptoms/Krankheitsanzeichens.</items>
        <items id="comment">Wenn in Systemen "Beginn der Episode" und "Dauer" verwendet werden, kann dieses Datenelement berechnet oder alternativ als redundant betrachtet werden. Teil-Datumsangaben sind zulässig, gegebenenfalls kann aber auch das genaue Datum und die genaue Uhrzeit des Rückgangs erfasst werden.</items>
      </items>
      <items code="at0163">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Angaben zu dem Symptom/Krankheitsanzeichen, die nicht in anderen Feldern erfasst wurden.</items>
      </items>
      <items code="at0164">
        <items id="text">Zeitpunkt des Beginns</items>
        <items id="description">Zeitpunkt des Beginns und der Entwicklung des Symptoms oder Anzeichens.</items>
        <items id="comment">Es besteht die Möglichkeit die Art des Beginns mit einer Terminologie zu kodieren. Zum Beispiel: schleichend oder plötzlich.</items>
      </items>
      <items code="at0165">
        <items id="text">Auslösender Faktor</items>
        <items id="description">Details zu bestimmten Faktoren, die mit der Ausprägung des Symptoms oder Krankheitsanzeichens verbunden sind.</items>
        <items id="comment">Zum Beispiel: Hinlegen führt zu Sodbrennen oder das Gehen bergauf führt zu Claudicatio.</items>
      </items>
      <items code="at0170">
        <items id="text">Faktor</items>
        <items id="description">Name des die Gesundheit betreffenden Ereignisses, Symptoms, Krankheitsanzeichens oder eines anderen Faktors.</items>
        <items id="comment">Zum Beispiel: Beginn eines anderen Symptoms, hinlegen oder bergauf gehen.</items>
      </items>
      <items code="at0171">
        <items id="text">Zeitintervall</items>
        <items id="description">Das Zeitintervall zwischen dem Auftreten oder Einsetzen des Faktors und dem Einsetzen des Symptoms oder Krankheitsanzeichens.</items>
      </items>
      <items code="at0175">
        <items id="text">Episode</items>
        <items id="description">Kategorie dieser Episode für das identifizierte Symptom/Krankheitsanzeichen.</items>
      </items>
      <items code="at0176">
        <items id="text">Neu</items>
        <items id="description">Eine neue Episode des Symptoms/Krankheitsanzeichens - entweder das erste Auftreten oder ein Wiederauftreten, bei dem die vorherige Episode vollständig abgeklungen ist.</items>
      </items>
      <items code="at0177">
        <items id="text">Unbestimmt</items>
        <items id="description">Es ist nicht möglich zu bestimmen, ob dieses Auftreten des Symptoms/Krankheitsanzeichens neu oder andauernd ist.</items>
      </items>
      <items code="at0178">
        <items id="text">Andauernd</items>
        <items id="description">Das Symptom/Krankheitsanzeichen ist andauernd, im Grunde eine einzige, kontinuierliche Episode.</items>
      </items>
      <items code="at0180">
        <items id="text">Progression</items>
        <items id="description">Beschreibung der Entwicklung des Symptoms/Krankheitsanzeichens zum Zeitpunkt der Meldung.</items>
        <items id="comment">Das Vorkommen dieses Datenelements wird auf 0..* gesetzt, um zu ermöglichen, dass mehrere Arten der Progression in einem Template auf Wunsch definiert werden können – zum Beispiel Schweregrad oder Häufigkeit. Der Datentyp Text wird als Option hinzugefügt, um andere Wertesätze als die im Archetyp enthaltenen zu unterstützen.</items>
      </items>
      <items code="at0181">
        <items id="text">Verbesserung</items>
        <items id="description">Der Schweregrad dieses Symptoms/Krankheitsanzeichens hat sich im Verlauf dieser Episode allgemein verbessert.</items>
      </items>
      <items code="at0182">
        <items id="text">Unverändert</items>
        <items id="description">Der Schweregrad dieses Symptoms/Krankheitsanzeichens blieb im Verlauf dieser Episode allgemein unverändert.</items>
      </items>
      <items code="at0183">
        <items id="text">Verschlechterung</items>
        <items id="description">Der Schweregrad des Symptoms/Krankheitsanzeichens hat sich im Verlauf dieser Episode allgemein verschlechtert.</items>
      </items>
      <items code="at0184">
        <items id="text">Vollständiger Rückgang</items>
        <items id="description">Der Schweregrad dieses Symptoms/Krankheitsanzeichens ist im Verlauf dieser Episode vollständig zurückgegangen.</items>
      </items>
      <items code="at0185">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung des Einflusses des Faktors auf das identifizierte Symptom/Krankheitsanzeichen.</items>
      </items>
      <items code="at0186">
        <items id="text">Auftreten</items>
        <items id="description">Wie ist die Art des Auftretens des Symptoms/Krankheitsanzeichens?</items>
      </items>
      <items code="at0187">
        <items id="text">Erstmaliges Auftreten</items>
        <items id="description">Dies ist das erstmalige Auftreten des Symptoms/Krankheitsanzeichens.</items>
      </items>
      <items code="at0188">
        <items id="text">Erneutes Auftreten</items>
        <items id="description">Das Symptom/Krankheitsanzeichen ist in der Vergangenheit bereits aufgetreten.</items>
      </items>
      <items code="at0189">
        <items id="text">Charakterisierung</items>
        <items id="description">Wort oder kurzer Satz, mit dem die Art des Symptoms/Krankheitsanzeichens beschrieben wird.</items>
        <items id="comment">Zum Beispiel: Schmerzen können als "bohrend", "brennend" oder "wie ein Stromschlag" beschrieben werden; Kopfschmerzen können "pochend" oder "konstant" sein. Wenn möglich soll eine Kodierung mit einer externen Terminologie bevorzugt werden.</items>
      </items>
      <items code="at0190">
        <items id="text">Rückbildender Faktor</items>
        <items id="description">Details zu bestimmten Faktoren, die mit der Rückbildung des Symptoms oder Krankheitsanzeichens verbunden sind.</items>
        <items id="comment">Zum Beispiel: eine aufrechte Körperhaltung stoppt Sodbrennen oder Ruhepause bei Claudicatio.</items>
      </items>
      <items code="at0193">
        <items id="text">Faktor</items>
        <items id="description">Name des die Gesundheit betreffenden Ereignisses, Symptoms, Krankheitsanzeichens oder eines anderen Faktors.</items>
        <items id="comment">Zum Beispiel: aufrechte Körperhaltung oder ruhen.</items>
      </items>
      <items code="at0194">
        <items id="text">Detail zum Faktor</items>
        <items id="description">Strukturiertes Detail über den Faktor, der mit dem identifizierten Symptom/Krankheitsanzeichen in Verbindung steht.</items>
      </items>
      <items code="at0195">
        <items id="text">Zeitintervall</items>
        <items id="description">Das Zeitintervall zwischen dem Auftreten oder Einsetzen des Faktors und des Rückgangs des Symptoms oder Krankheitsanzeichens.</items>
      </items>
      <items code="at0196">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung des Einflusses des Faktors auf das identifizierte Symptom/Krankheitsanzeichen.</items>
      </items>
      <items code="at0197">
        <items id="text">Detail zum Faktor</items>
        <items id="description">Strukturiertes Detail über den Faktor, der mit dem identifizierten Symptom/Krankheitsanzeichen in Verbindung steht.</items>
      </items>
      <items code="at0198">
        <items id="text">Schwere-Ratingskala</items>
        <items id="description">Numerische Bewertungsskala, die den Gesamtschweregrad des Symptoms oder Anzeichens darstellt.</items>
        <items id="comment">Die Schwere der Symptome kann von der Person bewertet werden, indem sie beispielsweise eine Punktzahl von 0 (d. h. kein Symptom vorhanden) bis 10 (d. h. das Symptom ist so schwerwiegend, wie die Person es sich vorstellen kann) aufzeichnet.</items>
      </items>
      <items code="at0200">
        <items id="text">Tiefpunkt</items>
        <items id="description">Datum/Uhrzeit, als ein monophasisches, fortschreitendes Symptom oder Zeichen seine maximale Intensität oder funktionelle Auswirkung erreichte.</items>
        <items id="comment">Zum Beispiel: das Datum, an dem die neurologischen Symptome bei der Guillain-Barré-Krankheit am schlimmsten waren.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Symptom/Sykdomstegn</items>
        <items id="description">Rapportert observasjon av fysiske tegn eller beskrivelse av unormale eller ubehagelige fornemmelser i kropp og/eller sinn.</items>
      </items>
      <items code="at0001">
        <items id="text">Navn på symptom/sykdomstegn</items>
        <items id="description">Navnet på det rapporterte symptomet eller sykdomstegnet.</items>
        <items id="comment">Navnet på symptom/sykdomstegn bør kodes med en terminologi om mulig.</items>
      </items>
      <items code="at0002">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse av det rapporterte symptomet eller sykdomstegnet.</items>
        <items id="comment">Eksempel: "Svimmelhet med rotasjonsfølelse og av og til besvimelsesfølelse. Hurtig bevegelse fra sittende eller liggende til stående stilling virker å være en utløsende faktor. Opptrer typisk flere ganger daglig, og varer i ca et halvt til ett minutt hver gang. Å sette eller legge seg ned virker lindrende."</items>
      </items>
      <items code="at0003">
        <items id="text">Mønster</items>
        <items id="description">Fritekstbeskrivelse av symptomet eller sykdomstegnet i løpet av denne episoden.</items>
        <items id="comment">For eksempel: Smerte kan beskrives som konstant eller intermitterende. Dette elementet kan brukes til å registrere tekstlige beskrivelser (enten det er fri eller kodet tekst) av den typiske frekvensen og varigheten av symptomanfall under den aktuelle episoden.</items>
      </items>
      <items code="at0017">
        <items id="text">Effekt</items>
        <items id="description">Oppfattet effekt av den modifiserende faktoren på symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0018">
        <items id="text">Modifiserende faktor</items>
        <items id="description">Detaljer om hvordan en spesifikk faktor påvirker det identifiserte symptomet eller sykdomstegnet i løpet av denne episoden.</items>
      </items>
      <items code="at0019">
        <items id="text">Faktor</items>
        <items id="description">Navn på den modifiserende faktoren.</items>
        <items id="comment">Dette elementet er ment for å dokumentere faktorer, terapeutiske eller andre, som har innvirkning på symptomet. En oversikt over planlagte og utførte tiltak for symptomet eller sykdomstegnet må dokumenteres ved hjelp av andre arketyper.&#xD;
Eksempel på modifiserende faktor: sengeleie med flere puter, spising, eller administrering av et spesifikt legemiddel.</items>
      </items>
      <items code="at0021">
        <items id="text">Alvorlighetskategori</items>
        <items id="description">Kategori for å beskrive symptomets eller sykdomstegnets helhetlige alvorlighet.</items>
        <items id="comment">Det er vanskelig å definere verdier som mild, moderat og alvorlig på en slik måte at det kan brukes om flere symptomer, og som samtidig sikrer at tolkning og registrering av verdiene er konsistent. Ved å utvide verdisettet med verdier som "ubetydelig" og "veldig alvorlig", og/eller "moderat mild" og "moderat alvorlig" øker kompleksiteten, og påliteligheten i registreringen reduseres. Bruk av verdier som "Livstruende" eller "fatal" tas ofte med i et slikt verdisett, men disse verdiene gjenspeiler heller resultat enn alvorlighet. I lys av dette foretrekkes en mindre, mer veldefinert liste.</items>
      </items>
      <items code="at0023">
        <items id="text">Mild</items>
        <items id="description">Symptomet eller sykdomstegnets intensitet forstyrrer ikke normal aktivitet.</items>
      </items>
      <items code="at0024">
        <items id="text">Moderat</items>
        <items id="description">Symptomet eller sykdomstegnet intensitet forstyrrer normal aktivitet.</items>
      </items>
      <items code="at0025">
        <items id="text">Alvorlig</items>
        <items id="description">Symptomets eller sykdomstegnets intensitet hindrer normal aktivitet.</items>
      </items>
      <items code="at0028">
        <items id="text">Varighet av episoden</items>
        <items id="description">Varigheten av denne episoden av symptomet eller sykdomstegnet siden debut.</items>
        <items id="comment">Dersom "Dato/tid for debut" og "Dato/tid for opphør" registreres i systemet, kan dette dataelementet kalkuleres av systemet eller være overflødig. Tekst-datatypen kan brukes til å registrere forhåndsdefinerte intervaller som "0–7 dager", "1–2 uker" eller "2 uker eller mer".</items>
      </items>
      <items code="at0031">
        <items id="text">Antall tidligere episoder</items>
        <items id="description">Antall ganger symptomet eller sykdomstegnet tidligere har forekommet.</items>
      </items>
      <items code="at0037">
        <items id="text">Episodebeskrivelse</items>
        <items id="description">Fritekstbeskrivelse av symptomet eller sykdomstegnets utvikling gjennom denne episoden.</items>
        <items id="comment">For eksempel: Fritekstbeskrivelse av symptomdebuten, aktiviteter som forverret eller forbedret symptomet, om det er i bedring eller forverring og hvordan det ble fullstendig bedret i løpet av uker.</items>
      </items>
      <items code="at0056">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse av den modifiserende faktorens effekt på symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0057">
        <items id="text">Beskrivelse av tidligere episoder</items>
        <items id="description">Fritekstbeskrivelse av tidligere episoder.</items>
        <items id="comment">For eksempel: Frekvens/periodisitet - pr. time, dag, uke, måned, år og regularitet. Kan inneholde en sammenligning med denne episoden.</items>
      </items>
      <items code="at0063">
        <items id="text">Tilknyttede symptomer/sykdomstegn</items>
        <items id="description">Strukturerte detaljer om ethvert tilknyttet symptom eller sykdomstegn som er tilstede samtidig.</items>
        <items id="comment">I kliniske systemer med mulighet for linking er det mulig at tilknyttede symptomer/sykdomstegn allerede er registrert i det kliniske systemet. Systemet kan tillatte en kliniker å linke til relevante tilknyttede symptomer/sykdomstegn. Tillater ikke systemet linking eller det er en pasient som ikke har noen tilknyttede symptomer registrert, kan man legge til ytterligere instanser av symptom-arketypen for å beskrive de tidligere episodene.</items>
      </items>
      <items code="at0146">
        <items id="text">Tidligere episoder</items>
        <items id="description">Strukturerte detaljer om symptomet eller sykdomstegnet i løpet av en tidligere episode.</items>
        <items id="comment">I kliniske systemer med mulighet for linking er det mulig at tidligere episoder allerede er registrert i det kliniske systemet. Systemet kan tillatte en kliniker å linke til relevante tilknyttede symptomer. Tillater ikke systemet linking eller det er en pasient som ikke har noen tilknyttede symptomer registrert, kan man legge til ytterligere instanser av symptom-arketypen for å beskrive de tidligere episodene.</items>
      </items>
      <items code="at0147">
        <items id="text">Strukturert anatomisk lokalisering</items>
        <items id="description">Strukturert anatomisk lokalisering hvor symptomet eller sykdomstegnet ble rapportert.</items>
        <items id="comment">Hvis den anatomiske lokaliseringen allerede er satt i elementet "Navn på symptom/sykdomstegn" via prekoordinerte koder, blir dette SLOTet overflødig. Er den anatomiske lokaliseringen registrert i dataelementet "Anatomisk lokalisering", er bruken av dette SLOTet ikke tillatt. Registrer bare "Anatomisk lokalisering" eller "Strukturert anatomisk lokalisering", ikke begge.</items>
      </items>
      <items code="at0151">
        <items id="text">Anatomisk lokalisering</items>
        <items id="description">Registrering av ett enkelt område på kroppen hvor symptomet eller sykdomstegnet var rapportert.</items>
        <items id="comment">Forekomster for dette dataelementet er satt 0..* for å tillate at flere kroppssted kan trekkes ut i et templat om ønsket. Dette åpner for å representere kliniske scenarier hvor et symptom må registreres flere steder på kroppen eller for å identifisere både opphavssted for smerte og ytterpunkt for utstråling av smerter, og alle andre dataelementer i arketypen som "Innvirkning" og "Varighet" er like. Om kravet for registrering av kroppsplassering er bestemt i en applikasjon eller krever en mer kompleks modellering som for eksempel relativ lokalisering, bruk arketypen CLUSTER.anatomical_location eller CLUSTER.relative_location i "Strukturert anatomisk lokalisering"-SLOTet i denne arketypen. Er den anatomiske lokaliseringen inkludert i "Navn på symptom/sykdomstegn" via prekoordinerte koder er dette dataelementet overflødig. Registreres den anatomiske lokaliseringen i SLOTet "Strukturert anatomisk lokalisering" er bruken av dette dataelementet ikke tillatt. Registrer enten i "Anatomisk lokalisering" eller i "Strukturert anatomisk lokalisering", ikke i begge.</items>
      </items>
      <items code="at0152">
        <items id="text">Dato/tid for episodens debut</items>
        <items id="description">Debuttidspunkt for denne episoden av symptomet eller sykdomstegnet.</items>
        <items id="comment">Partielle datoer er tillatt. Nøyaktig tid for symptomets debut kan registreres, dersom relevant. Dersom dette symptomet eller sykdomstegnet oppleves for første gang eller er en ny episode av et tidligere opplevd symptom, kan denne datoen brukes for å representere debuten for denne episoden. Dersom symptomet eller sykdomstegnet opptrer kontinuerlig, kan dette dataelementet være overflødig dersom det er registrert tidligere.</items>
      </items>
      <items code="at0153">
        <items id="text">Spesifikke detaljer</items>
        <items id="description">Ekstra dataelementer som er nødvendige for å registrere egenskaper unike for det identifiserte symptomet eller sykdomstegnet.</items>
        <items id="comment">For eksempel: Graderingen "Common Terminology Criteria for Adverse Events".</items>
      </items>
      <items code="at0154">
        <items id="text">Faktordetaljer</items>
        <items id="description">Strukturerte detaljer om faktoren som er forbundet med det identifiserte symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0155">
        <items id="text">Innvirkning</items>
        <items id="description">Beskrivelse av symptomet eller sykdomstegnets innvirkning.</items>
        <items id="comment">Bedømmelsen av innvirkning må ta høyde for alvorlighet, varighet og frekvens av symptomet, i tillegg til type innvirkning, for eksempel: funksjonell, sosial og emosjonell innvirkning. Dataelementet er satt til 0..* for å tillate at flere typer innvirkning kan trekkes ut i et templat om ønskelig. For hørselstap vil innvirkning kunne omfatte "Vansker med å høre i et stille miljø", "Vansker med å høre TV eller radio"; "Vansker med å høre gruppesamtaler" og "Vansker med å høre i telefon".</items>
      </items>
      <items code="at0156">
        <items id="text">Ingen effekt</items>
        <items id="description">Faktoren har ingen effekt på symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0158">
        <items id="text">Forverrer</items>
        <items id="description">Faktoren øker alvorlighet eller innvirkning av symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0159">
        <items id="text">Lindrer</items>
        <items id="description">Faktoren reduserer alvorligheten eller innvirkning av symptomet eller sykdomstegnet, men får det ikke til å opphøre fullstendig.</items>
      </items>
      <items code="at0161">
        <items id="text">Dato/tid for opphør</items>
        <items id="description">Dato/tid for opphør av denne episoden av symptomet eller sykdomstegnet.</items>
        <items id="comment">Brukes "Dato/tid for debut" og "Varighet" i systemer, kan dette dataelementet kalkuleres av systemet eller være overflødig. Ufullstendig dato er tillatt, nøyaktig dato og tid for opphør kan registreres om ønskelig.</items>
      </items>
      <items code="at0163">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om symptomet eller sykdomstegnet som ikke dekkes i andre felt.</items>
      </items>
      <items code="at0164">
        <items id="text">Debuttidspunkt</items>
        <items id="description">Tidspunkt for start og utvikling av symptomet eller sykdomstegnet.</items>
        <items id="comment">Debuttypen kan kodes med en terminologi om ønsket. For eksempel: Gradvis eller plutselig.</items>
      </items>
      <items code="at0165">
        <items id="text">Utløsende faktor</items>
        <items id="description">Detaljer om spesifikke faktorer som utløser symptomet eller sykdomstegnet.</items>
        <items id="comment">For eksempel: Å ligge flatt fører til sure oppstøt, eller å gå opp en bakke fører til beinsmerter.</items>
      </items>
      <items code="at0170">
        <items id="text">Faktor</items>
        <items id="description">Navn på helserelatert hendelse, symptom, rapportert sykdomstegn eller annen faktor.</items>
        <items id="comment">For eksempel: Debut av annet symptom, å ligge flatt, eller å gå opp en bakke.</items>
      </items>
      <items code="at0171">
        <items id="text">Tidsintervall</items>
        <items id="description">Tidsintervall mellom forekomst eller debut av faktoren og debut av symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0175">
        <items id="text">Episodisitet</items>
        <items id="description">Kategorisering av denne episoden av det identifiserte symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0176">
        <items id="text">Nytt</items>
        <items id="description">En ny episode av symptomet eller sykdomstegnet - enten den første forekomsten eller en ny forekomst der den tidligere episoden var fullstendig opphørt.</items>
      </items>
      <items code="at0177">
        <items id="text">Ubestemt</items>
        <items id="description">Det er ikke mulig å bestemme om denne forekomsten av symptomet er ny eller pågående.</items>
      </items>
      <items code="at0178">
        <items id="text">Kontinuerlig</items>
        <items id="description">Symptomet eller sykdomstegnet er kontinuerlig tilstedeværende, i praksis en enkelt pågående episode.</items>
      </items>
      <items code="at0180">
        <items id="text">Progresjon</items>
        <items id="description">Beskrivelse av symptomets eller sykdomstegnets progresjon ved rapporteringstidspunktet.</items>
        <items id="comment">Dataelementet er definert som 0..* for å tillate at flere typer progresjon trekkes ut i et templat om ønsket. For eksempel: alvorlighet eller frekvens. Tekst-datatypen er lagt til som et alternativ for å støtte andre verdisett enn det som er inkludert i arketypen.</items>
      </items>
      <items code="at0181">
        <items id="text">Forbedret</items>
        <items id="description">Symptomet eller sykdomstegnets alvorlighetsgrad er forbedret i løpet av denne episoden.</items>
      </items>
      <items code="at0182">
        <items id="text">Uendret</items>
        <items id="description">Symptomet eller sykdomstegnets alvorlighetsgrad er ikke endret i løpet av denne episoden.</items>
      </items>
      <items code="at0183">
        <items id="text">Forverret</items>
        <items id="description">Symptomet eller sykdomstegnets alvorighetsgrad har blitt forverret i løpet av denne episoden.</items>
      </items>
      <items code="at0184">
        <items id="text">Opphørt</items>
        <items id="description">Symptomet eller sykdomstegnets alvorlighetsgrad er opphørt i løpet av denne episoden.</items>
      </items>
      <items code="at0185">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse av faktorens effekt på det identifiserte symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0186">
        <items id="text">Forekomst</items>
        <items id="description">Type forekomst for dette symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0187">
        <items id="text">Første forekomst</items>
        <items id="description">Dette er den første forekomsten av dette symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0188">
        <items id="text">Tilbakefall</items>
        <items id="description">Ny forekomst av det samme symptomet eller sykdomstegnet etter at en tidligere episode var bedret.</items>
      </items>
      <items code="at0189">
        <items id="text">Karakter</items>
        <items id="description">Ord eller en kort frase som beskriver symptomets eller sykdomstegnets karakter.</items>
        <items id="comment">For eksempel: Smerte kan beskrives som "gnagende", "brennende" eller "som et elektrisk støt", mens en hodepine kan være "bankende" eller "konstant". Karakteren bør kodes med en terminologi, der det er mulig.</items>
      </items>
      <items code="at0190">
        <items id="text">Avsluttende faktor</items>
        <items id="description">Detaljer om spesifikke faktorer som får symptomet eller sykdomstegnet til å opphøre.</items>
        <items id="comment">For eksempel: vertikal posisjon stopper sure oppstøt, eller hvile får beinsmerter til å gå over.</items>
      </items>
      <items code="at0193">
        <items id="text">Faktor</items>
        <items id="description">Navn på helserelatert hendelse, symptom, rapportert sykdomstegn eller annen faktor.</items>
        <items id="comment">For eksempel: vertikal stilling, eller hvile.</items>
      </items>
      <items code="at0194">
        <items id="text">Faktordetaljer</items>
        <items id="description">Strukturerte detaljer om faktoren som er forbundet med det identifiserte symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0195">
        <items id="text">Tidsintervall</items>
        <items id="description">Tidsintervall mellom forekomst eller debut av faktoren og opphør av symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0196">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse av faktorens effekt på det identifiserte symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0197">
        <items id="text">Faktordetaljer</items>
        <items id="description">Strukturerte detaljer om faktoren som er forbundet med det identifiserte symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0198">
        <items id="text">Gradering av alvorlighet</items>
        <items id="description">Numerisk graderingsskala som representerer den overordnede alvorligheten til symptomet eller sykdomstegnet.</items>
        <items id="comment">Symptomets alvorlighet graderes av individet ved å registrere en skår for eksempel fra 0 (symptom ikke tilstede) til 10 (symptomet er så alvorlig som individet kan forestille seg).</items>
      </items>
      <items code="at0200">
        <items id="text">Nadir</items>
        <items id="description">Dato/tidspunkt da et monophasisk, progredierende symptom eller sykdomstegn nådde sin maksimale intensitet eller funksjonelle påvirkning.</items>
        <items id="comment">For eksempel tidspunktet da nevrologiske funn ved Guillain-Barrés sykdom var på sitt verste.</items>
      </items>
    </term_definitions>
    <term_definitions language="fi">
      <items code="at0000">
        <items id="text">Oire</items>
        <items id="description">Reported observation of a physical or mental disturbance in an individual.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">Oireen nimi</items>
        <items id="description">The name of the reported symptom or sign.(en)</items>
        <items id="comment">*Symptom name should be coded with a terminology, where possible.(en)</items>
      </items>
      <items code="at0002">
        <items id="text">Kuvaus</items>
        <items id="description">Narrative description about the reported symptom or sign.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">Malli</items>
        <items id="description">Narrative description about the pattern of the symptom or sign during this episode.(en)</items>
        <items id="comment">*For example: pain could be described as constant or intermittent.(en)</items>
      </items>
      <items code="at0017">
        <items id="text">Vaikutus</items>
        <items id="description">Perceived effect of the modifying factor on the symptom or sign.(en)</items>
      </items>
      <items code="at0018">
        <items id="text">Vaikuttajan kerroin</items>
        <items id="description">Detail about how a specific factor effects the identified symptom or sign during this episode.(en)</items>
      </items>
      <items code="at0019">
        <items id="text">Vaikuttaja</items>
        <items id="description">Name of the modifying factor.(en)</items>
        <items id="comment">*Examples of modifying factor: lying on multiple pillows, eating or administration of a specific medication.(en)</items>
      </items>
      <items code="at0021">
        <items id="text">Vakavuusasteikko</items>
        <items id="description">Category representing the overall severity of the symptom or sign.(en)</items>
        <items id="comment">*Defining values such as mild, moderate or severe in such a way that is applicable to multiple symptoms or signs plus allows multiple users to interpret and record them consistently is not easy. Some organisations extend the value set further with inclusion of additional values such as 'Trivial' and 'Very severe', and/or 'Mild-Moderate' and 'Moderate-Severe', adds to the definitional difficulty and may also worsen inter-recorder reliability issues. Use of 'Life-threatening' and 'Fatal' is also often considered as part of this value set, although from a pure point of view it may actually reflect an outcome rather than a severity. In view of the above, keeping to a well-defined but smaller list is preferred and so the mild/moderate/severe value set is offered, however the choice of other text allows for other value sets to be included at this data element in a template. (en)</items>
      </items>
      <items code="at0023">
        <items id="text">Vähäinen</items>
        <items id="description">The intensity of the symptom or sign does not cause interference with normal activity.(en)</items>
      </items>
      <items code="at0024">
        <items id="text">Kohtuullinen</items>
        <items id="description">The intensity of the symptom or sign causes interference with normal activity.(en)</items>
      </items>
      <items code="at0025">
        <items id="text">Vakava</items>
        <items id="description">The intensity of the symptom or sign causes prevents normal activity.(en)</items>
      </items>
      <items code="at0028">
        <items id="text">*Episode duration (en)</items>
        <items id="description">*The duration of this episode of the symptom or sign since initial onset. (en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Date/time of resolution' are used in systems, this data element may be calculated, or alternatively, be considered redundant in this scenario. The text data type is used for recording preset duration intervals such as '0-7 days, 1-2 weeks, 2 weeks or more'. (en)</items>
      </items>
      <items code="at0031">
        <items id="text">Aikasempien kohtauksien lukumäärä</items>
        <items id="description">The number of times this symptom or sign has previously occurred.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">Kohtauksen kuvaus</items>
        <items id="description">Narrative description about the course of the symptom or sign during this episode.(en)</items>
        <items id="comment">*For example: a text description of the immediate onset of the symptom, activities that worsened or relieved the symptom, whether it is improving or worsening and how it resolved over weeks.(en)</items>
      </items>
      <items code="at0056">
        <items id="text">Kuvaus</items>
        <items id="description">Narrative description of the effect of the modifying factor on the symptom or sign.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">Edellisen kohtausten kuvaus</items>
        <items id="description">Narrative description of any or all previous episodes.(en)</items>
        <items id="comment">*For example: frequency/periodicity - per hour, day, week, month, year; and regularity. May include a comparison to this episode.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">Liittyvä oire</items>
        <items id="description">Structured details about any associated symptoms or signs that are concurrent.(en)</items>
        <items id="comment">*In linked clinical systems, it is possible that associated symptoms or signs are already recorded within the EHR. Systems can allow the clinician to LINK to relevant associated symptoms/signs. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent associated symptoms/signs.(en)</items>
      </items>
      <items code="at0146">
        <items id="text">Edelliset kohtaukset</items>
        <items id="description">Structured details of the symptom or sign during a previous episode.(en)</items>
        <items id="comment">*In linked clinical systems, it is possible that previous episodes are already recorded within the EHR. Systems can allow the clinician to LINK to relevant previous episodes. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent previous episodes. It is recommended that new instances of the Symptom archetype inserted in this SLOT represent one or many previous episodes to this Symptom instance only.(en)</items>
      </items>
      <items code="at0147">
        <items id="text">Rakenteellinen kehon alue</items>
        <items id="description">Structured body site where the symptom or sign was reported.(en)</items>
        <items id="comment">*If the anatomical location is included in the Symptom name via precoordinated codes, use of this SLOT becomes redundant. If the anatomical location is recorded using the 'Body site' data element, then use of CLUSTER archetypes in this SLOT is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.(en)</items>
      </items>
      <items code="at0151">
        <items id="text">Kehon alue</items>
        <items id="description">Simple body site where the symptom or sign was reported.(en)</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple body sites to be separated out in a template if desired. This allows for representation of clinical scenarios where a symptom or sign needs to be recorded in multiple locations or identifying both the originating and distal site in pain radiation, but where all of the other attributes such as impact and duration are identical. If the requirements for recording the body site are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the Detailed anatomical location' SLOT in this archetype. &#xD;
If the anatomical location is included in the Symptom name via precoordinated codes, this data element becomes redundant.  If the anatomical location is recorded using the 'Structured body site' SLOT, then use of this data element is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.(en)</items>
      </items>
      <items code="at0152">
        <items id="text">Kohtauksen alku</items>
        <items id="description">The onset for this episode of the symptom or sign.(en)</items>
        <items id="comment">*While partial dates are permitted, the exact date and time of onset can be recorded, if appropriate. If this symptom or sign is experienced for the first time or is a re-occurrence, this date is used to represent the onset of this episode. If this symptom or sign is ongoing, this data element may be redundant if it has been recorded previously.(en)</items>
      </items>
      <items code="at0153">
        <items id="text">Ominaistiedot</items>
        <items id="description">Specific data elements that are additionally required to record as unique attributes of the identified symptom or sign.(en)</items>
        <items id="comment">*For example: CTCAE grading.(en)</items>
      </items>
      <items code="at0154">
        <items id="text">Vaikutustiedot</items>
        <items id="description">Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0155">
        <items id="text">Vaikutus</items>
        <items id="description">Description of the impact of this symptom or sign.(en)</items>
        <items id="comment">*Assessment of impact could consider the severity, duration and frequency of the symptom as well as the type of impact including, but not limited to, functional, social and emotional impact. Occurrences of this data element are set to 0..* to allow multiple types of impact to be separated out in a template if desired. Examples for functional impact from hearing loss may include: 'Difficulty Hearing in Quiet Environment'; 'Difficulty Hearing the TV or Radio'; 'Difficulty Hearing Group Conversation'; and 'Difficulty Hearing on Phone'.(en)</items>
      </items>
      <items code="at0156">
        <items id="text">Ei vaikutusta</items>
        <items id="description">The factor has no impact on the symptom or sign.(en)</items>
      </items>
      <items code="at0158">
        <items id="text">Pahentaa</items>
        <items id="description">The factor increases the severity or impact of the symptom or sign.(en)</items>
      </items>
      <items code="at0159">
        <items id="text">Helpottaa</items>
        <items id="description">The factor decreases the severity or impact of the symptom or sign, but does not fully resolve it.(en)</items>
      </items>
      <items code="at0161">
        <items id="text">Päättymisaika</items>
        <items id="description">The timing of the cessation of this episode of the symptom or sign.(en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Duration' are used in systems, this data element may be calculated, or alternatively, considered redundant. While partial dates are permitted, the exact date and time of resolution can be recorded, if appropriate.(en)</items>
      </items>
      <items code="at0163">
        <items id="text">Kommentti</items>
        <items id="description">Additional narrative about the symptom or sign not captured in other fields.(en)</items>
      </items>
      <items code="at0164">
        <items id="text">*Onset timing (en)</items>
        <items id="description">*Timing of the onset and development of the symptom or sign. (en)</items>
        <items id="comment">*The type of the onset can be coded with a terminology, if desired. For example: gradual; or sudden.(en)</items>
      </items>
      <items code="at0165">
        <items id="text">*Precipitating factor (en)</items>
        <items id="description">*Details about specified factors that are associated with the precipitation of the symptom or sign. (en)</items>
        <items id="comment">*For example: lying down leads to heartburn; or walking up a hill leads to claudication. (en)</items>
      </items>
      <items code="at0170">
        <items id="text">Vaikuttaja</items>
        <items id="description">Name of the health event, symptom, reported sign or other factor.(en)</items>
        <items id="comment">*For example: onset of another symptom; lying down; or walking up a hill. (en)</items>
      </items>
      <items code="at0171">
        <items id="text">Aikaväli</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and onset of the symptom or sign. (en)</items>
      </items>
      <items code="at0175">
        <items id="text">Jaksollisuus</items>
        <items id="description">Category of this episode for the identified symptom or sign.(en)</items>
      </items>
      <items code="at0176">
        <items id="text">Uusi</items>
        <items id="description">A new episode of the symptom or sign - either the first ever occurrence or a reoccurrence where the previous episode had completely resolved.(en)</items>
      </items>
      <items code="at0177">
        <items id="text">Epämääräinen</items>
        <items id="description">It is not possible to determine if this occurrence of the symptom or sign is new or ongoing.(en)</items>
      </items>
      <items code="at0178">
        <items id="text">Meneillään oleva</items>
        <items id="description">This symptom or sign is ongoing, effectively a single, continuous episode.(en)</items>
      </items>
      <items code="at0180">
        <items id="text">Progressio</items>
        <items id="description">Description progression of the symptom or sign at the time of reporting.(en)</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple types of progression to be separated out in a template if desired - for example, severity or frequency. The Text data type is added as an option, to support other value sets than the ones included in the archetype. (en)</items>
      </items>
      <items code="at0181">
        <items id="text">Parantuva</items>
        <items id="description">The severity of the symptom or sign has improved overall during this episode.(en)</items>
      </items>
      <items code="at0182">
        <items id="text">Ei muutosta</items>
        <items id="description">The severity of the symptom or sign has not changed overall during this episode.(en)</items>
      </items>
      <items code="at0183">
        <items id="text">Pahentuva</items>
        <items id="description">The severity of the symptom or sign has worsened overall during this episode.(en)</items>
      </items>
      <items code="at0184">
        <items id="text">Ratkaistu</items>
        <items id="description">The severity of the symptom or sign has resolved.(en)</items>
      </items>
      <items code="at0185">
        <items id="text">Kuvaus</items>
        <items id="description">Narrative description about the effect of the factor on the identified symptom or sign.(en)</items>
      </items>
      <items code="at0186">
        <items id="text">*Occurrence (en)</items>
        <items id="description">*Type of occurrence for this symptom or sign? (en)</items>
      </items>
      <items code="at0187">
        <items id="text">*First occurrence (en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign. (en)</items>
      </items>
      <items code="at0188">
        <items id="text">*Recurrence (en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign. (en)</items>
      </items>
      <items code="at0189">
        <items id="text">*Character (en)</items>
        <items id="description">*Word or short phrase describing the nature of the symptom or sign. (en)</items>
        <items id="comment">*For example: pain could be described as 'gnawing', 'burning', or 'like an electric shock'; a headache could be 'throbbing' or 'constant'. Coding with an external terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0190">
        <items id="text">*Resolving factor (en)</items>
        <items id="description">*Details about specified factors that are associated with the resolution of the symptom or sign. (en)</items>
        <items id="comment">*For example: upright posture stops heartburn; or resting stops claudication. (en)</items>
      </items>
      <items code="at0193">
        <items id="text">Vaikuttaja</items>
        <items id="description">Name of the health event, symptom, reported sign or other factor.(en)</items>
        <items id="comment">*For example: upright posture; or resting. (en)</items>
      </items>
      <items code="at0194">
        <items id="text">Vaikutustiedot</items>
        <items id="description">Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0195">
        <items id="text">Aikaväli</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and resolution of the symptom or sign. (en)</items>
      </items>
      <items code="at0196">
        <items id="text">Kuvaus</items>
        <items id="description">Narrative description about the effect of the factor on the identified symptom or sign.(en)</items>
      </items>
      <items code="at0197">
        <items id="text">Vaikutustiedot</items>
        <items id="description">Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0198">
        <items id="text">*Severity rating (en)</items>
        <items id="description">*Numerical rating scale representing the overall severity of the symptom or sign. (en)</items>
        <items id="comment">*Symptom severity can be rated by the individual by recording a score for example from 0 (ie symptom not present) to 10 (ie symptom is as severe as the individual can imagine). (en)</items>
      </items>
      <items code="at0200">
        <items id="text">*Nadir (en)</items>
        <items id="description">*Date/time when a monophasic, progressive symptom or sign reached its' maximal intensity or functional impact. (en)</items>
        <items id="comment">*For example: the date when neurological signs in Guillain-Barre disease was at its worst. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Symtom/Tecken</items>
        <items id="description">Rapporterat symtom eller observerat tecken på fysisk eller psykisk påverkan hos en individ.</items>
      </items>
      <items code="at0001">
        <items id="text">Namn på symtom/tecken</items>
        <items id="description">Namnet på det rapporterade symtomet eller tecknet.</items>
        <items id="comment">Koda om möjligt namnet på symtomet med en terminologi.</items>
      </items>
      <items code="at0002">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning av rapporterat symtom eller tecken.</items>
      </items>
      <items code="at0003">
        <items id="text">Mönster</items>
        <items id="description">Beskrivning av karakterisering och mönster av symtomet eller tecknet under denna episod.</items>
        <items id="comment">Exempelvis smärta som kan beskrivas som konstant eller återkommande.</items>
      </items>
      <items code="at0017">
        <items id="text">Effekt</items>
        <items id="description">Upplevd effekt av den påverkande faktorn på symtomet eller tecknet.</items>
      </items>
      <items code="at0018">
        <items id="text">Påverkande faktor</items>
        <items id="description">Beskrivning av hur en specifik faktor påverkar symtomet eller tecknet under denna episod.</items>
      </items>
      <items code="at0019">
        <items id="text">Faktor</items>
        <items id="description">Namn på den påverkande faktorn.</items>
        <items id="comment">Exempelvis att individen ligger på flera kuddar eller tillförs ett specifikt läkemedel.</items>
      </items>
      <items code="at0021">
        <items id="text">Svårighetsgrad</items>
        <items id="description">Symtomets eller tecknets svårighetsgrad.</items>
        <items id="comment">Det är inte lätt att göra en gradering såsom mild, måttlig eller svår på ett sätt som är tillämpligt på flera symtom eller tecken samt utforma dem så att flera användare kan tolka och registrera dem på ett konsekvent sätt. Vissa organisationer utökar alternativen ytterligare genom att inkludera fler steg som "Obetydlig" och "Mycket allvarlig" eller "Mild-måttlig" och "Måttlig-svår", vilket ökar definitionssvårigheterna och kan också försämra tillförlitligheten mellan olika bedömare. Användning av "Livshotande" och "Dödlig" betraktas också ofta som en del av denna skala, även om det mer speglar ett resultat snarare än en en svårighetsgrad. Mot denna bakgrund är det att föredra att hålla sig till en kortare men väldefinierad lista som skalan med mild/måttlig/svår erbjuder. Möjligheten kvarstår dock att inkludera ytterligare värden i detta datafält i en template.</items>
      </items>
      <items code="at0023">
        <items id="text">Mild</items>
        <items id="description">Intensiteten av symtomet eller tecknet påverkar inte normal livsföring.</items>
      </items>
      <items code="at0024">
        <items id="text">Måttlig</items>
        <items id="description">Intensiteten av symtmet eller tecknet påverkar normal livsföring.</items>
      </items>
      <items code="at0025">
        <items id="text">Svår</items>
        <items id="description">Intensiteten av symtomet eller tecknet hindrar normal livsföring.</items>
      </items>
      <items code="at0028">
        <items id="text">Episodens duration</items>
        <items id="description">Varaktigheten av nuvarande episod med symtomet eller tecknet sedan debut.</items>
        <items id="comment">Om "Episodens start" och "Tidpunkt för upphörande" används i IT-system, kan detta datafält beräknas, eller alternativt betraktas som överflödigt i detta scenario. Datatypen text används för att fånga förinställda intervall för varaktighet som 0-7 dagar, 1-2 veckor, 2 veckor eller mer.</items>
      </items>
      <items code="at0031">
        <items id="text">Antal tidigare episoder</items>
        <items id="description">Antal gånger som symtomet eller tecknet har förekommit tidigare.</items>
      </items>
      <items code="at0037">
        <items id="text">Beskrivning av episoden</items>
        <items id="description">Beskrivning av förloppet för symtomet eller tecknet under denna episod.</items>
        <items id="comment">Exempelvis en beskrivning av symtomdebut, aktiviteter som ger symtomförsämring eller förbättring, på vilket sätt som förbättring eller försämring sker och hur det försvinner över tid.</items>
      </items>
      <items code="at0056">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning av den påverkande faktorns effekt på symtomet eller tecknet.</items>
      </items>
      <items code="at0057">
        <items id="text">Beskrivning av tidigare episoder</items>
        <items id="description">Beskrivning av en eller flera tidigare episoder.</items>
        <items id="comment">Exempelvis frekvens eller periodicitet såsom per timme, dag, vecka, månad, år och eventuell regelbundenhet. Beskrivningen kan även innehålla en jämförelse med aktuell episod.</items>
      </items>
      <items code="at0063">
        <items id="text">Associerade symtom/tecken</items>
        <items id="description">Strukturerad beskrivning av eventuella samtidiga associerade symtom eller tecken.</items>
        <items id="comment">I kliniska system med länkningsmöjlighet är det möjligt att associerade symtom eller tecken redan har registrerats i patientjournalen. System kan låta vårdpersonalen länka till relevanta associerade symtom och tecken. Däremot i ett system eller i meddelanden utan länkningsmöjlighet till befintliga data eller med en ny patient, kan ytterligare fall av Symtom/Tecken-arketypen ingå för att presentera associerade symtom och tecken.</items>
      </items>
      <items code="at0146">
        <items id="text">Tidigare episoder</items>
        <items id="description">Strukturerad beskrivning av symtomet eller tecknet som förekommit under en tidigare episod.</items>
        <items id="comment">I länkade kliniska system är det möjligt att tidigare episoder redan har registrerats i patientjournalen. System kan låta vårdpersonalen länka till relevanta tidigare episoder (med dataypen LINK). Men i ett system eller meddelande utan länkningsmöjlighet till befintlig data eller med en ny patient, kan ytterligare användningsfall av Symtom/Tecken-arketypen ingå, för att beskriva tidigare episoder. Det rekommenderas att nya exempel med Symtom/Tecken-arketypen som förs in i denna SLOT presenterar en eller flera tidigare episoder kopplade till det aktuella symtomet.</items>
      </items>
      <items code="at0147">
        <items id="text">Strukturerad kroppslokalisation</items>
        <items id="description">Strukturerad lokalisation på kroppen där symtomen eller tecknet uppvisats.</items>
        <items id="comment">Om kroppslokalisationen ingår i "Namnet på symtomet eller tecknet" genom prekoordinerade koder blir det här datafältet överflödigt. &#xD;
Om kroppslokalisation beskrivs i datafältet "Kroppslokalisation" är det inte tillåtet att använda CLUSTER-arketyper i det här datafältet. Registrera antingen i "Kroppslokalisation" eller i "Strukturerad kroppslokalisation", men använd inte båda datafälten.</items>
      </items>
      <items code="at0151">
        <items id="text">Kroppslokalisation</items>
        <items id="description">Lokalisation på kroppen där symtomet eller tecknet uppvisats.</items>
        <items id="comment">Det här datafältet kan repeteras, förekomst 0.. *, för att tillåta att flera kroppslokalisationer kan anges separat i en template, om så önskas. Detta möjliggör dokumentation av kliniska användningsfall där ett symtom eller tecken kan förekomma på flera ställen samtidigt eller för att identifiera både start- och slutpunkter för en utstrålande smärta, samtidigt som andra aspekter som svårighetsgrad och varaktighet är identiska.&#xD;
Om kraven för att registrera kroppslokalisationer kan genereras automatiskt av vissa IT-system, eller om dokumentationskraven för lokalisationen är mer komplex (som att ange den relativa lokalisationen), använd då arketyperna CLUSTER.anatomical_location eller CLUSTER.relative_location inom datafältet SLOT för "Strukturerad kroppslokalisation" i den här arketypen.&#xD;
&#xD;
Om kroppslokalisationen ingår i "Namnet på symtomet eller tecknet" genom prekoordinerade koder blir det här datafältet överflödigt. &#xD;
Om kroppslokalisationen beskrivs i datafältet SLOT för "Strukturerad kroppslokalisation", är det inte tillåtet att använda detta fält. Registrera alltså endast i "Kroppslokalisation" ELLER i "Strukturerad kroppslokalisation", inte i båda datafälten.</items>
      </items>
      <items code="at0152">
        <items id="text">Episodens start</items>
        <items id="description">Start för nuvarande episod med symtomet eller tecknet.</items>
        <items id="comment">Även om partiella datum är tillåtna, kan det exakta datumet och tiden för start registreras, om så är lämpligt. Om detta symtom eller tecken upplevs för första gången eller återkommer, används detta datum för att representera starten på denna episod. Om detta symtom eller tecken pågår kan detta datafält vara överflödigt om det har registrerats tidigare.</items>
      </items>
      <items code="at0153">
        <items id="text">Specifika detaljer</items>
        <items id="description">Ytterligare specifika datafält som kan krävas för att fånga unika egenskaper för aktuellt symtom eller tecken.</items>
        <items id="comment">Exempelvis CTCAE-skattning (skattning av svårighetsgrad).</items>
      </items>
      <items code="at0154">
        <items id="text">Detaljer om faktor</items>
        <items id="description">Strukturerad beskrivning av den faktor som är kopplad till aktuellt symtom eller tecken.</items>
      </items>
      <items code="at0155">
        <items id="text">Påverkan</items>
        <items id="description">Beskrivning av vilken påverkan detta symptom eller tecken medför.</items>
        <items id="comment">Vid bedömningen av påverkan kan olika faktorer ingå som symtomets svårighetsgrad, varaktighet och frekvens samt typen av påverkan inklusive, men inte begränsat till, funktionell, social och emotionell påverkan. Förekomster av detta datafält är inställt på 0..*, vilket tillåter att flera typer av påverkan kan separeras i en template, om så önskas. Exempel på funktionell påverkan av en hörselnedsättning kan vara hörselsvårigheter i tyst miljö, svårigheter att höra TV eller radio, svårigheter att höra gruppsamtal eller svårigheter att höra i telefon.</items>
      </items>
      <items code="at0156">
        <items id="text">Ingen effekt</items>
        <items id="description">Faktorn har ingen påverkan på symtomet eller tecknet.</items>
      </items>
      <items code="at0158">
        <items id="text">Förvärrande</items>
        <items id="description">Faktorn ökar svårighetsgraden eller effekten av symtomet eller tecknet.</items>
      </items>
      <items code="at0159">
        <items id="text">Lindrande</items>
        <items id="description">Faktorn minskar svårighetsgraden eller påverkan på symtomet eller tecknet, men leder inte till fullständig lindring.</items>
      </items>
      <items code="at0161">
        <items id="text">Tidpunkt för upphörande</items>
        <items id="description">Tidpunkten då denna episod av symtom eller tecken har upphört.</items>
        <items id="comment">Om "Episodens start" och "Episodens duration" har använts i systemen, kan detta datafält beräknas alternativt betraktas som överflödigt. Partiella datum och tidsuppgifter är tillåtna, men om det är möjligt och lämpligt kan exakt datum och tid för symtomfrihet registreras.</items>
      </items>
      <items code="at0163">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligare beskrivning av symtom eller tecken som inte registrerats i andra datafält.</items>
      </items>
      <items code="at0164">
        <items id="text">Tidpunkt för debut</items>
        <items id="description">Tidpunkten för debuten och utvecklingen av symtomet eller tecknet.</items>
        <items id="comment">Typ av debut kan kodas med en terminologi. Exempelvis gradvis eller plötslig.</items>
      </items>
      <items code="at0165">
        <items id="text">Utlösande faktor</items>
        <items id="description">Beskrivning av specifika faktorer som kan associeras med att symtomet eller tecknet utlöses.</items>
        <items id="comment">Exempelvis att ligga ner leder till halsbränna eller att gå uppför en kulle leder till krampsmärta i vaderna (claudicatio).</items>
      </items>
      <items code="at0170">
        <items id="text">Faktor</items>
        <items id="description">Namn på hälsotillstånd, symtom, uppvisat tecken eller annan faktor.</items>
        <items id="comment">Exempelvis uppkomst av ett annat symtom, att lägga sig ner eller gå uppför en kulle.</items>
      </items>
      <items code="at0171">
        <items id="text">Tidsintervall</items>
        <items id="description">Tidsintervallet mellan uppkomst av faktorn och uppkomst av symtomet eller tecknet.</items>
      </items>
      <items code="at0175">
        <items id="text">Episodicitet</items>
        <items id="description">Status för episodicitet av symtomet eller tecknet.</items>
      </items>
      <items code="at0176">
        <items id="text">Ny</items>
        <items id="description">En ny episod av symtomet eller tecknet, antingen som debutsymtom eller som återfall, där den föregående episoden redan har upphört.</items>
      </items>
      <items code="at0177">
        <items id="text">Obestämd</items>
        <items id="description">Det är inte möjligt att avgöra om denna förekomst av symtomet eller tecknet är nytt eller pågående.</items>
      </items>
      <items code="at0178">
        <items id="text">Pågående</items>
        <items id="description">Symtomet eller tecknet är pågående, registrerat som en enskild sammanhängande episod.</items>
      </items>
      <items code="at0180">
        <items id="text">Progression</items>
        <items id="description">Beskrivning av den stegvisa utvecklingen av symtomet eller tecknet vid tidpunkten för rapportering.</items>
        <items id="comment">Förekomster av detta datafält är satt till 0..* för att tillåta flera typer av utveckling och kan separeras i en template om så önskas, till exempel svårighetsgrad eller frekvens. Datatypen Text läggs till som ett alternativ för att stödja andra skalor än de som ingår i arketypen.</items>
      </items>
      <items code="at0181">
        <items id="text">Förbättrat</items>
        <items id="description">Svårighetsgraden av symtomet eller tecknet har förbättrats under denna episod.</items>
      </items>
      <items code="at0182">
        <items id="text">Oförändrat</items>
        <items id="description">Svårighetsgraden av symtomet eller tecknet har inte förändrats under denna episod.</items>
      </items>
      <items code="at0183">
        <items id="text">Försämrat</items>
        <items id="description">Svårighetsgraden av symtomet eller tecknet har förvärrats under denna episod.</items>
      </items>
      <items code="at0184">
        <items id="text">Upphört</items>
        <items id="description">Symtomet eller tecknet har upphört.</items>
      </items>
      <items code="at0185">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning av faktorns effekt på identifierat symtom eller tecken.</items>
      </items>
      <items code="at0186">
        <items id="text">Förekomst</items>
        <items id="description">Typ av förekomst av symtomet eller tecknet.</items>
      </items>
      <items code="at0187">
        <items id="text">Första tillfället</items>
        <items id="description">Första förekomst någonsin av symtomet eller tecknet.</items>
      </items>
      <items code="at0188">
        <items id="text">Upprepning</items>
        <items id="description">Ny förekomst av samma symtom eller tecken efter att en tidigare episod har upphört.</items>
      </items>
      <items code="at0189">
        <items id="text">Karakterisering</items>
        <items id="description">Ord eller kort fras som beskriver symtomets (eller tecknets) egenskaper.</items>
        <items id="comment">Exempelvis smärta kan beskrivas som "gnagande", "brännande" eller "som en elektrisk stöt". Huvudvärk kan vara "bultande" eller "konstant". Koda om möjligt med extern terminologi.</items>
      </items>
      <items code="at0190">
        <items id="text">Upphävande faktor</items>
        <items id="description">Detaljer om specificerade faktorer som är associerade med att symtomet eller tecknet försvinner.</items>
        <items id="comment">Exempelvis att upprätt hållning stoppar halsbrännan eller att en vilopaus upphäver krampsmärta i vaderna (claudicatio).</items>
      </items>
      <items code="at0193">
        <items id="text">Faktor</items>
        <items id="description">Namn på hälsotillstånd, symtom, uppvisat tecken eller annan faktor.</items>
        <items id="comment">Exempelvis upprätt hållning eller vila.</items>
      </items>
      <items code="at0194">
        <items id="text">Detaljer om faktor</items>
        <items id="description">Strukturerad beskrivning av den faktor som är kopplad till aktuellt symtom eller tecken.</items>
      </items>
      <items code="at0195">
        <items id="text">Tidsintervall</items>
        <items id="description">Tidsintervallet mellan uppkomsten av faktorn och att symtomet eller tecknet försvinner.</items>
      </items>
      <items code="at0196">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning av effekten av faktorn på identifierat symtom eller tecken.</items>
      </items>
      <items code="at0197">
        <items id="text">Detaljer om faktor</items>
        <items id="description">Strukturerad beskrivning av den faktor som är kopplad till symtomet eller tecknet.</items>
      </items>
      <items code="at0198">
        <items id="text">Skattning av svårighetsgrad</items>
        <items id="description">Numerisk bedömningsskala av svårighetsgraden av symtomet eller tecknet.</items>
        <items id="comment">Symtomets svårighetsgrad kan bedömas av individen själv genom att registrera ett steg på en skala, till exempel från 0 (dvs. symtom saknas) till 10 (dvs. symtomet är så allvarligt som individen kan föreställa sig).</items>
      </items>
      <items code="at0200">
        <items id="text">Maximal symtomintensitet</items>
        <items id="description">Datum eller tidpunkt då ett monofasiskt, progressivt symtom eller tecken nådde sin maximala intensitet eller funktionella effekt.</items>
        <items id="comment">Exempelvis det datum då neurologiska symtom vid Guillain-Barres sjukdom var som mest intensiva.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Sintoma/sinal</items>
        <items id="description">Observação de um distúrbio físico ou mental relatada em um indivíduo.</items>
      </items>
      <items code="at0001">
        <items id="text">Nome do sintoma/sinal</items>
        <items id="description">O nome do sintoma ou sinal relatado.</items>
        <items id="comment">Nome do sintoma deve ser codificado com uma terminologia, se possível.</items>
      </items>
      <items code="at0002">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o sintoma ou sinal relatado.</items>
      </items>
      <items code="at0003">
        <items id="text">Padrão</items>
        <items id="description">Descrição narrativa sobre o padrão do sintoma ou sinal durante este episódio.</items>
        <items id="comment">Por exemplo: dor pode ser descrita como constante ou intermitente.</items>
      </items>
      <items code="at0017">
        <items id="text">Efeito</items>
        <items id="description">Efeito percebido do fator modificador sobre o sintoma ou sinal.</items>
      </items>
      <items code="at0018">
        <items id="text">Fator modificador</items>
        <items id="description">Detalhe sobre como um fator específico afeta o sintoma ou sinal identificado durante este episódio.</items>
      </items>
      <items code="at0019">
        <items id="text">Fator</items>
        <items id="description">Nome do fator modificador.</items>
        <items id="comment">Exemplos de fatores modificadores: deitar sobre múltiplos travesseiros, comer ou administração de um medicamento específico.</items>
      </items>
      <items code="at0021">
        <items id="text">Categoria de gravidade</items>
        <items id="description">Categoria representando a gravidade geral do sintoma ou sinal.</items>
        <items id="comment">*Defining values such as mild, moderate or severe in such a way that is applicable to multiple symptoms or signs plus allows multiple users to interpret and record them consistently is not easy. Some organisations extend the value set further with inclusion of additional values such as 'Trivial' and 'Very severe', and/or 'Mild-Moderate' and 'Moderate-Severe', adds to the definitional difficulty and may also worsen inter-recorder reliability issues. Use of 'Life-threatening' and 'Fatal' is also often considered as part of this value set, although from a pure point of view it may actually reflect an outcome rather than a severity. In view of the above, keeping to a well-defined but smaller list is preferred and so the mild/moderate/severe value set is offered, however the choice of other text allows for other value sets to be included at this data element in a template. (en)</items>
      </items>
      <items code="at0023">
        <items id="text">Leve</items>
        <items id="description">A intensidade do sintoma ou sinal não causa interferência com a atividade normal.</items>
      </items>
      <items code="at0024">
        <items id="text">Moderada</items>
        <items id="description">A intensidade do sintoma ou sinal causa interferência com a atividade normal.</items>
      </items>
      <items code="at0025">
        <items id="text">Grave</items>
        <items id="description">A intensidade do sintoma ou sinal impede a atividade normal.</items>
      </items>
      <items code="at0028">
        <items id="text">*Episode duration (en)</items>
        <items id="description">*The duration of this episode of the symptom or sign since initial onset. (en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Date/time of resolution' are used in systems, this data element may be calculated, or alternatively, be considered redundant in this scenario. The text data type is used for recording preset duration intervals such as '0-7 days, 1-2 weeks, 2 weeks or more'. (en)</items>
      </items>
      <items code="at0031">
        <items id="text">Número de episódios prévios</items>
        <items id="description">O número de vezes que este sintoma ou sinal cocorreu previamente.</items>
      </items>
      <items code="at0037">
        <items id="text">Descrição do episódio</items>
        <items id="description">Descrição narrativa sobre o curso do sintoma ou sinal durante o episódio.</items>
        <items id="comment">Por exemplo: uma descrição em texto do início imediato do sintoma, atividades que pioram ou aliviam o sintoma, se está melhorando ou piorando e como se resolveu ao longo de semanas.</items>
      </items>
      <items code="at0056">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa do efeito do fato modificador no sintoma ou sinal.</items>
      </items>
      <items code="at0057">
        <items id="text">Descrição de episódios prévios</items>
        <items id="description">Descrição narrativa de alguns ou todos os episódios prévios.</items>
        <items id="comment">Por exemplo: frequência/periodicidade - por hora, dia, semana, mês, ano; e regularidade. Pode incluir uma comparação com o episódio atual.</items>
      </items>
      <items code="at0063">
        <items id="text">Sintoma/sinal associado</items>
        <items id="description">Detalhes estruturados sobre quaisquer sintomas ou sinais associados que sejam concorrentes.</items>
        <items id="comment">Em sistemas clínicos concatenados, é possível que sintomas ou sinais associados já estejam registrados no PEP. O sistema pode permitir que o clínico relacione com sintomas e sinais associados. Entretanto em um sistema ou mensagem sem este relacionamento com dados existentes ou com um novo paciente, instâncias adicionais do arquétipo de sintoma podem ser incluídas para representar sintomas ou sinais associados.</items>
      </items>
      <items code="at0146">
        <items id="text">Episódios prévios</items>
        <items id="description">Detalhes estruturados do sintoma ou sinal durante um episódio prévio.</items>
        <items id="comment">Em sistemas clínicos concatenados, é possível que episódios prévios já etejam registrados no PEP. O sistema pode permitir que o clínico relacione este a episódios relevantes prévios. Entretanto em um sistema ou mensagem sem este relacionamento com dados existentes ou com um novo paciente, instâncias adicionais do arquétipo de sintoma podem ser incluídas para representar episódios prévios. É recomendado que novas instâncias do arquétipo de Sintomas inseridas neste SLOT representem um ou vários episódios prévios relacionados à esta instância.</items>
      </items>
      <items code="at0147">
        <items id="text">Parte do corpo estruturada</items>
        <items id="description">Parte do corpo estruturada em que o sintoma ou sinal foi relatado.</items>
        <items id="comment">Se a localização anatômica estiver incluída no nome do Sintoma através de códigos pré-coordenados, a utilização deste SLOT torna-se redundante. Se a localização anatômica for registrada utilizando o elemento de dado 'Parte do corpo', então o uso de arquétipos CLUSTER neste SLOT não é permitido - registre apenas o 'Parte do corpo' simples ou 'Parte do corpo estruturada' mas não ambos.</items>
      </items>
      <items code="at0151">
        <items id="text">Parte do corpo</items>
        <items id="description">Parte do corpo em que o sintoma ou sinal foi relatado.</items>
        <items id="comment">Ocorrências deste elemento de dado são ajustadas de 0..* para permitir múltiplas partes do corpo para serem separadas num template se desejado. Isto permite a representação de cenários clínicos em que o sintoma ou sinal precise ser registrado em múltiplas localizações ou identificar tanto local original e local distante de irradiação de dor, mas em que todos os outros atributos como o impacto e duração são idênticos. Se os requerimntos para registro da parte do corpo for determinado em tempo real pela aplicação ou requeira modelagem mais complexa como localizações relativas então utilize CLUSTER.anatomical_location ou CLUSTER.relative_location no SLOT 'Localização anatômica detalhada' neste arquétipo.&#xD;
Se a localização anatômica estiver incluída no nome do Sintoma através de códigos pré-coordenados, este elemento de dado torna-se redundante. Se a localização anatômica for registrada utilizando o SLOT 'Parte do corpo estruturada', então a utilização deste elemento de dado não é permitida - registre apenas o 'Parte do corpo' simples ou 'Parte do corpo estruturada', mas não ambos.</items>
      </items>
      <items code="at0152">
        <items id="text">Início do episódio</items>
        <items id="description">O início para este epsiódio de sintoma ou sinal.</items>
        <items id="comment">Datas parciais são permitidas, a data e hora exata do início pode ser registrada, se apropriado. Se este sintoma ou sinal for experimentado pela primeira ou se for uma recorrência, esta data é utilizada para representar o início deste episódio. Se o sintoma ou sinal estiver em curso, este elemento de dado pode ser redundante se já tiver sido registrado anteriormente.</items>
      </items>
      <items code="at0153">
        <items id="text">Detalhes específicos</items>
        <items id="description">Elementos de dados específicos que são necessários adicionar para registrar atributos exclusivos do sintoma ou sinal identificado.</items>
        <items id="comment">Por exemplo: graduação CTCAE.</items>
      </items>
      <items code="at0154">
        <items id="text">Dealhes do fator</items>
        <items id="description">Detalhe estruturado sobre o fator associado com o sintoma ou sinal identificado.</items>
      </items>
      <items code="at0155">
        <items id="text">Impacto</items>
        <items id="description">Descrição do impacto deste sintoma ou sinal.</items>
        <items id="comment">Avaliação do impacto pode considerar a gravidade, duração e frequência do sintoma ou sinal como também o tipo de impacto incluindo, mas limitado a, impacto funcional, social e emocional. Ocorrências deste elemento de dado são setadas para 0..* para permitir múltiplos tipos de impacto para serem separados no template se desejado. Exemplos de impacto funcional para perda auditiva podem incluir: 'Dificuldade de audição em ambiente quieto'; 'Dificuldade para ouvir rádio e TV'; 'Dificuldade de audição para conversa em grupo' e 'Dificuldade de audição ao telefone'.</items>
      </items>
      <items code="at0156">
        <items id="text">Sem efeito</items>
        <items id="description">O fator não tem impacto no sintoma ou sinal.</items>
      </items>
      <items code="at0158">
        <items id="text">Piora</items>
        <items id="description">O fator aumenta a gravidade ou impacto do sintoma ou sinal.</items>
      </items>
      <items code="at0159">
        <items id="text">Alivia</items>
        <items id="description">O fator diminui a gravidade ou impacto do sintoma ou sinal mas não resolve completamente.</items>
      </items>
      <items code="at0161">
        <items id="text">Data/hora de resolução</items>
        <items id="description">O momento de cessação deste episódio de sintoma ou sinal.</items>
        <items id="comment">Se 'Data/hora de início' e 'Duração' são utilizados no sistema, este elemento de dado pode ser calculado, ou alternativamente, considerado redundante. Datas parciais são permitidas, a data e hora exatas de resolução podem ser registradas, se apropriado.</items>
      </items>
      <items code="at0163">
        <items id="text">Comentários</items>
        <items id="description">Narrativa adicional sobre o sintoma ou sinal não capturada em outros campos.</items>
      </items>
      <items code="at0164">
        <items id="text">*Onset timing (en)</items>
        <items id="description">*Timing of the onset and development of the symptom or sign. (en)</items>
        <items id="comment">O tipo de início pode ser codificado utilizando uma terminologia, se desejado. Por exemplo: gradual; ou súbito.</items>
      </items>
      <items code="at0165">
        <items id="text">*Precipitating factor (en)</items>
        <items id="description">*Details about specified factors that are associated with the precipitation of the symptom or sign. (en)</items>
        <items id="comment">*For example: lying down leads to heartburn; or walking up a hill leads to claudication. (en)</items>
      </items>
      <items code="at0170">
        <items id="text">Fator</items>
        <items id="description">Nome do evento de saúde, sintoma, sinal relatado ou outro fator.</items>
        <items id="comment">*For example: onset of another symptom; lying down; or walking up a hill. (en)</items>
      </items>
      <items code="at0171">
        <items id="text">Intervalo de tempo</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and onset of the symptom or sign. (en)</items>
      </items>
      <items code="at0175">
        <items id="text">Episodicidade</items>
        <items id="description">Categoria deste episódio para o sintoma ou sinal identificado.</items>
      </items>
      <items code="at0176">
        <items id="text">Novo</items>
        <items id="description">Um episódio novo de sintoma ou sinal - tanto para primeira ocorrência como para uma reccorrência quando o episódio prévio estiver completamente resolvido.</items>
      </items>
      <items code="at0177">
        <items id="text">Indeterminado</items>
        <items id="description">Não é possível determinar se esta ocorrência de sintoma ou sinal é nova ou em curso.</items>
      </items>
      <items code="at0178">
        <items id="text">Em curso</items>
        <items id="description">O sintoma ou sinal está em curso, efetivamente um episódio único e contínuo.</items>
      </items>
      <items code="at0180">
        <items id="text">Progressão</items>
        <items id="description">Descrição da progressão do sintoma ou sinal no momento do relato.</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple types of progression to be separated out in a template if desired - for example, severity or frequency. The Text data type is added as an option, to support other value sets than the ones included in the archetype. (en)</items>
      </items>
      <items code="at0181">
        <items id="text">Melhorando</items>
        <items id="description">O gravidade do sintoma ou sinal melhorou ao longo deste episódio.</items>
      </items>
      <items code="at0182">
        <items id="text">Imutável</items>
        <items id="description">O gravidade do sintoma ou sinal não mudou ao longo deste episódio.</items>
      </items>
      <items code="at0183">
        <items id="text">Piorando</items>
        <items id="description">O gravidade do sintoma ou sinal piorou ao longo deste episódio.</items>
      </items>
      <items code="at0184">
        <items id="text">Resolvido</items>
        <items id="description">A gravidade do sintoma ou sinal resolveu-se.</items>
      </items>
      <items code="at0185">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o efeito do fator no sintoma ou sinal identificado.</items>
      </items>
      <items code="at0186">
        <items id="text">*Occurrence (en)</items>
        <items id="description">*Type of occurrence for this symptom or sign? (en)</items>
      </items>
      <items code="at0187">
        <items id="text">*First occurrence (en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign. (en)</items>
      </items>
      <items code="at0188">
        <items id="text">*Recurrence (en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign. (en)</items>
      </items>
      <items code="at0189">
        <items id="text">*Character (en)</items>
        <items id="description">*Word or short phrase describing the nature of the symptom or sign. (en)</items>
        <items id="comment">*For example: pain could be described as 'gnawing', 'burning', or 'like an electric shock'; a headache could be 'throbbing' or 'constant'. Coding with an external terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0190">
        <items id="text">*Resolving factor (en)</items>
        <items id="description">*Details about specified factors that are associated with the resolution of the symptom or sign. (en)</items>
        <items id="comment">*For example: upright posture stops heartburn; or resting stops claudication. (en)</items>
      </items>
      <items code="at0193">
        <items id="text">Fator</items>
        <items id="description">Nome do evento de saúde, sintoma, sinal relatado ou outro fator.</items>
        <items id="comment">*For example: upright posture; or resting. (en)</items>
      </items>
      <items code="at0194">
        <items id="text">Dealhes do fator</items>
        <items id="description">Detalhe estruturado sobre o fator associado com o sintoma ou sinal identificado.</items>
      </items>
      <items code="at0195">
        <items id="text">Intervalo de tempo</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and resolution of the symptom or sign. (en)</items>
      </items>
      <items code="at0196">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o efeito do fator no sintoma ou sinal identificado.</items>
      </items>
      <items code="at0197">
        <items id="text">Dealhes do fator</items>
        <items id="description">Detalhe estruturado sobre o fator associado com o sintoma ou sinal identificado.</items>
      </items>
      <items code="at0198">
        <items id="text">*Severity rating (en)</items>
        <items id="description">*Numerical rating scale representing the overall severity of the symptom or sign. (en)</items>
        <items id="comment">*Symptom severity can be rated by the individual by recording a score for example from 0 (ie symptom not present) to 10 (ie symptom is as severe as the individual can imagine). (en)</items>
      </items>
      <items code="at0200">
        <items id="text">*Nadir (en)</items>
        <items id="description">*Date/time when a monophasic, progressive symptom or sign reached its' maximal intensity or functional impact. (en)</items>
        <items id="comment">*For example: the date when neurological signs in Guillain-Barre disease was at its worst. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="nl">
      <items code="at0000">
        <items id="text">Symptoom</items>
        <items id="description">Vastgestelde observatie van een fysieke of mentale afwijking bij een individu.</items>
      </items>
      <items code="at0001">
        <items id="text">Naam van het symptoom</items>
        <items id="description">De naam van het vastgelegde symptoom</items>
        <items id="comment">*Symptom name should be coded with a terminology, where possible.(en)</items>
      </items>
      <items code="at0002">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the reported symptom or sign.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">*Pattern(en)</items>
        <items id="description">*Narrative description about the pattern of the symptom or sign during this episode.(en)</items>
        <items id="comment">*For example: pain could be described as constant or intermittent.(en)</items>
      </items>
      <items code="at0017">
        <items id="text">*Effect(en)</items>
        <items id="description">*Perceived effect of the modifying factor on the symptom or sign.(en)</items>
      </items>
      <items code="at0018">
        <items id="text">*Modifying factor(en)</items>
        <items id="description">*Detail about how a specific factor effects the identified symptom or sign during this episode.(en)</items>
      </items>
      <items code="at0019">
        <items id="text">*Factor(en)</items>
        <items id="description">*Name of the modifying factor.(en)</items>
        <items id="comment">*Examples of modifying factor: lying on multiple pillows, eating or administration of a specific medication.(en)</items>
      </items>
      <items code="at0021">
        <items id="text">*Severity category(en)</items>
        <items id="description">*Category representing the overall severity of the symptom or sign.(en)</items>
        <items id="comment">*Defining values such as mild, moderate or severe in such a way that is applicable to multiple symptoms or signs plus allows multiple users to interpret and record them consistently is not easy. Some organisations extend the value set further with inclusion of additional values such as 'Trivial' and 'Very severe', and/or 'Mild-Moderate' and 'Moderate-Severe', adds to the definitional difficulty and may also worsen inter-recorder reliability issues. Use of 'Life-threatening' and 'Fatal' is also often considered as part of this value set, although from a pure point of view it may actually reflect an outcome rather than a severity. In view of the above, keeping to a well-defined but smaller list is preferred and so the mild/moderate/severe value set is offered, however the choice of other text allows for other value sets to be included at this data element in a template.(en)</items>
      </items>
      <items code="at0023">
        <items id="text">*Mild(en)</items>
        <items id="description">*The intensity of the symptom or sign does not cause interference with normal activity.(en)</items>
      </items>
      <items code="at0024">
        <items id="text">*Moderate(en)</items>
        <items id="description">*The intensity of the symptom or sign causes interference with normal activity.(en)</items>
      </items>
      <items code="at0025">
        <items id="text">*Severe(en)</items>
        <items id="description">*The intensity of the symptom or sign causes prevents normal activity.(en)</items>
      </items>
      <items code="at0028">
        <items id="text">*Episode duration(en)</items>
        <items id="description">*The duration of this episode of the symptom or sign since initial onset.(en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Date/time of resolution' are used in systems, this data element may be calculated, or alternatively, be considered redundant in this scenario. The text data type is used for recording preset duration intervals such as '0-7 days, 1-2 weeks, 2 weeks or more'.(en)</items>
      </items>
      <items code="at0031">
        <items id="text">*Number of previous episodes(en)</items>
        <items id="description">*The number of times this symptom or sign has previously occurred.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Episode description(en)</items>
        <items id="description">*Narrative description about the course of the symptom or sign during this episode.(en)</items>
        <items id="comment">*For example: a text description of the immediate onset of the symptom, activities that worsened or relieved the symptom, whether it is improving or worsening and how it resolved over weeks.(en)</items>
      </items>
      <items code="at0056">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description of the effect of the modifying factor on the symptom or sign.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">*Description of previous episodes(en)</items>
        <items id="description">*Narrative description of any or all previous episodes.(en)</items>
        <items id="comment">*For example: frequency/periodicity - per hour, day, week, month, year; and regularity. May include a comparison to this episode.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Associated symptom/sign(en)</items>
        <items id="description">*Structured details about any associated symptoms or signs that are concurrent.(en)</items>
        <items id="comment">*In linked clinical systems, it is possible that associated symptoms or signs are already recorded within the EHR. Systems can allow the clinician to LINK to relevant associated symptoms/signs. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent associated symptoms/signs.(en)</items>
      </items>
      <items code="at0146">
        <items id="text">*Previous episodes(en)</items>
        <items id="description">*Structured details of the symptom or sign during a previous episode.(en)</items>
        <items id="comment">*In linked clinical systems, it is possible that previous episodes are already recorded within the EHR. Systems can allow the clinician to LINK to relevant previous episodes. However in a system or message without LINKs to existing data or with a new patient, additional instances of the symptom archetype could be included here to represent previous episodes. It is recommended that new instances of the Symptom archetype inserted in this SLOT represent one or many previous episodes to this Symptom instance only.(en)</items>
      </items>
      <items code="at0147">
        <items id="text">*Structured body site(en)</items>
        <items id="description">*Structured body site where the symptom or sign was reported.(en)</items>
        <items id="comment">*If the anatomical location is included in the Symptom name via precoordinated codes, use of this SLOT becomes redundant. If the anatomical location is recorded using the 'Body site' data element, then use of CLUSTER archetypes in this SLOT is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.(en)</items>
      </items>
      <items code="at0151">
        <items id="text">*Body site(en)</items>
        <items id="description">*Simple body site where the symptom or sign was reported.(en)</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple body sites to be separated out in a template if desired. This allows for representation of clinical scenarios where a symptom or sign needs to be recorded in multiple locations or identifying both the originating and distal site in pain radiation, but where all of the other attributes such as impact and duration are identical. If the requirements for recording the body site are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the Detailed anatomical location' SLOT in this archetype. &#xD;
If the anatomical location is included in the Symptom name via precoordinated codes, this data element becomes redundant. If the anatomical location is recorded using the 'Structured body site' SLOT, then use of this data element is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both.(en)</items>
      </items>
      <items code="at0152">
        <items id="text">Episodebegin</items>
        <items id="description">Het begin van deze episode van het symptoom of het teken.</items>
        <items id="comment">Hoewel gedeeltelijke datums toegestaan zijn, kunnen exacte datum en tijd van het begin worden vastgelegd, indien gepast. Als dit symptoom of teken voor de eerste keer ervaren wordt, of opnieuw optreedt, wordt deze datum gebruikt om het begin van deze episode weer te geven. Als het symptoom of het teken langer bestaat, kan dit dataelement redundant zijn, als het eerder al is vastgelegd.</items>
      </items>
      <items code="at0153">
        <items id="text">*Specific details(en)</items>
        <items id="description">*Specific data elements that are additionally required to record as unique attributes of the identified symptom or sign.(en)</items>
        <items id="comment">*For example: CTCAE grading.(en)</items>
      </items>
      <items code="at0154">
        <items id="text">*Factor detail(en)</items>
        <items id="description">*Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0155">
        <items id="text">*Impact(en)</items>
        <items id="description">*Description of the impact of this symptom or sign.(en)</items>
        <items id="comment">*Assessment of impact could consider the severity, duration and frequency of the symptom as well as the type of impact including, but not limited to, functional, social and emotional impact. Occurrences of this data element are set to 0..* to allow multiple types of impact to be separated out in a template if desired. Examples for functional impact from hearing loss may include: 'Difficulty Hearing in Quiet Environment'; 'Difficulty Hearing the TV or Radio'; 'Difficulty Hearing Group Conversation'; and 'Difficulty Hearing on Phone'.(en)</items>
      </items>
      <items code="at0156">
        <items id="text">*No effect(en)</items>
        <items id="description">*The factor has no impact on the symptom or sign.(en)</items>
      </items>
      <items code="at0158">
        <items id="text">*Worsens(en)</items>
        <items id="description">*The factor increases the severity or impact of the symptom or sign.(en)</items>
      </items>
      <items code="at0159">
        <items id="text">*Relieves(en)</items>
        <items id="description">*The factor decreases the severity or impact of the symptom or sign, but does not fully resolve it.(en)</items>
      </items>
      <items code="at0161">
        <items id="text">*Resolution date/time(en)</items>
        <items id="description">*The timing of the cessation of this episode of the symptom or sign.(en)</items>
        <items id="comment">*If 'Date/time of onset' and 'Duration' are used in systems, this data element may be calculated, or alternatively, considered redundant. While partial dates are permitted, the exact date and time of resolution can be recorded, if appropriate.(en)</items>
      </items>
      <items code="at0163">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the symptom or sign not captured in other fields.(en)</items>
      </items>
      <items code="at0164">
        <items id="text">*Onset timing(en)</items>
        <items id="description">*Timing of the onset and development of the symptom or sign.(en)</items>
        <items id="comment">*The type of the onset can be coded with a terminology, if desired. For example: gradual; or sudden.(en)</items>
      </items>
      <items code="at0165">
        <items id="text">*Precipitating factor(en)</items>
        <items id="description">*Details about specified factors that are associated with the precipitation of the symptom or sign.(en)</items>
        <items id="comment">*For example: lying down leads to heartburn; or walking up a hill leads to claudication.(en)</items>
      </items>
      <items code="at0170">
        <items id="text">*Factor(en)</items>
        <items id="description">*Name of the health event, symptom, reported sign or other factor.(en)</items>
        <items id="comment">*For example: onset of another symptom; lying down; or walking up a hill.(en)</items>
      </items>
      <items code="at0171">
        <items id="text">*Time interval(en)</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and onset of the symptom or sign.(en)</items>
      </items>
      <items code="at0175">
        <items id="text">*Episodicity(en)</items>
        <items id="description">*Category of this episode for the identified symptom or sign.(en)</items>
      </items>
      <items code="at0176">
        <items id="text">*New(en)</items>
        <items id="description">*A new episode of the symptom or sign - either the first ever occurrence or a reoccurrence where the previous episode had completely resolved.(en)</items>
      </items>
      <items code="at0177">
        <items id="text">*Indeterminate(en)</items>
        <items id="description">*It is not possible to determine if this occurrence of the symptom or sign is new or ongoing.(en)</items>
      </items>
      <items code="at0178">
        <items id="text">*Ongoing(en)</items>
        <items id="description">*This symptom or sign is ongoing, effectively a single, continuous episode.(en)</items>
      </items>
      <items code="at0180">
        <items id="text">Beloop</items>
        <items id="description">Beloop van het symptoom op het moment van verslaglegging.</items>
        <items id="comment">*Occurrences of this data element are set to 0..* to allow multiple types of progression to be separated out in a template if desired - for example, severity or frequency. The Text data type is added as an option, to support other value sets than the ones included in the archetype.(en)</items>
      </items>
      <items code="at0181">
        <items id="text">Verbeterend</items>
        <items id="description">*The severity of the symptom or sign has improved overall during this episode.(en)</items>
      </items>
      <items code="at0182">
        <items id="text">Onveranderd</items>
        <items id="description">*The severity of the symptom or sign has not changed overall during this episode.(en)</items>
      </items>
      <items code="at0183">
        <items id="text">Verslechtering</items>
        <items id="description">*The severity of the symptom or sign has worsened overall during this episode.(en)</items>
      </items>
      <items code="at0184">
        <items id="text">Hersteld</items>
        <items id="description">*The severity of the symptom or sign has resolved.(en)</items>
      </items>
      <items code="at0185">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the effect of the factor on the identified symptom or sign.(en)</items>
      </items>
      <items code="at0186">
        <items id="text">*Occurrence(en)</items>
        <items id="description">*Type of occurrence for this symptom or sign?(en)</items>
      </items>
      <items code="at0187">
        <items id="text">*First occurrence(en)</items>
        <items id="description">*This is the first ever occurrence of this symptom or sign.(en)</items>
      </items>
      <items code="at0188">
        <items id="text">*Recurrence(en)</items>
        <items id="description">*New occurrence of the same symptom or sign after a previous episode was resolved.(en)</items>
      </items>
      <items code="at0189">
        <items id="text">*Character(en)</items>
        <items id="description">*Word or short phrase describing the nature of the symptom or sign.(en)</items>
        <items id="comment">*For example: pain could be described as 'gnawing', 'burning', or 'like an electric shock'; a headache could be 'throbbing' or 'constant'. Coding with an external terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0190">
        <items id="text">*Resolving factor(en)</items>
        <items id="description">*Details about specified factors that are associated with the resolution of the symptom or sign.(en)</items>
        <items id="comment">*For example: upright posture stops heartburn; or resting stops claudication.(en)</items>
      </items>
      <items code="at0193">
        <items id="text">*Factor(en)</items>
        <items id="description">*Name of the health event, symptom, reported sign or other factor.(en)</items>
        <items id="comment">*For example: upright posture; or resting.(en)</items>
      </items>
      <items code="at0194">
        <items id="text">*Factor detail(en)</items>
        <items id="description">*Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0195">
        <items id="text">*Time interval(en)</items>
        <items id="description">*The interval of time between the occurrence or onset of the factor and resolution of the symptom or sign.(en)</items>
      </items>
      <items code="at0196">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the effect of the factor on the identified symptom or sign.(en)</items>
      </items>
      <items code="at0197">
        <items id="text">*Factor detail(en)</items>
        <items id="description">*Structured detail about the factor associated with the identified symptom or sign.(en)</items>
      </items>
      <items code="at0198">
        <items id="text">*Severity rating(en)</items>
        <items id="description">*Numerical rating scale representing the overall severity of the symptom or sign.(en)</items>
        <items id="comment">*Symptom severity can be rated by the individual by recording a score for example from 0 (ie symptom not present) to 10 (ie symptom is as severe as the individual can imagine).(en)</items>
      </items>
      <items code="at0200">
        <items id="text">*Nadir(en)</items>
        <items id="description">*Date/time when a monophasic, progressive symptom or sign reached its' maximal intensity or functional impact.(en)</items>
        <items id="comment">*For example: the date when neurological signs in Guillain-Barre disease was at its worst.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="ca">
      <items code="at0000">
        <items id="text">Símptoma/Signe</items>
        <items id="description">Observació notificada d’una alteració física o mental en un pacient.</items>
      </items>
      <items code="at0001">
        <items id="text">Nom del símptoma/signe</items>
        <items id="description">El nom del símptoma o signe notificat.</items>
        <items id="comment">Es recomana programar el nom del símptoma amb una terminologia quan sigui possible.</items>
      </items>
      <items code="at0002">
        <items id="text">Informació</items>
        <items id="description">Informació descriptiva sobre el símptoma o signe notificat.</items>
      </items>
      <items code="at0003">
        <items id="text">Patró</items>
        <items id="description">Informació descriptiva sobre el patró del símptoma o signe durant aquest episodi.</items>
        <items id="comment">Per exemple: el dolor es pot descriure com a constant o intermitent.</items>
      </items>
      <items code="at0017">
        <items id="text">Efecte</items>
        <items id="description">Efecte percebut del factor de modificació en el símptoma o signe.</items>
      </items>
      <items code="at0018">
        <items id="text">Factor de modificació</items>
        <items id="description">Dada sobre com un factor específic afecta el símptoma o signe identificat durant aquest episodi.</items>
      </items>
      <items code="at0019">
        <items id="text">Factor</items>
        <items id="description">Nom del factor de modificació.</items>
        <items id="comment">Exemples de factors de modificació: gitar-se damunt de múltiples coixins, menjar o l’administració d’una medicació específica.</items>
      </items>
      <items code="at0021">
        <items id="text">Categoria de gravetat</items>
        <items id="description">Categoria que representi la gravetat general del símptoma o signe.</items>
        <items id="comment">Definir valors com lleu, moderat o greu de forma que es puguin aplicar a múltiples símptomes o signes i que permetin que múltiples usuaris els interpretin i registrin de forma consistent no és fàcil. Algunes organitzacions amplien més el conjunt de valors amb la inclusió de valors com «Trivial» i «Molt greu», o «Lleu-Moderat» i «Moderat-Greu». Això augmenta la dificultat de les definicions i pot també agreujar els problemes d’exactitud entre els registradors. L’ús de «Mortal» i «Letal» també es considera sovint com a part d’aquest conjunt de valors, encara que, des d’un punt de vista lògic, en realitat pot reflectir el resultat més que la gravetat. Tenint en compte això, continuar amb una llista ben definida, però més breu és preferible, i per això s’ofereix el conjunt lleu/moderat/greu, encara que elegir altre text permet que altres conjunts de valors s’incloguin dins d’aquest element de dades en una plantilla.</items>
      </items>
      <items code="at0023">
        <items id="text">Lleu</items>
        <items id="description">La intensitat del símptoma o signe no interfereix amb el desenvolupament de les activitats habituals.</items>
      </items>
      <items code="at0024">
        <items id="text">Moderat</items>
        <items id="description">La intensitat del símptoma o signe interfereix amb el desenvolupament de les activitats habituals.</items>
      </items>
      <items code="at0025">
        <items id="text">Greu</items>
        <items id="description">La intensitat del símptoma o signe impedeix el desenvolupament de les activitats habituals.</items>
      </items>
      <items code="at0028">
        <items id="text">Durada de l’episodi</items>
        <items id="description">La durada d’aquest episodi del símptoma o signe des de l’aparició inicial.</items>
        <items id="comment">Si la «Data/hora de l’aparició» i la «Data/hora de la resolució» s’utilitzen en sistemes, aquest element de dades es pot calcular, o, alternativament, es pot considerar redundant en aquesta situació. El tipus de dades en text s’utilitza per a registrar els intervals de la duració programada, com «0-7 dies, 1-2 setmanes, 2 setmanes o més».</items>
      </items>
      <items code="at0031">
        <items id="text">Nombre dels episodis anteriors</items>
        <items id="description">El nombre de vegades que aquest símptoma o signe ha ocorregut prèviament.</items>
      </items>
      <items code="at0037">
        <items id="text">Descripció de l'episodi</items>
        <items id="description">Informació descriptiva sobre el curs del símptoma o signe durant aquest episodi.</items>
        <items id="comment">Per exemple: una descripció d’un text sobre l’aparició immediata del símptoma, activitats que agreujaren o alleugeraren el símptoma, si està millorant o agreujant, i com es resolgué al llarg de les setmanes.</items>
      </items>
      <items code="at0056">
        <items id="text">Informació</items>
        <items id="description">Informació descriptiva de l'efecte del factor de modificació en el símptoma o signe.</items>
      </items>
      <items code="at0057">
        <items id="text">Descripció d'episodis anteriors</items>
        <items id="description">Informació descriptiva de qualsevol o tots els episodis anterior.</items>
        <items id="comment">Per exemple: freqüència/periodicitat - per hora, dia, setmana, mes, any; i regularitat. Pot incloure una comparació amb aquest episodi.</items>
      </items>
      <items code="at0063">
        <items id="text">Símptoma/signe associat</items>
        <items id="description">Dades estructurades de qualsevol símptoma o signe associat que sigui concurrent.</items>
        <items id="comment">En els sistemes clínics connectats, és possible que ja s'hagin registrat dins del EHR símptomes o signes associats. Els sistemes permeten al metge fer LINK a símptomes/signes associats rellevants. No obstant això, en un sistema o missatge sense LINKs a dades existents o amb un nou pacient, es poden incloure instàncies addicionals de l'arquetip símptoma per a representar símptomes/signes associats.</items>
      </items>
      <items code="at0146">
        <items id="text">Episodis anteriors</items>
        <items id="description">Dades estructurades del símptoma o signe durant un episodi anterior.</items>
        <items id="comment">En els sistemes clínics connectats, és possible que ja s'hagin registrat dins del EHR episodis anteriors. Els sistemes permeten al metge fer LINK a episodis anteriors rellevants. No obstant això, en un sistema o missatge sense LINKs a dades existents o amb un nou pacient, es poden incloure instàncies addicionals de l'arquetip símptoma per a representar episodis anteriors. Es recomana que les noves instàncies de l'arquetip Símptoma inserides en aquest SLOT representen un o molts episodis anteriors només a aquesta instància del símptoma.</items>
      </items>
      <items code="at0147">
        <items id="text">Zona estructurada del cos</items>
        <items id="description">Zona estructurada del cos on s'ha notificat el símptoma o signe.</items>
        <items id="comment">Si la ubicació anatòmica està inclosa en el Nom del símptoma mitjançant codis precoordinats, l’ús d’aquest SLOT esdevé redundant. Si es registra la ubicació anatòmica utilitzant l’element de dades «Zona del cos», aleshores l’ús d’arquetips de tipus CLUSTER en aquest SLOT no està permès – registrar només la «Zona simple del cos» O la «Zona estructurada del cos», però no ambdues.</items>
      </items>
      <items code="at0151">
        <items id="text">Zona del cos</items>
        <items id="description">Zona particular del cos on s'ha notificat el símptoma o signe.</items>
        <items id="comment">Esdeveniments d’aquest element de dades estan configurats en 0..* per a permetre la separació de múltiples zones del cos en una plantilla si així es vol. Això permet la representació de situacions clíniques on un símptoma o signe s’hagi de registrar en múltiples ubicacions o per a identificar tant la zona d’origen com la zona distal de la radiació del dolor quan tots els altres aspectes com l’impacte i la duració són idèntics. Si els requisits per a registrar la zona del cos es determinen durant el temps d’execució mitjançant l’aplicació o requereixen un modelatge més complex, com ubicacions relatives, aleshores s’ha d’utilitzar CLUSTER.anatomical_location o CLUSTER.relative_location dins del SLOT «Ubicació anatòmica precisa» d’aquest arquetip.&#xD;
Si la ubicació anatòmica està inclosa en el Nom del símptoma mitjançant codis precoordinats, aquest element de dades esdevé redundant. Si la ubicació anatòmica es registra utilitzant el SLOT «Zona estructurada del cos», aleshores l’ús d’aquest element de dades no està permès – registrar només la «Zona particular del cos» O la «Zona estructurada del cos», però no ambdues.</items>
      </items>
      <items code="at0152">
        <items id="text">Aparició de l’episodi</items>
        <items id="description">L’aparició del símptoma o signe d’aquest episodi.</items>
        <items id="comment">Encara que les dates parcials estan permeses, la data i hora exactes de l’aparició es poden registrar si fos necessari. Si s’experimenta aquest símptoma o signe per primera vegada o és una reaparició, aquesta data s’utilitza per a representar l’aparició d’aquest episodi. Si aquest símptoma o signe està en curs, aquest element de dades pot ser redundant si s’ha registrat amb anterioritat.</items>
      </items>
      <items code="at0153">
        <items id="text">Dades específiques</items>
        <items id="description">Els elements de dades específics que es necessiten addicionalment per a registrar com a únics els atributs dels símptomes o signes identificats.</items>
        <items id="comment">Per exemple: escala CTCAE.</items>
      </items>
      <items code="at0154">
        <items id="text">Dada del factor</items>
        <items id="description">Dada estructurada sobre el factor associat amb el símptoma o signe identificat.</items>
      </items>
      <items code="at0155">
        <items id="text">Impacte</items>
        <items id="description">Descripció de l'impacte d'aquest símptoma o signe.</items>
        <items id="comment">L'avaluació de l'impacte pot considerar la severitat, duració i freqüència del símptoma, així com el tipus d'impacte, incloent-hi, però no limitat a l'impacte funcional, social i emocional. Els esdeveniments d'aquest element de dades estan configurats en 0..* per a permetre la separació de múltiples tipus d'impactes en una plantilla si així es vol. Exemples d’un impacte funcional originats per la pèrdua d'escolta poden incloure: «Dificultat per a Escoltar en un Ambient Tranquil», «Dificultat per a Escoltar la Televisió o la Ràdio»; «Dificultat per a Escoltar una Conversació de Grup»; i «Dificultat per a Escoltar quan es parla per Telèfon».</items>
      </items>
      <items code="at0156">
        <items id="text">Cap efecte</items>
        <items id="description">El factor no té cap efecte en el símptoma o signe.</items>
      </items>
      <items code="at0158">
        <items id="text">Agreuja</items>
        <items id="description">El factor augmenta la gravetat o impacte del símptoma o signe.</items>
      </items>
      <items code="at0159">
        <items id="text">Alleuja</items>
        <items id="description">El factor disminueix la gravetat o impacte del símptoma o signe, però no el resol totalment.</items>
      </items>
      <items code="at0161">
        <items id="text">Data/hora de la resolució</items>
        <items id="description">El moment de la cessació d'aquest episodi del símptoma o signe.</items>
        <items id="comment">Si «Data/hora de l’aparició» i «Duració» s'utilitzen en sistemes, aquest element de dades es pot calcular o, alternativament, es pot considerar redundant. Encara que les dades parcials estan permeses, la data i hora exactes de la resolució es poden registrar, si fos necessari.</items>
      </items>
      <items code="at0163">
        <items id="text">Observacions</items>
        <items id="description">Informació addicional sobre un símptoma o signe no recollida en altres caselles.</items>
      </items>
      <items code="at0164">
        <items id="text">Temporització de l’aparició</items>
        <items id="description">Temporització de l’aparició i desenvolupament del símptoma o signe.</items>
        <items id="comment">El tipus d’aparició es pot programar amb una terminologia, si així es vol. Per exemple: gradual o abrupte.</items>
      </items>
      <items code="at0165">
        <items id="text">Factor desencadenant</items>
        <items id="description">Dades sobre els factors específics associats amb el desencadenant del símptoma o signe.</items>
        <items id="comment">Per exemple: tombar-se provoca cremor d'estómac, o pujar un turó provoca claudicació.</items>
      </items>
      <items code="at0170">
        <items id="text">Factor</items>
        <items id="description">Nom de l'esdeveniment sanitari, símptoma, signe notificat o altre factor.</items>
        <items id="comment">Per exemple: l'aparició d'altre símptoma; tombar-se, o pujar un turó.</items>
      </items>
      <items code="at0171">
        <items id="text">Interval de temps</items>
        <items id="description">Interval de temps entre l'esdeveniment o l'aparició del factor i l'aparició del símptoma o signe.</items>
      </items>
      <items code="at0175">
        <items id="text">Circumstancialitat</items>
        <items id="description">Categoria d’aquest episodi per al símptoma o signe identificat.</items>
      </items>
      <items code="at0176">
        <items id="text">Nou</items>
        <items id="description">Un episodi nou del símptoma o signe – sigui el primer cas o una reaparició quan l’episodi anterior ja estava totalment resolt.</items>
      </items>
      <items code="at0177">
        <items id="text">Indeterminat</items>
        <items id="description">No és possible determinar si aquest esdeveniment del símptoma o signe és nou o està en curs.</items>
      </items>
      <items code="at0178">
        <items id="text">En curs</items>
        <items id="description">Aquest símptoma o signe segueix en curs, particularment en un únic episodi continu.</items>
      </items>
      <items code="at0180">
        <items id="text">Progressió</items>
        <items id="description">Descripció de la progressió del símptoma o signe al moment de presentar l’informe.</items>
        <items id="comment">Esdeveniments d’aquest element de dades estan configurats en 0..* per a permetre que múltiples tipus de progressió estiguin separats en una plantilla si així es vol – per exemple, gravetat o freqüència. El Tipus de dades en text s’afegeix com a opció, per a mantenir altres conjunts de valors que no siguin els que estan inclosos en l’arquetip.</items>
      </items>
      <items code="at0181">
        <items id="text">Millorament</items>
        <items id="description">La gravetat del símptoma o signe en conjunt ha millorat durant aquest episodi.</items>
      </items>
      <items code="at0182">
        <items id="text">Inalterat</items>
        <items id="description">La gravetat del símptoma o signe en conjunt no ha canviat durant aquest episodi.</items>
      </items>
      <items code="at0183">
        <items id="text">Agreujament</items>
        <items id="description">La gravetat del símptoma o signe en conjunt ha agreujat durant aquest episodi.</items>
      </items>
      <items code="at0184">
        <items id="text">Resolt</items>
        <items id="description">La gravetat del símptoma o signe s’ha resolt.</items>
      </items>
      <items code="at0185">
        <items id="text">Informació</items>
        <items id="description">Informació descriptiva sobre l'efecte del factor en el símptoma o signe identificat.</items>
      </items>
      <items code="at0186">
        <items id="text">Esdeveniment</items>
        <items id="description">Tipus d’esdeveniment per aquest símptoma o signe.</items>
      </items>
      <items code="at0187">
        <items id="text">Primer cas</items>
        <items id="description">Aquest és el primer cas d’aquest símptoma o signe.</items>
      </items>
      <items code="at0188">
        <items id="text">Reaparició</items>
        <items id="description">Nou esdeveniment del mateix símptoma o signe després que es resolgués un episodi anterior.</items>
      </items>
      <items code="at0189">
        <items id="text">Caràcter</items>
        <items id="description">Paraula o oració breu que descrigui la natura del símptoma o signe.</items>
        <items id="comment">Per exemple: el dolor es pot descriure com «persistent», «roent» o «com una descàrrega elèctrica»; el mal de cap pot ser «palpitant» o «constant». Es recomana programar amb una terminologia externa quan sigui possible.</items>
      </items>
      <items code="at0190">
        <items id="text">Factor resolutiu</items>
        <items id="description">Dades sobre els factors específics associats amb la resolució del símptoma o signe.</items>
        <items id="comment">Per exemple: mantindre una postura dreta deté la cremor d'estómac, o reposar deté la claudicació.</items>
      </items>
      <items code="at0193">
        <items id="text">Factor</items>
        <items id="description">Nom de l'esdeveniment sanitari, símptoma, signe notificat o altre factor.</items>
        <items id="comment">Per exemple: mantindre una postura dreta o reposar.</items>
      </items>
      <items code="at0194">
        <items id="text">Dada del factor</items>
        <items id="description">Dada estructurada sobre el factor associat amb el símptoma o signe identificat.</items>
      </items>
      <items code="at0195">
        <items id="text">Interval de temps</items>
        <items id="description">Interval de temps entre l'esdeveniment o l'aparició del factor i la resolució del símptoma o signe.</items>
      </items>
      <items code="at0196">
        <items id="text">Informació</items>
        <items id="description">Informació descriptiva sobre l'efecte del factor en el símptoma o signe identificat.</items>
      </items>
      <items code="at0197">
        <items id="text">Dada del factor</items>
        <items id="description">Dada estructurada sobre el factor associat amb el símptoma o signe identificat.</items>
      </items>
      <items code="at0198">
        <items id="text">Classificació de gravetat</items>
        <items id="description">Escala de classificació numèrica que representa la gravetat general del símptoma o signe.</items>
        <items id="comment">El pacient pot classificar la gravetat registrant una puntuació; per exemple, de 0 (és a dir, símptoma absent), a 10 (és a dir, el símptoma és tan greu com la persona se’l pot imaginar).</items>
      </items>
      <items code="at0200">
        <items id="text">Nadir</items>
        <items id="description">Data/hora quan un símptoma o signe monofàsic i progressiu arribà a la seva intensitat o impacte funcional màxims.</items>
        <items id="comment">Per exemple: la data quan els signes neurològics de la malaltia de Guillain-Barré estaven en el moment de major intensitat.</items>
      </items>
    </term_definitions>
    <term_definitions language="ja">
      <items code="at0000">
        <items id="text">症状・徴候</items>
        <items id="description">本人の心身の変調について、本人または他者が捉え、伝えた観察内容。</items>
      </items>
      <items code="at0001">
        <items id="text">症状・徴候の名称</items>
        <items id="description">報告された症状または徴候の名称。</items>
        <items id="comment">可能であれば、症状の名称は用語集によりコード化すべきである。</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">例：疼痛は持続性または間欠性と記述できる。</items>
      </items>
      <items code="at0017">
        <items id="text">影響</items>
        <items id="description">修飾因子が症状または徴候に及ぼすと認識された影響。</items>
      </items>
      <items code="at0018">
        <items id="text">修飾因子</items>
        <items id="description">このエピソードにおいて、特定の因子が特定された症状または徴候にどのように影響するかに関する詳細情報。</items>
      </items>
      <items code="at0019">
        <items id="text">因子</items>
        <items id="description">修飾因子の名称。</items>
        <items id="comment">修飾因子の例：枕を複数重ねて横になること、食事、または特定の薬剤の投与。</items>
      </items>
      <items code="at0021">
        <items id="text">重症度</items>
        <items id="description">症状または徴候の全体的な重症度を表す区分。</items>
        <items id="comment">「軽症」「中等症」「重症」などの値を、さまざまな症状や徴候に適用でき、複数の利用者が一貫した基準で解釈・記録できるように定義するのは容易ではない。組織によっては、「ごく軽症」「非常に重症」や「軽症〜中等症」「中等症〜重症」などを加えて値セットを拡張している。しかし、選択肢を増やすと各値の定義がさらに難しくなり、記録者間で評価が一致しにくくなるおそれもある。「生命を脅かす」や「致死的」をこの値セットに含めることもよく検討されるが、厳密には、これらは重症度ではなく転帰を表している可能性がある。以上を踏まえ、各値の定義を明確にし、選択肢を少数に絞ることが望ましいため、本archetypeでは「軽症」「中等症」「重症」の値セットを用意している。ただし、これら以外のテキストも使用できるため、テンプレートではこのデータエレメントに別の値セットを設定することもできる。</items>
      </items>
      <items code="at0023">
        <items id="text">軽症</items>
        <items id="description">症状または徴候の強さは通常の活動を妨げない。</items>
      </items>
      <items code="at0024">
        <items id="text">中等症</items>
        <items id="description">症状または徴候の強さは通常の活動を妨げる。</items>
      </items>
      <items code="at0025">
        <items id="text">重症</items>
        <items id="description">症状または徴候の強さは通常の活動を不可能にする。</items>
      </items>
      <items code="at0028">
        <items id="text">エピソードの持続期間</items>
        <items id="description">症状または徴候の今回のエピソードにおける、発症からの持続期間。</items>
        <items id="comment">システムで「発症日時」と「消失日時」を使用している場合、このデータエレメントの値は両者から算出できる。そのため、冗長とみられることもある。テキストデータ型は、「0〜7日」「1〜2週」「2週以上」など、あらかじめ設定された期間区分を記録するために用いる。</items>
      </items>
      <items code="at0031">
        <items id="text">過去のエピソードの回数</items>
        <items id="description">この症状または徴候が過去に生じた回数。</items>
      </items>
      <items code="at0037">
        <items id="text">エピソードの説明</items>
        <items id="description">このエピソードにおける症状または徴候の経過についての叙述的な記述。</items>
        <items id="comment">例：発症直後の様子、症状を悪化または軽減させた活動、改善しているか悪化しているか、数週間かけてどのように消失したかについてのテキスト記述。</items>
      </items>
      <items code="at0056">
        <items id="text">説明</items>
        <items id="description">修飾因子が症状または徴候に及ぼす影響の叙述的な記述。</items>
      </items>
      <items code="at0057">
        <items id="text">過去のエピソードの説明</items>
        <items id="description">過去のエピソードのいずれかまたはすべてについての叙述的な記述。</items>
        <items id="comment">例：頻度／周期性 - 1時間、1日、1週、1か月、1年あたりといった頻度、周期性および規則性。このエピソードとの比較を含めてもよい。</items>
      </items>
      <items code="at0063">
        <items id="text">随伴症状・徴候</items>
        <items id="description">同時に生じている随伴症状または徴候についての構造化された詳細記録。</items>
        <items id="comment">連携している臨床システムでは、随伴する症状や徴候がすでに EHR 内に記録されていることがある。その場合、システムは、医療従事者が関連する随伴症状・徴候への LINK を設定する機能を提供できる。一方、既存データへの LINK がないシステムやメッセージ、あるいは新規患者の場合には、この SLOT に Symptom archetypeのインスタンスを追加して、随伴症状・徴候を記録できる。</items>
      </items>
      <items code="at0146">
        <items id="text">過去のエピソード</items>
        <items id="description">過去のエピソードにおける症状または徴候の構造化された詳細記録。</items>
        <items id="comment">連携している臨床システムでは、過去のエピソードがすでに EHR 内に記録されていることがある。その場合、システムは、医療従事者が関連する過去のエピソードへの LINK を設定する機能を提供できる。一方、既存データへの LINK がないシステムやメッセージ、あるいは新規患者の場合には、この SLOT に Symptom archetypeのインスタンスを追加して、過去のエピソードを記録できる。追加するインスタンスには、この SLOT を含む Symptom インスタンスに関連する過去のエピソードのみを、1つまたは複数記録することを推奨する。</items>
      </items>
      <items code="at0147">
        <items id="text">構造化された身体部位表現</items>
        <items id="description">症状または徴候が報告された身体部位の構造化された表現。</items>
        <items id="comment">解剖学的部位が事前調整されたコードによって症状の名称に含まれている場合、この SLOT を使用する必要はない。解剖学的部位を「身体部位」データエレメントで記録する場合、この SLOT での CLUSTER archetypeの使用は許可されない。単純な「身体部位」または「構造化された身体部位表現」のどちらか一方だけを記録し、両方は記録しない。</items>
      </items>
      <items code="at0151">
        <items id="text">身体部位</items>
        <items id="description">症状または徴候があると報告された身体部位の簡潔な記述。</items>
        <items id="comment">このデータエレメントの出現回数は 0..* に設定されており、必要に応じてテンプレートで複数の身体部位を分けて表せる。これにより、症状や徴候を複数の部位に記録する必要がある臨床シナリオや、放散痛の起始部位と遠位部位の両方を特定するが、影響や持続期間などの他の属性はすべて同一であるシナリオを表現できる。身体部位の記録要件がアプリケーションによって実行時に決定される場合や、相対的な位置関係などより複雑なモデリングが必要な場合は、本archetypeの「詳細な解剖学的部位」SLOT 内で CLUSTER.anatomical_location または CLUSTER.relative_location を用いること。 &#xD;
解剖学的部位が事前調整されたコードによって症状の名称に含まれている場合、このデータエレメントは冗長になる。解剖学的部位を「構造化された身体部位表現」SLOT で記録する場合、このデータエレメントの使用は許可されない。単純な「身体部位」または「構造化された身体部位表現」のどちらか一方だけを記録し、両方は記録しない。</items>
      </items>
      <items code="at0152">
        <items id="text">エピソードの発症日時</items>
        <items id="description">症状または徴候のこのエピソードの発症。</items>
        <items id="comment">部分的な日付も記録できるが、適切であれば発症の正確な日時を記録できる。初発・再発のいずれの場合も、この日付は今回のエピソードの発症時点を表す。症状または徴候が継続しており、発症日時がすでに記録されている場合、このデータエレメントは冗長とみられることがある。</items>
      </items>
      <items code="at0153">
        <items id="text">詳細記録</items>
        <items id="description">特定された症状または徴候に固有の属性として、追加で記録する必要がある特定のデータエレメント。</items>
        <items id="comment">例：CTCAE のグレード分類。</items>
      </items>
      <items code="at0154">
        <items id="text">因子の詳細</items>
        <items id="description">特定された症状または徴候に関連する因子についての構造化された詳細記録。</items>
      </items>
      <items code="at0155">
        <items id="text">影響</items>
        <items id="description">この症状または徴候の影響の記述。</items>
        <items id="comment">影響の評価では、症状の重症度、持続期間、頻度に加え、機能面、社会面、情緒面など、影響が及ぶ側面も考慮できる。必要に応じてテンプレート内で影響を種類ごとに分けて表せるよう、このデータエレメントの出現回数は 0..* に設定されている。難聴による機能面への影響の例としては、「静かな環境で聞き取りにくい」「テレビやラジオの音声を聞き取りにくい」「複数人での会話を聞き取りにくい」「電話で聞き取りにくい」などが挙げられる。</items>
      </items>
      <items code="at0156">
        <items id="text">影響なし</items>
        <items id="description">その因子は症状または徴候に影響を及ぼさない。</items>
      </items>
      <items code="at0158">
        <items id="text">増悪</items>
        <items id="description">その因子は症状または徴候の重症度または影響を増大させる。</items>
      </items>
      <items code="at0159">
        <items id="text">軽減</items>
        <items id="description">その因子は症状または徴候の重症度または影響を軽減させるが、完全には消失させない。</items>
      </items>
      <items code="at0161">
        <items id="text">消失日時</items>
        <items id="description">症状または徴候のこのエピソードが消失した時期。</items>
        <items id="comment">システムで「発症日時」と「持続期間」を使う場合、このデータエレメントは計算で求められるか、あるいは冗長とみられることがある。部分的な日付も許容されるが、適切であれば消失の正確な日時を記録できる。</items>
      </items>
      <items code="at0163">
        <items id="text">コメント</items>
        <items id="description">他の項目には収まらない症状または徴候についての追加の記述。</items>
      </items>
      <items code="at0164">
        <items id="text">発症時期</items>
        <items id="description">症状または徴候の発症と進展のタイミング。</items>
        <items id="comment">発症の型は、必要に応じて用語集によりコード化できる。例：緩徐；または突発。</items>
      </items>
      <items code="at0165">
        <items id="text">誘発因子</items>
        <items id="description">症状または徴候の誘発に関連する特定の因子に関する詳細情報。</items>
        <items id="comment">例：横になると胸やけが生じる；または坂を上ると跛行が生じる。</items>
      </items>
      <items code="at0170">
        <items id="text">因子</items>
        <items id="description">健康イベント、症状、報告された徴候、またはその他の因子の名称。</items>
        <items id="comment">例：別の症状の発症；横になること；または坂を上ること。</items>
      </items>
      <items code="at0171">
        <items id="text">時間間隔</items>
        <items id="description">因子の発生または発症から、症状または徴候の発症までの時間間隔。</items>
      </items>
      <items code="at0175">
        <items id="text">エピソード区分</items>
        <items id="description">特定された症状または徴候における、このエピソードの区分。</items>
      </items>
      <items code="at0176">
        <items id="text">新規</items>
        <items id="description">症状または徴候の新しいエピソード。初発、または以前のエピソードが完全に消失した後の再発のいずれか。</items>
      </items>
      <items code="at0177">
        <items id="text">判定不能</items>
        <items id="description">この症状または徴候の今回の発症が新規か継続中かを判定できない。</items>
      </items>
      <items code="at0178">
        <items id="text">継続中</items>
        <items id="description">この症状または徴候は継続しており、実質的に単一の連続したエピソードである。</items>
      </items>
      <items code="at0180">
        <items id="text">進行状況</items>
        <items id="description">報告時点における症状または徴候の進行状況の記述。</items>
        <items id="comment">このデータエレメントの出現回数は 0..* に設定されており、必要に応じてテンプレートで複数の種類の進行状況（例えば重症度や頻度）を分けて表せる。archetypeに含まれる値セット以外の値セットに対応するため、テキストデータ型が選択肢として追加されている。</items>
      </items>
      <items code="at0181">
        <items id="text">改善</items>
        <items id="description">このエピソードの間に、症状または徴候の重症度は全体として改善した。</items>
      </items>
      <items code="at0182">
        <items id="text">不変</items>
        <items id="description">このエピソードの間に、症状または徴候の重症度は全体として変化していない。</items>
      </items>
      <items code="at0183">
        <items id="text">悪化</items>
        <items id="description">このエピソードの間に、症状または徴候の重症度は全体として悪化した。</items>
      </items>
      <items code="at0184">
        <items id="text">消失</items>
        <items id="description">症状または徴候は消失した。</items>
      </items>
      <items code="at0185">
        <items id="text">説明</items>
        <items id="description">因子が特定された症状または徴候に及ぼす影響についての叙述的な記述。</items>
      </items>
      <items code="at0186">
        <items id="text">発症区分</items>
        <items id="description">この症状または徴候の発症の種類。</items>
      </items>
      <items code="at0187">
        <items id="text">初発</items>
        <items id="description">この症状または徴候の、初めての発症である。</items>
      </items>
      <items code="at0188">
        <items id="text">再発</items>
        <items id="description">以前のエピソードが消失した後の、同じ症状または徴候の新たな発症。</items>
      </items>
      <items code="at0189">
        <items id="text">性状</items>
        <items id="description">症状または徴候の性質を表す語または短い句。</items>
        <items id="comment">例：疼痛は「うずくような」「灼けるような」「電気が走るような」、頭痛は「拍動性」または「持続性」と記述できる。可能であれば、外部用語集によりコード化することが望ましい。</items>
      </items>
      <items code="at0190">
        <items id="text">消失因子</items>
        <items id="description">症状または徴候の消失に関連する特定の因子に関する詳細情報。</items>
        <items id="comment">例：直立姿勢で胸やけが止まる；または休息で跛行が止まる。</items>
      </items>
      <items code="at0193">
        <items id="text">因子</items>
        <items id="description">健康イベント、症状、報告された徴候、またはその他の因子の名称。</items>
        <items id="comment">例：直立姿勢；または休息。</items>
      </items>
      <items code="at0194">
        <items id="text">因子の詳細</items>
        <items id="description">特定された症状または徴候に関連する因子についての構造化された詳細記録。</items>
      </items>
      <items code="at0195">
        <items id="text">時間間隔</items>
        <items id="description">因子の発生または発症から、症状または徴候の消失までの時間間隔。</items>
      </items>
      <items code="at0196">
        <items id="text">説明</items>
        <items id="description">因子が特定された症状または徴候に及ぼす影響についての叙述的な記述。</items>
      </items>
      <items code="at0197">
        <items id="text">因子の詳細</items>
        <items id="description">特定された症状または徴候に関連する因子についての構造化された詳細記録。</items>
      </items>
      <items code="at0198">
        <items id="text">重症度評価</items>
        <items id="description">症状または徴候の全体的な重症度を表す数値評価スケール。</items>
        <items id="comment">症状の重症度は、例えば 0（症状なし）から 10（本人が想像しうる最も重い症状）までのスコアを記録することで、本人が評価できる。</items>
      </items>
      <items code="at0200">
        <items id="text">最悪時</items>
        <items id="description">単相性で進行性の症状または徴候が、最大の強さまたは機能的に最悪の影響に達した日時。</items>
        <items id="comment">例：ギラン・バレー症候群の神経学的徴候が最も悪化した日。</items>
      </items>
    </term_definitions>
    <term_bindings terminology="SNOMED-CT">
      <items code="at0023">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>162468002</code_string>
        </value>
      </items>
      <items code="at0024">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>162469005</code_string>
        </value>
      </items>
      <items code="at0025">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>162470006</code_string>
        </value>
      </items>
      <items code="at0028">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>162434008</code_string>
        </value>
      </items>
      <items code="at0021">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>405162009</code_string>
        </value>
      </items>
      <items code="at0152">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>405795006</code_string>
        </value>
      </items>
    </term_bindings>
  </ontology>
</archetype>
