<?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>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>Per Meinich, Helse Sør-Øst RHF, Norway</other_contributors>
    <other_contributors>Mikael Nyström, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil</other_contributors>
    <other_contributors>Erik Skjemstad, Helse Nord RHF, Norway</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>Martijn van Eenennaam, Nedap Healthcare, Netherlands</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: Procedure 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.4439</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">5860FF5470219DF112E9B113832703C7</other_details>
    <other_details id="build_uid">10c432a4-61ee-4ead-b5d7-2c33ea6ca307</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 https://www.snomed.org/snomed-ct/get-snomed or info@snomed.org.</other_details>
    <other_details id="revision">1.0.6</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Schaffung von Rahmenbedingungen für die Darstellung von Antworten auf vordefinierte Screening-Fragen über das klinische Management im Zusammenhang mit chirurgischen/operativen Prozeduren, die in der Vergangenheit durchgeführt wurden.</purpose>
      <keywords>Prozedur, Verfahren, Eingriff, Operation, Beurteilung, Untersuchung, Fragebogen, Screening</keywords>
      <use>Zur Schaffung von Rahmenbedingungen für die Darstellung von Antworten auf vordefinierte Screening-Fragen über das klinische Management im Zusammenhang mit chirurgischen/operativen Prozeduren, die in der Vergangenheit durchgeführt wurden.&#xD;
&#xD;
Häufige Anwendungsfälle umfassen, sind aber nicht beschränkt auf:&#xD;
- Gezielte Befragung zu bisherigen Eingriffen vor Aufnahme in ein Krankenhaus.&#xD;
- Systematische Befragung in jedem Beratungsgespräch, zum Beispiel:&#xD;
--- Hatten Sie jemals eine Appendektomie? Ja, Nein, Unbekannt.&#xD;
--- Hatten Sie in den letzten zwölf Monaten einen Hüft- oder Kniegelenkersatz? Ja, Nein, Unbekannt.&#xD;
&#xD;
Die Semantik dieses Archetyps ist mit Absicht etwas locker definiert und diesen Archetyp zu verwenden ist nur sinnvoll im Kontext eines spezifischen Templates. In einem Template würde jedes Datenelement in eine der spezifischen Fragen umbenannt werden. Wenn für bestimmte Anwendungsfälle Gruppen an Werten vorgesehen sind, können diese für den lokalen Gebrauch auf den jeweiligen Anwendungsfall mit den Datentypen DV_TEXT oder DV_BOOLEAN angepasst werden.&#xD;
&#xD;
Die EVENT-Struktur vom Referenzmodell kann verwendet werden, um weiter zu spezifizieren, ob die Fragen sich auf einen bestimmten Zeitpunkt oder eher eine Zeitspanne beziehen. Eine seperate Instanz dieses Archetyps wird verwendet, um zwischen einer Befragung zur Prozedur zu irgendeinem bestimmten Zeitpunkt in der Vergangenheit und Informationen zu Prozeduren, die in einer bestimmten Zeitspanne durchgeführt wurden - zum Beispiel den Unterschied zwischen "Haben Sie jemals eine Hüft- oder Knieoperation gehabt?" im Vergleich zu „Haben Sie in den letzten 12 Monaten eine Hüft- oder Knieoperation gehabt?&#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 die abgeschlossene Prozedur identifiziert, wird empfohlen, dass das klinische System die spezifischen Details über die Prozedur (z. B. die Dauer der Prozedur) unter Verwendung des Archetyps ACTION.procedure aufzeichnet und beibehält.</use>
      <misuse>Der Archetyp darf nicht verwendet werden, um Details über das Vorhandensein oder Nichtvorhandensein einer Prozedur außerhalb eines Screening-Kontexts darzustellen. Verwenden Sie für diese Zwecke ACTION.procedure oder EVALUATION.exclusion_specific.&#xD;
&#xD;
Nicht zur Darstellung von nicht-chirurgischem oder nicht-invasivem klinischen Managementaktivitäten verwenden. Verwenden Sie zu diesem Zweck OBSERVATION.management_screening.&#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>nb</code_string>
      </language>
      <purpose>For å lage et rammeverk for registrering av svar på forhåndsdefinerte spørsmål om kirurgiske/operative prosedyrer som er utført tidligere.</purpose>
      <keywords>prosedyre, operasjon, kirurgi, spørreskjema, kartlegging</keywords>
      <use>Brukes for å lage et rammeverk for registrering av svar på forhåndsdefinerte spørsmål om kirurgiske/operative prosedyrer som er utført tidligere.&#xD;
&#xD;
Vanlige bruksområder inkluderer, men er ikke begrenset til:&#xD;
- Spesifikke spørsmål før innleggelse ved sykehuset.&#xD;
- Systematiske spørsmål ved konsultasjoner, for eksempel:&#xD;
--- Har du gjennomgått en appendektomi? Ja, Nei, Ukjent.&#xD;
--- Har du fått gjennomført en hofte eller kneoperasjon de siste tolv månedene? Ja, Nei, Ukjent.&#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 noen sinne fått utført en hofte eller kneoperasjon?" sammenlignet med "Har du fått gjennomført en hofte- eller kneoperasjon i løpet av de siste 12 månedene?".&#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 kartleggingen identifiseres at en prosedyre er gjennomført, anbefales det at spesifikke detaljer om prosedyren (som for eksempel når og/eller hvor prosedyren ble gjort) registreres og lagres i pasientjournalen i arketypen Prosedyre (ACTION.procedure).</use>
      <misuse>Brukes ikke for å registrere detaljer om tilstedeværelse eller fravær av en prosedyre utenfor konteksten av kartleggingen. Bruk arketypen ACTION.procedure (Prosedyre) eller EVALUATION.exclusion_specific (Eksklusjonsutsagn - spesifikt) for dette formålet.&#xD;
&#xD;
Brukes ikke for å registrere detaljer om ikke kirugisk eller noninvasiv sykdomshåndtering. Bruk arketypen OBSERVATION.management_screening (Kartleggingsspørsmål om sykdomshåndtering) 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 clinical management related to surgical/operative procedures that have been carried out in the past.</purpose>
      <keywords>Procedure, surgery, operation, assessment, investigation, questionnaire, screening</keywords>
      <use>Use to create a framework for recording answers to pre-defined screening questions about clinical management related to surgical/operative procedures that have been carried out in the past.&#xD;
&#xD;
Common use cases include, but are not limited to:&#xD;
- Specific questioning about previous procedures before admission to a hospital.&#xD;
- Systematic questioning in any consultation, for example:&#xD;
--- Have you ever had an appendectomy? Yes, No, Unknown.&#xD;
--- Have you had a hip or knee replacement in the past twelve months? Yes, No, Unknown.&#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 procedure that has been performed at any time in the past and information about a procedure performed within a specified time interval - for example the difference between "Have you ever had any hip or knee surgery?" compared to "Have you had any hip or knee surgery in the last 12 months?&#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 process identifies a completed procedure, it is recommended that clinical system record and persist the specific details about the procedure (such as the duration of the procedure) using the ACTION.procedure archetype.</use>
      <misuse>Not to be used to record details about the presence or absence of a procedure, outside of a screening context. Use ACTION.procedure or EVALUATION.exclusion_specific for these purposes.&#xD;
&#xD;
Not to be used to record non-surgical or non-invasive clinical management. Use OBSERVATION.management_screening for this 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>© openEHR Foundation</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 to pre-defined screening questions about clinical management related to specific invasive interventions or surgical/operative procedures that have been carried out in the past. (en)</purpose>
      <keywords>*Procedure, surgery, operation, assessment, investigation, questionnaire, screening (en)</keywords>
      <use>*Use to create a framework for recording answers to pre-defined screening questions about clinical management related to specific invasive interventions or surgical/operative procedures that have been carried out in the past.&#xD;
&#xD;
Common use cases include, but are not limited to:&#xD;
- Specific questioning about previous procedures before admission to a hospital.&#xD;
- Systematic questioning in any consultation, for example:&#xD;
--- Have you ever had an appendectomy? Yes, No, Unknown.&#xD;
--- Have you had a hip or knee replacement in the past twelve months? Yes, No, Unknown.&#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 procedure that has been performed at any time in the past and information about a procedure performed within a specified time interval - for example the difference between "Have you ever had any hip or knee surgery?" compared to "Have you had any hip or knee surgery in the last 12 months?&#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 process identifies a completed procedure, it is recommended that clinical system record and persist the specific details about the procedure (such as the duration of the procedure) using the ACTION.procedure archetype. (en)</use>
      <misuse>*Not to be used to record details about the presence or absence of a procedure, outside of a screening context. Use ACTION.procedure or EVALUATION.exclusion_specific for these purposes.&#xD;
&#xD;
Not to be used to record non-surgical or non-invasive clinical management. Use OBSERVATION.management_screening for this 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 sélection prédéfinies sur la gestion clinique liée aux procédures chirurgicales/opératoires qui ont été effectuées dans le passé.</purpose>
      <keywords>Procédure, chirurgie, opération, évaluation, enquête, questionnaire, dépistage</keywords>
      <use>A utiliser pour créer un cadre permettant d'enregistrer les réponses à des questions prédéfinies sur la gestion clinique liée à des procédures chirurgicales/opératoires qui ont été effectuées dans le passé.&#xD;
&#xD;
Les cas d'utilisation les plus courants sont, entre autres, les suivants&#xD;
- des questions spécifiques sur les interventions antérieures avant l'admission à l'hôpital&#xD;
- Interrogation systématique lors d'une consultation, par exemple : --- Avez-vous déjà eu une appendicite ?&#xD;
--- Avez-vous déjà subi une appendicectomie ? Oui, Non, Inconnu.&#xD;
--- Avez-vous subi une arthroplastie de la hanche ou du genou au cours des douze derniers mois ? Oui, Non, Inconnu.&#xD;
&#xD;
La sémantique de cet archétype est intentionnellement 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 une procédure effectuée à tout moment dans le passé et des informations sur une procédure effectuée dans un intervalle de temps donné - par exemple la différence entre "Avez-vous déjà subi une opération de la hanche ou du genou ?" et "Avez-vous subi une opération de la hanche ou du genou au cours des 12 derniers mois ?&#xD;
&#xD;
La source des informations contenues dans une réponse à un questionnaire peut varier selon le contexte, mais elle 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 processus de dépistage identifie une procédure terminée, il est recommandé que le système clinique enregistre et conserve les détails spécifiques de la procédure (tels que la durée de la procédure) à l'aide de l'archétype ACTION.procedure.</use>
      <misuse>Ne pas utiliser pour enregistrer des détails sur la présence ou l'absence d'une procédure, en dehors d'un contexte de dépistage. Utiliser ACTION.procedure ou EVALUATION.exclusion_specific à cette fin.&#xD;
&#xD;
Ne doit pas être utilisé pour enregistrer une prise en charge clinique non chirurgicale ou non invasive. Utilisez OBSERVATION.management_screening à cette fin.&#xD;
&#xD;
Ne pas utiliser pour enregistrer les détails d'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>ca</code_string>
      </language>
      <purpose>Crear un marc per a l'enregistrament de respostes a preguntes predefinides de cribratge sobre la gestió clínica relacionada amb els procediments quirúrgics/operatius que s'han dut a terme en el passat.</purpose>
      <keywords>Procediment</keywords>
      <keywords>cirurgia</keywords>
      <keywords>operació</keywords>
      <keywords>avaluació</keywords>
      <keywords>investigació</keywords>
      <keywords>qüestionari</keywords>
      <keywords>cribratge</keywords>
      <use>Creació d'un marc per a l'enregistrament de respostes a preguntes predefinides de cribratge sobre la gestió clínica relacionada amb els procediments quirúrgics/operatius que s'han dut a terme en el passat.&#xD;
&#xD;
Els casos d'ús comuns inclouen, però no es limiten a:&#xD;
- Qüestionari específic sobre els procediments previs abans de l'ingrés a un hospital.&#xD;
- Qüestionari sistemàtic en qualsevol consulta, per exemple:&#xD;
--- Alguna vegada has tingut una apendectomia? Sí, no, desconegut.&#xD;
--- Has tingut un reemplaçament de maluc o genoll en els últims dotze mesos? Sí, no, desconegut.&#xD;
&#xD;
La semàntica d'aquest arquetip és intencionadament laxa, i la consulta d'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 reanomena segons la pregunta específica formulada. Quan s'han proposat conjunts de valors per a casos d'ús comuns, aquests es poden adaptar per a ús local utilitzant el DV_TEXT o els tipus de dades DV_BOOLEAN per a coincidir amb cada cas d'ús específic.&#xD;
&#xD;
L'estructura de l'EVENT a partir del model de referència es pot utilitzar per especificar si les preguntes es relacionen amb un punt en el temps o durant un període de temps. Utilitzeu una instància separada d'aquest arquetip per distingir entre un qüestionari que registra informació sobre un procediment que s'ha realitzat en qualsevol moment del passat i informació sobre un procediment realitzat en un interval de temps especificat - per exemple la diferència entre "Has tingut alguna cirurgia de maluc o genoll?" en comparació amb "Has tingut alguna cirurgia de maluc o genoll en els últims 12 mesos?".&#xD;
&#xD;
La font de la informació en una resposta de qüestionari pot variar en diferents contextos, però es pot identificar específicament utilitzant l'element 'Proveïdor d'informació' del Model de Referència.&#xD;
&#xD;
Aquest arquetip ha estat dissenyat per ser utilitzat com a eina de cribratge o per registrar dades simples en format qüestionari per al seu ús en situacions com un registre de malalties. Si el procés de cribratge identifica un procediment completat, es recomana que el sistema clínic registri i persisteixi els detalls específics sobre el procediment (com la durada del procediment) utilitzant l'arquetip ACTION.procedure.</use>
      <misuse>No s'ha d'utilitzar per registrar detalls sobre la presència o absència d'un procediment, fora d'un context de cribratge. Utilitzar ACTION.procedure o EVALUATION.exclusion_specific per a aquestes finalitats.&#xD;
&#xD;
No s'ha d'utilitzar per registrar una gestió clínica no quirúrgica o no invasiva. Utilitzar OBSERVATION.management_screening per a aquestes finalitats.&#xD;
&#xD;
No s'ha d'utilitzar per a enregistrar detalls sobre una llista de selecció senzilla on una pregunta es pot enregistrar com a «present» o «indeterminada». Utilitzeu OBSERVATION.selection_list per a aquesta finalitat</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 el manejo clínico relacionado con procedimientos quirúrgicos/operatorios que se han llevado a cabo en el pasado.</purpose>
      <keywords>Procedimiento</keywords>
      <keywords>cirugía</keywords>
      <keywords>operación</keywords>
      <keywords>evaluación</keywords>
      <keywords>investigación</keywords>
      <keywords>cuestionario</keywords>
      <keywords>cribado</keywords>
      <use>Se utiliza para crear un marco para registrar las respuestas a preguntas de cribado predefinidas sobre la gestión clínica relacionada con procedimientos quirúrgicos/operatorios realizados en el pasado.&#xD;
&#xD;
Los casos de uso comunes incluyen, entre otros:&#xD;
- Preguntas específicas sobre procedimientos previos al ingreso hospitalario.&#xD;
- Preguntas sistemáticas en cualquier consulta, por ejemplo:&#xD;
--- ¿Se ha sometido alguna vez a una apendicectomía? Sí, No, Desconocido.&#xD;
--- ¿Se ha sometido a un reemplazo de cadera o rodilla en los últimos doce meses? Sí, No, Desconocido.&#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 relacionan con un punto en Tiempo o durante un período de tiempo. Utilice una instancia separada de este arquetipo para distinguir entre un cuestionario que registra información sobre un procedimiento realizado en cualquier momento del pasado y la información sobre un procedimiento realizado dentro de un intervalo de tiempo específico; por ejemplo, la diferencia entre "¿Se ha sometido alguna vez a una cirugía de cadera o rodilla?" y "¿Se ha sometido a alguna cirugía de cadera o rodilla en los últimos 12 meses?".&#xD;
&#xD;
La fuente de información en una respuesta al 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 utilizarse 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 proceso de cribado identifica un procedimiento completado, se recomienda que el sistema clínico registre y conserve los detalles específicos del procedimiento (como su duración) utilizando el arquetipo ACTION.procedure.</use>
      <misuse>No debe utilizarse para registrar detalles sobre la presencia o ausencia de un procedimiento fuera del contexto de un cribado. Utilice ACTION.procedure o EVALUATION.exclusion_specific para estos fines.&#xD;
&#xD;
No debe utilizarse para registrar el manejo clínico no quirúrgico o no invasivo. Utilice OBSERVATION.management_screening 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">Nina Schewe, Natalia Strauch, Darin Leonhardt</author>
    <author id="organisation">Medizinische Hochschule Hannover, PLRI für medizinische Informatik/ Medizinische Hochschule</author>
    <author id="email">nina.schewe@plri.de, Strauch.Natalia@mh-hannover.de, leonhardt.darin@mh-hannover.de</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, 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-bergen.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>ca</code_string>
    </language>
    <author id="name">TRADCREA - Clara Calleja Vega</author>
    <author id="organisation">CatSalut. Servei Català de la Salut.</author>
    <author id="email">ccalleja@catsalut.cat</author>
  </translations>
  <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>7d2adbd4-0ab6-4def-af0a-00c722cc180e</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-OBSERVATION.procedure_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>at0038</code_list>
                            <code_list>at0042</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>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>0</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0041</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>at0039</code_list>
                                <code_list>at0043</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_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_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>
                          <children xsi:type="C_COMPLEX_OBJECT">
                            <rm_type_name>DV_INTERVAL&lt;DV_DATE_TIME&gt;</rm_type_name>
                            <occurrences>
                              <lower_included>true</lower_included>
                              <upper_included>true</upper_included>
                              <lower_unbounded>false</lower_unbounded>
                              <upper_unbounded>false</upper_unbounded>
                              <lower>1</lower>
                              <upper>1</upper>
                            </occurrences>
                            <node_id />
                          </children>
                        </attributes>
                      </children>
                      <children xsi:type="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>at0036</node_id>
                        <includes>
                          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.organisation\.v1/}</string_expression>
                          <expression xsi:type="EXPR_BINARY_OPERATOR">
                            <type>Boolean</type>
                            <operator>2007</operator>
                            <precedence_overridden>false</precedence_overridden>
                            <left_operand xsi:type="EXPR_LEAF">
                              <type>String</type>
                              <item xsi:type="xsd:string">archetype_id/value</item>
                              <reference_type>attribute</reference_type>
                            </left_operand>
                            <right_operand xsi:type="EXPR_LEAF">
                              <type>C_STRING</type>
                              <item xsi:type="C_STRING">
                                <pattern>openEHR-EHR-CLUSTER\.organisation\.v1</pattern>
                              </item>
                              <reference_type>constraint</reference_type>
                            </right_operand>
                          </expression>
                        </includes>
                      </children>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>ELEMENT</rm_type_name>
                        <occurrences>
                          <lower_included>true</lower_included>
                          <upper_included>true</upper_included>
                          <lower_unbounded>false</lower_unbounded>
                          <upper_unbounded>false</upper_unbounded>
                          <lower>0</lower>
                          <upper>1</upper>
                        </occurrences>
                        <node_id>at0025</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>at0040</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">Procedure screening questionnaire</items>
        <items id="description">Series of questions and associated answers used to screen for procedures that has been carried out in the past.</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">Procedure name</items>
        <items id="description">Name of a procedure or grouping of procedures.</items>
        <items id="comment">Coding of the 'Procedure name' with a terminology is preferred, where possible.</items>
      </items>
      <items code="at0005">
        <items id="text">Carried out?</items>
        <items id="description">Is there a history of the identified procedure being done or carried out?</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 procedure</items>
        <items id="description">Details about a specific procedure or grouping of procedures relevant 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="at0025">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the specific procedure question, not captured in other fields.</items>
      </items>
      <items code="at0028">
        <items id="text">Any previous procedures?</items>
        <items id="description">Is there a history of any past procedures 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="at0031">
        <items id="text">Yes</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">No</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. For example: pre-admission screening or the name of the actual questionnaire.</items>
      </items>
      <items code="at0036">
        <items id="text">Additional details</items>
        <items id="description">Structured details or questions about the specific procedure.</items>
        <items id="comment">For example: hospital where treated.</items>
      </items>
      <items code="at0037">
        <items id="text">Timing</items>
        <items id="description">Timing of the procedure.</items>
        <items id="comment">Indication of timing related to the investigation.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 an procedure was carried out. 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 the procedure ; the interval of time during which the procedure was carried out; the duration of the procedure; the age of the individual at the time of the procedure; 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="at0038">
        <items id="text">Unknown</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">Unknown</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">Additional details</items>
        <items id="description">Structured details or questions about screening for procedures.</items>
      </items>
      <items code="at0041">
        <items id="text">Description</items>
        <items id="description">Narrative description about the history of any past procedures relevant for the screening purpose.</items>
      </items>
      <items code="at0042">
        <items id="text">Unsure</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <items id="text">Unsure</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Kartleggingsspørsmål om prosedyrer</items>
        <items id="description">Spørsmål og tilhørende svar som brukes til å kartlegge prosedyrer som er utført.</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">Prosedyrenavn</items>
        <items id="description">Navnet på en prosedyre eller gruppe av prosedyrer.</items>
        <items id="comment">Koding av "Prosedyrenavn" med en terminologi foretrekkes der det er mulig.</items>
      </items>
      <items code="at0005">
        <items id="text">Utført?</items>
        <items id="description">Har den identifiserte prosedyren vært utført?</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">Spesifikk prosedyre</items>
        <items id="description">Detaljer om en spesifikk prosedyre eller gruppe av prosedyrer 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="at0025">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om det spesifikke prosedyrespørsmålet som ikke er omfattet av andre felt.</items>
      </items>
      <items code="at0028">
        <items id="text">Noen tidligere prosedyrer?</items>
        <items id="description">Finnes det noen tidligere gjennomførte prosedyrer som 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="at0031">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Nei</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, dersom 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. For eksempel: "Preoperativ screening" eller navnet på det faktiske spørreskjemaet.</items>
      </items>
      <items code="at0036">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Strukturerte detaljer eller spørsmål om den spesifikke prosedyren.</items>
        <items id="comment">For eksempel: Behandlende sykehus.</items>
      </items>
      <items code="at0037">
        <items id="text">Tidsangivelse</items>
        <items id="description">Tidsangivelse for prosedyren.</items>
        <items id="comment">Dataelementet "Tidsangivelse" er med hensikt løst modellert for å støtte ulike måter å angi tidsangivelser for prosedyrer i et spørreskjema. Den konkrete semantikken defineres i templatet. For eksempel: Prosedyrens faktiske dato og/eller klokkeslett, start- og slutttid for prosedyren, et tidsintervall for når prosedyren ble gjort, varigheten av prosedyren, individets alder på tidspunktet for prosedyren, eller hvor lenge det siden den ble gjort. Kan være en deldato, for eksempel bare år, ved å bruke datatypen DV_DATE_TIME.</items>
      </items>
      <items code="at0038">
        <items id="text">Ukjent</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">Ukjent</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Strukturerte detaljer eller spørsmål om kartleggingen av prosedyrer.</items>
      </items>
      <items code="at0041">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse om prosedyrer som er tidligere utført og som er innenfor kartleggingsformålet.</items>
      </items>
      <items code="at0042">
        <items id="text">Usikker</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <items id="text">Usikker</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Screening-Fragebogen zur Prozeduren</items>
        <items id="description">Eine Reihe von Fragen und zugehörigen Antworten, die zum Screening auf Prozeduren, die in der Vergangenheit durchgeführt wurden, 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 der Prozedur</items>
        <items id="description">Name einer Prozedur oder einer Gruppe von Prozeduren.</items>
        <items id="comment">Die Codierung des „Name der Prozedur“ mit einer Terminologie wird nach Möglichkeit bevorzugt.</items>
      </items>
      <items code="at0005">
        <items id="text">Durchgeführt?</items>
        <items id="description">Gibt es eine Historie, in der das identifizierte Verfahren durchgeführt oder ausgeführt wurde?</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">Spezifische Prozedur</items>
        <items id="description">Details zu einer bestimmten Prozedur oder zu einer bestimmten Gruppe von Prozeduren, 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="at0025">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Beschreibung über die spezifische Frage zur Prozedur, die nicht in anderen Bereichen erfasst wird.</items>
      </items>
      <items code="at0028">
        <items id="text">Irgendwelche frühere Prozeduren?</items>
        <items id="description">Gibt es eine Vorgeschichte von früheren Prozeduren, die für den Screening-Zweck relevant sind?</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="at0031">
        <items id="text">Ja</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Nein</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. Zum Beispiel: "Screening vor der Aufnahme" oder der Name des eigentlichen Fragebogens.</items>
      </items>
      <items code="at0036">
        <items id="text">Zusätzliche Angaben</items>
        <items id="description">Strukturierte Angaben oder Fragen zur konkreten Prozedur.</items>
        <items id="comment">Zum Beispiel: Krankenhaus, wo behandelt wurde.</items>
      </items>
      <items code="at0037">
        <items id="text">Zeitangaben</items>
        <items id="description">Zeitpunkt der Prozedur.</items>
        <items id="comment">Angabe des Zeitplans im Zusammenhang mit der Untersuchung. Kommentar: Das Datenelement „Zeitpunkt“ wurde bewusst locker modelliert, um die unzähligen Möglichkeiten zu unterstützen, mit denen es in Fragebögen zur Erfassung des Zeitpunkts der Durchführung eines Verfahrens verwendet werden kann. Die spezifische und beabsichtigte Semantik kann in einem Template weiter geklärt werden. Zum Beispiel: das tatsächliche Datum und/oder die tatsächliche Uhrzeit; die Start- und Endzeit des Verfahrens; das Zeitintervall, in dem das Verfahren durchgeführt wurde; die Dauer des Verfahrens; das Alter der Person zum Zeitpunkt des Verfahrens; oder die Zeitdauer seit dem Verfahren. Ein Teildatum ist unter Verwendung des Datentyps DV_DATE_TIME gültig, um nur ein Jahr zu erfassen.</items>
      </items>
      <items code="at0038">
        <items id="text">Unbekannt</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">Unbekannt</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">Zusätzliche Angaben</items>
        <items id="description">Strukturierte Angaben oder Fragen zum Screening zur Prozeduren.</items>
      </items>
      <items code="at0041">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung über die Geschichte von früheren Prozeduren, die für das Screening relevant sind.</items>
      </items>
      <items code="at0042">
        <items id="text">Unsicher</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <items id="text">Unsicher</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="it">
      <items code="at0000">
        <items id="text">Questionario di screening della procedura</items>
        <items id="description">*Series of questions and associated answers used to screen for procedures that has been carried out in the past. (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">Nome della procedura</items>
        <items id="description">*Name of a procedure or grouping of procedures. (en)</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0005">
        <items id="text">*Carried out? (en)</items>
        <items id="description">*Is there a history of the identified procedure being done or carried out? (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">Procedura specifica</items>
        <items id="description">*Details about a specific procedure or grouping of procedures relevant 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="at0025">
        <items id="text">Commento</items>
        <items id="description">*Additional narrative about the specified procedure, not captured in other fields. (en)</items>
      </items>
      <items code="at0028">
        <items id="text">*Any previous procedures? (en)</items>
        <items id="description">*Is there a history of any past procedures relevant 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="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="at0034">
        <items id="text">Scopo dello screening</items>
        <items id="description">*The context or reason for screening. (en)</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. For example: pre-admission screening or the name of the actual questionnaire. (en)</items>
      </items>
      <items code="at0036">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Structured details or questions about the specific procedure. (en)</items>
        <items id="comment">*For example: The result of a performed laboratory analyte test.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Timing (en)</items>
        <items id="description">*Timing of the procedure. (en)</items>
        <items id="comment">*Indication of timing related to the investigation.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 an procedure was carried out. 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 the procedure ; the interval of time during which the procedure was carried out; the duration of the procedure; the age of the individual at the time of the procedure; 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="at0038">
        <items id="text">*Unknown (en)</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">*Unknown (en)</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Structured details or questions about screening for procedures. (en)</items>
      </items>
      <items code="at0041">
        <items id="text">*Description (en)</items>
        <items id="description">*Narrative description about the history of any past procedures relevant for the screening purpose. (en)</items>
      </items>
      <items code="at0042">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="fr">
      <items code="at0000">
        <items id="text">Questionnaire d'évaluation de la procédure</items>
        <items id="description">Série de questions et de réponses associées utilisées pour vérifier si des procédures ont été effectuées dans le passé.</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">Nom de la procédure</items>
        <items id="description">Nom d'une procédure ou d'un groupe de procédures.</items>
        <items id="comment">Dans la mesure du possible, il est préférable de coder le "nom de la procédure" à l'aide d'une terminologie.</items>
      </items>
      <items code="at0005">
        <items id="text">*Carried out? (en)</items>
        <items id="description">*Is there a history of the identified procedure being done or carried out? (en)</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">Procédure spécifique</items>
        <items id="description">Détails d'une procédure spécifique ou d'un groupe de procédures en rapport avec l'objectif de la sélection.</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="at0025">
        <items id="text">Commentaire</items>
        <items id="description">Description supplémentaire de la question de procédure spécifique, qui n'est pas saisie dans d'autres champs.</items>
      </items>
      <items code="at0028">
        <items id="text">Y a-t-il eu des procédures antérieures ?</items>
        <items id="description">Existe-t-il des antécédents de procédures antérieures en rapport avec l'objectif du 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="at0031">
        <items id="text">Oui</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">Non</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. Par exemple : la sélection préalable à l'admission ou le nom du questionnaire proprement dit.</items>
      </items>
      <items code="at0036">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails structurés ou questions sur la procédure spécifique.</items>
        <items id="comment">Par exemple : hôpital où le patient a été traité.</items>
      </items>
      <items code="at0037">
        <items id="text">Timing</items>
        <items id="description">Moment de la procédure.</items>
        <items id="comment">Indication du moment de l'enquête Commentaire : L'élément de données "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 la date à laquelle une procédure a été effectuée. 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 de la procédure ; l'intervalle de temps pendant lequel la procédure a été effectuée ; la durée de la procédure ; l'âge de l'individu au moment de la procédure ; ou la durée écoulée depuis qu'elle a eu lieu. 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="at0038">
        <items id="text">Inconnu</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">Inconnu</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails ou questions structurées sur le dépistage des procédures.</items>
      </items>
      <items code="at0041">
        <items id="text">Description</items>
        <items id="description">Description narrative des antécédents de toute procédure antérieure pertinente pour l'objectif du dépistage.</items>
      </items>
      <items code="at0042">
        <items id="text">*Unsure (en)</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <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 cribratge de procediments</items>
        <items id="description">Sèries de preguntes i respostes associades utilitzades per a analitzar els procediments que s'han dut a terme en el passat.</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">Per defecte, un punt no especificat en l'esdeveniment de temps o interval 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 procediment</items>
        <items id="description">Nom d'un procediment o agrupació de procediments.</items>
        <items id="comment">Es prefereix la codificació del 'nom del procés' amb una terminologia, quan sigui possible.</items>
      </items>
      <items code="at0005">
        <items id="text">Realitzat?</items>
        <items id="description">S'està fent o duent a terme un historial del procediment identificat?</items>
        <items id="comment">En una plantilla, l'element de dades normalment es reanomenaria segons la pregunta específica formulada. El conjunt de valors proposat es pot adaptar per a l'ús local utilitzant el DV_TEXT o l'elecció dels tipus de dades DV_BOOLEAN per 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-se amb altres models de referència o formalismes.</items>
        <items id="comment">Per exemple: requisits d'informació local; o metadades addicionals per alinear-se amb FHIR.</items>
      </items>
      <items code="at0022">
        <items id="text">Procediment específic</items>
        <items id="description">Detalls sobre un procediment específic o agrupació de procediments rellevants per a la finalitat 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="at0025">
        <items id="text">Comentari</items>
        <items id="description">Narrativa addicional sobre la qüestió del procediment específic, no capturada en altres camps.</items>
      </items>
      <items code="at0028">
        <items id="text">Hi ha algun procediment previ?</items>
        <items id="description">Hi ha algun historial de procediments anteriors rellevants per a l'objectiu de la detecció?</items>
        <items id="comment">En una plantilla, l'element de dades normalment es canviaria el nom a la pregunta específica formulada. El conjunt de valors proposat es pot adaptar per a l'ús local utilitzant el DV_TEXT o l'elecció dels tipus de dades DV_BOOLEAN per a cada cas d'ús específic.</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="at0034">
        <items id="text">Motiu del cribratge</items>
        <items id="description">El context o motiu del cribratge.</items>
        <items id="comment">Aquest element de dades està destinat a proporcionar context de recollida per als grups de preguntes/respostes quan es consulti en una data posterior. No s'espera que aquest element de dades estigui exposat a l'individu, sinó només emmagatzemat en dades. Per exemple: el cribratge previ a l'admissió o el nom del qüestionari real.</items>
      </items>
      <items code="at0036">
        <items id="text">Dades addicionals</items>
        <items id="description">Detalls estructurats o preguntes sobre el procediment concret.</items>
        <items id="comment">Per exemple: l'hospital on es tracta.</items>
      </items>
      <items code="at0037">
        <items id="text">Temps</items>
        <items id="description">Temps del procediment.</items>
        <items id="comment">Indicació del temps relacionat amb la investigació.Comentari: L'element de dades "Temps" s'ha modelat laxament deliberadament per donar suport a la infinitat de maneres que es poden utilitzar en qüestionaris per capturar quan es va dur a terme un procediment. La semàntica específica i pretesa es pot aclarir en una plantilla. Per exemple: la data i/o hora reals; l'hora d'inici i finalització del procediment; l'interval de temps durant el qual es va dur a terme el procediment; la durada del procediment; l'edat de l'individu en el moment del procediment; o la durada del temps 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="at0038">
        <items id="text">Desconegut</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">Desconegut</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">Dades addicionals</items>
        <items id="description">Detalls estructurats o preguntes sobre el cribratge per a procediments.</items>
      </items>
      <items code="at0041">
        <items id="text">Descripció</items>
        <items id="description">Descripció narrativa sobre la història de qualsevol procediment anterior rellevant per a la finalitat del cribratge.</items>
      </items>
      <items code="at0042">
        <items id="text">No n'està segur</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <items id="text">No n'està segur</items>
        <items id="description" />
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Cuestionario de cribado de procedimientos</items>
        <items id="description">Serie de preguntas y respuestas asociadas que se utilizan para filtrar procedimientos realizados en el pasado.</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, 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 procedimiento</items>
        <items id="description">Nombre de un procedimiento o grupo de procedimientos.</items>
        <items id="comment">Se prefiere codificar el "Nombre del procedimiento" con una terminología, siempre que sea posible.</items>
      </items>
      <items code="at0005">
        <items id="text">¿Realizado?</items>
        <items id="description">¿Existe un historial de la ejecución o ejecución del procedimiento identificado?</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 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">Procedimiento específico</items>
        <items id="description">Detalles sobre un procedimiento específico o un grupo de procedimientos relevantes para el propósito de la filtración.</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="at0025">
        <items id="text">Comentario</items>
        <items id="description">Narrativa adicional sobre la cuestión del procedimiento específico, no capturada en otros campos.</items>
      </items>
      <items code="at0028">
        <items id="text">¿Algún procedimiento previo?</items>
        <items id="description">¿Existen antecedentes de algún procedimiento previo que sea 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="at0031">
        <items id="text">Sí</items>
        <items id="description" />
      </items>
      <items code="at0032">
        <items id="text">No</items>
        <items id="description" />
      </items>
      <items code="at0034">
        <items id="text">Objetivo del cribado</items>
        <items id="description">El contexto o el motivo de la evaluación.</items>
        <items id="comment">Este elemento de datos proporciona contexto de recopilación para los grupos de preguntas y respuestas cuando se consulten posteriormente. No se espera que este elemento de datos se exponga a la persona, sino que solo se almacene en los datos. Por ejemplo: evaluación previa al ingreso o el nombre del cuestionario.</items>
      </items>
      <items code="at0036">
        <items id="text">Detalles adicionales</items>
        <items id="description">Detalles o preguntas estructuradas sobre el procedimiento específico.</items>
        <items id="comment">Por ejemplo: hospital donde se realizó el tratamiento.</items>
      </items>
      <items code="at0037">
        <items id="text">Fecha de inicio</items>
        <items id="description">Momento del procedimiento.</items>
        <items id="comment">Indicación del momento relacionado con la investigación. Comentario: El elemento de datos "Tiempo" se ha modelado de forma flexible para facilitar su uso en cuestionarios para registrar cuándo se realizó un procedimiento. 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 finalización del procedimiento; el intervalo de tiempo durante el cual se realizó el procedimiento; la duración del procedimiento; la edad de la persona en el momento del procedimiento; o el tiempo transcurrido desde que se realizó. Una fecha parcial es válida, utilizando el tipo de dato DV_DATE_TIME, para registrar solo un año.</items>
      </items>
      <items code="at0038">
        <items id="text">Desconocido</items>
        <items id="description" />
      </items>
      <items code="at0039">
        <items id="text">Desconocido</items>
        <items id="description" />
      </items>
      <items code="at0040">
        <items id="text">Detalles adicionales</items>
        <items id="description">Detalles estructurados o preguntas sobre la selección de procedimientos.</items>
      </items>
      <items code="at0041">
        <items id="text">Descripción</items>
        <items id="description">Descripción narrativa sobre el historial de cualquier procedimiento pasado relevante para el propósito de la evaluación.</items>
      </items>
      <items code="at0042">
        <items id="text">Dudoso</items>
        <items id="description" />
      </items>
      <items code="at0043">
        <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="at0038">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>261665006</code_string>
        </value>
      </items>
      <items code="at0039">
        <value>
          <terminology_id>
            <value>SNOMED-CT</value>
          </terminology_id>
          <code_string>261665006</code_string>
        </value>
      </items>
    </term_bindings>
  </ontology>
</archetype>
