<?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">619A905601290A99C5F1601986DCEF64</other_details>
    <other_details id="build_uid">65ccbf2e-5ce5-4a7f-9f1c-5ce8d7dc31c4</other_details>
    <other_details id="revision">1.0.6</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur 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>pt-pt</code_string>
      </language>
      <purpose>Para registar um ficheiro de media adquirido ou utilizado como parte do processo médico e detalhes sobre os metadados associados.</purpose>
      <keywords>imagem</keywords>
      <keywords>áudio</keywords>
      <keywords>texto</keywords>
      <keywords>vídeo</keywords>
      <keywords>aplicação</keywords>
      <keywords>ficheiro</keywords>
      <keywords>multimédia</keywords>
      <keywords>áudio</keywords>
      <keywords>DICOM</keywords>
      <keywords>digital</keywords>
      <keywords>documento</keywords>
      <keywords>fotografia</keywords>
      <keywords>voz</keywords>
      <use>Utilize para registar um ficheiro de media adquirido ou utilizado como parte do processo médico e detalhes sobre os metadados associados.&#xD;
&#xD;
A intenção deste arquétipo é apenas armazenar o ficheiro de media e os metadados que descrevem a sua captura. Este arquétipo estará aninhado dentro de outro arquétipo, geralmente uma OBSERVATION ou ACTION que conterá o contexto e as circunstâncias relacionadas com a captura do ficheiro de media. Por exemplo, os detalhes sobre a modalidade, visualização ou aspeto de uma imagem radiográfica e detalhes DICOM serão captados no arquétipo OBSERVATION.imaging_exam_result.&#xD;
&#xD;
Os exemplos incluem, mas não estão limitados a:&#xD;
- Uma foto de uma lesão;&#xD;
- Um diagrama da localização de um achado clínico específico;&#xD;
- Uma imagem radiológica;&#xD;
- Uma gravação áudio ou vídeo de uma entrevista;&#xD;
- Lâmina de patologia digitalizada;&#xD;
- Saída de dados de um dispositivo clínico, como por exemplo uma máquina de ECG; ou&#xD;
- Uma imagem digitalizada de documentação em papel ou notas clínicas manuscritas.&#xD;
&#xD;
O elemento de dados 'Conteúdo' permite que o ficheiro de media seja capturado e armazenado no registo de saúde utilizando o tipo de dados Multimedia. O tipo de dados Multimedia tem muitos atributos, como o tamanho do ficheiro e URI para uma fonte externa. Consulte https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Se tiver sido capturado mais do que um ficheiro de media, como imagens “antes” e “depois” de uma ferida, utilize uma instância separada deste arquétipo para representar cada ficheiro de media.&#xD;
&#xD;
Se uma série de ficheiros de media for representada como um único item, como uma tomografia computorizada, uma instância desse arquétipo pode ser utilizada para representar um caminho URI para o grupo.</use>
      <misuse>Não deve ser utilizado para representar informações, materiais instrucionais ou educativos fornecidos a um indivíduo ou ao seu cuidador, por exemplo, folhetos educativos para doentes. Utilize o CLUSTER.information_resource para este fim.&#xD;
&#xD;
Não deve ser utilizado para registar uma referência para uma base de conhecimento - utilize CLUSTER.knowledge_base_reference para este fim.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Att registrera en mediefil som förvärvats eller använts som en del i en vårdprocess, samt detaljer om filens metadata.</purpose>
      <keywords>bild</keywords>
      <keywords>foto</keywords>
      <keywords>ljud</keywords>
      <keywords>text</keywords>
      <keywords>video</keywords>
      <keywords>film</keywords>
      <keywords>applikation</keywords>
      <keywords>fil</keywords>
      <keywords>multimedia</keywords>
      <keywords>DICOM</keywords>
      <keywords>digital</keywords>
      <keywords>dokument</keywords>
      <keywords>röst</keywords>
      <use>Används för att registrera en mediefil som förvärvats eller används som del i en vårdprocess, samt detaljer om filens metadata. &#xD;
&#xD;
Avsikten med denna arketyp är att lagra mediefilen och dess metadata och beskriva hur den har skapats. Arketypen nästlas vanligtvis in i en OBSERVATION eller ACTION arketyp som innehåller information om kontexten och sammanhanget för skapandet av mediefilen. Till exempel kan detaljer om behandlingsmetod, synvinkel eller aspekt på en röntgenbild eller detaljer rörande DICOM-filer lagras i arketypen OBSERVATION.imaging_exam_result.&#xD;
&#xD;
Exempel inkluderar, men är inte begränsade till:&#xD;
-Ett foto av en skada&#xD;
-Ett diagram över anatomisk lokalisation av ett specifikt kliniskt fynd&#xD;
-En röntgenbild&#xD;
-En ljud- eller videoinspelning av en intervju&#xD;
-Inskannade histopatologiska objektglas&#xD;
-Data från medicinsk utrustning, så som en EKG-apparat, eller&#xD;
-Inskannat foto av pappersdokumentation eller handskrivna kliniska anteckningar&#xD;
&#xD;
Datafältet "Innehåll" tillåter mediefilen att förvärvas och lagras i journalen via datatypen Multimedia. Multimedia datatypen har flertalet Reference modell attribut som filstorlek och URI till en extern källa. Se https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Om mer än en mediefil har registrerats, såsom "före" och "efter" bilder av ett sår, använd separata instanser av denna arketyp för att representera varje mediefil.&#xD;
&#xD;
Om en serie av mediefiler representeras av ett enda objekt, till exempel en datortomografi, kan en instans av denna arketyp användas för att representera en URI sträng till filen.</use>
      <misuse>Ska inte användas för innehåll som information, instruktions- eller undervisningsmaterial som utdelats till en patient eller deras vårdgivare, till exempel som utbildningsbroschyrer. Använd CLUSTER.information_resource för detta syfte.&#xD;
&#xD;
Ska inte användas för att registrera en referens till en databas. Använd CLUSTER.knowledge_base_reference för detta syfte.</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>sk</code_string>
      </language>
      <purpose>Na zaznamenanie mediálneho súboru, ktorý sa získa alebo použije ako súčasť procesu zdravotnej starostlivosti, a podrobností o súvisiacich metadátach.</purpose>
      <keywords>obrázky</keywords>
      <keywords>zvuky</keywords>
      <keywords>text</keywords>
      <keywords>video</keywords>
      <keywords>aplikácie</keywords>
      <keywords>súbory</keywords>
      <keywords>multimédiá</keywords>
      <keywords>zvuky</keywords>
      <keywords>DICOM</keywords>
      <keywords>digital</keywords>
      <keywords>dokument</keywords>
      <keywords>fotka</keywords>
      <keywords>hlasový záznam</keywords>
      <use>Používa sa na zaznamenanie mediálneho súboru, ktorý sa získa alebo použije ako súčasť procesu zdravotnej starostlivosti, a podrobností o súvisiacich metadátach.&#xD;
&#xD;
Zámerom tohto archetypu je iba uchovávať mediálny súbor a metadáta popisujúce jeho zachytenie. Tento archetyp bude vnorený do iného archetypu, zvyčajne POZOROVANIA alebo AKCIE, ktorá bude obsahovať kontext a okolnosti súvisiace so zachytením mediálneho súboru. Napríklad podrobnosti o modalite, zobrazení alebo aspekte rádiografickej snímky a podrobnosti DICOM budú zachytené v rámci archetypu OBSERVATION.imaging_exam_result.&#xD;
&#xD;
Príklady zahŕňajú, ale nie sú obmedzené na:&#xD;
- fotografia zranenia;&#xD;
- Schéma lokalizácie konkrétneho klinického nálezu;&#xD;
- rádiologický obraz;&#xD;
- audio alebo video záznam rozhovoru;&#xD;
- Naskenovaný patologický diapozitív;&#xD;
- Výstup údajov z klinického zariadenia, ako je EKG prístroj; alebo&#xD;
- Naskenovaný obraz papierovej dokumentácie alebo ručne písané klinické poznámky.&#xD;
&#xD;
Údajový prvok „Obsah“ umožňuje zaznamenať a uložiť mediálny súbor do zdravotného záznamu pomocou dátového typu Multimedia. Dátový typ Multimedia má veľa atribútov RM, ako je veľkosť súboru a URI pre externý zdroj. Pozrite si https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Ak bol zachytený viac ako jeden mediálny súbor, napríklad obrázky rany „pred“ a „po“, použite na reprezentáciu každého mediálneho súboru samostatnú inštanciu tohto archetypu.&#xD;
&#xD;
Ak je séria mediálnych súborov reprezentovaná ako jedna položka, ako napríklad CT sken, tak sa môže jedna inštancia tohto archetypu použiť na reprezentáciu cesty pomocou URI k skupine.</use>
      <misuse>Nesmie sa používať na reprezentáciu informácií, inštruktážnych alebo vzdelávacích materiálov dodávaných jednotlivcom alebo ich opatrovateľom, napríklad letáky s informáciami pre pacientov. Na tento účel použite CLUSTER.information_resource.&#xD;
&#xD;
Nesmie sa používať na zaznamenanie odkazu na bázu znalostí – na tento účel použite CLUSTER.knowledge_base_reference.</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>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fr</code_string>
      </language>
      <purpose>Pour enregistrer un fichier multimédia acquis ou utilisé dans le cadre du processus de soins, ainsi que les détails relatifs aux métadonnées associées.</purpose>
      <keywords>image</keywords>
      <keywords>audio</keywords>
      <keywords>texte</keywords>
      <keywords>vidéo</keywords>
      <keywords>application</keywords>
      <keywords>fichier</keywords>
      <keywords>multimédia</keywords>
      <keywords>audio</keywords>
      <keywords>DICOM</keywords>
      <keywords>numérique</keywords>
      <keywords>document</keywords>
      <keywords>photo</keywords>
      <keywords>voix</keywords>
      <use>À utiliser pour enregistrer un fichier multimédia acquis ou utilisé dans le cadre du processus de soins, ainsi que les détails relatifs aux métadonnées associées.&#xD;
&#xD;
Cet archétype a pour seul objectif de contenir le fichier multimédia et les métadonnées décrivant sa saisie. Il sera imbriqué dans un autre archétype, généralement un archétype OBSERVATION ou ACTION qui contiendra le contexte et les circonstances liées à la saisie du fichier multimédia. Par exemple, les détails concernant la modalité, la vue ou l’aspect d’une image radiographique ainsi que les informations DICOM seront enregistrés dans l’archétype OBSERVATION.imaging_exam_result. &#xD;
&#xD;
Voici quelques exemples, sans que cette liste soit exhaustive :&#xD;
- Une photo d’une blessure ;&#xD;
- Un schéma indiquant l’emplacement d’un signe clinique spécifique ;&#xD;
- Une image radiologique ;&#xD;
- Un enregistrement audio ou vidéo d’un entretien ;&#xD;
- Une lame de pathologie numérisée ;&#xD;
- Des données issues d’un appareil clinique, tel qu’un électrocardiographe ; ou&#xD;
- Une image numérisée de documents papier ou de notes cliniques manuscrites.&#xD;
&#xD;
L’élément de données « Contenu » permet de capturer et de stocker le fichier multimédia au sein du dossier de santé à l’aide du type de données « Multimédia ». Le type de données « Multimédia » comporte de nombreux attributs RM, tels que la taille du fichier et l’URI vers une source externe. Voir https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Si plusieurs fichiers multimédias ont été enregistrés, par exemple des images « avant » et « après » d’une plaie, utilisez une instance distincte de cet archétype pour représenter chaque fichier multimédia.&#xD;
&#xD;
Si une série de fichiers multimédias est représentée sous la forme d’un seul élément, comme un scanner, une seule instance de cet archétype peut être utilisée pour représenter le chemin URI menant à l’ensemble.</use>
      <misuse>À ne pas utiliser pour enregister des informations, du matériel pédagogique ou éducatif fourni à une personne ou à son proche aidant, par exemple des brochures d’information destinées aux patients. Utilisez CLUSTER.information_resource à cette fin.&#xD;
&#xD;
À ne pas utiliser pour enregistrer une référence à une base de connaissances ; utilisez CLUSTER.knowledge_base_reference à cette fin.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nl</code_string>
      </language>
      <purpose>Om een mediabestand vast te leggen dat is verkregen of gebruikt als onderdeel van het zorgproces, en details over bijbehorende metadata.</purpose>
      <keywords>afbeelding</keywords>
      <keywords>audio</keywords>
      <keywords>tekst</keywords>
      <keywords>video</keywords>
      <keywords>applicatie</keywords>
      <keywords>bestand</keywords>
      <keywords>multimedia</keywords>
      <keywords>geluid</keywords>
      <keywords>DICOM</keywords>
      <keywords>digitaal</keywords>
      <keywords>document</keywords>
      <keywords>foto</keywords>
      <keywords>spraak</keywords>
      <use>Te gebruiken om een mediabestand vast te leggen dat is verkregen of gebruikt als onderdeel van het zorgproces, en details over bijbehorende metadata.&#xD;
&#xD;
Dit archetype is alleen bedoeld voor het mediabestand en de metadata die het vastleggen ervan beschrijven. Dit archetype wordt genest binnen een ander archetype, meestal een OBSERVATION of ACTION die de context en omstandigheden bevat die verband houden met het vastleggen van het mediabestand. Bijvoorbeeld, details over de modaliteit, weergave of aspect van een radiografisch beeld en DICOM-details worden vastgelegd in het archetype OBSERVATION.imaging_exam_result.&#xD;
&#xD;
Voorbeelden omvatten, maar zijn niet beperkt tot:&#xD;
- Een foto van een blessure;&#xD;
- Een diagram van de locatie van een specifieke klinische bevinding;&#xD;
- Een radiologisch beeld;&#xD;
- Een audio- of video-opname van een interview;&#xD;
- Gescande pathologiedia;&#xD;
- Gegevensuitvoer van een klinisch apparaat, zoals een ECG-apparaat; of&#xD;
- Een gescande afbeelding van papieren documentatie of handgeschreven klinische aantekeningen.&#xD;
&#xD;
Met het gegevenselement 'Inhoud' kan het mediabestand worden vastgelegd en opgeslagen in het gezondheidsdossier met behulp van het gegevenstype Multimedia. Het gegevenstype Multimedia heeft veel RM-attributen, zoals de grootte van het bestand en de URI naar een externe bron. Zie https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.&#xD;
&#xD;
Als er meer dan één mediabestand is vastgelegd, zoals 'voor' en 'na' beelden van een wond, gebruik dan een afzonderlijke instantie van dit archetype om elk mediabestand te vertegenwoordigen.&#xD;
&#xD;
Als een reeks mediabestanden wordt weergegeven als een enkel item, zoals een CT-scan, kan één instantie van dit archetype worden gebruikt om een URI-pad naar de groep weer te vertegenwoordigen.</use>
      <misuse>Niet te gebruiken om informatie, instructie- of educatief materiaal weer te geven dat aan een persoon of hun verzorger wordt verstrekt, bijvoorbeeld folders voor patiënteneducatie. Gebruik hiervoor de CLUSTER.information_resource.&#xD;
&#xD;
Niet te gebruiken om een verwijzing naar een kennisbank op te nemen - gebruik hiervoor CLUSTER.knowledge_base_reference.</misuse>
      <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>pt-pt</code_string>
    </language>
    <author id="name">Hugo Silva</author>
    <author id="organisation">University of Minho</author>
    <author id="email">pg50416@uminho.pt</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, Manna Vosta, Oscar Karlsson, Jörgen Kuylenstierna</author>
    <author id="organisation">Region Östergötland, Karolinska University Hospital, eWeave AB</author>
    <author id="email">asa.skagerhult@regionostergotland.se, erik.sundvall@regionostergotland.se, manna.vosta@regionstockholm.se, jorgen.kuylenstierna@solvikshalsan.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>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sk</code_string>
    </language>
    <author id="name">Maritn Kapinos</author>
    <author id="organisation">PROSOFT Košice, a.s.</author>
    <author id="email">kapinos.martin@prosoftke.sk</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fr</code_string>
    </language>
    <author id="name">Jonas Bucher</author>
    <author id="organisation">Cistec AG</author>
    <author id="email">jonas.bucher@cistec.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nl</code_string>
    </language>
    <author id="name">Jelte Zeilstra</author>
    <author id="organisation">Nedap</author>
  </translations>
  <uid>
    <value>e2c3697a-6163-4bc7-86d0-519dd6b954f9</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/}</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</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. Full list of available media types: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types.  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">Mediefil</items>
        <items id="description">En mediefil och dess metadata som förvärvats eller använts som del i en vårdprocess.</items>
      </items>
      <items code="at0001">
        <items id="text">Innehåll</items>
        <items id="description">Digitalt åskådliggörande av mediefilen.</items>
        <items id="comment">Om filen lagras lokalt kommer det faktiska innehållet att fångas och lagras med hjälp av datatypen Multimedia. Till exempel: RTF eller PDF för ett dokument; JPG för en bild; MP4 för en video; eller WAV för en ljudfil. Fullständig lista över tillgängliga mediatyper: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types. Om filen lagras på en plats utanför hälsojournalen, fångas den detaljerade sökvägen till filen med URI-attributet i datatypen Multimedia. Datatypen Multimedia har många Referens Modell-attribut som filstorlek och URI till en extern källa - se https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.</items>
      </items>
      <items code="at0002">
        <items id="text">Innehållets namn</items>
        <items id="description">Beskrivande namn eller titel för mediefilen.</items>
        <items id="comment">En beskrivning av innehållet i mediefilen. Om tillgängligt, använd ett standardiserat sätt för att namnge filen. Till exempel: "Höger hand brännskada #1" eller "Kardiologi video konsultation 2/5".</items>
      </items>
      <items code="at0004">
        <items id="text">Skapad</items>
        <items id="description">Datum och tid eller period då mediefilen skapades.</items>
      </items>
      <items code="at0005">
        <items id="text">Beskrivning</items>
        <items id="description">Beskrivning av mediefilen.</items>
      </items>
      <items code="at0007">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligare redogörelse om mediefilen som inte beskrivits i andra fält.</items>
      </items>
      <items code="at0010">
        <items id="text">Identifierare</items>
        <items id="description">Unikt ID för mediefilen.</items>
      </items>
      <items code="at0011">
        <items id="text">Källutrustning</items>
        <items id="description">Detaljer om den utrustning som användes för att skapa mediefilen.</items>
        <items id="comment">Till exempel: kameran som användes för att ta en bild.</items>
      </items>
      <items code="at0012">
        <items id="text">Skapare</items>
        <items id="description">Detaljer om den individ eller organisation som skapade mediefilen.</items>
      </items>
      <items code="at0013">
        <items id="text">Ytterligare detaljer</items>
        <items id="description">Ytterligare strukturerade detaljer om mediefilen.</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">*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. Full list of available media types: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types.  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">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. Full liste over tilgjengelige mediatyper: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types&#xD;
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>
    <term_definitions language="nl">
      <items code="at0000">
        <items id="text">Mediabestand</items>
        <items id="description">Een mediabestand dat wordt verkregen of gebruikt als onderdeel van het zorgproces, en bijbehorende metadata.</items>
      </items>
      <items code="at0001">
        <items id="text">Inhoud</items>
        <items id="description">Digitale representatie van het mediabestand.</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. Full list of available media types: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types.  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">Naam inhoud</items>
        <items id="description">Beschrijvende naam of titel voor het mediabestand.</items>
        <items id="comment">Een beschrijving van de inhoud van het mediabestand. Gebruik een overeengekomen gestandaardiseerde naamgevingsconventie, indien beschikbaar. Bijvoorbeeld: "Brandwond rechterhand #1" of "Videoconsult Cardiologie op 2 mei".</items>
      </items>
      <items code="at0004">
        <items id="text">Aangemaakt op</items>
        <items id="description">De datum/tijd, gedeeltelijke datum of periode waarop het mediabestand is gegenereerd of gemaakt.</items>
      </items>
      <items code="at0005">
        <items id="text">Beschrijving</items>
        <items id="description">Verhalende beschrijving van het mediabestand.</items>
      </items>
      <items code="at0007">
        <items id="text">Opmerking</items>
        <items id="description">Aanvullende beschrijving over het mediabestand dat niet in andere velden is vastgelegd.</items>
      </items>
      <items code="at0010">
        <items id="text">Identificatie</items>
        <items id="description">Unieke identificatie voor het mediabestand.</items>
      </items>
      <items code="at0011">
        <items id="text">Bronapparaat</items>
        <items id="description">Details over het apparaat dat is gebruikt om het mediabestand te genereren of te maken.</items>
        <items id="comment">Bijvoorbeeld: de camera die wordt gebruikt om een beeld vast te leggen.</items>
      </items>
      <items code="at0012">
        <items id="text">Aangemaakt door</items>
        <items id="description">Details over de persoon of organisatie die het mediabestand heeft gegenereerd of gemaakt.</items>
      </items>
      <items code="at0013">
        <items id="text">Aanvullende details</items>
        <items id="description">Aanvullende gestructureerde details over het mediabestand.</items>
      </items>
    </term_definitions>
    <term_definitions language="sk">
      <items code="at0000">
        <items id="text">Mediálny súbor</items>
        <items id="description">Mediálny súbor, ktorý sa získava alebo používa ako súčasť procesu zdravotnej starostlivosti, a súvisiace metadáta</items>
      </items>
      <items code="at0001">
        <items id="text">Obsah</items>
        <items id="description">Digitálna reprezentácia mediálneho súboru.</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. Full list of available media types: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types.  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">Názov obsahu</items>
        <items id="description">Popisný názov alebo názov pre mediálny súbor.</items>
        <items id="comment">Popis obsahu mediálneho súboru. Použite dohodnutú štandardizovanú konvenciu pomenovania, ak je k dispozícii. Napríklad: „Popálenina pravej ruky č. 1“ alebo „Kardiologická videokonzultácia 2. mája“.</items>
      </items>
      <items code="at0004">
        <items id="text">Vytvorený</items>
        <items id="description">Dátum/čas, čiastočný dátum alebo obdobie, kedy bol mediálny súbor vygenerovaný alebo vytvorený.</items>
      </items>
      <items code="at0005">
        <items id="text">Popis</items>
        <items id="description">Naratívny popis o mediálnom súbore.</items>
      </items>
      <items code="at0007">
        <items id="text">Poznámky</items>
        <items id="description">Dodatočné poznámky o mediálnom súbore nezachytené v iných poliach.</items>
      </items>
      <items code="at0010">
        <items id="text">Identifikátor</items>
        <items id="description">Jedinečný identifikátor pre mediálny súbor.</items>
      </items>
      <items code="at0011">
        <items id="text">Zdrojový prístroj</items>
        <items id="description">Podrobnosti o prístroji použitom na generovanie alebo vytvorenie mediálneho súboru.</items>
        <items id="comment">Napríklad: fotoaparát použitý zachytenie snímky.</items>
      </items>
      <items code="at0012">
        <items id="text">Tvorca</items>
        <items id="description">Podrobnosti o jednotlivcovi alebo organizácii, ktorá vygenerovala alebo vytvorila mediálny súbor.</items>
      </items>
      <items code="at0013">
        <items id="text">Ďalšie detaily</items>
        <items id="description">Ďalšie štruktúrované detaily o mediálnom súbore.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-pt">
      <items code="at0000">
        <items id="text">Ficheiro de media</items>
        <items id="description">Um ficheiro de media adquirido ou utilizado como parte do processo médico e metadados associados.</items>
      </items>
      <items code="at0001">
        <items id="text">Conteúdo</items>
        <items id="description">Representação digital do ficheiro de media.</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. Full list of available media types: https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types.  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">Nome do conteúdo</items>
        <items id="description">Nome ou título descritivo do ficheiro de media.</items>
        <items id="comment">Uma descrição do conteúdo do ficheiro de média. Utilize uma convenção de nomenclatura normalizada acordada, se disponível. Por exemplo: “Queimadura na mão direita nº 1” ou “Vídeo consulta de cardiologia no dia 2 de maio”.</items>
      </items>
      <items code="at0004">
        <items id="text">Criado</items>
        <items id="description">A data/hora, data parcial ou período em que o ficheiro de média foi gerado ou criado.</items>
      </items>
      <items code="at0005">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o ficheiro de media.</items>
      </items>
      <items code="at0007">
        <items id="text">Comentário</items>
        <items id="description">Narrativa adicional sobre o ficheiro de média não capturada noutros campos.</items>
      </items>
      <items code="at0010">
        <items id="text">Identificador</items>
        <items id="description">ID único do ficheiro de media.</items>
      </items>
      <items code="at0011">
        <items id="text">Dispositivo de origem</items>
        <items id="description">Detalhes sobre o dispositivo utilizado para gerar ou criar o ficheiro de média.</items>
        <items id="comment">Por exemplo: a câmara utilizada para captar uma imagem.</items>
      </items>
      <items code="at0012">
        <items id="text">Criador</items>
        <items id="description">Detalhes sobre o indivíduo ou organização que gerou ou criou o ficheiro de media.</items>
      </items>
      <items code="at0013">
        <items id="text">Detalhes adicionais</items>
        <items id="description">Detalhes estruturados adicionais sobre o ficheiro de media.</items>
      </items>
    </term_definitions>
    <term_definitions language="fr">
      <items code="at0000">
        <items id="text">Fichier multimédia</items>
        <items id="description">Un fichier multimédia acquis ou utilisé dans le cadre du processus de soins, ainsi que les métadonnées associées.</items>
      </items>
      <items code="at0001">
        <items id="text">Contenu</items>
        <items id="description">Représentation numérique du fichier multimédia.</items>
        <items id="comment">Si le fichier est stocké localement, son contenu réel sera capturé et stocké à l’aide du type de données « Multimédia ». Par exemple : RTF ou PDF pour un document ; JPG pour une image ; MP4 pour une vidéo ; ou WAV pour un fichier audio. Liste complète des types de fichiers multimédias disponibles : https://specifications.openehr.org/releases/TERM/latest/SupportTerminology.html#_media_types.  Si le fichier est stocké à un emplacement extérieur au dossier médical, le chemin d’accès détaillé vers le fichier est enregistré à l’aide de l’attribut URI du type de données « Multimédia ». Le type de données « Multimédia » comporte de nombreux attributs RM, tels que la taille du fichier et l’URI vers une source externe – voir https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_multimedia_class.</items>
      </items>
      <items code="at0002">
        <items id="text">Nom du contenu</items>
        <items id="description">Nom ou titre descriptif du fichier multimédia.</items>
        <items id="comment">Une description du contenu du fichier multimédia. Utilisez une convention de nommage standardisée et convenue, le cas échéant. Par exemple : « Brûlure à la main droite n° 1 » ou « Consultation vidéo en cardiologie du 2 mai ».</items>
      </items>
      <items code="at0004">
        <items id="text">Créé</items>
        <items id="description">La date/heure, une date partielle ou une période correspondant à la création ou à la production du fichier multimédia.</items>
      </items>
      <items code="at0005">
        <items id="text">Description</items>
        <items id="description">Description narrative du fichier multimédia.</items>
      </items>
      <items code="at0007">
        <items id="text">Commentaire</items>
        <items id="description">Informations supplémentaires concernant le fichier multimédia qui ne sont pas reprises dans d’autres champs.</items>
      </items>
      <items code="at0010">
        <items id="text">Identifiant</items>
        <items id="description">Identifiant unique du fichier multimédia.</items>
      </items>
      <items code="at0011">
        <items id="text">Appareil source</items>
        <items id="description">Informations détaillées sur le dispositif utilisé pour générer ou créer le fichier multimédia.</items>
        <items id="comment">Par exemple : l'appareil photo utilisé pour prendre une photo.</items>
      </items>
      <items code="at0012">
        <items id="text">Créateur</items>
        <items id="description">Informations détaillées sur la personne ou l'organisme ayant généré ou créé le fichier multimédia.</items>
      </items>
      <items code="at0013">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails supplémentaires concernant le fichier multimédia.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
