<?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">2019-12-10</original_author>
    <original_author id="name">Heather Leslie</original_author>
    <original_author id="organisation">Atomica Informatics</original_author>
    <original_author id="email">heather.leslie@atomicainformatics.com</original_author>
    <other_contributors>Michael Anywar, Universitätsklinikum SH, Germany</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Paulo Bandiera-Paiva, Federal University of Sao Paulo, Brazil</other_contributors>
    <other_contributors>itai Basel, Private, Israel</other_contributors>
    <other_contributors>SB Bhattacharyya, Sudisa Consultancy Services, India</other_contributors>
    <other_contributors>Stefan Dubois, Dep't of Pathology and Genetics, University Hospitals of Lund and Malmö, Sweden</other_contributors>
    <other_contributors>Grant Forrest, Lunaria Ltd, United Kingdom</other_contributors>
    <other_contributors>Rosane Gotardo, Systema Ltda., Brazil</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Mikkel Johan Gaup Grønmo, Forvaltningssenter EPJ, Helse-Nord, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Joost Holslag, Nedap, Netherlands</other_contributors>
    <other_contributors>Anjali Kulkarni, Karkinos, India</other_contributors>
    <other_contributors>Jörgen Kuylenstierna, eWeave AB, Sweden</other_contributors>
    <other_contributors>Liv Laugen, ​Oslo University Hospital, Norway, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Michael Lutz, BITsoft, Germany</other_contributors>
    <other_contributors>Manisha Mantri, C-DAC, India</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom</other_contributors>
    <other_contributors>Arunakiry Natarajan, medondo, Germany</other_contributors>
    <other_contributors>Mikael Nyström, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Ana Pereira, CINTESIS, CUF-Porto, Portugal</other_contributors>
    <other_contributors>Sidharth Ramesh, Kasturba Medical College, India</other_contributors>
    <other_contributors>FREDERICO RIBEIRO, Hospital das Clínicas da UFPE, Brazil</other_contributors>
    <other_contributors>Saeed Samie, Pars Hospital, Iran</other_contributors>
    <other_contributors>Bjoern Schreiweis, UKSH, Germany</other_contributors>
    <other_contributors>Natalia Strauch, Medizinische Hochschule Hannover, Germany</other_contributors>
    <other_contributors>Norwegian Review Summary, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Nyree Taylor, Ocean Health Systems, Australia</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Michael Zampaglione, Australia</other_contributors>
    <other_contributors>Wouter Zanen, Eurotranplant, Netherlands</other_contributors>
    <other_contributors>Lin Zhang, Taikang Insurance Group, China</other_contributors>
    <lifecycle_state>published</lifecycle_state>
    <other_details id="licence">This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.</other_details>
    <other_details id="custodian_organisation">openEHR Foundation</other_details>
    <other_details id="references">HL7 FHIR Resource - Media v4.0.1 R4 [Internet]. Health Level Seven International; [accessed 2021 Jun 29]. Available from https://www.hl7.org/fhir/media.html.</other_details>
    <other_details id="current_contact">Heather Leslie, Atomica Informatics, heather.leslie@atomicainformatics.com</other_details>
    <other_details id="original_namespace">org.openehr</other_details>
    <other_details id="original_publisher">openEHR Foundation</other_details>
    <other_details id="custodian_namespace">org.openehr</other_details>
    <other_details id="MD5-CAM-1.0.1">2632F7EFC3646C971EA2EEFD11E102A2</other_details>
    <other_details id="build_uid">6ca2141f-e7c3-4662-b792-24bbb53a73a7</other_details>
    <other_details id="revision">1.0.0</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Darstellung einer Mediendatei erworbenen und verwendeten im Bereich des Gesundheitswesens sowie der Informationen zu den zugehörigen Metadaten.</purpose>
      <keywords>Bild</keywords>
      <keywords>Audio</keywords>
      <keywords>Text</keywords>
      <keywords>Video</keywords>
      <keywords>Anwendung</keywords>
      <keywords>Datei</keywords>
      <keywords>Multimedia</keywords>
      <keywords>DICOM</keywords>
      <keywords>digital</keywords>
      <keywords>Dokument</keywords>
      <keywords>Foto</keywords>
      <keywords>Sprachaufnahme</keywords>
      <use>Zur Darstellung einer Mediendatei erworbenen und verwendeten im Bereich des Gesundheitswesens sowie der Informationen zu den zugehörigen Metadaten.&#xD;
&#xD;
Die Absicht dieses Archetyps besteht nur darin, die Mediendatei und die Metadaten, die ihre Erfassung beschreiben, darzustellen. Dieser Archetyp wird in einen anderen Archetyp verschachtelt, normalerweise ein OBSERVATION- oder ACTION-Archetyp, der den Kontext und die Umstände im Zusammenhang mit der Erfassung der Mediendatei enthält. Zum Beispiel werden Details zu Modalität, Ansicht oder Aspekt eines Röntgenbildes und DICOM-Details im Archetyp OBSERVATION.imaging_exam_result dargestellt.&#xD;
&#xD;
Die Beispiele umfassen, sind aber nicht beschränkt auf:&#xD;
- Ein Foto einer Verletzung;&#xD;
- Ein Diagramm der Lokalisation eines bestimmten klinischen Befundes;&#xD;
- Ein digitales Ergebnis der Röntgen- oder CT-Aufnahme;&#xD;
- Eine Audio- oder Videoaufzeichnung eines Interviews;&#xD;
- Gescannte pathologische Schnitte;&#xD;
- Datenausgabe von einem klinischen Gerät, wie z.B. einem EKG-Gerät; oder&#xD;
- Ein gescanntes Bild von handgeschriebenen klinischen Notizen.&#xD;
&#xD;
Das Datenelement „Inhalt“ ermöglicht mithilfe des Multimedia-Datentyps die Erfassung und Speicherung der Mediendatei in der Gesundheitsakte. Der Multimedia-Datentyp hat viele RM-Attribute wie die Dateigröße und URI zu einer externen Quelle. Siehe https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Wenn mehr als eine Mediendatei erfasst wurde, z. B. „Vorher“- und „Nachher“-Bilder einer Wunde, verwenden Sie eine Instanz dieses Archetyps, um jede Mediendatei darzustellen.&#xD;
&#xD;
Wenn eine Reihe von Mediendateien als einzelnes Element dargestellt wird, z. B. ein CT-Scan, kann eine Instanz dieses Archetyps verwendet werden, um einen URI-Pfad zu der Gruppe darzustellen.</use>
      <misuse>Nicht zur Darstellung von Informationen, Lehr- oder Schulungsmaterial verwenden, die außerhalb des Gesundheitsprozesses generiert werden, z. B. Broschüren zur Patientenaufklärung, die dem Patienten oder der Pflegeperson zur Verfügung gestellt werden. Verwenden Sie für diesen Zweck den Archetyp CLUSTER.information_resource.&#xD;
&#xD;
Nicht zur Darstellung von Referenz auf eine externe digitale Ressource, die als Quelle für maßgebliche Informationen oder Experteninformationen verwendet wird. Verwenden Sie für diesen Zweck den Archetyp CLUSTER.knowledge_base_reference.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>*To record a media file that is acquired or used as part of the healthcare process, and details about associated metadata. (en)</purpose>
      <keywords>*image (en)</keywords>
      <keywords>*audio (en)</keywords>
      <keywords>*text (en)</keywords>
      <keywords>*video (en)</keywords>
      <keywords>*application (en)</keywords>
      <keywords>*file (en)</keywords>
      <keywords>*multimedia (en)</keywords>
      <keywords>*audio (en)</keywords>
      <keywords>*DICOM (en)</keywords>
      <keywords>*digital (en)</keywords>
      <keywords>*document (en)</keywords>
      <keywords>*photo (en)</keywords>
      <keywords>*voice (en)</keywords>
      <use>*Use to record a media file that is acquired or used as part of the healthcare process, and details about associated metadata.&#xD;
&#xD;
The intent of this archetype is only to hold the media file and the metadata describing its capture. This archetype will be nested within another archetype, usually an OBSERVATION or ACTION that will hold the context and circumstances related to the capture of the media file. For example, details about the modality, view or aspect of a radiographic image and DICOM details will be captured within the OBSERVATION.imaging_exam_result archetype. &#xD;
&#xD;
Examples include, but are not limited to:&#xD;
- A photo of an injury;&#xD;
- A diagram of the location of a specific clinical finding;&#xD;
- A radiological image;&#xD;
- An audio or video recording of an interview;&#xD;
- Scanned pathology slide;&#xD;
- Data output from a clinical device, such as an ECG machine; or&#xD;
- A scanned image of paper documentation or hand-written clinical notes.&#xD;
&#xD;
The 'Content' data element allows for the media file to be captured and stored within the health record using the Multimedia data type. The Multimedia data type has many RM attributes such as the size of file and URI to an external source. See https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
If more than one media file has been captured, such as 'before' and 'after' images of a wound, use a separate instance of this archetype to represent each media file.&#xD;
&#xD;
If a series of media files is represented as a single item, such as a CT scan, one instance of this archetype can be used to represent a URI path to the group. (en)</use>
      <misuse>*Not to be used to represent information, instructional or educational material supplied to an individual, or their carer, for example patient education leaflets. Use the CLUSTER.information_resource for this purpose.&#xD;
&#xD;
Not to be used to record a reference to a knowledge base - use CLUSTER.knowledge_base_reference for this purpose. (en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å dokumentere detaljer om en mediafil, samt tilknyttede metadata, som er ervervet eller brukt i forbindelse med en helsetjeneste.</purpose>
      <keywords>bilde</keywords>
      <keywords>foto</keywords>
      <keywords>audio</keywords>
      <keywords>tekstfil</keywords>
      <keywords>video</keywords>
      <keywords>applikasjon</keywords>
      <keywords>fil</keywords>
      <keywords>multimedia</keywords>
      <keywords>DICOM</keywords>
      <keywords>digital</keywords>
      <keywords>dokument</keywords>
      <keywords>skannet</keywords>
      <keywords>scannet</keywords>
      <keywords>lyd</keywords>
      <use>Brukes for å dokumentere detaljer om en mediafil, samt tilknyttede metadata, som er ervervet eller brukt i forbindelse med en helsetjeneste.&#xD;
&#xD;
Hensikten med denne arketypen er kun å være en bærer for mediafilen og metadataene som beskriver innholdet i filen. Denne arketypen vil være nøstet i en annen arketype, vanligvis en OBSERVATION eller ACTION arketype, som vil inneholde konteksten og omstendighetene knyttet til hvordan innholdet ble dannet. For eksempel blir detaljer om modalitet, visning eller aspekt av et radiologisk bilde og DICOM-detaljer dokumentert i arketypen OBSERVATION.imaging_exam_result.&#xD;
&#xD;
Eksempler inkluderer, men er ikke begrenset til:&#xD;
- Et bilde av en skade;&#xD;
- Et diagram over plasseringen av et spesifikt klinisk funn;&#xD;
- Et digital radiologisk bilde;&#xD;
- Et lyd- eller videoopptak av et intervju;&#xD;
- Et skannet objektglass til mikroskopisk diagnostikk;&#xD;
- Data fra medisinsk utstyr, for eksempel en EKG-apparat;&#xD;
- Et skannet bilde av papirdokumentasjon eller håndskrevne kliniske notater.&#xD;
&#xD;
Dataelementet "Innhold" gjør det mulig å fange og lagre mediafiler i den elektroniske pasientjournalen (EPJ) ved hjelp av multimedia-datatypen. Multimedia-datatypen har mange RM-attributter, for eksempel filstørrelsen og URI til en ekstern kilde. Se https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Hvis mer enn én mediafil skal dokumenteres, for eksempel bilder før og etter behandling av et sår, bruk en forekomst av denne arketypen for hvert bilde.&#xD;
&#xD;
Hvis en serie mediafiler er representert som et enkelt element, for eksempel en CT-skanning, kan en forekomst av denne arketypen brukes til å representere en URI til gruppen/serien.</use>
      <misuse>Skal ikke brukes til å representere informasjon, instruksjons- eller utdanningsmateriale levert til en person, eller dens omsorgsperson, for eksempel brosjyrer for pasientopplæring. Bruk CLUSTER.information_resource til dette formålet.&#xD;
&#xD;
Skal ikke brukes til å registrere en referanse til en kunnskapsbase - bruk CLUSTER. Knowledge_base_reference for dette formålet.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record a media file that is acquired or used as part of the healthcare process, and details about associated metadata.</purpose>
      <keywords>image</keywords>
      <keywords>audio</keywords>
      <keywords>text</keywords>
      <keywords>video</keywords>
      <keywords>application</keywords>
      <keywords>file</keywords>
      <keywords>multimedia</keywords>
      <keywords>audio</keywords>
      <keywords>DICOM</keywords>
      <keywords>digital</keywords>
      <keywords>document</keywords>
      <keywords>photo</keywords>
      <keywords>voice</keywords>
      <use>Use to record a media file that is acquired or used as part of the healthcare process, and details about associated metadata.&#xD;
&#xD;
The intent of this archetype is only to hold the media file and the metadata describing its capture. This archetype will be nested within another archetype, usually an OBSERVATION or ACTION that will hold the context and circumstances related to the capture of the media file. For example, details about the modality, view or aspect of a radiographic image and DICOM details will be captured within the OBSERVATION.imaging_exam_result archetype. &#xD;
&#xD;
Examples include, but are not limited to:&#xD;
- A photo of an injury;&#xD;
- A diagram of the location of a specific clinical finding;&#xD;
- A radiological image;&#xD;
- An audio or video recording of an interview;&#xD;
- Scanned pathology slide;&#xD;
- Data output from a clinical device, such as an ECG machine; or&#xD;
- A scanned image of paper documentation or hand-written clinical notes.&#xD;
&#xD;
The 'Content' data element allows for the media file to be captured and stored within the health record using the Multimedia data type. The Multimedia data type has many RM attributes such as the size of file and URI to an external source. See https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
If more than one media file has been captured, such as 'before' and 'after' images of a wound, use a separate instance of this archetype to represent each media file.&#xD;
&#xD;
If a series of media files is represented as a single item, such as a CT scan, one instance of this archetype can be used to represent a URI path to the group.</use>
      <misuse>Not to be used to represent information, instructional or educational material supplied to an individual, or their carer, for example patient education leaflets. Use the CLUSTER.information_resource for this purpose.&#xD;
&#xD;
Not to be used to record a reference to a knowledge base - use CLUSTER.knowledge_base_reference for this purpose.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Natalia Strauch</author>
    <author id="organisation">Medizinische Hochschule Hannover</author>
    <author id="email">Strauch.Natalia@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Åsa Skagerhult, Erik Sundvall</author>
    <author id="organisation">Region Östergötland</author>
    <author id="email">asa.skagerhult@regionostergotland.se, erik.sundvall@regionostergotland.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Liv Laugen, John Tore Valand</author>
    <author id="organisation">​Oslo University Hospital, Norway, Helse Bergen</author>
    <author id="email">liv.laugen@ous-hf.no, john.tore.valand@helse-bergen.no</author>
  </translations>
  <uid>
    <value>5990f36e-7fa7-4e45-a49d-eff753459882</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-CLUSTER.media_file.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <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>1</lower>
      <upper>1</upper>
    </occurrences>
    <node_id>at0000</node_id>
    <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
      <rm_attribute_name>items</rm_attribute_name>
      <existence>
        <lower_included>true</lower_included>
        <upper_included>true</upper_included>
        <lower_unbounded>false</lower_unbounded>
        <upper_unbounded>false</upper_unbounded>
        <lower>1</lower>
        <upper>1</upper>
      </existence>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0001</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_MULTIMEDIA</rm_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>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>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0010</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_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>
          <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="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>at0004</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_DATE_TIME</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_INTERVAL&lt;DV_DATE_TIME&gt;</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </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>at0012</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v0/}</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\.person(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v0</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>at0011</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.device\.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\.v1</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>at0013</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>at0007</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>
  </definition>
  <ontology>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Media file</items>
        <items id="description">A media file that is acquired or used as part of the healthcare process, and associated metadata.</items>
      </items>
      <items code="at0001">
        <items id="text">Content</items>
        <items id="description">Digital representation of the media file.</items>
        <items id="comment">If the file is stored locally, the actual content will be captured and stored using the Multimedia data type. For example: RTF or PDF for a document; JPG for an image; MP4 for a video; or WAV for an audio file. If the file is stored at a location outside of the health record, the detailed path to the file is captured using the URI attribute in the Multimedia data type. The Multimedia data type has many RM attributes such as the size of file and URI to an external source - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.</items>
      </items>
      <items code="at0002">
        <items id="text">Content name</items>
        <items id="description">Descriptive name or title for the media file.</items>
        <items id="comment">A description of the content of the media file. Use an agreed standardised naming convention, if available. For example: "Right hand burn #1" or "Cardiology video consultation on May 2".</items>
      </items>
      <items code="at0004">
        <items id="text">Created</items>
        <items id="description">The date/time, partial date or period when the media file was generated or authored.</items>
      </items>
      <items code="at0005">
        <items id="text">Description</items>
        <items id="description">Narrative description about the media file.</items>
      </items>
      <items code="at0007">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the media file not captured in other fields.</items>
      </items>
      <items code="at0010">
        <items id="text">Identifier</items>
        <items id="description">Unique ID for the media file.</items>
      </items>
      <items code="at0011">
        <items id="text">Source device</items>
        <items id="description">Details about the device used to generate or author the media file.</items>
        <items id="comment">For example: the camera used to capture an image.</items>
      </items>
      <items code="at0012">
        <items id="text">Creator</items>
        <items id="description">Details about the individual or organisation who generated or authored the media file.</items>
      </items>
      <items code="at0013">
        <items id="text">Additional details</items>
        <items id="description">Additional structured details about the media file.</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">*Media file (en)</items>
        <items id="description">*A media file that is acquired or used as part of the healthcare process, and associated metadata. (en)</items>
      </items>
      <items code="at0001">
        <items id="text">Multimedia</items>
        <items id="description">*Digital representation of the media file. (en)</items>
        <items id="comment">*If the file is stored locally, the actual content will be captured and stored using the Multimedia data type. For example: RTF or PDF for a document; JPG for an image; MP4 for a video; or WAV for an audio file. If the file is stored at a location outside of the health record, the detailed path to the file is captured using the URI attribute in the Multimedia data type. The Multimedia data type has many RM attributes such as the size of file and URI to an external source - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class. (en)</items>
      </items>
      <items code="at0002">
        <items id="text">*Content name (en)</items>
        <items id="description">*Descriptive name or title for the media file. (en)</items>
        <items id="comment">*A description of the content of the media file. Use an agreed standardised naming convention, if available. For example: "Right hand burn #1" or "Cardiology video consultation on May 2". (en)</items>
      </items>
      <items code="at0004">
        <items id="text">Skapad</items>
        <items id="description">*The date/time, partial date or period when the media file was generated or authored. (en)</items>
      </items>
      <items code="at0005">
        <items id="text">Beskrivning</items>
        <items id="description">*Narrative description about the media file. (en)</items>
      </items>
      <items code="at0007">
        <items id="text">Version</items>
        <items id="description">*Additional narrative about the media file not captured in other fields. (en)</items>
      </items>
      <items code="at0010">
        <items id="text">*Identifier (en)</items>
        <items id="description">*Unique ID for the media file. (en)</items>
      </items>
      <items code="at0011">
        <items id="text">*Source device(en)</items>
        <items id="description">*Details about the device used to generate or author the media file. (en)</items>
        <items id="comment">*For example: the camera used to capture an image.(en)</items>
      </items>
      <items code="at0012">
        <items id="text">*Creator(en)</items>
        <items id="description">*Details about the individual or organisation who generated or authored the media file. (en)</items>
      </items>
      <items code="at0013">
        <items id="text">*Additional details(en)</items>
        <items id="description">*Additional structured details about the media file. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Mediendatei</items>
        <items id="description">Eine Mediendatei mit zugehörigen Metadaten, die im Rahmen des Gesundheitsprozesses erworben oder verwendet wird.</items>
      </items>
      <items code="at0001">
        <items id="text">Inhalt</items>
        <items id="description">Digitale Repräsentation der Mediendatei.</items>
        <items id="comment">Wenn die Datei lokal gespeichert wird, wird der eigentliche Inhalt erfasst und mit dem Datentyp Multimedia gespeichert. Beispiel: RTF oder PDF für ein Dokument, JPG für ein Bild, MP4 für ein Video oder WAV für eine Audiodatei. Wenn die Datei an einem Ort außerhalb der Gesundheitsakte gespeichert ist, wird der detaillierte Pfad zur Datei mithilfe des URI-Attributs im Multimedia-Datentyp erfasst. Der Multimedia-Datentyp hat viele RM-Attribute wie die Größe der Datei und URI zu einer externen Quelle - siehe https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.</items>
      </items>
      <items code="at0002">
        <items id="text">Inhalt</items>
        <items id="description">Beschreibender Name oder Titel für die Mediendatei.</items>
        <items id="comment">Eine Beschreibung des Inhalts der Mediendatei. Verwenden Sie, falls verfügbar, eine vereinbarte standardisierte Namenskonvention. Zum Beispiel: „Verbrennung der rechten Hand Nr. 1“ oder „Videosprechstunde Kardiologie am 2. Mai“.</items>
      </items>
      <items code="at0004">
        <items id="text">Erstellt</items>
        <items id="description">Datum/Uhrzeit, Teildatum oder Zeitraum, in dem die Mediendatei generiert oder verfasst wurde.</items>
      </items>
      <items code="at0005">
        <items id="text">Beschreibung</items>
        <items id="description">Kurze Beschreibung der Mediendatei.</items>
      </items>
      <items code="at0007">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Information zu der Mediendatei, die nicht in anderen Feldern erfasst wurde.</items>
      </items>
      <items code="at0010">
        <items id="text">Identifikator</items>
        <items id="description">Eindeutige ID für die Mediendatei.</items>
      </items>
      <items code="at0011">
        <items id="text">Quellgerät</items>
        <items id="description">Informationen zu dem Gerät, mit dem die Mediendatei generiert oder erzeugt wurde.</items>
        <items id="comment">Zum Beispiel: Die Kamera, mit der ein Bild aufgenommen wurde.</items>
      </items>
      <items code="at0012">
        <items id="text">Urheber</items>
        <items id="description">Informationen zu der Person oder Organisation, die die Mediendatei generiert oder verfasst hat.</items>
      </items>
      <items code="at0013">
        <items id="text">Zusätzliche Informationen</items>
        <items id="description">Zusätzliche strukturierte Details zur Mediendatei.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Mediafil</items>
        <items id="description">En mediafil, samt tilknyttede metadata, som er ervervet eller brukt forbindelse med en helsetjeneste.</items>
      </items>
      <items code="at0001">
        <items id="text">Innhold</items>
        <items id="description">Digital representasjon av mediafilen.</items>
        <items id="comment">Hvis filen lagres lokalt, blir det faktiske innholdet lagret ved hjelp av datatypen Multimedia. For eksempel: RTF eller PDF for et dokument; JPG for et bilde; MP4 for en video; eller WAV for en lydfil. Hvis filen lagres et sted utenfor den elektroniske journalen, kan adressen til filen bli lagret ved hjelp av URI-attributtet i multimediedatatypen. Multimedia-datatypen har mange RM-attributter, for eksempel filstørrelse og URI til en ekstern kilde - se https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.</items>
      </items>
      <items code="at0002">
        <items id="text">Navn på innhold</items>
        <items id="description">Beskrivende navn eller tittel på mediafilen.</items>
        <items id="comment">En beskrivelse av innholdet i mediafilen. For eksempel: "Brannsår høyre hånd #1" eller "Kardiologisk videokonsultasjon 2. mai". Bruk avtalt standardisert navnekonvensjon dersom det er mulig.</items>
      </items>
      <items code="at0004">
        <items id="text">Opprettet dato</items>
        <items id="description">Dato/klokkeslett, delvis dato eller periode da multimediafilen ble generert eller laget.</items>
      </items>
      <items code="at0005">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstlig beskrivelse av mediafilen.</items>
      </items>
      <items code="at0007">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om mediafilen som ikke dekkes av andre elementer.</items>
      </items>
      <items code="at0010">
        <items id="text">ID</items>
        <items id="description">Unik identifikator til mediafilen.</items>
      </items>
      <items code="at0011">
        <items id="text">Kildeenhet</items>
        <items id="description">Detaljer om enheten som ble brukt til å generere eller skape mediafilen.</items>
        <items id="comment">For eksempel: kamera som ble brukt til å ta bildet.</items>
      </items>
      <items code="at0012">
        <items id="text">Forfatter</items>
        <items id="description">Detaljer om personen eller organisasjonen som genererte eller skapte mediafilen.</items>
      </items>
      <items code="at0013">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Ytterligere strukturerte detaljer om mediafilen.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
