<?xml version="1.0" encoding="UTF-8"?>
<archetype xmlns="http://schemas.openehr.org/v1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <original_language>
    <terminology_id>
      <value>ISO_639-1</value>
    </terminology_id>
    <code_string>en</code_string>
  </original_language>
  <is_controlled>false</is_controlled>
  <description>
    <original_author id="date">2007-03-12</original_author>
    <original_author id="name">Heather Leslie</original_author>
    <original_author id="organisation">Ocean Informatics, Australia</original_author>
    <original_author id="email">heather.leslie@oceaninformatics.com</original_author>
    <other_contributors>Morten Aas, Diakonhjemmet Sykehus, Norway</other_contributors>
    <other_contributors>Tomas Alme, DIPS, Norway</other_contributors>
    <other_contributors>Anne Pauline Anderssen, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo universitetssykehus HF, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Koray Atalag, University of Auckland, New Zealand</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Maria Beate Nupen, Oslo Universitetssykehus, Norway</other_contributors>
    <other_contributors>Lars Bitsch-Larsen, Haukeland University Hospital, Bergen, Norway</other_contributors>
    <other_contributors>Fredrik Borchsenius, Oslo universitetssykehus, Norway</other_contributors>
    <other_contributors>Diego Bosca, VeraTech for Health, Spain</other_contributors>
    <other_contributors>Hanne Marte Bårholm, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Rong Chen, Cambio Healthcare Systems, Sweden</other_contributors>
    <other_contributors>Stephen Chu, NEHTA, Australia (Editor)</other_contributors>
    <other_contributors>Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway</other_contributors>
    <other_contributors>Kari Beate Engseth, Finnmarkssykehuset HF + Klinikk Kirkenes, Norway</other_contributors>
    <other_contributors>David Evans, Queensland Health, Australia</other_contributors>
    <other_contributors>Shahla Foozonkhah, Iran ministry of health and education, Iran</other_contributors>
    <other_contributors>Einar Fosse, UNN HF, Norwegian Centre for Integrated Care and Telemedicine, Norway</other_contributors>
    <other_contributors>Sebastian Garde, Ocean Informatics, Germany</other_contributors>
    <other_contributors>Jacquie Garton-Smith, Royal Perth Hospital and DoHWA, Australia</other_contributors>
    <other_contributors>Bente Gjelsvik, Helse Bergen, Norway</other_contributors>
    <other_contributors>Andrew Goodchild, NEHTA, Australia</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Mikkel Johan Gaup Grønmo, Helse Nord IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Megan Hawkins, Mater Health Services, Australia</other_contributors>
    <other_contributors>Sam Heard, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Kristian Heldal, Telemark Hospital Trust, Norway</other_contributors>
    <other_contributors>Andreas Hering, Helse Bergen HF, Haukeland universitetssjukehus, Norway</other_contributors>
    <other_contributors>Anca Heyd, DIPS ASA, Norway</other_contributors>
    <other_contributors>Hilde Hollås, DIPS ASA, Norway</other_contributors>
    <other_contributors>Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway</other_contributors>
    <other_contributors>Mary Kelaher, NEHTA, Australia</other_contributors>
    <other_contributors>Shinji Kobayashi, Kyoto University, Japan</other_contributors>
    <other_contributors>Kanika Kuwelker, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Liv Laugen, Oslo universitetssykehus, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Sabine Leh, Helse Bergen, Norway</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia</other_contributors>
    <other_contributors>Hugh Leslie, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Hallvard Lærum, Direktoratet for e-helse, Norway</other_contributors>
    <other_contributors>Mike Martyn, The Hobart Anaesthetic Group, Australia</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)</other_contributors>
    <other_contributors>Lars Ivar Mehlum, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Chris Mitchell, RACGP, Australia</other_contributors>
    <other_contributors>Stewart Morrison, NEHTA, Australia</other_contributors>
    <other_contributors>Maria Beate Nupen-Stieng, Oslo Universitetssykehus, Norway</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Michael Osborne, Mater Health Services, Australia</other_contributors>
    <other_contributors>Chris Pearce, Melbourne East GP Network, Australia</other_contributors>
    <other_contributors>Rune Pedersen, Universitetssykehuset i Nord Norge, Norway</other_contributors>
    <other_contributors>Norwegian Review Summary, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil</other_contributors>
    <other_contributors>Peter Scott, Australia</other_contributors>
    <other_contributors>Elizabeth Stanick, Hobart Anaesthetic Group, Australia</other_contributors>
    <other_contributors>Line Sørensen, Helse Bergen, Norway</other_contributors>
    <other_contributors>John Taylor, NEHTA, Australia</other_contributors>
    <other_contributors>Micaela Thierley, Helse Vest IKT, Norway</other_contributors>
    <other_contributors>Rowan Thomas, St. Vincent's Hospital Melbourne, Australia</other_contributors>
    <other_contributors>Line Thomassen, Helse Bergen, Norway</other_contributors>
    <other_contributors>Richard Townley-O'Neill, NEHTA, Australia</other_contributors>
    <other_contributors>John Tore Valand, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Ørjan Vermeer, Haukeland Universitetssjukehus, Kvinneklinikken, Norway</other_contributors>
    <other_contributors>Ivar Yrke, DIPS AS, 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="current_contact">Heather Leslie, Atomica Informatics, heather.leslie@atomicainformatics.com</other_details>
    <other_details id="original_namespace">org.openehr</other_details>
    <other_details id="original_publisher">openEHR Foundation</other_details>
    <other_details id="custodian_namespace">org.openehr</other_details>
    <other_details id="MD5-CAM-1.0.1">C6FB6DB1E0BC90E3BC8A0255BEAF7328</other_details>
    <other_details id="build_uid">ba0af11e-94e9-4fa2-a2fb-febb25648d62</other_details>
    <other_details id="revision">1.5.0</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Erfassung von Informationen über die erforderlichen Aktivitäten zum Ausführen einer Prozedur. Dazu zählen die Planung, Terminierung, Durchführung, Unterbrechung, Stornierung, Dokumentation und Beendigung.</purpose>
      <keywords>Prozedur</keywords>
      <keywords>Vorgehen</keywords>
      <keywords>Verfahren</keywords>
      <keywords>Intervention</keywords>
      <keywords>Eingriff</keywords>
      <keywords>chirurgisch</keywords>
      <keywords>medizinisch</keywords>
      <keywords>klinisch</keywords>
      <keywords>therapeutisch</keywords>
      <keywords>Diagnostik</keywords>
      <keywords>diagnostisch</keywords>
      <keywords>heilen</keywords>
      <keywords>Behandlung</keywords>
      <keywords>Bewertung</keywords>
      <keywords>Untersuchung</keywords>
      <keywords>Früherkennung</keywords>
      <keywords>Screening</keywords>
      <keywords>palliativ</keywords>
      <keywords>Therapie</keywords>
      <keywords>Operation</keywords>
      <use>Verwenden Sie diesen Archetypen zur Erfassung von Informationen über die erforderlichen Aktivitäten zum Ausführen einer Prozedur, einschließlich Planung, Terminierung, Durchführung, Unterbrechung, Stornierung, Dokumentation und Beendigung. Dies geschieht durch die Darstellung von Daten zu bestimmten Aktivitäten durch die "Pathway"-Verlaufsschritte.&#xD;
&#xD;
Der Anwendungsbereich dieses Archetyps umfasst Aktivitäten für eine breite Palette von klinischen Prozeduren, die für evaluative, ermittelnde, vorsorgliche, diagnostische, kurative, therapeutische oder palliative Zwecke durchgeführt werden. Die Beispiele reichen von relativ einfachen Aktivitäten wie dem Legen einer intravenösen Kanüle bis hin zu komplexen chirurgischen Eingriffen.&#xD;
&#xD;
Zusätzliche strukturierte und detaillierte Informationen über die Prozedur können bei Bedarf mit Hilfe von zweckmäßigen Archetypen erfasst werden, die in den Slot "Details zur Prozedur" eingefügt werden.&#xD;
&#xD;
Zeitpläne, die sich auf eine Prozedur beziehen, können auf zwei Arten verwaltet werden:&#xD;
- Unter Verwendung des Referenzmodells - die Zeit für die Ausführung eines beliebigen "Pathway"-Verlaufsschrittes verwendet das Attribut ACTION Zeit für jeden Schritt.&#xD;
- Archetypische Datenelemente:&#xD;
--- das Datenelement "Geplantes Datum/Uhrzeit" soll die genaue Zeit erfassen, zu der die Prozedur geplant ist. Hinweis: Das entsprechende Attribut ACTION Zeit für den geplanten "Pathway"-Verlaufsschritt erfasst die Zeit, zu der die Prozedur in einem System geplant wurde, nicht das vorgesehene Datum/Uhrzeit, zu der die Prozedur ausgeführt werden soll; und&#xD;
--- das "Enddatum/-uhrzeit" soll die genaue Zeit erfassen, zu der die Prozedur beendet wurde. Damit können die komplexen Vorgänge mit mehreren Komponenten dokumentiert werden. Hinweis: Das entsprechende Attribut ACTION Zeit in dem Element "Prozedur durchgeführt", dokumentiert den Beginn der einzelnen durchgeführten Komponenten. Das Datenelement "Enddatum/-uhrzeit" erfasst das Datum/die Uhrzeit der letzten aktiven Komponente der Prozedur. Dadurch kann die volle Dauer der aktiven Prozedur berechnet werden.&#xD;
&#xD;
Im Rahmen eines Operationsberichts wird dieser Archetyp nur verwendet, um zu erfassen, was während der Operation durchgeführt wurde. Eigenständige Archetypen werden verwendet, um die anderen erforderlichen Komponenten des Operationsberichts zu erfassen, einschließlich der Entnahme von Gewebeproben, der Verwendung von Bildkontrolle, der OP-Befunde, postoperativer Anweisungen und Plänen für die Nachsorge.&#xD;
&#xD;
Im Rahmen einer Problemliste oder Zusammenfassung kann dieser Archetyp verwendet werden, um durchgeführte Prozeduren darzustellen. Der Archetyp EVALUATION.Problem/Diagnose wird verwendet, um die Probleme und Diagnosen des Patienten darzustellen.&#xD;
&#xD;
In der Praxis werden viele Prozeduren (z.B. in der ambulanten Versorgung) einmalig durchgeführt und nicht im Voraus angeordnet. Angaben zur Prozedur werden im Datenelement "Prozedur beendet" hinzugefügt. In einigen Fällen wird eine wiederkehrende Prozedur angeordnet. In diesen Fällen werden jeweils Daten mit dem Element "Prozedur durchgeführt" erfasst, so dass die Instruktion im aktiven Zustand verbleibt. Wenn das letzte Ereignis erfasst wird, wird die Aktion "Prozedur beendet" dokumentiert. Dies zeigt an, dass sich diese Prozedur nun im abgeschlossenen Zustand befindet.&#xD;
&#xD;
In anderen Fällen, wie z.B. in der Sekundärversorgung, kann es eine formelle Anordnung für eine Prozedur mit einem entsprechenden INSTRUCTION-Archetyp geben. Dieser ACTION-Archetyp kann dann verwendet werden, um den Workflow aufzuzeichnen, wann und wie der Auftrag ausgeführt wurde.&#xD;
&#xD;
Die Erfassung von Informationen mit diesem ACTION-Archetyp zeigt an, dass tatsächlich eine Art von Aktivität stattgefunden hat; dies ist in der Regel die Prozedur selbst, kann aber auch ein fehlgeschlagener Versuch oder eine andere Aktivität, wie das Verschieben der Prozedur, sein. Wenn es eine formale Anordnung für die Prozedur gibt, wird der Status dieser Anordnung durch das "Pathway" Element, für das Daten erfasst werden, dargestellt. Mit diesem Archetyp kann beispielsweise der Fortschritt einer gastroskopischen Anordnung durch separate Einträge in den "Pathway" Elementen erfasst werden:&#xD;
- Erfassung des geplante Startdatum/-zeit für die Gastroskopie (Prozedur geplant (zeitlich)); und&#xD;
- Dokumentation, dass das Gastroskopieverfahren abgeschlossen ist, einschließlich zusätzlicher Angaben zur Prozedur (Prozedur beendet).&#xD;
&#xD;
Bitte beachten Sie, dass es im openEHR-Referenzmodell ein Attribut "Zeit" gibt, das dazu dient, das Datum und die Uhrzeit zu erfassen, zu der jeder Verlaufsschritt der Aktion ausgeführt wurde. Dies ist das Attribut, mit dem der Beginn der Prozedur (mit dem Schritt "Prozedur durchgeführt") oder die Zeit, zu der die Prozedur abgebrochen wurde (mit dem Schritt "Prozedur abgebrochen"), erfasst wird.</use>
      <misuse>Nicht zur Erfassung von Angaben zur Anästhesie - verwenden Sie dazu einen separaten ACTION-Archetyp.&#xD;
&#xD;
Nicht zur Erfassung von Angaben über bildgebende Untersuchungen - verwenden Sie dazu den Archetypen ACTION.imaging_exam.&#xD;
&#xD;
Nicht zur Erfassung von Angaben über Laboruntersuchungen - verwenden Sie dazu den Archetypen ACTION.laboratory_test.&#xD;
&#xD;
Nicht zur Erfassung von Angaben über erbrachte Ausbildungen/Schulungen - verwenden Sie dazu den Archetypen ACTION.health_education.&#xD;
&#xD;
Nicht zur Erfassung von Angaben über administrative Aktivitäten - verwenden Sie zu diesem Zweck spezifische ADMIN-Archetypen.&#xD;
&#xD;
Nicht zu verwenden, um Angaben über zusammenhängende Aktivitäten zu erfassen. Beispiele für zusammenhängende Aktivitäten sind: der Einsatz von Gefrierschnitten, die während einer Operation durchgeführt werden; Medikamente, die im Rahmen der Prozedur verabreicht werden oder der Einsatz von Bildkontrolle während der Prozedur. Verwenden Sie zu diesem Zweck eigenständige und spezifische ACTION-Archetypen innerhalb des Templates.&#xD;
&#xD;
Nicht zur Erfassung eines vollständigen Berichts über eine OP- oder eine Prozedur - verwenden Sie ein Template, in der dieser Archetyp nur eine Komponente des Gesamtberichts darstellt.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-pt</code_string>
      </language>
      <purpose>Registar informações sobre as atividades necessárias para realizar um procedimento, incluindo planeamento, programação, desempenho, suspensão, cancelamento, documentação e conclusão.</purpose>
      <keywords>procedimento(pt)</keywords>
      <keywords>intervenção(pt)</keywords>
      <keywords>cirúrgico(pt)</keywords>
      <keywords>médico(pt)</keywords>
      <keywords>clínico(pt)</keywords>
      <keywords>terapêutico(pt)</keywords>
      <keywords>diagnóstico(pt)</keywords>
      <keywords>cura(pt)</keywords>
      <keywords>tratamento(pt)</keywords>
      <keywords>avaliação(pt)</keywords>
      <keywords>investigação(pt)</keywords>
      <keywords>rastreio(pt)</keywords>
      <keywords>paliativo(pt)</keywords>
      <keywords>terapia(pt)</keywords>
      <use>Use para registar informações sobre as atividades necessárias para realizar um procedimento, incluindo o planeamento, programação, desempenho, suspensão, cancelamento, documentação e conclusão. Isso é feito pelo registo de dados contra atividades específicas, conforme definido pelas etapas de fluxo de cuidado 'Pathway' (caminho) neste arquétipo.&#xD;
&#xD;
O âmbito deste arquétipo engloba atividades para uma ampla gama de procedimentos clínicos realizados para fins de avaliação, investigação, de triagem, diagnósticos, curativos, terapêuticos ou paliativos. Os exemplos vão desde as atividades relativamente simples, como a inserção de uma catéter intravenoso, até operações cirúrgicas complexas.&#xD;
&#xD;
Informações adicionais estruturadas e detalhadas sobre o procedimento podem ser capturadas usando arquétipos específicos inseridos no slot 'Detalhes do procedimento', quando necessário.&#xD;
&#xD;
Os prazos relativos a um procedimento podem ser geridos de duas formas:&#xD;
- Utilizando o modelo de referência - o tempo de execução de qualquer etapa do percurso utilizará o atributo ACTION time para cada etapa.&#xD;
- Elementos de dados arqueados:&#xD;
--- o elemento de dados 'Data/hora programada' destina-se a registar a hora exata em que o procedimento está planeado. Nota: o atributo de tempo ACTION correspondente para a etapa Caminho agendado registará o tempo que o procedimento foi programado num sistema, não a data/ hora prevista em que o procedimento deve ser realizado; e&#xD;
--- A data/hora final destina-se a registar a hora exata em que o procedimento terminou. Ele pode ser usado para documentar os procedimentos complexos com vários componentes. Nota: o atributo de tempo ACTION correspondente para o 'Procedimento executado' documentará o tempo em que cada componente executado foi iniciado. Este elemento de dados 'Data/hora final' registará a data/hora do componente ativo final do procedimento. Isso permitirá calcular a duração total do procedimento ativo.&#xD;
&#xD;
No contexto de um Relatório de Operação, este arquétipo será usado para registar apenas o que foi feito durante o procedimento. Serão utilizados arquétipos separados para registar os outros componentes necessários do Relatório de Operação, incluindo a recolha de amostras de tecido, a utilização de orientação por imagem, os resultados da operação, as instruções pós-operatórias e os planos de acompanhamento.&#xD;
&#xD;
No contexto de uma lista ou resumo de problemas, esse arquétipo pode ser usado para representar procedimentos que foram realizados. O EVALUATION.problem_diagnosis será utilizado para representar os problemas e diagnósticos do doente.&#xD;
&#xD;
Na prática, muitos procedimentos (por exemplo, em cuidados ambulatórios) ocorrerão uma vez e não serão solicitados com antecedência. Os detalhes sobre o procedimento serão adicionados contra a etapa do caminho, 'Procedimento concluído'. Em alguns casos, um procedimento recorrente será ordenado, e nesta situação os dados contra a etapa 'Procedimento executado' serão registados em cada ocasião, deixando a instrução no estado ativo. Quando a última ocorrência é registada, a ação 'Procedimento concluído' é registada mostrando que essa ordem está agora no estado concluído.&#xD;
&#xD;
Noutras situações, como a assistência secundária, pode haver uma ordem formal para um procedimento usando um arquétipo de INSTRUÇÃO correspondente. Este arquétipo ACTION pode então ser usado para registar o fluxo de trabalho de quando e como o pedido foi realizado.&#xD;
&#xD;
Registar informações usando este arquétipo ACTION indica que algum tipo de atividade realmente ocorreu; isso geralmente será o procedimento em si, mas pode ser uma tentativa fracassada ou outra atividade, como adiar o procedimento. Se houver uma ordem formal para o procedimento, o estado dessa ordem é representado pela etapa Pathway (caminho) contra a qual os dados são registados. Por exemplo, usando este arquétipo, o estado de progresso de uma ordem de Gastroscopia pode ser registado por entradas separadas nas notas de progresso do EHR em cada passo do 'Caminho':&#xD;
- registar a data/hora de início prevista para a gastroscopia (procedimento agendado); e&#xD;
- registar que o procedimento de gastroscopia foi concluído, incluindo informações sobre os pormenores do procedimento (procedimento concluído).&#xD;
&#xD;
Por favor, note que no openEHR Reference Model existe um atributo 'Time', que se destina a registar a data e a hora em que cada etapa do caminho da Ação foi executada. Este é o atributo a ser usado para registar o início do procedimento (usando a etapa de caminho 'Procedimento realizado') ou o tempo em que o procedimento foi abortado (usando a etapa de caminho 'Procedimento abortado').</use>
      <misuse>Não deve ser usado para registar detalhes sobre a anestesia - use um arquétipo ACTION separado para essa finalidade.&#xD;
&#xD;
Não deve ser usado para registar detalhes sobre exames de imagem - use ACTION.imaging_exam para este propósito.&#xD;
&#xD;
Não deve ser usado para registar detalhes sobre testes laboratoriais - use ACTION.laboratory_test para esta finalidade.&#xD;
&#xD;
Não deve ser usado para registar detalhes sobre a educação entregue - use ACTION.health_education para este propósito.&#xD;
&#xD;
Não deve ser usado para registar detalhes sobre atividades administrativas - use arquétipos ADMIN, específicos para essa finalidade.&#xD;
&#xD;
Não deve ser usado para registar detalhes sobre atividades relacionadas, como o uso de amostras congeladas tomadas durante uma operação, medicação administrada como parte do procedimento ou quando a orientação por imagem é usada durante o procedimento - usar arquétipos ACTION separados e específicos dentro do mesmo modelo para esta finalidade.&#xD;
&#xD;
Não deve ser usado para registar toda uma operação ou relatório de procedimento - use um modelo no qual este arquétipo é apenas um componente do relatório completo.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ru</code_string>
      </language>
      <purpose>Для записи сведений об проведенной процедуре</purpose>
      <keywords>процедура, выполнение</keywords>
      <use>Используется для записи подробной информации о процедуре, выполненной пациенту.&#xD;
Информация о действиях, связанных с выполнением процедуры, таких как анестезия или применение лекарств, долдно быть записано в отдельных архетипах типа ДЕЙСТВИЕ</use>
      <misuse />
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Att registrera information om de aktiviteter som krävs för att genomföra en åtgärd, inklusive planering, schemaläggning, utförande, avstängning, avbokning, dokumentation och slutförande.</purpose>
      <keywords>åtgärd</keywords>
      <keywords>intervention</keywords>
      <keywords>kirurgisk</keywords>
      <keywords>medicinsk</keywords>
      <keywords>klinisk</keywords>
      <keywords>terapeutisk</keywords>
      <keywords>diagnostisk</keywords>
      <keywords>bota</keywords>
      <keywords>behandling</keywords>
      <keywords>utredning</keywords>
      <keywords>undersökning</keywords>
      <keywords>screening</keywords>
      <keywords>palliativ</keywords>
      <keywords>terapi</keywords>
      <use>Används för att dokumentera aktiviteter som krävs för att utföra en åtgärd. Detta inkluderar information om alla steg, från planering och schemaläggning till utförande, dokumentation och färdigställande. Varje aktivitet registreras genom specifika processteg som definieras i arketypens "Pathway".&#xD;
&#xD;
Arketypen är flexibel och omfattar:&#xD;
- Enkla åtgärder som insättning av en intravenös kateter.&#xD;
- Komplexa åtgärder som kirurgiska ingrepp.&#xD;
Detaljerad information om åtgärden kan registreras med hjälp av ytterligare arketyper infogade i SLOT "Åtgärdsdetaljer" vid behov.&#xD;
&#xD;
Tider relaterade till en åtgärd hanteras på två sätt:&#xD;
- Referensmodell – Attributet "ACTION time" används för att registrera när ett processteg utfördes, dvs exakta tidpunkter för varje steg i åtgärden, inklusive avbrott och färdigställande.&#xD;
- Dataelement i en arketyp: "Schemalagt datum/tid" registrerar den planerade tidpunkten för åtgärden. "Datum/tid avslut av åtgärd" anger exakt tid för åtgärdens avslutning.&#xD;
&#xD;
Notera att "ACTION time" för schemalagda steg registrerar när en åtgärd dokumenteras i systemet, inte den faktiska tiden för åtgärden. Notera även att vid komplexa åtgärder med flera komponenter registreras durationen av åtgärden genom att dokumentera varje enskilt steg av åtgärden.&#xD;
&#xD;
Används för att registrera utförda åtgärder i en operationsrapport (Övriga delar, som provtagning, avbildning och uppföljning, hanteras med separata arketyper.).&#xD;
Används för att registrera utförda åtgärder i problemlistor eller sammanfattningar (medan EVALUATION.problem_diagnosis hanterar patientens problem och diagnoser).&#xD;
&#xD;
Används för att dokumentera arbetsflöden, där åtgärder i vissa situationer kommer registreras i steget "Åtgärd slutförd" eftersom de inte registreras i förväg.&#xD;
Används för att dokumentera återkommande åtgärder, där varje utförd åtgärd dokumenteras individuellt.&#xD;
Används för att dokumentera formella arbetsflöden, såsom ordningsföljd för åtgärder i specialistvård.&#xD;
&#xD;
Används för att dokumentera att en aktivitet faktiskt inträffat. Om en åtgärd avbrutits registreras detta i motsvarande processteg.&#xD;
Exempelvis gastroskopi med&#xD;
- Schemalagt startdatum/tid registreras som en planerad åtgärd.&#xD;
- Slutförd gastroskopi registreras med detaljer om åtgärden.</use>
      <misuse>Ska inte användas för att registrera detaljer om anestesi. Använd en separat ACTION-arketyp för detta ändamål. &#xD;
&#xD;
Ska inte användas för att registrera detaljer om bildundersökningar. Använd ACTION.imaging_exam för detta ändamål. &#xD;
&#xD;
Ska inte användas att registrera detaljer om laboratorieundersökningar. Använd ACTION.laboratory_test för detta ändamål. &#xD;
&#xD;
Ska inte användas för att registrera detaljer om utbildning. Använd ACTION.health_education för detta ändamål. &#xD;
&#xD;
Ska inte användas för att registrera detaljer om administrativa aktiviteter. Använd specifika ADMIN-arketyper för detta ändamål. &#xD;
&#xD;
Ska inte användas för att registrera detaljer om relaterade aktiviteter, såsom användning av fryssnitt som tagits under en operation, läkemedel som administreras som en del av åtgärden eller när vägledning för bildvisning används under åtgärden. Använd separata och specifika ACTION-arketyper inom samma template för detta syfte. &#xD;
&#xD;
Ska inte användas för att registrera en hel operation eller rapport för åtgärd. Använd en template där den här arketypen bara är en av flera komponenter i rapporten.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere informasjon om aktiviteter som må gjennomføres for å utføre en klinisk prosedyre, inkludert planlegging, fastsetting av tidspunkt, utførelse, utsettelse, kansellering, dokumentering og fullføring.</purpose>
      <keywords>prosedyre</keywords>
      <keywords>intervensjon</keywords>
      <keywords>kirurgisk</keywords>
      <keywords>medisinsk</keywords>
      <keywords>klinisk</keywords>
      <keywords>terapeutisk</keywords>
      <keywords>diagnostisk</keywords>
      <keywords>behandling</keywords>
      <keywords>kur</keywords>
      <keywords>evaluering</keywords>
      <keywords>undersøkelse</keywords>
      <keywords>screening</keywords>
      <keywords>palliativ</keywords>
      <keywords>terapi</keywords>
      <keywords>prognostisk</keywords>
      <use>Brukes til å registrere nødvendig informasjon om aktiviteter i gjennomføringen av en klinisk prosedyre. Dette inkluderer planlegging, fastsetting av tidspunkt, utførelse, utsettelse, avlysning, dokumentering og fullføring. Dette gjøres ved å registrere data knyttet til spesifikke aktiviteter som definert i arketypens prosesstrinn (Engelsk: "Pathway careflow steps").&#xD;
&#xD;
Arketypen dekker aktiviteter for et bredt spekter av kliniske prosedyrer utført i evaluerende, undersøkende, diagnostisk, kurativ, terapeutisk eller palliativ hensikt. Eksempler strekker seg fra relativt enkle aktiviteter som innlegging av et intravenøst kateter, til komplekse kirurgiske operasjoner.&#xD;
&#xD;
Strukturert og detaljert tilleggsinformasjon om prosedyren kan registreres ved bruk av spesifikke CLUSTER-arketyper satt inn i "Prosedyredetaljer"-SLOTet der dette kreves.&#xD;
&#xD;
Tidsberegning relatert til en prosedyre kan håndteres på en av to måter:&#xD;
-Ved å benytte referansemodellen: Tiden for gjennomføring av et prosesstrinn vil benytte "time"-attributtet som ligger implisitt i en ACTION-arketype, for hvert enkelt prosesstrinn.&#xD;
-Dataelementer i arketypen:&#xD;
---Dataelementet "Planlagt dato/tid" skal brukes for å registrere nøyaktig tidspunkt prosedyren er planlagt. Merk: Det korresponderende "time"-attributtet for prosesstrinnet "Fastsatt tidspunkt for prosedyre" registrerer tidspunktet da prosedyren ble planlagt, ikke dato/tid for når prosedyren er planlagt gjennomført. &#xD;
--- "Endelig dato/tid" skal registrere nøyaktig tidspunkt for da prosedyren ble avsluttet. Den kan brukes for å dokumentere komplekse prosedyrer med mange komponenter. Merk: Det korresponderende "time"-attributtet for prosesstrinnet "Prosedyre iverksatt" dokumenterer tidspunkt for hver gang en komponent er gjennomført eller påbegynt. Dataelementet "Endelig dato/tid" registrerer dato/tid for det siste aktive komponenten av prosedyren. Dette åpner for mulighet for utregning av den totale varigheten av den aktive prosedyren.&#xD;
&#xD;
Ved bruk i en operasjonsrapport skal arketypen bare benyttes for å registrere hva som ble utført under prosedyren. Egne arketyper vil bli benyttet for å registrere andre komponenter av operasjonsrapporten, dette inkluderer biopsitakning, bildediagnostisk veiledning, funn under operasjonen, postoperative instruksjoner og videre planer for oppfølging.&#xD;
&#xD;
I en problemliste eller i et problemsammendrag kan denne arketypen benyttes for å gi en oversikt over hvilke prosedyrer som er utført. Arketypen EVALUATION.problem_diagnosis vil benyttes for å gi en oversikt over pasientens problemer og diagnoser.&#xD;
&#xD;
I praksis vil mange prosedyrer (f.eks. i primærhelsetjenesten) utføres én gang, og ikke bestilles i forkant. Detaljene om prosedyren vil da registreres for det aktuelle prosesstrinnet. I noen tilfeller vil en gjentagende prosedyre bli rekvirert, og i en slik situasjon registreres prosesstrinnet "Prosedyre utført" i hvert enkelt tilfelle, og instruksjonen forblir i en aktiv tilstand. Når den siste prosedyren i serien er registrert settes prosesstrinnet "Prosedyre avsluttet" for å avslutte forordningen.&#xD;
&#xD;
I andre situasjoner, for eksempel i spesialisthelsetjenesten, kan det foreligge en formell rekvisisjon for en prosedyre hvor en motsvarende INSTRUCTION-arketype er benyttet. Denne ACTION-arketypen benyttes da for å registrere arbeidsflyt og når og hvordan prosedyren ble utført.&#xD;
&#xD;
Registrering av informasjon i denne ACTION-arketypen indikerer at en eller annen type aktivitet faktisk er utført; dette vil vanligvis være prosedyren i seg selv, men kan også være et mislykket forsøk eller en annen aktivitet som f.eks. en utsettelse av prosedyren. Finnes det en formell henvisning til en prosedyre, er henvisningens status representert i det prosesstrinnet hvor data er registrert. For eksempel vil gjennomføringen av en gastroskopi lagret i denne arketypen kunne registreres som flere påfølgende oppføringer innen et fremdriftsnotat, en oppføring for hvert prosesstrinn:&#xD;
&#xD;
- registrert planlagt Start dato/tid for gastroskopien ("Prosedyre planlagt")&#xD;
- registrert at gastroskopiprosedyren er fullført, inkludert informasjon om prosedyredetaljene ("Prosedyre avsluttet").&#xD;
&#xD;
Legg merke til at det i openEHR referansemodellen er et attributt "time" som er tenkt brukt til å registrere dato og tid for når hvert enkelt prosesstrinn i ACTION-arketypen ble utført. Denne attributten skal brukes til å registre da prosedyren startet (ved prosesstrinnet "Prosedyre iverksatt"), eller tidspunktet da prosedyren ble avbrutt (ved prosesstrinnet "Prosedyre avbrutt").</use>
      <misuse>Benyttes ikke til å registrere detaljer om administrasjon av legemidler - bruk ACTION.medication til dette formålet.&#xD;
&#xD;
Benyttes ikke til å registrere detaljer om bildediagnostiske undersøkelser - bruk ACTION.imaging_exam til dette formålet.&#xD;
&#xD;
Benyttes ikke til å registrere detaljer om laboratorieundersøkelser - bruk ACTION.laboratory_test til dette formålet.&#xD;
&#xD;
Benyttes ikke til å registrere detaljer om pasientopplæring - bruk ACTION.health_education til dette formålet.&#xD;
&#xD;
Benyttes ikke til å registrere detaljer om administrative aktiviteter - bruk spesifikke ADMIN-arketyper til dette formålet.&#xD;
&#xD;
Benyttes ikke til registrering om relaterte aktiviteter som bruk av frysesnitt tatt under en operasjon, legemidler gitt som del av prosedyren, eller når bildeveiledning er brukt under prosedyren. Bruk separate og spesifikke ACTION-arketyper innen samme templat til dette formålet.&#xD;
&#xD;
Benyttes ikke for å registrere en hel operasjon eller prosedyrerapport - bruk en templat der denne arketypen er kun en komponent av den fullstendige rapporten.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Para registrar os detalhes sobre um procedimento realizado, incluindo o planejamento, programação , execução, suspensão , cancelamento , documentação e conclusão.</purpose>
      <keywords>procedimento</keywords>
      <keywords>intervenção</keywords>
      <keywords>cirúrgico</keywords>
      <keywords>médico</keywords>
      <keywords>clínico</keywords>
      <keywords>terapêutico</keywords>
      <keywords>diagnóstico</keywords>
      <keywords>cura</keywords>
      <keywords>tratamento</keywords>
      <keywords>evolução</keywords>
      <keywords>investigação</keywords>
      <keywords>paliativo</keywords>
      <keywords>terapia</keywords>
      <use>Use para registrar informações sobre as atividades necessárias para realizar um procedimento , incluindo o planejamento, programação , execução, suspensão , cancelamento , documentação e conclusão. Isto é feito através do registro de dados de atividades específicas , conforme definido neste arquétipo .&#xD;
&#xD;
O escopo deste arquétipo abrange as atividades para uma ampla gama de procedimentos clínicos realizados para avaliação, investigação , triagem , diagnóstico , curativo, terapêutico ou fins paliativos. Os exemplos vão desde as atividades relativamente simples, tais como a inserção de uma cânula intravenosa , através de operações cirúrgicas complexas .&#xD;
&#xD;
Informações adicionais estruturadas e detalhadas sobre o procedimento podem ser capturadas utilizando arquétipos específicos de uso inserido no slot 'Detalhe do Procedimento', onde for necessário.&#xD;
&#xD;
Tempos relacionados a um procedimento podem ser gerenciados de uma de duas maneiras:&#xD;
- Usando o modelo de referência - o prazo para realização de qualquer passo/caminho usará o atributo tempo de ação para cada etapa.&#xD;
- Elementos de dados arquetipados:&#xD;
--- Elemento de dados "data / hora agendada" destina-se a registrar o tempo exato em que o procedimento é planejado. Nota: o atributo de tempo de ação correspondente para o passo via Programado irá registrar o tempo que o procedimento foi programado em um sistema, não a data / hora pretendida em que o procedimento se destina a ser realizado; e&#xD;
--- O 'data final / hora' destina-se a registrar o tempo exato em que o processo foi encerrado. Ele pode ser usado para documentar os procedimentos complexos com componentes múltiplos. Nota: o atributo de tempo de ação correspondente para o "procedimento realizado" irá documentar o tempo de cada componente realizada foi iniciada. Este elemento de dados 'Data / hora Final' registrará a data / hora do último componente ativo do procedimento. Isto irá permitir uma duração total do processo ativo a ser calculado.&#xD;
&#xD;
Dentro do contexto de um Relatório de Cirurgia, esse arquétipo será usado para gravar apenas o que foi feito durante o procedimento. Arquétipos separados serão utilizados para gravar os outros componentes necessários, incluindo a coleta de amostras de tecidos, utilização de imagens intraoperatórias, achados cirúrgicos, instruções pós-operatória e planos de acompanhamento.&#xD;
&#xD;
Dentro do contexto de uma lista de problemas ou resumo, este arquétipo pode ser usado ​​para representar os procedimentos que têm sido realizados. O EVALUATION.problem_diagnosis será usado para representar os problemas do paciente e diagnósticos.&#xD;
&#xD;
Na prática, muitos procedimentos (por exemplo, um atendimento ambulatorial) ocorrerá uma vez e não será planejado com antecedência. Os detalhes sobre o procedimento serão adicionados ao passo/caminho, «Processo concluído". Em alguns casos um procedimento recorrente será ordenado, e nesta situação os dados do "procedimento realizado" será gravado em cada ocasião, deixando a instrução no estado ativo. Quando a última ocorrência é registrada do "Procedimento concluído" a ação é registrada mostrando que essa ordem está agora no estado concluído.&#xD;
&#xD;
Em outras situações, tais como atenção secundária, pode haver uma ordem formal de um procedimento usando um arquétipo instrução correspondente. Este arquétipo ação pode então ser usado para registrar o fluxo de trabalho de quando e como a ordem foi executada.&#xD;
&#xD;
Gravando informações utilizando esse arquétipo AÇÃO indica que algum tipo de atividade realmente ocorreu; este será geralmente o procedimento em si, mas pode ser uma tentativa fracassada ou outra atividade, como o adiamento do procedimento. Se existe uma ordem formal para o procedimento, o estado desta ordem é representado pelo passo Pathway contra a qual os dados são gravados. Por exemplo, usando esse arquétipo do estado progredindo de uma ordem Gastroscopia podem ser registrados através de entradas separadas no progresso EHR observado um passo a cada 'Caminho':&#xD;
- Registrar o início de data / hora programada para a gastroscopia (Procedimento programado); e&#xD;
- Gravar que o procedimento foi concluído gastroscopia, incluindo informações sobre os detalhes de procedimento (processo encerrado).&#xD;
&#xD;
Por favor, note que no Modelo de Referência openEHR há um atributo 'Time', que se destina a registrar a data e hora em que foi realizada a cada passo via da ação. Este é o atributo a ser usado para registar o início do procedimento (usando o "procedimento realizado 'passo via), ou o tempo que o procedimento foi abortada (usando o" procedimento abortado' passo via)</use>
      <misuse>Não deve ser usado para gravar detalhes sobre o anestésico - usar um arquétipo ação separada para esse fim.&#xD;
&#xD;
Não deve ser usado para registrar detalhes sobre as investigações de imagem - use ACTION.imaging_exam para esta finalidade.&#xD;
&#xD;
Não deve ser usado para gravar detalhes sobre investigações laboratoriais - ACTION.laboratory_test usar para essa finalidade.&#xD;
&#xD;
Não deve ser usado para gravar detalhes sobre educação entregues - ACTION.health_education usar para essa finalidade.&#xD;
&#xD;
Não deve ser usado para registrar detalhes sobre as atividades administrativas - usar arquétipos ADMIN específicos para esta finalidade.&#xD;
&#xD;
Não deve ser usado para gravar detalhes sobre as atividades relacionadas, tais como medicação administrada como parte do processo ou quando utilização de imagens para visualização é utilizado durante o procedimento - usar arquétipos ação separados e específicos dentro do mesmo modelo para este fim.&#xD;
&#xD;
Não deve ser usado para gravar uma operação ou procedimento relatório conjunto - usar um modelo em que esse arquétipo é apenas um componente do relatório completo.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record information about the activities required to carry out a procedure, including the planning, scheduling, performance, suspension, cancellation, documentation and completion.</purpose>
      <keywords>procedure</keywords>
      <keywords>intervention</keywords>
      <keywords>surgical</keywords>
      <keywords>medical</keywords>
      <keywords>clinical</keywords>
      <keywords>therapeutic</keywords>
      <keywords>diagnostic</keywords>
      <keywords>cure</keywords>
      <keywords>treatment</keywords>
      <keywords>evaluation</keywords>
      <keywords>investigation</keywords>
      <keywords>screening</keywords>
      <keywords>palliative</keywords>
      <keywords>therapy</keywords>
      <use>Use to record information about the activities required to carry out a procedure, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. This is done by the recording of data against specific activities, as defined by the 'Pathway' careflow steps in this archetype.&#xD;
&#xD;
The scope of this archetype encompasses activities for a broad range of clinical procedures performed for evaluative, investigative, screening, diagnostic, curative, therapeutic or palliative purposes. Examples range from the relatively simple activities, such as insertion of an intravenous cannula, through to complex surgical operations.&#xD;
&#xD;
Additional structured and detailed information about the procedure can be captured using purpose-specific archetypes inserted into the 'Procedure detail' slot, where required.&#xD;
&#xD;
Timings related to a procedure can be managed in one of two ways:&#xD;
- Using the reference model - the time for performance of any pathway step will use the ACTION time attribute for each step.&#xD;
- Archetyped data elements:&#xD;
--- the 'Scheduled date/time' data element is intended to record the precise time when the procedure is planned. Note: the corresponding ACTION time attribute for the Scheduled pathway step will record the time that the procedure was scheduled into a system, not the intended date/time on which the procedure is intended to be carried out; and&#xD;
--- the 'Final end date/time' is intended to record the precise time when the procedure was ended. It can be used to document the complex procedures with multiple components. Note: the corresponding ACTION time attribute for the 'Procedure performed' will document the time each component performed was commenced. This 'Final end date/time' data element will record the date/time of the final active component of the procedure. This will enable a full duration of the active procedure to be calculated.&#xD;
&#xD;
Within the context of an Operation Report, this archetype will be used to record only what was done during the procedure. Separate archetypes will be used to record the other required components of the Operation Report, including the taking of tissue specimen samples, use of imaging guidance, operation findings, post-operative instructions and plans for follow up.&#xD;
&#xD;
Within the context of a Problem list or summary, this archetype may be used to represent procedures that have been performed. The EVALUATION.problem_diagnosis will be used to represent the patient's problems and diagnoses.&#xD;
&#xD;
In practice, many procedures (for example, in ambulatory care) will occur once and not be ordered in advance. The details about the procedure will be added against the pathway step, 'Procedure completed'. In some cases a recurring procedure will be ordered, and in this situation data against the 'Procedure performed' step will be recorded on each occasion, leaving the instruction in the active state. When the last occurrence is recorded the 'Procedure completed' action is recorded showing that this order is now in the completed state.&#xD;
&#xD;
In other situations, such as secondary care, there may be a formal order for a procedure using a corresponding INSTRUCTION archetype. This ACTION archetype can then be used to record the workflow of when and how the order has been carried out.&#xD;
&#xD;
Recording information using this ACTION archetype indicates that some sort of activity has actually occurred; this will usually be the procedure itself but may be a failed attempt or another activity such as postponing the procedure. If there is a formal order for the procedure, the state of this order is represented by the Pathway step against which the data is recorded. For example, using this archetype the progressing state of a Gastroscopy order may be recorded through separate entries in the EHR progress notes at each 'Pathway' step:&#xD;
- record the scheduled Start date/time for the gastroscopy (Procedure scheduled); and&#xD;
- record that the gastroscopy procedure has been completed, including information about the procedure details (Procedure completed).&#xD;
&#xD;
Please note that in the openEHR Reference Model there is a 'Time' attribute, which is intended to record the date and time at which each pathway step of the Action was performed. This is the attribute to use to record the start of the procedure (using the 'Procedure performed' pathway step) or the time that the procedure was aborted (using the 'Procedure aborted' pathway step).</use>
      <misuse>Not to be used to record details about the anaesthetic - use a separate ACTION archetype for this purpose.&#xD;
&#xD;
Not to be used to record details about imaging investigations - use ACTION.imaging_exam for this purpose.&#xD;
&#xD;
Not to be used to record details about laboratory investigations - use ACTION.laboratory_test for this purpose.&#xD;
&#xD;
Not to be used to record details about education delivered - use ACTION.health_education for this purpose.&#xD;
&#xD;
Not to be used to record details about administrative activities - use specific ADMIN archetypes for this purpose.&#xD;
&#xD;
Not to be used to record details about related activities such as the use of frozen sections taken during an operation, medication administered as part of the procedure or when imaging guidance is used during the procedure - use separate and specific ACTION archetypes within the same template for this purpose .&#xD;
&#xD;
Not to be used to record a whole operation or procedure report - use a template in which this archetype is only one component of the full report.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ar-sy</code_string>
      </language>
      <purpose>لتسجيل تفاصيل حول إجراء طبي تم بالفعل إجراؤه</purpose>
      <keywords>الإجراء الطبي</keywords>
      <use>لتسجيل معلومات تفصيلية حول إجراء طبي تم تنفيذه على شخص ما. و ينبغي تسجيل المعلومات حول النشاطات المتعلقة بالنشاطات المتعلقة بالإجراء الطبي, مثل التخدير أو إعطاء الأدوية في نماذج (فعل) منفردة.</use>
      <misuse />
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sl</code_string>
      </language>
      <purpose>Za beleženje podrobnosti o izvedeni aktivnosti</purpose>
      <keywords>aktivnosti</keywords>
      <keywords>postopek</keywords>
      <use>Za beleženje podrobnosto o izvedeni aktivnosti, ki zadeva posameznega pacienta/subjekt</use>
      <misuse>Podrobnosti o aktivnostih povezani z opisano kativnostjo, kot npr. dajanje zdravil, se zabeleži v arhetipih tipa ACTION</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>zh-cn</code_string>
      </language>
      <purpose>旨在记录为执行某项操作时所需开展的各项活动的相关信息，包括操作的规划/计划编制、排程/排期、执行/实施、暂停、取消/撤销、记载/文档记录以及完成等环节。</purpose>
      <keywords>操作</keywords>
      <keywords>操作项目</keywords>
      <keywords>干预</keywords>
      <keywords>干预措施</keywords>
      <keywords>外科</keywords>
      <keywords>外科手术</keywords>
      <keywords>医疗</keywords>
      <keywords>临床</keywords>
      <keywords>治疗性</keywords>
      <keywords>治疗类</keywords>
      <keywords>诊断性</keywords>
      <keywords>诊断类</keywords>
      <keywords>治愈</keywords>
      <keywords>治疗</keywords>
      <keywords>处理</keywords>
      <keywords>处置</keywords>
      <keywords>评价</keywords>
      <keywords>评估</keywords>
      <keywords>探查</keywords>
      <keywords>检查</keywords>
      <keywords>筛查</keywords>
      <keywords>姑息治疗</keywords>
      <keywords>疗法</keywords>
      <keywords>治疗方法</keywords>
      <use>旨在记录为执行某项操作时所需开展的各项活动的相关信息，包括操作的规划/计划编制、排程/排期、执行/实施、暂停、取消/撤销、记载/文档记录以及完成等环节。为此采取的方法就是记录关于本原始型之中的“路径”（Pathway）照护服务流程步骤所定义的这些具体活动的数据。&#xD;
&#xD;
本原始型的适用范围涵盖为了实现评估类、探查类、筛查类、诊断类、治愈类、疗法类或姑息治疗类等目的而开展的各类临床操作的相关活动。示例既包括相对简单的操作（如静脉插管置入），也涵盖复杂的外科手术。&#xD;
&#xD;
必要时，通过将针对特定用途的原始型插入到操作详情槽位“Procedure detail”当中，来记录更多其他关于当前操作的结构化详情。&#xD;
&#xD;
可采取下列两种方式之一来管理与当前操作相关的时间特征：&#xD;
&#xD;
- 采用参考模型：任何路径步骤的执行时间均采用该步骤的行动类时间属性ACTION.time。&#xD;
- 原始型化的数据元：&#xD;
--- 排程日期/时间“Scheduled date/time”数据元用于记录为操作编制计划/排程时的精确时间。注：已排程路径步骤相应的行动类时间属性ACTION.time，记录的是将当前操作排程到信息系统之中时的时间，而并非预定开展/执行当前操作时的日期/时间；&#xD;
--- 最终结束日期/时间“Final end date/time”用于记录操作实际结束时的精确时间。该数据元可用于记录包含多个组成部分的复杂操作。注：针对已执行操作“Procedure performed”的行动类时间属性ACTION.time，记录的是所执行的每个组成部分的实际开始[执行]时间；而最终结束日期/时间数据元则记录的是操作最后一个有效的组成部分的[实际]结束日期/时间。这样，就可以利用这些来计算当前整个有效操作的总时长。&#xD;
&#xD;
在“手术报告”（Operation Report）语境下，本原始型仅用于记录手术操作过程中实际执行的内容。对于手术报告所需的其他组成部分（包括组织标本取样、影像引导的使用、手术发现、术后指导及随访计划等），则需要利用其他单独的原始型来加以记录。&#xD;
&#xD;
在“问题列表”（Problem list）或“问题摘要”（Problem summary）语境下，本原始型可用于呈现已完成的那些操作。而问题诊断评估类原始型 EVALUATION.problem_diagnosis 则用于表达患者的各类问题和诊断。&#xD;
&#xD;
实际应用中，许多的操作（如门诊诊疗中的操作）属于是一次性的执行，且并不会提前下达医嘱。对于此类操作的相关详情，可在“已完成操作”（Procedure completed）路径步骤下加以录入。在某些情况下，会下达关于重复性操作的医嘱；此时，就需在每次执行操作的场合下，在“已执行操作”（Procedure performed）路径步骤之下记录相关的数据，并将相应的操作指令/医嘱保持在有效状态。当记录最后一次[的重复性]操作执行情况时，将会记录“已完成操作”（Procedure completed）行动，以表明该医嘱现已处于完成状态。&#xD;
&#xD;
在其他的场景（如二级诊疗/照护服务）下，可能会存在针对某一操作的正式医嘱，并利用相应的指令类原始型（INSTRUCTION）来加以记录。那么，则可以利用本动作类原始型（ACTION）来记录关于该医嘱执行时间和执行方式的工作流信息。&#xD;
&#xD;
利用本动作类原始型（ACTION）来记录信息，表明已实际发生了某种活动；该活动通常为当前操作本身，但也可能是一次失败的尝试，或其他的活动（如操作延期）。若当前操作有相应的正式医嘱，则会利用录入数据时所针对的路径步骤来表达该医嘱的状态。例如，每个“路径”步骤上，则可利用本原始型，在电子健康档案（EHR）病程记录当中，采用多个单独的条目，来记录胃镜检查医嘱的进展状态：&#xD;
&#xD;
- 记录为胃镜检查（已排程操作）所排程的开始日期/时间；&#xD;
- 记录胃镜检查已完成，包括操作详情（已完成操作）的相关信息。&#xD;
&#xD;
请注意，在openEHR参考模型中，其中设有的时间属性“Time”，用于记录相应行动（Action）之中每个路径步骤的实际执行日期/时间。该属性旨在用于记录当前操作的开始（利用“已执行操作”路径步骤）或当前操作的中止时间（利用“已中止操作”路径步骤）。</use>
      <misuse>并非旨在用于记录麻醉的相关详情 —— 应当采用单独的行动类原始型（ACTION）来记录此类的信息。&#xD;
&#xD;
并非旨在用于记录影像检查的相关详情 —— 应当采用行动类影像检查原始型（ACTION.imaging_exam）来记录此类的信息。&#xD;
&#xD;
并非旨在用于记录实验室检查的相关详情 —— 应当采用行动类实验室检验项目原始型（ACTION.laboratory_test）来记录此类的信息。&#xD;
&#xD;
并非旨在用于记录关于所提供的健康教育的相关详情 —— 应当采用行动类健康宣教原始型（ACTION.health_education）来记录此类的信息。&#xD;
&#xD;
并非旨在用于记录行政管理类活动的相关详情 —— 应当采用特定的管理类原始型（ADMIN）来记录此类的信息。&#xD;
&#xD;
并非旨在用于记录相关活动的详情，如术中冰冻切片的使用、操作过程中所施用的药物或操作过程中所采用的影像引导措施等 —— 应当在同一模板内采用特定单独的行动类原始型（ACTION）来记录此类的信息。&#xD;
&#xD;
并非旨在用于记录完整的手术或操作报告 —— 应当采用模板来加以记录，而本原始型则仅仅是作为完整报告的组成部分之一。</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Registrar información sobre las actividades necesarias para llevar a cabo un procedimiento, incluida la planificación, programación, ejecución, suspensión, cancelación, documentación y finalización.</purpose>
      <keywords>procedimiento</keywords>
      <keywords>intervención</keywords>
      <keywords>quirúrgico</keywords>
      <keywords>médico</keywords>
      <keywords>clínico</keywords>
      <keywords>terapéutico</keywords>
      <keywords>diagnóstico</keywords>
      <keywords>cura</keywords>
      <keywords>tratamiento</keywords>
      <keywords>evaluación</keywords>
      <keywords>investigación</keywords>
      <keywords>cribado</keywords>
      <keywords>paliativo</keywords>
      <keywords>terapia</keywords>
      <use>Se utiliza para registrar información sobre las actividades requeridas para llevar a cabo un procedimiento, incluyendo planificación, coordinación, ejecución, suspensión, cancelación, documentación y finalización. Esto se hace mediante el registro de los datos sobre actividades específicas, según la definición de los pasos de la vía clínica definida en el arquetipo.&#xD;
&#xD;
El alcance de este arquetipo abarca actividades para una amplia gama de procedimientos clínicos realizados con fines evaluativos, de investigación, cribado, diagnóstico, curativos, terapéuticos o paliativos. Los ejemplos van desde actividades relativamente sencillas, como la inserción de una cánula intravenosa, hasta operaciones quirúrgicas complejas.&#xD;
&#xD;
Se puede capturar información adicional estructurada y detallada sobre el procedimiento utilizando arquetipos específicos insertados en el slot "Detalle del procedimiento", cuando sea necesario.&#xD;
&#xD;
Los tiempos relacionados con un procedimiento pueden gestionarse de dos maneras:&#xD;
- Utilizando el modelo de referencia: el tiempo de realización de cualquier etapa del proceso utilizará el atributo de tiempo ACTION de cada etapa.&#xD;
- Elementos de datos arquetipados:&#xD;
--- el elemento de datos "Fecha/hora prevista" tiene por objeto registrar el momento preciso en que está previsto realizar el procedimiento. Nota: el atributo de hora ACTION correspondiente a la etapa Scheduled registrará la hora en la que el procedimiento se programó en un sistema, no la fecha/hora prevista en la que se pretende llevar a cabo el procedimiento; y&#xD;
--- la "Fecha/hora de finalización" tiene por objeto registrar la hora exacta en que finalizó el procedimiento. Puede utilizarse para documentar los procedimientos complejos con múltiples componentes. Nota: el atributo ACTION time correspondiente al "Procedimiento realizado" documentará la hora en que se inició cada componente realizado. Este elemento de datos "Fecha/hora final" registrará la fecha/hora del último componente activo del procedimiento. Esto permitirá calcular la duración completa del procedimiento activo.&#xD;
&#xD;
En el contexto de un Informe Quirúrgico, este arquetipo se utilizará para registrar únicamente lo que se hizo durante el procedimiento. Se utilizarán arquetipos separados para registrar los demás componentes necesarios del informe, incluida la toma de muestras de tejido, el uso de la guía por imagen, los resultados de la intervención, las instrucciones postoperatorias y los planes de seguimiento.&#xD;
&#xD;
En el contexto de una lista o resumen de problemas, este arquetipo puede utilizarse para representar los procedimientos que se han realizado. EVALUATION.problem_diagnosis se utilizará para representar los problemas y diagnósticos del paciente.&#xD;
&#xD;
En la práctica, muchos procedimientos (por ejemplo, en atención ambulatoria) tendrán lugar una sola vez y no se solicitarán con antelación. Los detalles sobre el procedimiento se añadirán en el apartado "Procedimiento realizado". En algunos casos se pedirá un procedimiento recurrente, y en esta situación los datos contra el apartado "Procedimiento realizado" se registrarán en cada ocasión, dejando la instrucción en estado activo. Cuando se registre la última incidencia, se registra la acción "Procedimiento completado", lo que indica que esta orden se encuentra ahora en estado completado.&#xD;
&#xD;
En otras situaciones, como la atención secundaria, puede existir una orden formal para un procedimiento utilizando el correspondiente arquetipo INSTRUCTION. Este arquetipo ACTION puede utilizarse para registrar el flujo de trabajo de cuándo y cómo se ha llevado a cabo la orden.&#xD;
&#xD;
El registro de información mediante este arquetipo ACTION indica que se ha producido algún tipo de actividad; normalmente será el procedimiento en sí, pero puede tratarse de un intento fallido u otra actividad, como el aplazamiento del procedimiento. Si existe una orden formal para el procedimiento, el estado de esta orden queda representado por la fase del proceso contra la que se registran los datos. Por ejemplo, utilizando este arquetipo, el estado de progreso de una orden de Gastroscopia puede registrarse mediante entradas separadas en las notas de progreso de la HCE en cada fase:&#xD;
- registrar la fecha/hora de inicio programada para la gastroscopia (Procedimiento programado); y&#xD;
- registrar que el procedimiento de gastroscopia se ha completado, incluyendo información sobre los detalles del procedimiento (Procedimiento completado).&#xD;
&#xD;
Tenga en cuenta que en el Modelo de Referencia openEHR existe un atributo "Hora", cuyo objetivo es registrar la fecha y hora en que se completó cada uno de los distintos apartados. Este es el atributo que debe utilizarse para registrar el inicio del procedimiento (utilizando el apartado "Procedimiento realizado") o el momento en que se interrumpió el procedimiento (utilizando el apartado "Procedimiento interrumpido").</use>
      <misuse>No debe utilizarse para registrar detalles acerca de la anestesia; para ello, utilizar un arquetipo ACTION distinto.&#xD;
&#xD;
No debe utilizarse para registrar detalles acerca de estudios por imagen; para ello, utilizar el arquetipo ACTION.imaging_exam.&#xD;
&#xD;
No debe utilizarse para registrar detalles acerca de estudios de laboratorio; para ello, utilizar el arquetipo ACTION.laboratory_test.&#xD;
&#xD;
No debe utilizarse para registrar datos acerca de la educación impartida; para ello, utilizar el arquetipo ACTION.health_education.&#xD;
&#xD;
No debe utilizarse para registrar detalles acerca de actividades administrativas; para ello, utilizar arquetipos ADMIN específicos.&#xD;
&#xD;
No debe utilizarse para registrar detalles acerca de actividades relacionadas, como el uso de secciones congeladas tomadas durante una operación, medicación administrada durante el procedimiento o al hacer uso de la guía por imagen durante el procedimiento; para ello, utilizar arquetipos ACTION por separado y específicos dentro de la misma plantilla.&#xD;
&#xD;
No debe utilizarse para registrar un informe de operación o procedimiento completo: utilizar una plantilla en la que este arquetipo sea sólo un componente del informe completo.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ca</code_string>
      </language>
      <purpose>Registrar informació sobre les activitats necessàries per dur a terme un procediment, inclosa la planificació, la programació, l'execució, la suspensió, la cancel·lació, la documentació i la finalització.</purpose>
      <keywords>procediment</keywords>
      <keywords>intervenció</keywords>
      <keywords>quirúrgic</keywords>
      <keywords>metge</keywords>
      <keywords>clínic</keywords>
      <keywords>terapèutic</keywords>
      <keywords>diagnòstic</keywords>
      <keywords>curar</keywords>
      <keywords>tractament</keywords>
      <keywords>avaluació</keywords>
      <keywords>investigació</keywords>
      <keywords>detecció</keywords>
      <keywords>pal·liatiu</keywords>
      <keywords>teràpia</keywords>
      <use>S'utilitza per registrar informació sobre les activitats requerides per dur a terme un procediment, incloent-hi planificació, coordinació, execució, suspensió, cancel·lació, documentació i finalització. Això es fa mitjançant el registre de les dades sobre activitats específiques, segons la definició de les diferents etapes/apartats definit a l'arquetip.&#xD;
&#xD;
L'abast d'aquest arquetip inclou activitats per a una àmplia gamma de procediments clínics realitzats amb fins avaluatius, de recerca, cribratge, diagnòstic, curatius, terapèutics o pal·liatius. Els exemples van des d'activitats relativament senzilles, com ara la inserció d'una cànula intravenosa, fins a operacions quirúrgiques complexes.&#xD;
&#xD;
Es pot capturar informació addicional estructurada i detallada sobre el procediment utilitzant arquetips específics inserits a l'slot "Detall del procediment", quan sigui necessari.&#xD;
&#xD;
Els temps relacionats amb un procediment es poden gestionar de dues maneres:&#xD;
- Utilitzant el model de referència: el temps de realització de qualsevol etapa del procés utilitzarà l‟atribut de temps ACTION de cada etapa.&#xD;
- Elements de dades arquetipades:&#xD;
--- l'element de dades "Data/hora prevista" té per objecte registrar el moment precís en què està previst fer el procediment. Nota: l'atribut d'hora ACTION corresponent a l'etapa Scheduled registrarà l'hora en què el procediment es va programar en un sistema, no la data/hora prevista en què es vol dur a terme el procediment; i&#xD;
--- la "Data/hora de finalització" té per objecte registrar l'hora exacta en què va finalitzar el procediment. Es pot utilitzar per documentar els procediments complexos amb múltiples components. Nota: l'atribut ACTION time corresponent al "Procediment realitzat" documentarà l'hora en què es va iniciar cada component realitzat. Aquest element de dades "Data/hora final" registrarà la data/hora del darrer component actiu del procediment. Això permetrà calcular la durada completa del procediment actiu.&#xD;
&#xD;
En el context d'un informe quirúrgic, aquest arquetip s'utilitzarà per registrar únicament allò que es va fer durant el procediment. S'utilitzaran arquetips separats per registrar els altres components requerits de l'informe quirúrgic, inclosa la presa de mostres de teixit, l'ús de guia per imatges, les troballes de l'operació, les instruccions postoperatòries i els plans de seguiment.&#xD;
&#xD;
Dins del context d'un llistat o resum de problemes, aquest arquetip es pot fer servir per representar procediments que s'han realitzat. L'AVALUATION.problem_diagnosis s'utilitzarà per representar els problemes i els diagnòstics del pacient.&#xD;
&#xD;
A la pràctica, molts procediments (per exemple, en atenció ambulatòria) es realitzaran una vegada i no se sol·licitaran amb anticipació. Els detalls sobre el procediment s'afegiran a la fase del procés "Procediment completat". En alguns casos, s'ordenarà un procediment recurrent i, en aquesta situació, es registraran les dades de la fase 'Procediment realitzat' cada vegada, deixant la instrucció en estat actiu. Quan es registra la darrera ocurrència, es registra l'acció "Procediment completat", cosa que mostra que aquesta ordre ara està en estat completat.&#xD;
&#xD;
En altres situacions, com a l'atenció secundària, hi pot haver una ordre formal per a un procediment utilitzant l'arquetip d'INSTRUCTION corresponent. Aquest arquetip de ACTION es pot utilitzar per registrar el flux de treball de quan i com es va dur a terme l'ordre.&#xD;
&#xD;
Registrar informació utilitzant aquest arquetip de ACTION indica que realment ha passat algun tipus d'activitat; En general, aquest serà el procediment en si, però pot ser un intent fallit o una altra activitat, com ara posposar el procediment. Si hi ha una ordre formal per al procediment, l‟estat d‟aquesta ordre està representat per la fase del procés contra la qual es registren les dades. Per exemple, en utilitzar aquest arquetip, l'estat de progrés d'una ordre de gastroscòpia es pot registrar a través d'entrades separades a les notes de progrés de l'HCE a cada fase del procés:&#xD;
- registrar la data/hora d'inici programada per a la gastroscòpia (procediment programat); i&#xD;
- Enregistrar que s'ha completat el procediment de gastroscòpia, inclosa informació sobre els detalls del procediment (Procediment completat).&#xD;
&#xD;
Cal tenir en compte que al model de referència d'openEHR hi ha un atribut de 'Temps', l'objectiu del qual és registrar la data i l'hora en què es va realitzar cada fase del procés de l'Acció. Aquest és l'atribut que s'utilitzarà per registrar l'inici del procediment (usant la fase 'Procediment realitzat') o el moment en què es va avortar el procediment (usant la fase 'Procediment avortat').</use>
      <misuse>No s'ha de fer servir per registrar detalls sobre l'anestèsia; per fer-ho, utilitzar un arquetip ACTION diferent.&#xD;
&#xD;
No s'ha de fer servir per registrar detalls sobre estudis per imatge; per fer-ho, utilitzar l'arquetip ACTION.imaging_exam.&#xD;
&#xD;
No s'ha de fer servir per registrar detalls sobre estudis de laboratori; per fer-ho, utilitzar l'arquetip ACTION.laboratory_test.&#xD;
&#xD;
No s'ha de fer servir per registrar dades sobre l'educació impartida; per fer-ho, utilitzar l'arquetip ACTION.health_education.&#xD;
&#xD;
No s'ha de fer servir per registrar detalls sobre activitats administratives; per això, utilitzar arquetips ADMIN específics.&#xD;
&#xD;
No s'ha de fer servir per registrar detalls sobre activitats relacionades, com l'ús de seccions congelades preses durant una operació, medicació administrada durant el procediment o en fer ús de la guia per imatge durant el procediment; per això, utilitzar arquetips ACTION per separat i específics dins de la mateixa plantilla.&#xD;
&#xD;
No s'ha de fer servir per registrar un informe d'operació o procediment complet: utilitzar una plantilla on aquest arquetip sigui només un component de l'informe complet.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Kim Sommer, Natalia Strauch, Alina Rehberg</author>
    <author id="organisation">MHH, Medizinische Hochschule Hannover</author>
    <author id="email">sommer.kimkatrin@mh-hannover.de, Strauch.Natalia@mh-hannover.de, rehberg.alina@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-pt</code_string>
    </language>
    <author id="name">Ana Garcia Niza</author>
    <author id="organisation">EY</author>
    <author id="email">ana.niza16@gmail.com</author>
    <accreditation>I have no accreditation</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ru</code_string>
    </language>
    <author id="name">Art Latyp; Латыпов Артур</author>
    <author id="organisation">RusBITech; РусБИТех, Москва</author>
    <accreditation>hmm</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Sofia Lång Janstad, Romi Shweta Pathak, Anette Larsson, Åsa Skagerhult, Per Nemirovski, Anders Thurin, Jörgen Kuylenstierna, Emma Molin, Henrik Nilsson, Sajjad Saffari Miandoab, Mikael Nyström</author>
    <author id="organisation">SLL, Karolinska universitetssjukhuset, Tieto Sweden AB, openEHR Sverige, Region Östergötland, B3 HealthTech, Västra Götalandsregionen, Region Uppsala, Cambio, Eweave, CAG</author>
    <author id="email">sofia.lang-janstad@sll.se, romi.pathak@regionstockholm.se, anette.a.larsson@tietoevry.com, asa.skagerhult@regionostergotland.se, per.nemirovski@b3.se, sajjad.saffari-miandoab@regionstockholm.se, jorgen.kuylenstierna@solvikshalsan.se, emma.molin@cambio.se, anders.thurin@vgregion.se, Henrik.Nilsson@cag.se, Mikael.Nystrom@cambio.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">John Tore Valand / Silje Ljosland Bakke</author>
    <author id="organisation">Helse Vest IKT AS</author>
    <author id="email">john.tore.valand@helse-vest-ikt.no, silje.ljosland.bakke@helse-vest-ikt.no</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-br</code_string>
    </language>
    <author id="name">Osmeire Chamelette Sanzovo</author>
    <author id="organisation">Hospital Sírio Libanês</author>
    <author id="email">osmeire.acsanzovo@hsl.org.br</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ar-sy</code_string>
    </language>
    <author id="name">Mona Saleh</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sl</code_string>
    </language>
    <author id="name">Uroš Rajkovič, Biljana Prinčič</author>
    <author id="organisation">Slovenia</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>zh-cn</code_string>
    </language>
    <author id="name">Lin Zhang</author>
    <author id="organisation">Freelancer</author>
    <author id="email">linforest@163.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es</code_string>
    </language>
    <author id="name">Pablo Pazos, Julio de Sosa</author>
    <author id="organisation">CaboLabs, Servei Català de la Salut</author>
    <author id="pablo.pazos@cabolabs.com">pablo.pazos@cabolabs.com</author>
    <author id="email">pablo.pazos@cabolabs.com, juliodesosa@catsalut.cat</author>
    <accreditation>Computer Engineer</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ca</code_string>
    </language>
    <author id="name">Julio de Sosa</author>
    <author id="organisation">Servei Català de la Salut</author>
    <author id="email">juliodesosa@catsalut.cat</author>
  </translations>
  <uid>
    <value>a8585fcc-28d7-4902-aa42-31d1c01f7213</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-ACTION.procedure.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>ACTION</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>ism_transition</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>ISM_TRANSITION</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>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>526</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0004</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0034</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>524</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0034</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>526</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0007</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0035</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>524</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0035</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0038</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>527</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0038</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0039</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>528</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0039</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0036</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>529</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0036</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0068</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>245</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0068</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0047</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>245</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0047</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0040</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>530</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0040</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0041</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>531</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0041</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0043</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</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>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>openehr</value>
                </terminology_id>
                <code_list>532</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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>at0043</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
    </attributes>
    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
      <rm_attribute_name>description</rm_attribute_name>
      <existence>
        <lower_included>true</lower_included>
        <upper_included>true</upper_included>
        <lower_unbounded>false</lower_unbounded>
        <upper_unbounded>false</upper_unbounded>
        <lower>1</lower>
        <upper>1</upper>
      </existence>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ITEM_TREE</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>1</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0001</node_id>
        <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
          <rm_attribute_name>items</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0002</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0049</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>at0070</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>at0072</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>at0065</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>at0058</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>at0063</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="ARCHETYPE_SLOT">
            <rm_type_name>CLUSTER</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </occurrences>
            <node_id>at0003</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_circle(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v2/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_circle(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v2</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </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>at0071</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>at0048</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>at0069</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>at0006</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>at0066</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DATE_TIME</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0073</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DATE_TIME</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0060</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DATE_TIME</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0061</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DURATION</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>value</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_PRIMITIVE_OBJECT">
                    <rm_type_name>DV_DURATION</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_DURATION">
                      <range>
                        <lower_included>true</lower_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>true</upper_unbounded>
                        <lower>PT0S</lower>
                      </range>
                    </item>
                  </children>
                </attributes>
              </children>
            </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>at0074</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DURATION</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="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>at0062</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.media_file\.v1/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.media_file\.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>at0067</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>at0014</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_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>
    </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>at0053</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>at0054</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_IDENTIFIER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="ARCHETYPE_SLOT">
            <rm_type_name>CLUSTER</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0055</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/.*/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>.*</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0056</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_IDENTIFIER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </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>at0057</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/.*/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>.*</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="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>at0064</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="pt-br">
      <items code="at0000">
        <items id="text">Procedimento</items>
        <items id="description">A atividade clínica realizada para rastreamento , investigação , diagnóstico , cura , terapêutica, avaliação ou finalidade paliativos.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Nome do procedimento</items>
        <items id="description">Identificação do procedimento pelo nome.</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">Detalhes do Procedimento</items>
        <items id="description">São as informações estruturadas sobre o procedimento.</items>
        <items id="comment">Use para capturar informações detalhadas , estruturadas sobre a localização anatômica , método e técnica , os equipamentos utilizados , dispositivos implantados , os resultados , as conclusões, etc.</items>
      </items>
      <items code="at0004">
        <items id="text">*Procedure planned (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0005">
        <items id="text">Comentários</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">Complicações</items>
        <items id="description">Detalhes sobre alguma complicação decorrente do procedimento</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">*Procedure request sent (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0014">
        <items id="text">Justificativa</items>
        <items id="description">Razão pela qual a atividade ou cuidado foi identificada para que o procedimento fosse realizado.</items>
        <items id="comment">Por exemplo: o motivo do cancelamento ou suspensão de um procedimento.</items>
      </items>
      <items code="at0034">
        <items id="text">Plano de procedimento</items>
        <items id="description">O procedimento a ser realizado é planejado</items>
      </items>
      <items code="at0035">
        <items id="text">Procedimento pedido enviado</items>
        <items id="description">Pedido de procedimento enviado.</items>
      </items>
      <items code="at0036">
        <items id="text">Procedimento agendado</items>
        <items id="description">O procedimento foi agendado.</items>
      </items>
      <items code="at0038">
        <items id="text">Procedimento adiado</items>
        <items id="description">O procedimento foi adiado.</items>
      </items>
      <items code="at0039">
        <items id="text">Procedimento cancelado</items>
        <items id="description">O procedimento planejado foi cancelado antes do início.</items>
      </items>
      <items code="at0040">
        <items id="text">Procedimento suspenso</items>
        <items id="description">O procedimento foi suspenso.</items>
      </items>
      <items code="at0041">
        <items id="text">Procedimento abortado</items>
        <items id="description">O procedimento foi abortado.</items>
      </items>
      <items code="at0043">
        <items id="text">Procedimento concluído</items>
        <items id="description">O procedimento foi realizado e todas as atividades clínicas associadas concluídas.</items>
      </items>
      <items code="at0047">
        <items id="text">Procedimento realizado</items>
        <items id="description">O procedimento, ou procedimento secundário no caso de procedimentos sequenciado, foi realizado.</items>
      </items>
      <items code="at0048">
        <items id="text">Resultado</items>
        <items id="description">Resultado do procedimento realizado.</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o procedimento, conforme apropriado para a etapa.</items>
        <items id="comment">Por exemplo : Descrição sobre o desempenho e os resultados do procedimento, a tentativa abortada ou a anulação do procedimento.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree(en)</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Identificador do pedido do solicitante</items>
        <items id="description">O ID local atribuído ao pedido realizado pelo profissional de saúde ou organização solicitando o serviço.</items>
        <items id="comment">Isto é equivalente ao "Placer Order Number" nas especificações do HL7 v2.</items>
      </items>
      <items code="at0055">
        <items id="text">Solicitante</items>
        <items id="description">Detalhes sobre o profissional ou organização de saúde que solicitou o serviço.</items>
      </items>
      <items code="at0056">
        <items id="text">Identificador do pedido do destinatário</items>
        <items id="description">O ID atribuído ao pedido pelo provedor de cuidados de saúde ou organização que recebe o pedido de serviço. Isto é também relacionado ao preenchimento da identificação do pedido.</items>
        <items id="comment">Isto é equivalente ao "Placer Order Number" nas especificações do HL7 v2.</items>
      </items>
      <items code="at0057">
        <items id="text">Destinatário</items>
        <items id="description">Detalhes sobre o profissional ou organização de saúde que recebeu o requerimento para o serviço.</items>
      </items>
      <items code="at0058">
        <items id="text">Urgência</items>
        <items id="description">Urgência do procedimento.</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">Apenas para utilização em associação com o "Procedimento realizado" da etapa, e em situações em que o procedimento é repetido em várias ocasiões antes de ser concluído ou houver vários componentes para todo o processo. Este pode ser o mesmo que o atributo para o tempo de RM "Processo concluído".</items>
      </items>
      <items code="at0061">
        <items id="text">Duração Total</items>
        <items id="description">A quantidade total de tempo necessária para concluir o procedimento, o que pode incluir o tempo gasto durante a fase ativa do procedimento mais o tempo durante o qual o procedimento foi suspenso.</items>
        <items id="comment">Apenas para utilização em associação com o "Procedimento concluído".</items>
      </items>
      <items code="at0062">
        <items id="text">Multimidia</items>
        <items id="description">Representação multimídia de um procedimento realizado.</items>
      </items>
      <items code="at0063">
        <items id="text">Localização no corpo</items>
        <items id="description">Identificação do local no corpo onde será realizado o procedimento.</items>
        <items id="comment">Ocorrências para este elemento de dados são ilimitadas para permitir cenários clínicos, tais como a remoção de lesões da pele em múltiplos locais diferentes , mas em que todos os outros atributos são idênticos . Utilize este elemento de dados para gravar termos simples ou localizações anatômicas padrão. Se as condições de gravação da localização anatômica são determinados em tempo de execução pelo aplicativo ou exigir modelagem mais complexa, como localizações relativas , em seguida, usar o CLUSTER.anatomical_location ou CLUSTER.relative_location dentro do campo "detalhes do procedimento" neste arquétipo. Se a localização anatômica estiver incluída no "Nome do procedimento" através de códigos padronizados, este elemento de dados torna-se redundante.</items>
      </items>
      <items code="at0064">
        <items id="text">Extensão</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="at0065">
        <items id="text">Método</items>
        <items id="description">Identificação do método específico ou técnica do procedimento.</items>
        <items id="comment">Utilize este elemento de dados para registrar termos simples ou uma descrição narrativa . Se as condições de registro do método requer uma modelagem mais complexa , então isso pode ser representado por arquétipos adicionais dentro do campo "Detalhes do procedimento" deste arquétipo. Se o método está incluído no "Nome do procedimento" através de códigos padrão , este elemento de dados torna-se redundante.</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">Apenas para utilização em associação com o " Procedimento Programado ' para a etapa em curso.</items>
      </items>
      <items code="at0067">
        <items id="text">Tipo do procedimento</items>
        <items id="description">O tipo do procedimento.</items>
        <items id="comment">Esse elemento de dados pragmático pode ser usado para apoiar a organização dentro da interface do usuário.</items>
      </items>
      <items code="at0068">
        <items id="text">Procedimento Iniciou</items>
        <items id="description">O procedimento, ou procedimento secundário, no caso de procedimentos sequenciados, foi iniciado.</items>
      </items>
      <items code="at0069">
        <items id="text">*Procedural difficulty(en)</items>
        <items id="description">*Difficulties or issues encountered during the procedure.(en)</items>
      </items>
      <items code="at0070">
        <items id="text">*Indication (en)</items>
        <items id="description">*The clinical or process-related reason for the procedure. (en)</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">*DV_TEXT (en)</items>
        <items id="description" />
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="sl">
      <items code="at0000">
        <items id="text">*Procedure(en)</items>
        <items id="description">*A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0002">
        <items id="text">*Procedure name(en)</items>
        <items id="description">*Identification of the procedure by name.(en)</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">*Procedure detail(en)</items>
        <items id="description">*Structured information about the procedure. Use to capture detailed, structured information about anatomical location, method &amp; technique, equipment used, devices implanted, results, findings etc.(en)</items>
      </items>
      <items code="at0004">
        <items id="text">*Procedure planned (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0005">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">*Complication(en)</items>
        <items id="description">*Details about any complication arising from the procedure.(en)</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">*Procedure request sent (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0014">
        <items id="text">*Reason(en)</items>
        <items id="description">*Reason that the activity or care pathway step for the identified procedure was carried out.(en)</items>
        <items id="comment">*For example: the reason for the cancellation or suspension of the procedure.(en)</items>
      </items>
      <items code="at0034">
        <items id="text">*Procedure planned(en)</items>
        <items id="description">*The procedure to be undertaken is planned.(en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Procedure request sent(en)</items>
        <items id="description">*Request for procedure sent.(en)</items>
      </items>
      <items code="at0036">
        <items id="text">*Procedure scheduled(en)</items>
        <items id="description">*The procedure has been scheduled.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Procedure postponed(en)</items>
        <items id="description">*The procedure has been postponed.(en)</items>
      </items>
      <items code="at0039">
        <items id="text">*Procedure cancelled(en)</items>
        <items id="description">*The planned procedure has been cancelled prior to commencement.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Procedure suspended(en)</items>
        <items id="description">*The procedure has been suspended.(en)</items>
      </items>
      <items code="at0041">
        <items id="text">*Procedure aborted(en)</items>
        <items id="description">*The procedure has been aborted.(en)</items>
      </items>
      <items code="at0043">
        <items id="text">*Procedure completed(en)</items>
        <items id="description">*The procedure has been performed and all associated clinical activities completed.(en)</items>
      </items>
      <items code="at0047">
        <items id="text">*Procedure performed(en)</items>
        <items id="description">*The procedure, or subprocedure in a multicomponent procedure, has been performed.(en)</items>
      </items>
      <items code="at0048">
        <items id="text">*Outcome(en)</items>
        <items id="description">*Outcome of procedure performed.(en)</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the procedure, as appropriate for the pathway step.(en)</items>
        <items id="comment">*For example: description about the performance and findings from the the procedure, the aborted attempt or the cancellation of the procedure.(en)</items>
      </items>
      <items code="at0053">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0054">
        <items id="text">*Requestor order identifier(en)</items>
        <items id="description">*The local ID assigned to the order by the healthcare provider or organisation requesting the service.(en)</items>
        <items id="comment">*This is equivalent to Placer Order Number in HL7 v2 specifications.(en)</items>
      </items>
      <items code="at0055">
        <items id="text">Naročnik</items>
        <items id="description">Kdo je naročil aktivnost, posameznik ali organizacija</items>
      </items>
      <items code="at0056">
        <items id="text">*Receiver order identifier(en)</items>
        <items id="description">*The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.(en)</items>
        <items id="comment">*This is equivalent to Filler Order Number in HL7 v2 specifications.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">Prejemnik</items>
        <items id="description">Prejemnik naročila za izvedbo aktivnosti</items>
      </items>
      <items code="at0058">
        <items id="text">*Urgency(en)</items>
        <items id="description">*Urgency of the procedure.(en)</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">*Only for use in association with the 'Procedure performed' pathway step, and in situations where the procedure is repeated on multiple occasions before being completed or there are multiple components to the whole procedure. This may be the same as the RM time attribute for the 'Procedure completed' pathway step.(en)</items>
      </items>
      <items code="at0061">
        <items id="text">*Total duration(en)</items>
        <items id="description">*The total amount of time taken to complete the procedure, which may include time spent during the active phase of the procedure plus time during which the procedure was suspended.(en)</items>
        <items id="comment">*Only for use in association with the 'Procedure completed' pathway steps.(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Multimedia(en)</items>
        <items id="description">*Mulitimedia representation of a performed procedure.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Body site(en)</items>
        <items id="description">*Identification of the body site for the procedure.(en)</items>
        <items id="comment">*Occurrences for this data element are unbounded to allow for clinical scenarios such as removing multiple skin lesions in different places, but where all of the other attributes are identical. Use this data element to record simple terms or precoordinated anatomical locations. If the requirements for recording the anatomical location are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the 'Procedure detail' SLOT in this archetype. If the anatomical location is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.(en)</items>
      </items>
      <items code="at0064">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to extend the model with local content or to align with other reference models or formalisms. (en)</items>
        <items id="comment">*For example: local information requirements; or additional metadata to align with FHIR. (en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Method(en)</items>
        <items id="description">*Identification of specific method or technique for the procedure.(en)</items>
        <items id="comment">*Use this data element to record simple terms or a narrative description. If the requirements for recording the method require more complex modelling then this can be represented by additional archetypes within the 'Procedure detail' SLOT in this archetype. If the method is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.(en)</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">*Only for use in association with the 'Procedure scheduled' pathway step.(en)</items>
      </items>
      <items code="at0067">
        <items id="text">*Procedure type(en)</items>
        <items id="description">*The type of procedure.(en)</items>
        <items id="comment">*This pragmatic data element may be used to support organisation within the user interface.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Procedure commenced(en)</items>
        <items id="description">*The procedure, or subprocedure in a multicomponent procedure, has been commenced.(en)</items>
      </items>
      <items code="at0069">
        <items id="text">*Procedural difficulty(en)</items>
        <items id="description">*Difficulties or issues encountered during the procedure.(en)</items>
      </items>
      <items code="at0070">
        <items id="text">*Indication (en)</items>
        <items id="description">*The clinical or process-related reason for the procedure. (en)</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">Impact</items>
        <items id="description">Overall assessment of the impact of a health problem for the specific patient.</items>
        <items id="comment">The same diagnosis, with the same severity, has a different impact on each patient. This relevance qualifier implies adjusting the overall impact of that health problem according to the patient's characteristics.&#xD;
For example: Two patients have the same diagnosis. First-degree burn.&#xD;
One is a healthy person, the other is a diabetic patient.&#xD;
The impact for that problem in a diabetic patient is HIGHER (more risk of infection..., longuer time healing).&#xD;
This element is meant to allow for multiple types of impact, including but not limited to: clinical treatment, home functioning, work life.</items>
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Procedure</items>
        <items id="description">A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Procedure name</items>
        <items id="description">Identification of the procedure by name.</items>
        <items id="comment">Coding of the 'Procedure name' with a terminology is recommended, if available.</items>
      </items>
      <items code="at0003">
        <items id="text">Procedure detail</items>
        <items id="description">Structured information about the procedure.</items>
        <items id="comment">Use to capture detailed, structured information about anatomical location, method &amp; technique, equipment used, devices implanted, results, findings etc.</items>
      </items>
      <items code="at0004">
        <items id="text">Procedure planned</items>
        <items id="description">The procedure to be undertaken is planned.</items>
      </items>
      <items code="at0005">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the procedure or care pathway step not captured in other fields.</items>
      </items>
      <items code="at0006">
        <items id="text">Complication</items>
        <items id="description">Details about any complication arising from the procedure.</items>
        <items id="comment">Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant.</items>
      </items>
      <items code="at0007">
        <items id="text">Procedure request sent</items>
        <items id="description">Request for procedure sent.</items>
      </items>
      <items code="at0014">
        <items id="text">Reason</items>
        <items id="description">Reason that the activity or care pathway step for the identified procedure was carried out.</items>
        <items id="comment">For example: the reason for the cancellation or suspension of the procedure.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Procedure planned</items>
        <items id="description">This pathway step has been deprecated as it was incorrectly associated with 'initial' status - use the new 'Procedure planned' (at0004) pathway step  which is correctly associated with 'planned' status.</items>
        <items id="comment">(Was: The procedure to be undertaken is planned.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Procedure request sent</items>
        <items id="description">This pathway step has been deprecated as it was incorrectly associated with 'initial' status - use the new 'Procedure request sent' (at0007) pathway step  which is correctly associated with 'planned' status.</items>
        <items id="comment">(Was: Request for procedure sent.)</items>
      </items>
      <items code="at0036">
        <items id="text">Procedure scheduled</items>
        <items id="description">The procedure has been scheduled.</items>
      </items>
      <items code="at0038">
        <items id="text">Procedure postponed</items>
        <items id="description">The procedure has been postponed.</items>
      </items>
      <items code="at0039">
        <items id="text">Procedure cancelled</items>
        <items id="description">The planned procedure has been cancelled prior to commencement.</items>
      </items>
      <items code="at0040">
        <items id="text">Procedure suspended</items>
        <items id="description">The procedure has been suspended.</items>
      </items>
      <items code="at0041">
        <items id="text">Procedure aborted</items>
        <items id="description">The procedure has been aborted.</items>
      </items>
      <items code="at0043">
        <items id="text">Procedure completed</items>
        <items id="description">The procedure has been performed and all associated clinical activities completed.</items>
      </items>
      <items code="at0047">
        <items id="text">Procedure performed</items>
        <items id="description">The procedure, or subprocedure in a multicomponent procedure, has been performed.</items>
      </items>
      <items code="at0048">
        <items id="text">Outcome</items>
        <items id="description">Outcome of procedure performed.</items>
        <items id="comment">Coding of the 'Outcome' with a terminology is recommended, if available.</items>
      </items>
      <items code="at0049">
        <items id="text">Description</items>
        <items id="description">Narrative description about the procedure, as appropriate for the pathway step.</items>
        <items id="comment">For example: description about the performance and findings from the the procedure, the aborted attempt or the cancellation of the procedure.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Requestor order identifier</items>
        <items id="description">The local ID assigned to the order by the healthcare provider or organisation requesting the service.</items>
        <items id="comment">This is equivalent to Placer Order Number in HL7 v2 specifications.</items>
      </items>
      <items code="at0055">
        <items id="text">Requestor</items>
        <items id="description">Details about the healthcare provider or organisation requesting the service.</items>
      </items>
      <items code="at0056">
        <items id="text">Receiver order identifier</items>
        <items id="description">The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.</items>
        <items id="comment">This is equivalent to Filler Order Number in HL7 v2 specifications.</items>
      </items>
      <items code="at0057">
        <items id="text">Receiver</items>
        <items id="description">Details about the healthcare provider or organisation receiving the request for service.</items>
      </items>
      <items code="at0058">
        <items id="text">Urgency</items>
        <items id="description">Urgency of the procedure.</items>
        <items id="comment">Coding of the 'Urgency' with a terminology is recommended, if available.</items>
      </items>
      <items code="at0060">
        <items id="text">End datetime</items>
        <items id="description">The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished.</items>
        <items id="comment">Only for use in association with the 'Procedure performed' pathway step, and in situations where the procedure is repeated on multiple occasions before being completed or there are multiple components to the whole procedure. This may be the same as the RM time attribute for the 'Procedure completed' pathway step.</items>
      </items>
      <items code="at0061">
        <items id="text">Total duration</items>
        <items id="description">The total amount of time taken to complete the procedure, which may include time spent during the active phase of the procedure plus time during which the procedure was suspended.</items>
        <items id="comment">Only for use in association with the 'Procedure completed' pathway steps.</items>
      </items>
      <items code="at0062">
        <items id="text">Multimedia</items>
        <items id="description">Mulitimedia representation of a performed procedure.</items>
      </items>
      <items code="at0063">
        <items id="text">Body site</items>
        <items id="description">Identification of the body site for the procedure.</items>
        <items id="comment">Occurrences for this data element are unbounded to allow for clinical scenarios such as removing multiple skin lesions in different places, but where all of the other attributes are identical. Use this data element to record simple terms or precoordinated anatomical locations. If the requirements for recording the anatomical location are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the 'Procedure detail' SLOT in this archetype. If the anatomical location is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.</items>
      </items>
      <items code="at0064">
        <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="at0065">
        <items id="text">Method</items>
        <items id="description">Identification of specific method or technique for the procedure.</items>
        <items id="comment">Use this data element to record simple terms or a narrative description. If the requirements for recording the method require more complex modelling then this can be represented by additional archetypes within the 'Procedure detail' SLOT in this archetype. If the method is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.</items>
      </items>
      <items code="at0066">
        <items id="text">Scheduled datetime</items>
        <items id="description">The date or datetime on which the procedure is intended to be performed.</items>
        <items id="comment">Only for use in association with the 'Procedure scheduled' pathway step.</items>
      </items>
      <items code="at0067">
        <items id="text">Procedure type</items>
        <items id="description">The type of procedure.</items>
        <items id="comment">This pragmatic data element may be used to support organisation within the user interface.</items>
      </items>
      <items code="at0068">
        <items id="text">Procedure commenced</items>
        <items id="description">The procedure, or subprocedure in a multicomponent procedure, has been commenced.</items>
      </items>
      <items code="at0069">
        <items id="text">Procedural difficulty</items>
        <items id="description">Difficulties or issues encountered during performance of the procedure.</items>
        <items id="comment">Examples: The patient was agitated, insufficient emptying of the stomach before gastroscopy, a tumour in the bile ducts made it impossible to pass the scope through.</items>
      </items>
      <items code="at0070">
        <items id="text">Indication</items>
        <items id="description">The clinical or process-related reason for the procedure.</items>
        <items id="comment">For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required.</items>
      </items>
      <items code="at0071">
        <items id="text">Impact</items>
        <items id="description">Assessment of the impact of a procedure or its outcome for a specific patient.</items>
        <items id="comment">The same procedure, with the same severity or outcome, can have a different impact on each patient. This relevance factor involves adjusting the overall impact of that procedure or outcome according to the patient's characteristics.&#xD;
&#xD;
For example: Two patients have undergone the same procedure with the same outcome: osteosynthesis repair of the fifth finger of their non-dominant hand.&#xD;
&#xD;
One is a gardener or construction worker; the other, a pianist.&#xD;
&#xD;
The impact of that procedure on the pianist is GREATER (longer sick leave, need for full functional rehabilitation to adapt to the high fine motor demands of work).&#xD;
&#xD;
This element is intended to allow for multiple types of impact, including but not limited to: clinical treatment, home functioning, or work life.</items>
      </items>
      <items code="at0072">
        <items id="text">Intent</items>
        <items id="description">The intended outcome of the procedure.</items>
        <items id="comment">For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required.</items>
      </items>
      <items code="at0073">
        <items id="text">Start datetime</items>
        <items id="description">The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started.</items>
        <items id="comment">For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step.</items>
      </items>
      <items code="at0074">
        <items id="text">Pathway step duration</items>
        <items id="description">The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step.</items>
      </items>
    </term_definitions>
    <term_definitions language="ar-sy">
      <items code="at0000">
        <items id="text">*Procedure(en)</items>
        <items id="description">*A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">*Procedure name(en)</items>
        <items id="description">*Identification of the procedure by name.(en)</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">*Procedure detail(en)</items>
        <items id="description">*Structured information about the procedure. Use to capture detailed, structured information about anatomical location, method &amp; technique, equipment used, devices implanted, results, findings etc.(en)</items>
      </items>
      <items code="at0004">
        <items id="text">*Procedure planned (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0005">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">*Complication(en)</items>
        <items id="description">*Details about any complication arising from the procedure.(en)</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">*Procedure request sent (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0014">
        <items id="text">*Reason(en)</items>
        <items id="description">*Reason that the activity or care pathway step for the identified procedure was carried out.(en)</items>
        <items id="comment">*For example: the reason for the cancellation or suspension of the procedure.(en)</items>
      </items>
      <items code="at0034">
        <items id="text">*Procedure planned(en)</items>
        <items id="description">*The procedure to be undertaken is planned.(en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Procedure request sent(en)</items>
        <items id="description">*Request for procedure sent.(en)</items>
      </items>
      <items code="at0036">
        <items id="text">*Procedure scheduled(en)</items>
        <items id="description">*The procedure has been scheduled.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Procedure postponed(en)</items>
        <items id="description">*The procedure has been postponed.(en)</items>
      </items>
      <items code="at0039">
        <items id="text">*Procedure cancelled(en)</items>
        <items id="description">*The planned procedure has been cancelled prior to commencement.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Procedure suspended(en)</items>
        <items id="description">*The procedure has been suspended.(en)</items>
      </items>
      <items code="at0041">
        <items id="text">*Procedure aborted(en)</items>
        <items id="description">*The procedure has been aborted.(en)</items>
      </items>
      <items code="at0043">
        <items id="text">*Procedure completed(en)</items>
        <items id="description">*The procedure has been performed and all associated clinical activities completed.(en)</items>
      </items>
      <items code="at0047">
        <items id="text">*Procedure performed(en)</items>
        <items id="description">*The procedure, or subprocedure in a multicomponent procedure, has been performed.(en)</items>
      </items>
      <items code="at0048">
        <items id="text">*Outcome(en)</items>
        <items id="description">*Outcome of procedure performed.(en)</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the procedure, as appropriate for the pathway step.(en)</items>
        <items id="comment">*For example: description about the performance and findings from the the procedure, the aborted attempt or the cancellation of the procedure.(en)</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">*Requestor order identifier(en)</items>
        <items id="description">*The local ID assigned to the order by the healthcare provider or organisation requesting the service.(en)</items>
        <items id="comment">*This is equivalent to Placer Order Number in HL7 v2 specifications.(en)</items>
      </items>
      <items code="at0055">
        <items id="text">الطالب</items>
        <items id="description">تفاصيل حول مقدم الخدمة الصحية أو المؤسسة التي تطلب الخدمة</items>
      </items>
      <items code="at0056">
        <items id="text">*Receiver order identifier(en)</items>
        <items id="description">*The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.(en)</items>
        <items id="comment">*This is equivalent to Filler Order Number in HL7 v2 specifications.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">المستقبِل</items>
        <items id="description">تفاصيل حول مقدم الخدمة الصحية أو المؤسسة التي تستقبل طلب الخدمة.</items>
      </items>
      <items code="at0058">
        <items id="text">*Urgency(en)</items>
        <items id="description">*Urgency of the procedure.(en)</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">*Only for use in association with the 'Procedure performed' pathway step, and in situations where the procedure is repeated on multiple occasions before being completed or there are multiple components to the whole procedure. This may be the same as the RM time attribute for the 'Procedure completed' pathway step.(en)</items>
      </items>
      <items code="at0061">
        <items id="text">*Total duration(en)</items>
        <items id="description">*The total amount of time taken to complete the procedure, which may include time spent during the active phase of the procedure plus time during which the procedure was suspended.(en)</items>
        <items id="comment">*Only for use in association with the 'Procedure completed' pathway steps.(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Multimedia(en)</items>
        <items id="description">*Mulitimedia representation of a performed procedure.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Body site(en)</items>
        <items id="description">*Identification of the body site for the procedure.(en)</items>
        <items id="comment">*Occurrences for this data element are unbounded to allow for clinical scenarios such as removing multiple skin lesions in different places, but where all of the other attributes are identical. Use this data element to record simple terms or precoordinated anatomical locations. If the requirements for recording the anatomical location are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the 'Procedure detail' SLOT in this archetype. If the anatomical location is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.(en)</items>
      </items>
      <items code="at0064">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to extend the model with local content or to align with other reference models or formalisms. (en)</items>
        <items id="comment">*For example: local information requirements; or additional metadata to align with FHIR. (en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Method(en)</items>
        <items id="description">*Identification of specific method or technique for the procedure.(en)</items>
        <items id="comment">*Use this data element to record simple terms or a narrative description. If the requirements for recording the method require more complex modelling then this can be represented by additional archetypes within the 'Procedure detail' SLOT in this archetype. If the method is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.(en)</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">*Only for use in association with the 'Procedure scheduled' pathway step.(en)</items>
      </items>
      <items code="at0067">
        <items id="text">*Procedure type(en)</items>
        <items id="description">*The type of procedure.(en)</items>
        <items id="comment">*This pragmatic data element may be used to support organisation within the user interface.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Procedure commenced(en)</items>
        <items id="description">*The procedure, or subprocedure in a multicomponent procedure, has been commenced.(en)</items>
      </items>
      <items code="at0069">
        <items id="text">*Procedural difficulty(en)</items>
        <items id="description">*Difficulties or issues encountered during the procedure.(en)</items>
      </items>
      <items code="at0070">
        <items id="text">*Indication (en)</items>
        <items id="description">*The clinical or process-related reason for the procedure. (en)</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">*DV_TEXT (en)</items>
        <items id="description" />
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="ru">
      <items code="at0000">
        <items id="text">*Procedure(en)</items>
        <items id="description">*A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0002">
        <items id="text">*Procedure name(en)</items>
        <items id="description">*Identification of the procedure by name.(en)</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">*Procedure detail(en)</items>
        <items id="description">*Structured information about the procedure. Use to capture detailed, structured information about anatomical location, method &amp; technique, equipment used, devices implanted, results, findings etc.(en)</items>
      </items>
      <items code="at0004">
        <items id="text">*Procedure planned (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0005">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">*Complication(en)</items>
        <items id="description">*Details about any complication arising from the procedure.(en)</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">*Procedure request sent (en)</items>
        <items id="description">*</items>
      </items>
      <items code="at0014">
        <items id="text">*Reason(en)</items>
        <items id="description">*Reason that the activity or care pathway step for the identified procedure was carried out.(en)</items>
        <items id="comment">*For example: the reason for the cancellation or suspension of the procedure.(en)</items>
      </items>
      <items code="at0034">
        <items id="text">*Procedure planned(en)</items>
        <items id="description">*The procedure to be undertaken is planned.(en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Procedure request sent(en)</items>
        <items id="description">*Request for procedure sent.(en)</items>
      </items>
      <items code="at0036">
        <items id="text">*Procedure scheduled(en)</items>
        <items id="description">*The procedure has been scheduled.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Procedure postponed(en)</items>
        <items id="description">*The procedure has been postponed.(en)</items>
      </items>
      <items code="at0039">
        <items id="text">*Procedure cancelled(en)</items>
        <items id="description">*The planned procedure has been cancelled prior to commencement.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Procedure suspended(en)</items>
        <items id="description">*The procedure has been suspended.(en)</items>
      </items>
      <items code="at0041">
        <items id="text">*Procedure aborted(en)</items>
        <items id="description">*The procedure has been aborted.(en)</items>
      </items>
      <items code="at0043">
        <items id="text">*Procedure completed(en)</items>
        <items id="description">*The procedure has been performed and all associated clinical activities completed.(en)</items>
      </items>
      <items code="at0047">
        <items id="text">*Procedure performed(en)</items>
        <items id="description">*The procedure, or subprocedure in a multicomponent procedure, has been performed.(en)</items>
      </items>
      <items code="at0048">
        <items id="text">*Outcome(en)</items>
        <items id="description">*Outcome of procedure performed.(en)</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">*Description(en)</items>
        <items id="description">*Narrative description about the procedure, as appropriate for the pathway step.(en)</items>
        <items id="comment">*For example: description about the performance and findings from the the procedure, the aborted attempt or the cancellation of the procedure.(en)</items>
      </items>
      <items code="at0053">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0054">
        <items id="text">*Requestor order identifier(en)</items>
        <items id="description">*The local ID assigned to the order by the healthcare provider or organisation requesting the service.(en)</items>
        <items id="comment">*This is equivalent to Placer Order Number in HL7 v2 specifications.(en)</items>
      </items>
      <items code="at0055">
        <items id="text">Заказчик</items>
        <items id="description">Подробности о заказчике (организации), запросившей услугу</items>
      </items>
      <items code="at0056">
        <items id="text">*Receiver order identifier(en)</items>
        <items id="description">*The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.(en)</items>
        <items id="comment">*This is equivalent to Filler Order Number in HL7 v2 specifications.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">Исполнитель</items>
        <items id="description">Подробные сведение об организации, получившей заявку на выполнение процедуры</items>
      </items>
      <items code="at0058">
        <items id="text">*Urgency(en)</items>
        <items id="description">*Urgency of the procedure.(en)</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">*Only for use in association with the 'Procedure performed' pathway step, and in situations where the procedure is repeated on multiple occasions before being completed or there are multiple components to the whole procedure. This may be the same as the RM time attribute for the 'Procedure completed' pathway step.(en)</items>
      </items>
      <items code="at0061">
        <items id="text">*Total duration(en)</items>
        <items id="description">*The total amount of time taken to complete the procedure, which may include time spent during the active phase of the procedure plus time during which the procedure was suspended.(en)</items>
        <items id="comment">*Only for use in association with the 'Procedure completed' pathway steps.(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Multimedia(en)</items>
        <items id="description">*Mulitimedia representation of a performed procedure.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Body site(en)</items>
        <items id="description">*Identification of the body site for the procedure.(en)</items>
        <items id="comment">*Occurrences for this data element are unbounded to allow for clinical scenarios such as removing multiple skin lesions in different places, but where all of the other attributes are identical. Use this data element to record simple terms or precoordinated anatomical locations. If the requirements for recording the anatomical location are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the 'Procedure detail' SLOT in this archetype. If the anatomical location is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.(en)</items>
      </items>
      <items code="at0064">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to extend the model with local content or to align with other reference models or formalisms. (en)</items>
        <items id="comment">*For example: local information requirements; or additional metadata to align with FHIR. (en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Method(en)</items>
        <items id="description">*Identification of specific method or technique for the procedure.(en)</items>
        <items id="comment">*Use this data element to record simple terms or a narrative description. If the requirements for recording the method require more complex modelling then this can be represented by additional archetypes within the 'Procedure detail' SLOT in this archetype. If the method is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant.(en)</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">*Only for use in association with the 'Procedure scheduled' pathway step.(en)</items>
      </items>
      <items code="at0067">
        <items id="text">*Procedure type(en)</items>
        <items id="description">*The type of procedure.(en)</items>
        <items id="comment">*This pragmatic data element may be used to support organisation within the user interface.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Procedure commenced(en)</items>
        <items id="description">*The procedure, or subprocedure in a multicomponent procedure, has been commenced.(en)</items>
      </items>
      <items code="at0069">
        <items id="text">*Procedural difficulty(en)</items>
        <items id="description">*Difficulties or issues encountered during the procedure.(en)</items>
      </items>
      <items code="at0070">
        <items id="text">*Indication (en)</items>
        <items id="description">*The clinical or process-related reason for the procedure. (en)</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">Impact</items>
        <items id="description">Overall assessment of the impact of a health problem for the specific patient.</items>
        <items id="comment">The same diagnosis, with the same severity, has a different impact on each patient. This relevance qualifier implies adjusting the overall impact of that health problem according to the patient's characteristics.&#xD;
For example: Two patients have the same diagnosis. First-degree burn.&#xD;
One is a healthy person, the other is a diabetic patient.&#xD;
The impact for that problem in a diabetic patient is HIGHER (more risk of infection..., longuer time healing).&#xD;
This element is meant to allow for multiple types of impact, including but not limited to: clinical treatment, home functioning, work life.</items>
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Prosedyre</items>
        <items id="description">En klinisk aktivitet som er utført i undersøkende, diagnostisk, kurativ, terapeutisk, evaluerende, prognostisk eller palliativ hensikt.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Prosedyrenavn</items>
        <items id="description">Navnet på prosedyren.</items>
        <items id="comment">Det anbefales å kode "Prosedyrenavn" med en terminologi, om mulig.</items>
      </items>
      <items code="at0003">
        <items id="text">Prosedyredetaljer</items>
        <items id="description">Strukturert informasjon om prosedyren.</items>
        <items id="comment">Bruk for å registrere detaljert, strukturert informasjon om anatomisk lokalisering, metode og teknikker, utstyr som ble benyttet, medisinsk utstyr som ble implantert, funn, etc.</items>
      </items>
      <items code="at0004">
        <items id="text">Prosedyre planlagt</items>
        <items id="description">Prosedyren er planlagt.</items>
      </items>
      <items code="at0005">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om prosedyren eller prosesstrinnet som ikke er registrert i andre felt.</items>
      </items>
      <items code="at0006">
        <items id="text">Komplikasjon</items>
        <items id="description">Detaljer om komplikasjoner oppstått under gjennomføring av prosedyren.</items>
        <items id="comment">Bruk dette dataelementet til å registrere enkle termer eller prekoordinerte komplikasjoner. For eksempel hematuri etter nyrebiopsi eller vevsirritasjon etter innlegging av intravenøst kateter. Dersom kravene til registrering av komplikasjoner er mer komplekse, anbefales bruk av en spesifikk CLUSTER‑arketype i "Prosedyredetaljer"-SLOTet i denne arketypen, og dette dataelementet blir da overflødig.</items>
      </items>
      <items code="at0007">
        <items id="text">Prosedyrerekvisisjon sendt</items>
        <items id="description">Det er sendt rekvisisjon for prosedyren.</items>
      </items>
      <items code="at0014">
        <items id="text">Begrunnelse</items>
        <items id="description">Begrunnelse for at aktiviteten eller prosesstrinnet for den aktuelle prosedyren ble utført.</items>
        <items id="comment">For eksempel grunnen til at prosedyren ble avlyst eller midlertidig stanset.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Prosedyre planlagt</items>
        <items id="description">Dette prosesstrinnet er satt ut av bruk, siden det ved en feil hadde statusen "initial". Bruk det nye prosesstrinnet "Prosedyre planlagt" (at0004) som har den korrekte statusen "planned".</items>
        <items id="comment">(Var: Prosedyren er planlagt.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Prosedyrerekvisisjon sendt</items>
        <items id="description">Dette prosesstrinnet er satt ut av bruk, siden det ved en feil hadde statusen "initial". Bruk det nye prosesstrinnet "Prosedyre planlagt" (at0007) som har den korrekte statusen "planned".</items>
        <items id="comment">(Var: Det er sendt rekvisisjon for prosedyren.)</items>
      </items>
      <items code="at0036">
        <items id="text">Fastsatt tidspunkt for prosedyre</items>
        <items id="description">Tidspunkt for prosedyre er fastsatt.</items>
      </items>
      <items code="at0038">
        <items id="text">Prosedyre utsatt</items>
        <items id="description">Prosedyren er utsatt.</items>
      </items>
      <items code="at0039">
        <items id="text">Prosedyre avlyst</items>
        <items id="description">Den planlagte prosedyren har blitt avlyst før den ble igangsatt.</items>
      </items>
      <items code="at0040">
        <items id="text">Prosedyre midlertidig stanset</items>
        <items id="description">Prosedyren er suspendert/ midlertidig stanset.</items>
      </items>
      <items code="at0041">
        <items id="text">Prosedyre avbrutt</items>
        <items id="description">Prosedyren har blitt avbrutt.</items>
      </items>
      <items code="at0043">
        <items id="text">Prosedyre fullført</items>
        <items id="description">Prosedyren er utført og alle tilknyttede kliniske handlinger er fullførte.</items>
      </items>
      <items code="at0047">
        <items id="text">Prosedyre utført</items>
        <items id="description">Prosedyren eller en del av en prosedyre som består av flere delprosedyrer er utført.</items>
      </items>
      <items code="at0048">
        <items id="text">Resultat</items>
        <items id="description">Resultatet av den utførte prosedyren.</items>
        <items id="comment">Det anbefales å kode "Resultat" med en terminologi, om mulig.</items>
      </items>
      <items code="at0049">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse av prosedyren, tilpasset det aktuelle prosesstrinnet.</items>
        <items id="comment">For eksempel en beskrivelse av utførelsen og funnene fra prosedyren, det avbrutte forsøket, eller avlysningen av prosedyren.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Rekvisisjonsidentifikator</items>
        <items id="description">Den lokale IDen tilordnet rekvisisjonen av helsepersonellet eller organisasjonen som rekvirerer prosedyren.</items>
        <items id="comment">Tilsvarer "Placer Order Number" i HL7 v2-spesifikasjonene.</items>
      </items>
      <items code="at0055">
        <items id="text">Rekvirent</items>
        <items id="description">Detaljer om helsepersonellet eller organisasjonen som har rekvirert prosedyren.</items>
      </items>
      <items code="at0056">
        <items id="text">Mottakers rekvisisjonsidentifikator</items>
        <items id="description">IDen tilordnet rekvisisjonen av helsepersonellet eller organisasjonen som mottar rekvisisjonen.</items>
        <items id="comment">Tilsvarer "Filler Order Number" i HL7 v2-spesifikasjonene.</items>
      </items>
      <items code="at0057">
        <items id="text">Mottaker</items>
        <items id="description">Detaljer om helsepersonellet eller organisasjonen som mottar prosedyrerekvisisjonen.</items>
      </items>
      <items code="at0058">
        <items id="text">Hastegrad</items>
        <items id="description">Prosedyrens hastegrad.</items>
        <items id="comment">Det anbefales å kode "Hastegrad" med en terminologi, om mulig.</items>
      </items>
      <items code="at0060">
        <items id="text">Slutt datotid</items>
        <items id="description">Dato eller datotid da hele prosedyren, eller den siste komponenten i en flerkomponentprosedyre, ble avsluttet.</items>
        <items id="comment">Kun for bruk i forbindelse med prosesstrinnet "Prosedyre utført" og i situasjoner der prosedyren gjentas flere ganger før den fullføres, eller det finnes flere komponenter i prosedyren. Dette kan være det samme som RM-attributtet "time" for prosesstrinnet "Prosedyre utført".</items>
      </items>
      <items code="at0061">
        <items id="text">Total varighet</items>
        <items id="description">Den totale tiden som ble brukt til å fullføre prosedyren. Dette kan omfatte tidsbruk under den aktive fasen av prosedyren, og i tillegg tid da prosedyren var midlertidig stanset.</items>
        <items id="comment">Kun for bruk i forbindelse med prosesstrinnet "Prosedyre fullført".</items>
      </items>
      <items code="at0062">
        <items id="text">Multimedia</items>
        <items id="description">Multimediarepresentasjon av en utført prosedyre.</items>
      </items>
      <items code="at0063">
        <items id="text">Kroppssted</items>
        <items id="description">Stedet på kroppen der prosedyren er utført.</items>
        <items id="comment">Forekomster for dette dataelementet er satt ubegrenset for å tillate kliniske scenarier som f.eks. å fjerne flere hudlesjoner på forskjellige steder, men der alle de andre attributtene er identiske. Bruk dette dataelementet til å registrere enkle termer eller prekoordinerte anatomiske lokaliseringer. Dersom behovene for registrering av anatomisk lokalisering bestemmes først av applikasjonen eller krever mer kompleks modellering som f.eks. relative lokaliseringer, kan arketypene CLUSTER.anatomical_location eller CLUSTER.relative_location brukes i SLOTet "Prosedyredetaljer" i denne arketypen. Dersom den anatomiske lokaliseringen inkluderes som en del av "Prosedyrenavn"-elementet ved hjelp av prekoordinerte koder blir dette dataelementet overflødig.</items>
      </items>
      <items code="at0064">
        <items id="text">Tilleggsinformasjon</items>
        <items id="description">Ytterligere informasjon som trengs for å kunne registrere lokalt definert innhold eller for å tilpasse til andre referansemodeller eller formalismer.</items>
        <items id="comment">For eksempel lokale informasjonsbehov eller ytterligere metadata for å kunne tilpasse til tilsvarende konsepter i FHIR.</items>
      </items>
      <items code="at0065">
        <items id="text">Metode</items>
        <items id="description">Den spesifikke metoden eller teknikken for prosedyren.</items>
        <items id="comment">Bruk dette dataelementet til å registrere enkle termer eller en fritekstlig beskrivelse. Dersom behovene for beskrivelse av metoden krever mer kompleks modellering, kan dette representeres ved hjelp av tilleggsarketyper i SLOTet "Prosedyredetaljer" i denne arketypen. Dersom metoden inkluderes som en del av "Prosedyrenavn"-elementet ved hjelp av prekoordinerte koder blir dette dataelementet overflødig.</items>
      </items>
      <items code="at0066">
        <items id="text">Planlagt datotid</items>
        <items id="description">Dato eller datotid for når prosedyren er planlagt utført.</items>
        <items id="comment">Kun til bruk i forbindelse med prosesstrinnet "Fastsatt tidspunkt for prosedyre".</items>
      </items>
      <items code="at0067">
        <items id="text">Prosedyretype</items>
        <items id="description">Typen prosedyre.</items>
        <items id="comment">Dette dataelementet kan brukes til å støtte organisering innenfor brukergrensesnittet.</items>
      </items>
      <items code="at0068">
        <items id="text">Prosedyre påbegynt</items>
        <items id="description">Prosedyren eller en del av en prosedyre som består av flere delprosedyrer er påbegynt.</items>
      </items>
      <items code="at0069">
        <items id="text">Problem ved prosedyre</items>
        <items id="description">Vanskeligheter eller problemer som det ble støtt på under prosedyren.</items>
        <items id="comment">Eksempler: Pasienten var urolig, magen var ikke skikkelig tømt før gastroskopi, en svulst i gallegangene gjorde det umulig å få skopet gjennom.</items>
      </items>
      <items code="at0070">
        <items id="text">Indikasjon</items>
        <items id="description">Den kliniske eller prosessrelaterte årsaken til prosedyren.</items>
        <items id="comment">For eksempel "Mislykket tarmtømming" eller "Tarmkreftscreening". Det anbefales å kode "Indikasjon" med en terminologi, om mulig. Dette dataelementet tillater flere forekomster, for å tillate brukeren å registrere flere svar ved behov.</items>
      </items>
      <items code="at0071">
        <items id="text">Konsekvens</items>
        <items id="description">Vurdering av prosedyrens konsekvens eller resultat for individet.</items>
        <items id="comment">Samme prosedyre, med samme alvorlighetsgrad eller utfall, kan ha ulik konsekvens for hver enkelt pasient. Denne relevansfaktoren innebærer å justere den samlede påvirkningen av prosedyren eller utfallet i henhold til pasientens individuelle kjennetegn.&#xD;
&#xD;
For eksempel: To pasienter har gjennomgått samme prosedyre med samme resultat: osteosyntese av femte finger på ikke-dominant hånd.&#xD;
&#xD;
Den ene er gartner eller bygningsarbeider, den andre er pianist.&#xD;
&#xD;
Inngrepets konsekvens for pianisten er STØRRE (lengre sykmelding, behov for full funksjonell rehabilitering for å tilpasse seg de høye kravene til finmotorikk i arbeidet).&#xD;
&#xD;
Dette elementet er ment å ta høyde for flere typer konsekvenser, inkludert klinisk behandling, funksjon i hjemmet og arbeidsliv.</items>
      </items>
      <items code="at0072">
        <items id="text">Hensikt</items>
        <items id="description">Det ønskede resultatet av prosedyren.</items>
        <items id="comment">For eksempel kan en operasjon planlegges med kurativ hensikt, men under operasjonen blir det oppdaget at kurativ behandling ikke er mulig, og operasjonen utføres med palliativ hensikt i stedet. Det anbefales å kode "Hensikt" med en terminologi, om mulig. Dette dataelementet tillater flere forekomster, for å tillate brukeren å registrere flere svar ved behov.</items>
      </items>
      <items code="at0073">
        <items id="text">Start datotid</items>
        <items id="description">Dato eller datotid da hele prosedyren, eller den første komponenten i en flerkomponentprosedyre, først ble startet.</items>
        <items id="comment">For eksempel tidspunktet for første snitt. Kun til bruk i sammenheng med prosesstrinnene "Prosedyre utført", "Prosedyre midlertidig stanset", "Prosedyre avbrutt" eller "Prosedyre fullført". Dette kan være det samme som RM-attributtet "time" for prosesstrinnet "Prosedyre påbegynt".</items>
      </items>
      <items code="at0074">
        <items id="text">Varighet av prosesstrinn</items>
        <items id="description">Tidsrommet mellom starten på det forrige prosesstrinnet for denne prosedyren og starten på gjeldende prosesstrinn.</items>
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Procedimiento</items>
        <items id="description">Actividad clínica llevada a cabo con fines de cribado, investigación, diagnóstico, curativos, terapéuticos, de evaluación o paliativos.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Nombre del procedimiento</items>
        <items id="description">Identificación del procedimiento por su nombre.</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">Detalles del procedimiento</items>
        <items id="description">Información estructurada sobre el procedimiento.</items>
        <items id="comment">Se utiliza para recopilar información detallada y estructurada sobre la localización anatómica, el método y la técnica, el equipo utilizado, los dispositivos implantados, los resultados, los hallazgos, etc.</items>
      </items>
      <items code="at0004">
        <items id="text">Procedimiento planificado</items>
        <items id="description">Se planifica el procedimiento a llevar a cabo.</items>
      </items>
      <items code="at0005">
        <items id="text">Comentarios</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">Complicación</items>
        <items id="description">Detalles sobre cualquier complicación derivada del procedimiento.</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Solicitud de procedimiento enviada</items>
        <items id="description">Solicitud de procedimiento enviada.</items>
      </items>
      <items code="at0014">
        <items id="text">Motivo</items>
        <items id="description">Motivo por el que se llevó a cabo la actividad o etapa asistencial para el procedimiento identificado.</items>
        <items id="comment">Por ejemplo: motivo de la cancelación o suspensión del procedimiento.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Procedimiento planificado</items>
        <items id="description">Este apartado ha quedado obsoleto, ya que se asociaba incorrectamente con el estado "inicial". Utilice el nuevo apartado "Procedimiento planificado" (at0004), asociado correctamente con el estado "planificado".</items>
        <items id="comment">(Obsoleto: Se planifica el procedimiento a llevar a cabo.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Solicitud de procedimiento enviada</items>
        <items id="description">Este apartado ha quedado obsoleto, ya que se asociaba incorrectamente con el estado "inicial". Utilice el nuevo apartado "Solicitud de procedimiento enviada" (at0004), asociado correctamente con el estado "planificado".</items>
        <items id="comment">(Obsoleto: Solicitud de procedimiento enviada.)</items>
      </items>
      <items code="at0036">
        <items id="text">Procedimiento programado</items>
        <items id="description">Se ha programado el procedimiento.</items>
      </items>
      <items code="at0038">
        <items id="text">Procedimiento pospuesto</items>
        <items id="description">El procedimiento se ha pospuesto.</items>
      </items>
      <items code="at0039">
        <items id="text">Procedimiento cancelado</items>
        <items id="description">El procedimiento previsto se ha cancelado antes de comenzar.</items>
      </items>
      <items code="at0040">
        <items id="text">Procedimiento suspendido</items>
        <items id="description">Se ha suspendido el procedimiento.</items>
      </items>
      <items code="at0041">
        <items id="text">Procedimiento interrumpido</items>
        <items id="description">Se ha interrumpido el procedimiento.</items>
      </items>
      <items code="at0043">
        <items id="text">Procedimiento completado</items>
        <items id="description">Se ha realizado el procedimiento y se han completado todas las actividades clínicas asociadas.</items>
      </items>
      <items code="at0047">
        <items id="text">Procedimiento realizado</items>
        <items id="description">El procedimiento, o subprocedimiento en un procedimiento multicomponente, se ha realizado.</items>
      </items>
      <items code="at0048">
        <items id="text">Resultado</items>
        <items id="description">Resultado del procedimiento realizado.</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">Descripción</items>
        <items id="description">Descripción narrativa sobre el procedimiento, según corresponda a la fase del proceso.</items>
        <items id="comment">Por ejemplo: descripción de la realización y los resultados del procedimiento, el intento interrumpido o la cancelación del procedimiento.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Identificador de orden del solicitante</items>
        <items id="description">El ID local asignado a la orden por el proveedor sanitario o la organización que solicita el servicio.</items>
        <items id="comment">Equivalente al Placer Order Number en las especificaciones HL7 v2.</items>
      </items>
      <items code="at0055">
        <items id="text">Solicitante</items>
        <items id="description">Datos del profesional sanitario u organización que solicita el servicio.</items>
      </items>
      <items code="at0056">
        <items id="text">Identificador de orden del receptor</items>
        <items id="description">El identificador asignado a la orden por el proveedor sanitario o la organización que recibe la solicitud de servicio. También se denomina Identificador de Orden de Cumplimentación.</items>
        <items id="comment">Equivalente al Placer Order Number en las especificaciones HL7 v2.</items>
      </items>
      <items code="at0057">
        <items id="text">Receptor</items>
        <items id="description">Datos sobre el proveedor u organización sanitaria que recibe la solicitud de servicio.</items>
      </items>
      <items code="at0058">
        <items id="text">Urgencia</items>
        <items id="description">Urgencia del procedimiento.</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">Sólo para su uso en asociación con la etapa "Procedimiento realizado", y en situaciones en las que el procedimiento se repite en varias ocasiones antes de completarse, o hay varios componentes en todo el procedimiento. Puede ser el mismo que el atributo de tiempo RM de la etapa "Procedimiento completado".</items>
      </items>
      <items code="at0061">
        <items id="text">Duración</items>
        <items id="description">Cantidad total de tiempo empleado en completar el procedimiento, que puede incluir el tiempo empleado durante la fase activa del procedimiento más el tiempo durante el cual el procedimiento estuvo suspendido.</items>
        <items id="comment">Sólo para su uso en asociación con la etapa "Procedimiento completado".</items>
      </items>
      <items code="at0062">
        <items id="text">Multimedia</items>
        <items id="description">Representación multimedia del procedimiento realizado.</items>
      </items>
      <items code="at0063">
        <items id="text">Zona corporal</items>
        <items id="description">Identificación de la zona del cuerpo para el procedimiento.</items>
        <items id="comment">Las ocurrencias de este elemento de datos son ilimitadas para permitir escenarios clínicos como la extirpación de múltiples lesiones cutáneas en diferentes lugares, pero donde todos los demás atributos son idénticos. Utilice este elemento de datos para registrar términos sencillos o localizaciones anatómicas precoordinadas. Si los requisitos para registrar la localización anatómica se determinan en tiempo de ejecución por la aplicación o requieren un modelado más complejo, como localizaciones relativas, utilice CLUSTER.anatomical_location o CLUSTER.relative_location en el SLOT "Detalles del procedimiento" de este arquetipo. Si la localización anatómica se incluye en el "Nombre del procedimiento" mediante códigos precoordinados, este elemento de datos será redundante.</items>
      </items>
      <items code="at0064">
        <items id="text">Ampliación</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="at0065">
        <items id="text">Método</items>
        <items id="description">Identificación del método o técnica específicos para el procedimiento.</items>
        <items id="comment">Utilice este elemento de datos para registrar términos sencillos o una descripción narrativa. Si los requisitos para registrar el método requieren una modelización más compleja, ésta puede representarse mediante arquetipos adicionales dentro del SLOT "Detalle del procedimiento", de este arquetipo. Si el método se incluye en el "Nombre del procedimiento" mediante códigos precoordinados, este elemento de datos será redundante.</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">Sólo para su uso en asociación con la etapa "Procedimiento programado".</items>
      </items>
      <items code="at0067">
        <items id="text">Tipo de procedimiento</items>
        <items id="description">Tipo de procedimiento.</items>
        <items id="comment">Este elemento de datos puede utilizarse para dar soporte a la organización dentro de la interfaz de usuario.</items>
      </items>
      <items code="at0068">
        <items id="text">Procedimiento iniciado</items>
        <items id="description">El procedimiento, o subprocedimiento en un procedimiento multicomponente, se ha iniciado.</items>
      </items>
      <items code="at0069">
        <items id="text">Dificultades del procedimiento</items>
        <items id="description">Dificultades o problemas encontrados durante la realización del procedimiento.</items>
        <items id="comment">Ejemplos: El paciente estaba agitado, vaciado insuficiente del estómago antes de la gastroscopia, un tumor en las vías biliares impedía el paso del endoscopio.</items>
      </items>
      <items code="at0070">
        <items id="text">Indicación</items>
        <items id="description">El motivo, clínico o relacionado con el proceso, del procedimiento.</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">Impacto</items>
        <items id="description">Evaluación global del impacto o relevancia de un procedimiento o su resultado para un paciente concreto.</items>
        <items id="comment">El mismo procedimiento, con la misma gravedad o resultado, puede tener un impacto diferente en cada paciente. Este factor de relevancia implica ajustar el impacto general de ese procedimiento o de su resultado, según las características del paciente.&#xD;
Por ejemplo: Dos pacientes se han sometido al mismo procedimiento con el mismo resultado. Reparación mediante osteosíntesis de quinto dedo de mano no dominante. &#xD;
&#xD;
Uno es una jardinero o un peon de obra; el otro, un pianista.&#xD;
El impacto de ese procedimiento en el pianista es MAYOR (baja laboral mas larga, necesidad de rehabilitación funcional completa para ajustar a altos requerimientos de motricidad fina en actividad laboral ).&#xD;
Este elemento está destinado a permitir múltiples tipos de impacto, incluidos pero no limitado a: tratamiento clínico, funcionamiento en el hogar o vida laboral.</items>
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Prozedur</items>
        <items id="description">Eine klinische Aktivität, die zur Früherkennung, Untersuchung, Diagnose, Heilung, Therapie, Bewertung oder in Hinsicht auf palliative Maßnahmen durchgeführt wird.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Name der Prozedur</items>
        <items id="description">Identifizierung der Prozedur über den Namen.</items>
        <items id="comment">Wenn möglich wird die Kodierung der spezifischen Prozedur mit einer Terminologie bevorzugt.</items>
      </items>
      <items code="at0003">
        <items id="text">Details zur Prozedur</items>
        <items id="description">Strukturierte Informationen über die Prozedur.</items>
        <items id="comment">Zur Erfassung detaillierter, strukturierter Informationen über die anatomische Lokalisation, Methode und Technik, verwendetes Equipment, implantierte Geräte, Ergebnisse, Befunde usw.</items>
      </items>
      <items code="at0004">
        <items id="text">Geplante Prozedur</items>
        <items id="description">Die Prozedur, die durchgeführt werden soll, ist geplant.</items>
      </items>
      <items code="at0005">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Beschreibung der Aktivität oder der "Pathway"-Verlaufsschritte, die in anderen Bereichen nicht erfasst wurden.</items>
      </items>
      <items code="at0006">
        <items id="text">Komplikationen</items>
        <items id="description">Details zu allen Komplikationen, die sich aus der Prozedur ergeben haben.</items>
        <items id="comment">Verwenden Sie dieses Datenelement, um einfache Begriffe oder präkoordinierte Komplikationen zu erfassen. Wenn die Anforderungen an die Erfassung der Komplikationen komplexer sind, wird die Verwendung eines spezifischen CLUSTER-Archetyps innerhalb des Slots "Details zur Prozedur" in diesem Archetyp empfohlen. Dieses Datenelement wird dann redundant. Beispiele: Hämaturie nach einer Nierenbiopsie, Reizungen des Gewebes nach dem Legen eines intravenösen Katheters.</items>
      </items>
      <items code="at0007">
        <items id="text">Auftrag für Prozedur versendet</items>
        <items id="description">Der Auftrag für die Prozedur wurde versendet.</items>
      </items>
      <items code="at0014">
        <items id="text">Grund</items>
        <items id="description">Grund, warum die angegebene Aktivität für diese Prozedur durchgeführt wurde.</items>
        <items id="comment">Zum Beispiel: der Grund für den Abbruch oder die Unterbrechung der Prozedur.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Prozedur geplant</items>
        <items id="description">Dieses Element ist veraltet, da es fälschlicherweise mit dem Status "initial" verknüpft war - verwenden Sie das neue Element "Prozedur geplant" (at0004), das korrekt mit dem Status "geplant" verknüpft ist.</items>
        <items id="comment">(War: Die Prozedur, die durchgeführt werden soll, ist geplant.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Auftrag für Prozedur versendet</items>
        <items id="description">Dieses Element ist veraltet, da es fälschlicherweise mit dem Status "initial" verknüpft war - verwenden Sie das neue Element "Geplante Prozedur" (at0007), das korrekt mit dem Status "geplant" verknüpft ist.</items>
        <items id="comment">(War: Der Auftrag für die Prozedur wurde versendet.)</items>
      </items>
      <items code="at0036">
        <items id="text">geplanter Termin der Prozedur</items>
        <items id="description">Ein Termin für die Prozedur wurde geplant.</items>
      </items>
      <items code="at0038">
        <items id="text">Prozedur verschoben</items>
        <items id="description">Die Prozedur wurde verschoben.</items>
      </items>
      <items code="at0039">
        <items id="text">Prozedur storniert</items>
        <items id="description">Die geplante Prozedur wurde vor Beginn storniert.</items>
      </items>
      <items code="at0040">
        <items id="text">Prozedur unterbrochen</items>
        <items id="description">Die Prozedur wurde unterbrochen.</items>
      </items>
      <items code="at0041">
        <items id="text">Prozedur abgebrochen</items>
        <items id="description">Die Prozedur wurde abgebrochen.</items>
      </items>
      <items code="at0043">
        <items id="text">Prozedur beendet</items>
        <items id="description">Die Prozedur wurde durchgeführt und alle damit verbundenen klinischen Aktivitäten wurden beendet.</items>
      </items>
      <items code="at0047">
        <items id="text">Prozedur durchgeführt</items>
        <items id="description">Die Prozedur, oder eine Subprozedur in einem mehrstufigen Vorgehen, wurde durchgeführt.</items>
      </items>
      <items code="at0048">
        <items id="text">Ausgang</items>
        <items id="description">Ausgang der durchgeführten Prozedur.</items>
        <items id="comment">Wenn möglich wird die Kodierung mit einer Terminologie bevorzugt.</items>
      </items>
      <items code="at0049">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung der Prozedur, angepasst an den "Pathway"-Verlaufsschritt.</items>
        <items id="comment">Zum Beispiel: Beschreibung der Durchführung und der Ergebnisse dieser Prozedur, des abgebrochenen Versuchs oder der Stornierung der Prozedur.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Auftragskennung des Antragstellers</items>
        <items id="description">Die lokale ID, die dem Auftrag vom Gesundheitsdienstleister oder der Organisation, die die Leistung anfordert, zugewiesen wurde.</items>
        <items id="comment">Dies entspricht der "Placer Order Number" in den Spezifikationen von HL7 v2.</items>
      </items>
      <items code="at0055">
        <items id="text">Antragsteller</items>
        <items id="description">Angaben über den Gesundheitsdienstleister oder die Organisation, die die Leistung anfordert.</items>
      </items>
      <items code="at0056">
        <items id="text">Auftragskennung des Empfängers</items>
        <items id="description">Die ID, die dem Auftrag von dem Gesundheitsdienstleister oder der Organisation, die die Leistungsanforderung erhält, zugewiesen wurde. Dies wird auch als "Filler Order Identifier" bezeichnet.</items>
        <items id="comment">Dies entspricht der "Filler Order Number" in den Spezifikationen von HL7 v2.</items>
      </items>
      <items code="at0057">
        <items id="text">Empfänger</items>
        <items id="description">Angaben über den Gesundheitsdienstleister oder die Organisation, die die Leistungsanforderung erhält.</items>
      </items>
      <items code="at0058">
        <items id="text">Dringlichkeit</items>
        <items id="description">Dringlichkeit der Prozedur.</items>
        <items id="comment">Wenn möglich wird die Kodierung mit einer Terminologie bevorzugt.</items>
      </items>
      <items code="at0060">
        <items id="text">Enddatum/-uhrzeit</items>
        <items id="description">Das Datum und/oder die Uhrzeit, an dem die gesamte Prozedur, oder die letzte Komponente einer mehrstufigen Prozedur, beendet wurde.</items>
        <items id="comment">Nur zur Verwendung in Verbindung mit dem Element "Prozedur durchgeführt" und in Situationen, in denen die Prozedur vor dem Abschluss mehrmals wiederholt wird oder die Prozedur sich aus mehreren Komponenten zusammensetzt. Dies kann mit dem RM-Zeitattribut des Elements "Prozedur beendet" übereinstimmen.</items>
      </items>
      <items code="at0061">
        <items id="text">Gesamtdauer</items>
        <items id="description">Die Gesamtdauer der Prozedur - diese kann sich aus der aktiven Phase und der Phase, in der die Prozedur unterbrochen wurde, ergeben.</items>
        <items id="comment">Nur in Verbindung mit dem Element "Prozedur beendet" verwenden.</items>
      </items>
      <items code="at0062">
        <items id="text">Multimedia</items>
        <items id="description">Multimediale Darstellung der durchgeführten Prozedur.</items>
      </items>
      <items code="at0063">
        <items id="text">Körperstelle</items>
        <items id="description">Anatomische Lokalisation, an der die Prozedur durchgeführt wird.</items>
        <items id="comment">Das Vorkommen dieses Datenelements ist nicht eingeschränkt. Dies ermöglicht die Darstellung von klinischen Situationen, in denen alle Eigenschaften, ausgenommen die anatomische Lokalisation, identisch sind, wie z.B. das Entfernen mehrerer Hautläsionen an verschiedenen Stellen. Verwenden Sie dieses Datenelement, um einfache Begriffe oder präkoordinierte anatomische Lokalisationen aufzunehmen. Wenn die Anforderungen an die Erfassung der anatomischen Lokalisation zur Laufzeit durch die Anwendung festgelegt werden oder komplexere Modellierungen wie z.B. die relative Lokalisation erforderlich sind, verwenden Sie entweder CLUSTER.anatomical_location oder CLUSTER.relative_location innerhalb des Slots "Details zur Prozedur" in diesem Archetyp. Wird die anatomische Lokalisation über vordefinierte Codes in den Namen der Prozedur aufgenommen, wird dieses Datenelement redundant.</items>
      </items>
      <items code="at0064">
        <items id="text">Erweiterung</items>
        <items id="description">Zusätzliche Informationen, die erforderlich sind, um lokale Inhalte zu erfassen oder mit anderen Referenzmodellen/Formalismen abzugleichen.</items>
        <items id="comment">Zum Beispiel: Lokaler Informationsbedarf oder zusätzliche Metadaten zur Anpassung an FHIR- oder CIMI-Äquivalente.</items>
      </items>
      <items code="at0065">
        <items id="text">Methode</items>
        <items id="description">Identifizierung der spezifischen Prozedurmethode oder -technik.</items>
        <items id="comment">Verwenden Sie dieses Datenelement, um einfache Begriffe oder eine Beschreibung zu erfassen. Wenn die Anforderungen an die Erfassung der Methode eine komplexere Modellierung erfordern, kann dies durch zusätzliche Archetypen innerhalb des SLOTs "Details zur Prozedur" in diesem Archetyp dargestellt werden. Wird die Methode über vordefinierte Codes in dem Element "Name der Prozedur" aufgenommen, wird dieses Datenelement redundant.</items>
      </items>
      <items code="at0066">
        <items id="text">Geplantes Datum/Uhrzeit</items>
        <items id="description">Das Datum und/oder die Uhrzeit für die die Prozedur angesetzt ist.</items>
        <items id="comment">Nur für die Verwendung in Verbindung mit dem Element "geplanter Termin der Prozedur" .</items>
      </items>
      <items code="at0067">
        <items id="text">Art der Prozedur</items>
        <items id="description">Die Art der Prozedur.</items>
        <items id="comment">Dieses pragmatische Datenelement kann zur Unterstützung der Gliederung für die Benutzeroberfläche verwendet werden.</items>
      </items>
      <items code="at0068">
        <items id="text">Prozedur begonnen</items>
        <items id="description">Die Prozedur, oder eine Subprozedur in einem mehrstufigen Vorgehen, wurde begonnen.</items>
      </items>
      <items code="at0069">
        <items id="text">Schwierigkeiten bei der Durchführung der Prozedur</items>
        <items id="description">Schwierigkeiten oder Probleme, die während der Durchführung der Prozedur aufgetreten sind.</items>
        <items id="comment">Beispiele: Der Patient war unruhig; unzureichende Entleerung des Magens vor der Gastroskopie; ein Tumor in den Gallengängen machte es unmöglich, den Bereich zu passieren.</items>
      </items>
      <items code="at0070">
        <items id="text">Indikation</items>
        <items id="description">Der klinische oder prozessbezogene Grund für die Prozedur.</items>
        <items id="comment">Die Kodierung der Indikation mit einer Terminologie wird nach Möglichkeit bevorzugt. Dieses Datenelement ermöglicht mehrere Vorkommen. Zum Beispiel: "Fehlgeschlagenen Darmvorbereitung" oder "Darmkrebsvorsorge".</items>
      </items>
      <items code="at0071">
        <items id="text">Auswirkungen</items>
        <items id="description">Beurteilung der Auswirkungen eines Eingriffs oder seines Ergebnisses für einen bestimmten Patienten.</items>
        <items id="comment">Derselbe Eingriff, bei gleichem Schweregrad oder gleichem Ergebnis, kann sich auf jeden Patienten unterschiedlich auswirken. Dieser Relevanzfaktor beinhaltet die Anpassung der Gesamtauswirkungen des Eingriffs oder des Ergebnisses an die individuellen Merkmale des Patienten.&#xD;
&#xD;
Beispiel: Zwei Patienten haben sich demselben Eingriff mit gleichem Ergebnis unterzogen: einer Osteosynthese des fünften Fingers ihrer nicht-dominanten Hand.&#xD;
&#xD;
Einer ist Gärtner oder Bauarbeiter, der andere Pianist.&#xD;
&#xD;
Die Auswirkungen des Eingriffs sind für den Pianisten GRÖSSER (längere Krankschreibung, Notwendigkeit einer umfassenden funktionellen Rehabilitation zur Anpassung an die hohen feinmotorischen Anforderungen seines Berufs).&#xD;
&#xD;
Dieses Element soll verschiedene Arten von Auswirkungen berücksichtigen, darunter unter anderem die klinische Behandlung, die Alltagsbewältigung und das Berufsleben.</items>
      </items>
      <items code="at0072">
        <items id="text">*Intent(en)</items>
        <items id="description">*The intended outcome of the procedure.(en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required.(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime(en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started.(en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step.(en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration(en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-pt">
      <items code="at0000">
        <items id="text">Procedimento</items>
        <items id="description">Atividade clínica realizada para fins de rastreio, investigação, diagnóstico, cura, tratamento, avaliação ou cuidados paliativos.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Nome do procedimento</items>
        <items id="description">Identificação do procedimento pelo nome.</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">Detalhe do procedimento</items>
        <items id="description">Informação estruturada sobre o procedimento.</items>
        <items id="comment">Use para capturar informações detalhadas e estruturadas sobre localização anatómica, método e técnica, equipamentos usados, dispositivos implantados, resultados, descobertas, etc.</items>
      </items>
      <items code="at0004">
        <items id="text">Procedimento Planeado</items>
        <items id="description">O procedimento a ser realizado está planeado.</items>
      </items>
      <items code="at0005">
        <items id="text">Comentário</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">Complicação</items>
        <items id="description">Detalhes sobre qualquer complicação decorrente do procedimento.</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Pedido de procedimento enviado</items>
        <items id="description">Pedido para o procedimento enviado.</items>
      </items>
      <items code="at0014">
        <items id="text">Motivo</items>
        <items id="description">Motivo pelo qual foi realizada a etapa da atividade ou da via de cuidado para o procedimento identificado.</items>
        <items id="comment">Por exemplo: o motivo do cancelamento ou suspensão do procedimento.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Procedimento planeado</items>
        <items id="description">Esta etapa de caminho foi preterida, pois foi incorretamente associada ao estado 'inicial' - use a nova etapa de caminho 'Procedimento planeado' (at0004) que está corretamente associada ao estado 'planeado'.</items>
        <items id="comment">(Era: O procedimento a ser realizado está planeado.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Solicitação de procedimento enviada</items>
        <items id="description">Esta etapa de caminho foi preterida, pois foi incorretamente associada ao estado 'inicial' - use a nova etapa de caminho 'Pedido de procedimento enviado' (at0007) que está corretamente associada ao estado 'planeado'.</items>
        <items id="comment">(Foi: Pedido de procedimento enviado.)</items>
      </items>
      <items code="at0036">
        <items id="text">Procedimento programado</items>
        <items id="description">O procedimento foi agendado.</items>
      </items>
      <items code="at0038">
        <items id="text">Procedimento Adiado</items>
        <items id="description">O procedimento foi adiado.</items>
      </items>
      <items code="at0039">
        <items id="text">Procedimento Cancelado</items>
        <items id="description">O procedimento previsto foi cancelado antes do início.</items>
      </items>
      <items code="at0040">
        <items id="text">Procedimento suspenso</items>
        <items id="description">O procedimento foi suspenso.</items>
      </items>
      <items code="at0041">
        <items id="text">Procedimento abortado</items>
        <items id="description">O procedimento foi abortado.</items>
      </items>
      <items code="at0043">
        <items id="text">Procedimento concluído</items>
        <items id="description">O procedimento foi realizado e todas as atividades clínicas associadas foram concluídas.</items>
      </items>
      <items code="at0047">
        <items id="text">Procedimento realizado</items>
        <items id="description">O procedimento, ou subprocedimento num procedimento com vários componentes, foi realizado.</items>
      </items>
      <items code="at0048">
        <items id="text">Resultado</items>
        <items id="description">Resultado do procedimento realizado.</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o procedimento, conforme apropriado para a etapa do caminho.</items>
        <items id="comment">Por exemplo: descrição do desempenho e resultados do procedimento, da tentativa abortada ou do cancelamento do procedimento.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Identificador do requerente do pedido</items>
        <items id="description">O documento de identificação local atribuído ao pedido pelo prestador de cuidados de saúde ou organização que solicita o serviço.</items>
        <items id="comment">Isto é equivalente ao número de ordem Placer em HL7 v2 especificações.</items>
      </items>
      <items code="at0055">
        <items id="text">Requerente</items>
        <items id="description">Detalhes sobre o prestador de cuidados de saúde ou a organização que solicita o serviço.</items>
      </items>
      <items code="at0056">
        <items id="text">Identificador do destinatário do pedido</items>
        <items id="description">O ID atribuído à encomenda pelo prestador de cuidados de saúde ou organização que recebe o pedido de serviço. Isto também é referido como Filler Order Identifier.</items>
        <items id="comment">Isso é equivalente ao número Filler Order Identifier nas especificações HL7 v2.</items>
      </items>
      <items code="at0057">
        <items id="text">Recetor</items>
        <items id="description">Informações sobre o prestador de cuidados de saúde ou a organização que recebe o pedido de assistência.</items>
      </items>
      <items code="at0058">
        <items id="text">Urgência</items>
        <items id="description">Urgência do procedimento.</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">Apenas para utilização em associação com a etapa da via 'Procedimento realizado' e em situações em que o procedimento é repetido em várias ocasiões antes de ser concluído ou há vários componentes em todo o procedimento. Isso pode ser o mesmo que o atributo de tempo RM para a etapa de caminho 'Procedimento concluído'.</items>
      </items>
      <items code="at0061">
        <items id="text">Duração total</items>
        <items id="description">O tempo total necessário para concluir o procedimento, que pode incluir o tempo gasto durante a fase ativa do procedimento e o tempo durante o qual o procedimento foi suspenso.</items>
        <items id="comment">Apenas para utilização em associação com as etapas do caminho 'Procedimento concluído'.</items>
      </items>
      <items code="at0062">
        <items id="text">Multimédia</items>
        <items id="description">Representação multimédia de um procedimento realizado.</items>
      </items>
      <items code="at0063">
        <items id="text">Local do corpo</items>
        <items id="description">Identificação do local do corpo para o procedimento.</items>
        <items id="comment">As ocorrências para este elemento de dados são ilimitadas para permitir cenários clínicos tais como a remoção de lesões de pele múltiplas em lugares diferentes, mas onde todos os outros atributos são idênticos. Use esse elemento de dados para registar termos simples ou localizações anatómicas pré-ordenadas. Se os requisitos para o registo da localização anatómica forem determinados no CLUSTER.anatomical_location ou CLUSTER.relative_location dentro do SLOT 'Detalhe do procedimento' neste arquétipo. Se a localização anatómica for incluída no 'Nome do procedimento' por meio de códigos pré-ordenados, esse elemento de dados ficará redundante.</items>
      </items>
      <items code="at0064">
        <items id="text">Extensão</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="at0065">
        <items id="text">Método</items>
        <items id="description">Identificação do método ou técnica específica para o procedimento.</items>
        <items id="comment">Use esse elemento de dados para registar termos simples ou uma descrição narrativa. Se os requisitos para o registo do método exigirem uma modelagem mais complexa, isso pode ser representado por arquétipos adicionais dentro do SLOT 'Detalhes do procedimento' neste arquétipo. Se o método for incluído no 'Nome do procedimento' com códigos pré-ordenados, esse elemento de dados ficará redundante.</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">Apenas para utilização em associação com a etapa de caminho 'Procedimento agendado'.</items>
      </items>
      <items code="at0067">
        <items id="text">Tipo de procedimento</items>
        <items id="description">O tipo de procedimento.</items>
        <items id="comment">Este elemento de dados pragmáticos pode ser usado para apoiar a organização dentro da interface do/a utilizador/a.</items>
      </items>
      <items code="at0068">
        <items id="text">Procedimento iniciado</items>
        <items id="description">O procedimento, ou subprocedimento num procedimento com vários componentes, foi iniciado.</items>
      </items>
      <items code="at0069">
        <items id="text">Dificuldade processual</items>
        <items id="description">Dificuldades ou problemas encontrados durante a execução do procedimento.</items>
        <items id="comment">Exemplos: O doente estava agitado, esvaziamento insuficiente do estômago antes da gastroscopia, um tumor nos ductos biliares impossibilitou a passagem da sonda.</items>
      </items>
      <items code="at0070">
        <items id="text">indicação</items>
        <items id="description">A razão clínica ou relacionada ao processo para o procedimento.</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">Impact</items>
        <items id="description">Overall assessment of the impact of a health problem for the specific patient.</items>
        <items id="comment">The same diagnosis, with the same severity, has a different impact on each patient. This relevance qualifier implies adjusting the overall impact of that health problem according to the patient's characteristics.&#xD;
For example: Two patients have the same diagnosis. First-degree burn.&#xD;
One is a healthy person, the other is a diabetic patient.&#xD;
The impact for that problem in a diabetic patient is HIGHER (more risk of infection..., longuer time healing).&#xD;
This element is meant to allow for multiple types of impact, including but not limited to: clinical treatment, home functioning, work life.</items>
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Åtgärd</items>
        <items id="description">En klinisk aktivitet utförd för screening-, undersökande, diagnostiska, botande, terapeutiska, utvärderande eller palliativa ändamål.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Benämning på åtgärd</items>
        <items id="description">Åtgärdens benämning.</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">Åtgärdsdetaljer</items>
        <items id="description">Strukturerad information om åtgärden.</items>
        <items id="comment">Används för att fånga detaljerad, strukturerad information om anatomisk plats, metod och teknik, utrustning som används, implanterat såsom enheter eller utrustning, resultat, fynd m.m.</items>
      </items>
      <items code="at0004">
        <items id="text">Åtgärd planerad</items>
        <items id="description">Den åtgärd som ska genomföras är planerad.</items>
      </items>
      <items code="at0005">
        <items id="text">Kommentar</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">Komplikation</items>
        <items id="description">Detaljer om eventuella komplikationer som uppstår från åtgärden.</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Förfrågan om åtgärd skickad</items>
        <items id="description">Förfrågan om åtgärd är skickad.</items>
      </items>
      <items code="at0014">
        <items id="text">Anledning</items>
        <items id="description">Anledning till att nytt processteg för åtgärden dokumenterats.</items>
        <items id="comment">Exempelvis anledningen till att åtgärden är i processteget pausad eller avbruten.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Åtgärd planerad</items>
        <items id="description">Detta steg har upphört att gälla eftersom det felaktigt var associerat med status "initial". Använd det nya steget "Åtgärd planerad" (at0004) som är korrekt associerat med status "planerad" .</items>
        <items id="comment">(Var: Den åtgärd som ska utföras är planerad.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Förfrågan om åtgärd skickad</items>
        <items id="description">Detta steg har upphört att gälla eftersom det felaktigt var associerat med status "initial". Använd det nya steget "Åtgärdsförfrågan skickad" (at0007) som är korrekt associerat med status "planerad".</items>
        <items id="comment">(Var: Åtgärdsförfrågan skickad.)</items>
      </items>
      <items code="at0036">
        <items id="text">Åtgärd bokad</items>
        <items id="description">Åtgärden är bokad.</items>
      </items>
      <items code="at0038">
        <items id="text">Åtgärd uppskjuten</items>
        <items id="description">Åtgärden är uppskjuten.</items>
      </items>
      <items code="at0039">
        <items id="text">Åtgärd inställd</items>
        <items id="description">Den planerade åtgärden är inställd.</items>
      </items>
      <items code="at0040">
        <items id="text">Åtgärd pausad</items>
        <items id="description">Åtgärden är pausad.</items>
      </items>
      <items code="at0041">
        <items id="text">Åtgärd avbruten</items>
        <items id="description">Åtgärden är avbruten.</items>
      </items>
      <items code="at0043">
        <items id="text">Åtgärd slutförd</items>
        <items id="description">Åtgärden och alla tillhörande kliniska aktiviteter är slutförda.</items>
      </items>
      <items code="at0047">
        <items id="text">Åtgärd utförd</items>
        <items id="description">Åtgärden är utförd.</items>
      </items>
      <items code="at0048">
        <items id="text">Resultat</items>
        <items id="description">Resultat av genomförd åtgärd</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning av åtgärden, anpassad till det aktuella processteget.</items>
        <items id="comment">Exempelvis, en beskrivning av åtgärdens utförande och dess fynd, den avbrutna åtgärden eller den inställda åtgärden.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Beställnings-ID hos avsändare</items>
        <items id="description">Beställnings-ID definierat av den aktör som är avsändare av förfrågan av tjänst.</items>
        <items id="comment">Detta motsvarar Place Order Number i specifikationerna för HL7 v2.</items>
      </items>
      <items code="at0055">
        <items id="text">Beställare</items>
        <items id="description">Detaljer om den aktör som efterfrågar tjänsten.</items>
      </items>
      <items code="at0056">
        <items id="text">Betällnings-ID hos mottagare</items>
        <items id="description">Beställnings-ID definierat av den aktör som tar emot förfrågan av tjänsten.</items>
        <items id="comment">Detta motsvarar Filler Order Number i specifikationerna för HL7 v2.</items>
      </items>
      <items code="at0057">
        <items id="text">Mottagare</items>
        <items id="description">Detaljer om den aktör som tar emot förfrågan av tjänsten.</items>
      </items>
      <items code="at0058">
        <items id="text">Brådskandegrad</items>
        <items id="description">Åtgärdens brådskandegrad.</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">Kan endast användas i samband med steget "Åtgärd utförd" och i situationer där åtgärden upprepas vid flera tillfällen innan den avslutas eller om det finns flera delåtgärder i hela åtgärden. Detta kan vara detsamma som RM-tidsattributet för steget "Åtgärd slutförd".</items>
      </items>
      <items code="at0061">
        <items id="text">Total varaktighet</items>
        <items id="description">Den totala tid som krävs för att utföra åtgärden, vilket kan inkludera tid som tillbringats under den aktiva fasen av åtgärden plus den tid under vilken åtgärden pausades.</items>
        <items id="comment">Kan endast användas i samband med steget "Åtgärd slutförd".</items>
      </items>
      <items code="at0062">
        <items id="text">Multimedia</items>
        <items id="description">Multimedierepresentation av utförd åtgärd.</items>
      </items>
      <items code="at0063">
        <items id="text">Anatomisk position</items>
        <items id="description">Identifiering av anatomisk plats för åtgärden.</items>
        <items id="comment">Förekomsten av detta fält är obegränsat för att möjliggöra kliniska scenarier som att ta bort flera hudförändringar på olika platser, men där alla andra attribut är identiska. Använd detta fält för att dokumentera enkla termer eller prekoordinerade anatomiska platser. Om kraven på dokumentation av den anatomiska platsen bestäms vid körning av applikationen eller kräver mer komplex modellering, till exempel relativa platser (exempelvis 3 cm ovanför vänster knä), använd CLUSTER.anatomical_location eller CLUSTER.relative_location i SLOT "Åtgärdsdetaljer" i denna arketyp. Om den anatomiska platsen ingår i "Benämning på åtgärd" genom prekoordinerade koder blir detta fält överflödigt.</items>
      </items>
      <items code="at0064">
        <items id="text">Tilläggsinformation</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="at0065">
        <items id="text">Metod</items>
        <items id="description">Identifiering av specifik metod eller teknik för åtgärden.</items>
        <items id="comment">Använd detta fält för att dokumentera metoden. Om kraven för dokumentation av metoden kräver mer komplex modellering kan detta representeras av ytterligare arketyper i SLOT "Åtgärdsdetalj" i denna arketyp. Om metoden ingår i "Benämning på åtgärd" genom prekoordinerade koder blir detta fält överflödigt.</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">Ska endast användas i samband med steget "Åtgärd bokad".</items>
      </items>
      <items code="at0067">
        <items id="text">Åtgärdstyp</items>
        <items id="description">Typ av åtgärd</items>
        <items id="comment">Detta fält kan användas för att stödja en verksamhet genom användargränssnittet.</items>
      </items>
      <items code="at0068">
        <items id="text">Åtgärd påbörjad</items>
        <items id="description">Åtgärden är påbörjad.</items>
      </items>
      <items code="at0069">
        <items id="text">Svårigheter med åtgärd</items>
        <items id="description">Svårigheter eller problem som uppstår under genomförandet av åtgärden.</items>
        <items id="comment">Exempelvis patienten var upprörd, otillräcklig tömning av magsäcken före gastroskopi, en tumör i gallgångarna gjorde det omöjligt att passera igenom med gastroskop.</items>
      </items>
      <items code="at0070">
        <items id="text">Indikation</items>
        <items id="description">Den kliniska eller processrelaterade orsaken till åtgärden.</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">*DV_TEXT (en)</items>
        <items id="description" />
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="ca">
      <items code="at0000">
        <items id="text">Procediment</items>
        <items id="description">Activitat clínica duta a terme amb fins de cribratge, investigació, diagnòstic, curatius, terapèutics, d'avaluació o pal·liatius.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Nom del procediment</items>
        <items id="description">Identificació del procediment pel nom.</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">Detalls del procediment</items>
        <items id="description">Informació estructurada sobre el procediment.</items>
        <items id="comment">S'utilitza per recopilar informació detallada i estructurada sobre la localització anatòmica, el mètode i la tècnica, l'equip utilitzat, els dispositius implantats, els resultats, les troballes, etc.</items>
      </items>
      <items code="at0004">
        <items id="text">Procediment planificat</items>
        <items id="description">Es planifica el procediment que cal dur a terme.</items>
      </items>
      <items code="at0005">
        <items id="text">Comentaris</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">Complicació</items>
        <items id="description">Detalls sobre qualsevol complicació derivada del procediment.</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Sol·licitud de procediment enviada</items>
        <items id="description">Sol·licitud de procediment enviada.</items>
      </items>
      <items code="at0014">
        <items id="text">Motiu</items>
        <items id="description">Motiu pel qual es va dur a terme l'activitat o etapa assistencial per al procediment identificat.</items>
        <items id="comment">Per exemple: motiu de la cancel·lació o suspensió del procediment.</items>
      </items>
      <items code="at0034">
        <items id="text">X - Procediment planificat</items>
        <items id="description">Aquest apartat ha quedat obsolet, ja que s'associava incorrectament amb l'estat inicial. Utilitzeu el nou apartat "Procediment planificat" (at0004), associat correctament amb l'estat "planificat".</items>
        <items id="comment">(Obsolet: Es planifica el procediment a dur a terme.)</items>
      </items>
      <items code="at0035">
        <items id="text">X - Sol·licitud de procediment enviada</items>
        <items id="description">Aquest apartat ha quedat obsolet, ja que s'associava incorrectament amb l'estat inicial. Utilitzeu el nou apartat "Sol·licitud de procediment enviada" (at0004), associat correctament amb l'estat "planificat".</items>
        <items id="comment">(Obsolet: Sol·licitud de procediment enviada.)</items>
      </items>
      <items code="at0036">
        <items id="text">Procediment programat</items>
        <items id="description">El procediment s'ha programat.</items>
      </items>
      <items code="at0038">
        <items id="text">Procediment posposat</items>
        <items id="description">El procediment s'ha posposat.</items>
      </items>
      <items code="at0039">
        <items id="text">Procediment cancel·lat</items>
        <items id="description">S'ha cancel·lat el procediment previst abans de començar.</items>
      </items>
      <items code="at0040">
        <items id="text">Procediment suspès</items>
        <items id="description">El procediment s'ha suspès.</items>
      </items>
      <items code="at0041">
        <items id="text">Procediment interromput</items>
        <items id="description">El procediment s'ha interromput.</items>
      </items>
      <items code="at0043">
        <items id="text">Procediment completat</items>
        <items id="description">S'ha fet el procediment i s'han completat totes les activitats clíniques associades.</items>
      </items>
      <items code="at0047">
        <items id="text">Procediment realitzat</items>
        <items id="description">El procediment o subprocediment en un procediment multicomponent s'ha realitzat.</items>
      </items>
      <items code="at0048">
        <items id="text">Resultat</items>
        <items id="description">Resultat del procediment realitzat.</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">Descripció</items>
        <items id="description">Descripció narrativa del procediment, segons correspongui a la fase del procés.</items>
        <items id="comment">Per exemple: descripció de la realització i resultats del procediment, l'intent interromput o la cancel·lació del procediment.</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">Identificador d'ordre del sol·licitant</items>
        <items id="description">L'ID local assignat a l'ordre pel proveïdor sanitari o l'organització que sol·licita el servei.</items>
        <items id="comment">Equivalent al Placer Order Number a les especificacions HL7 v2.</items>
      </items>
      <items code="at0055">
        <items id="text">Sol·licitant</items>
        <items id="description">Dades del professional sanitari o organització que sol·licita el servei.</items>
      </items>
      <items code="at0056">
        <items id="text">Identificador d'ordre del receptor</items>
        <items id="description">L'identificador assignat a l'ordre pel proveïdor sanitari o organització que rep la sol·licitud de servei. També s'anomena identificador d'ordre d'emplenament.</items>
        <items id="comment">Equivalent al Filler Order Number a les especificacions HL7 v2.</items>
      </items>
      <items code="at0057">
        <items id="text">Receptor</items>
        <items id="description">Dades sobre el proveïdor o organització sanitària que rep la sol·licitud de servei.</items>
      </items>
      <items code="at0058">
        <items id="text">Urgència</items>
        <items id="description">Urgència del procediment.</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">Només per al seu ús en associació amb l'etapa "Procediment realitzat", i en situacions en què el procediment es repeteix diverses vegades abans de completar-se, o hi ha diversos components en tot el procediment. Pot ser el mateix que l'atribut de temps RM de l'etapa "Procediment completat".</items>
      </items>
      <items code="at0061">
        <items id="text">Durada</items>
        <items id="description">Quantitat total de temps emprat a completar el procediment, que pot incloure el temps emprat durant la fase activa del procediment més el temps durant el qual el procediment va estar suspès.</items>
        <items id="comment">Només per a ús en associació amb l'etapa "Procediment completat".</items>
      </items>
      <items code="at0062">
        <items id="text">Multimèdia</items>
        <items id="description">Representació multimèdia del procediment realitzat.</items>
      </items>
      <items code="at0063">
        <items id="text">Zona corporal</items>
        <items id="description">Identificació de la zona del cos per al procediment.</items>
        <items id="comment">Les ocurrències d'aquest element de dades són il·limitades per permetre escenaris clínics com l'extirpació de múltiples lesions cutànies a diferents llocs, però on tots els altres atributs són idèntics. Utilitzeu aquest element de dades per registrar termes senzills o localitzacions anatòmiques precoordinades. Si els requisits per registrar la localització anatòmica es determinen en temps d'execució per l'aplicació o requereixen un modelatge més complex, com ara localitzacions relatives, utilitzeu CLUSTER.anatomical_location o CLUSTER.relative_location al SLOT "Detalls del procediment" d'aquest arquetip. Si la localització anatòmica s'inclou al “Nom del procediment” mitjançant codis precoordinats, aquest element de dades serà redundant.</items>
      </items>
      <items code="at0064">
        <items id="text">Ampliació</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="at0065">
        <items id="text">Mètode</items>
        <items id="description">Identificació del mètode o tècnica específics per al procediment.</items>
        <items id="comment">Utilitzeu aquest element de dades per registrar termes senzills o una descripció narrativa. Si els requisits per registrar el mètode requereixen una modelització més complexa, aquesta es pot representar mitjançant arquetips addicionals dins del SLOT "Detall del procediment" d'aquest arquetip. Si el mètode s'inclou al "Nom del procediment" mitjançant codis precoordinats, aquest element de dades serà redundant.</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">Només per utilitzar-lo en associació amb l'etapa "Procediment programat".</items>
      </items>
      <items code="at0067">
        <items id="text">Tipus de procediment</items>
        <items id="description">Tipus de procediment.</items>
        <items id="comment">Aquest element de dades es pot utilitzar per donar suport a l'organització dins la interfície d'usuari.</items>
      </items>
      <items code="at0068">
        <items id="text">Procediment iniciat</items>
        <items id="description">El procediment o subprocediment en un procediment multicomponent s'ha iniciat.</items>
      </items>
      <items code="at0069">
        <items id="text">Dificultats del procediment</items>
        <items id="description">Dificultats o problemes trobats durant la realització del procediment.</items>
        <items id="comment">Exemples: El pacient estava agitat, buidat insuficient de l'estómac abans de la gastroscòpia, un tumor a les vies biliars impedia el pas de l'endoscopi.</items>
      </items>
      <items code="at0070">
        <items id="text">Indicació</items>
        <items id="description">El motiu, clínic o relacionat amb el procés, del procediment.</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">Impacte</items>
        <items id="description">Avaluació de l'impacte o la rellevància d'un procediment o del seu resultat per a un pacient concret.</items>
        <items id="comment">El mateix procediment, amb la mateixa gravetat o resultat, pot tenir un impacte diferent a cada pacient. Aquest factor de rellevància implica ajustar l'impacte general d'aquest procediment o del seu resultat, segons les característiques del pacient.&#xD;
Per exemple: Dos pacients han estat sotmesos al mateix procediment amb el mateix resultat. Reparació mitjançant osteosíntesi de cinquè dit de mà no dominant.&#xD;
Un és un jardiner o un peó d'obra; l'altre, un pianista.&#xD;
L'impacte d'aquest procediment al pianista és MAJOR (baixa laboral més llarga, necessitat de rehabilitació funcional completa per ajustar a alts requeriments de motricitat fina en activitat laboral).&#xD;
Aquest element està destinat a permetre múltiples tipus d'impacte, inclosos però no limitat a: tractament clínic, funcionament a la llar o vida laboral.</items>
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="zh-cn">
      <items code="at0000">
        <items id="text">操作</items>
        <items id="description">为了实现评估类、探查类、筛查类、诊断类、治愈类、疗法类或姑息治疗类等目的而开展的临床活动。</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">操作名称</items>
        <items id="description">利用名称对于此项操作进行的标识。</items>
        <items id="comment">*Coding of the 'Procedure name' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0003">
        <items id="text">操作详情</items>
        <items id="description">关于此项操作的结构化信息。</items>
        <items id="comment">用于记录操作相关的详细的结构化信息，包括解剖学位置、方法与技术方法、所采用的设备、所植入的器械/装置、结果、发现/所见等。</items>
      </items>
      <items code="at0004">
        <items id="text">操作已编制计划</items>
        <items id="description">计划有待开展/执行/实施的操作。</items>
      </items>
      <items code="at0005">
        <items id="text">注释</items>
        <items id="description">*Additional narrative about the procedure or care pathway step not captured in other fields. (en)</items>
      </items>
      <items code="at0006">
        <items id="text">并发症</items>
        <items id="description">关于此项操作所引发的任何并发症的详情。</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. For example: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter. If the requirements for recording complication are more complex then use of a specific CLUSTER archetype within the 'Procedure detail' SLOT in this archetype is advised and this data element becomes redundant. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">操作请求已发送</items>
        <items id="description">已发送关于当前操作的请求。</items>
      </items>
      <items code="at0014">
        <items id="text">原因</items>
        <items id="description">关于针对当前操作实际开展/执行此项活动或照护服务路径步骤的原因。</items>
        <items id="comment">例如：关于取消或暂停当前操作的原因。</items>
      </items>
      <items code="at0034">
        <items id="text">X - 操作已编制计划</items>
        <items id="description">目前已弃用此路径步骤，因其错误地关联了“初始”（initial）状态 —— 请采用新的“操作已编制计划”（Procedure planned，编码：at0004）路径步骤，该步骤正确地关联了“已计划”（planned）状态。</items>
        <items id="comment">（原描述：计划有待开展/执行/实施的操作。）</items>
      </items>
      <items code="at0035">
        <items id="text">X - 操作请求已发送</items>
        <items id="description">目前已弃用此路径步骤，因其错误地关联了“初始”（initial）状态 —— 请采用新的“操作请求已发送”（Procedure request sent，编码：at0007）路径步骤，该步骤正确地关联了“已计划”（planned）状态。</items>
        <items id="comment">（原描述：已发送关于当前操作的请求。）</items>
      </items>
      <items code="at0036">
        <items id="text">操作已排程</items>
        <items id="description">目前已对此项操作进行了排程。</items>
      </items>
      <items code="at0038">
        <items id="text">操作已延期</items>
        <items id="description">目前已延期此项操作。</items>
      </items>
      <items code="at0039">
        <items id="text">操作已取消</items>
        <items id="description">已计划的操作在开始之前已被取消。</items>
      </items>
      <items code="at0040">
        <items id="text">操作已暂停</items>
        <items id="description">目前已暂停此项操作。</items>
      </items>
      <items code="at0041">
        <items id="text">操作已中止</items>
        <items id="description">目前已中止此项操作。</items>
      </items>
      <items code="at0043">
        <items id="text">操作已完成</items>
        <items id="description">目前已执行此项操作，且所有相关的临床活动均已完成。</items>
      </items>
      <items code="at0047">
        <items id="text">操作已执行</items>
        <items id="description">目前已执行此项操作（或多组成部分操作之中的此项子操作）。</items>
      </items>
      <items code="at0048">
        <items id="text">结局</items>
        <items id="description">已执行操作的结局。</items>
        <items id="comment">*Coding of the 'Outcome' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0049">
        <items id="text">描述</items>
        <items id="description">对于此项操作进行的，适合于当前路径步骤的叙述性描述。</items>
        <items id="comment">例如：关于此项操作的执行情况与发现/所见、已中止的尝试或此项操作的取消的描述。</items>
      </items>
      <items code="at0053">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0054">
        <items id="text">申请方医嘱标识符</items>
        <items id="description">申请此项服务的健康医疗服务提供方或机构为此项医嘱所分配的本地标识符。</items>
        <items id="comment">该标识符等同于HL7 v2标准中的“申请方医嘱编号”（Placer Order Number）。</items>
      </items>
      <items code="at0055">
        <items id="text">申请方</items>
        <items id="description">关于申请此项服务的健康医疗服务提供方或机构的相关详情。</items>
      </items>
      <items code="at0056">
        <items id="text">接收方医嘱标识符</items>
        <items id="description">由接收服务请求的健康医疗服务提供方或机构为此项医嘱所分配的标识符，也称为“执行方医嘱标识符”（Filler Order Identifier）。</items>
        <items id="comment">该标识符等同于 HL7 v2 标准之中的“执行方医嘱编号”（Filler Order Number）。</items>
      </items>
      <items code="at0057">
        <items id="text">接收方</items>
        <items id="description">关于接收服务请求的健康医疗服务提供方或机构的相关详情。</items>
      </items>
      <items code="at0058">
        <items id="text">紧急程度</items>
        <items id="description">此项操作的紧急程度。</items>
        <items id="comment">*Coding of the 'Urgency' with a terminology is recommended, if available. (en)</items>
      </items>
      <items code="at0060">
        <items id="text">*End datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the last component of a multicomponent procedure, was finished. (en)</items>
        <items id="comment">仅仅旨在与“已执行的操作”（Procedure performed）路径步骤联合运用，且适用于以下场景：操作在完成之前需多次重复进行，或整个操作包含多个组成部分。该时间可能与“已完成的操作”（Procedure completed）路径步骤的参考模型（RM）时间属性相同。</items>
      </items>
      <items code="at0061">
        <items id="text">总时长</items>
        <items id="description">完成此项操作所实际花费的总时间，可能包括操作执行阶段所花费的时间以及操作暂停期间所流逝的时间。</items>
        <items id="comment">仅仅旨在与“已完成的操作”（Procedure completed）路径步骤联合运用。</items>
      </items>
      <items code="at0062">
        <items id="text">多媒体</items>
        <items id="description">关于所执行的操作的多媒体呈现资料。</items>
      </items>
      <items code="at0063">
        <items id="text">身体部位</items>
        <items id="description">对于此项操作所针对的身体部位的标识。</items>
        <items id="comment">该数据元的出现次数不限，以便适配需对不同部位进行相同操作的临床场景（例如，切除不同部位的多个皮肤病变，而操作的其余所有属性均相同）。请采用本数据元来记录简单的术语或先组配型的解剖学位置。若解剖学位置的记录需求需要的是应用程序在运行时确定，或者是需更为复杂的建模（如相对位置），则应当采用本原始型操作详情槽位（Procedure detail）之中的群簇类解剖学位置原始型（CLUSTER.anatomical_location）或群簇类相对位置原始型（CLUSTER.relative_location）。若已经利用先组配型代码将解剖学位置信息包含在“操作名称”数据元当中，则无需填写本数据元。</items>
      </items>
      <items code="at0064">
        <items id="text">扩展</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="at0065">
        <items id="text">方法</items>
        <items id="description">对于此项操作所采用的特定方法或技术方法的标识。</items>
        <items id="comment">请采用本数据元来记录简单的术语或叙述性的描述。若方法的记录需求需要更为复杂的建模，则可在本原始型之中的操作详情槽位（Procedure detail）内利用其他的原始型来表达。若已经利用先组配型代码将方法信息包含在“操作名称”数据元当中，则无需填写本数据元。</items>
      </items>
      <items code="at0066">
        <items id="text">*Scheduled datetime (en)</items>
        <items id="description">*The date or datetime on which the procedure is intended to be performed. (en)</items>
        <items id="comment">仅仅旨在与“作排程的操作”（Procedure scheduled）路径步骤联合运用。</items>
      </items>
      <items code="at0067">
        <items id="text">操作类型</items>
        <items id="description">此项操作的类型。</items>
        <items id="comment">这一实用性数据元可用于支持实现用户界面之中的内容分类组织。</items>
      </items>
      <items code="at0068">
        <items id="text">操作已开始</items>
        <items id="description">此项操作（或多组成部分操作之中的此项子操作）目前已开始。</items>
      </items>
      <items code="at0069">
        <items id="text">操作难度</items>
        <items id="description">执行此项操作过程中所遇到的困难或问题。</items>
        <items id="comment">示例：患者烦躁不安、胃镜检查前胃排空不充分、胆管内肿瘤导致内镜无法通过。</items>
      </items>
      <items code="at0070">
        <items id="text">适应证</items>
        <items id="description">此项操作的临床原因/理由或流程相关原因/理由。</items>
        <items id="comment">*For example: 'Failed bowel preparation' or 'Bowel cancer screening'. Coding of the 'Indication' with a terminology is recommended, if available.  This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0071">
        <items id="text">*DV_TEXT (en)</items>
        <items id="description" />
      </items>
      <items code="at0072">
        <items id="text">*Intent (en)</items>
        <items id="description">*The intended outcome of the procedure. (en)</items>
        <items id="comment">*For example: An operation with curative intent may be planned, while during the operation it is discovered that curative treatment is not possible and the operation is carried out with a palliative intent instead. Coding of the 'Intent' with a terminology is recommended, if available. This data element allows multiple occurrences to enable the user to record multiple responses, if required. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Start datetime (en)</items>
        <items id="description">*The date or datetime when the entire procedure, or the first component of a multicomponent procedure, was first started. (en)</items>
        <items id="comment">*For example: the knife to skin time. Only for use in association with the 'Procedure performed', 'Procedure suspended', 'Procedure aborted' or 'Procedure completed' pathway steps. This may be the same as the RM 'time' attribute for the 'Procedure commenced' pathway step. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Pathway step duration (en)</items>
        <items id="description">*The duration of time between the start of the most recent pathway step for this procedure and the start of the current pathway step. (en)</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
