<?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">2012-12-10</original_author>
    <original_author id="name">Heather Leslie</original_author>
    <original_author id="organisation">Ocean Informatics</original_author>
    <original_author id="email">heather.leslie@oceaninformatics.com</original_author>
    <other_contributors>Nasrin Amele Jamedari, DIPS ASA, Norway</other_contributors>
    <other_contributors>Vebjoern Arntzen, Oslo university hospital, Norway</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo universitetssykehus HF, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Sistine Barretto-Daniels, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Lars Bitsch-Larsen, Haukeland University hospital, Norway</other_contributors>
    <other_contributors>Hanne Marte Bårholm, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway</other_contributors>
    <other_contributors>Heath Frankel, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Mikkel Johan Gaup Grønmo, Helse Nord IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Sam Heard, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Anca Heyd, DIPS ASA, Norway</other_contributors>
    <other_contributors>Hilde Hollås, Norway</other_contributors>
    <other_contributors>Lars Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway</other_contributors>
    <other_contributors>Kanika Kuwelker, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Liv Laugen, Oslo universitetssykehus, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Sabine Leh, Haukeland University Hospital, Department of Pathology, Norway</other_contributors>
    <other_contributors>Heather Leslie, Ocean Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Hugh Leslie, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)</other_contributors>
    <other_contributors>Lars Ivar Mehlum, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Jussara Rotzsch, UNB, Brazil</other_contributors>
    <other_contributors>Terje Sagmyr, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Annette Hole Sjøborg, DIPS ASA, Norway</other_contributors>
    <other_contributors>Jon Tysdahl, Furst medlab AS, Norway</other_contributors>
    <other_contributors>John Tore Valand, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway (Nasjonal IKT redaktør)</other_contributors>
    <lifecycle_state>published</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">openEHR Foundation</other_details>
    <other_details id="references">Avgrenet fra: Procedure report, Published archetype [Internet]. openEHR Foundation, openEHR Clinical Knowledge Manager [cited: 2023-07-11]. Available from: https://ckm.openehr.org/ckm/archetypes/1013.1.1322</other_details>
    <other_details id="current_contact">Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com</other_details>
    <other_details id="original_namespace">org.openehr</other_details>
    <other_details id="original_publisher">openEHR Foundation</other_details>
    <other_details id="custodian_namespace">org.openehr</other_details>
    <other_details id="MD5-CAM-1.0.1">D831E6F008D61BBAEEEA0970D8CFBB46</other_details>
    <other_details id="build_uid">dcc9f73b-c53d-4a2d-8bff-6fa920e98857</other_details>
    <other_details id="revision">1.0.1</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Ein generischer Container-Archetyp zur Speicherung von Informationen über jede eigenständige Prozedur oder durchgeführte Operation.</purpose>
      <keywords>Bericht</keywords>
      <keywords>Prozedur</keywords>
      <keywords>Operation</keywords>
      <keywords>Verfahren</keywords>
      <keywords>Ablauf</keywords>
      <keywords>Vorgang</keywords>
      <use>Diesen Archetypen als generischer verfahrensbezogener Archetyp verwenden, um Informationen über jedes eigenständige Verfahren oder jede durchgeführte Operation aufzuzeichnen.&#xD;
&#xD;
Voraussichtlich wird jeder Archetyp des COMPOSITION.Bericht-Prozedur mindestens ein ACTION.Prozedur (oder ein verwandter Archetyp) beinhalten. Je nach Komplexität des Verfahrens kann es eine Vielzahl anderer Archetypen enthalten. Zum Beispiel Archetypen zur Darstellung der damit verbundenen Anästhesie- oder Bildgebungsaktivitäten, die während des Eingriffs durchgeführt wurden.&#xD;
&#xD;
Häufige Anwendungsfälle sind: &#xD;
- jedes Verfahren, das nicht als Teil einer Konsultation aufgezeichnet wird, sondern als eigenständige Aktivität durchgeführt werden muss; &#xD;
- Endoskopie-Bericht; bis hin zu einem &#xD;
- vollständiger Operationsbericht für eine Laparatomie oder einen Gelenkersatz.&#xD;
&#xD;
Die Erfassung des Anästhetikums, das zur Abdeckung des Eingriffs verwendet wurde, wird anhand von zweckgebundenen Archetypen dokumentiert. Sie können gleichzeitig mit dem Verfahrensbericht in die Gesundheitsakte aufgenommen werden und zwar höchstwahrscheinlich auf eine von zwei Arten:&#xD;
- in einem separaten Anästhesiebericht. Dies gilt am ehesten, wenn die Anästhesie von einem anderen Arzt als dem ausführenden Arzt verabreicht wurde; oder&#xD;
- im gleichen Prozedurenbericht wie die Prozedur aufgezeichnet wurde. Dies gilt am ehesten, wenn die Narkose von demselben Arzt verabreicht wurde, der den Eingriff durchgeführt hat.&#xD;
&#xD;
Die Sections-Komponente wurde bewusst frei gelassen, um die Wiederverwendung dieses Archetyps zu optimieren.</use>
      <misuse>Nicht für Berichte zu verwenden, die nicht mit einem Verfahren in Zusammenhang stehen. Hierfür verwenden Sie den generischen COMPOSITION.Bericht oder ggf. zweckgebundene COMPOSITIONs.&#xD;
&#xD;
Nicht für Prozeduren zu verwenden, die als Teil eines Konsultationsvermerks aufgezeichnet werden, z.B. die Entfernung einer Hautläsion in einer Erstversorgungsberatung. Hierfür verwenden Sie einen ACTION.Prozedur Archetyp innerhalb des COMPOSITION.Kontakt.&#xD;
&#xD;
Nicht für Prozeduren zu verwenden, die als Teil einer Pflegefortschrittsanzeige dokumentiert werden, z. B. Einführen eines Katheters. Hierfür verwenden Sie einen ACTION.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fi</code_string>
      </language>
      <purpose>*Generic container archetype to carry information that needs to be shared with others.(en)</purpose>
      <keywords>*report(en)</keywords>
      <use>*Use as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>En generell behållare för information som behöver delas med andra.</purpose>
      <keywords>rapport</keywords>
      <use>Används som en generell arketyp för information som behöver delas med andra.&#xD;
&#xD;
Vanliga användningsfall är att dokumentera ett svar på en förfrågan om information, resultatet av ett test, aktiviteter som har utförts, eller händelser som har inträffat.&#xD;
&#xD;
Rapporten kan fyllas med alla SECTION- eller ENTRY-arketyper som är lämpliga för det kliniska syftet i en mall.</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ko</code_string>
      </language>
      <purpose>다른 사람들과 공유될 필요가 있는 정보를 운반하기 위한 일반적인 컨테이너 아키타입</purpose>
      <keywords>리포트</keywords>
      <use>*Use as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Arquétipo genérico para carregar informações sobre procedimentos isolados ou cirurgia realizada.</purpose>
      <keywords>relatório</keywords>
      <keywords>procedimento</keywords>
      <keywords>cirurgia</keywords>
      <keywords>operação</keywords>
      <use>Use como um arquétipo relacionado com o procedimento genérico para levar informações sobre qualquer procedimento isolado ou operação realizada.&#xD;
&#xD;
Prevê-se que cada arquétipo-COMPOSITION.report procedimento irá conter, pelo menos, um ACTION.procedure (ou arquétipo relacionados) mas, dependendo da complexidade do processo pode incluir uma variedade de outros arquétipos, dependendo da natureza e complexidade do procedimento executado . Por exemplo, os arquétipos para descrever as atividades anestésicas ou de imagem associadas realizadas durante o procedimento.&#xD;
&#xD;
Casos de uso comuns:&#xD;
- Qualquer procedimento que não é registrado como parte de uma consulta, mas precisa ser registrado como uma atividade isolada realizada;&#xD;
- Relatório Endoscopia; através de um&#xD;
- Completar Relatório de Cirurgia para uma laparotomia ou substituição da articulação.&#xD;
&#xD;
Gravação do anestésico usado em um procedimento será gravado utilizando arquétipos de propósito específico. Eles podem ser acrescentados ao registro de saúde, ao mesmo tempo que o relatório do procedimento, provavelmente em uma de duas maneiras:&#xD;
- Em um relatório de anestesia separado. Isto é o mais provável, se o anestésico é administrado por um médico diferente que realiza o procedimento; ou&#xD;
- No mesmo relatório do procedimento gravado. Isto é o mais provável, se o anestésico foi administrado pelo mesmo médico que realizou o procedimento.&#xD;
&#xD;
O componente Section foi deliberadamente deixado sem restrições para maximizar a reutilização deste arquétipo</use>
      <misuse>Não deve ser usado para relatórios que não estão relacionados a um procedimento. Use o arquétipo genérico COMPOSITION.report ou composições específicas de uso, conforme apropriado.&#xD;
&#xD;
Não deve ser utilizado para procedimentos que são gravadas como parte de uma nota de consulta, por exemplo, a remoção de uma lesão de pele em uma consulta na assistência básica - usar um arquétipo ACTION.procedure dentro do COMPOSITION.encouter para esta finalidade.&#xD;
&#xD;
Não deve ser utilizado para procedimentos que são gravadas como parte de uma nota progresso de enfermagem, por exemplo a inserção de um catéter - usar um arquétipo ACTION.procedure dentro do COMPOSITION.progress_note.</misuse>
      <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 as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>Generic container archetype to carry information about any stand-alone procedure or operation performed.</purpose>
      <keywords>report</keywords>
      <keywords>procedure</keywords>
      <keywords>operation</keywords>
      <use>Use as a generic procedure-related archetype to carry information about any stand-alone procedure or operation performed. &#xD;
&#xD;
It is anticipated that each COMPOSITION.report-procedure archetype will contain at least one ACTION.procedure (or related archetype) but depending on the complexity of the procedure it may contain a variety of other archetypes depending on the nature and complexity of the procedure performed. For example, archetypes to describe the associated anaesthetic or imaging activities carried out during the procedure.&#xD;
&#xD;
Common use cases are: &#xD;
- any procedure that is not recorded as part of a consultation but needs to be carried out recorded as a stand-alone activity; &#xD;
- Endoscopy Report; through to a &#xD;
- complete Operation Report for an laparotomy or joint replacement.&#xD;
&#xD;
Record of the anaesthetic used to cover the procedure will be recorded using purpose-specific archetypes. They can be committed to the health record at the same time as the Procedure report, most likely in one of two ways:&#xD;
- in a separate Anaesthetic report. This is most likely if the anaesthetic is administered by a separate clinician to the one performing the procedure; or&#xD;
- in the same Procedure report as the procedure is recorded. This is most likely if the anaesthetic was administered by the same clinician who performed the procedure.&#xD;
&#xD;
The Sections component has been deliberately left unconstrained to maximise re-use of this archetype.</use>
      <misuse>Not to be used for reports that are not related to a procedure. Use the generic COMPOSITION.report or purpose specific COMPOSITIONs as appropriate.&#xD;
&#xD;
Not to be used for procedures that are recorded as part of a consultation note, for example removal of a skin lesion in a primary care consultation - use a ACTION.procedure archetype inside the COMPOSITION.encouter for this purpose.&#xD;
&#xD;
Not to be used for procedures that are recorded as part of a nursing progress note, for example insertion of a catheter - use an ACTION.procedure archetype inside the COMPOSITION.progress_note.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>it</code_string>
      </language>
      <purpose>Archetipo contenitore generico per veicolare informazioni che devono essere condivise con gli altri.</purpose>
      <keywords>rapporto</keywords>
      <use>*Use as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>zh</code_string>
      </language>
      <purpose>用作携带共享所需信息的通用容器原型。</purpose>
      <keywords>报告</keywords>
      <use>用作携带共享所需信息的通用原型。&#xD;
常见用例是：请求信息的响应记录；测试结果；已进行的活动；或已经发生的事件。&#xD;
主要的Section/Content有意设计为不受约束，从而允许在模板中填充符合临床目的的任何 SECTION 或 ENTRY 原型。</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es-ar</code_string>
      </language>
      <purpose>Arquetipo contenedor genérico para la portación de información que necesita ser compartida con otros.</purpose>
      <keywords>informe</keywords>
      <use>*Use as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>En generisk COMPOSITION-arketype for å lagre informasjon om enkeltstående prosedyrer eller operasjoner som er gjennomført.</purpose>
      <keywords>rapport</keywords>
      <keywords>prosedyre</keywords>
      <keywords>operasjon</keywords>
      <keywords>anestesirapport</keywords>
      <keywords>operasjonsbeskrivelse</keywords>
      <keywords>operasjonsprotokoll</keywords>
      <keywords>prosedyrebeskrivelse</keywords>
      <use>En generisk container-arketype for å lagre informasjon om enkeltstående prosedyrer eller operasjoner som er gjennomført.&#xD;
&#xD;
Det forventes at hver enkelt COMPOSTION.report_procedure inneholder minst en ACTION.procedure (eller beslektet arketype), men den kan også inneholde en stor variasjon av andre arketyper avhengig av kompleksiteten av prosedyren som er gjennomført. For eksempel: arketyper som omhandler aktiviteter knyttet til anestesi eller radiologi gjennomført under prosedyren.&#xD;
&#xD;
Vanlige bruksområder: &#xD;
- Rapport etter prosedyrer som utføres som selvstendige aktiviteter, og som ikke inngår i en ordinær konsultasjon.&#xD;
- Alt fra en endoskopirapport til en komplett operasjonsbekrivelse for en laparatomi eller utskifting av et hofteledd.&#xD;
&#xD;
Innholdet i arketypen er bevisst ubegrenset, slik at alle SECTION- og/eller ENTRY-arketyper som er nødvendig/hensiktsmessig i den aktuelle kliniske konteksten kan brukes i templaten.</use>
      <misuse>Brukes ikke for å dokumentere rapporter som ikke er relatert til en prosedyre. Bruk den generiske COMPOSTION.report eller en spesfikk COMPOSITON-arketype for dette formålet.&#xD;
&#xD;
Brukes ikke for prosedyrer som er dokumentert som del av et konsultasjonsnotat. For eksempel fjerning av en hudlesjon under en konsultasjon i primærhelsetjenesten. Bruk arketypen ACTION.procedure i arketypen COMPOSITION.encouter for dette formålet.&#xD;
&#xD;
Brukes ikke for å registrere prosedyrer som er en del av et sykepleienotat, for eksempel innleggelse av urinkateter. Bruk ACTION.procedure i arketypen COMPOSTION.progess_note for dette formålet.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sl</code_string>
      </language>
      <purpose>*Generic container archetype to carry information that needs to be shared with others.(en)</purpose>
      <keywords>*report(en)</keywords>
      <use>*Use as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nl</code_string>
      </language>
      <purpose>Generiek containerarchetype om informatie over te dragen die met anderen moet worden gedeeld.</purpose>
      <keywords>rapportage</keywords>
      <use>*Use as a generic archetype to carry information that needs to be shared with others, where no specialised archetype for a specific report type exists.&#xD;
&#xD;
Common use cases are: documenting a response to a request for information; the outcome of testing; activities that have been performed; or events that have occurred.&#xD;
&#xD;
The main Sections/Content component has been deliberately left unconstrained. This will allow it to be populated with any SECTION or ENTRY archetypes appropriate for the clinical purpose within a template. (en)</use>
      <misuse />
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Sarah Ballout</author>
    <author id="organisation">MHH-Hannover</author>
    <author id="email">ballout.sarah@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fi</code_string>
    </language>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Sofia Janstad, Åsa Skagerhult</author>
    <author id="organisation">SLL, Region Östergötland</author>
    <author id="email">sofia.lang-janstad@sll.se, asa.skagerhult@regionostergotland.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Vebjørn Arntzen; John Tore Valand</author>
    <author id="organisation">Oslo univeristetsykehus HF; Helse Bergen HF</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es-ar</code_string>
    </language>
    <author id="name">Alan March</author>
    <author id="organisation">Hospital Universitario Austral - Buenos Aires - Argentina</author>
    <author id="email">alandmarch@gmail.com</author>
    <accreditation>physician</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ko</code_string>
    </language>
    <author id="name">Seung-Jong Yu</author>
    <author id="organisation">InfoClinic Co.,Ltd.</author>
    <author id="email">seungjong.yu@gmail.com</author>
    <accreditation>Certified Board of Family Medicine in South Korea</accreditation>
  </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 - SP</author>
    <author id="email">osmeire.acsanzovo@hsl.org.br</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sl</code_string>
    </language>
    <author id="name">?</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>it</code_string>
    </language>
    <author id="name">Francesca Frexia</author>
    <author id="organisation">CRS4 - Center for advanced studies, research and development in Sardinia, Pula (Cagliari), Italy</author>
    <author id="email">francesca.frexia@crs4.it</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nl</code_string>
    </language>
    <author id="name">Pieter Bos, Jelte Zeilstra</author>
    <author id="organisation">Nedap Healthcare</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>zh</code_string>
    </language>
    <author id="name">Yexuan Cheng</author>
    <author id="organisation">浙江大学</author>
    <author id="email">3160100913@zju.edu.cn</author>
  </translations>
  <uid>
    <value>128eff7a-e791-40dc-8989-488645a16e62</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-COMPOSITION.report-procedure.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000.1</concept>
  <parent_archetype_id>
    <value>openEHR-EHR-COMPOSITION.report.v1</value>
  </parent_archetype_id>
  <definition>
    <rm_type_name>COMPOSITION</rm_type_name>
    <occurrences>
      <lower_included>true</lower_included>
      <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.1</node_id>
    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
      <rm_attribute_name>category</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>433</code_list>
          </children>
        </attributes>
      </children>
    </attributes>
    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
      <rm_attribute_name>context</rm_attribute_name>
      <existence>
        <lower_included>true</lower_included>
        <upper_included>true</upper_included>
        <lower_unbounded>false</lower_unbounded>
        <upper_unbounded>false</upper_unbounded>
        <lower>0</lower>
        <upper>1</upper>
      </existence>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>EVENT_CONTEXT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <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>other_context</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>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>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0002</node_id>
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>value</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>0</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>DV_TEXT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                  </children>
                </attributes>
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>ELEMENT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>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>
              <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>at0006</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/.*/}</string_expression>
                  <expression xsi:type="EXPR_BINARY_OPERATOR">
                    <type>Boolean</type>
                    <operator>2007</operator>
                    <precedence_overridden>false</precedence_overridden>
                    <left_operand xsi:type="EXPR_LEAF">
                      <type>String</type>
                      <item xsi:type="xsd:string">archetype_id/value</item>
                      <reference_type>attribute</reference_type>
                    </left_operand>
                    <right_operand xsi:type="EXPR_LEAF">
                      <type>C_STRING</type>
                      <item xsi:type="C_STRING">
                        <pattern>.*</pattern>
                      </item>
                      <reference_type>constraint</reference_type>
                    </right_operand>
                  </expression>
                </includes>
              </children>
              <cardinality>
                <is_ordered>false</is_ordered>
                <is_unique>false</is_unique>
                <interval>
                  <lower_included>true</lower_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </interval>
              </cardinality>
            </attributes>
          </children>
        </attributes>
      </children>
    </attributes>
  </definition>
  <ontology>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Report</items>
        <items id="description">Document to communicate information to others, commonly in response to a request from another party.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Procedure report</items>
        <items id="description">Document to communicate information to others about any stand-alone procedure or operation performed.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Report ID</items>
        <items id="description">Identification information about the report.</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">The status of the entire report. Note: This is not the status of any of the report components.</items>
      </items>
      <items code="at0006">
        <items id="text">Extension</items>
        <items id="description">Additional information required to capture local context 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>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000.1">
        <items id="text">Prosedyrerapport</items>
        <items id="description">Dokument for å kommunisere informasjon om enkeltstående prosedyrer eller operasjoner som er utført.</items>
      </items>
      <items code="at0000">
        <items id="text">Rapport</items>
        <items id="description">Dokument som brukes for å kommunisere informasjon til andre, ofte som svar på en forespørsel.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Rapport ID</items>
        <items id="description">Informasjon som identifiserer rapporten.</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">Status for hele rapporten. Merk: Dette er ikke statusen for noen av enkeltkomponentene i rapporten.</items>
      </items>
      <items code="at0006">
        <items id="text">Tilleggsinformasjon</items>
        <items id="description">Ytterligere informasjon som trengs for å kunne registrere lokalt definert innhold eller for å tilpasse til andre referansemodeller/formalismer.</items>
        <items id="comment">For eksempel lokale informasjonsbehov eller ytterligere metadata for å kunne tilpasse til tilsvarende konsepter i FHIR eller CIMI.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Relatório</items>
        <items id="description">Documento para comunicar informações a outros, comumente em resposta a uma solicitação de terceiros.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Relatório do procedimento</items>
        <items id="description">Documento para comunicar informações aos outros sobre qualquer procedimento isolado ou operação executada.</items>
      </items>
      <items code="at0002">
        <items id="text">Identificador do relatório</items>
        <items id="description">Informação de identificação sobre o relatório.</items>
      </items>
      <items code="at0005">
        <items id="text">Estado</items>
        <items id="description">O estado de todo o relatório. Nota: este não é o estado de qualquer dos componentes do relatório.</items>
      </items>
      <items code="at0006">
        <items id="text">Extensão</items>
        <items id="description">Informação adicional requerida para capturar o contexto local ou para alinhar a outros modelos de referência/formalismos.</items>
        <items id="comment">Por exemplo: requisitos de informações locais ou metadados para alinhar com equivalentes do FHIR or CIMI.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Bericht</items>
        <items id="description">Ein Dokument zur Übermittlung von Informationen an andere, meist als Antwort auf eine Anfrage.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Verfahrensbericht</items>
        <items id="description">Ein Dokument, um Informationen über jedes eigenständige Verfahren oder jeden durchgeführten Vorgang zu übermitteln.</items>
      </items>
      <items code="at0002">
        <items id="text">Bericht ID</items>
        <items id="description">Identifizierungsmerkmal des Berichts.</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">Der Status des gesamten Berichts. Hinweis: Dies ist nicht der Status einer Berichtskomponente.</items>
      </items>
      <items code="at0006">
        <items id="text">Erweiterung</items>
        <items id="description">Zusätzliche Informationen zur Erfassung lokaler Inhalte oder Anpassung an andere Referenzmodelle/Formalismen.</items>
        <items id="comment">Zum Beispiel: lokaler Informationsbedarf oder zusätzliche Metadaten zur Anpassung an FHIR-Ressourcen oder CIMI-Modelle.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
    </term_definitions>
    <term_definitions language="ar-sy">
      <items code="at0000">
        <items id="text">تقرير</items>
        <items id="description">وثيقة لتوصيل المعلومات للآخرين, عادة كاستجابة لطلب من طرف آخر.</items>
      </items>
      <items code="at0000.1">
        <items id="text">تقرير</items>
        <items id="description">وثيقة لتوصيل المعلومات للآخرين, عادة كاستجابة لطلب من طرف آخر.</items>
      </items>
      <items code="at0001">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0002">
        <items id="text">العنصر التعريفي الفريد للتقرير</items>
        <items id="description">معلومات التعريف حول التقرير</items>
      </items>
      <items code="at0005">
        <items id="text">الحالة</items>
        <items id="description">حالة التقرير بشكل كلي. و لا تمثل هذه الحالة جزءا من التقرير و إنما جميعه ككل.</items>
      </items>
      <items code="at0006">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to capture local context or to align with other reference models/formalisms.(en)</items>
        <items id="comment">* e.g. Local hospital departmental infomation or additional metadata to align with FHIR or CIMI equivalents.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="sl">
      <items code="at0000">
        <items id="text">Poročilo</items>
        <items id="description">*Document to communicate information to others, commonly in response to a request from another party.(en)</items>
      </items>
      <items code="at0000.1">
        <items id="text">Poročilo</items>
        <items id="description">*Document to communicate information to others, commonly in response to a request from another party.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0002">
        <items id="text">ID Poročila</items>
        <items id="description">*Identification information about the report.(en)</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">*The status of the entire report. Note: This is not the status of any of the report components.(en)</items>
      </items>
      <items code="at0006">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to capture local context or to align with other reference models/formalisms.(en)</items>
        <items id="comment">* e.g. Local hospital departmental infomation or additional metadata to align with FHIR or CIMI equivalents.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="es-ar">
      <items code="at0000">
        <items id="text">Informe</items>
        <items id="description">Documento para comunicar información a otros, comunmente en respuesta a la solicitud de un tercero.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Informe</items>
        <items id="description">Documento para comunicar información a otros, comunmente en respuesta a la solicitud de un tercero.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">ID del informe</items>
        <items id="description">Información para la identificación del informe.</items>
      </items>
      <items code="at0005">
        <items id="text">Estado</items>
        <items id="description">El estado del informe como un todo. Nota: no se refiere al estado de alguno de los componentes del informe.</items>
      </items>
      <items code="at0006">
        <items id="text">*Extension(en)</items>
        <items id="description">*Additional information required to capture local context or to align with other reference models/formalisms.(en)</items>
        <items id="comment">* e.g. Local hospital departmental infomation or additional metadata to align with FHIR or CIMI equivalents.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="ko">
      <items code="at0000">
        <items id="text">*Report(en)</items>
        <items id="description">일반적으로 다른 상대의 요청에 대한 응답으로, 다른 사람들과 정보를 통신하는 문서.</items>
      </items>
      <items code="at0000.1">
        <items id="text">*Report(en)</items>
        <items id="description">일반적으로 다른 상대의 요청에 대한 응답으로, 다른 사람들과 정보를 통신하는 문서.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">*Report ID(en)</items>
        <items id="description">리포트에 대한 식별 정보.</items>
      </items>
      <items code="at0005">
        <items id="text">*Status(en)</items>
        <items id="description">전체 리포트의 상태. 주의: 이것은 리포트 컴포넌트들 중 어떤 부분의 상태가 아님.</items>
      </items>
      <items code="at0006">
        <items id="text">*Extension(en)</items>
        <items id="description">로컬 컨텍스트를 획득하는데 필요하거나 다른 참조 모델/표현과 조정에 필요한 추가 정보</items>
        <items id="comment">예: 로컬 정보 요구사항 또는 FHIR나 CIMI의 동등한 것들과 조정하는 추가 메타데이터</items>
      </items>
    </term_definitions>
    <term_definitions language="fi">
      <items code="at0000">
        <items id="text">Raportti</items>
        <items id="description">Asiakirja tiedon välittämiseksi muille, vastauksena yleensä toisen osapuolen pyyntöön.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Raportti</items>
        <items id="description">Asiakirja tiedon välittämiseksi muille, vastauksena yleensä toisen osapuolen pyyntöön.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Raportti ID</items>
        <items id="description">Raportin tunnistetiedot</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">Koko raportin tila. Huomaa: Tämä ei ole minkään raporttiosien tila.</items>
      </items>
      <items code="at0006">
        <items id="text">Laajennus</items>
        <items id="description">Tarvitaan lisätietoja paikallisen tilanteen mallintamiseksi tai yhdenmukaistamiseksi muiden vertailumallien / muodollisuuksien kanssa.</items>
        <items id="comment">Esimerkiksi: paikalliset tietovaatimukset tai ylimääräiset metatiedot FHIR- tai CIMI-vastaavien mukaisiksi.</items>
      </items>
    </term_definitions>
    <term_definitions language="it">
      <items code="at0000">
        <items id="text">Rapporto</items>
        <items id="description">Documento per comunicare informazioni ad altri, comunemente in risposta ad una richiesta di un altro soggetto.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Rapporto</items>
        <items id="description">Documento per comunicare informazioni ad altri, comunemente in risposta ad una richiesta di un altro soggetto.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">ID del rapporto</items>
        <items id="description">Informazioni di identificazione del rapporto</items>
      </items>
      <items code="at0005">
        <items id="text">Stato</items>
        <items id="description">Lo stato dell'intero rapporto. Nota: Questo non è lo stato di alcuna delle componenti del rapporto.</items>
      </items>
      <items code="at0006">
        <items id="text">Estensione</items>
        <items id="description">Informazioni aggiuntive necessarie per catturare il contesto locale o per allinearsi con altri modelli/formalismi di riferimento.</items>
        <items id="comment">Per esempio: requisiti informativi locali o metadati aggiuntivi per allinearsi con gli equivalenti FHIR o CIMI.</items>
      </items>
    </term_definitions>
    <term_definitions language="nl">
      <items code="at0000">
        <items id="text">Rapportage</items>
        <items id="description">Document om informatie met anderen te communiceren, vaak op verzoek van een andere partij.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Rapportage</items>
        <items id="description">Document om informatie met anderen te communiceren, vaak op verzoek van een andere partij.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Rapportage ID</items>
        <items id="description">Identificerende informatie over deze rapportage.</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">De status van de rapportage. Let op, dit is niet de status van een van de onderdelen van de rapportage.</items>
      </items>
      <items code="at0006">
        <items id="text">Uitbreiding</items>
        <items id="description">Extra informatie nodig om de context te beschrijven of te voldoen aan andere modellen of formalismen.</items>
        <items id="comment">Bijvoorbeeld: lokale informatievereisten of aanvullende metadata om overeen te komen met FHIR- of CIMI-equivalenten.</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Rapport</items>
        <items id="description">Dokument för att förmedla information till andra, vanligen som svar på en begäran från en annan part.</items>
      </items>
      <items code="at0000.1">
        <items id="text">Rapport</items>
        <items id="description">Dokument för att förmedla information till andra, vanligen som svar på en begäran från en annan part.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Rapport-id</items>
        <items id="description">Information som identifierar rapporten.</items>
      </items>
      <items code="at0005">
        <items id="text">Status</items>
        <items id="description">Status för hela rapporten. Observera att detta inte är status för någon av rapportkomponenterna.</items>
      </items>
      <items code="at0006">
        <items id="text">Tilläggsinformation</items>
        <items id="description">Plats för tilläggsinformation som krävs för lokala anpassningar eller anpassning till andra referensmodeller eller formella krav.</items>
        <items id="comment">Exempelvis lokala informationskrav eller metadata för anpassning till FHIR- eller CIMI-motsvarigheter.</items>
      </items>
    </term_definitions>
    <term_definitions language="zh">
      <items code="at0000">
        <items id="text">报告</items>
        <items id="description">用于交流信息的文件，通常是为了响应某一方的请求</items>
      </items>
      <items code="at0000.1">
        <items id="text">报告</items>
        <items id="description">用于交流信息的文件，通常是为了响应某一方的请求</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">报告ID</items>
        <items id="description">关于这份报告的标识信息。</items>
      </items>
      <items code="at0005">
        <items id="text">状态</items>
        <items id="description">整份报告的状态。注意：这不是指报告的任何一个组成部分的状态</items>
      </items>
      <items code="at0006">
        <items id="text">扩展</items>
        <items id="description">用于捕获本地的上下文或与其他参考模型/形式保持一致所需的其他信息。</items>
        <items id="comment">比如：本地的信息需求或是为了与FHIR或CIMI保持一致的其他元数据。</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
