<?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">2015-10-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>Morten Aas, Oslo Universitetssykehus, Norway</other_contributors>
    <other_contributors>Tomas Alme, DIPS, Norway</other_contributors>
    <other_contributors>Ole Andreas Bjordal, Webmed, Norway</other_contributors>
    <other_contributors>Erling Are Hole, Helse Bergen, Norway</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, Helse Vest IKT AS, 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>Kristian Berg, Universitetssykehuset Nord Norge, Norway (Nasjonal IKT redaktør)</other_contributors>
    <other_contributors>SumanBhusan 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>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>Inderjit Daphu, Helse Bergen, Norway</other_contributors>
    <other_contributors>Gail Easterbrook, Flinders Medical Centre, Australia</other_contributors>
    <other_contributors>Gunn Elin Blakkisrud, DIPS ASA, Norway</other_contributors>
    <other_contributors>Stig Erik Hegrestad, Helse Førde, Norway</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>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Cecilie Graver, Oslo universitetssykehus HF, Norway</other_contributors>
    <other_contributors>Trina Gregory, cpc, Australia</other_contributors>
    <other_contributors>Bjørn Grøva, Diretoratet for e-helse, Norway</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>Kristian Heldal, Telemark Hospital Trust, Norway</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>Roar Holm, Helse Vest IKT A/S, Norway</other_contributors>
    <other_contributors>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Gunnar Jårvik, Nasjonal IKT HF, 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>Ole Kristian Losvik, Losol AS, 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>Fest Legemiddelverket, Statens Legemiddelverk, Norway</other_contributors>
    <other_contributors>Øygunn Leite Kallevik, Helse Bergen, Norway</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Colin Macfarlane, Elsevier, United Kingdom</other_contributors>
    <other_contributors>Alan March, Hospital Universitario Austral, Argentina</other_contributors>
    <other_contributors>Siv Marie Lien, DIPS ASA, Norway</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>Lars Morgan Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Stewart Morrison, NEHTA, Australia</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Anne Pauline Anderssen, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>Martin Paulson, Sykehuset i Vestfold, Norway</other_contributors>
    <other_contributors>Chris Pearce, Melbourne East GP Network, Australia</other_contributors>
    <other_contributors>Kristian Pedersen, Nordlandssykehuset HF, Norway</other_contributors>
    <other_contributors>Rune Pedersen, Universitetssykehuset i Nord Norge, Norway</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>Cathy Richardson, NEHTA, Australia</other_contributors>
    <other_contributors>Robyn Richards, NEHTA - Clinical Terminology, Australia</other_contributors>
    <other_contributors>Tanja Riise, Nasjonal IKT HF, Norway</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>Raymond Simkus, Brookswood Family Practice, Canada</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>Tesfay Teame, Folkehelseinstituttet, Norway</other_contributors>
    <other_contributors>Richard Townley-O'Neill, Australian Digital Health Agency, Australia</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Ines Vaz, UFN, Portugal</other_contributors>
    <other_contributors>Nils Widnes, Helse-Bergen, Norway</other_contributors>
    <other_contributors>Kylie Young, The Royal Australian College of General Practitioners, Australia</other_contributors>
    <lifecycle_state>in_development</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">HiGHmed</other_details>
    <other_details id="references">Derived from: &lt;Add reference to original resource here&gt;&#xD;
&#xD;
Medication instruction, Draft Archetype [Internet]. nehta, Australia, nehta Clinical Knowledge Manager [cited: 2015-12-15]. Available from: http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.838&#xD;
&#xD;
Intermountain Healthcare Medication order model, Personal Communication to Sam Heard by Dr Stan Huff.&#xD;
&#xD;
Royal Australian College of General Practitioners. Fact Sheet: Medicines List. 2010.&#xD;
&#xD;
NHS HSCIC Messaging Implementation Manual (GP2GP messages) http://www.uktcregistration.nss.cfh.nhs.uk/trud3&#xD;
&#xD;
Standards for medication and medical device records – technical annex [Internet]. RCP London. [cited 2015 Dec 15]. Available from: https://www.rcplondon.ac.uk/projects/outputs/standards-medication-and-medical-device-records-technical-annex</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.highmed</other_details>
    <other_details id="original_publisher">HiGHmed</other_details>
    <other_details id="custodian_namespace">org.highmed</other_details>
    <other_details id="MD5-CAM-1.0.1">97E8170BDF74FF3DD735CCC13D028B13</other_details>
    <other_details id="build_uid">22ae3d47-2e7c-4d56-945a-09195236ac0d</other_details>
    <other_details id="revision">3.0.0-alpha</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Repräsentation aller Aspekte einer Verordnung eines Arzneimittels, Impfstoffs, Ernährungsprodukts oder eines anderen therapeutischen Mittels für eine bestimmte Person.</purpose>
      <keywords>Medikament</keywords>
      <keywords>Verordnung</keywords>
      <keywords>Rezept</keywords>
      <keywords>verschreiben</keywords>
      <keywords>verordnen</keywords>
      <keywords>Therapie</keywords>
      <keywords>Substanz</keywords>
      <keywords>Wirkstoff</keywords>
      <keywords>Arzneimittel</keywords>
      <keywords>therapeutisch</keywords>
      <keywords>OTC</keywords>
      <keywords>rezeptfrei</keywords>
      <keywords>therapeutisches Mittel</keywords>
      <keywords>Pharmazeutikum</keywords>
      <keywords>Produkt</keywords>
      <keywords>Posologie</keywords>
      <keywords>Dosierung</keywords>
      <keywords>Behandlung</keywords>
      <keywords>Flüssigkeit</keywords>
      <keywords>Ernährung</keywords>
      <keywords>Arzneimittelverordnung</keywords>
      <keywords>CPOE</keywords>
      <use>Verwende diesen Archetypen, um alle Aspekte einer Verordnung eines Arzneimittels, Impfstoffs, Ernährungsprodukts oder medizinischen Bedarfs für eine bestimmte Person darzustellen.&#xD;
&#xD;
Der Archetyp ist für jede Arzneimittelart und die damit verbundene Verordnung bestimmt, unabhängig davon, ob sie von einem medizinischen Fachpersonal verschrieben wird oder, ob sie "rezeptfrei" erhältlich ist. Der Anwendungsbereich dieses Medikamenten-Archetyps umfasst auch Verordnungen von Impfungen, parenteralen Flüssigkeiten oder anderen therapeutischen Mitteln, wie Verbände, Ernährungsprodukte oder andere Erzeugnisse, die angewendet oder verabreicht werden, um eine therapeutische Wirkung zu erzielen, sowie ein gemeinsames Muster für die Datenerfassung haben.&#xD;
&#xD;
Der Archetyp ist für die Verwendung in einer Reihe von klinischen Kontexten konzipiert, einschließlich, aber nicht beschränkt auf:&#xD;
- eine Aufzeichnung in einer klinischen Beratung (COMPOSITION.encounter);&#xD;
- ein schriftliches Rezept eines Arztes, Zahnarztes, Krankenpflegers oder einer anders bezeichneten medizinischen Fachkraft für ein Arzneimittel oder ein Ernährungsprodukt, das ausgegeben und verabreicht werden soll (innerhalb eines COMPOSITION.prescription);&#xD;
- ein Element in einer aktuellen Medikamentenliste, einem Rezept oder einer Medikamentenübersicht (innerhalb der COMPOSITION.medication_list); und&#xD;
- ein Element in einem zusammenfassenden Dokuments, wie z.B. die Übertragung von Pflegeleistungen (COMPOSITION.transfer_summary) oder eine Überweisung (COMPOSITION.request).&#xD;
&#xD;
Eine Medikamentenverordnung ist in meisten Fällen einfach - normalerweise für ein einzelnes Arzneimittel mit unkomplizierten Anweisungen für die Abgabe und Verabreichung. Dieser Archetyp soll jedoch auch komplexere therapeutische Verordnungen ermöglichen. Zum Beispiel:&#xD;
&#xD;
- eine reduzierte Dosis von Prednisolon über einen Zeitraum von Wochen;&#xD;
- Insulintitration mit Dosierung abhängig von Testergebnissen;&#xD;
- mehrere Medikamente, die gleichzeitig im Rahmen eines einzelnen Medikamentenplans verschrieben werden, wie beispielsweise eine Dreifachtherapie bei Magengeschwür;&#xD;
- intravenöse Verabreichung von Medikamenten oder Nahrungsergänzungsmitteln, einschließlich parenteraler Ernährung.&#xD;
&#xD;
Der Archetyp wurde daher so entworfen, um eine Reihe von Komplexitäten zuzulassen: &#xD;
- einfache Anweisungen bei Rezepten wie "Furosemid 40 mg zwei Tabletten morgens und eine zum Mittagessen", um die Kompatibilität mit bestehenden Systemen zu gewährleisten;&#xD;
- die Menge des Arzneimittels wird normalerweise in Form einer Anzahl und einer entsprechenden Dosiseinheit dargestellt. Alternativ kann jedoch auch ein Statement getroffen werden, um die Kompatibilität mit vorhandenen Systemen und die Abdeckung aller klinischen Szenarien sicherzustellen.&#xD;
- strukturierte Details für Dosis, Verabreichungsweg und Zeitpunkt, um eine vollständig berechenbare Spezifikation darzustellen.&#xD;
&#xD;
Es wurde auch so konzipiert, dass eine einzige Darstellung der Medikamentenverordnung folgendes darstellen kann:&#xD;
- komplexe aufeinanderfolgende Medikamentenverordnungen mit derselben Arzneimittelstärke werden innerhalb einer einzigen Verordnungsstruktur unterstützt;&#xD;
- mehrere Medikamentenverordnungen können verkettet werden, wenn verschiedene Medikamente oder Arzneizubereitungen nacheinander verabreicht werden müssen.&#xD;
&#xD;
Dieser Archetyp eignet sich auch für die Verordnung von parenteralen Flüssigkeiten in Pflegeeinrichtungen, in denen es üblich ist, solche "verordnungsfähige" Stoffe herzustellen. In anderer Umgebung kann eine separate "Verordnung parenteraler Flüssigkeit" angebracht sein.&#xD;
&#xD;
SLOTs mit CLUSTER-Archetypen wurden aus drei Gründen verwendet, um einen Teil des Inhalts darzustellen:&#xD;
- um einen zentralen Archetyp zu erhalten, der für alle oben genannten Anwendungsfälle verwendet werden kann und dennoch Flexibilität bietet, wo es erforderlich ist, z.B. der SLOT „Arzneimitteldetails“', wo zusätzliche strukturierte Details hinzugefügt werden können. Ein Kandidat-Archetyp wird für Arzneimittel vorgeschlagen. Es ist möglich, dass in Zukunft andere CLUSTER-Archetypen für andere Zwecke, wie z.B. komplexe Verordnungen von parenteraler Ernährung, benötigt werden;&#xD;
- Unterstützung der Wiederverwendung von Archetypen in Situationen, in denen der Inhalt auch in anderen klinischen Kontexten verwendet wird, hauptsächlich im zugehörigen Archetyp ACTION.medication, um tatsächliche Abgabe, Verabreichung usw. darzustellen; und&#xD;
- um weniger genutzten Inhalt aus dem zentralen Archetyp-Framework zu entfernen.&#xD;
&#xD;
Mehrfache Verordnungen können als separate Aktivitäten innerhalb dieser einzigen Archetypen-Instanz dargestellt werden, um eng gebundene Verordnungen verschiedener Medikamente zu tragen, z.B. H. pylori-Therapie, wenn diese nicht als einzelne Packung verschrieben wird.&#xD;
&#xD;
Beachten Sie, dass diese Verwendungen sowohl die Anwendungsfälle der FHIR-Profile „Medikation Order“ als auch „Medikation Statement“ zusammenfassen. D.h. dieser Archetyp ist eine Übereinstimmung für beide FHIR-Ressourcen, die im entsprechenden Kontext verwendet werden.</use>
      <misuse>Nicht zur Repräsentation der Aktivitäten im Zusammenhang mit der Ausführung der Verordnung von Medikamenten, Impfstoffen, Nahrungsmitteln oder therapeutischen Mitteln verwenden, z. B. Angaben zur tatsächlichen Verabreichung oder Abgabe. Verwenden Sie dafür den Archetyp ACTION.medication.&#xD;
&#xD;
Nicht zur Repräsentation der Verordnung von Blutprodukten verwenden, da dies einen grundlegend anderen klinischen Prozess beinhaltet und wahrscheinlich andere unterstützende Informationen erfordert. Verwenden Sie dafür den Archetyp INSTRUCTION.transfusion.&#xD;
&#xD;
Nicht zur Repräsentation der Verordnung zum Einsetzen von Implantaten oder medizinischen Geräten wie Herzschrittmachern und Defibrillatoren verwenden. Verwenden Sie dafür den Archetyp INSTRUCTION.procedure</misuse>
      <copyright>© openEHR Foundation, HiGHmed</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Att registrera samtliga aspekter av en beställning av ett läkemedel, vaccin, näringspreparat eller annat terapeutiskt produkt för en identifierad individ.</purpose>
      <keywords>medicinering</keywords>
      <keywords>order</keywords>
      <keywords>beställning</keywords>
      <keywords>ordinera</keywords>
      <keywords>terapi</keywords>
      <keywords>substans</keywords>
      <keywords>läkemedel</keywords>
      <keywords>terapeutisk</keywords>
      <keywords>farmaceutisk</keywords>
      <keywords>produkt</keywords>
      <keywords>dosering</keywords>
      <keywords>behandling</keywords>
      <keywords>vätska</keywords>
      <keywords>näring</keywords>
      <keywords>medicin</keywords>
      <use>Används för att registrera samtliga aspekter av en beställning av ett läkemedel, vaccin, näringspreparat eller annan terapeutisk produkt för en identifierad individ.&#xD;
&#xD;
Den här arketypen är avsedd att användas för alla typer av läkemedel och relaterade ordrar, oavsett om de ordinerats av vårdpersonal eller är tillgängligt för köp "över disk". Omfattningen av denna arketyp inkluderar även beställning av vaccin, parenterala vätskor och andra terapeutiska produkter, såsom bandage, näringspreparat eller andra föremål som appliceras eller administreras för att uppnå en terapeutisk effekt. &#xD;
&#xD;
Denna arketyp är utformad för att användas vid ett flertal kliniska sammanhang, bland annat: &#xD;
- dokumentation i ett kliniskt samråd (COMPOSITION.encounter);&#xD;
- skriftlig ordination av en läkare, tandläkare, sjuksköterska eller annan utsedd hälso- och sjukvårdspersonal för ett läkemedel eller ett näringsperparat som ska dispenseras och administreras (COMPOSITION.prescription);&#xD;
- objekt i aktuell läkemedelslista, ordination eller läkemedelsjournal (COMPOSITION.medication_list); och&#xD;
- objekt i ett sammanfattande dokument för exempelvis vårdöverföring (COMPOSITION.transfer_summary) eller en remiss (COMPOSITION.request).&#xD;
&#xD;
I många fall är en läkemedelsbeställning simpel och omfattar vanligtvis en läkemedelsartikel med okomplicerade instruktioner för dosering och administrering. Denna arketyp är dock utformad för att även möjliggöra mer komplexa beställningar. Till exempel:&#xD;
- en reducerande dos av prednisolon under en period på några veckor;&#xD;
- titrering av insulin, med dosering beroende på testresultat;&#xD;
- flera läkemedel (del av samma läkemedelsregim) som ordinerats samtidigt. Exempelvis trippelbehandling för magsår; och&#xD;
- intravenös administrering av läkemedel eller näringstillskott, inklusive parenteral nutrition. &#xD;
&#xD;
Arketypen har därför utformats för att hantera olika komplexiteter:&#xD;
- enkla beställningsinstruktioner som "furosemid 40 mg två tabletter på morgonen och en vid lunch" för att säkerställa kompatibilitet med befintliga system; och&#xD;
- läkemedelsmängden betecknas vanligtvis genom antal och motsvarande dosenhet. För att säkerställa kompatibilitet med befintliga system samt omfatta alla kliniska scenarier, kan det dock finnas alternativa redogörelser; genom att &#xD;
- strukturera detaljer för dosering, administreringsväg och tidpunkt för att uppnå fullständig specifikation. &#xD;
&#xD;
Arketypen har även utformats så att strukturen för alla läkemedelsbeställningar omfattar:&#xD;
- komplexa och sekventiella läkemedelsbeställningar med samma beredningsstyrka; och&#xD;
- flera läkemedelsbeställningar kan under omständigheter där olika läkemedel eller preparat måste ges i följd länkas.&#xD;
&#xD;
Arketypen är även lämplig för beställning av parenterala vätskor, trots att dessa normalt är "ordinationsbara" artiklar. I andra fall kan dock en separat "parenteral vätskebeställning" vara lämpligt. &#xD;
&#xD;
De SLOTs som innehåller CLUSTER-arketyper används för att representera vis del av innehållet. Detta grundas på tre skäl:&#xD;
- För att säkerställa att en kärnarketyp kan användas för alla ovanstående användningsfall, samt möjliggöra flexibilitet där det behövs. Under exempelvis ”Detaljer om beredning” kan ytterligare information tilläggas. För läkemedel föreslås en kandidatarketyp. Det är även möjligt att andra CLUSTER-arketyper i framtiden kan krävas för ytterlige ändamål, såsom komplexa parenterala nutritionsordrar;&#xD;
- för att stödja återanvändning av arketyper i situationer där innehållet används i flera kliniska sammanhang, i synnerhet ACTION.medication-arketypen som används för registrering av dispensering, administrering osv; och&#xD;
- för att avlägsna mindre vanligt förekommande innehåll från kärnarketypen.&#xD;
&#xD;
Flera beställningar kan representeras som separata aktiviteter inom denna arketypsinstans, för hantering av beställningar av olika läkemedel, exempelvis terapi för H. pylori när det inte ordineras som enpack.&#xD;
&#xD;
Det bör nämnas att dessa användningsområden omfattar både fall av FHIR-läkemedelsorder och läkemedelsutlåtande. Denna arketyp är således anpassad för båda FHIR-resurserna, och används i lämpligt sammanhang.</use>
      <misuse>Ska inte användas för att registrera aktiviteter relaterade till att utföra en beställning av läkemedel, vaccin, näringspreparat eller terapeutiska produkter, såsom information om administrering eller dispensering. Använd i stället ACTION.medication för detta ändamål.&#xD;
&#xD;
Ska inte användas för att registrera beställning av blodprodukter, då denna aktivitet kräver annan klinisk process. Använd i stället INSTRUCTION.transfusion för detta ändamål.&#xD;
&#xD;
Ska inte användas för att registrera beställning av insättning av implantat eller medicintekniska produkter som pacemaker och defibrillatorer. Använd i stället INSTRUCTION.procedure för detta ändamål.</misuse>
      <copyright>© openEHR Foundation, HiGHmed</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere alle aspekter av ordinering av et legemiddel, en vaksine, ernæringsprodukt eller medisinsk forbruksmateriell for et spesifikt individ.</purpose>
      <keywords>medikasjon</keywords>
      <keywords>foreskriving</keywords>
      <keywords>forordning</keywords>
      <keywords>forordne</keywords>
      <keywords>terapi</keywords>
      <keywords>substans</keywords>
      <keywords>stoff</keywords>
      <keywords>virkestoff</keywords>
      <keywords>medikament</keywords>
      <keywords>legemiddel</keywords>
      <keywords>terapeutisk</keywords>
      <keywords>medisinsk forbruksmateriell</keywords>
      <keywords>ordinering</keywords>
      <keywords>preparat</keywords>
      <keywords>spesialpreparat</keywords>
      <keywords>diagnostikum</keywords>
      <keywords>forskrivning</keywords>
      <keywords>forskriving</keywords>
      <keywords>resept</keywords>
      <keywords>legemiddelhåndtering</keywords>
      <keywords>farmasøytisk</keywords>
      <keywords>produkt</keywords>
      <keywords>posologi</keywords>
      <keywords>ordinasjon</keywords>
      <keywords>rekvirering</keywords>
      <keywords>behandling</keywords>
      <keywords>væske</keywords>
      <keywords>ernæring</keywords>
      <keywords>ordinere</keywords>
      <keywords>medisin</keywords>
      <keywords>medisiner</keywords>
      <keywords>medisinering</keywords>
      <use>Brukes for å registrere alle aspekter av ordinering av et legemiddel, en vaksine, enæringsvare eller medisinsk forbruksmateriell for et spesifikt individ.&#xD;
&#xD;
Arketypen kan brukes i alle legemiddelrelaterte ordineringer, enten de er for reseptpliktige legemidler ordinert av en kliniker, eller for reseptfrie legemidler. Arketypen dekker også ordinering av vaksiner, parenterale væsker, eller medisinsk forbruksmateriell, som bandasjer, ernæringsprodukter eller andre varer som påføres eller administreres for å ha en terapeutisk effekt, og der dataene som skal registreres er de samme.&#xD;
&#xD;
Arketypen er designet for bruk i en rekke ulike kliniske sammenhenger, for eksempel:&#xD;
- en registrering i en klinisk konsultasjon (COMPOSITION.encounter).&#xD;
- en resept skrevet av en lege, tannlege eller annet helsepersonell, på et legemiddel eller ernæringsprosdukt som skal utdeles eller administreres (i en COMPOSITION.prescription).&#xD;
- et element i en legemiddelliste, resept eller legemiddelkurve (COMPOSITION.medication_list)&#xD;
- et element i et oppsummeringsdokument som f.eks. en epikrise (COMPOSITION.transfer_summary) eller en henvisning (COMPOSITION.request).&#xD;
&#xD;
Merk at disse bruksområdene omfatter FHIR-ressursene for både Medication Order og Medication Statement.&#xD;
&#xD;
I mange tilfeller vil legemiddelordineringen være enkel - typisk for en enkelt legemiddelvare med ukompliserte instruksjoner for utdeling og administrering. Arketypen er imidlertid også utviklet for å tillate mer komplekse ordineringer, for eksempel:&#xD;
- ved nedtrapping av en prednisolondose over flere uker.&#xD;
- ved titrering av insulin, hvor dosering er avhengig av prøveresultater.&#xD;
- flere legemidler ordinert på samme tidspunkt som en del av et samlet behandlingsregime, for eksempel trippelbehandling for magesår.&#xD;
- ved parenteral administrering av legemidler eller ernæring, inkludert parenteral ernæring.&#xD;
&#xD;
Arketypen er derfor utviklet for å tillate ulik kompleksitet, fra&#xD;
- enkle fritekstinstrukser for ordineringer som "Furosemid 40 mg, to tabletter om morgenen og en til lunsj" for å sikre kompatibilitet med eksisterende systemer, og&#xD;
- legemiddelmengden representeres som regel ved et tall med tilhørende måleenhet, alternativt med fritekst for å sikre kompatibilitet med eksisterende systemer og for å dekke alle kliniske scenarier&#xD;
til&#xD;
- strukturerte detaljer for dose, administreringssvei og administreringsstidspunkter for at datamaskiner skal kunne lese og gjøre beregninger med dataene.&#xD;
&#xD;
Arketypen er designet slik at en enkel legemiddelordinering kan representere:&#xD;
-komplekse sekvensielle legemiddelordineringer som bruker samme preparatstyrke i samme ordineringsstruktur.&#xD;
-flere legemiddelordineringer kan lenkes, der ulike legemidler eller blandinger må administreres sekvensielt.&#xD;
&#xD;
Arketypen er også egnet for å ordinere væsker, der det er vanlig at disse ordineres. I andre sammenhenger kan det være mer passende å bruke en egen arketype for væskeforordninger.&#xD;
&#xD;
Mengden av et legemiddel representeres vanligvis med et tall og en enhet, men det kan også dokumenteres i fritekst for å sikre kompatibilitet med eksisterende systemer og for å dekke alle scenarier.&#xD;
&#xD;
SLOTer med CLUSTER-arketyper brukes for å representere deler av innholdet av tre årsaker:&#xD;
- For å sikre en kjernearketype som kan brukes i alle de overnevnte brukscasene, men likevel være fleksibel der det trengs, f.eks. i SLOTet "Legemiddeldetaljer" der ytterligere strukturerte detaljer kan legges til. Det er foreslått en arketype for detaljer om legemidler, og det kan tenkes at man i fremtiden vil trenge andre CLUSTER-arketyper for andre formål, som f.eks. komplekse ordineringer av parenteral ernæring.&#xD;
- for å tillate gjenbruk av arketyper i situasjoner hvor innholdet også brukes i andre kliniske kontekster, i hovedsak i den tilhørende arketypen ACTION.medication for å registrere faktisk utdeling, administrering osv.&#xD;
- for å fjerne mindre brukt innhold fra arketypens rammeverk.&#xD;
&#xD;
Det er mulig å legge inn flere ordinasjoner som aktiviteter innenfor én instans av arketypen for å representere tett sammenbundne ordinasjoner av forskjellige legemidler, for eksempel en legemiddelpakke mot H. pylori der denne ikke ordineres som en enkelt pakning.&#xD;
&#xD;
Merk at disse bruksområdene innbefatter FHIR-ressursene for både "Medication Order" og "Medication Statement", det vil si at denne arketypen matcher begge disse FHIR-ressursene i passende brukssammenhenger.</use>
      <misuse>Skal ikke brukes for å registrere faktisk administrering eller utdeling av legemidler, vaksiner, parenterale væsker, ernæringsprodukter eller medisinsk forbruksmateriell. Bruk arketypen ACTION.medication for dette formålet.&#xD;
&#xD;
Skal ikke brukes for å registrere ordinering av blodkomponenter, som omfatter en fundamentalt ulik klinisk prosess og sannsynligvis vil trenge ulik støtteinformasjon. Bruk arketypen INSTRUCTION.transfusion for dette formålet.&#xD;
&#xD;
Skal ikke brukes for å registrere ordinering av innlegging av implantater og medisinsk utstyr som pacemakere og defibrillatorer. Bruk arketypen INSTRUCTION.procedure for dette formålet.</misuse>
      <copyright>© openEHR Foundation, HiGHmed</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es-ar</code_string>
      </language>
      <purpose>Registrar todos los aspectos de una orden de medicamento, vacuna, producto nutricional u otro ítem terapéutico para un individuo identificado.</purpose>
      <keywords>medicamento</keywords>
      <keywords>orden</keywords>
      <keywords>prescribir</keywords>
      <keywords>prescripción</keywords>
      <keywords>terapéutica</keywords>
      <keywords>substancia</keywords>
      <keywords>droga</keywords>
      <keywords>terapéutico</keywords>
      <keywords>sin receta</keywords>
      <keywords>insumo terapéutico</keywords>
      <keywords>fármaco</keywords>
      <keywords>producto</keywords>
      <keywords>posología</keywords>
      <keywords>tratamiento</keywords>
      <keywords>fluido</keywords>
      <keywords>nutrición</keywords>
      <keywords>CPOE</keywords>
      <use>Utilizar para el registro de todos los aspectos de una orden de medicamento, vacuna, producto nutricional u otro ítem terapéutico para un individuo identificado.&#xD;
&#xD;
Su objetivo es la utilización para cualquier orden de medicamento o ítems relacionados, ya sea que los prescriba un profesional de la salud o que se encuentren disponibles sin receta médica. El alcance de este arquetipo de medicamento incluye órdenes de vacuna, fluidos parenterales u otros insumos terpéuticos tales como vendajes, productos nutricionales u otros ítems que se aplican o son administrados para obtener un efecto terapéutico, y que tiene un patrón común de registro de datos.&#xD;
&#xD;
Este arquetipo seta diseñado para ser utilizado en un conjunto de contexto clínicos que incluyen, pero no se limitan, a:&#xD;
- un registro de una consulta clínica (COMPOSITION.encounter);&#xD;
- una prescripción escrita por un médico, odontólogo, enfermero u otro profesional de la salud, para una medicación o producto nutricional a ser dispensado y administrado (como parte de una COMPOSITION.prescription);&#xD;
- un ítem incluido en una lista de medicamentos recibidos actualmente, en una prescripción o en una lista de medicamentos (como parte de una COMPOSITION.medication_list); y como&#xD;
- un ítem incluido en un documento de resumen, tal como una transferencia de sitio de cuidados (COMPOSITION.transfer_summary) o una interconsulta (COMPOSITION.request).&#xD;
&#xD;
En muchos casos una orden de medicamento será simple -típicamente para un solo ítem medicamentoso con instrucciones carentes de complejidad para su dispensación y administración. Sin embargo, este arquetipo también esta diseñado para permitir órdenes terapéuticas mas complejas, como por ejemplo:&#xD;
- la reducción de una dosis de prednisolona a lo largo de un período de semanas;&#xD;
- la titulación de insulina, donde la dosis dependerá de los resultados de una prueba;&#xD;
- la prescripción simultanea de varios medicamentos como parte de un régimen único de medicamentos, tales como la terapia triple para la úlcera péptica; y&#xD;
- la administración endovenosa de medicamentos o suplementos nutricionales, incluyendo nutrición parenteral.&#xD;
&#xD;
El arquetipo ha sido por lo tanto diseñado para permitir diversos rangos de complejidad, desde:&#xD;
- instrucciones narrativas simples para órdenes tales como "furosemida 40 miligramos, dos tabletas por la mañana y una al almuerzo", para asegurar la compatibilidad con sistemas existentes&#xD;
- la cantidad de la medicación, usualmente representada en términos de un número y su correspondiente unidad de dosis, pero que alternativamente puede ser representada mediante una narrativa para asegurar compatibilidad con sistemas existentes y la cobertura de diferentes escenarios clínicos; hasta&#xD;
- el detalle estructurado de la dosis, vía de administración y temporalidad, para así representar una especificación completamente computable.&#xD;
&#xD;
También ha sido diseñado de modo tal que la estructura de una sola orden de medicamento permita representar:&#xD;
- una secuencia compleja de órdenes de medicamento que utiliza la misma potencia del preparado como una sola estructura de orden; y&#xD;
- múltiples órdenes de medicamentos encadenadas en circunstancias donde diferentes medicamentos o preparados deben ser administrados conforme a una secuencia.&#xD;
&#xD;
Este arquetipo es también adecuado para ordenar fluidos en entornos de cuidado donde es de uso corriente que estos ítems sean "prescribibles". EN otros contextos una orden separada de fluido parenteral podría ser mas apropiada.&#xD;
&#xD;
Los SLOTs que contienen arquetipos CLUSTER han sido utilizados para representar parte del contenido por tres razones:&#xD;
- Para asegurar un arquetipo de base que pueda ser utilizado en todos los casos arriba descritos pero que permitan flexibilidad alli donde esta es requerida, como por ejemplo el SLOT `Detalles de la preparación´ en el cual un mayor detalle estructurado puede ser agregado. Se ha sugerido un arquetipo candidato para Medicaciones. Es posible que otros arquetipos CLUSTER sean necesarios en el futuro para otros propósitos tal como las órdenes de nutrición parenteral compleja;&#xD;
- Para permitir la re-utilización del arquetipo en situaciones en las cuales el contenido ha sido identificado como utilizado también en otros contextos clínicos, en particular en forma apareada como el arquetipo ACTION.medication, para el registro de la dispensación, administración, etc. concretas; y&#xD;
- Para remover del arquetipo base los contenidos menos comúnmente utilizados.&#xD;
&#xD;
Varias órdenes pueden ser representadas como actividades separadas dentro de una sola instancia de este arquetipo, para el uso de órdenes fuertemente vinculadas (como la terapia del Helicobacter Pylori) cuando estas nos son prescriptas como paquete único.&#xD;
&#xD;
Debe tenerse en cuenta que estos usos subsumen lso casos de uso tanto de la Orden de Medicamento FHIR como de la Declaración de Medicamento, es decir que este arquetipo coincide con ambos recursos FHIR, utilizados en el contexto apropiado.</use>
      <misuse>No debe ser utilizado para el registro de las actividades relacionadas con el cumplimiento de la orden del medicamento, vacuna, producto nutricional o ítem terapéutico, tal como los detalles de su administración o dispensa. Se debe utilizar el ACTION.medication para este propósito.&#xD;
&#xD;
No debe ser utilizado para el registro de órdenes de sangre o sus preparados, lo cual involucra un proceso clínico fundamentalmente diferente que muy probablemente requiera otro tipo de información. Se debe utilizar el ACTION.transfusion para este propósito.&#xD;
&#xD;
No debe ser utilizado para el registro de órdenes de inserción de implantes o dispositivos médicos tales como marcapasos o defibriladores. Se debe utilizar el ACTION.procedure para este propósito.</misuse>
      <copyright>© openEHR Foundation, HiGHmed</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Registrar todos os aspectos de uma prescrição de medicamento, vacina, produtos nutricionais ou outros itens terapêuticos para um indivíduo identificado.</purpose>
      <keywords>medicamento</keywords>
      <keywords>prescrição</keywords>
      <keywords>prescrever</keywords>
      <keywords>terapia</keywords>
      <keywords>substância</keywords>
      <keywords>droga</keywords>
      <keywords>terapêutico</keywords>
      <keywords>Otc</keywords>
      <keywords>produto terapêutico</keywords>
      <keywords>Farmacêutico</keywords>
      <keywords>produtos</keywords>
      <keywords>Posologia</keywords>
      <keywords>tratamento</keywords>
      <keywords>Solução</keywords>
      <keywords>nutrição</keywords>
      <keywords>Prescrição Eletrônica</keywords>
      <use>Utilizado para registrar todos os aspectos da prescrição de medicamentos, vacinas, produtos nutricionais ou outros itens terapêuticos, para um indivíduo identificado.&#xD;
&#xD;
Destina-se a ser usado para qualquer tipo de medicamento e prescrição relacionada, quer seja prescrito por um profissional de saúde ou disponível para compra "no balcão"da farmácia. O escopo deste arquétipo de medicamentos também inclui prescrições de vacinas, fluidos parenterais ou outros produtos terapêuticos, como bandagens, produtos nutricionais ou outros ítens que possuem um padrão comum para o seu registro e são aplicados ou administrados com vistas a um efeito terapêutico. &#xD;
&#xD;
Este arquétipo é projetado para ser usado em vários contextos clínicos, incluindo, entre outros:&#xD;
- um registro em uma consulta clínica (COMPOSITION.encounter);&#xD;
- uma receita escrita por um médico, dentista, ou outro profissional de saúde autorizado para prescrever uma medicamento ou produto nutricional a ser dispensado e administrado (COMPOSITION.prescription);&#xD;
- um ítem em uma lista atual de medicamento, receita ou carta de medicamentos (dentro de COMPOSITION.medication_list); e&#xD;
- um ítem em um documento de resumo, como a transferência de cuidados (COMPOSITION.transfer_summary) ou um documento de contra-referência (COMPOSITION.request).&#xD;
&#xD;
Em muitos casos, uma prescrição de medicamento será simples - tipicamente para um único item de medicamento com instruções simples para a sua dispensação e administração. No entanto, este arquétipo foi também projetado para permitir prescrições mais complexas. Por exemplo:&#xD;
&#xD;
-	uma redução de dose de prednisolona durante um período de semanas;&#xD;
-	fracionamento de insulina, com dosagem dependente dos resultados do teste;&#xD;
-	medicamentos múltiplos prescritos simultaneamente como parte de um regime de fármaco único, como uma terapia tripla para úlcera péptica; e&#xD;
-	administração intravenosa de medicamentos ou suplementos nutricionais, incluindo nutrição parenteral.&#xD;
&#xD;
O arquétipo foi, portanto, projetado para atender prescrições de maior complexidade, como, por exemplo: &#xD;
-	instruções narrativas simples tais como "furosemida 40mg dois comprimidos pela manhã e um no almoço" para assegurar a compatibilidade com os sistemas existentes; &#xD;
-	a quantidade do medicamento geralmente é representada por um número e uma unidade de dose correspondente, no entanto, pode haver uma descrição em texto livre para garantir a compatibilidade com os sistemas existentes e a cobertura de todos os cenários clínicos; através de&#xD;
-	detalhes estruturados para a dose, via e duração para representar uma especificação totalmente computável.&#xD;
&#xD;
Este arquétipo foi também projetado para que uma única estrutura de prescrição de medicamento possa representar:&#xD;
&#xD;
-	Prescrições sequencias complexas de medicamento com a mesma concentração de preparação representados em uma única estrutura de prescrição; e&#xD;
-	múltiplas prescrições de medicamentos que podem ser encadeadas em circunstâncias em que diferentes medicamentos ou preparações precisem ser administrados sequencialmente.&#xD;
&#xD;
Este arquétipo é também adequado para prescrição de soluções parenterais, em cenários de atendimento onde é normal prescrever estes itens. Em outras cenários, uma prescrição separada de soluções parenterais poderá ser mais apropriada.&#xD;
&#xD;
SLOTs contendo arquétipos do tipo CLUSTER foram utilizados ​​para representar parte do conteúdo por três razões:&#xD;
-	Para garantir que um arquétipo básico possa ser utilizado em todos os casos de uso descritos acima, oferecendo flexibilidade onde for necessário, por exemplo, o SLOT de "Detalhes da preparação", permite que detalhes adicionais estruturados da preparação possam ser adicionados. Existe um arquétipo sugerido para medicamentos. É possível que outros arquétipos do tipo CLUSTER sejam necessários no futuro, para outros fins, como pedidos complexos de nutrição parenteral;&#xD;
-	apoiar a reutilização do arquétipo em situações em que o conteúdo foi identificado como sendo utilizado também em outros contextos clínicos, em particular o arquétipo ACTION.medication (para deste arquéitpo) para gravação de distribuição real, administração, etc. e&#xD;
-	remover o conteúdo de menor utilização do núcleo do arquétipo. &#xD;
&#xD;
Várias prescrições podem ser representadas como atividades separadas nesta instância de arquétipo, para, por exemplo, representar prescrições de diferentes medicamentos, conectadas entre si, como ocorre na terapia de H. pylori, quando se opta por não prescrever como um único pacote.&#xD;
&#xD;
Observar que esses casos de usos acima descritos incluem os casos de uso da Prescrição de Medicamento e Medicamentos do FHIR. Isto é, este arquétipo é uma correspondência para ambos os recursos do FHIR, desde que utilizado no contexto apropriado.</use>
      <misuse>Não deve ser utilizado para registrar as atividades relacionadas à realização da prescrição de medicação, vacina, produto nutricional ou item terapêutico, como detalhes sobre a administração ou a dispensação. Use o arquétipo ACTION.medication para este propósito.&#xD;
&#xD;
Não deve ser utilizado para registrar o pedido de produtos sanguíneos, o que envolve um processo clínico fundamentalmente diferente e é provável que exija informações adicionais diferentes. Use o arquétipo INSTRUCTION.transfusion para este propósito.&#xD;
&#xD;
Não deve ser utilizado para registrar a ordem de inserção de implantes ou dispositivos médicos, como marcapassos e desfibriladores. Utilize o procedimento INSTRUCTION.Para este fim.</misuse>
      <copyright>© openEHR Foundation, HiGHmed</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record all aspects of an order of a medication, vaccine, nutritional product or other therapeutic item for an identified individual.</purpose>
      <keywords>medication</keywords>
      <keywords>order</keywords>
      <keywords>prescribe</keywords>
      <keywords>therapy</keywords>
      <keywords>substance</keywords>
      <keywords>drug</keywords>
      <keywords>therapeutic</keywords>
      <keywords>otc</keywords>
      <keywords>therapeutic good</keywords>
      <keywords>pharmaceutical</keywords>
      <keywords>product</keywords>
      <keywords>posology</keywords>
      <keywords>treatment</keywords>
      <keywords>fluid</keywords>
      <keywords>nutrition</keywords>
      <keywords>CPOE</keywords>
      <keywords>medicine</keywords>
      <use>Use to record all aspects of an order of a medication, vaccine, nutritional product or other therapeutic item for an identified individual.&#xD;
&#xD;
It is intended to be used for any type of medication and related order, whether prescribed by a health professional or available for purchase 'over the counter'. The scope of this medication archetype also includes orders for vaccinations, parenteral fluids or other therapeutic goods, such as bandages, nutritional products or other items that are applied or administered to have a therapeutic effect and which have a common pattern for data recording.&#xD;
&#xD;
This archetype is designed to be used in a number of clinical contexts, including but not limited to:&#xD;
- a record in a clinical consultation (COMPOSITION.encounter);&#xD;
- a written prescription by a physician, dentist, nurse practitioner, or other designated health professional for a medication or nutritional product to be dispensed and administered (within a COMPOSITION.prescription);&#xD;
- an item in a current medication list, prescription or drug chart (within COMPOSITION.medication_list); and&#xD;
- an item in a summary document such as transfer of care (COMPOSITION.transfer_summary) or a referral (COMPOSITION.request).&#xD;
&#xD;
In many cases a medication order will be simple – typically for a single medication item with uncomplicated instructions for dispensing and administration. However this archetype is also designed to allow for more complex therapeutic orders. For example:&#xD;
&#xD;
- a reducing dose of prednisolone over a period of weeks;&#xD;
- titration of insulin, with dosing dependent on test results;&#xD;
- multiple medications prescribed simultaneously as part of a single drug regimen, such as a triple therapy for peptic ulcer; and&#xD;
- intravenous administration of medications or nutrition supplements, including parenteral nutrition.&#xD;
&#xD;
The archetype has therefore been designed to allow for a range of complexity, from:&#xD;
- simple narrative instructions for orders like 'furosemide 40mg two tablets in the morning and one at lunch' to ensure compatibility with existing systems; and&#xD;
- the amount of medication is usually represented in terms of a number and corresponding dose unit, however there can alternatively be a narrative statement to ensure compatibility with existing systems and coverage of all clinical scenarios; through to&#xD;
- structured detail for dose, route and timing to represent a fully computable specification.&#xD;
&#xD;
It has also been designed so that a single medication order structure can represent:&#xD;
- complex sequential medication orders using the same preparation strength to be supported within a single order structure; and&#xD;
- multiple medication orders can be chained in circumstances where different medications or preparations need to be given sequentially.&#xD;
&#xD;
This archetype is also suitable for ordering parenteral fluids, in care settings where it is normal practice to make these 'prescribable' items. In other settings a separate 'parenteral fluid order' may be appropriate.&#xD;
&#xD;
SLOTs containing CLUSTER archetypes have been used to represent some of the content for three reasons:&#xD;
- To ensure a core archetype that can be used for all the above use cases, yet allow flexibility where it is required, for example the ‘Preparation details’ SLOT where additional structured detail can be added. A candidate archetype has been suggested for Medications. It is possible that other CLUSTER archetypes may be required in future for other purposes such as complex parenteral nutrition orders;&#xD;
- to support archetype re-use in situations where the content has been identified as being also used in other clinical contexts, in particular the paired ACTION.medication archetype for recording actual dispensing, administration etc; and&#xD;
- to remove less commonly used content from the core archetype framework.&#xD;
&#xD;
Multiple orders can be represented as separate activities within this single archetype instance to carry tightly bound orders of different medications, for example, H. pylori therapy when this is not prescribed as a single pack.&#xD;
&#xD;
It should be noted that these uses subsume both the FHIR Medication Order and Medication Statement use cases. i.e this archetype is a match for both FHIR resources, used in the appropriate context.</use>
      <misuse>Not to be used to record the activities related to carrying out the order for medication, vaccine, nutritional product or therapeutic item, such as details about actual administration or dispensing. Use the ACTION.medication for this purpose.&#xD;
&#xD;
Not to be used to record the ordering of blood products, which involves a fundamentally different clinical process and is likely to require different supporting information Use the INSTRUCTION.transfusion for this purpose.&#xD;
&#xD;
Not to be used to record the order for insertion of implants or medical devices such as pacemakers and defibrillators. Use the INSTRUCTION.procedure for this purpose.</misuse>
      <copyright>© openEHR Foundation, HiGHmed</copyright>
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Sarah Ballout</author>
    <author id="organisation">Medizinische Hochschule Hannover</author>
    <author id="email">ballout.sarah@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Emma Malm</author>
    <author id="organisation">Karolinska Universitetssjukhuset</author>
    <author id="email">emma.malm@cambio.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es-ar</code_string>
    </language>
    <author id="name">Alan March</author>
    <author id="organisation">Hospital Universitario Austral</author>
    <author id="email">amarch@cas.austral.edu.ar</author>
    <accreditation>MD</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">John Tore Valand, Silje Ljosland Bakke</author>
    <author id="organisation">Helse 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">Osmeire Chamelette Sanzovo</author>
    <author id="organisation">Hospital Sírio Libanês - SP</author>
    <author id="email">osmeire.acsanzovo@hsl.org.br</author>
    <accreditation>R.N.</accreditation>
  </translations>
  <uid>
    <value>4173ce20-8ed6-4acd-a7f0-5e65a937041c</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-INSTRUCTION.medication_order_gr1.v3</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>INSTRUCTION</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>activities</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>ACTIVITY</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>at0001</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>description</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ITEM_TREE</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0002</node_id>
            <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
              <rm_attribute_name>items</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>ELEMENT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0070</node_id>
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>value</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>0</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>DV_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>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0143</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.medication(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.medication(-[a-zA-Z0-9_]+)*\.v2/}</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\.medication(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.medication(-[a-zA-Z0-9_]+)*\.v2</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>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </occurrences>
                <node_id>at0091</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>at0092</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>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0093</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_circle(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v2/}</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\.anatomical_location(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_circle(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.anatomical_location_relative(-[a-zA-Z0-9_]+)*\.v2</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>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </occurrences>
                <node_id>at0094</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>at0095</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
                  <expression xsi:type="EXPR_BINARY_OPERATOR">
                    <type>Boolean</type>
                    <operator>2007</operator>
                    <precedence_overridden>false</precedence_overridden>
                    <left_operand xsi:type="EXPR_LEAF">
                      <type>String</type>
                      <item xsi:type="xsd:string">archetype_id/value</item>
                      <reference_type>attribute</reference_type>
                    </left_operand>
                    <right_operand xsi:type="EXPR_LEAF">
                      <type>C_STRING</type>
                      <item xsi:type="C_STRING">
                        <pattern>openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1</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>at0009</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>at0047</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_PARSABLE</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>formalism</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>STRING</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_STRING">
                          <list>text/html</list>
                          <list>text/plain</list>
                          <list>text/xml</list>
                        </item>
                      </children>
                    </attributes>
                  </children>
                </attributes>
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>ELEMENT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </occurrences>
                <node_id>at0173</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>at0174</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>at0177</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.therapeutic_direction(-[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\.therapeutic_direction(-[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>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </occurrences>
                <node_id>at0018</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>at0148</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>at0179</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>CLUSTER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0113</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>at0012</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>value</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>0</lower>
                        <upper>1</upper>
                      </existence>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_DATE_TIME</rm_type_name>
                        <occurrences>
                          <lower_included>true</lower_included>
                          <upper_included>true</upper_included>
                          <lower_unbounded>false</lower_unbounded>
                          <upper_unbounded>false</upper_unbounded>
                          <lower>1</lower>
                          <upper>1</upper>
                        </occurrences>
                        <node_id />
                      </children>
                    </attributes>
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>0</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0013</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>value</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>0</lower>
                        <upper>1</upper>
                      </existence>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_DATE_TIME</rm_type_name>
                        <occurrences>
                          <lower_included>true</lower_included>
                          <upper_included>true</upper_included>
                          <lower_unbounded>false</lower_unbounded>
                          <upper_unbounded>false</upper_unbounded>
                          <lower>1</lower>
                          <upper>1</upper>
                        </occurrences>
                        <node_id />
                      </children>
                    </attributes>
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>0</lower>
                    </occurrences>
                    <node_id>at0011</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>at0016</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>at0060</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>value</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>0</lower>
                        <upper>1</upper>
                      </existence>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_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>0</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>at0050</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>PWDTH</pattern>
                              <range>
                                <lower_included>true</lower_included>
                                <lower_unbounded>false</lower_unbounded>
                                <upper_unbounded>true</upper_unbounded>
                                <lower>PT0H</lower>
                              </range>
                            </item>
                          </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>
              </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>at0069</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.medication_authorisation(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.medication_authorisation(-[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\.medication_authorisation(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.medication_authorisation(-[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>at0167</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>true</is_ordered>
                <is_unique>false</is_unique>
                <interval>
                  <lower_included>true</lower_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>1</lower>
                </interval>
              </cardinality>
            </attributes>
          </children>
        </attributes>
      </children>
      <cardinality>
        <is_ordered>false</is_ordered>
        <is_unique>false</is_unique>
        <interval>
          <lower_included>true</lower_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>true</upper_unbounded>
          <lower>0</lower>
        </interval>
      </cardinality>
    </attributes>
    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
      <rm_attribute_name>protocol</rm_attribute_name>
      <existence>
        <lower_included>true</lower_included>
        <upper_included>true</upper_included>
        <lower_unbounded>false</lower_unbounded>
        <upper_unbounded>false</upper_unbounded>
        <lower>0</lower>
        <upper>1</upper>
      </existence>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ITEM_TREE</rm_type_name>
        <occurrences>
          <lower_included>true</lower_included>
          <upper_included>true</upper_included>
          <lower_unbounded>false</lower_unbounded>
          <upper_unbounded>false</upper_unbounded>
          <lower>1</lower>
          <upper>1</upper>
        </occurrences>
        <node_id>at0005</node_id>
        <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
          <rm_attribute_name>items</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </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_IDENTIFIER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="ARCHETYPE_SLOT">
            <rm_type_name>CLUSTER</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </occurrences>
            <node_id>at0008</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/.*/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>.*</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <cardinality>
            <is_ordered>false</is_ordered>
            <is_unique>false</is_unique>
            <interval>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </interval>
          </cardinality>
        </attributes>
      </children>
    </attributes>
  </definition>
  <ontology>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Medication order</items>
        <items id="description">An order for a medication, vaccine, nutritional product or other therapeutic item for an identified individual.</items>
      </items>
      <items code="at0001">
        <items id="text">Order</items>
        <items id="description">Details of the requested order.</items>
      </items>
      <items code="at0002">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Order identifier</items>
        <items id="description">Unique identifier for the medication order.</items>
        <items id="comment">This data element allows for multiple occurrences to be defined more explicitly at run-time, if required.</items>
      </items>
      <items code="at0005">
        <items id="text">Dose amount description</items>
        <items id="description">The amount and units of the medication, vaccine or other therapeutic good to be used or administered at one time.</items>
      </items>
      <items code="at0008">
        <items id="text">Extension</items>
        <items id="description">Additional information required to capture local content or to align with other reference models/formalisms.</items>
        <items id="comment">For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.</items>
      </items>
      <items code="at0009">
        <items id="text">Overall directions description</items>
        <items id="description">Complete narrative description about how the ordered item is to be used.</items>
        <items id="comment">This narrative should normally subsume data captured in 'Dose amount', 'Dose timing' and any additional instructions for use. Where the medication dose directions are fully carried by the structured, computable dose directions, this element should carry the narrative equivalent, generally auto-generated. If it is not possible to represent the intended 'Dose direction' fully in computable form, partial representation is not recommended, and the directions should be only recorded in narrative form using this data element.</items>
      </items>
      <items code="at0011">
        <items id="text">Order start criterion</items>
        <items id="description">A condition which, when met, requires the commencement of administration or use.</items>
        <items id="comment">For example: 'Start if symptoms recur'. This is intended for a general pre-condition which should trigger the whole medication course to be started, and not for 'as required' administrations of an ongoing order.</items>
      </items>
      <items code="at0012">
        <items id="text">Order start date/time</items>
        <items id="description">The date and optional time to commence use of the ordered item.</items>
      </items>
      <items code="at0013">
        <items id="text">Order stop date/time</items>
        <items id="description">The date and optional time when it is planned to cease use of the ordered item.</items>
      </items>
      <items code="at0016">
        <items id="text">Order stop criterion</items>
        <items id="description">A condition which, when met, requires the cessation of administration or use.</items>
        <items id="comment">For example: 'Stop after symptoms disappear''.</items>
      </items>
      <items code="at0018">
        <items id="text">Clinical indication</items>
        <items id="description">The clinical reason for use of the ordered item.</items>
        <items id="comment">For example: 'Angina'. Coding of the clinical indication with a terminology is preferred, where possible. This data element allows multiple occurrences. It is not intended to carry an indication for administrative authorisation purposes.</items>
      </items>
      <items code="at0047">
        <items id="text">Parsable directions</items>
        <items id="description">A parsable, computable text representation of the directions.</items>
        <items id="comment">Generally this is only used when passing information between legacy systems. For example: '10mg bd; 20mg n' as used by the NHS Dose syntax (in development).</items>
      </items>
      <items code="at0050">
        <items id="text">Duration of order completed</items>
        <items id="description">The time period during which the individual/patient has already been using the ordered item as a part of the intended whole order but prior to the issuance of this order.</items>
        <items id="comment">For example: To record that the patient had been taking antibiotics 3 days prior to hospital admission, in the context of a 7 day course.</items>
      </items>
      <items code="at0060">
        <items id="text">Administrations completed</items>
        <items id="description">The number of administrations of the ordered item that have been completed, as part of the intended whole order but prior to the issuance of this order.</items>
        <items id="comment">For example: To record that the patient has taken the two first antibiotic tablets of a three day course, prior to discharge from the hospital to a nursing home.</items>
      </items>
      <items code="at0069">
        <items id="text">Authorisation directions</items>
        <items id="description">Details of authorisation of the ordered item, including supporting local self-administration, issue and endorsement policies.</items>
        <items id="comment">For example: details of repeat/refill supply. This SLOT allows for local variation in the different jurisdictions regarding medication authorisation and re-authorisation to be managed.</items>
      </items>
      <items code="at0070">
        <items id="text">Medication item</items>
        <items id="description">Name of the medication, vaccine or other therapeutic/prescribable item being ordered.</items>
        <items id="comment">Depending on the prescribing context this field could be used for either generic- or product-based prescribing. This data field can be used to record tightly bound orders of different medications when they are prescribed as a single pack. It is strongly recommended that the 'Medication item' be coded with a terminology capable of triggering decision support, where possible. The extent of coding may vary from the simple name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available.</items>
      </items>
      <items code="at0091">
        <items id="text">Route</items>
        <items id="description">The route by which the ordered item is to be administered into the subject's body.</items>
        <items id="comment">For example: 'oral', 'intravenous', or 'topical'.&#xD;
Coding of the route with a terminology is preferred, where possible. Multiple potential routes may be specified.</items>
      </items>
      <items code="at0092">
        <items id="text">Body site</items>
        <items id="description">Name of the site of administration of the ordered item.</items>
        <items id="comment">For example: 'left upper arm', 'intravenous catheter right hand'.&#xD;
 Coding of the body site with a terminology is preferred, where possible.</items>
      </items>
      <items code="at0093">
        <items id="text">Structured body site</items>
        <items id="description">Structured description of the site of administration of the ordered item.</items>
      </items>
      <items code="at0094">
        <items id="text">Administration method</items>
        <items id="description">The technique or device by which the ordered item is to be administered.</items>
        <items id="comment">For example: ' via Z-track injection'; 'via nebuliser'. Coding of the method with a terminology is preferred, where possible.</items>
      </items>
      <items code="at0095">
        <items id="text">Administration device</items>
        <items id="description">Details of the medical device used to assist administration of the ordered item.</items>
      </items>
      <items code="at0113">
        <items id="text">Order details</items>
        <items id="description">Details about the whole medication order.</items>
      </items>
      <items code="at0143">
        <items id="text">Medication details</items>
        <items id="description">Structured details about the overall medication including strength, form and constituent substances.</items>
        <items id="comment">Use this SLOT where the detailed description of the ordered item needs to be explicitly stated. For example: the form, strength, any diluents or mixture of ingredients.</items>
      </items>
      <items code="at0148">
        <items id="text">Therapeutic intent</items>
        <items id="description">The overall therapeutic intent of the ordered item.</items>
        <items id="comment">For example: 'pain relief'; 'palliative care'; 'low-dose prophylaxis'; 'rehydration'; 'nutritional infusion'.</items>
      </items>
      <items code="at0167">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the medication order not captured in other fields.</items>
      </items>
      <items code="at0173">
        <items id="text">Specific directions description</items>
        <items id="description">A narrative description of a specific part of overall directions.</items>
        <items id="comment">In some settings, it is common to split overall narrative directions into more specific segments of narrative. For example in hospital settings, it can be common to split the overall directions into 'Dose amount' and 'Dose timing', both as narrative text. These terms can be applied at template or run-time.</items>
      </items>
      <items code="at0174">
        <items id="text">Dosage justification</items>
        <items id="description">A description of the justification used to calculate a dose amount or administration rate where this is dependent on some other factor.</items>
        <items id="comment">For example: 'Adjusted for amputation'.</items>
      </items>
      <items code="at0177">
        <items id="text">Structured dose and timing directions</items>
        <items id="description">Details of structured dose and timing directions.</items>
        <items id="comment">This SLOT has been designed to be used with the CLUSTER.therapeutic_direction archetype to enable recording of a complex set of dosage and timing directions. While it's possible to use other CLUSTER archetypes within this SLOT, it's strongly advised to do so only when predictable queryability is not a priority.</items>
      </items>
      <items code="at0179">
        <items id="text">Clinician guidance</items>
        <items id="description">Advice to future prescribers/dispensers about the ongoing, long term order.</items>
        <items id="comment">For example: 'don't allow brand substitution' or advice regarding using a specific brand to avoid fillers that cause reactions.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Legemiddelordinering</items>
        <items id="description">Ordinering av et legemiddel, en vaksine, parenteral væske, ernæringsprodukt eller medisinsk forbruksmateriell, for et spesifikt individ.</items>
      </items>
      <items code="at0001">
        <items id="text">Ordinering</items>
        <items id="description">Detaljer knyttet til ordineringen.</items>
      </items>
      <items code="at0002">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Ordineringsidentifikator</items>
        <items id="description">Unik identifikator for ordineringen.</items>
        <items id="comment">Dette dataelementet tillater flere forekomster, som ved behov kan defineres mer spesifikt i applikasjonen.</items>
      </items>
      <items code="at0005">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0008">
        <items id="text">Tilleggsinformasjon</items>
        <items id="description">Ytterligere informasjon som er nødvendig for å registrere lokalt innhold/kontekst, eller for å sammenstille med andre referansemodeller/formalismer.</items>
        <items id="comment">For eksempel lokale informasjonsbehov eller ytterligere metadata for å kunne tilpasse til tilsvarende konsepter i FHIR eller CIMI.</items>
      </items>
      <items code="at0009">
        <items id="text">Overordnet anvisningsbeskrivelse</items>
        <items id="description">En komplett fritekstbeskrivelse av hvordan den ordinerte varen skal brukes.</items>
        <items id="comment">Denne fritekstbeskrivelsen bør vanligvis omfatte data i "Dosemengde", "Timing" og eventuelle andre instruksjoner. I tilfeller hvor legemiddelets anvisning er fullt strukturert, bør dette feltet inneholde en fritekstekvivalent som vanligvis autogenereres. Er det ikke mulig å representere de ønskede anvisningene i en fullt strukturert form, anbefales ikke delvis strukturert form. I stedet bør anvisningen kun registreres som fritekst i dette dataelementet.</items>
      </items>
      <items code="at0011">
        <items id="text">Startkriterium</items>
        <items id="description">Et vilkår for at den ordinerte varen kan tas i bruk.</items>
        <items id="comment">For eksempel "Start dersom symptomer kommer tilbake". Dette er ment som et generelt kriterium som setter i gang hele ordineringen, og ikke for behovsadministrering i en pågående ordinering.</items>
      </items>
      <items code="at0012">
        <items id="text">Startdato/tid for ordineringen</items>
        <items id="description">Dato og valgfri tid for oppstart av den ordinerte varen.</items>
      </items>
      <items code="at0013">
        <items id="text">Dato/tid for seponering</items>
        <items id="description">Dato og valgfri tid når det er planlagt å seponere den ordinerte varen.</items>
      </items>
      <items code="at0016">
        <items id="text">Seponeringskriterium</items>
        <items id="description">Et vilkår for at den ordinerte varen skal seponeres.</items>
        <items id="comment">For eksempel "Seponer når symptomer forsvinner".</items>
      </items>
      <items code="at0018">
        <items id="text">Klinisk indikasjon</items>
        <items id="description">Den kliniske begrunnelsen for bruk av den ordinerte varen.</items>
        <items id="comment">For eksempel "Angina". Koding av klinisk indikasjon med en terminologi foretrekkes, der det er mulig. Dette dataelementet kan repeteres. Elementet er ikke ment for administrativ autorisering.</items>
      </items>
      <items code="at0047">
        <items id="text">Maskinlesbare anvisninger</items>
        <items id="description">En maskinlesbar tekstfremstilling av anvisningene.</items>
        <items id="comment">Brukes vanligvis ved deling av informasjon mellom eldre systemer.</items>
      </items>
      <items code="at0050">
        <items id="text">Del av ordinering allerede administrert</items>
        <items id="description">Tidsperioden individet/pasienten har brukt den ordinerte varen i forkant av denne instruksjonen.</items>
        <items id="comment">Eksempel: For å registrere at pasienten har tatt antibiotika i 3 dager av en 7-dagerskur før en sykehusinnleggelse.</items>
      </items>
      <items code="at0060">
        <items id="text">Antall administreringer utført</items>
        <items id="description">Antall administreringer av den ordinerte varen som er utført som del av den planlagte ordineringen, men i forkant av denne instruksjonen.</items>
        <items id="comment">For eksempel for å registrere at pasienten har tatt de to første antibiotikatablettene av en 3 dagers kur, i forkant av utskrivelse fra sykehus til sykehjem.</items>
      </items>
      <items code="at0069">
        <items id="text">Autoriseringsveiledning</items>
        <items id="description">Detaljer om autoriseringen for den ordinerte varen, støtter også selvadministrering, utlevering og retningslinjer for godkjenning.</items>
        <items id="comment">For eksempel detaljer om reiterering. Dette SLOTet tillater lokale variasjoner mellom forskjellige myndighetsområder når det gjelder legemiddelautorisering og re-autorisering.</items>
      </items>
      <items code="at0070">
        <items id="text">Legemiddel</items>
        <items id="description">Navnet på legemiddelet, vaksinen eller det medisinske forbruksmateriellet som ordineres.</items>
        <items id="comment">Avhengig av kontekst kan dette elementet brukes enten for generisk eller varebasert ordinering. Dataelementet kan brukes til å registrere tett sammenbundne ordineringer av forskjellige legemidler når de ordineres som en pakke. Det anbefales sterkt at "Legemiddel" kodes med en terminologi som understøtter beslutningsstøtte der dette er mulig, f.eks. FEST. Nivå av koding kan variere fra legemiddelnavn til strukturerte detaljer om den aktuelle legemiddelforpakningen som skal brukes. Fritekst bør bare brukes om ingen passende terminologi er tilgjengelig.</items>
      </items>
      <items code="at0091">
        <items id="text">Administreringsvei</items>
        <items id="description">Administreringsveien for den ordinerte varen.</items>
        <items id="comment">For eksempel "oral bruk", "intravenøst", "på huden" eller "enteralt".&#xD;
Det bør om mulig benyttes terminologi, f.eks. FEST, for å angi administreringsvei. Det kan spesifiseres flere mulige administreringsveier.</items>
      </items>
      <items code="at0092">
        <items id="text">Anatomisk lokalisering</items>
        <items id="description">Navn på kroppsstedet der den ordinerte varen skal administreres.</items>
        <items id="comment">For eksempel "venstre overarm", "intravenøst kateter høyre hånd". Det bør om mulig benyttes terminologi, f.eks. SNOMED CT eller EDQM standardtermer, for å angi kroppssted.</items>
      </items>
      <items code="at0093">
        <items id="text">Strukturert anatomisk lokalisering</items>
        <items id="description">Strukturert beskrivelse av administreringsstedet for den ordinerte varen.</items>
      </items>
      <items code="at0094">
        <items id="text">Administreringsmetode</items>
        <items id="description">Teknikken eller utstyret som brukes for å administrere den ordinerte varen.</items>
        <items id="comment">For eksempel "via Z-trackinjeksjon", "via forstøver". Koding av administreringsmetoden med en terminologi er anbefalt, der det er mulig.</items>
      </items>
      <items code="at0095">
        <items id="text">Administreringsutstyr</items>
        <items id="description">Detaljer om det medisinske utstyret som brukes til å administrere den ordinerte varen.</items>
      </items>
      <items code="at0113">
        <items id="text">Ordineringsdetaljer</items>
        <items id="description">Detaljer om hele legemiddelordineringen.</items>
      </items>
      <items code="at0143">
        <items id="text">Legemiddeldetaljer</items>
        <items id="description">Strukturerte detaljer om det overordnede legemiddelet, blant annet styrke, form og substansene det består av.</items>
        <items id="comment">Bruk dette SLOTet til å spesifisere en detaljert beskrivelse av den ordinerte varen. For eksempel form, styrke, fortynningsmiddel eller blandinger av ingredienser.</items>
      </items>
      <items code="at0148">
        <items id="text">Terapeutisk hensikt</items>
        <items id="description">Overordnet terapeutisk hensikt med den ordinerte varen.</items>
        <items id="comment">For eksempel "smertelindring", "palliasjon", "lavdose profylakse", "rehydrering" eller "ernæringsinfusjon".</items>
      </items>
      <items code="at0167">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om legemiddelordineringen som ikke er fanget i andre felt.</items>
      </items>
      <items code="at0173">
        <items id="text">Spesifikk anvisningsbeskrivelse</items>
        <items id="description">Fritekstbeskrivelse av en spesifikk del av den overordnede anvisningen.</items>
        <items id="comment">I noen sammenhenger er det vanlig å dele den samlede fritekstbeskrivelsen av anvisningen inn i mer spesifikke segmenter. For eksempel kan det i sykehus være vanlig å dele de samlede anvisningene opp i "Mengde" og "Administreringstidspunkt", selv om begge er i fritekst. Segmentnavnene kan legges til i et templat eller i applikasjonen.</items>
      </items>
      <items code="at0174">
        <items id="text">Begrunnelse for dose</items>
        <items id="description">Begrunnelsen for hvorfor en spesifikk dose er valgt, der dette er avhengig av en ytre faktor.</items>
        <items id="comment">For eksempel: "Justert pga amputasjon".</items>
      </items>
      <items code="at0177">
        <items id="text">Strukturerte anvisninger om dose og timing</items>
        <items id="description">Detaljerte og strukturerte anvisninger om dose og timing.</items>
        <items id="comment">Dette SLOTet er designet for å brukes med arketypen CLUSTER.therapeutic_direction for å tilrettelegge for å registrere et komplekst sett av anvisninger om dosering og timing. Det er mulig å bruke andre CLUSTER-arketyper i SLOTet, men det anbefales på det sterkeste å kun gjøre dette der det ikke er en prioritet å kunne gjøre forutsigbare spørringer på dataene.</items>
      </items>
      <items code="at0179">
        <items id="text">Klinikerveiledning</items>
        <items id="description">Råd til personer som i fremtiden ordinerer eller deler ut legemiddelet, om den langvarige ordineringen.</items>
        <items id="comment">For eksempel "ikke tillat generisk bytte" eller råd om å bruke et spesifikt merke for å unngå hjelpestoffer som forårsaker reaksjoner.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Prescrição de Medicamentos</items>
        <items id="description">Prescrição de medicamentos, vacina, produtos nutricionais ou outro item de tratamento para um indivíduo identificado.</items>
      </items>
      <items code="at0001">
        <items id="text">Prescrição</items>
        <items id="description">Detalhes da prescrição solicitada.</items>
      </items>
      <items code="at0002">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Outros identificadores</items>
        <items id="description">Identificador unívoco do ítem prescrito.</items>
        <items id="comment">Este elemento possui múltiplas ocorrências e deve ser explicitado em tempo de execução, se assim for exigido.</items>
      </items>
      <items code="at0005">
        <items id="text">Descrição da quantidade da dose</items>
        <items id="description">A quantidade e unidades de medida do medicamento, vacina ou outro ítem terapêutico viável para utilização e administração num período de tempo.</items>
      </items>
      <items code="at0008">
        <items id="text">Extensão</items>
        <items id="description">Informações adicionais necessárias para capturar o conteúdo local ou para se alinhar com outros modelos de referência / formalismos.</items>
        <items id="comment">Por exemplo: requisitos de informações locais ou metadados adicionais para alinhar com os equivalentes FHIR ou CIMI.</items>
      </items>
      <items code="at0009">
        <items id="text">Instruções Gerais da Prescrição</items>
        <items id="description">Narrativa completa da descrição de como o item deve ser utilizado.</items>
        <items id="comment">Esta narrativa deve normalmente incluir os dados capturados em "quantidade de dose", "Duração da dose" e quaisquer instruções adicionais de uso. Ainda que o detalhamento da dose esteja totalmente representado de forma estruturada e computável, esse elemento deve também representar o equivalente narrativo, geralmente gerado automaticamente. Se não for possível representar o detalhamento da dose do medicamento na forma computável, não se recomenda a representação parcial destes itens, Neste caso, deve ser registradas somente em forma narrativa usando este elemento de dados.</items>
      </items>
      <items code="at0011">
        <items id="text">Critério para o início da prescrição</items>
        <items id="description">Uma condição que, quando encontrada, exige o início da administração ou uso.</items>
        <items id="comment">Por exemplo: "Iniciar se o sintoma reaparecerem". Isso se destina a uma pré-condição geral que deve desencadear o uso da medicamento, e não para as administrações "se necessário" de uma prescrição em andamento.</items>
      </items>
      <items code="at0012">
        <items id="text">Data/Hora do início prescrição</items>
        <items id="description">A data e hora opcional para iniciar o uso do medicamento prescrito.</items>
      </items>
      <items code="at0013">
        <items id="text">Data/hora do final da prescrição</items>
        <items id="description">A data e hora opcional quando está planejado finalizar a utilização do ítem prescrito</items>
      </items>
      <items code="at0016">
        <items id="text">Critérios para interromper a prescrição</items>
        <items id="description">Uma condição que se existente, exige a interrupção da administração ou uso.</items>
        <items id="comment">Por exemplo: "Interromper após o desaparecimento dos sintomas".</items>
      </items>
      <items code="at0018">
        <items id="text">Indicação Clínica</items>
        <items id="description">A indicação clínica para o uso do item prescrito.</items>
        <items id="comment">Por exemplo: "Angina". Sempre que possível, a codificação da indicação clínica com uma terminologia deve existir. Este elemento de dados permite múltiplas ocorrências. Não se destina a fornecer uma indicação para fins de autorização administrativa.</items>
      </items>
      <items code="at0047">
        <items id="text">Orientação para parsear texto</items>
        <items id="description">Uma representação em texto parseável das orientações.</items>
        <items id="comment">Normalmente isto é utilizado somente quando passando informações entre sistemas legados.</items>
      </items>
      <items code="at0050">
        <items id="text">Duração do uso do ítem da prescrição</items>
        <items id="description">O período de tempo em que o indíviduo/paciente vem fazendo uso do item prescrito com parte da duração total do tratamento, antes da execução da prescrição atual.</items>
        <items id="comment">Por exemplo: para registrar que o paciente está fazendo uso de antibióticos por 3 dias, num total de 7 dias previstos para o tratamento, antes da internação hospitalar.</items>
      </items>
      <items code="at0060">
        <items id="text">Administrações finalizadas</items>
        <items id="description">O número de administrações realizadas do item prescrito, como parte da prescrição total, antes da execução da prescrição atual.</items>
        <items id="comment">Por exemplo: para registrar que o paciente tomou os dois primeiros comprimidos de antibiótico de três dias de tratamento, antes da alta hospitalar para a casa de repouso.</items>
      </items>
      <items code="at0069">
        <items id="text">Informações da autorização</items>
        <items id="description">Detalhes da autorização do ítem prescrito, incluindo o local de administração e políticas de reembolso.</items>
        <items id="comment">Por exemplo: detalhes sobre a renovação da prescrição. Este SLOT possibilita o gerenciamento das diferenças regionais a respeito das autorizações. No caso Brasileiro, não existe "refill"de prescrições.</items>
      </items>
      <items code="at0070">
        <items id="text">Item da prescrição de medicamentos</items>
        <items id="description">Nome do medicamento, vacina ou outro item terapêutico/prescritível a ser solicitado.</items>
        <items id="comment">Dependendo do contexto da prescrição, esse campo pode ser utilizado para uma prescrição de medicamentos genériicos ou comerciais. Este campo de dados pode ser utilizado para registrar prescrições relacionadas de vários medicamentos diferentes quando estão são prescritos como um único pacote. É altamente recomendável que o "item de medicação" seja codificado com uma terminologia capaz de desencadear o suporte à decisão, sempre que possível. A extensão da codificação pode variar do nome simples do item de medicação até os detalhes estruturados sobre o a embalagem da medicação a ser utilizada. A entrada de texto livre só deve ser utilizada se não houver uma terminologia apropriada disponível.</items>
      </items>
      <items code="at0091">
        <items id="text">Via de Administração</items>
        <items id="description">A via de administração pela qual o item prescrito deve ser administrada à pessoa.</items>
        <items id="comment">Por exemplo: 'oral', 'intravenosa', ou 'cutâena.'&#xD;
É desejável que avia de administração seja condificada com uma terminologia, sempre que possível. Várias vias de administração potenciais poderão ser especificadas.</items>
      </items>
      <items code="at0092">
        <items id="text">Local do corpo</items>
        <items id="description">Nome do local de administração do item prescrito.</items>
        <items id="comment">Por exemplo: "braço esquerdo", "catéter intravenoso da mão direita˜.&#xD;
Sempre que possível, é desejável que o local do corpo seja codificado com uma terminologia.</items>
      </items>
      <items code="at0093">
        <items id="text">Local do corpo estruturado</items>
        <items id="description">Descrição estruturada do local da administração do item prescrito.</items>
      </items>
      <items code="at0094">
        <items id="text">*Administration method(en)</items>
        <items id="description">*The technique or device by which the ordered item is to be administered.(en)</items>
        <items id="comment">*For example: ' via Z-track injection'; 'via nebuliser'. Coding of the method with a terminology is preferred, where possible.(en)</items>
      </items>
      <items code="at0095">
        <items id="text">*Administration device(en)</items>
        <items id="description">*Details of the medical device used to assist administration of the ordered item.(en)</items>
      </items>
      <items code="at0113">
        <items id="text">Prescrição detalhada</items>
        <items id="description">Detalhes sobre a prescrição como um todo.</items>
      </items>
      <items code="at0143">
        <items id="text">*Medication details (en)</items>
        <items id="description">*Structured details about the overall medication including strength, form and constituent substances. (en)</items>
        <items id="comment">Use este SLOT quando os detalhes do item prescrito precisam ser explicitamente declarado. Por exemplo: a forma, a concentração, algum diluente ou mistura de ingredientes.</items>
      </items>
      <items code="at0148">
        <items id="text">Intenção terapêutica</items>
        <items id="description">A intenção terapêutica sobre o item prescrito.</items>
        <items id="comment">Por exemplo: "Alívio da dor", "cuidado paliativo"; "baixa-dose profilática", "rehidratação", "infusão nutricional".</items>
      </items>
      <items code="at0167">
        <items id="text">Comentários</items>
        <items id="description">Comentários adicionais sobre o ítem prescrito em texto livre, não capturados em outros campos.</items>
      </items>
      <items code="at0173">
        <items id="text">Orientações específicas</items>
        <items id="description">Descrição em texto de uma parte das orientações globais.</items>
        <items id="comment">Em algumas situações é comum separar as orientações em segmentos de narrativas mais específicas. Por exemplo: é comum num hospital separar as orientações em 'quantidade da dose' e 'duração da dose', ambas como texto. Estes termos podem se aplicados no template ou durante a excecução do sistema.</items>
      </items>
      <items code="at0174">
        <items id="text">Justificativa da dosagem</items>
        <items id="description">A descrição da justificativa utilizada para calcular a dose total ou taxa da administração quando esta é dependente de algum outro fator.</items>
        <items id="comment">Por exemplo: "Ajustado por causa da amputação".</items>
      </items>
      <items code="at0177">
        <items id="text">Orientações estuturadas de dose e duração</items>
        <items id="description">Detalhes das orientações estuturadas de dose e duração.</items>
        <items id="comment">*This SLOT has been designed to be used with the CLUSTER.therapeutic_direction archetype to enable recording of a complex set of dosage and timing directions. While it's possible to use other CLUSTER archetypes within this SLOT, it's strongly advised to do so only when predictable queryability is not a priority. (en)</items>
      </items>
      <items code="at0179">
        <items id="text">*Clinician guidance (en)</items>
        <items id="description">*Advice to future prescribers/dispensers about the ongoing, long term order. (en)</items>
        <items id="comment">*For example: 'don't allow brand substitution' or advice regarding using a specific brand to avoid fillers that cause reactions. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="es-ar">
      <items code="at0000">
        <items id="text">Orden de medicamento</items>
        <items id="description">Una orden para un medicamento, vacuna, producto nutricional u otro ítem terapéutico para un individuo identificado.</items>
      </items>
      <items code="at0001">
        <items id="text">Orden</items>
        <items id="description">Detalles de la orden requerida.</items>
      </items>
      <items code="at0002">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Identificador de la orden</items>
        <items id="description">Identificador unívoco de la orden de medicamento.</items>
        <items id="comment">Este elemento permite que ocurrencias múltiples puedan ser definidas mas explícitamente en tiempo de ejecución si así se requiere.</items>
      </items>
      <items code="at0005">
        <items id="text">Descripción de la cantidad de dosis</items>
        <items id="description">La cantidad y unidad del medicamento, vacuna u otro recurso terapéutico que debe ser utilizado o administrado en algún momento.</items>
      </items>
      <items code="at0008">
        <items id="text">Extensión</items>
        <items id="description">Información adicional requerida para representar contenidos locales o para compatibilizar con otros modelos o formalismos de referencia.</items>
        <items id="comment">Por ejemplo: requerimientos locales de información o metadatos para compatibilizar con equivalentes FHIR o CIMI.</items>
      </items>
      <items code="at0009">
        <items id="text">Descripción de las directivas generales</items>
        <items id="description">Descripción narrativa completa del modo en que el ítem ordenado debe ser utilizado.</items>
        <items id="comment">Esta narrativa normalmente debería subsumir los datos contenidos en 'cantidad de dosis', 'temporalidad de la dosis', y cualquier otra instrucción adicional para el uso. Cuando las directivas de la dosis del medicamento se encuentran completamente incluidas en las dosis estructuradas y computables, este elemento debería contener su equivalente narrativo, generalmente autogenerado. Si no resulta posible representar la directiva de dosis en forma computable, no se recomienda una representación parcial y las directivas solo deberán ser registradas como narrativa utilizando este elemento.</items>
      </items>
      <items code="at0011">
        <items id="text">Criterio de comienzo de la orden</items>
        <items id="description">La condición frente a la cual se debe comenzar la administración o uso.</items>
        <items id="comment">Por ejemplo: 'Comenzar si los síntomas recurren'. Esto se utiliza como un pre-condición que debería gatillar el inicio del curso completo de la medicación y no como la administración 'según necesidad' de una orden activa.</items>
      </items>
      <items code="at0012">
        <items id="text">Fecha y hora de comienzo de la orden</items>
        <items id="description">La fecha y hora (esta última opcional) de comienzo del uso del ítem ordenado.</items>
      </items>
      <items code="at0013">
        <items id="text">Fecha y hora de finalización de la orden</items>
        <items id="description">La fecha y hora (esta última opcional) para la cual se planea discontinuar el uso del ítem ordenado.</items>
      </items>
      <items code="at0016">
        <items id="text">Criterio de finalización de la orden</items>
        <items id="description">La condición frente a la cual se debe discontinuar la administración o uso.</items>
        <items id="comment">Por ejemplo: 'Discontinuar ante la desaparición de los síntomas''.</items>
      </items>
      <items code="at0018">
        <items id="text">Indicación clínica</items>
        <items id="description">La razón clínica para el uso del ítem ordenado.</items>
        <items id="comment">Pro ejemplo 'Angina'. Este elemento puede ocurrir múltiples veces. No esta destinado a contener una indicación de autorización con fines administrativos.</items>
      </items>
      <items code="at0047">
        <items id="text">Directivas parseables</items>
        <items id="description">La de las directivas en forma de texto parseable y computable.</items>
        <items id="comment">Generalmente esto solo se utiliza cuando se transfiere información entre sistemas legados. Por ejemplo: '10mg bd; 20mg n' como utiliza la NHS Dose syntax (en desarrollo).</items>
      </items>
      <items code="at0050">
        <items id="text">Duración de la orden completada</items>
        <items id="description">El período de tiempo durante el cual el individuo/paciente ha estado recibiendo el item ordenado como parte de la orden completa panificaa pero previo a la emisión de esta orden.</items>
        <items id="comment">Por ejemplo: Para registrar que el paciente ya había estado tomando antibióticos tres días previos a la admisión, en el contexto de un curso de 7 días.</items>
      </items>
      <items code="at0060">
        <items id="text">Administraciones realizadas</items>
        <items id="description">La cantidad de administraciones del ítem ordenado que ya han sido completadas como parte de la orden completa pero previo a la emisión de esta orden.</items>
        <items id="comment">Por ejemplo: Para registrar que el paciente ya ha tomado dos tabletas del antibiótico de un curso de tres días, previo a ser dado de alta desde el hospital para su traslado a un hogar de ancianos.</items>
      </items>
      <items code="at0069">
        <items id="text">Directivas de autorización</items>
        <items id="description">Detalles sobre la autorización del ítem ordenado, incluyendo ayuda para autoadministración local, y politicas frente a problemas y ratificaciones.</items>
        <items id="comment">Por ejemplo: Detalles sobre el provisión de repeticiones de receta. Este SLOT permite variaciones locales para las diferentes jurisdicciones respecto de autorización y re-autorizaciones que deban ser gestionadas.</items>
      </items>
      <items code="at0070">
        <items id="text">Ítem medicamentoso</items>
        <items id="description">Nombre del medicamento, vacuna, u otro ítem terapéutico o prescribible que es ordenado</items>
        <items id="comment">Dependiendo del contexto de prescripción este campo puede ser utilizado para una prescripción basada tanto en genéricos como en productos. Este campo puede ser utilizado para registrar ordenes de diferentes medicamentos estrechamente vinculados que son prescriptos como paquete único. Se recomienda fuertemente que este atributo sea codificado mediante una terminología capaz de disparar procesos de apoyo a la decisión cuando esto sea posible. El alcance de la codificación puede variar desde el simple nombre del medicamento hasta los detalles estructurados del paquete a ser utilizado. El texto libre solo debe ser utilizado cuando no exista una terminología disponible.</items>
      </items>
      <items code="at0091">
        <items id="text">Ruta</items>
        <items id="description">La ruta o vía de administración a través de la cual el ítem ordenado debe ser administrado en el cuerpo del sujeto.</items>
        <items id="comment">Por ejemplo: `oral´, `intravenoso´, o `tópico´.&#xD;
La codificación de la ruta mediante una terminología debe preferirse cuando sea posible. Se pueden especificar múltiples rutas potenciales.</items>
      </items>
      <items code="at0092">
        <items id="text">Sitio corporal</items>
        <items id="description">Nombre del sitio de administración del ítem ordenado.</items>
        <items id="comment">Por ejemplo: 'brazo izquierdo', 'catéter endovenoso de la mano derecha'.&#xD;
La codificación del sitio corporal mediante una terminología debe preferirse cuando sea posible.</items>
      </items>
      <items code="at0093">
        <items id="text">Sitio corporal estructurado</items>
        <items id="description">Descripción estructurada del sitio de administración del ítem ordenado.</items>
      </items>
      <items code="at0094">
        <items id="text">Método de administración</items>
        <items id="description">La técnica o dispositivo mediante el cual el ítem ordenado será administrado.</items>
        <items id="comment">Por ejemplo: 'a través de inyección en Z', 'por nebulización'. La codificación del método mediante una terminología debe preferirse cuando sea posible.</items>
      </items>
      <items code="at0095">
        <items id="text">Detalles del dispositivo de administración</items>
        <items id="description">Detalles del dispositivo médico utilizado para asistir en la administración del ítem ordenado.</items>
      </items>
      <items code="at0113">
        <items id="text">Detalle de la orden</items>
        <items id="description">Detalles aplicados a la orden en su totalidad.</items>
      </items>
      <items code="at0143">
        <items id="text">*Medication details (en)</items>
        <items id="description">*Structured details about the overall medication including strength, form and constituent substances. (en)</items>
        <items id="comment">Utilizar este SLOT cuando la descripción detallada de los ítems ordenados debe ser explícitamente declarada.</items>
      </items>
      <items code="at0148">
        <items id="text">Propósito terapéutico</items>
        <items id="description">El propósito terapéutico general del ítem ordenado.</items>
        <items id="comment">Por ejemplo: 'alivio del dolor'; 'cuidado paliativo'; 'profilaxis a baja dosis'; 'rehidratación'; 'infusión nutricional';</items>
      </items>
      <items code="at0167">
        <items id="text">Comentario</items>
        <items id="description">Narrativa adicional relativa a datos del medicamento que pueden no haber sido representados en otros campos.</items>
      </items>
      <items code="at0173">
        <items id="text">Descripción de las directivas específicas</items>
        <items id="description">La descripción narrativa de una parte específica de las directivas generales.</items>
        <items id="comment">En determinadas situaciones es común dividir la descripción narrativa general en segmentos específicos, también narrativos. Por ejemplo, en el contexto hospitalario es común separar las directivas generales en 'Cantidad de dosis' y 'frecuencia de la dosis', ambas como texto narrativo. Estos términos pueden ser aplicados como una plantilla o en tiempo de ejecución.</items>
      </items>
      <items code="at0174">
        <items id="text">Justificación de la dosis</items>
        <items id="description">La descripción de la justificación utilizada para calcular la cantidad o frecuencia de administración de una dosis cuando este depende de otro factor.</items>
        <items id="comment">Por ejemplo: 'ajustada por amputación'.</items>
      </items>
      <items code="at0177">
        <items id="text">Directivas estructuradas de dosis y frecuencia</items>
        <items id="description">Detalles de las directivas estructuradas de dosis y frecuencia.</items>
        <items id="comment">*This SLOT has been designed to be used with the CLUSTER.therapeutic_direction archetype to enable recording of a complex set of dosage and timing directions. While it's possible to use other CLUSTER archetypes within this SLOT, it's strongly advised to do so only when predictable queryability is not a priority. (en)</items>
      </items>
      <items code="at0179">
        <items id="text">*Clinician guidance (en)</items>
        <items id="description">*Advice to future prescribers/dispensers about the ongoing, long term order. (en)</items>
        <items id="comment">*For example: 'don't allow brand substitution' or advice regarding using a specific brand to avoid fillers that cause reactions. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Verordnung von Arzneimittel</items>
        <items id="description">Verschreibung eines Medikaments, Impfstoffs, Ernährungsprodukts oder anderen therapeutischen Mittels für eine bestimmte Person.</items>
      </items>
      <items code="at0001">
        <items id="text">Verordnung</items>
        <items id="description">Angaben zur Verordnung.</items>
      </items>
      <items code="at0002">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">ID der Verordnung</items>
        <items id="description">Eindeutige Kennung der Medikamentenverordnung / des Rezeptes.</items>
        <items id="comment">Dieses Datenelement ermöglicht während der Laufzeit der Anwendung eine genauere Spezifikation von mehrfach auftretenden Instanzen, wenn notwendig.</items>
      </items>
      <items code="at0005">
        <items id="text">Beschreibung der Dosismenge</items>
        <items id="description">Die Menge und Einheiten der Medikamente, Impfstoffe oder anderen therapeutischen Mitteln, die gleichzeitig verwendet oder verabreicht werden sollen.</items>
      </items>
      <items code="at0008">
        <items id="text">Erweiterung</items>
        <items id="description">Zusätzliche Informationen zur Erfassung lokaler Inhalte oder Anpassung an andere Referenzmodelle/Formalismen.</items>
        <items id="comment">Zum Beispiel: Lokaler Informationsbedarf oder zusätzliche Metadaten zur Anpassung an FHIR-Ressourcen oder CIMI-Modelle.</items>
      </items>
      <items code="at0009">
        <items id="text">Allgemeine Beschreibung der Anweisungen</items>
        <items id="description">Gesamtbeschreibung, wie das verordneten Medikament zu verwenden ist.</items>
        <items id="comment">Wenn die Anweisungen zur Dosierung vollständig strukturiert dargestellt werden können, sollte dieses Element ein Freitextäquivalent enthalten, das normalerweise automatisch generiert wird. Wenn es nicht möglich ist, die gewünschten Dosisanweisungen vollständig in strukturierter Form darzustellen, wird eine Teildarstellung nicht empfohlen. Stattdessen sollte die Anweisung nur als Freitext in diesem Datenelement aufgezeichnet werden.</items>
      </items>
      <items code="at0011">
        <items id="text">Startkriterium für die Verordnung</items>
        <items id="description">Eine Bedingung für den Beginn der Verwendung des verordneten Arzneimittels.</items>
        <items id="comment">Zum Beispiel: "Start, wenn die Symptome wieder auftreten". Dies ist als Voraussetzung gedacht, die den Beginn des gesamten Medikationsverlaufs auslösen soll, und nicht für Verabreichungen "bei Bedarf" innerhalb einer laufenden Verordnung.</items>
      </items>
      <items code="at0012">
        <items id="text">Beginn der Verordnung</items>
        <items id="description">Datum und optionale Uhrzeit für den Beginn der Verwendung des verordneten Arzneimittels.</items>
      </items>
      <items code="at0013">
        <items id="text">Ende der Verordnung</items>
        <items id="description">Datum und optionale Uhrzeit, wann die Verwendung des verordneten Arzneimittels eingestelt werden soll.</items>
      </items>
      <items code="at0016">
        <items id="text">Stopkriterium für die Verordnung</items>
        <items id="description">Eine Bedingung für das Einstellen der Verwendung des verordneten Arzneimittels.</items>
        <items id="comment">Zum Beispiel: "Beenden nach Abklingen der Symptome".</items>
      </items>
      <items code="at0018">
        <items id="text">Klinische Indikation</items>
        <items id="description">Der klinische Grund für die Verwendung des verordneten Arzneimittels.</items>
        <items id="comment">Zum Beispiel: "Angina". Die Kodierung der klinischen Indikation mit einer Terminologie wird nach Möglichkeit bevorzugt. Dieses Datenelement kann mehrfach vorkommen. Es ist nicht beabsichtigt, eine Angabe für behördliche Genehmigungszwecke mitzuführen.</items>
      </items>
      <items code="at0047">
        <items id="text">Maschinenlesbare Anweisungen</items>
        <items id="description">Eine maschinenlesbare, berechenbare Textdarstellung der Anweisung.</items>
        <items id="comment">Wird normalerweise zum Austausch von Informationen zwischen Legacy-Systemen verwendet. Zum Beispiel: "10mg bd; 20 mg n", wie von der NHS-Dosissyntax verwendet (in Entwicklung).</items>
      </items>
      <items code="at0050">
        <items id="text">Dauer der durchgeführten Verordnung</items>
        <items id="description">Der Zeitraum, in dem die Person / der Patient das verordnete Arzneimittel noch vor der Ausstellung dieser Verordnung bereits angewendet hat.</items>
        <items id="comment">Zum Beispiel: Zur Darstellung, dass der Patient vor einem Krankenhausaufenthalt, im Kontext eines 7-tägigen Kurs, 3 Tage lang Antibiotika eingenommen hat.</items>
      </items>
      <items code="at0060">
        <items id="text">Anwendungen durchgeführt</items>
        <items id="description">Die Anzahl der Verabreichungen des verordneten Arzneimittels, die im Rahmen der geplanten Gesamtverordnung, bereits vor dieser Ausgabe, durchgeführt wurden.</items>
        <items id="comment">Zum Beispiel: Zur Darstellung, dass der Patient die beiden ersten Antibiotika-Tabletten eines dreitägigen Kurses eingenommen hat, bevor er aus dem Krankenhaus in ein Pflegeheim entlassen wurde.</items>
      </items>
      <items code="at0069">
        <items id="text">Anweisungen zur Genehmigung</items>
        <items id="description">Details der Autorisierung für das verordnete Arzneimittel, einschließlich Unterstützung der lokalen Richtlinien zur Selbstverwaltung, Ausgabe und Bestätigung.</items>
        <items id="comment">Zum Beispiel: Angaben über Wiederholung oder Nachbereitung. Dieser SLOT ermöglicht lokale Unterschiede zwischen verschiedenen Rechtsordnungen hinsichtlich der Genehmigung und Re-Autorisierung von Arzneimitteln zu verwalten.</items>
      </items>
      <items code="at0070">
        <items id="text">Arzneimittel</items>
        <items id="description">Name des verordneten Medikaments, Impfstoffs oder anderen therapeutischen / verschreibungsfähigen Mittels.</items>
        <items id="comment">Je nach Kontext kann dieses Feld entweder für die generische oder die produktbasierte Verschreibung verwendet werden. In diesem Datenelement können eng gebundene Verordnungen verschiedener Medikamente dargestellt werden, wenn diese als Einzelpackung verschrieben werden. Es wird dringend empfohlen, das „Arzneimittel“ mit einer Terminologie zu kodieren, die nach Möglichkeit eine Entscheidungsunterstützung triggern kann. Der Umfang der Kodierung kann vom einfachen Medikamentennamen bis zu strukturierten Details über die tatsächlich zu verwendende Medikamentenpackung variieren. &#xD;
Die Freitexteingabe sollte nur verwendet werden, wenn keine entsprechende Terminologie verfügbar ist.</items>
      </items>
      <items code="at0091">
        <items id="text">Verabreichungsweg</items>
        <items id="description">Die Angabe darüber, auf welche Art das verordnete Arzneimittel am Körper des Patienten angewendet wird.</items>
        <items id="comment">Zum Beispiel: "oral", "intravenös" oder "topisch". &#xD;
Die Kodierung des Verabreichungswegs mit einer Terminologie wird nach Möglichkeit bevorzugt. Es können mehrere mögliche Verabreichungswege angegeben werden.</items>
      </items>
      <items code="at0092">
        <items id="text">Körperstelle</items>
        <items id="description">Name der Körperstelle, an der das Arzneimittel verabreicht wird.</items>
        <items id="comment">Zum Beispiel: "linker Oberarm", "intravenöser Katheter rechte Hand".&#xD;
Die Kodierung der Körperstelle mit einer Terminologie ist nach Möglichkeit bevorzugt.</items>
      </items>
      <items code="at0093">
        <items id="text">Lokalisation</items>
        <items id="description">Strukturierte Beschreibung der Körperstelle, an der das Arzneimittel verabreicht wird.</items>
      </items>
      <items code="at0094">
        <items id="text">Methode der Verabreichung</items>
        <items id="description">Die Technik oder das Gerät mit dem das versordnete Arzneimittel verabreicht werden soll.</items>
        <items id="comment">Zum Beispiel: "via Z-track Injektion"; "via Vernebler". Die Kodierung der Methode mit einer Terminologie, wenn möglich, wird bevorzugt.</items>
      </items>
      <items code="at0095">
        <items id="text">Verabreichungsmittel</items>
        <items id="description">Details zu der Vorrichtung mit der das verordnete Arzneimittel verabreicht wird.</items>
      </items>
      <items code="at0113">
        <items id="text">Detaillierte Angaben zu der Verordnung</items>
        <items id="description">Detaillierte Angaben zu der gesamten Medikamentenverordnung.</items>
      </items>
      <items code="at0143">
        <items id="text">Angaben zur Medikation</items>
        <items id="description">Strukturierte Angaben über das gesamte Medikament, einschließlich Stärke, Form und Inhaltsstoffe.</items>
        <items id="comment">Verwenden Sie diesen SLOT, wenn detaillierte Beschreibung des verordneten Arzneimittels explizit angegeben werden muss. Zum Beispiel: Form, Stärke, Verdünnungsmittel oder Mischung von Inhaltsstoffen.</items>
      </items>
      <items code="at0148">
        <items id="text">Therapiezweck</items>
        <items id="description">Gesamttherapeutischer Zweck des verordneten Arzneimittels.</items>
        <items id="comment">Zum Beispiel: "Schmerzlinderung"; "Palliativversorgung"; "Niedrigdosis-Prophylaxe"; "Rehydratation"; "Ernährungsinfusion".</items>
      </items>
      <items code="at0167">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Kommentare über die Medikamentenverordnung, die nicht in anderen Feldern erfasst wurden.</items>
      </items>
      <items code="at0173">
        <items id="text">Beschreibung der spezifischen Anweisungen</items>
        <items id="description">Freitextbeschreibung eines bestimmten Teils der Gesamtanweisung.</items>
        <items id="comment">In einigen Kontexten ist es üblich, die gesamte Freitextbeschreibung der Anweisung in spezifischere Segmente aufzuteilen. In Krankenhäusern kann es beispielsweise üblich sein, die gesamten Anweisungen in "Dosismenge" und "Verabreichungszeiten" zu unterteilen, beide als Freitext. Diese Begriffe können im Template oder zur Laufzeit der Anwendung angewendet werden.</items>
      </items>
      <items code="at0174">
        <items id="text">Begründung der Dosis</items>
        <items id="description">Eine Beschreibung der Begründung für die Berechnung einer Dosismenge oder Verabreichungsrate, wenn dies von einem anderen Faktor abhängt.</items>
        <items id="comment">Zum Beispiel: "Angepasst wegen Amputation".</items>
      </items>
      <items code="at0177">
        <items id="text">Strukturierte Dosis- und Zeitangaben</items>
        <items id="description">Details zu strukturierten Dosis- und Zeitangaben</items>
        <items id="comment">Dieser SLOT wurde für die Verwendung mit dem Archetyp CLUSTER.therapeutic_direction konzipiert, um die Erfassung einer komplexen Reihe von Dosierungs- und Zeitangaben zu ermöglichen. Es ist zwar möglich, andere CLUSTER-Archetypen innerhalb dieses SLOTs zu verwenden, aber es wird dringend empfohlen, dies nur dann zu tun, wenn die vorhersehbare Abfragefähigkeit keine Priorität hat.</items>
      </items>
      <items code="at0179">
        <items id="text">Klinische Leitlinie</items>
        <items id="description">Empfehlung an die zukünftigen Verordner/Abgeber über die fortlaufende, langjährige Verordnung.</items>
        <items id="comment">Zum Beispiel: "keinen Markenersatz zulassen" oder Ratschläge zur Verwendung einer bestimmten Marke, um Füllstoffe zu vermeiden, die Reaktionen hervorrufen.</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Läkemedelsbeställning</items>
        <items id="description">En beställning av ett läkemedel, vaccin, näringspreparat eller annat terapeutiskt produkt för en identifierad individ.</items>
      </items>
      <items code="at0001">
        <items id="text">Order</items>
        <items id="description">Information om den begärda ordern.</items>
      </items>
      <items code="at0002">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Beställnings-ID</items>
        <items id="description">Unik identifikator för läkemedelsbeställningen.</items>
        <items id="comment">Detta dataelement möjliggör exakt identifiering av flera ordrar samtidigt.</items>
      </items>
      <items code="at0005">
        <items id="text">Beskrivning av dosmängd</items>
        <items id="description">Mängd med tillhörande enhet av läkemedlet, vaccinet eller annat terapeutiskt produkt som ska användas eller administreras vid samma tillfälle.</items>
      </items>
      <items code="at0008">
        <items id="text">Tilläggsinformation</items>
        <items id="description">Plats för att infoga tilläggsinformation som krävs för lokala anpassningar eller anpassning till andra referensmodeller eller formella krav.</items>
        <items id="comment">Exempelvis lokala informationskrav eller metadata för anpassning till FHIR- eller CIMI-motsvarigheter.</items>
      </items>
      <items code="at0009">
        <items id="text">Fullständig beskrivning av anvisningar</items>
        <items id="description">Komplett beskrivning om hur den beställda artikeln ska användas.</items>
        <items id="comment">Beskrivningen ska normalt sammanfoga data som registrerats i "Dosmängd", "Tidpunkt för dos" och eventuella ytterligare bruksanvisningar. Where the medication dose directions are fully carried by the structured, computable dose directions, this element should carry the narrative equivalent, generally auto-generated. If it is not possible to represent the intended 'Dose direction' fully in computable form, partial representation is not recommended, and the directions should be only recorded in narrative form using this data element.</items>
      </items>
      <items code="at0011">
        <items id="text">Startkriterium för order</items>
        <items id="description">Det villkor som måste vara uppfyllt innan administrering eller användning påbörjas.</items>
        <items id="comment">Till exempel: "Påbörja om symptomen återkommer". Detta är ett generellt förhandsvillkor som bör leda till att hela läkemedelsbehandlingen startar, och inte för "vid behov"-administreringar av en pågående order.</items>
      </items>
      <items code="at0012">
        <items id="text">Datum/tid för påbörjad order</items>
        <items id="description">Datum och tid (valfritt) då användning av den beställda artikeln planeras påbörja.</items>
      </items>
      <items code="at0013">
        <items id="text">Datum/tid för avslutad order</items>
        <items id="description">Datum och tid (valfritt) då användning av den beställda artikeln planeras upphöra.</items>
      </items>
      <items code="at0016">
        <items id="text">Stoppkriterium för order</items>
        <items id="description">Det villkor som måste vara uppfyllt innan administrering eller användning upphör.</items>
        <items id="comment">Till exempel: "Stoppa efter att symptomen försvinner".</items>
      </items>
      <items code="at0018">
        <items id="text">Klinisk indikation</items>
        <items id="description">Klinisk orsak till användning av den beställda artikeln.</items>
        <items id="comment">Till exempel: "Angina pectoris". Om möjligt, benämn den kliniska indikationen med en terminologi. Dataelementet tillåter flera förekomster. Är dock ej avsedd att innehålla indikation för administrativa tillståndsändamål.</items>
      </items>
      <items code="at0047">
        <items id="text">Tolkningsanvisningar</items>
        <items id="description">En tolkbar, computable textrepresentation av anvisningarna.</items>
        <items id="comment">Generellt används detta endast när information skickas mellan äldre system. Till exempel: "10 mg bd; 20 mg n" som används av NHS dos-syntax (under utveckling).</items>
      </items>
      <items code="at0050">
        <items id="text">Varaktighet för slutförd order</items>
        <items id="description">Den tidsperiod under vilken individen/patienten redan har använt den beställda artikeln. Detta är en del av den avsedda totala beställningen, men före utfärdandet av denna beställning.</items>
        <items id="comment">Exempelvis för att registrera att patienten hade tagit antibiotika tre dagar före inskrivning på sjukhus i samband med en 7-dagarskur.</items>
      </items>
      <items code="at0060">
        <items id="text">Slutförda administrationer</items>
        <items id="description">Antalet slutförda administrationer av den beställda artikeln. Detta är en del av den avsedda totala beställningen, men före utfärdandet av denna beställning.</items>
        <items id="comment">Exempelvis för att registrera att patienten har tagit de två första antibiotikatabletterna under en 3-dagarskur före utskrivning från sjukhuset till ett vårdhem.</items>
      </items>
      <items code="at0069">
        <items id="text">Anvisningar om auktorisering</items>
        <items id="description">Detaljer om auktorisering av den beställda artikeln, inklusive stöd för lokal självadministrering, utförda och godkännandepolicyer.</items>
        <items id="comment">Exempelvis information om upprepning/påfyllning. Denna SLOT gör det möjligt att hantera lokal variation i de olika jurisdiktionerna med avseende på medicineringstillstånd och återbehörighet.</items>
      </items>
      <items code="at0070">
        <items id="text">Läkemedelsartikel</items>
        <items id="description">Benämning på det läkemedel, vaccin eller annan terapeutisk/ordinerbar artikel som beställs.</items>
        <items id="comment">Beroende på ordinationstyp, kan detta fält användas för antingen generisk eller produktbaserad ordination. Detta datafält kan användas för att registrera relaterade beställningar av olika läkemedel när de ordineras som enpack. Om möjligt, benämn läkemedelsartikeln med en terminologi. Omfattningen av benämningen kan variera från namn på läkemedelsartikeln till detaljer om själva läkemedelspaketet. Fri textinmatning bör endast användas om det inte finns någon lämplig terminologi tillgänglig.</items>
      </items>
      <items code="at0091">
        <items id="text">Administreringsväg</items>
        <items id="description">Sättet genom vilken den beställda artikeln ska administreras i patientens kropp.</items>
        <items id="comment">Till exempel: "oralt", "intravenöst" eller "lokalt". Om möjligt, benämn administreringsvägen med en terminologi. Flera potentiella administreringsvägar kan specificeras.</items>
      </items>
      <items code="at0092">
        <items id="text">Kroppsområde</items>
        <items id="description">Beskrivning av administrationsstället för den beställda artikeln.</items>
        <items id="comment">Till exempel: "vänster överarm", "intravenös kateter, höger hand". Om möjligt, benämn den anatomiska lokaliseringen med en terminologi.</items>
      </items>
      <items code="at0093">
        <items id="text">Strukturerat kroppsområde</items>
        <items id="description">Strukturerad beskrivning av administrationsstället för den beställda produkten.</items>
      </items>
      <items code="at0094">
        <items id="text">Administreringsmetod</items>
        <items id="description">Den teknik eller utrustning med vilken den beställda artikeln ska administreras.</items>
        <items id="comment">Till exempel: "via Z-teknik"; "via nebulisator". Om möjligt, benämn metoden med en terminologi.</items>
      </items>
      <items code="at0095">
        <items id="text">Administreringsutrustning</items>
        <items id="description">Information om den medicinska utrustning som används vid administrering av läkemedlet.</items>
      </items>
      <items code="at0113">
        <items id="text">Orderdetaljer</items>
        <items id="description">Detaljer om läkemedelsbeställningen.</items>
      </items>
      <items code="at0143">
        <items id="text">*Medication details (en)</items>
        <items id="description">*Structured details about the overall medication including strength, form and constituent substances. (en)</items>
        <items id="comment">Använd denna SLOT om beskrivningen av den beställda artikeln måste anges explicit. Till exempel: formen, styrkan, eventuella utspädningsmedel eller blandning av ingredienser.</items>
      </items>
      <items code="at0148">
        <items id="text">Behandlingsavsikt</items>
        <items id="description">Den övergripande behandlingsavsikten med den beställda artikeln.</items>
        <items id="comment">Till exempel: "smärtlindring"; "palliativ vård"; "lågdosprofylakse"; "rehydrering"; "näringsinfusion".</items>
      </items>
      <items code="at0167">
        <items id="text">Kommentar</items>
        <items id="description">Kommentarer avseende läkemedelsbeställningen som inte beskrivs i övriga fält.</items>
      </items>
      <items code="at0173">
        <items id="text">Specifika anvisningar</items>
        <items id="description">Beskrivning av en specifik del av de övergripande anvisningarna.</items>
        <items id="comment">I vissa fall är det vanligt att fördela övergripande anvisningar i mer specifika segment. I exempelvis sjukhussammanhang kan det vara vanligt att dela upp anvisningarna i "Dosmängd" och "Tidpunkt för dos", båda som berättande text. These terms can be applied at template or run-time.</items>
      </items>
      <items code="at0174">
        <items id="text">Motivering till dos</items>
        <items id="description">Motivering till beräkning av dosmängd eller administreringshastighet där detta är beroende av utomstående faktor.</items>
        <items id="comment">Till exempel: "Justerad för amputation".</items>
      </items>
      <items code="at0177">
        <items id="text">Strukturerad dos och tidsanvisningar</items>
        <items id="description">Detaljer om strukturerad dos och tidsanvisningar.</items>
        <items id="comment">*This SLOT has been designed to be used with the CLUSTER.therapeutic_direction archetype to enable recording of a complex set of dosage and timing directions. While it's possible to use other CLUSTER archetypes within this SLOT, it's strongly advised to do so only when predictable queryability is not a priority. (en)</items>
      </items>
      <items code="at0179">
        <items id="text">*Clinician guidance (en)</items>
        <items id="description">*Advice to future prescribers/dispensers about the ongoing, long term order. (en)</items>
        <items id="comment">*For example: 'don't allow brand substitution' or advice regarding using a specific brand to avoid fillers that cause reactions. (en)</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
