<?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">2017-03-21</original_author>
    <original_author id="name">Ian McNicoll</original_author>
    <original_author id="organisation">freshEHR Clinical Informatics</original_author>
    <original_author id="email">ian@freshehr.com</original_author>
    <other_contributors>Tomas Alme, DIPS ASA, Norway</other_contributors>
    <other_contributors>Paula Anderson, UCLH, United Kingdom</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Koray Atalag, University of Auckland, New Zealand</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Marcus Baw, openGPSoC / BawMedical Ltd, United Kingdom</other_contributors>
    <other_contributors>John Bennett, NEHTA, Australia</other_contributors>
    <other_contributors>SBhusan Bhattacharyya, Sudisa Consultancy Services, India</other_contributors>
    <other_contributors>Sharmila Biswas, Australia</other_contributors>
    <other_contributors>Lars Bitsch-Larsen, Haukeland University hospital, Norway</other_contributors>
    <other_contributors>Laila Bruun, Oslo universitetssykehus HF, Norway</other_contributors>
    <other_contributors>Ruth Caudwell, retired, United Kingdom</other_contributors>
    <other_contributors>Bjørn Christensen, Helse Bergen HF, Norway</other_contributors>
    <other_contributors>Stephen Chu, NEHTA, Australia (Editor)</other_contributors>
    <other_contributors>Matthew Cordell, NEHTA, Australia</other_contributors>
    <other_contributors>Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway</other_contributors>
    <other_contributors>Robert Eager, Healthways, Australia</other_contributors>
    <other_contributors>Gail Easterbrook, Flinders Medical Centre, Australia</other_contributors>
    <other_contributors>David Evans, Queensland Health, Australia</other_contributors>
    <other_contributors>Samuel Frade, Marand, Portugal</other_contributors>
    <other_contributors>Hildegard Franke, freshEHR Clinical Informatics Ltd., United Kingdom</other_contributors>
    <other_contributors>Sarah Gaunt, NEHTA, Australia</other_contributors>
    <other_contributors>Mikkel Gaup Grønmo, FSE, Helse Nord, Norway</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Trina Gregory, cpc, Australia</other_contributors>
    <other_contributors>Robert Hausam, Hausam Consulting LLC, United States</other_contributors>
    <other_contributors>Sam Heard, Ocean Informatics, Australia (Editor)</other_contributors>
    <other_contributors>Teresa Highway, Alberta Health Services, Canada</other_contributors>
    <other_contributors>Annette Hole Sjøborg, DIPS ASA, Norway</other_contributors>
    <other_contributors>Hilde Hollås, DIPS ASA, Norway</other_contributors>
    <other_contributors>Alfred Honore, Haukeland, Norway</other_contributors>
    <other_contributors>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Lars Ivar Mehlum, Helse Bergen HF, Norway</other_contributors>
    <other_contributors>Tom Jarl Jakobsen, Helse Bergen, Norway</other_contributors>
    <other_contributors>Mary Kelaher, NEHTA, Australia</other_contributors>
    <other_contributors>Nils Kolstrup, Skansen Legekontor og Nasjonalt Senter for samhandling og telemedisin, Norway</other_contributors>
    <other_contributors>Robert L'egan, NEHTA, Australia</other_contributors>
    <other_contributors>Russell Leftwich, Russell B Leftwich MD, United States</other_contributors>
    <other_contributors>Heather Leslie, Ocean Health Systems, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Marit Ludvigsen, St Olavs Hospital, Norway</other_contributors>
    <other_contributors>Colin Macfarlane, Elsevier, United Kingdom</other_contributors>
    <other_contributors>Siv Marie Lien, DIPS ASA, Norway</other_contributors>
    <other_contributors>Olof Mattsson, Region Skane, Sweden</other_contributors>
    <other_contributors>Susan McIndoe, Royal District Nursing Service, Australia</other_contributors>
    <other_contributors>David McKillop, NEHTA, Australia</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)</other_contributors>
    <other_contributors>Chris Mitchell, RACGP, Australia</other_contributors>
    <other_contributors>Stewart Morrison, NEHTA, Australia</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Chris Pearce, Melbourne East GP Network, Australia</other_contributors>
    <other_contributors>Vladimir Pizzo, Hospital Sírio Libanês, Brazil</other_contributors>
    <other_contributors>Camilla Preeston, Royal Australian College of General Practitioners, Australia</other_contributors>
    <other_contributors>Margaret Prichard, NEHTA, Australia</other_contributors>
    <other_contributors>Norwegian Review Summary, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Cathy Richardson, NEHTA, Australia</other_contributors>
    <other_contributors>Robyn Richards, NEHTA - Clinical Terminology, Australia</other_contributors>
    <other_contributors>Anoop Shah, University College London, United Kingdom</other_contributors>
    <other_contributors>Line Silsand, Universitetssykehuset i Nord-Norge, Norway</other_contributors>
    <other_contributors>Sam Stokes, Citizen Scientist, United States</other_contributors>
    <other_contributors>Iztok Stotl, UKCLJ, Slovenia</other_contributors>
    <other_contributors>John Taylor, NEHTA, Australia</other_contributors>
    <other_contributors>Nyree Taylor, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Rowan Thomas, St. Vincent's Hospital Melbourne, Australia</other_contributors>
    <other_contributors>Richard Townley-O'Neill, NEHTA, Australia</other_contributors>
    <other_contributors>Gro-Hilde Ulriksen, Norwegian center for ehealthresearch, Norway</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Ines Vaz, UFN, Portugal</other_contributors>
    <other_contributors>Soon Ghee Yap, Singapore General Hospital, Singapore</other_contributors>
    <other_contributors>Kylie Young, The Royal Australian College of General Practitioners, Australia</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">Medication statement, [Internet]. Intermountain Healthcare. Available from http://www.opencem.org/#/20170613/Intermountain/MedicationStatement&#xD;
&#xD;
Messaging Implementation Manual (GP2GP messages) [Internet], NHS Digital England. Available from: https://data.developer.nhs.uk/dms/mim/6.3.01/Domains/GP2GP/Document%20files/GP2GP%20IM.htm#_Toc_Section_7.2&#xD;
&#xD;
Standards for the clinical structure and content of patient records (Complete document) [Internet]. PRSB London. [cited 2017 Aug 29]. Available from: http://theprsb.org/download/document/7-standards-for-the-clinical-structure-and-content-of-patient-records"</other_details>
    <other_details id="current_contact">Ian McNicoll, freshEHR Clinical Informatics, UK &lt;ian@freshehr.com&gt;</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">7642B7C6FD3E445EA35DA32279728164</other_details>
    <other_details id="build_uid">673dfd30-fb11-4c55-92c3-5023241a841e</other_details>
    <other_details id="revision">2.0.3</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Darstellung der Kombination von Medikamentendosis und Verabreichungszeit an einem Tag im Kontext einer Medikamentenverordnung oder der Arzneimittelverwaltung oder gegebenenfalls für andere therapeutische/verschreibungspflichtige Produkte.</purpose>
      <keywords>Medikation</keywords>
      <keywords>Verordnung</keywords>
      <keywords>verschreiben</keywords>
      <keywords>verordnen</keywords>
      <keywords>Therapie</keywords>
      <keywords>Substanz</keywords>
      <keywords>Wirkstoff</keywords>
      <keywords>Arzneimittel</keywords>
      <keywords>Medikament</keywords>
      <keywords>therapeutisch</keywords>
      <keywords>therapeutisches Erzeugnis</keywords>
      <keywords>Pharmazeutikum</keywords>
      <keywords>Produkt</keywords>
      <keywords>Posologie</keywords>
      <keywords>Dosierung</keywords>
      <keywords>Behandlung</keywords>
      <keywords>Fluid</keywords>
      <keywords>Flüssigkeit</keywords>
      <keywords>Ernährung</keywords>
      <keywords>Timing</keywords>
      <keywords>Zeitplan</keywords>
      <keywords>Verabreichung</keywords>
      <keywords>Applikation</keywords>
      <keywords>Dosis</keywords>
      <use>Wird verwendet, um die Kombination einer Medikamentendosis und der Verabreichungszeiten innerhalb eines Tages, als Teil einer Medikamentenverordnung oder der Arzneimittelverwaltung oder gegebenenfalls für andere verschriebene therapeutische Produkte darzustellen.&#xD;
Das Zeitmuster für einen einzelnen Tag kann einfach eine einzelne Verabreichungszeit oder mehrere Verabreichungszeiten mit unterschiedlichem Komplexitätsgrad sein.&#xD;
&#xD;
Timing-Details, die nicht innerhalb eines Tages liegen, z. B. wöchentlicher oder monatlicher Rhythmus, werden im CLUSTER-Archetyp "Verabreichungszeitpunkte - nicht täglich" aufgeführt, der im CLUSTER-Archetyp "Therapeutische Anweisungen" (CLUSTER.therapeutic_direction) enthalten ist.&#xD;
&#xD;
Im Kontext einer therapeutischen INSTRUCTION kann dieser Archetyp in den SLOT "Strukturierte Dosis- und Zeitangaben" im CLUSTER "Therapeutische Anweisung" (CLUSTER.therapeutic_direction) eingefügt werden, um die Dosis und Details zum Zeitmuster der einzelnen beabsichtigten Verabreichungen eines therapeutischen Produktes darzustellen.&#xD;
&#xD;
Im Kontext eines ACTION-Archetyps fügen Sie diesen Archetyp direkt in den SLOT "Dosis" ein, um die Dosis und den Zeitpunkt der tatsächlichen Verabreichung eines therapeutischen Produktes darzustellen.&#xD;
&#xD;
Spezifische Start- / Stoppzeiten der Verabreichung sollten in einem CLUSTER-Archetyp "Verabreichungszeitpunkte - täglich" angegeben werden.</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Att registrera kombinationen av läkemedelsmängd och administrationstid för en enda dag, som en del av en läkemedelsorder eller läkemedelshantering eller för andra lämpliga terapeutiska / förskrivningsbara föremål.</purpose>
      <keywords>medicinering</keywords>
      <keywords>beställa</keywords>
      <keywords>ordinera</keywords>
      <keywords>terapi</keywords>
      <keywords>ämne</keywords>
      <keywords>läkemedel</keywords>
      <keywords>terapeutisk</keywords>
      <keywords>terapeutiskt bra</keywords>
      <keywords>läkemedel</keywords>
      <keywords>produkt</keywords>
      <keywords>dosering</keywords>
      <keywords>behandling</keywords>
      <keywords>vätska</keywords>
      <keywords>näring</keywords>
      <keywords>timing</keywords>
      <keywords>administration</keywords>
      <keywords>dos</keywords>
      <use>Används för att registrera kombinationen av läkemedelsmängd och administreringstid för en enda dag, som en del av en läkemedelsorder eller läkemedelshantering eller för andra lämpliga terapeutiska / förskrivningsbara föremål.&#xD;
Tidmönstret för en dag kan vara så enkelt som en enda administreringstid eller flera administreringstider med varierande nivåer av komplexitet.&#xD;
&#xD;
Tidsuppgifter som inte ligger inom en enda dag, t.ex. vecko- eller månatliga tider, tas i CLUSTER 'Timing - non-daily' arketypen, inom CLUSTER 'Therapeutic direction' arketypen.&#xD;
&#xD;
I samband med en terapeutisk INSTRUCTION kan den här arketypen införas i 'Strukturerad dos och tidsriktning' SLOT i 'Therapeutic direction' CLUSTER för att registrera dos- och tidsdetaljer för mönstret för enstaka avsedda administrationer av en terapeutisk artikel.&#xD;
&#xD;
I samband med en ACTION-arketyp, sätt in den här arketypen direkt i 'Amount' SLOT för att registrera dosen och tidpunkten för den faktiska administreringen av ett terapeutisk objekt&#xD;
&#xD;
Specifika administrationsstart / stopptider bör anges inom en innesluten CLUSTER 'Timing - daily' arketyp.</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere kombinasjonen av en legemiddeldose og administrasjonstidspunkter innenfor en dag, som del av en legemiddelordinering eller legemiddelhåndtering, eller for andre ordinerte produkter der det er passende.</purpose>
      <keywords>legemiddel</keywords>
      <keywords>ordinering</keywords>
      <keywords>foreskrive</keywords>
      <keywords>terapi</keywords>
      <keywords>substans</keywords>
      <keywords>medisin</keywords>
      <keywords>terapeutisk</keywords>
      <keywords>farmasøytisk</keywords>
      <keywords>produkt</keywords>
      <keywords>behandling</keywords>
      <keywords>væske</keywords>
      <keywords>ernæring</keywords>
      <keywords>timing</keywords>
      <keywords>administrering</keywords>
      <keywords>administrasjon</keywords>
      <keywords>dose</keywords>
      <use>Brukes for å registrere kombinasjonen av en legemiddeldose og administrasjonstidspunkter innenfor en dag, som del av en legemiddelordinering eller legemiddelhåndtering, eller for andre ordinerte produkter der det er passende. Mønsteret for administrasjonstidspunkter innenfor en dag kan være så enkelt som ett administrasjonstidspunkt, eller flere administrasjonstidspunkter med forskjellige nivåer av kompleksitet.&#xD;
&#xD;
Timingdetaljer som ikke er innenfor én dag, f.eks. ukentlig eller månedlige timinger, håndteres av CLUSTER-arketypen "Timing - repetering" som benyttes i CLUSTER-arketypen "Terapeutisk anvisning".&#xD;
&#xD;
Innenfor en INSTRUCTION og i den igjen innenfor CLUSTER-arketypen "Terapeutisk anvisning" (CLUSTER.therapeutic_direction) for å registrere dose og timing av et ordinert produkt, som f.eks. et legemiddel.&#xD;
&#xD;
Innenfor en ACTION-arketype kan denne arketypen brukes for å registrere dosen og timing for den faktiske administreringen av det ordinerte produktet.&#xD;
&#xD;
Spesifikke tidspunkter for administrering og start/stopp-tidspunkter spesifiseres i CLUSTER-arketypen "Timing - daglig".</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Para gravar a combinação de uma quantidade de medicamento e o tempo de administração diário, como parte de uma solicitação ou gestão de medicamentos ou para outros itens terapêuticos/prescritos apropriados.</purpose>
      <keywords>medicamento</keywords>
      <keywords>solicitação</keywords>
      <keywords>prescrever</keywords>
      <keywords>terapia</keywords>
      <keywords>substância</keywords>
      <keywords>fármaco</keywords>
      <keywords>terapêutico</keywords>
      <keywords>item terapêutico</keywords>
      <keywords>farmacêutico</keywords>
      <keywords>produto</keywords>
      <keywords>posologia</keywords>
      <keywords>tratamento</keywords>
      <keywords>fluido</keywords>
      <keywords>nutrição</keywords>
      <keywords>tempo</keywords>
      <keywords>administração</keywords>
      <keywords>dose</keywords>
      <use>Usado para gravar a combinação de uma quantidade de medicamento e o tempo de administração diário, como parte de uma solicitação ou gestão de medicamentos ou para outros itens terapêuticos/prescritos apropriados.&#xD;
O padrão de tempo diário pode ser simples como uma administração única ou múltiplas administrações com níveis variados de complexidade.&#xD;
&#xD;
Os detalhes de tempo que não estão dentro de um mesmo dia p.e. semanalmente ou mensalmente são incluídos dentro do arquétipo CLUSTER "Timing repetition" carregado dentro do arquétipo CLUSTER "Therapeutic direction".&#xD;
&#xD;
No contexto de uma INSTRUÇÃO terapêutica este arquétipo pode ser inserido dentro do SLOT "Dosage administration" no CLUSTER "Therapeutic direction" para gravar a dose e detalhes de tempo do padrão de uma administração única de um item terapêutico.&#xD;
&#xD;
No contexto de um arquétipo tipo ACTION insira este arquétipo diretamente no SLOT "Amount" para gravar a dose e tempo da administração de um item terapêutico.&#xD;
&#xD;
Tempos específicos de início e parada de administração devem ser especificados dentro do arquétipo CLUSTER "Timing - daily".</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sk</code_string>
      </language>
      <purpose>Slúži pre záznam množstva dávky a časov podania za jeden deň - ako časť preskripcie alebo medikácie alebo pre iné terapeutické/preskribovateľné položky.</purpose>
      <keywords>medikácia</keywords>
      <keywords>objendávka</keywords>
      <keywords>preskricpia</keywords>
      <keywords>terapia</keywords>
      <keywords>účinná látka</keywords>
      <keywords>liek</keywords>
      <keywords>terapeutický</keywords>
      <keywords>farmaceutický</keywords>
      <keywords>produkt</keywords>
      <keywords>liečba</keywords>
      <keywords>tekutina</keywords>
      <keywords>výživa</keywords>
      <keywords>časový rozpis</keywords>
      <keywords>podanie</keywords>
      <keywords>dávka</keywords>
      <use>Slúži pre záznam množstva dávky a časov podania za jeden deň - ako časť preskripcie alebo medikácie alebo pre iné terapeutické/preskribovateľné položky.&#xD;
Časový rozpis pre jeden deň môže byť jednoduchý - ako napr. jeden konkrétny čas podania alebo viacej časov podania - v závislosti od úrovne komplexity&#xD;
Časový rozpis, ktorý sa netýka iba jedného dňa napr. týždenný alebo mesačný rozpis, je potrebné zadať v CLUSTER 'Timing - non-daily' archetype , ktorý má byť vnorený v rámci CLUSTER 'Therapeutic direction' archetype.&#xD;
&#xD;
V kontexte INSTRUCTION tento archetyp má byť vložený v SLOTe "Štrukturované dávkovanie a časy podania" v rámci CLUSTER 'Therapeutic direction' archetypu - aby bolo možné zadať dávku a časový rozpis pre jednotlivé požadované podanie preskribovanej položky&#xD;
V kontexte ACTION tento archetyp má byť vložený priamo do SLOTu "Množstvo" - aby bolo možné zadať dávku a čas pre aktuálne podanie položky&#xD;
&#xD;
Špecifické časy pre začiatok podávania a koniec podávania majú byť špecifikované vo vloženom CLUSTER 'Timing - daily' archetype.</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record the combination of a medication amount and the administration timing within a single day, as part of a medication order or medication management or for other appropriate therapeutic/prescribable items.</purpose>
      <keywords>medication</keywords>
      <keywords>order</keywords>
      <keywords>prescribe</keywords>
      <keywords>therapy</keywords>
      <keywords>substance</keywords>
      <keywords>drug</keywords>
      <keywords>therapeutic</keywords>
      <keywords>therapeutic good</keywords>
      <keywords>pharmaceutical</keywords>
      <keywords>product</keywords>
      <keywords>posology</keywords>
      <keywords>treatment</keywords>
      <keywords>fluid</keywords>
      <keywords>nutrition</keywords>
      <keywords>timing</keywords>
      <keywords>administration</keywords>
      <keywords>dose</keywords>
      <use>Use to record the combination of a medication amount and the administration timing for a single day, as part of a medication order or medication management or for other appropriate therapeutic/prescribable items. &#xD;
The timing pattern for a single day can be as simple as a single administration time, or multiple administration times with varying levels of complexity.&#xD;
&#xD;
Timing details which are not within a single day, for example, weekly or monthly timings, are carried in the CLUSTER 'Timing - non-daily' archetype carried within the CLUSTER 'Therapeutic direction' archetype.&#xD;
&#xD;
In the context of a therapeutic INSTRUCTION, this archetype may be inserted into the 'Structured dose and timing directions' SLOT in the 'Therapeutic direction' CLUSTER to record the dose and timing details of the pattern of single intended administrations of a therapeutic item. &#xD;
&#xD;
In the context of an ACTION archetype insert this archetype directly into the 'Amount' SLOT to record the dose and timing of the actual administration of a therapeutic item.&#xD;
&#xD;
Specific administration start/stop times should be specified within a contained CLUSTER 'Timing - daily' archetype.</use>
      <misuse />
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Registrar la combinación de una cantidad de medicación y el momento de administración en un mismo día, como parte de una prescripción o gestión de medicación, o para otros elementos terapéuticos/prescribibles apropiados.</purpose>
      <keywords>medicación</keywords>
      <keywords>orden</keywords>
      <keywords>prescribir</keywords>
      <keywords>terapia</keywords>
      <keywords>sustancia</keywords>
      <keywords>medicamento</keywords>
      <keywords>terapéutico</keywords>
      <keywords>bien terapéutico</keywords>
      <keywords>farmacéutico</keywords>
      <keywords>producto</keywords>
      <keywords>posología</keywords>
      <keywords>tratamiento</keywords>
      <keywords>fluido</keywords>
      <keywords>nutrición</keywords>
      <keywords>timing</keywords>
      <keywords>administración</keywords>
      <keywords>dosis</keywords>
      <use>Se utiliza para registrar la combinación de una cantidad de medicación y el momento de administración para un solo día, como parte de una prescripción o gestión de medicación, o para otros elementos terapéuticos/prescribibles apropiados. &#xD;
&#xD;
La pauta temporal de un único día puede ser tan simple como una sola hora de administración, o varias horas de administración con distintos niveles de complejidad.&#xD;
&#xD;
Los detalles de temporización que no correspondan a un único día, por ejemplo, temporizaciones semanales o mensuales, han de llevarse a cabo en el arquetipo de tipo CLUSTER 'Temporización - no diaria', dentro del arquetipo CLUSTER 'Dirección terapéutica'.&#xD;
&#xD;
En el contexto de una INSTRUCTION terapéutica, este arquetipo puede insertarse en el SLOT "Direcciones estructuradas de dosis y timing", dentro del CLUSTER "Dirección terapéutica", para registrar los detalles de dosis y timing del patrón de administraciones únicas previstas de un elemento terapéutico. &#xD;
&#xD;
En el contexto de un arquetipo de tipo ACTION, inserte este arquetipo directamente en el SLOT "Cantidad" para registrar la dosis y el momento de la administración real de un elemento terapéutico.&#xD;
&#xD;
Las horas específicas de inicio y finalización de la administración deben especificarse dentro de un arquetipo CLUSTER "Timing - diario".</use>
      <misuse />
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ca</code_string>
      </language>
      <purpose>Registrar la combinació d’una quantitat de medicació i el moment d’administració en un mateix dia, com a part d’una prescripció o gestió de medicació o per a altres elements terapèutics/prescriptibles apropiats.</purpose>
      <keywords>medicació</keywords>
      <keywords>encàrrec</keywords>
      <keywords>prescriure</keywords>
      <keywords>teràpia</keywords>
      <keywords>substància</keywords>
      <keywords>medicament</keywords>
      <keywords>terapèutic</keywords>
      <keywords>producte terapèutic</keywords>
      <keywords>fàrmac</keywords>
      <keywords>producte</keywords>
      <keywords>posologia</keywords>
      <keywords>tractament</keywords>
      <keywords>fluid</keywords>
      <keywords>nutrició</keywords>
      <keywords>temporització</keywords>
      <keywords>administració</keywords>
      <keywords>dosi</keywords>
      <use>Utilitzar per a registrar la combinació d’una quantitat de medicació i el moment d’administració en un mateix dia, com a part d’una prescripció o gestió de medicació o per a altres elements terapèutics/prescriptibles apropiats.&#xD;
La pauta horària d’un únic dia pot ser tan simple com una sola hora d’administració o diverses hores d’administració amb diversos nivells de complexitat.&#xD;
&#xD;
Les dades de temporització que no corresponguin a un únic dia; per exemple, temporitzacions setmanals o mensuals, estan contingudes en l’arquetip de tipus CLUSTER «Temporització – no diària», que es troba dins de l’arquetip de tipus CLUSTER «Instruccions terapèutiques».&#xD;
&#xD;
En el context d’una INSTRUCTION terapèutica, aquest arquetip es pot inserir al SLOT «Instruccions estructurals de dosi i temporització» dins del CLUSTER «Instruccions terapèutiques» per a registrar les dades de dosi i temporalització de les pautes d’administracions úniques previstes d’un element terapèutic.&#xD;
&#xD;
En el context d’un arquetip de tipus ACTION, aquest arquetip s’ha d’inserir directament al SLOT «Quantitat» per a registrar la dosi i el moment d’una administració concreta d’un element terapèutic.&#xD;
&#xD;
Els moments específics d’inici i de finalització s’han d’especificar dins d’un arquetip «Temporització – diària» de tipus CLUSTER.</use>
      <misuse />
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Nazli Soltani, Natalia Strauch, Alexander Bachmeier</author>
    <author id="organisation">UMG, Medizinische Schule Hannover (MHH), Medizinische Hochschule Hannover, Heidelberg University Hospital</author>
    <author id="email">nazli.soltani@med.uni-goettingen.de, strauch.natalia@mh-hannover.de, Strauch.Natalia@mh-hannover.de, alexander.bachmeier@med.uni-heidelberg.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Therese Lindberg</author>
    <author id="organisation">Cambio CDS</author>
    <author id="email">therese.lindberg@cambio.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Silje Ljosland Bakke</author>
    <author id="organisation">Nasjonal IKT HF, Helse Vest IKT AS</author>
    <author id="email">silje.ljosland.bakke@helse-vest-ikt.no</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-br</code_string>
    </language>
    <author id="name">Debora Farage, Fernanda Maia, Laíse Figueiredo</author>
    <author id="organisation">Core Consulting</author>
    <author id="email">contato@coreconsulting.com.br</author>
    <accreditation>Hospital Alemão Oswaldo Cruz (HAOC)</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sk</code_string>
    </language>
    <author id="name">Alica Ciglanska</author>
    <author id="organisation">Prosoft Košice, a.s.</author>
    <author id="email">ciglanska.alica@prosoftke.sk</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es</code_string>
    </language>
    <author id="name">Julio de Sosa</author>
    <author id="organisation">Servei Català de la Salut</author>
    <author id="email">juliodesosa@catsalut.cat</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ca</code_string>
    </language>
    <author id="name">Manuel José Zafra Doménech</author>
    <author id="organisation">TRADCREA, S.L.</author>
    <author id="email">mzafra@tradcrea.com</author>
    <other_details id="other_contributors">Servei Català de la Salut</other_details>
  </translations>
  <uid>
    <value>938dd9db-f631-4df2-9221-07aeadac7917</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-CLUSTER.dosage.v2</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>
      <lower_unbounded>false</lower_unbounded>
      <upper_unbounded>true</upper_unbounded>
      <lower>0</lower>
    </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>at0164</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_COUNT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>magnitude</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_PRIMITIVE_OBJECT">
                <rm_type_name>INTEGER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <item xsi:type="C_INTEGER">
                  <range>
                    <lower_included>true</lower_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>true</upper_unbounded>
                    <lower>1</lower>
                  </range>
                </item>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0144</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_QUANTITY</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_QUANTITY&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="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>at0135</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_QUANTITY</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>at0178</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
          </children>
        </attributes>
      </children>
      <children xsi:type="ARCHETYPE_SLOT">
        <rm_type_name>CLUSTER</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </occurrences>
        <node_id>at0037</node_id>
        <includes>
          <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.timing_daily(-[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\.timing_daily(-[a-zA-Z0-9_]+)*\.v1</pattern>
              </item>
              <reference_type>constraint</reference_type>
            </right_operand>
          </expression>
        </includes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ELEMENT</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>0</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0134</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_DV_QUANTITY">
            <rm_type_name>DV_QUANTITY</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 />
            <property>
              <terminology_id>
                <value>openehr</value>
              </terminology_id>
              <code_string>126</code_string>
            </property>
            <list>
              <magnitude>
                <lower_included>true</lower_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>true</upper_unbounded>
                <lower>0.0</lower>
              </magnitude>
              <units>l/h</units>
            </list>
            <list>
              <magnitude>
                <lower_included>true</lower_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>true</upper_unbounded>
                <lower>0.0</lower>
              </magnitude>
              <units>ml/min</units>
            </list>
            <list>
              <magnitude>
                <lower_included>true</lower_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>true</upper_unbounded>
                <lower>0.0</lower>
              </magnitude>
              <units>ml/s</units>
            </list>
            <list>
              <magnitude>
                <lower_included>true</lower_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>true</upper_unbounded>
                <lower>0.0</lower>
              </magnitude>
              <units>ml/h</units>
            </list>
          </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>at0102</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>value</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_DURATION</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_PRIMITIVE_OBJECT">
                <rm_type_name>DV_DURATION</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <item xsi:type="C_DURATION">
                  <pattern>PDTHMS</pattern>
                  <range>
                    <lower_included>true</lower_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>true</upper_unbounded>
                    <lower>PT0S</lower>
                  </range>
                </item>
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_INTERVAL&lt;DV_DURATION&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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>lower</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DURATION</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>value</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_PRIMITIVE_OBJECT">
                    <rm_type_name>DV_DURATION</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_DURATION">
                      <pattern>PDTHMS</pattern>
                      <range>
                        <lower_included>true</lower_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>true</upper_unbounded>
                        <lower>PT0S</lower>
                      </range>
                    </item>
                  </children>
                </attributes>
              </children>
            </attributes>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>upper</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DURATION</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>value</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_PRIMITIVE_OBJECT">
                    <rm_type_name>DV_DURATION</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_DURATION">
                      <pattern>PDTHMS</pattern>
                      <range>
                        <lower_included>true</lower_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>true</upper_unbounded>
                        <lower>PT0S</lower>
                      </range>
                    </item>
                  </children>
                </attributes>
              </children>
            </attributes>
          </children>
        </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>at0176</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_QUANTITY</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_QUANTITY&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 />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>upper</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_QUANTITY</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>
        </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">Dosage</items>
        <items id="description">The combination of a medication amount and administration timing for a single day, in the context of a medication order or medication management.</items>
        <items id="comment">For example: '2 tablets at 6pm' or '20 mg three times per day'. Please note: this cluster allows multiple occurrences to enable representation of a complete set of dose patterns for a single dose direction.</items>
      </items>
      <items code="at0037">
        <items id="text">Daily timing</items>
        <items id="description">Structured details about the timing pattern for a single day.</items>
        <items id="comment">For example: 'in the morning', 'at 0600, 1400, 2100'.</items>
      </items>
      <items code="at0102">
        <items id="text">Administration duration</items>
        <items id="description">The period of time over which a single dose of the medication or vaccine should be administered.</items>
        <items id="comment">For example: 'Administer over 10 minutes'.</items>
      </items>
      <items code="at0134">
        <items id="text">Administration rate</items>
        <items id="description">The rate at which the medication, such as an infusion, is to be administered.</items>
        <items id="comment">For example: '200 ml/h'. Use the text data type to record non- or semi-quantifiable instructions.</items>
      </items>
      <items code="at0135">
        <items id="text">Dose formula</items>
        <items id="description">The formula used to calculate the dose amount or administration rate where this is dependent on some other factor, such as body weight or surface area.</items>
        <items id="comment">For example: '10 mg/kg/day'. The result of this formula would normally be held in Dose or Administration rate/duration. Where clinical measurements such as body weight is used in the dose calculation, a LINK attribute should used to specify which particular measurement has been used.</items>
      </items>
      <items code="at0144">
        <items id="text">Dose</items>
        <items id="description">The amount of medication administered at one time.</items>
        <items id="comment">For example: 1 mg, 1.5 ml, 0.125 g; or 1-2 ml, 12.5-20.5 mg.</items>
      </items>
      <items code="at0164">
        <items id="text">Dosage sequence</items>
        <items id="description">The intended position of this dosage within the overall sequence of dosages.</items>
        <items id="comment">For example: '1', '2', '3'. &#xD;
Where multiple dosages are expressed, the 'Pattern sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab in the morning, (2) 2 tab at 2pm, (3) 1 tab at night.</items>
      </items>
      <items code="at0176">
        <items id="text">Alternate dose</items>
        <items id="description">An alternate representation of the amount of medication administered at one time.</items>
        <items id="comment">For example, can be used to represent a unit-dose based value such as 'tabs', when the Dose amount is expressed as an SI unit such as 'mg', or where it is required to express the total volume of an infusion as well as the amount of the active ingredient.</items>
      </items>
      <items code="at0178">
        <items id="text">Dose description</items>
        <items id="description">Text description of the dose.</items>
        <items id="comment">For example: "Apply ointment to affected area until it glistens". This element is intended to allow implementers to use the structures for increasing/tapering dosages without necessarily specifying the doses in a structured way.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Dosering</items>
        <items id="description">Kombinasjonen av legemiddeldose og administrasjonstidspunkter for en dag, innenfor sammenhengen legemiddelordinering eller legemiddelhåndtering.</items>
        <items id="comment">For eksempel "2 tabletter kl. 18:00" eller "20 mg tre ganger om dagen". Merk: Dette clusteret er laget for å repeteres for å kunne representere et fullstendig sett av doseringsmønstre for en enkelt Terapeutisk anvisning.</items>
      </items>
      <items code="at0037">
        <items id="text">Administreringstidspunkt</items>
        <items id="description">Strukturerte detaljer om mønsteret for administreringstidspunkter innenfor en dag.</items>
        <items id="comment">For eksempel "om morgenen", "kl 6, 14 og 21".</items>
      </items>
      <items code="at0102">
        <items id="text">Administreringsvarighet</items>
        <items id="description">Tidsperioden en enkelt dose av legemiddelet eller vaksinen skal administreres over.</items>
        <items id="comment">For eksempel "Administreres over 10 minutter".</items>
      </items>
      <items code="at0134">
        <items id="text">Administreringshastighet</items>
        <items id="description">Hastigheten som skal benyttes under administreringen, for eksempel ved en infusjon.</items>
        <items id="comment">For eksempel "200 ml/t". Bruk datatypen "tekst" for å registrere ikke- eller semikvantifiserbare instruksjoner.</items>
      </items>
      <items code="at0135">
        <items id="text">Doseringsformel</items>
        <items id="description">Formelen som er brukt for å regne ut dosen eller administreringshastigheten der dette er avhengig av en annen faktor som f.eks. kroppsvekt eller hudoverflate.</items>
        <items id="comment">For eksempel "10 mg/kg/dag". Resultatet av denne formelen vil normalt registreres i Dosemengde/-enhet eller Administreringshastighet/-varighet. Der det benyttes kliniske målinger som for eksempel kroppsvekt i doseberegningen, bør det brukes en LINK-attributt for å spesifisere hvilken måling som er brukt.</items>
      </items>
      <items code="at0144">
        <items id="text">Dose</items>
        <items id="description">Legemiddelmengden (dosen) administrert på ett tidspunkt</items>
        <items id="comment">For eksempel 1 mg, 1,5 ml, 0.125 g eller 1-2 ml, 12.5-20.5 mg.</items>
      </items>
      <items code="at0164">
        <items id="text">Doseringsrekkefølge</items>
        <items id="description">Tilsiktet rekkefølge for denne doseringen i den overordnede sekvensen av doseringer.</items>
        <items id="comment">For eksempel "1", "2", "3". Der det er spesifisert flere doseringer, gjør Doseringsrekkefølge det tydelig hvilken rekkefølge de hører hjemme i. Eksempel: (1) 1 tablett om morgenen, (2) 2 tabletter kl. 14, (3) 1 tablett om kvelden.</items>
      </items>
      <items code="at0176">
        <items id="text">Alternativ dose</items>
        <items id="description">En alternativ representasjon av legemiddelmengden (dosen) administrert på ett tidspunkt.</items>
        <items id="comment">Kan for eksempel brukes for å representere en verdi basert på pakningsenheter som "tabletter", der Dosemengde uttrykkes som en SI-enhet som "mg", eller der det er nødvendig å uttrykke den totale mengden infusjonsvæske i tillegg til mengden aktiv substans.</items>
      </items>
      <items code="at0178">
        <items id="text">Dosebeskrivelse</items>
        <items id="description">Tekstbeskrivelse av dosen.</items>
        <items id="comment">For eksempel "Påfør salve på det affiserte området til det glinser". Dette elementet har som hensikt å tillate implementasjoner å bruke strukturene for økende og avtagende dosering uten å nødvendigvis spesifisere dosene strukturert.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Dose</items>
        <items id="description">A combinação de uma quantidade de medicamento e o tempo de administração para um único dia, no contexto de uma solicitação ou gestão de medicamento.</items>
        <items id="comment">Por exemplo: "2 comprimidos às 18h" ou "20 mg três vezes ao dia". Por favor note que: este cluster permite ocorrências múltiplas para possibilitar a representação de um conjunto completo de padrões de dose para uma orientação de dose única.</items>
      </items>
      <items code="at0037">
        <items id="text">Tempo</items>
        <items id="description">Detalhes estruturados sobre o padrão temporal dentro de um único dia.</items>
        <items id="comment">Por exemplo: "pela manhã", às 6h, 14h, 21h.</items>
      </items>
      <items code="at0102">
        <items id="text">Duração da administração</items>
        <items id="description">O período de tempo no qual uma única dose do medicamento ou vacina deve ser administrado.</items>
        <items id="comment">Por exemplo: "Administrar por 10 minutos".</items>
      </items>
      <items code="at0134">
        <items id="text">Taxa de administração</items>
        <items id="description">A taxa na qual o medicamento, como uma infusão, deve ser administrado.</items>
        <items id="comment">Por exemplo: "200 ml/h". Use o tipo de dado texto para gravar instruções qualitativas ou semi-quantitativas.</items>
      </items>
      <items code="at0135">
        <items id="text">Fórmula da dose</items>
        <items id="description">A fórmula utilizada para calcular a quantidade da dose ou taxa de administração à qual é dependente ou algum outro fator, como peso corporal ou área de superfície.</items>
        <items id="comment">*For example: '10mg/kg/day'. The result of this formula would normally be held in Dose or Administration rate/duration. Where clinical measurements such as body weight is used in the dose calculation, a LINK attribute should used to specify which particular measurement has been used. (en)</items>
      </items>
      <items code="at0144">
        <items id="text">*Dose (en)</items>
        <items id="description">*The value of the amount of medication administered at one time. (en)</items>
        <items id="comment">*For example: 1 mg, 1.5 ml, 0.125 g; or 1-2 ml, 12.5-20.5 mg. (en)</items>
      </items>
      <items code="at0164">
        <items id="text">Sequência de dosagem</items>
        <items id="description">A posição determinada desta dose dentro da sequência geral de doses.</items>
        <items id="comment">Por exemplo: "1", "2", "3". &#xD;
Quando são expressas múltiplas doses, a "Sequência Padrão" indica a ordem na qual deve ser explicitamente executada. Por exemplo: (1) 1 comprimido pela manhã, (2) 2 comprimidos às 14h, (3) 1 comprimido à noite.</items>
      </items>
      <items code="at0176">
        <items id="text">*Alternate dose (en)</items>
        <items id="description">*An alternate representation of the value of the amount of medication administered at one time. (en)</items>
        <items id="comment">*For example, can be used to represent a unit-dose based value such as 'tabs', when the Dose amount is expressed as an SI unit such as 'mg', or where it is required to express the total volume of an infusion as well as the amount of the active ingredient. (en)</items>
      </items>
      <items code="at0178">
        <items id="text">Descrição da dose</items>
        <items id="description">Descrição textual da dose.</items>
        <items id="comment">Por exemplo: "Aplicar pomada na área afetada até preenchê-la". Este elemento pretende permitir aos implementadores o uso de estruturas para doses crescentes/decrescentes sem especificar necessariamente as doses de uma forma estruturada.</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Dosierung</items>
        <items id="description">Kombination von Medikamentendosis und Verabreichungszeit an einem Tag im Kontext einer Medikamentenverordnung oder der Arzneimittelverwaltung.</items>
        <items id="comment">Zum Beispiel: "2 Tabletten um 18 Uhr" oder "20 mg dreimal täglich". Bitte beachten Sie: Dieser Cluster kann mehrfach vorkommen, um einen vollständigen Satz von Dosismustern für eine einzelne Dosisanweisung darzustellen.</items>
      </items>
      <items code="at0037">
        <items id="text">Tägliche Verabreichungszeiten</items>
        <items id="description">Strukturierte Details des Musters für Verabreichungszeiten innerhalb eines Tages.</items>
        <items id="comment">Zum Beispiel: "Morgens", "Um 06:00, 14:00, 21:00".</items>
      </items>
      <items code="at0102">
        <items id="text">Verabreichungsdauer</items>
        <items id="description">Der Zeitraum, in dem eine Einzeldosis des Medikaments oder Impfstoffs verabreicht werden soll.</items>
        <items id="comment">Zum Beispiel: "Über 10 Minuten verabreichen".</items>
      </items>
      <items code="at0134">
        <items id="text">Verabreichungsrate</items>
        <items id="description">Die Rate, mit der das Medikament, beispielsweise eine Infusion, verabreicht werden soll.</items>
        <items id="comment">Zum Beispiel: "200 ml/h". Verwenden Sie den Datentyp Text, um nicht- oder nur teilweise quantifizierbare Anweisungen aufzuzeichnen.</items>
      </items>
      <items code="at0135">
        <items id="text">Dosisformel</items>
        <items id="description">Die Formel zur Berechnung der Dosismenge oder der Verabreichungsrate, wenn dies von einem anderen Faktor abhängt, wie z. B. dem Körpergewicht oder der Hautoberfläche.</items>
        <items id="comment">Zum Beispiel: "10mg/kg/Tag". Das Ergebnis der Formel würde üblicherweise in Dosierung oder Verabreichungsrate/-dauer gehalten werden. Wenn klinische Maße, wie das Körpergewicht, bei der Berechnung der Dosis verwendet werden, sollte ein LINK-Attribut genutzt werden, um anzugeben, welche bestimmte Messung verwendet wurde.</items>
      </items>
      <items code="at0144">
        <items id="text">Dosis</items>
        <items id="description">Die Menge der verabreichten Medikation zu einem Zeitpunkt.</items>
        <items id="comment">Zum Beispiel: 1 mg, 1,5 ml, 0,125 g; oder 1-2 ml, 1,5-20,5 mg.</items>
      </items>
      <items code="at0164">
        <items id="text">Dosierungsreihenfolge</items>
        <items id="description">Beabsichtigte Reihenfolge dieser Dosierung in der Gesamtdosierungsfolge.</items>
        <items id="comment">Zum Beispiel: "1", "2", "3".&#xD;
Wenn mehrere Dosierungen angegeben werden, gibt die "Dosierungsreihenfolge" die Reihenfolge an, in der sie ausgeführt werden soll. Zum Beispiel: (1) 1 Tablette am Morgen, (2) 2 Tabletten um 14 Uhr, (3) 1 Tablette am Abend.</items>
      </items>
      <items code="at0176">
        <items id="text">Alternative Dosis</items>
        <items id="description">Eine alternative Darstellung vom Wert der verabreichten Medikation zu einem Zeitpunkt.</items>
        <items id="comment">Kann zum Beispiel verwendet werden, um einen Wert darzustellen, der auf Verpackungseinheit wie "Tabletten" basiert, wobei die Dosismenge als SI-Einheit angegeben ist, z. B. "mg"; oder wenn sowohl die Gesamtmenge als auch die Dosismenge des Wirkstoffes einer Infusionslösung angegeben werden müssen.</items>
      </items>
      <items code="at0178">
        <items id="text">Dosisbeschreibung</items>
        <items id="description">Textbeschreibung der Dosis.</items>
        <items id="comment">Zum Beispiel: "Salbe auf die betroffene Stelle auftragen, bis sie glänzt". Dieses Element soll den Entwicklern ermöglichen, die Strukturen zum Erhöhen / Verringern von Dosierungen zu verwenden, ohne die Dosierungen notwendigerweise auf strukturierte Weise spezifizieren zu müssen.</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Dosering</items>
        <items id="description">Kombinationen av läkemedelsmängd och administreringstidpunkt för en dag, i samband med en läkemedelsorder eller läkemedelshantering.</items>
        <items id="comment">Till exempel: "2 tabletter kl. 18" eller "20 mg tre gånger per dag". Observera: cluster tillåter här flera förekomster för att möjliggöra representation av en komplett uppsättning dosmönster för en enda dosriktning.</items>
      </items>
      <items code="at0037">
        <items id="text">Daglig timing</items>
        <items id="description">Strukturerade detaljer om tidsmönstret för en dag.</items>
        <items id="comment">Till exempel: "på morgonen", "0600, 1400, 2100".</items>
      </items>
      <items code="at0102">
        <items id="text">Administrationens varaktighet</items>
        <items id="description">Tiden under vilken en enda dos av läkemedlet eller vaccinet ska administreras.</items>
        <items id="comment">Till exempel: 'Administrera över 10 minuter'.</items>
      </items>
      <items code="at0134">
        <items id="text">Administrationshastighet</items>
        <items id="description">Den hastighet med vilken läkemedlet, såsom en infusion, ska administreras.</items>
        <items id="comment">Till exempel: '200 ml / h'. Använd textdatatypen för att spela in icke- eller halvkvantifierbara instruktioner.</items>
      </items>
      <items code="at0135">
        <items id="text">Doseringsformel</items>
        <items id="description">Formeln som används för att beräkna dosmängden eller administreringshastigheten då detta är beroende av någon annan faktor, såsom kroppsvikt eller ytarea.</items>
        <items id="comment">*For example: '10mg/kg/day'. The result of this formula would normally be held in Dose or Administration rate/duration. Where clinical measurements such as body weight is used in the dose calculation, a LINK attribute should used to specify which particular measurement has been used. (en)</items>
      </items>
      <items code="at0144">
        <items id="text">*Dose (en)</items>
        <items id="description">*The value of the amount of medication administered at one time. (en)</items>
        <items id="comment">*For example: 1 mg, 1.5 ml, 0.125 g; or 1-2 ml, 12.5-20.5 mg. (en)</items>
      </items>
      <items code="at0164">
        <items id="text">Doseringssekvens</items>
        <items id="description">Den avsedda positionen för denna dosering inom den totala doseringssekvensen.</items>
        <items id="comment">Till exempel: '1', '2', '3'.&#xD;
När flera doser uttrycks, gör 'Mönstresekvensen' ordningen i vilken de ska köras. Till exempel: (1) 1 flik på morgonen, (2) 2 flik vid 14:00, (3) 1 flik på natten.</items>
      </items>
      <items code="at0176">
        <items id="text">*Alternate dose (en)</items>
        <items id="description">*An alternate representation of the value of the amount of medication administered at one time. (en)</items>
        <items id="comment">*For example, can be used to represent a unit-dose based value such as 'tabs', when the Dose amount is expressed as an SI unit such as 'mg', or where it is required to express the total volume of an infusion as well as the amount of the active ingredient. (en)</items>
      </items>
      <items code="at0178">
        <items id="text">Doseringsbeskrivning</items>
        <items id="description">Textbeskrvining av dosen.</items>
        <items id="comment">Till exempel: "Applicera salva på det drabbade området tills det glänser". Detta element är avsett att tillåta implementerare att använda strukturerna för att öka/minska doser utan att nödvändigtvis specificera doserna på ett strukturerat sätt.</items>
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Dosificación</items>
        <items id="description">Combinación de una cantidad de medicación y el momento de administración para un mismo día, como parte de una prescripción o gestión de medicación.</items>
        <items id="comment">Por ejemplo: "2 comprimidos a las 18.00 horas" o "20 mg tres veces al día". Nota: este grupo permite múltiples ocurrencias para permitir la representación de un conjunto completo de patrones de dosis para una única dirección de dosis.</items>
      </items>
      <items code="at0037">
        <items id="text">Pauta horaria</items>
        <items id="description">Detalles estructurados sobre la pauta horaria de un solo día.</items>
        <items id="comment">Por ejemplo: "por la mañana", "a las 06.00, a las 14.00, a las 21.00".</items>
      </items>
      <items code="at0102">
        <items id="text">Duración de la administración</items>
        <items id="description">Periodo de tiempo durante el cual debe administrarse una dosis única del medicamento o vacuna.</items>
        <items id="comment">Por ejemplo: "Administrar durante 10 minutos".</items>
      </items>
      <items code="at0134">
        <items id="text">Velocidad de administración</items>
        <items id="description">La velocidad a la que debe administrarse la medicación, por ejemplo una infusión.</items>
        <items id="comment">Por ejemplo: "200 ml/h". Utilice el tipo de datos de texto para registrar instrucciones no cuantificables o semicuantificables.</items>
      </items>
      <items code="at0135">
        <items id="text">Fórmula de dosificación</items>
        <items id="description">La fórmula utilizada para calcular la cantidad de dosis o la tasa de administración cuando ésta depende de algún otro factor, como el peso corporal o la superficie.</items>
        <items id="comment">Por ejemplo: "10 mg/kg/día". El resultado de esta fórmula se mantendrá normalmente en Dosis o Tasa de administración/duración. Cuando en el cálculo de la dosis se utilicen medidas clínicas como el peso corporal, deberá utilizarse un atributo LINK para especificar qué medida concreta se ha utilizado.</items>
      </items>
      <items code="at0144">
        <items id="text">Dosis</items>
        <items id="description">La cantidad de medicación administrada de una sola vez.</items>
        <items id="comment">Por ejemplo: 1 mg, 1,5 ml, 0,125 g; o 1-2 ml, 12,5-20,5 mg.</items>
      </items>
      <items code="at0164">
        <items id="text">Secuencia de dosificación</items>
        <items id="description">La posición prevista de esta dosis dentro de la secuencia global de dosis.</items>
        <items id="comment">Por ejemplo: "1", "2", "3". &#xD;
Cuando se expresan dosis múltiples, la "Secuencia patrón" hace explícito el orden en que deben ejecutarse. Por ejemplo: (1) 1 cápsula por la mañana, (2) 2 cápsulas a las 14 horas, (3) 1 cápsula por la noche.</items>
      </items>
      <items code="at0176">
        <items id="text">Dosis alternativa</items>
        <items id="description">Representación alternativa de la cantidad de medicación administrada de una sola vez.</items>
        <items id="comment">Por ejemplo, puede utilizarse para representar un valor basado en la unidad de dosis, como "tabletas", cuando la cantidad de dosis se expresa como una unidad SI, como "mg", o cuando se requiere expresar el volumen total de una infusión, así como la cantidad de principio activo.</items>
      </items>
      <items code="at0178">
        <items id="text">Descripción de la dosis</items>
        <items id="description">Descripción textual de la dosis.</items>
        <items id="comment">Por ejemplo: "Aplicar pomada en la zona afectada hasta que brille". Este elemento está pensado para que los implementadores puedan utilizar las estructuras para aumentar/disminuir dosis sin especificar necesariamente las dosis de forma estructurada.</items>
      </items>
    </term_definitions>
    <term_definitions language="ca">
      <items code="at0000">
        <items id="text">Dosificació</items>
        <items id="description">La combinació d’una quantitat de medicació i el moment d’administració en un mateix dia, com a part d’una prescripció o gestió de medicació.</items>
        <items id="comment">Per exemple: «2 comprimits a les 18:00 h» o «20 mg tres vegades al dia». Nota: aquesta agrupació permet múltiples opcions per a permetre la representació d’un conjunt complet de pautes de dosificació que serveixen per a una única instrucció de dosificació.</items>
      </items>
      <items code="at0037">
        <items id="text">Pauta diària</items>
        <items id="description">Dades estructurals sobre la pauta horària d’un únic dia.</items>
        <items id="comment">Per exemple: «al matí», «a les 6:00 h, a les 14:00 h, a les 21:00 h».</items>
      </items>
      <items code="at0102">
        <items id="text">Durada de l'administració</items>
        <items id="description">Període de temps durant el qual s’ha d’administrar una única dosi de la medicació o vacuna.</items>
        <items id="comment">Per exemple: «Administrar durant 10 minuts».</items>
      </items>
      <items code="at0134">
        <items id="text">Freqüència d’administració</items>
        <items id="description">La freqüència amb la qual s’ha d’administrar la medicació. Per exemple, una infusió.</items>
        <items id="comment">Per exemple: «200 ml/hora». Utilitzar el tipus de dades de text per a registrar instruccions no quantificables o semiquantificables.</items>
      </items>
      <items code="at0135">
        <items id="text">Fórmula de dosificació</items>
        <items id="description">La fórmula utilitzada per a calcular la quantitat de dosi o la freqüència d’administració quan ambdues depenen d’algun altre factor, com el pes corporal o la superfície.</items>
        <items id="comment">Per exemple: «10 mg/kg/dia». El resultat d’aquesta fórmula normalment estarà contingut en freqüència/durada de Dosi o Administració. Quan s’utilitzen mesures clíniques com el pes corporal per a calcular la dosi, cal utilitzar un atribut LINK per a especificar la mesura concreta que s’ha utilitzat.</items>
      </items>
      <items code="at0144">
        <items id="text">Dosi</items>
        <items id="description">La quantitat de medicació administrada d’una sola vegada.</items>
        <items id="comment">Per exemple: 1 mg, 1,5 ml, 0,125 g; o 1-2 ml, 12,5-20,5 mg.</items>
      </items>
      <items code="at0164">
        <items id="text">Seqüència de dosificació</items>
        <items id="description">La posició prevista d’aquesta dosi dins de la seqüència global de dosis.</items>
        <items id="comment">Per exemple: «1», «2», «3».&#xD;
Quan s’expressen diverses dosis, la «Seqüència de pautes» explicita l’ordre en què s’han de realitzar. Per exemple: (1) 1 comprimit al matí, (2) 2 comprimits a les 14:00 h, (3) 1 comprimit a la nit.</items>
      </items>
      <items code="at0176">
        <items id="text">Dosi alternativa</items>
        <items id="description">Representació alternativa de la quantitat de medicació administrada al mateix temps.</items>
        <items id="comment">Per exemple: es pot utilitzar per a representar un valor basat en la unitat de dosi, com «comprimits», quan la quantitat de dosi s’expressa com una unitat del SI (Sistema Internacional), com «mg», o quan s’ha d’expressar el volum total d’una infusió, així com la quantitat del principi actiu.</items>
      </items>
      <items code="at0178">
        <items id="text">Descripció de la dosi</items>
        <items id="description">Descripció de la dosi.</items>
        <items id="comment">Per exemple: «Aplicar pomada a la zona afectada fins que brilli». Aquest element pretén que els implementadors puguin utilitzar les estructures per a augmentar/disminuir les dosis sense la necessitat d’especificar les dosis de manera estructurada.</items>
      </items>
    </term_definitions>
    <term_definitions language="sk">
      <items code="at0000">
        <items id="text">Dávkovanie</items>
        <items id="description">Slúži pre záznam množstva dávky a časov podania za jeden deň - ako časť preskripcie alebo medikácie</items>
        <items id="comment">Napr.: "2tbl o 18:00", "20mg 3x denne". Pozor: tento cluster umožňuje viacpočetný výskyt , aby bolo možné zapísať kompletný rozpis dávkovania pre jednotlivú dávku</items>
      </items>
      <items code="at0037">
        <items id="text">Denný rozpis</items>
        <items id="description">Štrukturované detaily ohľadom časového rozpisu pre jeden deň</items>
        <items id="comment">Napr.: "ráno", "o 6:00, 14:00, 12:00"</items>
      </items>
      <items code="at0102">
        <items id="text">Dĺžka podávania</items>
        <items id="description">Časový interval, počas ktorého má byť podávaná jednotlivá dávka lieku</items>
        <items id="comment">Napr.: "Podávajte 10min"</items>
      </items>
      <items code="at0134">
        <items id="text">Rýchlosť podávania</items>
        <items id="description">Rýchlosť , ktorou sa daný liek (ako napr infúzia) má podávať alebo podáva</items>
        <items id="comment">Napr.: "200ml/h". Pre nekvalifikovateľné údaje použite text</items>
      </items>
      <items code="at0135">
        <items id="text">Vzorec pre výpočet množstva dávky</items>
        <items id="description">Vzorec, ktorý sa použije pre výpočet množstva dávky alebo rýchlosti podania, v prípade, že to závislé od iných faktorov ako napr. váha pacienta alebo povrch tela</items>
        <items id="comment">Napr.: '10 mg/kg/day'. Výsledok tohto vzorca by mal by riadne zapísaný v elemente "Množstvo dávky" alebo "Rýchlosť podávania, Dĺžka podávania". V prípade, že boli použité fyzikálne parametre ako napr váha alebo povrch tela, mal by byť zadaný aj LINK atribút, aby bolo jasné , ktoré konkrétne meranie sa použilo.</items>
      </items>
      <items code="at0144">
        <items id="text">Dávka</items>
        <items id="description">Množstvo dávky, ktoré má byť podané naraz pri jednom podaní</items>
        <items id="comment">Napr.: 1 mg, 1.5 ml, 0.125 g; or 1-2 ml, 12.5-20.5 mg.</items>
      </items>
      <items code="at0164">
        <items id="text">Sekvencia dávkovania</items>
        <items id="description">Pozícia daného dávkovania v rámci celkovej sekvencie dávkovania</items>
        <items id="comment">Napr.: '1', '2', '3'. &#xD;
V prípade, že je zadaných viacej dávkovaní, táto sekvencia explicitne definuje poradie , v akom majú byť vykonané. Napr.: (1) 1 tbl ráno, (2) 2 tlb o 14:00, (3) 1 tbl večer.</items>
      </items>
      <items code="at0176">
        <items id="text">Alternatívna dávka</items>
        <items id="description">Alternatívne množstvo dávky, ktoré má byť podané naraz pri jednom podaní</items>
        <items id="comment">Napr.: môže byť použité v prípadoch, že jednotlivá dávka je v "tbl" alebo aj v SI jednotkách napr. "mg". Alebo v prípadoch, že je požadované zapísať celkový objem infúzie ako aj množstvá jednotlivých ingrediencií</items>
      </items>
      <items code="at0178">
        <items id="text">Popis množstva dávky</items>
        <items id="description">Textový popis k množstvu jednotlivej dávky</items>
        <items id="comment">Napr.: "aplikujte masť na postihnutú oblasť, kým sa leskne" . Účelom tohto elementu je umožniť evidenciu pre väčšiu alebo menšiu dávku, bez nutnosti ju špecifikovať štruktúrovaným spôsobom.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
