<?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">2020-03-13</original_author>
    <original_author id="name">Heather Leslie</original_author>
    <original_author id="organisation">Atomica Informatics</original_author>
    <original_author id="email">heather.leslie@atomicainformatics.com</original_author>
    <other_contributors>Dag Aarhus, Vestre Viken HF, Norway</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Astrid Askeland, Dips AS, Norway</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)</other_contributors>
    <other_contributors>SB Bhattacharyya, Bhattacharyyas Clinical Records Research &amp; Informatics LLP, India</other_contributors>
    <other_contributors>Yexuan Cheng, 浙江大学, China</other_contributors>
    <other_contributors>Are Edvardsen, SKDE, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>Alexander Eikrem-Lüthi, Lovisenberg Diakonale Sykehus, Norway</other_contributors>
    <other_contributors>Kåre Flø, DIPS ASA, Norway</other_contributors>
    <other_contributors>Grant Forrest, Lunaria Ltd, United Kingdom</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Anca Heyd, DIPS ASA, Norway</other_contributors>
    <other_contributors>Joost Holslag, Nedap, Netherlands</other_contributors>
    <other_contributors>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway</other_contributors>
    <other_contributors>Gunnar Jårvik, Helse Vest IKT AS, Norway</other_contributors>
    <other_contributors>Anjali Kulkarni, Karkinos, India</other_contributors>
    <other_contributors>Kanika Kuwelker, Helse Vest IKT, Norway</other_contributors>
    <other_contributors>Jörgen Kuylenstierna, eWeave AB, Sweden</other_contributors>
    <other_contributors>Liv Laugen, ​Oslo University Hospital, Norway, Norway</other_contributors>
    <other_contributors>Øygunn Leite Kallevik, Helse Bergen, Norway</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, UK</other_contributors>
    <other_contributors>Per Meinich, Helse Sør-Øst RHF, Norway</other_contributors>
    <other_contributors>Mikael Nyström, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Vanessa Pereira, Luxembourg Institute of Health (LIH), Portugal</other_contributors>
    <other_contributors>Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil</other_contributors>
    <other_contributors>Andre Smitt-Ingebretsen, Sørlandet sykehus HF, Norway</other_contributors>
    <other_contributors>Natalia Strauch, Medizinische Hochschule Hannover, Germany</other_contributors>
    <other_contributors>Norwegian Review Summary, Norwegian Public Hospitals, Norway</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Ina Wille, Helse-Vest RHF, 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">Avgrenet fra: Symptom/sign screening questionnaire, Published archetype [Internet]. openEHR Foundation, openEHR Clinical Knowledge Manager [cited: 2023-07-12]. Available from: https://ckm.openehr.org/ckm/archetypes/1013.1.4432</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">0C9C24C7FD5A3E1351E581E1C5A757D1</other_details>
    <other_details id="build_uid">abca21d3-cc51-4e81-aada-e302d958a4a2</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-snomedct or info@snomed.org.</other_details>
    <other_details id="revision">1.0.7</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Schaffung von Rahmenbedingungen für die Darstellung von Antworten auf vordefinierte Screening-Fragen zu Symptomen oder Anzeichen.</purpose>
      <keywords>Screening, Fragebogen, Beschwerde, Symptom, Störung, Problem, Unwohlsein, Anzeichen</keywords>
      <use>Verwendung als Rahmenbedingung für die Darstellung von Antworten auf vordefinierte Screening-Fragen zu Symptomen oder Anzeichen.&#xD;
&#xD;
Häufige Anwendungsfälle umfassen, sind aber nicht beschränkt auf:&#xD;
- Systematische Befragung in jeder Beratung, zum Beispiel:&#xD;
--- Haben Sie Kopfschmerzen? Ja, Nein, Unbekannt.&#xD;
--- Hatten Sie in den letzten vier Wochen Schwindel? Ja, Nein, Unbekannt.&#xD;
- Spezifische Befragung im Zusammenhang mit der Krankheitsüberwachung.&#xD;
&#xD;
Die Semantik dieses Archetyps ist absichtlich locker, und die Abfrage dieses Archetyps wäre normalerweise nur im Kontext jedes spezifischen Templates nützlich oder sicher. In einem Template würde normalerweise jedes Datenelement in die spezifisch gestellte Frage umbenannt. Wo Wertesätze für allgemeine Anwendungsfälle vorgeschlagen wurden, können diese für die lokale Verwendung angepasst werden, indem die „Text“-Auswahl verwendet wird, um jedem spezifischen Anwendungsfall zu entsprechen.&#xD;
&#xD;
Über die EVENT-Struktur aus dem Referenzmodell kann festgelegt werden, ob sich die Fragen auf einen Zeitpunkt oder einen Zeitraum beziehen. Verwenden Sie eine separate Instanz dieses Archetyps, um zwischen einer Befragung zu unterscheiden, die Informationen über ein Symptom enthält, das zu einem beliebigen Zeitpunkt in der Vergangenheit eingetreten war, und Informationen über ein Symptom, das innerhalb eines bestimmten Zeitintervalls vorhanden war - zum Beispiel den Unterschied zwischen "Ist Ihnen jetzt schwindelig?" im Vergleich zu "Hatten Sie in den letzten 4 Wochen Schwindel?".&#xD;
&#xD;
Die Quelle der Informationen in einer Fragebogenantwort kann in verschiedenen Kontexten variieren, kann jedoch mithilfe des Elements „Information provider“ im Referenzmodell spezifisch identifiziert werden.&#xD;
&#xD;
Dieser Archetyp wurde entwickelt, um als Screening-Tool oder zur Darstellung einfacher Daten im Fragebogenformat zur Verwendung in Situationen wie einem Krankheitsregister verwendet zu werden. Wenn der Screening-Fragebogen das Vorhandensein eines Symptoms oder Anzeichens identifiziert, wird empfohlen, dass das klinische System die spezifischen Details über das Symptom unter Verwendung des Archetyps CLUSTER.symptom_sign, der im SLOT für die Zusätzliche Angaben eingefügt wird, darstellt und beibehält.</use>
      <misuse>Darf nicht verwendet werden, um Details über das Vorhandensein oder Fehlen eines Symptoms außerhalb eines Screening-Kontexts darzustellen. Verwenden Sie zu diesem Zweck CLUSTER.symptom_sign oder CLUSTER.exclusion_symptom_sign.&#xD;
&#xD;
Darf nicht verwendet werden, um Details zu einer einfachen Auswahlliste darzustellen, in der eine Frage entweder als "vorhanden" oder "unbestimmt" aufgezeichnet werden kann. Verwenden Sie dazu OBSERVATION.selection_list.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Ett ramverk för att registrera svar på fördefinierade screeningfrågor om symtom eller tecken.</purpose>
      <keywords>screening, formulär, frågeformulär, självrapporteringsskala, symptom, besvär, problem, tecken</keywords>
      <use>Använd som ett ramverk för att registrera svar på fördefinierade screeningfrågor om symtom eller tecken.&#xD;
&#xD;
Vanliga användningsfall inkluderar, men är inte begränsade till:&#xD;
- Systematisk utredning vid konsultationer, exempelvis:&#xD;
--- Har du huvudvärk? Ja, nej, okänt.&#xD;
--- Har du haft yrsel under de senaste fyra veckorna? Ja, nej, okänt.&#xD;
- Specifika frågor relaterade till övervakning/uppföljning av sjukdom.&#xD;
&#xD;
Semantiken för denna arketyp är avsiktligt generell, sökfrågor baserade på denna arketyp är normalt bara säker och meningsfull inom ramen för varje specifik mall (template). I en mall döps vanligtvis varje dataelement om till den specifika fråga som ställdes. Svarsalternativ har föreslagits för vanliga användningsfall, men kan anpassas för lokal användning genom att använda "text"-valet för att matcha varje specifikt användningsfall.&#xD;
&#xD;
EVENT-strukturen från openEHRs referensmodell kan användas för att specificera om frågorna avser en tidpunkt eller en tidsperiod. Använd separata instanser av denna arketyp för att skilja mellan ett frågeformulär som gäller information om ett symptom som har funnits någon gång tidigare och information om ett symptom inom ett specifikt angivet tidsintervall - till exempel skillnaden mellan "Är du yr nu?" jämfört med "Har du haft yrsel någon gång under de senaste 4 veckorna?&#xD;
&#xD;
Källan till informationen i ett enkätsvar kan variera i olika sammanhang men kan specifikt identifieras med hjälp av elementet 'provider' i referensmodellens ENTRY-klass.&#xD;
&#xD;
Denna arketyp har utformats för att användas som ett screeningverktyg eller för att registrera enkla data i frågeformulärformat för användning i register etc. Om screeningsfrågeformuläret identifierar närvaron av ett symptom eller tecken, rekommenderas att det kliniska systemet även registrerar och behåller de specifika detaljerna om symtomet eller tecknet med hjälp av arketypen CLUSTER.symptom_sign inkapslad i avsedd SLOT för "ytterligare detaljer" i denna arketyp.</use>
      <misuse>Får inte användas för att registrera detaljer om närvaron eller frånvaron av ett symptom, utanför ett screeningsammanhang. Använd CLUSTER.symptom_sign eller CLUSTER.exclusion_symptom_sign inkapslade i andra lämpligare arketyper för dessa ändamål.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fi</code_string>
      </language>
      <purpose>*To create a framework for recording answers about symptoms or signs, to the questions of a pre-defined screening questionnaire. (en)</purpose>
      <keywords>*screening, questionnaire, emotions, pain numbness vertigo (en)</keywords>
      <use>*Use to create a framework for recording answers to pre-defined screening questions about symptoms or signs.&#xD;
&#xD;
Common use cases include, but are not limited to:&#xD;
- Systematic inquiry in any consultation, for example:&#xD;
--- Do you have headaches? Yes, No, Unknown.&#xD;
--- Have you had dizziness in the past four weeks? Yes, No, Unknown.&#xD;
- Specific questioning related to disease surveillance.&#xD;
&#xD;
The semantics of this archetype are intentionally loose, and querying this archetype would normally only be useful or safe within the context of each specific template. In a template, each data element would usually be renamed to the specific question asked. Where value sets have been proposed for common use cases, these can be adapted for local use by using the 'text' choice to match each specific use case.&#xD;
&#xD;
The EVENT structure from the reference model can be used to specify whether the questions relate to point in time or over a period of time. Use a separate instance of this archetype to distinguish between a questionnaire recording information about a symptom that has been present at any time in the past and information about a symptom within a specified time interval - for example the difference between ""Are you dizzy now?" compared to "Have you had any dizziness in the past 4 weeks?&#xD;
&#xD;
The source of the information in a questionnaire response may vary in different contexts but can be specifically identified using the 'Information provider' element in the Reference Model.&#xD;
&#xD;
This archetype has been designed to be used as a screening tool or to record simple questionnaire-format data for use in situations such as a disease registry. If the screening questionnaire identifies the presence of a symptom or sign, it is recommended that clinical system record and persist the specific details about the symptom or sign using the CLUSTER.symptom_sign archetype nested within the Additional details SLOT in this archetype. (en)</use>
      <misuse>*Not to be used to record details about the presence or absence of a symptom, outside of a screening context. Use CLUSTER.symptom_sign or CLUSTER.exclusion_symptom_sign for these purposes.&#xD;
&#xD;
Not to be used to record details about a simple selection list where a question may be recorded as either "present" or "indeterminate". Use OBSERVATION.selection_list 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 å lage et rammeverk for registrering av svar på forhåndsdefinerte spørsmål om symptomer eller sykdomstegn.</purpose>
      <keywords>intervjuskjema, kartleggingskjema, spørreskjema, lidelse, plage, problem, ubehag, symptom, sykdomstegn, lyte, skavank</keywords>
      <use>Brukes for å lage et rammeverk for registrering av svar på forhåndsdefinerte spørsmål om symptomer eller sykdomstegn.&#xD;
&#xD;
Vanlige bruksområder inkluderer, men er ikke begrenset til:&#xD;
- Systematiske spørsmål ved konsultasjoner, for eksempel:&#xD;
--- Har du hodepine? Ja, Nei, Usikker.&#xD;
--- Har du vært plaget med svimmelhet de siste fire ukene? Ja, Nei, Usikker.&#xD;
- Spesifikke spørsmål relatert til overvåkning av sykdommer.&#xD;
&#xD;
Semantikken til denne arketypen er med vilje løst definert, og spørringer etter data i denne arketypen vil normalt bare være hensiktsmessig eller sikkert i konteksten av det spesifikke templatet. I et templat vil hvert dataelement vanligvis døpes om til det (spesifikke) spørsmålet man ønsker svar på. Flere steder er det foreslått verdisett som passer til de vanligste bruksområder, men det er allikevel mulig å tilpasse/endre verdisett for lokal bruk ved å benytte de alternative datatypene DV_TEXT eller DV_BOOLEAN for å harmonere verdisettet til hvert enkelt brukstilfelle.&#xD;
&#xD;
EVENT-strukturen fra arketypens referansemodell kan brukes for å spesifisere om spørsmålene relateres til et tidspunkt eller til et tidsintervall.&#xD;
Bruk egne instanser av denne arketypen for å skille mellom spørsmål om prosedyrer som er gjennomførte på et hvilket som helst tidspunkt og spørsmål om prosedyrer som er gjennomført i et tidsintervall. For eksempel; "Har du hodepine?" sammenlignet med "Har du vært plaget med svimmelhet de siste fire ukene?".&#xD;
&#xD;
Kilden til informasjonen i et spørreskjema kan variere i ulike kontekster, men kan identifiseres spesifikt ved å benytte "Information provider" elementet i openEHR referansemodellen.&#xD;
&#xD;
Denne arketypen er laget for å bli brukt i et spørreskjema eller for å registrere enkle strukturerte data til for eksempel et sykdomsregister. Dersom det i spørreskjemaet identifiseres at et symptom eller sykdomstegn er tilstede, anbefales det at spesifikke detaljer om symptomet registreres og lagres i pasientjournalen i arketypen CLUSTER.symptom_sign (Symptom/Sykdomstegn) i SLOTet "Ytterligere detaljer" i denne arketypen.</use>
      <misuse>Brukes ikke for å registrere detaljer om tilstedeværelse eller fravær av et symptom utenfor konteksten av kartleggingen. Bruk arketypen CLUSTER.symptom_sign (Symptom/sykdomstegn) eller CLUSTER.exclusion_symptom_sign (Eksklusjon av et symptom) for dette formålet.&#xD;
&#xD;
Brukes ikke for å registrere detaljer om en enkel utvalgsliste der et spørsmål kan registreres som enten "Tilstede" eller "Ubestemt". Bruk arketypen OBSERVATION.selection_list for dette formålet.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To create a framework for recording answers to pre-defined screening questions about symptoms or signs.</purpose>
      <keywords>screening, questionnaire, complaint, symptom, disturbance, problem, discomfort, sign</keywords>
      <use>Use to create a framework for recording answers to pre-defined screening questions about symptoms or signs.&#xD;
&#xD;
Common use cases include, but are not limited to:&#xD;
- Systematic inquiry in any consultation, for example:&#xD;
--- Do you have headaches? Yes, No, Unknown.&#xD;
--- Have you had dizziness in the past four weeks? Yes, No, Unknown.&#xD;
- Specific questioning related to disease surveillance.&#xD;
&#xD;
The semantics of this archetype are intentionally loose, and querying this archetype would normally only be useful or safe within the context of each specific template. In a template, each data element would usually be renamed to the specific question asked. Where value sets have been proposed for common use cases, these can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.&#xD;
&#xD;
The EVENT structure from the reference model can be used to specify whether the questions relate to point in time or over a period of time. Use a separate instance of this archetype to distinguish between a questionnaire recording information about a symptom that has been present at any time in the past and information about a symptom within a specified time interval - for example the difference between ""Are you dizzy now?" compared to "Have you had any dizziness in the past 4 weeks?&#xD;
&#xD;
The source of the information in a questionnaire response may vary in different contexts but can be specifically identified using the 'Information provider' element in the Reference Model.&#xD;
&#xD;
This archetype has been designed to be used as a screening tool or to record simple questionnaire-format data for use in situations such as a disease registry. If the screening questionnaire identifies the presence of a symptom or sign, it is recommended that clinical system record and persist the specific details about the symptom or sign using the CLUSTER.symptom_sign archetype nested within the Additional details SLOT in this archetype.</use>
      <misuse>Not to be used to record details about the presence or absence of a symptom, outside of a screening context. Use CLUSTER.symptom_sign or CLUSTER.exclusion_symptom_sign for these purposes.&#xD;
&#xD;
Not to be used to record details about a simple selection list where a question may be recorded as either "present" or "indeterminate". Use OBSERVATION.selection_list for this purpose.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>it</code_string>
      </language>
      <purpose>*To create a framework for recording answers about symptoms or signs, to the questions of a pre-defined screening questionnaire. (en)</purpose>
      <keywords>*screening, questionnaire, emotions, pain numbness vertigo (en)</keywords>
      <use>*Use to create a framework for recording answers to pre-defined screening questions about symptoms or signs.&#xD;
&#xD;
Common use cases include, but are not limited to:&#xD;
- Systematic inquiry in any consultation, for example:&#xD;
--- Do you have headaches? Yes, No, Unknown.&#xD;
--- Have you had dizziness in the past four weeks? Yes, No, Unknown.&#xD;
- Specific questioning related to disease surveillance.&#xD;
&#xD;
The semantics of this archetype are intentionally loose, and querying this archetype would normally only be useful or safe within the context of each specific template. In a template, each data element would usually be renamed to the specific question asked. Where value sets have been proposed for common use cases, these can be adapted for local use by using the 'text' choice to match each specific use case.&#xD;
&#xD;
The EVENT structure from the reference model can be used to specify whether the questions relate to point in time or over a period of time. Use a separate instance of this archetype to distinguish between a questionnaire recording information about a symptom that has been present at any time in the past and information about a symptom within a specified time interval - for example the difference between ""Are you dizzy now?" compared to "Have you had any dizziness in the past 4 weeks?&#xD;
&#xD;
The source of the information in a questionnaire response may vary in different contexts but can be specifically identified using the 'Information provider' element in the Reference Model.&#xD;
&#xD;
This archetype has been designed to be used as a screening tool or to record simple questionnaire-format data for use in situations such as a disease registry. If the screening questionnaire identifies the presence of a symptom or sign, it is recommended that clinical system record and persist the specific details about the symptom or sign using the CLUSTER.symptom_sign archetype nested within the Additional details SLOT in this archetype. (en)</use>
      <misuse>*Not to be used to record details about the presence or absence of a symptom, outside of a screening context. Use CLUSTER.symptom_sign or CLUSTER.exclusion_symptom_sign for these purposes.&#xD;
&#xD;
Not to be used to record details about a simple selection list where a question may be recorded as either "present" or "indeterminate". Use OBSERVATION.selection_list for this purpose. (en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fr</code_string>
      </language>
      <purpose>Créer un cadre pour l'enregistrement des réponses à des questions de dépistage prédéfinies sur les symptômes ou les signes.</purpose>
      <keywords>dépistage</keywords>
      <keywords>questionnaire</keywords>
      <keywords>plainte</keywords>
      <keywords>symptôme</keywords>
      <keywords>perturbation</keywords>
      <keywords>problème</keywords>
      <keywords>gêne</keywords>
      <keywords>signe</keywords>
      <use>A utiliser pour créer un cadre permettant d'enregistrer les réponses à des questions de dépistage prédéfinies concernant des symptômes ou des signes.&#xD;
&#xD;
Les cas d'utilisation courants incluent, mais ne sont pas limités à :&#xD;
- Enquête systématique dans le cadre d'une consultation, par exemple :&#xD;
--- Avez-vous des maux de tête ? Oui, Non, Inconnu.&#xD;
--- Avez-vous eu des vertiges au cours des quatre dernières semaines ? Oui, Non, Inconnu.&#xD;
- Questionnement spécifique lié à la surveillance des maladies.&#xD;
&#xD;
La sémantique de cet archétype est volontairement floue, et l'interrogation de cet archétype ne serait normalement utile ou sûre que dans le contexte de chaque modèle spécifique. Dans un modèle, chaque élément de données est généralement renommé en fonction de la question spécifique posée. Lorsque des ensembles de valeurs ont été proposés pour des cas d'utilisation courants, ils peuvent être adaptés à un usage local en utilisant les types de données DV_TEXT ou DV_BOOLEAN pour correspondre à chaque cas d'utilisation spécifique.&#xD;
&#xD;
La structure EVENT du modèle de référence peut être utilisée pour spécifier si les questions se rapportent à un moment donné ou à une période de temps. Utilisez une instance distincte de cet archétype pour faire la distinction entre un questionnaire enregistrant des informations sur un symptôme qui a été présent à tout moment dans le passé et des informations sur un symptôme dans un intervalle de temps spécifié - par exemple la différence entre « Avez-vous des vertiges en ce moment ? » et « Avez-vous eu des vertiges au cours des 4 dernières semaines ?&#xD;
&#xD;
La source des informations contenues dans une réponse à un questionnaire peut varier dans différents contextes, mais peut être spécifiquement identifiée à l'aide de l'élément « Fournisseur d'informations » du modèle de référence.&#xD;
&#xD;
Cet archétype a été conçu pour être utilisé comme outil de dépistage ou pour enregistrer des données simples sous forme de questionnaire en vue d'une utilisation dans des situations telles qu'un registre des maladies. Si le questionnaire de dépistage identifie la présence d'un symptôme ou d'un signe, il est recommandé que le système clinique enregistre et conserve les détails spécifiques du symptôme ou du signe en utilisant l'archétype CLUSTER.symptom_sign imbriqué dans le SLOT Additional details de cet archétype.</use>
      <misuse>Ne pas utiliser pour enregistrer des détails sur la présence ou l'absence d'un symptôme, en dehors d'un contexte de dépistage. Utiliser CLUSTER.symptom_sign ou CLUSTER.exclusion_symptom_sign à cette fin.&#xD;
&#xD;
Ne pas utiliser pour enregistrer des détails sur une simple liste de sélection où une question peut être enregistrée comme « présente » ou « indéterminée ». Utiliser OBSERVATION.selection_list à cette fin.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>zh-cn</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>
      <keywords>紊乱</keywords>
      <keywords>问题</keywords>
      <keywords>不适</keywords>
      <keywords>体征</keywords>
      <use>旨在建立统一的框架，用于记录针对预先定义的关于症状或体征的筛查问题的答案。&#xD;
&#xD;
常见的用例包括但不仅限于：&#xD;
- 任何就诊过程中系统性的询问，例如：&#xD;
--- 您头痛吗？是、否、未知。&#xD;
--- 您在过去 4 周内是否出现过头晕？是、否、未知。&#xD;
- 与疾病监测（disease surveillance）相关的具体询问。&#xD;
&#xD;
本原始型故意保持着宽松的语义/含义，因而，通常只有在每个具体/特定模板的上下文背景下，针对本原始型的查询才会有用或安全。在具体的模板当中，通常会将每个数据元重命名为所提出的具体/特定问题。如果已经提出了针对常见用例的取值集合，则可以利用数据类型为文本型 DV_TEXT 或布尔型 DV_BOOLEAN 的选项来匹配每个具体/特定的用例，使得能够对此类的取值集合加以改编，以适合本地的使用。&#xD;
&#xD;
参考模型之中的事件结构 EVENT 可用于明确规定这些相应的问题是否与特定的时间点/时刻或时段相关。建议利用本原始型的单独/不同实例来区分记录过去任何时间出现的特定症状信息的调查问卷与指定时段/时间间隔内特定症状的相关信息 - 例如，“你现在头晕吗？”与“过去 4 周内你有没有出现过头晕？”&#xD;
&#xD;
在不同的上下文背景下，调查问卷答复之中信息的来源可能会有所不同，但可以利用参考模型之中的信息提供方数据元“'Information provider”元素来加以具体的标识。&#xD;
&#xD;
本原始型旨在作为筛查工具或者用于记录简单的问卷格式数据，以便将其用于疾病登记之类的情况。如果筛查问卷标识确定了症状或体征的存在情况，则建议临床系统利用嵌套在本原始型的其它详情槽位“Additional details”之中的群簇型症状体征原始型 CLUSTER.symptom_sign 来记录并持久保留关于相应症状或体征的具体详情。</use>
      <misuse>除了筛查的上下文背景之外，并非旨在用于记录关于症状存在情况/存在与否的详情。应当采用群簇型症状体征原始型 CLUSTER.symptom_sign 或群簇型除外症状体征原始型 CLUSTER.exclusion_symptom_sign 来实现此类的目的。&#xD;
&#xD;
并非旨在用于记录关于简单的选项列表的详情：其中，可能会将问题的答案选项记录为 “存在” 或 “不确定”。对于此类的目的，应当采用观察型选项列表原始型 OBSERVATION.selection_list。</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ca</code_string>
      </language>
      <purpose>Crear un marc per registrar respostes a preguntes de cribratge predefinides sobre símptomes o signes.</purpose>
      <keywords>cribratge</keywords>
      <keywords>qüestionari</keywords>
      <keywords>queixa</keywords>
      <keywords>símptoma</keywords>
      <keywords>pertorbació</keywords>
      <keywords>problema</keywords>
      <keywords>malestar</keywords>
      <keywords>signe</keywords>
      <use>Utilitzar per crear un marc per registrar respostes a preguntes de cribratge predefinides sobre símptomes o signes.&#xD;
&#xD;
Els casos d'ús comuns inclouen, entre d'altres:&#xD;
- Consulta sistemàtica en qualsevol consulta, per exemple:&#xD;
--- Té mals de cap? Sí, No, Desconegut.&#xD;
--- Ha tingut marejos en les darreres quatre setmanes? Sí, No, Desconegut.&#xD;
- Preguntes específiques relacionades amb la vigilància de malalties.&#xD;
&#xD;
La semàntica d'aquest arquetip és intencionadament flexible, i consultar aquest arquetip normalment només seria útil o segur dins del context de cada plantilla específica. En una plantilla, cada element de dades normalment es canviaria de nom a la pregunta específica que es fa. Quan s'han proposat conjunts de valors per a casos d'ús comuns, aquests es poden adaptar per a ús local mitjançant l'opció de tipus de dades DV_TEXT o DV_BOOLEAN per coincidir amb cada cas d'ús específic.&#xD;
&#xD;
L'estructura EVENT del model de referència es pot utilitzar per especificar si les preguntes es refereixen a un punt en el temps o a un període de temps. Utilitzeu una instància separada d'aquest arquetip per distingir entre un qüestionari que registra informació sobre un símptoma que ha estat present en qualsevol moment del passat i informació sobre un símptoma dins d'un interval de temps especificat; per exemple, la diferència entre "Està marejat ara?" en comparació amb "Ha tingut marejos en les darreres 4 setmanes?"&#xD;
&#xD;
La font de la informació en una resposta al qüestionari pot variar en diferents contextos, però es pot identificar específicament mitjançant l'element "Proveïdor d'informació" del model de referència.&#xD;
&#xD;
Aquest arquetip s'ha dissenyat per ser utilitzat com a eina de cribratge o per registrar dades simples en format de qüestionari per al seu ús en situacions com ara un registre de malalties. Si el qüestionari de cribratge identifica la presència d'un símptoma o signe, es recomana que el sistema clínic registri i persisteixi els detalls específics sobre el símptoma o signe mitjançant l'arquetip CLUSTER.symptom_sign imbricat dins de l'SLOT Detalls addicionals d'aquest arquetip.</use>
      <misuse>No s'ha d'utilitzar per registrar detalls sobre la presència o absència d'un símptoma, fora d'un context de cribratge. Utilitzeu CLUSTER.symptom_sign o CLUSTER.exclusion_symptom_sign per a aquests propòsits.&#xD;
&#xD;
No s'ha d'utilitzar per registrar detalls sobre una llista de selecció simple on una pregunta es pot registrar com a "present" o "indeterminada". Utilitzeu OBSERVATION.selection_list per a aquest propòsit.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Crear un marco para registrar respuestas a preguntas de detección predefinidas sobre síntomas o signos.</purpose>
      <keywords>cribado</keywords>
      <keywords>cuestionario</keywords>
      <keywords>queja</keywords>
      <keywords>síntoma</keywords>
      <keywords>perturbación</keywords>
      <keywords>problema</keywords>
      <keywords>malestar</keywords>
      <keywords>signo</keywords>
      <use>Se utiliza para crear un marco para registrar las respuestas a preguntas de cribado predefinidas sobre síntomas o signos.&#xD;
&#xD;
Los casos de uso comunes incluyen, entre otros:&#xD;
- Indagación sistemática en cualquier consulta, por ejemplo:&#xD;
--- ¿Tiene dolor de cabeza? Sí, No, Desconocido.&#xD;
--- ¿Ha tenido mareos en las últimas cuatro semanas? Sí, No, Desconocido.&#xD;
- Preguntas específicas relacionadas con la vigilancia de enfermedades.&#xD;
&#xD;
La semántica de este arquetipo es intencionadamente imprecisa, y consultarlo normalmente solo sería útil o seguro en el contexto de cada plantilla específica. En una plantilla, cada elemento de datos se renombraría generalmente según la pregunta específica formulada. Cuando se han propuesto conjuntos de valores para casos de uso comunes, estos se pueden adaptar para uso local utilizando los tipos de datos DV_TEXT o DV_BOOLEAN para que coincidan con cada caso de uso específico.&#xD;
&#xD;
La estructura EVENT del modelo de referencia se puede utilizar para especificar si las preguntas se refieren a un momento específico o a un período de tiempo. Utilice una instancia independiente de este arquetipo para distinguir entre un cuestionario para registrar información sobre un síntoma presente en cualquier momento del pasado e información sobre un síntoma dentro de un intervalo de tiempo específico; por ejemplo, la diferencia entre "¿Se siente mareado ahora?" y "¿Ha tenido mareos en las últimas 4 semanas?".&#xD;
&#xD;
La fuente de información en una respuesta a un cuestionario puede variar según el contexto, pero se puede identificar específicamente mediante el elemento "Proveedor de información" del Modelo de Referencia.&#xD;
&#xD;
Este arquetipo se ha diseñado para usarse como herramienta de cribado o para registrar datos sencillos en formato de cuestionario para su uso en situaciones como un registro de enfermedades. Si el cuestionario de cribado identifica la presencia de un síntoma o signo, se recomienda que el sistema clínico registre y conserve los detalles específicos sobre el síntoma o signo utilizando el arquetipo CLUSTER.symptom_sign, anidado dentro de la ranura "Detalles adicionales" de este arquetipo.</use>
      <misuse>No debe utilizarse para registrar detalles sobre la presencia o ausencia de un síntoma fuera del contexto de un cribado. Utilice CLUSTER.symptom_sign o CLUSTER.exclusion_symptom_sign para estos fines.&#xD;
&#xD;
No debe utilizarse para registrar detalles sobre una lista de selección simple donde una pregunta pueda registrarse como "presente" o "indeterminada". Utilice OBSERVATION.selection_list para este fin.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Sarah Ballout, Natalia Strauch, Alina Rehberg, Martin Koch</author>
    <author id="organisation">Medizinische Hochschule Hannover, Servei Català de la Salut</author>
    <author id="email">ballout.sarah@mh-hannover.de, Strauch.Natalia@mh-hannover.de, rehberg.alina@mh-hannover.de, martinandreaskoch@catsalut.cat</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fi</code_string>
    </language>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Emma Malm, Erik Sundvall</author>
    <author id="organisation">Karolinska University Hospital, Region Stockholm, Karolinska University Hospital, Region Stockholm + Linköping University, Karolinska Institutet + Karolinska University Hospital, Region Stockholm + Linköping University</author>
    <author id="email">emma.malm@cambio.se, erik.sundvall@regionstockholm.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Marit Alice Venheim, Silje Ljosland Bakke, John Tore Valand, Liv Laugen</author>
    <author id="organisation">Helse Vest IKT AS, Helse Bergen, ​Oslo University Hospital, Norway</author>
    <author id="email">marit.alice.venheim@helse-vest-ikt.no, silje.ljosland.bakke@helse-vest-ikt.no, john.tore.valand@helse-vest-ikt.no, liv.laugen@ous-hf.no</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>it</code_string>
    </language>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fr</code_string>
    </language>
    <author id="name">Vanessa Pereira</author>
    <author id="organisation">Luxembourg Institute of Health (LIH)</author>
    <author id="email">vanessapereira@protonmail.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>zh-cn</code_string>
    </language>
    <author id="name">Lin Zhang</author>
    <author id="organisation">Freelancer</author>
    <author id="email">linforest@163.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ca</code_string>
    </language>
    <author id="name">Clara Calleja Vega</author>
    <author id="organisation">CatSalut. Servei Català de la Salut.</author>
    <author id="email">ccalleja@catsalut.cat</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es</code_string>
    </language>
    <author id="name">Clara Calleja Vega</author>
    <author id="organisation">CatSalut. Servei Català de la Salut.</author>
    <author id="email">ccalleja@catsalut.cat</author>
  </translations>
  <uid>
    <value>dcae10b9-634e-4fa7-b695-1995af5c89dd</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-OBSERVATION.symptom_sign_screening.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>OBSERVATION</rm_type_name>
    <occurrences>
      <lower_included>true</lower_included>
      <upper_included>true</upper_included>
      <lower_unbounded>false</lower_unbounded>
      <upper_unbounded>false</upper_unbounded>
      <lower>1</lower>
      <upper>1</upper>
    </occurrences>
    <node_id>at0000</node_id>
    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
      <rm_attribute_name>data</rm_attribute_name>
      <existence>
        <lower_included>true</lower_included>
        <upper_included>true</upper_included>
        <lower_unbounded>false</lower_unbounded>
        <upper_unbounded>false</upper_unbounded>
        <lower>1</lower>
        <upper>1</upper>
      </existence>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>HISTORY</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>1</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0001</node_id>
        <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
          <rm_attribute_name>events</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>EVENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </occurrences>
            <node_id>at0002</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>data</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>ITEM_TREE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0003</node_id>
                <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
                  <rm_attribute_name>items</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>0</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>0</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0034</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>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_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>at0031</code_list>
                            <code_list>at0032</code_list>
                            <code_list>at0033</code_list>
                            <code_list>at0040</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>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_BOOLEAN</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>at0029</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>
                      <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>at0036</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>at0022</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>at0004</node_id>
                        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                          <rm_attribute_name>value</rm_attribute_name>
                          <existence>
                            <lower_included>true</lower_included>
                            <upper_included>true</upper_included>
                            <lower_unbounded>false</lower_unbounded>
                            <upper_unbounded>false</upper_unbounded>
                            <lower>0</lower>
                            <upper>1</upper>
                          </existence>
                          <children xsi:type="C_COMPLEX_OBJECT">
                            <rm_type_name>DV_TEXT</rm_type_name>
                            <occurrences>
                              <lower_included>true</lower_included>
                              <upper_included>true</upper_included>
                              <lower_unbounded>false</lower_unbounded>
                              <upper_unbounded>false</upper_unbounded>
                              <lower>1</lower>
                              <upper>1</upper>
                            </occurrences>
                            <node_id />
                          </children>
                        </attributes>
                      </children>
                      <children xsi:type="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>at0005</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>at0027</code_list>
                                <code_list>at0041</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>
                          <children xsi:type="C_COMPLEX_OBJECT">
                            <rm_type_name>DV_BOOLEAN</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>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_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>
                          <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>
                          <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>at0026</node_id>
                        <includes>
                          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.exclusion_symptom_sign\.v0|openEHR-EHR-CLUSTER\.symptom_sign\.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\.exclusion_symptom_sign\.v0|openEHR-EHR-CLUSTER\.symptom_sign\.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>at0035</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="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>at0039</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>
                  <cardinality>
                    <is_ordered>false</is_ordered>
                    <is_unique>false</is_unique>
                    <interval>
                      <lower_included>true</lower_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>0</lower>
                    </interval>
                  </cardinality>
                </attributes>
              </children>
            </attributes>
          </children>
          <cardinality>
            <is_ordered>false</is_ordered>
            <is_unique>false</is_unique>
            <interval>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </interval>
          </cardinality>
        </attributes>
      </children>
    </attributes>
    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
      <rm_attribute_name>protocol</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>ITEM_TREE</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>1</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0007</node_id>
        <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
          <rm_attribute_name>items</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="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>at0021</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>
          <cardinality>
            <is_ordered>false</is_ordered>
            <is_unique>false</is_unique>
            <interval>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </interval>
          </cardinality>
        </attributes>
      </children>
    </attributes>
  </definition>
  <ontology>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Symptom/sign screening questionnaire</items>
        <items id="description">Series of questions and associated answers used to screen for symptoms or signs.</items>
        <items id="comment">The answers may be self-reported.</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Any event</items>
        <items id="description">Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Symptom/sign name</items>
        <items id="description">Identification of a specific symptom or sign or grouping of symptoms or signs, by name.</items>
        <items id="comment">Coding of the 'Symptom/sign name' with a terminology is preferred, where possible.</items>
      </items>
      <items code="at0005">
        <items id="text">Presence?</items>
        <items id="description">Is there a history of the specific symptom or sign being present?</items>
        <items id="comment">In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Extension</items>
        <items id="description">Additional information required to extend the model with local content or to align with other reference models or formalisms.</items>
        <items id="comment">For example: local information requirements; or additional metadata to align with FHIR.</items>
      </items>
      <items code="at0022">
        <items id="text">Specific symptom/sign</items>
        <items id="description">Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose.</items>
      </items>
      <items code="at0023">
        <items id="text">Yes</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Additional details</items>
        <items id="description">Structured details or questions about the specific symptom or sign.</items>
      </items>
      <items code="at0027">
        <items id="text">Unknown</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">Any symptoms or signs?</items>
        <items id="description">Is there a history of any symptoms or signs relevant for the screening purpose?</items>
        <items id="comment">In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.</items>
      </items>
      <items code="at0029">
        <items id="text">Onset</items>
        <items id="description">Timing of the inital recognition of any symptom or sign relevant for the screening purpose.</items>
        <items id="comment">The 'Onset' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture the onset of symptoms or signs. The specific and intended semantics can be further clarified in a template. &#xD;
&#xD;
For example:&#xD;
Date/time for the date the symptom started. Interval of date/time for a period of time eg. between 1940 and 1942. Text for descriptions like 'Immediately after the operation', or 'Up to one week ago', 'Up to two weeks ago', 'Three weeks ago'. Duration for the individual's age at the onset. Interval of Duration for the approximate age of the individual at the time of onset.</items>
      </items>
      <items code="at0031">
        <items id="text">Yes</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Unknown</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Screening purpose</items>
        <items id="description">The context or reason for screening.</items>
        <items id="comment">This data element is intended to provide collection context for the question/answer groups when queried at a later date. It is not expected that this data element will be exposed to the individual, but only stored in data.&#xD;
For example: 'pre-admission screening' or the name of the actual questionnaire.</items>
      </items>
      <items code="at0035">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the specific symptom/sign question, not captured in other fields.</items>
      </items>
      <items code="at0036">
        <items id="text">Description</items>
        <items id="description">Narrative description about the history of any symptoms or signs relevant for the screening purpose.</items>
      </items>
      <items code="at0037">
        <items id="text">Timing</items>
        <items id="description">Indication of timing related to the specific symptom or sign.</items>
        <items id="comment">The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.</items>
      </items>
      <items code="at0039">
        <items id="text">Additional details</items>
        <items id="description">Structured details or questions about screening for symptoms or signs.</items>
      </items>
      <items code="at0040">
        <items id="text">Unsure</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">Unsure</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="fi">
      <items code="at0000">
        <items id="text">Oire / tuntemus seulontakysely</items>
        <items id="description">*Answers to questions about symptoms or signs in a pre-defined screening questionnaire. (en)</items>
        <items id="comment">*The answers may be self-reported. (en)</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">*Any event(en)</items>
        <items id="description">*Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">*Symptom/sign name (en)</items>
        <items id="description">*Identification of a specific symptom or sign or grouping of symptoms or signs, by name. (en)</items>
        <items id="comment">*Coding of the 'Symptom/sign name' with a terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0005">
        <items id="text">Olemassalolo</items>
        <items id="description">*Is there a history of the specific symptom or sign being present? (en)</items>
        <items id="comment">*In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to extend the model with local content or to align with other reference models or formalisms. (en)</items>
        <items id="comment">*For example: local information requirements; or additional metadata to align with FHIR. (en)</items>
      </items>
      <items code="at0022">
        <items id="text">Oire / tuntemus ryhmitys</items>
        <items id="description">*Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose. (en)</items>
      </items>
      <items code="at0023">
        <items id="text">*Yes (en)</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">*No (en)</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Structured details or questions about the specific symptom or sign. (en)</items>
      </items>
      <items code="at0027">
        <items id="text">Unknown</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">*Any symptoms or signs? (en)</items>
        <items id="description">*Is there a history of any symptoms or signs relatevant for the screening purpose? (en)</items>
        <items id="comment">*In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. (en)</items>
      </items>
      <items code="at0029">
        <items id="text">Toteamisen ajankohta</items>
        <items id="description">*Timing of the initial recognition of any of the symptoms or signs. (en)</items>
        <items id="comment">*The 'Onset' data element is deliberately loosely modelled to support the myriad of ways that it can be used in questionnaires to capture the onset of symptoms or signs. The specific and intended semantics can be further clarified in a template. &#xD;
For example:&#xD;
-Date: The date when the symptom started.&#xD;
-Interval of date/time: A period of time eg. between &#xD;
 1940 and 1942.&#xD;
-Text: 'Immediately after the operation', or 'Up to one week ago', 'Up to two weeks ago', 'Three weeks ago'.&#xD;
-Duration:  The individuals age at the time of onset.&#xD;
-Interval of Duration: The approximate age of the individual at the time of onset. (en)</items>
      </items>
      <items code="at0031">
        <items id="text">*Yes (en)</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">*No (en)</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Unknown</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">*Screening purpose(en)</items>
        <items id="description">*The context or reason for screening. (en)</items>
        <items id="comment">*For example: pre-admission screening or the name of the actual questionnaire. (en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the specific symptom/sign question, not captured in other fields. (en)</items>
      </items>
      <items code="at0036">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the history of any symptoms or signs relevant for the screening purpose. (en)</items>
      </items>
      <items code="at0039">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Structured details or questions about screening for symptoms or signs. (en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Timing (en)</items>
        <items id="description">*Indication of timing related to the specific symptom or sign. (en)</items>
        <items id="comment">*The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. (en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Kartleggingsspørsmål om symptomer/sykdomstegn</items>
        <items id="description">Spørsmål og tilhørende svar som brukes til å kartlegge symptomer eller sykdomstegn.</items>
        <items id="comment">Svarene kan være selvrapporterte.</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Uspesifisert hendelse</items>
        <items id="description">Standard, uspesifisert tidspunkt eller tidsintervall som kan defineres mer eksplisitt i et templat eller i en applikasjon.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Navn på symptom/sykdomstegn</items>
        <items id="description">Navn på det spesifikke symptomet eller sykdomstegnet; eller gruppen av symptomer eller sykdomstegn.</items>
        <items id="comment">Navnet på symptom/sykdomstegn bør kodes med en terminologi om mulig.</items>
      </items>
      <items code="at0005">
        <items id="text">Tilstede?</items>
        <items id="description">Har det spesifikke symptomet eller sykdomstegnet noen gang vært til stede?</items>
        <items id="comment">Navnet på dataelementet kan omformuleres til det spesifikke spørsmålet i et templat eller brukergrensesnitt. Det foreslåtte verdisettet kan tilpasses/endres i det enkelte bruksområde ved å benytte de alternative datatypene DV_TEXT eller DV_BOOLEAN.</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Tilleggsinformasjon</items>
        <items id="description">Ytterligere informasjon som trengs for å kunne registrere lokalt definert innhold eller for å tilpasse til andre referansemodeller/formalismer.</items>
        <items id="comment">For eksempel lokale informasjonsbehov eller ytterligere metadata for å kunne tilpasse til tilsvarende konsepter i FHIR.</items>
      </items>
      <items code="at0022">
        <items id="text">Spesifikt symptom/sykdomstegn</items>
        <items id="description">Detaljer om et spesifikt symptom eller sykdomstegn, eller gruppe av symptomer eller sykdomstegn som er innenfor kartleggingsformålet.</items>
      </items>
      <items code="at0023">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">Nei</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Strukturerte detaljer eller spørsmål om det spesifikke symptomet eller sykdomstegnet.</items>
      </items>
      <items code="at0027">
        <items id="text">Ukjent</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">Symptomer eller sykdomstegn?</items>
        <items id="description">Finnes det noen tidligere symptomer eller sykdomstegn som er innenfor kartleggingsformålet?</items>
        <items id="comment">Navnet på dataelementet kan omformuleres til det spesifikke spørsmålet i et templat eller brukergrensesnitt. Det foreslåtte verdisettet kan tilpasses/endres i det enkelte bruksområde ved å benytte de alternative datatypene DV_TEXT eller DV_BOOLEAN.</items>
      </items>
      <items code="at0029">
        <items id="text">Debut</items>
        <items id="description">Tidsrommet da en først oppdaget noen av symptomene eller sykdomstegene som er innenfor kartleggingsformålet.</items>
        <items id="comment">Dataelementet "Debut" er løst modellert for å støtte ulike måter spørsmål om tidsrom for debut av et symptom eller sykdomstegn stilles i et spørreskjema. Den spesifikke og tiltenkte semantikken defineres i et templat. &#xD;
For eksempel: Dato/klokkeslett brukes for dato for når symptomene først ble oppdaget. Intervall av dato/ klokkeslett brukes for å sette en tidsperiode, for eksempel mellom 1940 og 1942. Tekst brukes for spørsmålstillinger som "Rett etter en operasjon", "For en uke siden", "Opp til to uker siden", "Tre uker siden". Varighet brukes for å registrere individets alder ved debut. Intervall av varighet for å registrere tilnærmet alder ved debut.</items>
      </items>
      <items code="at0031">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Nei</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Ukjent</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Kartleggingsformål</items>
        <items id="description">Konteksten eller årsaken for kartleggingen.</items>
        <items id="comment">Dette dataelementet er ment for å sette en kontekst for spørsmålene om man senere ønsker å gjøre spørringer på dataene. Det er ikke forventet at dette dataelementet skal være synlig for en bruker av skjemaet, men kun tilgjengelig i de lagrede dataene. &#xD;
For eksempel: "Pre operativ screening" eller navnet på det faktiske spørreskjemaet.</items>
      </items>
      <items code="at0035">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om det spesifikke symptom- eller sykdomstegnspørsmålet som ikke er omfattet av andre felt.</items>
      </items>
      <items code="at0036">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse om symptomer eller sykdomstegn som er innenfor kartleggingsformålet.</items>
      </items>
      <items code="at0037">
        <items id="text">Tidsangivelse</items>
        <items id="description">Tidsangivelse for symptomet eller sykdomstegnet.</items>
        <items id="comment">Dataelementet "Tidsangivelse" er med hensikt løst modellert for å støtte ulike måter å angi tidsangivelser for symptomet eller sykdomstegnet i et spørreskjema. Den konkrete semantikken defineres i templatet. For eksempel: Symptomet eller sykdomstegnet faktiske dato og/eller klokkeslett, start- og sluttid for symptomet eller sykdomstegnet, et tidsintervall for når for symptomet eller sykdomstegnet oppstod, varigheten for symptomet eller sykdomstegnet, individets alder på tidspunktet symptomet eller sykdomstegnet oppstod, eller hvor lenge det siden det oppstod. Kan være en deldato, for eksempel bare år, ved å bruke datatypen DV_DATE_TIME.</items>
      </items>
      <items code="at0039">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Strukturerte detaljer eller spørsmål om kartleggingen av problemer eller diagnoser.</items>
      </items>
      <items code="at0040">
        <items id="text">Usikker</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">Usikker</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Screening-Fragebogen zur Symptomen/Anzeichen</items>
        <items id="description">Eine Reihe von Fragen und zugehörigen Antworten, die zum Screening auf Symptome oder Anzeichen verwendet werden.</items>
        <items id="comment">Die Antworten können selbst berichtet werden.</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Beliebiges Ereignis</items>
        <items id="description">Standardwert, ein undefinierter/s Zeitpunkt oder Intervallereignis, das explizit im Template oder zur Laufzeit der Anwendung definiert werden kann.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Name des Symptoms/Anzeichens</items>
        <items id="description">Identifizierung eines bestimmten Symptoms oder Anzeichens oder einer Gruppe von Symptomen oder Anzeichen nach Namen.</items>
        <items id="comment">Die Kodierung des „Name des Symptoms/Anzeichens“ mit einer Terminologie wird nach Möglichkeit bevorzugt.</items>
      </items>
      <items code="at0005">
        <items id="text">Vorhanden?</items>
        <items id="description">Gibt es eine Vorgeschichte, bei der das spezifische Symptom oder Anzeichen vorhanden war?</items>
        <items id="comment">In einem Template würde das Datenelement normalerweise in die spezifisch gestellte Frage umbenannt. Der vorgeschlagene Wertesatz kann für die lokale Verwendung angepasst werden, indem der Choice-Datentyp DV_TEXT oder DV_BOOLEAN verwendet wird, um jedem spezifischen Anwendungsfall zu entsprechen.</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Erweiterung</items>
        <items id="description">Zusätzliche Informationen zur Erfassung lokaler Inhalte oder Anpassung an andere Referenzmodelle/Formalismen.</items>
        <items id="comment">Zum Beispiel: Lokaler Informationsbedarf oder zusätzliche Metadaten zur Anpassung an FHIR-Ressourcen.</items>
      </items>
      <items code="at0022">
        <items id="text">Spezifisches Symptom/Anzeichen</items>
        <items id="description">Details zu einem bestimmten Symptom oder Anzeichen oder zu einer bestimmten Gruppe von Symptomen oder Anzeichen, die für das Screening relevant sind.</items>
      </items>
      <items code="at0023">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">Nein</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Zusätzliche Angaben</items>
        <items id="description">Strukturierte Angaben oder Fragen zum konkreten Symptom oder Anzeichen.</items>
      </items>
      <items code="at0027">
        <items id="text">Unbekannt</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">Irgendwelche Symptome oder Anzeichen?</items>
        <items id="description">Gibt es eine Vorgeschichte von Symptomen oder Anzeichen im Zusammenhang mit dem Screening-Zweck?</items>
        <items id="comment">In einem Template würde das Datenelement normalerweise in die spezifisch gestellte Frage umbenannt. Der vorgeschlagene Wertesatz kann für die lokale Verwendung angepasst werden, indem der Choice-Datentyp DV_TEXT oder DV_BOOLEAN verwendet wird, um jedem spezifischen Anwendungsfall zu entsprechen.</items>
      </items>
      <items code="at0029">
        <items id="text">Auftreten</items>
        <items id="description">Zeitpunkt der erstmaligen Erkennung eines für das Screening relevanten Symptoms oder Anzeichens.</items>
        <items id="comment">Das Datenelement „Auftreten“ wurde absichtlich locker modelliert, um die unzähligen Möglichkeiten zu unterstützen, wie es in Fragebögen verwendet werden können, um zu erfassen, wann ein Symptom oder Anzeichen aufgetreten war. Die spezifische und beabsichtigte Semantik kann in einem Template weiter präzisiert werden.&#xD;
&#xD;
Zum Beispiel: &#xD;
Datum/Uhrzeit für Beginn des Symptoms. Intervall von Datum/Uhrzeit für einen Zeitraum, z. B. zwischen 1940 und 1942. Text für Beschreibungen wie "Unmittelbar nach der Operation" oder "Bis vor einer Woche", "Bis vor zwei Wochen", "Vor drei Wochen". Dauer für das Alter der Person zu Beginn. Intervall der Dauer für das ungefähre Alter der Person zum Zeitpunkt des Beginns.</items>
      </items>
      <items code="at0031">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Nein</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Unbekannt</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Zweck des Screenings</items>
        <items id="description">Der Kontext oder Grund für das Screening.</items>
        <items id="comment">Dieses Datenelement soll bei einer späteren Abfrage den Erhebungskontext für die Frage/Antwort-Gruppen bereitstellen. Es wird nicht erwartet, dass dieses Datenelement der Person belichtet wird, sondern nur in Daten gespeichert wird. &#xD;
Zum Beispiel: "Screening vor der Aufnahme" oder der Name des eigentlichen Fragebogens.</items>
      </items>
      <items code="at0035">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Beschreibung über die spezifische Frage zum Symptom/Anzeichen, die nicht in anderen Bereichen erfasst wird.</items>
      </items>
      <items code="at0036">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung über die Geschichte der Symptome oder Anzeichen, die für das Screening relevant sind.</items>
      </items>
      <items code="at0037">
        <items id="text">Zeitpunkt</items>
        <items id="description">Angabe des Zeitpunkts im Zusammenhang mit dem spezifischen Symptom oder Zeichen.</items>
        <items id="comment">Das Datenelement „Zeitpunkt“ wurde bewusst locker modelliert, um die unzähligen Möglichkeiten zu unterstützen, wie es in Fragebögen verwendet werden kann, um zu erfassen, wann das spezifische Symptom oder Zeichen aufgetreten ist. Die spezifische und beabsichtigte Semantik kann in einem Template weiter verdeutlicht werden. Zum Beispiel: das tatsächliche Datum und/oder die tatsächliche Uhrzeit; die Start- und Stoppzeit für das Auftreten eines bestimmten Symptoms oder Zeichens; der Zeitraum, in dem das spezifische Symptom oder Zeichen auftrat; die Dauer des spezifischen Symptoms oder Anzeichens; das Alter der Person zum Zeitpunkt des Auftretens des spezifischen Symptoms oder Anzeichens; oder die Zeitspanne, seit es aufgetreten ist. Bei Verwendung des Datentyps DV_DATE_TIME ist ein Teildatum gültig, um nur ein Jahr aufzuzeichnen.</items>
      </items>
      <items code="at0039">
        <items id="text">Zusätzliche Angaben</items>
        <items id="description">Strukturierte Angaben oder Fragen zum Screening von Symptomen/Anzeichen.</items>
      </items>
      <items code="at0040">
        <items id="text">Unsicher</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">Unsicher</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="it">
      <items code="at0000">
        <items id="text">Questionario di screening dei sintomi/segni</items>
        <items id="description">*Answers to questions about symptoms or signs in a pre-defined screening questionnaire. (en)</items>
        <items id="comment">*The answers may be self-reported. (en)</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Qualsiasi evento</items>
        <items id="description">Evento predefinito, non specificato nel tempo o nell'intervallo di tempo, che può essere definito esplicitamente in un modello o in fase di esecuzione.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">*Symptom/sign name (en)</items>
        <items id="description">*Identification of a specific symptom or sign or grouping of symptoms or signs, by name. (en)</items>
        <items id="comment">*Coding of the 'Symptom/sign name' with a terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0005">
        <items id="text">Presenza?</items>
        <items id="description">*Is there a history of the specific symptom or sign being present? (en)</items>
        <items id="comment">*In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Estensione</items>
        <items id="description">*Additional information required to extend the model with local content or to align with other reference models or formalisms. (en)</items>
        <items id="comment">*For example: local information requirements; or additional metadata to align with FHIR. (en)</items>
      </items>
      <items code="at0022">
        <items id="text">Sintomo/segno specifico</items>
        <items id="description">*Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose. (en)</items>
      </items>
      <items code="at0023">
        <items id="text">*Yes (en)</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">*No (en)</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Structured details or questions about the specific symptom or sign. (en)</items>
      </items>
      <items code="at0027">
        <items id="text">Indeterminato</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">*Any symptoms or signs? (en)</items>
        <items id="description">*Is there a history of any symptoms or signs relatevant for the screening purpose? (en)</items>
        <items id="comment">*In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. (en)</items>
      </items>
      <items code="at0029">
        <items id="text">Inizio di qualsiasi sintomo o segno</items>
        <items id="description">*Timing of the initial recognition of any of the symptoms or signs. (en)</items>
        <items id="comment">*The 'Onset' data element is deliberately loosely modelled to support the myriad of ways that it can be used in questionnaires to capture the onset of symptoms or signs. The specific and intended semantics can be further clarified in a template. &#xD;
For example:&#xD;
-Date: The date when the symptom started.&#xD;
-Interval of date/time: A period of time eg. between &#xD;
 1940 and 1942.&#xD;
-Text: 'Immediately after the operation', or 'Up to one week ago', 'Up to two weeks ago', 'Three weeks ago'.&#xD;
-Duration:  The individuals age at the time of onset.&#xD;
-Interval of Duration: The approximate age of the individual at the time of onset. (en)</items>
      </items>
      <items code="at0031">
        <items id="text">*Yes (en)</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">*No (en)</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Indeterminato</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Scopo dello screening</items>
        <items id="description">*The context or reason for screening. (en)</items>
        <items id="comment">*For example: pre-admission screening or the name of the actual questionnaire. (en)</items>
      </items>
      <items code="at0035">
        <items id="text">Commento</items>
        <items id="description">*Additional narrative about the specific symptom/sign question, not captured in other fields. (en)</items>
      </items>
      <items code="at0036">
        <items id="text">Descrizione</items>
        <items id="description">*Narrative description about the history of any symptoms or signs relevant for the screening purpose. (en)</items>
      </items>
      <items code="at0039">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Structured details or questions about screening for symptoms or signs. (en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Timing (en)</items>
        <items id="description">*Indication of timing related to the specific symptom or sign. (en)</items>
        <items id="comment">*The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. (en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Frågeformulär för symptom och andra tecken</items>
        <items id="description">Lista av frågor och tillhörande svarsalternativ, används för att screena efter symtom eller tecken.</items>
        <items id="comment">Svaren kan vara självrapporterade.</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Ospecificerad händelse</items>
        <items id="description">Ospecificerad standardhändelse vid en tidpunkt eller inom ett tidsintervall som explicit kan definieras i en mall eller genereras automatiskt av vissa IT-system.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Symptom/tecken-benämning</items>
        <items id="description">Benämning på det symptom eller annat tecken (eller grupp av dessa) som screenas.</items>
        <items id="comment">Kodning av 'Symtom/teckennamn' med en terminologi är att föredra, om möjligt.</items>
      </items>
      <items code="at0005">
        <items id="text">Närvarande?</items>
        <items id="description">*Is there a history of the specific symptom or sign being present? (en)</items>
        <items id="comment">I en mall skulle dataelementet vanligtvis döpas om till den specifika fråga som ställdes till användaren. De föreslagna svarsalternativen kan anpassas för lokal användning genom att välja DV_TEXT eller DV_BOOLEAN datatyper för att matcha varje specifikt användningsfall.</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Tilläggsinformation</items>
        <items id="description">Plats för att infoga tilläggsinformation som krävs för lokala anpassningar eller anpassning till andra referensmodeller eller formella krav.</items>
        <items id="comment">Exempelvis lokala informationskrav eller metadata för anpassning till FHIR- eller CIMI-motsvarigheter.</items>
      </items>
      <items code="at0022">
        <items id="text">Specifika symptom/tecken</items>
        <items id="description">Detaljer om ett specifikt symptom eller tecken eller gruppering av symtom eller tecken som är relevanta för screeningändamålet.</items>
      </items>
      <items code="at0023">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">Nej</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Ytterligare detaljer</items>
        <items id="description">Ytterligare detaljer relaterade till det specifika symptomet eller tecknet.</items>
      </items>
      <items code="at0027">
        <items id="text">Okänt</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">Förekommer några symptom eller andra tecken?</items>
        <items id="description">Har det förekommit några symtom eller tecken som är relevanta för screeningändamålet?</items>
        <items id="comment">I en mall skulle dataelementet vanligtvis döpas om till den specifika fråga som ställdes. Den föreslagna svarsalternativen kan anpassas för lokal användning genom att använda datatyperna DV_TEXT eller DV_BOOLEAN för att matcha varje specifikt användningsfall</items>
      </items>
      <items code="at0029">
        <items id="text">Debut</items>
        <items id="description">Datum/tid då symptom eller andra tecken relevanta för screeningändamålet först upptäcktes.</items>
        <items id="comment">"Debut"-dataelementet har medvetet modellerats flexibelt för att stödja de otaliga sätt som det kan användas i frågeformulär för att fånga uppkomsten av symtom eller tecken. Den specifika och avsedda semantiken kan ytterligare förtydligas i en mall.&#xD;
&#xD;
Till exempel:&#xD;
Datum/tid för när symtomet började. Intervall för datum/tid under en tidsperiod, t.ex. mellan 1940 och 1942. Text för beskrivningar som 'Omedelbart efter operationen' eller 'Upp till en vecka sedan', 'Upp till två veckor sedan', 'Tre veckor sedan'. Varaktighet (duration) för individens ålder vid debut. Intervall av Varaktighet (duration) för individens ungefärliga ålder vid tidpunkten för debut.</items>
      </items>
      <items code="at0031">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Nej</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Okänt</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Screeningssyfte</items>
        <items id="description">Sammanhang eller orsak till screening.</items>
        <items id="comment">Detta dataelement är avsett att ange sammanhanget för frågor/svar-grupperna när formuläret efterfrågas vid ett senare tillfälle. Det förväntas inte att detta dataelement kommer att visas för användarna som fyller i formuläret, utan endast lagras i data.&#xD;
&#xD;
Exempel: "screening inför inskrivning" eller namnet på själva frågeformuläret.</items>
      </items>
      <items code="at0035">
        <items id="text">Kommentar</items>
        <items id="description">Kommentarer avseende det specifika symptomet eller tecknrt som inte beskrivs i övriga fält.</items>
      </items>
      <items code="at0036">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning om alla symptom eller andra tecken relevanta för screeningändamålet</items>
      </items>
      <items code="at0037">
        <items id="text">*Timing (en)</items>
        <items id="description">*Indication of timing related to the specific symptom or sign. (en)</items>
        <items id="comment">*The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. (en)</items>
      </items>
      <items code="at0039">
        <items id="text">Screening-detaljer eller frågor</items>
        <items id="description">Strukturerade detaljer eller frågor relaterade till screening av symptom och tecken</items>
      </items>
      <items code="at0040">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="fr">
      <items code="at0000">
        <items id="text">Questionnaire de dépistage des symptômes/signes</items>
        <items id="description">Série de questions et de réponses associées utilisées pour dépister des symptômes ou des signes.</items>
        <items id="comment">Les réponses peuvent être autodéclarées.</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tout événement</items>
        <items id="description">Par défaut, point dans le temps non spécifié ou événement d'intervalle qui peut être explicitement défini dans un modèle ou au moment de l'exécution.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Symptôme/nom du signe</items>
        <items id="description">Identification d'un symptôme ou d'un signe spécifique ou d'un groupe de symptômes ou de signes, par son nom.</items>
        <items id="comment">Dans la mesure du possible, il est préférable de coder le « nom du symptôme/signe » à l'aide d'une terminologie.</items>
      </items>
      <items code="at0005">
        <items id="text">Présence ?</items>
        <items id="description">Y a-t-il des antécédents de présence du symptôme ou du signe en question ?</items>
        <items id="comment">Dans un modèle, l'élément de données est généralement renommé en fonction de la question spécifique posée. L'ensemble de valeurs proposé peut être adapté à un usage local en utilisant les types de données DV_TEXT ou DV_BOOLEAN pour répondre à chaque cas d'utilisation spécifique.</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Extension</items>
        <items id="description">Informations supplémentaires nécessaires pour étendre le modèle au contenu local ou pour l'aligner sur d'autres modèles de référence ou formalismes.</items>
        <items id="comment">Par exemple : exigences locales en matière d'information ou métadonnées supplémentaires pour s'aligner sur FHIR.</items>
      </items>
      <items code="at0022">
        <items id="text">Symptôme/signe spécifique</items>
        <items id="description">Détails concernant un symptôme ou un signe spécifique ou un groupe de symptômes ou de signes en rapport avec l'objectif du dépistage.</items>
      </items>
      <items code="at0023">
        <items id="text">Oui</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">Non</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails ou questions structurés sur le symptôme ou le signe spécifique.</items>
      </items>
      <items code="at0027">
        <items id="text">Inconnu</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">Des symptômes ou des signes ?</items>
        <items id="description">Y a-t-il des antécédents de symptômes ou de signes pertinents pour le dépistage ?</items>
        <items id="comment">Dans un modèle, l'élément de données est généralement renommé en fonction de la question spécifique posée. L'ensemble de valeurs proposé peut être adapté à un usage local en utilisant les types de données DV_TEXT ou DV_BOOLEAN pour répondre à chaque cas d'utilisation spécifique.</items>
      </items>
      <items code="at0029">
        <items id="text">Début</items>
        <items id="description">Moment de la reconnaissance initiale de tout symptôme ou signe pertinent pour le dépistage.</items>
        <items id="comment">L'élément de données « Onset » a été délibérément modélisé de manière lâche afin de prendre en charge la myriade de façons dont il peut être utilisé dans les questionnaires pour saisir l'apparition de symptômes ou de signes. La sémantique spécifique et voulue peut être précisée dans un modèle. &#xD;
&#xD;
Par exemple :&#xD;
Date/heure pour la date d'apparition du symptôme. Intervalle de date/heure pour une période de temps, par exemple entre 1940 et 1942. Texte pour des descriptions telles que « Immédiatement après l'opération », ou « Il y a une semaine », « Il y a deux semaines », « Il y a trois semaines ». Durée pour l'âge de l'individu au moment de l'apparition de la maladie. Intervalle de durée pour l'âge approximatif de l'individu au moment de l'apparition.</items>
      </items>
      <items code="at0031">
        <items id="text">Oui</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Non</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Inconnu</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Objectif du dépistage</items>
        <items id="description">Le contexte ou la raison du dépistage.</items>
        <items id="comment">Cet élément de données est destiné à fournir un contexte de collecte pour les groupes de questions/réponses lors d'une interrogation ultérieure. Il n'est pas prévu que cet élément de données soit exposé à l'individu, mais seulement stocké dans les données.&#xD;
Par exemple : « dépistage avant l'admission » ou le nom du questionnaire proprement dit.</items>
      </items>
      <items code="at0035">
        <items id="text">Commentaire</items>
        <items id="description">Commentaire supplémentaire sur la question du symptôme/signe spécifique, non saisi dans d'autres champs.</items>
      </items>
      <items code="at0036">
        <items id="text">Description</items>
        <items id="description">Description narrative des antécédents de tout symptôme ou signe pertinent pour le dépistage.</items>
      </items>
      <items code="at0037">
        <items id="text">Timing</items>
        <items id="description">Indication de la chronologie liée au symptôme ou au signe spécifique.</items>
        <items id="comment">L'élément d'information « Timing » a été délibérément modélisé de manière souple afin de prendre en charge la myriade de façons dont il peut être utilisé dans les questionnaires pour saisir le moment où le symptôme ou le signe spécifique s'est manifesté. La sémantique spécifique et prévue peut être précisée dans un modèle. Par exemple : la date et/ou l'heure réelle ; l'heure de début et de fin du symptôme ou du signe spécifique ; l'intervalle de temps pendant lequel le symptôme ou le signe spécifique est apparu ; la durée du symptôme ou du signe spécifique ; l'âge de la personne au moment de l'apparition du symptôme ou du signe spécifique ; ou la durée écoulée depuis l'apparition du symptôme ou du signe. Une date partielle est valable, en utilisant le type de données DV_DATE_TIME, pour enregistrer seulement une année.</items>
      </items>
      <items code="at0039">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails ou questions structurées sur le dépistage des symptômes ou des signes.</items>
      </items>
      <items code="at0040">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="zh-cn">
      <items code="at0000">
        <items id="text">症状/体征筛查问卷</items>
        <items id="description">用于筛查症状或体征的一系列的问题及其关联的答案选项。</items>
        <items id="comment">答案选项可能是自行报告的。</items>
      </items>
      <items code="at0001">
        <items id="text">History</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">任何事件</items>
        <items id="description">可在模板之中或运行时明确定义的默认的、未明确指定的时间点型/时间型或时间区间型/时间间隔型事件。</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">症状/体征名称</items>
        <items id="description">利用名称对的特定症状或体征或者症状或体征分组的标识。</items>
        <items id="comment">尽可能首选采用术语标准对 “症状/体征名称” 进行编码。</items>
      </items>
      <items code="at0005">
        <items id="text">是否存在？</items>
        <items id="description">是否存在关于出现特定症状或体征的病史？</items>
        <items id="comment">在具体的模板当中，通常会将每个数据元重命名为所提出的具体/特定问题。可以利用数据类型为文本型 DV_TEXT 或布尔型 DV_BOOLEAN 的选项来匹配每个具体/特定的用例，从而针对本地的用途，对所已经提出的取值集合加以改编。</items>
      </items>
      <items code="at0007">
        <items id="text">Item tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">扩展</items>
        <items id="description">采集本地内容或与其他参考模型/形式保持一致时所需的其他信息。</items>
        <items id="comment">例如：本地信息需求要求，或者是与 FHIR 保持一致时所需的其他元数据。</items>
      </items>
      <items code="at0022">
        <items id="text">具体症状/体征</items>
        <items id="description">关于与筛查目的相关的特定症状或体征或者症状或体征分组的详情。</items>
      </items>
      <items code="at0023">
        <items id="text">是</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">否</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">其他详情</items>
        <items id="description">关于特定症状或体征的结构化详情或问题。</items>
      </items>
      <items code="at0027">
        <items id="text">未知</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">是否存在任何的症状或体征？</items>
        <items id="description">是否存在任何与筛查目的相关的症状或体征的病史？</items>
        <items id="comment">在具体的模板当中，通常会将每个数据元重命名为所提出的具体/特定问题。可以利用数据类型为文本型 DV_TEXT 或布尔型 DV_BOOLEAN 的选项来匹配每个具体/特定的用例，从而针对本地的用途，对所已经提出的取值集合加以改编。</items>
      </items>
      <items code="at0029">
        <items id="text">起始时间</items>
        <items id="description">最初认识到/识别与当前筛查目的相关的任何症状或体征的时间。</items>
        <items id="comment">起始时间数据元“Onset”有意采用了宽松的建模，以便能够支持在问卷当中利用它来采集症状或体征起始/发作时间的无数种方式。可以在模板当中进一步澄清具体的预定语义。&#xD;
&#xD;
例如：&#xD;
症状起始/发作日期的日期/时间。代表时段/一段时间的日期/时间区间。1940年至1942年期间。描述性的文本，如“手术后立即”或“最多1周前”、“最多2周前”、“3 周前”。起始/发作时个体年龄的持续时长。起始/发作时个体大致年龄的持续时长区间。</items>
      </items>
      <items code="at0031">
        <items id="text">是</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">否</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">未知</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">筛查目的</items>
        <items id="description">筛查的上下文背景或原因。</items>
        <items id="comment">本数据元旨在为后续查询时为问题/答案选项组提供关于数据采集的上下文背景信息。预计并不会将本数据元的信息暴露给相应的个人公开，而仅仅会将其存储在数据当中。&#xD;
例如：“入院前筛查”或实际问卷的名称。</items>
      </items>
      <items code="at0035">
        <items id="text">备注</items>
        <items id="description">关于特定症状/体征问题的，其他字段之中并未采集的其他叙述。</items>
      </items>
      <items code="at0036">
        <items id="text">描述</items>
        <items id="description">关于与筛选目的相关的任何症状或体征的病史的叙述性描述。</items>
      </items>
      <items code="at0037">
        <items id="text">时间特征</items>
        <items id="description">表明与特定症状或体征相关的时间特征。</items>
        <items id="comment">时间特征数据元“Timing”有意被特意进行了松散的建模，以便能够支持在问卷当中利用它来采集症状或体征发生时间的无数种方式。可以在模板当中进一步澄清具体的预定语义。例如：实际的日期和/或时间、特定症状或体征的开始和停止时间、特定症状或体征出现的时间区间；特定症状或体征的持续时长、出现特定症状或体征时的个人年龄，或者是自发生特定症状或体征以来的持续时长。可以利用日期时间型数据类型 DV_DATE_TIME ，采用部分型/并不完整的日期来合法有效地仅仅记录年份。</items>
      </items>
      <items code="at0039">
        <items id="text">其他详情</items>
        <items id="description">关于症状或体征筛查的结构化详情或问题。</items>
      </items>
      <items code="at0040">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="ca">
      <items code="at0000">
        <items id="text">Qüestionari de detecció de símptomes/signes</items>
        <items id="description">Sèrie de preguntes i respostes associades que s'utilitzen per detectar símptomes o signes.</items>
        <items id="comment">Les respostes poden ser autoinformades.</items>
      </items>
      <items code="at0001">
        <items id="text">Historial</items>
        <items id="description">@internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Qualsevol esdeveniment</items>
        <items id="description">Esdeveniment per defecte, puntual o d'interval no especificat, que es pot definir explícitament en una plantilla o en temps d'execució.</items>
      </items>
      <items code="at0003">
        <items id="text">Arbre</items>
        <items id="description">@internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Nom del símptoma/signe</items>
        <items id="description">Identificació d'un símptoma o signe específic o d'un grup de símptomes o signes, pel seu nom.</items>
        <items id="comment">Sempre que sigui possible, es prefereix la codificació del "nom del símptoma/signe" amb una terminologia.</items>
      </items>
      <items code="at0005">
        <items id="text">Presència?</items>
        <items id="description">Hi ha un historial de la presència del símptoma o signe específic?</items>
        <items id="comment">En una plantilla, l'element de dades normalment es rebatejarà amb la pregunta específica que es fa. El conjunt de valors proposat es pot adaptar per a ús local mitjançant l'opció de tipus de dades DV_TEXT o DV_BOOLEAN per adaptar-lo a cada cas d'ús específic.</items>
      </items>
      <items code="at0007">
        <items id="text">Arbre d'elements</items>
        <items id="description">@internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Extensió</items>
        <items id="description">Informació addicional necessària per ampliar el model amb contingut local o per alinear-lo amb altres models o formalismes de referència.</items>
        <items id="comment">Per exemple: requisits d'informació local; o metadades addicionals per alinear-se amb el FHIR.</items>
      </items>
      <items code="at0022">
        <items id="text">Símptoma/signe específic</items>
        <items id="description">Detalls sobre un símptoma o signe específic o un grup de símptomes o signes rellevants per al propòsit del cribratge.</items>
      </items>
      <items code="at0023">
        <items id="text">Sí</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Detalls addicionals</items>
        <items id="description">Detalls o preguntes estructurades sobre el símptoma o signe específic.</items>
      </items>
      <items code="at0027">
        <items id="text">Desconegut</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">Algun símptoma o signe?</items>
        <items id="description">Hi ha antecedents de símptomes o signes rellevants per al cribratge?</items>
        <items id="comment">En una plantilla, l'element de dades normalment es renombrarà a la pregunta específica que es fa. El conjunt de valors proposat es pot adaptar per a ús local mitjançant l'opció de tipus de dades DV_TEXT o DV_BOOLEAN per coincidir amb cada cas d'ús específic.</items>
      </items>
      <items code="at0029">
        <items id="text">Inici</items>
        <items id="description">Moment del reconeixement inicial de qualsevol símptoma o signe rellevant per al propòsit del cribratge.</items>
        <items id="comment">L'element de dades 'Inici' s'ha modelat deliberadament de manera flexible per admetre la infinitat de maneres en què es pot utilitzar en qüestionaris per capturar l'aparició de símptomes o signes. La semàntica específica i prevista es pot aclarir més en una plantilla.&#xD;
&#xD;
Per exemple:&#xD;
Data/hora de la data en què va començar el símptoma. Interval de data/hora per a un període de temps, p. ex., entre 1940 i 1942. Text per a descripcions com ara 'Immediatament després de l'operació' o 'Fins fa una setmana', 'Fins fa dues setmanes', 'Fa tres setmanes'. Durada per a l'edat de l'individu en l'aparició. Interval de Durada per a l'edat aproximada de l'individu en el moment de l'aparició.</items>
      </items>
      <items code="at0031">
        <items id="text">Sí</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Desconegut</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Objectiu del cribratge</items>
        <items id="description">El context o el motiu del cribratge.</items>
        <items id="comment">Aquest element de dades té com a objectiu proporcionar un context de recopilació per als grups de preguntes/respostes quan es consultin posteriorment. No s'espera que aquest element de dades es mostri a l'individu, sinó que només s'emmagatzemi a les dades. Per exemple: "cribratge previ a l'ingrés" o el nom del qüestionari real.</items>
      </items>
      <items code="at0035">
        <items id="text">Comentari</items>
        <items id="description">Narrativa addicional sobre la pregunta específica del símptoma/signe, no recollida en altres camps.</items>
      </items>
      <items code="at0036">
        <items id="text">Descripció</items>
        <items id="description">Descripció narrativa sobre l'historial de qualsevol símptoma o signe rellevant per al propòsit del cribratge.</items>
      </items>
      <items code="at0037">
        <items id="text">Temps</items>
        <items id="description">Indicació del moment relacionat amb el símptoma o signe específic.</items>
        <items id="comment">L'element de dades "Temps" s'ha modelat deliberadament de manera flexible per admetre la infinitat de maneres en què es pot utilitzar en qüestionaris per capturar quan es va produir el símptoma o signe específic. La semàntica específica i prevista es pot aclarir més en una plantilla. Per exemple: la data i/o hora reals; l'hora d'inici i de finalització del símptoma o signe específic; l'interval de temps durant el qual es va produir el símptoma o signe específic; la durada del símptoma o signe específic; l'edat de l'individu en el moment en què es va produir el símptoma o signe específic; o el temps transcorregut des que es va produir. Una data parcial és vàlida, utilitzant el tipus de dades DV_DATE_TIME, per registrar només un any.</items>
      </items>
      <items code="at0039">
        <items id="text">Detalls addicionals</items>
        <items id="description">Detalls o preguntes estructurades sobre el cribratge de símptomes o signes.</items>
      </items>
      <items code="at0040">
        <items id="text">Dubtós</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">Dubtós</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Cuestionario de detección de síntomas/signos</items>
        <items id="description">Serie de preguntas y respuestas asociadas utilizadas para la detección de síntomas o signos.</items>
        <items id="comment">Las respuestas pueden ser auto-reportadas.</items>
      </items>
      <items code="at0001">
        <items id="text">Historial</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Cualquier evento</items>
        <items id="description">Evento predeterminado, no especificado, en un punto temporal o intervalo de tiempo, que puede definirse explícitamente en una plantilla o en tiempo de ejecución.</items>
      </items>
      <items code="at0003">
        <items id="text">Árbol</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Nombre del síntoma/signo</items>
        <items id="description">Identificación de un síntoma o signo específico, o de un grupo de síntomas o signos, por nombre.</items>
        <items id="comment">Se prefiere codificar el "Nombre del síntoma/signo" con una terminología, siempre que sea posible.</items>
      </items>
      <items code="at0005">
        <items id="text">¿Presencia?</items>
        <items id="description">¿Existe un historial de la presencia del síntoma o signo específico?</items>
        <items id="comment">En una plantilla, el elemento de datos generalmente se renombraría según la pregunta específica formulada. El conjunto de valores propuesto puede adaptarse para uso local utilizando los tipos de datos DV_TEXT o DV_BOOLEAN para cada caso de uso específico.</items>
      </items>
      <items code="at0007">
        <items id="text">Árbol de ítems</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0021">
        <items id="text">Extensión</items>
        <items id="description">Información adicional necesaria para ampliar el modelo con contenido local o para alinearse con otros modelos de referencia o formalismos.</items>
        <items id="comment">Por ejemplo: requisitos de información local; o metadatos adicionales para alinearse con FHIR.</items>
      </items>
      <items code="at0022">
        <items id="text">Síntoma/signo específico</items>
        <items id="description">Detalles sobre un síntoma o signo específico, o de un grupo de síntomas o signos, relevantes para la propósito del cribado.</items>
      </items>
      <items code="at0023">
        <items id="text">Sí</items>
        <items id="description" />
      </items>
      <items code="at0024">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0026">
        <items id="text">Detalles adicionales</items>
        <items id="description">Detalles estructurados o preguntas sobre el síntoma o signo específico.</items>
      </items>
      <items code="at0027">
        <items id="text">Desconocido</items>
        <items id="description" />
      </items>
      <items code="at0028">
        <items id="text">¿Algún síntoma o signo?</items>
        <items id="description">¿Existen antecedentes de algún síntoma o signo relevante para el propósito de la evaluación?</items>
        <items id="comment">En una plantilla, el elemento de datos normalmente se renombraría según la pregunta específica formulada. El conjunto de valores propuesto puede adaptarse para uso local mediante los tipos de datos DV_TEXT o DV_BOOLEAN para cada caso de uso específico.</items>
      </items>
      <items code="at0029">
        <items id="text">Inicio</items>
        <items id="description">Momento del reconocimiento inicial de cualquier síntoma o signo relevante para el propósito de detección.</items>
        <items id="comment">El elemento de datos "Inicio" se ha modelado deliberadamente de forma flexible para respaldar las múltiples maneras en que puede utilizarse en cuestionarios para registrar la aparición de síntomas o signos. La semántica específica y prevista puede aclararse con más detalle en una plantilla.&#xD;
&#xD;
Por ejemplo:&#xD;
Fecha/hora de inicio del síntoma. Intervalo de fecha/hora para un período de tiempo, por ejemplo, entre 1940 y 1942. Texto para descripciones como "Inmediatamente después de la operación" o "Hasta hace una semana", "Hasta hace dos semanas", "Hace tres semanas". Duración para la edad del individuo al inicio. Intervalo de duración para la edad aproximada del individuo al momento del inicio.</items>
      </items>
      <items code="at0031">
        <items id="text">Sí</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0033">
        <items id="text">Desconocido</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Objetivo del cribado</items>
        <items id="description">Contexto o motivo del cribado.</items>
        <items id="comment">Este dato está diseñado para proporcionar contexto de recopilación para los grupos de preguntas y respuestas cuando se consulten posteriormente. No se espera que este dato se exponga al individuo, sino que solo se almacene en los datos.&#xD;
Por ejemplo: "cribado previo al ingreso" o el nombre del cuestionario.</items>
      </items>
      <items code="at0035">
        <items id="text">Comentario</items>
        <items id="description">Descripción adicional sobre el síntoma o signo específico, no reflejada en otros campos.</items>
      </items>
      <items code="at0036">
        <items id="text">Descripción</items>
        <items id="description">Descripción sobre el historial de cualquier síntoma o signo relevante para la evaluación.</items>
      </items>
      <items code="at0037">
        <items id="text">Tiempo</items>
        <items id="description">Indicación del tiempo relacionado con el síntoma o signo específico.</items>
        <items id="comment">El elemento de datos "Tiempo" se ha modelado deliberadamente de forma flexible para facilitar su uso en cuestionarios, que permite registrar la fecha de aparición del síntoma o signo específico. La semántica específica y prevista se puede aclarar con más detalle en una plantilla. Por ejemplo: la fecha y/o hora real; la hora de inicio y fin del síntoma o signo específico; el intervalo de tiempo durante el cual se produjo el síntoma o signo específico; la duración del síntoma o signo específico; la edad de la persona en el momento de la aparición del síntoma o signo específico; o el tiempo transcurrido desde su aparición. Una fecha parcial es válida, utilizando el tipo de dato DV_DATE_TIME, para registrar solo un año.</items>
      </items>
      <items code="at0039">
        <items id="text">Detalles adicionales</items>
        <items id="description">Detalles estructurados o preguntas sobre la detección de síntomas o signos.</items>
      </items>
      <items code="at0040">
        <items id="text">Dudoso</items>
        <items id="description" />
      </items>
      <items code="at0041">
        <items id="text">Dudoso</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_bindings terminology="SNOMED-CT">
      <items code="at0023">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>373066001</code_string>
        </value>
      </items>
      <items code="at0024">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>373067005</code_string>
        </value>
      </items>
      <items code="at0031">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>373066001</code_string>
        </value>
      </items>
      <items code="at0032">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>373067005</code_string>
        </value>
      </items>
      <items code="at0033">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>261665006</code_string>
        </value>
      </items>
      <items code="at0027">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>261665006</code_string>
        </value>
      </items>
    </term_bindings>
  </ontology>
</archetype>
