<?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, Oslo Universitetssykehus, Norway</other_contributors>
    <other_contributors>Tomas Alme, DIPS, Norway</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway</other_contributors>
    <other_contributors>Koray Atalag, University of Auckland, New Zealand</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Kari Beate Engseth, Finnmarkssykehuset HF + Klinikk Kirkenes, Norway</other_contributors>
    <other_contributors>Maria Beate Nupen, Oslo Universitetssykehus, Norway</other_contributors>
    <other_contributors>Lars Bitsch-Larsen, Haukeland University hospital, Norway</other_contributors>
    <other_contributors>Fredrik Borchsenius, Oslo universitetssykehus, Norway</other_contributors>
    <other_contributors>Diego Bosca, IBIME group, Spain</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>David Evans, Queensland Health, Australia</other_contributors>
    <other_contributors>Shahla Foozonkhah, Iran ministry of health and education, Iran</other_contributors>
    <other_contributors>Einar Fosse, National 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>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 Ivar Mehlum, Helse Bergen HF, Norway</other_contributors>
    <other_contributors>Lars Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Lars Morgan Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Mary Kelaher, NEHTA, Australia</other_contributors>
    <other_contributors>Shinji Kobayashi, Kyoto University, Japan</other_contributors>
    <other_contributors>Sabine Leh, Haukeland University Hospital, Department of Pathology, Norway</other_contributors>
    <other_contributors>Heather Leslie, Ocean Health Systems, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Hugh Leslie, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Hallvard Lærum, Oslo University Hospital, 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>Chris Mitchell, RACGP, Australia</other_contributors>
    <other_contributors>Stewart Morrison, NEHTA, Australia</other_contributors>
    <other_contributors>Bjoern Naess, DIPS ASA, Norway</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Michael Osborne, Mater Health Services, Australia</other_contributors>
    <other_contributors>Anne Pauline Anderssen, Helse Nord RHF, Norway</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>Jussara Rotzsch, UNB, Brazil</other_contributors>
    <other_contributors>Peter Scott, Australia</other_contributors>
    <other_contributors>Elizabeth Stanick, Hobart Anaesthetic Group, Australia</other_contributors>
    <other_contributors>Norwegian Review Summary, Nasjonal IKT HF, Norway</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 Bergen, 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>John Tore Valand, Haukeland Universitetssjukehus, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Richard Townley-O'Neill, NEHTA, Australia</other_contributors>
    <other_contributors>Ørjan Vermeer, Haukeland Universitetssjukehus, Kvinneklinikken, Norway</other_contributors>
    <other_contributors>Ivar Yrke, DIPS AS, Norway</other_contributors>
    <lifecycle_state>in_development</lifecycle_state>
    <other_details id="licence">This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.</other_details>
    <other_details id="custodian_organisation">HiGHmed</other_details>
    <other_details id="references">Procedure, Draft Archetype [Internet]. National eHealth Transition Authority, Australia, NEHTA Clinical Knowledge Manager [cited: 2015-03-21]. Available from: http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.936.</other_details>
    <other_details id="current_contact">Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com</other_details>
    <other_details id="original_namespace">org.highmed</other_details>
    <other_details id="original_publisher">HiGHmed</other_details>
    <other_details id="custodian_namespace">org.highmed</other_details>
    <other_details id="MD5-CAM-1.0.1">D05271784555B61534B1CA8EBB6DC6F1</other_details>
    <other_details id="build_uid">d25bfd4b-733d-4238-a3cf-079adbe5d933</other_details>
    <other_details id="revision">0.0.1-alpha</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>© openEHR Foundation, HiGHmed</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, HiGHmed</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, HiGHmed</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, HiGHmed</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, HiGHmed</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, HiGHmed</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, HiGHmed</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Para registrar información sobre las actividades requeridas para ejecutar un procedimiento, incluyendo planificación, coordinación, ejecución, suspensión, cancelación, documentación y finalización.</purpose>
      <keywords>procedimiento</keywords>
      <keywords>intervención</keywords>
      <keywords>terapia</keywords>
      <keywords>cirugía</keywords>
      <keywords>diagnóstico</keywords>
      <keywords>evaluación</keywords>
      <keywords>curación</keywords>
      <keywords>tratamiento</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 para la evaluación, investigación, detección, diagnóstico,&#xD;
curativos, terapéuticos o fines paliativos. Los ejemplos van desde las actividades relativamente simples, como la inserción de una cánula intravenosa, hasta operaciones quirúrgicas complejas.</use>
      <misuse>No utilizar para registrar detalles acerca de la anestesia, para eso utilizar un arquetipo de ACTION separado.&#xD;
No utilizar para registrar detalles acerca de estudios por imágenes, para eso utilizar el arquetipo ACTION.imaging_exam.&#xD;
No utilizar para registrar detalles acerca de estudios de laboratorio, para eso utilizar el arquetipo ACTION.laboratory_test.&#xD;
No utilizar para registrar detalles acerca de educación brindada, para eso utilizar el arquetipo ACTION.health_education.&#xD;
No utilizar para registrar detalles acerca de actividades administrativas, para eso utilizar un arquetipo ADMIN separado.&#xD;
No utilizar para registrar detalles acerca de actividades relacionadas, como medicación administrada durante el procedimiento, o sobre imágenes que se utilizaron como guía durante el procedimiento, para esto utilizar arquetipos de ACTION separados, dentro de la misma plantilla.&#xD;
No utilizar para registrar detalles acerca del informe de la operación, para eso se debe utilizar una plantilla donde este arquetipo sea parte de la misma.</misuse>
      <copyright>© openEHR Foundation, HiGHmed</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</author>
    <author id="organisation">MHH</author>
    <author id="email">sommer.kimkatrin@mh-hannover.de</author>
  </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>nb</code_string>
    </language>
    <author id="name">John Tore Valand / Silje Ljosland Bakke</author>
    <author id="organisation">Helse Bergen HF / Nasjonal IKT HF</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>es</code_string>
    </language>
    <author id="name">Pablo Pazos</author>
    <author id="organisation">CaboLabs</author>
    <author id="pablo.pazos@cabolabs.com">pablo.pazos@cabolabs.com</author>
    <author id="email">pablo.pazos@cabolabs.com</author>
    <accreditation>Computer Engineer</accreditation>
  </translations>
  <uid>
    <value>d7824784-5773-43c1-88d8-e26da7cef189</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-ACTION.umg_procedure.v0</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>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_clock(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_clock(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v1</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </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_BOOLEAN</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <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>BOOLEAN</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_BOOLEAN">
                      <true_valid>true</true_valid>
                      <false_valid>false</false_valid>
                    </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>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_BOOLEAN</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <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>BOOLEAN</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_BOOLEAN">
                      <true_valid>true</true_valid>
                      <false_valid>false</false_valid>
                    </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>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_BOOLEAN</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <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>BOOLEAN</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_BOOLEAN">
                      <true_valid>true</true_valid>
                      <false_valid>false</false_valid>
                    </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>
              <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>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="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\.multimedia(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.multimedia(-[a-zA-Z0-9_]+)*\.v1</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <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>
          <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>
          <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">Código do procedimento específico com uma terminologia é preferível , quando possível.</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">Comentários adicionais sobre a atividade ou etapas não informados em outros campos.</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">Utilize este elemento de dados para gravar termos simples ou complicações . Se as condições de gravação de complicação são mais complexas, é aconselhado usar de um arquétipo CLUSTER específico dentro do campo "Detalhes do Procedimento" neste arquétipo e este elemento de dados torna-se redundante.</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">Utilização de terminologia para a codificação é desejável, quando possível.</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">Codificação do procedimento é preferível, quando possível.</items>
      </items>
      <items code="at0060">
        <items id="text">Data final / hora</items>
        <items id="description">A data e/ou hora , quando todo o processo , ou o último componente de um procedimento de múltiplas etapas , foi finalizada.</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">Informações adicionais necessárias para capturar o conteúdo local ou para se alinhar com outros modelos / formalismos de referência</items>
        <items id="comment">Por exemplo : requisitos de informação locais ou metadados adicionais para alinhar com FHIR ou equivalentes CIMI.</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">Agendamento data/hora</items>
        <items id="description">A data e /ou hora em que o processo está previsto para ocorrer.</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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(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 specific procedure with a terminology is preferred, where possible.(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 activity 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. 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 with a terminology is preferred, where possible.(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 with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0060">
        <items id="text">*Final end date/time(en)</items>
        <items id="description">*The date and/or time 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 capture local content or to align with other reference models/formalisms.(en)</items>
        <items id="comment">*For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.(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 date/time(en)</items>
        <items id="description">*The date and/or time 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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(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 specific procedure with a terminology is preferred, where possible.</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 activity 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. 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. Examples: Hematuria after a kidney biopsy, tissue irritation after insertion of intravenous catheter.</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 with a terminology is preferred, where possible.</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 with a terminology is preferred, where possible.</items>
      </items>
      <items code="at0060">
        <items id="text">Final end date/time</items>
        <items id="description">The date and/or time 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 capture local content or to align with other reference models/formalisms.</items>
        <items id="comment">For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.</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 date/time</items>
        <items id="description">The date and/or time 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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</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 specific procedure with a terminology is preferred, where possible.(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 activity 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. 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 with a terminology is preferred, where possible.(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 with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0060">
        <items id="text">*Final end date/time(en)</items>
        <items id="description">*The date and/or time 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 capture local content or to align with other reference models/formalisms.(en)</items>
        <items id="comment">*For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.(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 date/time(en)</items>
        <items id="description">*The date and/or time 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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(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 specific procedure with a terminology is preferred, where possible.(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 activity 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. 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 with a terminology is preferred, where possible.(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 with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0060">
        <items id="text">*Final end date/time(en)</items>
        <items id="description">*The date and/or time 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 capture local content or to align with other reference models/formalisms.(en)</items>
        <items id="comment">*For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.(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 date/time(en)</items>
        <items id="description">*The date and/or time 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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(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 bør om mulig benyttes terminologi for å angi prosedyrenavnet.</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 fritekstbeskrivelse av aktivitet eller prosesstrinn 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. Dersom registreringskravene for komplikasjoner er mer komplekse er det anbefalt å bruke en spesifikk CLUSTER-arketype i SLOTet "Prosedyredetaljer" i denne arketypen, og i disse tilfellene blir dette dataelementet overflødig. Eksempler: Hematuri etter nyrebiopsi, vevsirritasjon etter innleggelse av venekateter.</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">Koding med en terminologi er ønskelig, 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">Koding med en terminologi er ønskelig, om mulig.</items>
      </items>
      <items code="at0060">
        <items id="text">Dato/tid for avslutning av prosedyren</items>
        <items id="description">Datoen og/eller tiden da hele eller den siste av komponentene i en kompleks prosedyre 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 referansemodellens "time"-atributt for prosesssteget "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 er nødvendig for å sammenstille med andre referansemodeller/formalismer.</items>
        <items id="comment">F.eks. lokale informasjonskrav eller ekstra metadata for å samsvare med FHIR eller CIMI ekvivalenter.</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 dato/tid</items>
        <items id="description">Dato/tid når prosedyren er planlagt utført.</items>
        <items id="comment">Kun til bruk i forbindelse med prosesstrinnet "Prosedyre planlagt".</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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Procedimiento</items>
        <items id="description">Una actividad clínica llevada a cabo para la detección, investigación, diagnóstico, curativos, terapéuticos, de evaluación o con fines 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">Nombre del procedimiento</items>
        <items id="comment">*Coding of the specific procedure with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">Detalles</items>
        <items id="description">Información estructurada de los detalles del procedimiento</items>
        <items id="comment">*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">Comentario</items>
        <items id="description">Comentario narrativo adicional acerca de las actividades llevadas a cabo en la ejecución del procedimiento y que no son capturadas por otros campos</items>
      </items>
      <items code="at0006">
        <items id="text">Complicación</items>
        <items id="description">Detalles de cualquier complicación surgida durante la ejecución del procedimiento</items>
        <items id="comment">*Use this data element to record simple terms or precoordinated complications. 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">Motivo</items>
        <items id="description">Motivo por el cual una actividad o paso de la vía clínica del arquetipo fue ejecutado como parte del procedimiento</items>
        <items id="comment">Por ejemplo: motivo de cancelación o suspensión del procedimiento</items>
      </items>
      <items code="at0034">
        <items id="text">Procedimiento planificado</items>
        <items id="description">Está previsto que el procedimiento que se ha llevado a cabo.</items>
      </items>
      <items code="at0035">
        <items id="text">Solicitud de procedimiento enviada</items>
        <items id="description">Solicitud de procedimiento enviada</items>
      </items>
      <items code="at0036">
        <items id="text">Procedimiento coordinado</items>
        <items id="description">Procedimiento coordinado</items>
      </items>
      <items code="at0038">
        <items id="text">Procedimiento pospuesto</items>
        <items id="description">Procedimiento pospuesto</items>
      </items>
      <items code="at0039">
        <items id="text">Procedimiento cancelado</items>
        <items id="description">Procedimiento cancelado antes de comenzar</items>
      </items>
      <items code="at0040">
        <items id="text">Procedimiento suspendido</items>
        <items id="description">Procedimiento suspendido</items>
      </items>
      <items code="at0041">
        <items id="text">Procedimiento interrumpido</items>
        <items id="description">Procedimiento interrumpido</items>
      </items>
      <items code="at0043">
        <items id="text">Procedimiento completado</items>
        <items id="description">Procedimiento completado</items>
      </items>
      <items code="at0047">
        <items id="text">Procedimiento realizado</items>
        <items id="description">Procedimiento realizado</items>
      </items>
      <items code="at0048">
        <items id="text">Resultado</items>
        <items id="description">Resultado del procedimiento realizado</items>
        <items id="comment">*Coding with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0049">
        <items id="text">Descripción</items>
        <items id="description">Descripción narrativa del procedimiento</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">Solicitante</items>
        <items id="description">Detalles del proveedor de salud que solicita la realización del procedimiento</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">Receptor</items>
        <items id="description">Detalles sobre el profesional, departamento u organización que debe realizar el procedimiento</items>
      </items>
      <items code="at0058">
        <items id="text">Urgencia</items>
        <items id="description">Urgencia del procedimiento</items>
        <items id="comment">*Coding with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0060">
        <items id="text">Fecha de finalización</items>
        <items id="description">Fecha y hora cuando el procedimiento fue finalizado en su totalidad</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">Duración</items>
        <items id="description">Cantidad total de tiempo que tomó la ejecución del procedimiento.</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</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">*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">Extensión</items>
        <items id="description">Información adicional requerida para capturar contenido local o alinear el arquetipo a otros modelos o formalismos</items>
        <items id="comment">*For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.(en)</items>
      </items>
      <items code="at0065">
        <items id="text">Método</items>
        <items id="description">Identificación del método o técnica específica para el procedimiento</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">Fecha coordinada</items>
        <items id="description">Fecha y hora en el cual se coordinó la realización del procedimiento</items>
        <items id="comment">Utilizar solamente para el paso de Procedimiento coordinado de la vía clínica del arquetipo</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">Procedimiento iniciado</items>
        <items id="description">Procedimiento 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">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0071">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0072">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Neues Element(en)</items>
        <items id="description">**(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">UMG_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">Anatomische Lokalisation</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">Typ 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">Belegoperateur</items>
        <items id="description">Wird die Prozedur durch einen Belegoperateur durchgeführt.</items>
        <items id="comment">Bei einem nicht ausgefüllten Feld sollte es möglich sein im späteren Verlauf (ETL,...) "nicht ausgefüllt" mit einer negativen Antwort gleichzusetzen. Dabei darf das Feld natürlich nicht auf "mandatory" gesetzt werden. &#xD;
Sollte das nicht funktionieren muss auch eine negative Antwortmöglichkeit eingefügt werden.</items>
      </items>
      <items code="at0071">
        <items id="text">Beleganästhesist</items>
        <items id="description">Wird die Prozedur durch einen Beleganästhesisten durchgeführt.</items>
        <items id="comment">Bei einem nicht ausgefüllten Feld sollte es möglich sein im späteren Verlauf (ETL,...) "nicht ausgefüllt" mit einer negativen Antwort gleichzusetzen. Dabei darf das Feld natürlich nicht auf "mandatory" gesetzt werden. &#xD;
Sollte das nicht funktionieren muss auch eine negative Antwortmöglichkeit eingefügt werden.</items>
      </items>
      <items code="at0072">
        <items id="text">Beleghebamme</items>
        <items id="description">Wird die Prozedur durch eine Beleghebamme durchgeführt. Nur bei eine Haupt- oder Belegabteilung der Frauenheilkunde oder Geburtshilfe möglich.</items>
        <items id="comment">Bei einem nicht ausgefüllten Feld sollte es möglich sein im späteren Verlauf (ETL,...) "nicht ausgefüllt" mit einer negativen Antwort gleichzusetzen. Dabei darf das Feld natürlich nicht auf "mandatory" gesetzt werden. &#xD;
Sollte das nicht funktionieren muss auch eine negative Antwortmöglichkeit eingefügt werden.</items>
      </items>
      <items code="at0073">
        <items id="text">Dokumentationsdatum</items>
        <items id="description">Datum an dem die Prozedur dokumentiert wurde.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
