<?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-12-21</original_author>
    <original_author id="name">Heather Leslie</original_author>
    <original_author id="organisation">Atomica Informatics, Australia</original_author>
    <original_author id="email">heather.leslie@atomicainformatics.com</original_author>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Maria Berggren, Region Uppsala, Sweden</other_contributors>
    <other_contributors>SB Bhattacharyya, Bhattacharyyas Clinical Records Research &amp; Informatics LLP, India</other_contributors>
    <other_contributors>Hanne Marte Bårholm, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Gunn Elin Blakkisrud, DIPS ASA, Norway</other_contributors>
    <other_contributors>Kåre Flø, DIPS ASA, Norway</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Gunnar Jårvik, Helse Vest IKT AS, Norway</other_contributors>
    <other_contributors>Mika Kiviaho, Tietoevry, Finland</other_contributors>
    <other_contributors>Kanika Kuwelker, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Liv Laugen, ​Oslo University Hospital, Norway, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Mikael Nyström, Cambio Healthcare Systems AB, Sweden</other_contributors>
    <other_contributors>Bjørn Næss, DIPS ASA, Norway</other_contributors>
    <other_contributors>Marte Rime Bø, Direktoratet for e-helse, Norway</other_contributors>
    <other_contributors>Terje Sagmyr, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Andre Smitt-Ingebretsen, Sørlandet sykehus HF, Norway</other_contributors>
    <other_contributors>Norwegian Review Summary, Norwegian Public Hospitals, Norway</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Ina Wille, Helse-Vest RHF, Norway</other_contributors>
    <lifecycle_state>published</lifecycle_state>
    <other_details id="licence">This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.</other_details>
    <other_details id="custodian_organisation">openEHR Foundation</other_details>
    <other_details id="references">Derived from: Service, Draft archetype [Internet]. Australian Digital Health Agency (NEHTA), ADHA Clinical Knowledge Manager. Authored: 2015 Dec 21. Available at: http://dcm.nehta.org.au/ckm#showArchetype_1013.1.1395_2 (discontinued)</other_details>
    <other_details id="current_contact">Heather Leslie, Atomica Informatics, Australia&lt;heather.leslie@atomicainformatics.com&gt;</other_details>
    <other_details id="original_namespace">org.openehr</other_details>
    <other_details id="original_publisher">openEHR Foundation</other_details>
    <other_details id="custodian_namespace">org.openehr</other_details>
    <other_details id="MD5-CAM-1.0.1">925AA0073C71763B0E55BDF7C35E4E86</other_details>
    <other_details id="build_uid">fbb3c0cd-10be-443b-a056-2a09b2372f51</other_details>
    <other_details id="revision">1.0.4</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Um Details über eine einfache, gesundheitsbezogene Dienstleistung oder Aktivität, die von einem Kliniker, einer Organisation oder einer Behörde erbracht wird, darzustellen.</purpose>
      <keywords>Überweisung</keywords>
      <keywords>Besuch</keywords>
      <keywords>Kontakt</keywords>
      <keywords>Leistung</keywords>
      <use>Zur Darstellung einer gesundheitsbezogener Dienstleistung oder Aktivität, die von einem Kliniker, einer Organisation oder einer Behörde bereitgestellt wird. Dies beinhaltet das Verfolgen des Fortschritts von der Planung über die Terminierung und Lieferung bis zur Fertigstellung sowie Abweichungen vom beabsichtigten Behandlungspfad wie Verschiebung oder Stornierung. Dies wird durch die Aufzeichnung relevanter Datenelemente zu bestimmten Aktivitäten erreicht, von denen jede als "Pathway"-Prozessschritte in diesem Archetyp beschrieben wird.&#xD;
&#xD;
Der Umfang dieses Archetyps umfasst bewusst Aktivitäten für eine breite Palette klinischer Dienstleistungen, um als nicht spezifisches Archetyp für alle Anwendungsfälle zu dienen. Beispiele hierfür sind unter anderem:&#xD;
- der selbstorganisierte Besuch eines Patienten zu einem vorsorglichen Check-Up bei einem Zahnarzt&#xD;
- eine Reihe von Besuchen zu einem Physiotherapeuten zur Behandlung einer muskuloskelettalen Belastung&#xD;
- die Überweisung einen anfordernden Gesundheitsdienstleister, wie zum Beispiel eines Hausarztes, an einen aufnehmenden Gesundheitsdienstleister, wie zum Beispiel einem Facharzt damit der Patient eine bestimmte Dienstleistung, Beratung oder Pflege erhält.&#xD;
&#xD;
Zusätzliche strukturierte und ausführliche Informationen über diese Dienstleistung können, unter Verwendung eines spezifischen Archetyps der in den SLOT "Dienstleistungsdetails" integriert wird, dokumentiert werden.&#xD;
&#xD;
Dieser Archetyp kann auf zwei Arten verwendet werden:&#xD;
- als vollständige Darstellung der erbrachten Dienstleistung, oder&#xD;
- als Rahmen um vorrangig den Status der angeforderten Leistung und separaten OBSERVATION-Archetypen um die eigentlichen Testergebnisse für die erbrachte Dienstleistung darzustellen. Zum Beispiel mit dem Archetyp OBSERVATION.hearing_screening_result.&#xD;
&#xD;
Die Zeitplanung im Zusammenhang mit einer Dienstleistung kann auf eine von zwei Arten verwaltet werden:&#xD;
- durch die Verwendung des Referenzmodells - die Zeit für die Ausführung eines Schritts im Prozess wird das Zeitattribut des ACTION-Archetyps für jeden Schritt verwendet.&#xD;
- durch die Verwendung von Archetyp-Datenelemente - das Datenfeld "Geplantes Datum/geplante Uhrzeit" ist dafür gedacht einen Zeitpunkt aufzuzeichnen, zu der die Dienstleistung durchgeführt werden sollte. Hinweis: Das zugehörige ACTION-Zeitattribut für den geplanten Prozessschritt wird die Zeit aufzeichnen, zu der die klinische Aktivität in ein System eingeplant wurde, nicht das beabsichtigte Datum/die beabsichtigte Uhrzeit, an dem die Aktivität durchgeführt werden soll.&#xD;
&#xD;
In der Praxis werden einige Dienstleistungen (zum Beispiel in der ambulanten Versorgung) einmalig erbracht und nicht im Voraus bestellt. Die Details zu dieser Dienstleistung werden gegen den Schritt im Pfad "Dienstleistung abgeschlossen" hinzugefügt. In einigen Fällen wird eine wiederkehrende Dienstleistung bestellt, und in diesem Fall werden bei jeder Gelegenheit Daten unter dem Schritt "Dienstleistung erbracht" erfasst, wobei die Anweisung im aktiven Zustand bleibt. Wenn die letzte Erbringung der Dienstleistung erfasst wird, wird die Aktion "Dienstleistung abgeschlossen" aufgezeichnet, um anzuzeigen, dass diese Anforderung nun im abgeschlossenen Zustand ist.&#xD;
&#xD;
In anderen Situationen, wie der sekundären Versorgung, gibt es möglicherweise eine formelle Anforderung einer Dienstleistung die dem Archetyp INSTRUCTION.request entspricht. Dieser ACTION-Archetyp kann dann verwendet werden um den Arbeitsablauf und die Durchführung der Anforderung zu beschreiben.&#xD;
&#xD;
Die Darstellung von Informationen mit Hilfe dieses ACTION-Archetyps deutet darauf hin, dass eine Art von Aktivität tatsächlich stattgefunden hat. In der Regel handelt es sich dabei um eine tatsächliche Erbringung der Dienstleistung, kann jedoch auch einen fehlgeschlagenen Versuch oder eine andere Aktivität wie die Verschiebung der Dienstleistung umfassen. Wenn es eine formelle Anforderung für die Dienstleistung gibt, wird der Status dieser Bestellung durch den Pathway-Schritt repräsentiert, gegen den die Daten aufgezeichnet werden. Zum Beispiel kann der Fortschrittszustand einer Überweisungsanfrage mithilfe dieses Archetyps durch separate Einträge in den Fortschrittsnotizen der EHR bei jedem "Pathway"-Schritt erfasst werden:&#xD;
- Aufzeichnung eines geplanten Startdatums/geplanter Uhrzeit für die Überweisung (Dienstleistung angesetzt), oder&#xD;
- Aufzeichnung über eine vollständig erbrachte Überweisung, möglicherweise mit zusätzlichen Informationen zur erbrachten Dienstleistung (Dienstleistung abgeschlossen).&#xD;
&#xD;
Wenn die Aktivitäten den üblichen Geplanten &gt; Angesetzten &gt; Aktiven &gt; Abgeschlossenen Zuständen folgen, ist es in der Regel nicht notwendig, einen "Grund" aufzuzeichnen - vielmehr wird er in der Regel verwendet, um den Grund für Abweichungen vom typischen Versorgungspfad zu protokollieren.&#xD;
&#xD;
Bitte beachten Sie, dass im openEHR-Referenzmodell ein 'Time'-Attribut vorhanden ist, das dazu dient, Datum und Uhrzeit zu erfassen, zu welchem Zeitpunkt jeder Schritt des Pfades der Aktion durchgeführt wurde. Dies ist das Attribut, das verwendet werden sollte, um den Beginn der Prozedur (unter Verwendung des Schritts "Dienstleistung erbracht") oder die Zeit zu protokollieren, zu der der Leistung abgebrochen wurde (unter Verwendung des Schritts "Dienstleistung eingestellt").</use>
      <misuse>Nicht zur Darstellung von Informationen über durchgeführte Aktivitäten die spezielle Archetypen benötigen, weil sie eine sehr spezifische Datenerfassung oder Anforderungen an Schritte des Pfades haben. Zum Beispiel: ACTION.procedure oder ACTION.health_education.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>Att registrera uppgifter om en enkel hälsorelaterad tjänst eller aktivitet som utförs av vårdpersonal, organisation eller verksamhet.</purpose>
      <keywords>remiss</keywords>
      <keywords>vårdbegäran</keywords>
      <keywords>besök</keywords>
      <keywords>vårdbesök</keywords>
      <keywords>vårdkontakt</keywords>
      <keywords>kontakt</keywords>
      <keywords>patientkontakt</keywords>
      <use>Används för att registrera uppgifter om en enkel hälsorelaterad tjänst eller aktivitet som utförs av vårdpersonal, organisation eller verksamhet. Detta inkluderar uppföljning av förloppet från planering, via schemaläggning och utförande, till avslut, samt avvikelser från den avsedda vårdprocessen såsom uppskjutande eller avbokning. Detta uppnås genom registrering av relevanta datafält för specifika aktiviteter, vilka beskrivs i "Pathway" som vårdflödessteg.&#xD;
&#xD;
Omfattningen av denna arketyp är medvetet bred och inkluderar aktiviteter för ett stort spektrum av kliniska tjänster, i syfte att fungera som en generell arketyp för alla icke-komplexa användningsfall. Exempel på användning inkluderar:&#xD;
- egen-remiss från patient för ett kontrollbesök inom tandvård för förebyggande vård&#xD;
- flera besök hos fysioterapeut för behandling av en muskuloskeletal överbelastning&#xD;
- remiss från en remitterande vårdgivare, till exempel primärvård, till en mottagande vårdgivare, till exempel specialistvård, för att patienten ska erhålla en specifik tjänst, rådgivning eller vård. &#xD;
&#xD;
Ytterligare strukturerad och detaljerad information om tjänsten kan vid behov registreras med hjälp av specifika arketyper för ändamålet som infogas i SLOT för Tjänstedetalj.&#xD;
&#xD;
Arketypen får endast användas på två sätt:&#xD;
- som en fullständig registrering av den tjänst som har utförts, eller&#xD;
- som ett ramverk för att i första hand registrera status för den begärda tjänsten, där separata OBSERVATION-arketyper används för att registrera faktiska undersöknings- eller testresultat för den utförda tjänsten, exempelvis OBSERVATION.hearing_screening_result.&#xD;
&#xD;
Tidsangivelser relaterade till tjänsten kan hanteras på ett av två sätt:&#xD;
- genom referensmodellen - tidpunkten för utförande av varje vårdflödessteg registreras med ACTION-attributet för Tid i respektive steg&#xD;
- genom arketypens datafält - datafältet Schemalagd datum/tid är avsett att registrera den tidpunkt då tjänsten var planerad att utföras. Observera: motsvarande ACTION-attribut för Tid i planerade vårdflödessteget registrerar tidpunkten då den kliniska aktiviteten schemalades i ett system, inte den avsedda tidpunkt då aktiviteten skulle utföras.&#xD;
&#xD;
I praktiken förekommer vissa tjänster (till exempel inom öppenvård) endast vid ett tillfälle och beställs inte i förväg. Uppgifter om tjänsten registreras då mot vårdflödessteget Tjänst slutförd. I andra fall kan en återkommande tjänst beställas, och i dessa situationer registreras data mot steget Tjänst utförd vid varje tillfälle, medan instruktionen lämnas i aktivt tillstånd. När den sista utförda tjänsten registreras, dokumenteras åtgärden Tjänst slutförd, vilket visar att beställningen nu är avslutad.&#xD;
&#xD;
I andra situationer, till exempel inom specialiserad vård, kan det finnas en formell beställning av en tjänst med hjälp av en INSTRUCTION.request-arketyp. Denna ACTION-arketyp kan då användas för att registrera arbetsflödet för när och hur beställningen har genomförts.&#xD;
&#xD;
Registrering av information med denna ACTION-arketyp indikerar att någon form av aktivitet har ägt rum. Detta är oftast själva utförandet av tjänsten, men kan även avse ett misslyckat försök eller en annan aktivitet, såsom uppskjutande av tjänstens utförande. Om det finns en formell beställning av tjänsten representeras dess status av det vårdflödessteg mot vilket informationen registreras. Till exempel kan statusen för en remiss registreras genom separata anteckningar i journalsystemet vid varje vårdflödessteg, såsom att:&#xD;
- registrera "Schemalagd datum/tid" för remissen (Tjänst bokad)&#xD;
- registrera att remissen har avslutats, eventuellt inklusive information om den utförda tjänsten (Tjänst slutförd).&#xD;
&#xD;
När aktiviteterna följer de vanliga tillstånden Planerad &amp;gt; Bokad &amp;gt; Aktiv &amp;gt; Slutförd är det vanligtvis inte nödvändigt att registrera en Orsak. Detta används istället främst för att dokumentera orsaken till avvikelser från det typiska vårdflödet.&#xD;
&#xD;
Observera att det i openEHR:s referensmodell finns ett attribut Tid, som är avsett att registrera datum och tid då varje vårdflödessteg i en ACTION utfördes. Detta attribut ska användas för att registrera start av tjänsten (med vårdflödessteget Tjänst utförd) eller tidpunkten då tjänsten avbröts (med vårdflödessteget Tjänst avslutad utan slutförande / Tjänst avslutad i förtid).</use>
      <misuse>Ska inte användas för att registrera uppgifter om aktiviteter som kräver en särskilt anpassad ACTION-arketyp på grund av att de har mycket specifika krav på dataregistrering eller vårdflödessteg.&#xD;
Till exempel: ACTION.procedure eller ACTION.health_education.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere detaljer om en enkel helserelatert tjeneste eller aktivitet utført av en kliniker, organisasjon eller virksomhet.</purpose>
      <keywords>henvisning</keywords>
      <keywords>konsultasjon</keywords>
      <keywords>kontakt</keywords>
      <use>Brukes for å registrere detaljer om en enkel helserelatert tjeneste eller aktivitet utført av en kliniker, organisasjon eller virksomhet. Dette omfatter sporing av fremdrift fra planlegging, via tidfesting og utførelse til fullføring, i tillegg til avvik fra det tilsiktede forløpet, for eksempel utsettelse eller avlysning. Dette gjøres ved å registrere informasjon i relevante dataelementer om de spesifikke prosesstrinnene i arketypen.&#xD;
&#xD;
Denne arketypen omfatter aktiviteter for et bredt spekter av ukomplekse kliniske tjenester, for eksempel:&#xD;
- egenhenvisning fra en pasient for kontroll hos tannlege til forebyggende behandling&#xD;
- en serie konsultasjoner hos en fysioterapeut til behandling av muskel/skjelettbelastning&#xD;
- en henvisning fra bestillende helsepersonell, for eksempel en fastlege, til mottakende helsepersonell, for eksempel et sykehus, for at pasienten skal motta en bestemt tjeneste, råd eller behandling.&#xD;
&#xD;
Ytterligere strukturert og detaljert informasjon om tjenesten kan registreres ved å bruke formålsspesifikke arketyper i SLOTet "Tjenestedetaljer", der det er nødvendig.&#xD;
&#xD;
Denne arketypen kan brukes på to måter:&#xD;
- som en fullstendig oversikt over tjenesten som ble levert; eller&#xD;
- som et rammeverk for å registrere tilstanden til den forespurte tjenesten, med separate OBSERVATION-arketyper i samme templat, og som brukes til å registrere de faktiske resultatene av den leverte tjenesten - for eksempel OBSERVATION.hearing_screening_result&#xD;
&#xD;
Tidspunkter knyttet til en tjeneste kan administreres på en av to måter:&#xD;
- ved å bruke referansemodellen - tiden for utførelse av ethvert prosesstrinn vil benytte ACTION time referansemodell-attributtet for hvert trinn; eller&#xD;
- ved bruk av arketypedata - dataelementet "Tidfestet dato/tid" er ment å registrere det nøyaktige tidspunktet når tjenesten er planlagt utført. Merk: det tilsvarende ACTION-tidsattributtet for trinnet "Tjeneste tidfestet" vil registrere tiden da tjenesten ble planlagt i et system, ikke den tiltenkte dato/klokkeslett som tjenesten er ment å bli utført på.&#xD;
&#xD;
I praksis vil enkelte tjenester (for eksempel innen dagbehandling) skje én gang og ikke bestilles og planlagges på forhånd. Detaljene om tjenesten vil bli lagt direkte til i prosesstrinnet, "Tjeneste fullført". I andre tilfeller vil en gjentakende tjeneste bli bestilt, og i denne situasjonen vil data knyttet til trinnet '"Tjeneste utført" bli registrert ved hver repetisjon av tjenesten, slik at den overordnede helsetjenesteaktiviteten blir værende i aktiv tilstand. Når siste tjeneste er registrert, benyttes prosesstrinnet "Tjeneste fullført" som viser at denne bestillingen nå er i fullført tilstand.&#xD;
&#xD;
I andre situasjoner, for eksempel andrelinjetjeneste, kan det være en formell bestilling av en tjeneste ved bruk av en tilsvarende INSTRUCTION.service_request-arketype. Denne ACTION-arketypen kan deretter brukes til å registrere arbeidsflyten for når og hvordan bestillingen er utført.&#xD;
&#xD;
Ved registrering av informasjon ved hjelp av denne arketypen indikeres det at en aktivitet faktisk har skjedd. Dette vil som oftest være tjenesteleveransen i seg selv, kan kan også være et mislykket forsøk eller en utsettelse. Dersom det finnes en formell ordinering av tjenesten, representeres statusen for ordinering ved prosesstrinnet som registreres. For eksempel kan denne arketypen brukes til å følge fremgangen i behandlingen av en henvisning gjennom separate journaloppføringer, hver med sitt prosesstrinn:&#xD;
- registrere dato/tiden tjenesten er ment utført på ved hjelp av elementet "Planlagt dato/id" og prosesstrinnet "Tjeneste tidfestet"&#xD;
- registrere at henvisningen er fullført, potensielt inkludert informasjon om den leverte tjenesten, og prosesstrinnet "Tjeneste fullført"&#xD;
&#xD;
Dersom aktivitetene følger den vanlige flyten Planlagt &gt; Tidfestet &gt; Aktiv &gt; Fullført, er det som regel ikke nødvendig å registrere en "Årsak". Elementet "Årsak" er ment brukt for å angi hvorfor et forløp avviker fra den typiske flyten.&#xD;
&#xD;
Vær oppmerksom på at i openEHR referansemodellen er det et "Time"-attributt, som er ment å registrere når hvert prosesstrinn i tjenesteaktiviteten ble utført. Dette er attributtet som skal brukes til å registrere starttidspunktet for tjenesteutføringen (ved å bruke prosesstrinnet 'Tjeneste utført') eller tidspunktet da tjenesten ble avbrutt (ved å bruke prosesstrinnet 'Tjeneste avbrutt').</use>
      <misuse>Skal ikke brukes til å registrere data om utførte aktiviteter som krever en spesialbygd ACTION-arketype fordi de har svært spesifikke data eller krav til prosesstrinn. For eksempel: ACTION.procedure eller ACTION.health_education.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>*To record details about a health-related service or activity delivered by a clinician, organisation or agency. This includes tracking progress from planning, via scheduling and delivery to completion, as well as deviations from the intended care path such as postponement or cancellation. (en)</purpose>
      <keywords>referência</keywords>
      <keywords>visita</keywords>
      <keywords>encontro</keywords>
      <use>*To record details about a health-related service or activity delivered by a clinician, organisation or agency. This includes tracking progress from planning, via scheduling and delivery to completion, as well as deviations from the intended care path such as postponement or cancellation. This is achieved by the recording of relevant data elements about specific activities, each of which are described as the 'Pathway' careflow steps in this archetype.&#xD;
&#xD;
The scope of this archetype deliberately encompasses activities for a broad range of clinical services, to act as a non-specific archetype for all use cases. Examples include, but are not limited to:&#xD;
- self-referral by a patient for a check-up visit to a dentist for preventive care&#xD;
- a series of visits to a physiotherapist for management of a musculoskeletal strain; and&#xD;
- a referral from a requesting healthcare provider, such as a primary care clinician, to a receiving healthcare provider, such as a specialist, for the patient to receive a specific service, advice or care.&#xD;
&#xD;
Additional structured and detailed information about the service can be captured using purpose-specific archetypes inserted into the 'Service detail' slot, where required.&#xD;
&#xD;
This archetype may only be used in two ways:&#xD;
- as a full record of the service that was delivered; or&#xD;
- as a framework to record primarily the state of the requested service, with separate OBSERVATION archetypes used to record the actual test results for the delivered service - for example OBSERVATION.hearing_screening_result.&#xD;
&#xD;
Timings related to service management can be managed in one of two ways:&#xD;
- Using the reference model - the time for performance of any pathway step will use the ACTION time attribute for each step.&#xD;
- Archetyped data elements - the 'Scheduled date/time' data element is intended to record the time when the service was intended to be carried out. Note: the corresponding ACTION time attribute for the Scheduled pathway step will record the time that the clinical activity was scheduled into a system, not the intended date/time on which the activity is intended to be carried out.&#xD;
&#xD;
In practice, some services (for example, in ambulatory care) will occur once and not be ordered in advance. The details about the service will be added against the pathway step, 'Service completed'. In some cases a recurring service will be ordered, and in this situation data against the 'Service delivered' step will be recorded on each occasion, leaving the instruction in the active state. When the last delivery of the service is recorded, the 'Service completed' action is recorded showing that this order is now in the completed state.&#xD;
&#xD;
In other situations, such as secondary care, there may be a formal order for a service using a corresponding INSTRUCTION.request archetype. This ACTION archetype can then be used to record the workflow of when and how the order has been carried out.&#xD;
&#xD;
Recording information using this ACTION archetype indicates that some sort of activity has actually occurred; this will usually be the service delivery itself but may be a failed attempt or another activity such as postponement of the service delivery. If there is a formal order for the service, the state of this order is represented by the Pathway step against which the data is recorded. For example, using this archetype the progressing state of a referral request may be recorded through separate entries in the EHR progress notes at each 'Pathway' step:&#xD;
- record the scheduled Start date/time for the referral (Service scheduled); and&#xD;
- record that the referral has been completed, potentially including information about the service delivered (Service completed).&#xD;
&#xD;
When the activities follow the usual Planned &gt; Scheduled &gt; Active &gt; Completed states, recording a 'Reason' is not usually necessary - rather, it is usually used to record the reason for deviation from the typical care pathway.&#xD;
&#xD;
Please note that in the openEHR Reference Model there is a 'Time' attribute, which is intended to record the date and time at which each pathway step of the Action was performed. This is the attribute to use to record the start of the service (using the 'Service delivered' pathway step) or the time that the service was aborted (using the 'Service abandoned' pathway step). (en)</use>
      <misuse>Não deve ser usado para registrar dados sobre atividades realizadas para atividades que exigem um arquétipo ACTION construído para esse fim, pois elas possuem requisitos muito específicos de registro de dados ou de etapas do caminho. Por exemplo: ACTION.procedure ou ACTION.health_education.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record details about a simple health-related service or activity delivered by a clinician, organisation or agency.</purpose>
      <keywords>referral</keywords>
      <keywords>visit</keywords>
      <keywords>encounter</keywords>
      <use>To record details about a simple health-related service or activity delivered by a clinician, organisation or agency. This includes tracking progress from planning, via scheduling and delivery to completion, as well as deviations from the intended care path such as postponement or cancellation. This is achieved by the recording of relevant data elements about specific activities, each of which are described as the 'Pathway' careflow steps in this archetype.&#xD;
&#xD;
The scope of this archetype deliberately encompasses activities for a broad range of clinical services, to act as a non-specific archetype for all non-complex use cases. Examples include, but are not limited to:&#xD;
- self-referral by a patient for a check-up visit to a dentist for preventive care&#xD;
- a series of visits to a physiotherapist for management of a musculoskeletal strain; and&#xD;
- a referral from a requesting healthcare provider, such as a primary care clinician, to a receiving healthcare provider, such as a specialist, for the patient to receive a specific service, advice or care.&#xD;
&#xD;
Additional structured and detailed information about the service can be captured using purpose-specific archetypes inserted into the 'Service detail' slot, where required.&#xD;
&#xD;
This archetype may only be used in two ways:&#xD;
- as a full record of the service that was delivered; or&#xD;
- as a framework to record primarily the state of the requested service, with separate OBSERVATION archetypes used to record the actual test results for the delivered service - for example OBSERVATION.hearing_screening_result.&#xD;
&#xD;
Timings related to service management can be managed in one of two ways:&#xD;
- Using the reference model - the time for performance of any pathway step will use the ACTION time attribute for each step.&#xD;
- Archetyped data elements - the 'Scheduled date/time' data element is intended to record the time when the service was intended to be carried out. Note: the corresponding ACTION time attribute for the Scheduled pathway step will record the time that the clinical activity was scheduled into a system, not the intended date/time on which the activity is intended to be carried out.&#xD;
&#xD;
In practice, some services (for example, in ambulatory care) will occur once and not be ordered in advance. The details about the service will be added against the pathway step, 'Service completed'. In some cases a recurring service will be ordered, and in this situation data against the 'Service delivered' step will be recorded on each occasion, leaving the instruction in the active state. When the last delivery of the service is recorded, the 'Service completed' action is recorded showing that this order is now in the completed state.&#xD;
&#xD;
In other situations, such as secondary care, there may be a formal order for a service using a corresponding INSTRUCTION.request archetype. This ACTION archetype can then be used to record the workflow of when and how the order has been carried out.&#xD;
&#xD;
Recording information using this ACTION archetype indicates that some sort of activity has actually occurred; this will usually be the service delivery itself but may be a failed attempt or another activity such as postponement of the service delivery. If there is a formal order for the service, the state of this order is represented by the Pathway step against which the data is recorded. For example, using this archetype the progressing state of a referral request may be recorded through separate entries in the EHR progress notes at each 'Pathway' step:&#xD;
- record the scheduled Start date/time for the referral (Service scheduled); and&#xD;
- record that the referral has been completed, potentially including information about the service delivered (Service completed).&#xD;
&#xD;
When the activities follow the usual Planned &gt; Scheduled &gt; Active &gt; Completed states, recording a 'Reason' is not usually necessary - rather, it is usually used to record the reason for deviation from the typical care pathway.&#xD;
&#xD;
Please note that in the openEHR Reference Model there is a 'Time' attribute, which is intended to record the date and time at which each pathway step of the Action was performed. This is the attribute to use to record the start of the service (using the 'Service delivered' pathway step) or the time that the service was aborted (using the 'Service abandoned' pathway step).</use>
      <misuse>Not to be used to record data about activities carried out for activities that require a purpose built ACTION archetype because they have very specific data recording or pathway step requirements. For example: ACTION.procedure or ACTION.health_education.</misuse>
      <copyright>© openEHR Foundation, Northern Territory Department of Health (Australia)</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fr</code_string>
      </language>
      <purpose>Pour enregistrer les détails d'un service ou d'une activité simple en matière de santé fourni(e) par un professionnel de santé, une organisation ou une autorité.</purpose>
      <keywords>référence</keywords>
      <keywords>visite</keywords>
      <keywords>consultation</keywords>
      <use>Pour enregistrer les détails d’un service ou d’une activité simple lié(e) à la santé et fourni(e) par un clinicien, une organisation ou une autorité. Cela inclut le suivi de l’avancement depuis la planification, en passant par la programmation et la prestation, jusqu’à l’achèvement, ainsi que les écarts par rapport au parcours de soins prévu, tels que les ajournements ou les annulations. Pour ce faire, les éléments de données pertinents relatifs à des activités spécifiques, dont chacune est décrite comme une étape du parcours de soins dans cet archétype, sont enregistrés (onglet « Pathway »).&#xD;
&#xD;
Le champ d’application de cet archétype englobe délibérément des activités relevant d’un large éventail de services cliniques, afin de servir d’archétype non spécifique pour tous les cas d’utilisation non complexes. Voici quelques exemples, sans que cette liste soit exhaustive :&#xD;
- prise de rendez-vous autonome par un patient pour une visite de contrôle chez un dentiste dans le cadre de soins préventifs ;&#xD;
- une série de consultations chez un physiothérapeute pour la prise en charge d’une lésion musculosquelettique ; et&#xD;
- une référence par un professionnel de santé demandeur, tel qu’un médecin généraliste, à un professionnel de santé destinataire, tel qu’un spécialiste, afin que le patient bénéficie d’un service, d’un conseil ou de soins spécifiques.&#xD;
&#xD;
Des informations supplémentaires structurées et détaillées concernant le service peuvent être saisies à l’aide d’archétypes spécifiques à cet effet, insérés dans l’emplacement « Détails du service », si nécessaire.&#xD;
&#xD;
Cet archétype ne peut être utilisé que de deux manières :&#xD;
- comme enregistrement complet du service qui a été fourni ; ou&#xD;
- comme cadre pour enregistrer principalement l’état du service demandé, des archétypes OBSERVATION distincts étant utilisés pour enregistrer les résultats réels des tests relatifs au service fourni — par exemple OBSERVATION.hearing_screening_result.&#xD;
&#xD;
Les timings liés à la gestion du service peuvent être gérés de deux manières :&#xD;
- À l’aide du modèle de référence : le temps nécessaire à l'exécution de chaque étape du parcours utilisera l’attribut de temps de la classe ACTION pour chaque étape.&#xD;
- Éléments de données archétypés : l’élément de données « Date planifiée/heure planifiée » est destiné à enregistrer l’heure à laquelle le service devait être effectué. Remarque : l’attribut de temps ACTION correspondant à l’étape « Service planifié » du parcours enregistrera l’heure à laquelle l’activité clinique a été programmée dans un système, et non la date/heure prévue à laquelle l’activité doit être effectuée.&#xD;
&#xD;
Dans la pratique, certains services (par exemple, en soins ambulatoires) ne sont fournis qu’une seule fois et ne font pas l’objet d’une prescription préalable. Les détails relatifs au service seront ajoutés à l’étape du parcours intitulée « Activité de service achevée ». Dans certains cas, un service récurrent sera prescrit ; dans cette situation, les données relatives à l’étape « Service effectué » seront enregistrées à chaque occasion, laissant l’instruction à l’état actif. Lorsque la dernière prestation du service est enregistrée, l’action « Activité de service achevée » est enregistrée, indiquant que cette demande est désormais à l’état « achevée / terminée ».&#xD;
&#xD;
Dans d’autres situations, telles que les soins secondaires, il peut exister une demande formelle de service utilisant l’archétype INSTRUCTION.request correspondant. L'archétype ACTION peut alors être utilisé pour enregistrer le déroulement du processus indiquant quand et comment la demande a été exécutée.&#xD;
&#xD;
L’enregistrement d’informations à l’aide de cet archétype ACTION indique qu’une activité quelconque a effectivement eu lieu ; il s’agira généralement de la prestation de service elle-même, mais cela peut également être une tentative infructueuse ou une autre activité telle que l'ajournement de la prestation du service. S’il existe une demande formelle de service, l’état de cette demande est représenté par l’étape du parcours par rapport à laquelle les données sont enregistrées. Par exemple, à l’aide de cet archétype, l’état d’avancement d’une demande de référence peut être enregistré par le biais d’entrées distinctes dans les notes d’évolution du dossier patient électronique à chaque étape du parcours de soins :&#xD;
- enregistrer la date/heure de début prévues pour la référence (Service programmé) ; et&#xD;
- enregistrer que la référence a été menée à bien, en incluant éventuellement des informations sur le service fourni (Service terminé).&#xD;
&#xD;
Lorsque les activités suivent les états habituels « Planifié » &gt; « Programmé » &gt; « Actif » &gt; « Terminé », il n’est généralement pas nécessaire d’enregistrer une « Raison » ; celle-ci sert plutôt à enregistrer la raison d’un écart par rapport au parcours de soins type.&#xD;
&#xD;
Veuillez noter que dans le modèle de référence openEHR, il existe un attribut « Time », destiné à enregistrer la date et l’heure à laquelle chaque étape du parcours de soins de l’action a été effectuée. C’est cet attribut qu’il convient d’utiliser pour enregistrer le début du service (à l’aide de l’étape du parcours « Service effectué ») ou l’heure à laquelle le service a été interrompu (à l’aide de l’étape du parcours « Service abandonné »).</use>
      <misuse>À ne pas utiliser pour enregister des données concernant des activités nécessitant un archétype ACTION spécialement conçu, si celles-ci ont des exigences très spécifiques en matière d’enregistrement des données ou d’étapes du parcours de soins. Par exemple : ACTION.procedure ou ACTION.health_education.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>zh-cn</code_string>
      </language>
      <purpose>旨在用于记录关于临床医务人员、组织机构或代理机构/服务机构所提供的，简单的，与健康相关的服务或活动的详情。</purpose>
      <keywords>服务</keywords>
      <keywords>服务项目</keywords>
      <keywords>转诊</keywords>
      <keywords>转诊介绍</keywords>
      <keywords>转介</keywords>
      <keywords>推荐</keywords>
      <keywords>推介</keywords>
      <keywords>就诊</keywords>
      <keywords>就医</keywords>
      <keywords>访视</keywords>
      <keywords>就医</keywords>
      <keywords>就医过程</keywords>
      <keywords>接触</keywords>
      <keywords>健康医疗服务接触</keywords>
      <use>旨在用于记录关于临床医务人员、组织机构或代理机构/服务机构所提供的，简单的，与健康相关的服务或活动的详情。其中包括追踪从计划编制/规划、排程/排期、提供/交付服务直至完成的整个过程的进展情况，以及相对于既定照护服务/诊疗路径的偏差/偏离情况（如服务延期或取消）。为此，实现的方式就是，在本原始型当中，记录特定活动的相关数据元，并将这些数据元均描述为“路径”（Pathway）照护服务/诊疗流程步骤。&#xD;
&#xD;
本原始型的适用范围有意涵盖了各类临床服务的活动，旨在作为适用于所有非复杂用例的通用原始型。示例包括但不限于：&#xD;
- 患者为接受预防性照护/诊疗服务，自行提出的牙科健康检查转诊；&#xD;
- 患者因肌肉骨骼劳损接受治疗而前往物理治疗师处的一系列就诊；&#xD;
- 转诊：由请求方健康医疗服务提供者（如初级保健/基层临床医务人员）将患者转诊至接收方健康医疗服务提供者（如专科医生），以便让患者获得特定的服务、建议或照护/诊疗服务。&#xD;
&#xD;
如需记录有关该服务的更多结构化详情，可在“服务详情”（Service detail）插槽中插入专用原始型。&#xD;
&#xD;
仅可采取下列两种方式来使用本原始型：&#xD;
- 作为关于所提供服务的完整记录；&#xD;
- 作为主要记录所请求服务的状态的框架，同时利用单独的观察类原始型（OBSERVATION）来记录所提供服务的实际观察（检验/检查）结果，如观察类听力筛查结果原始型（OBSERVATION.hearing_screening_result）。&#xD;
&#xD;
可以采取下列两种方式之一来管理那些与服务[项目]管理相关的时间：&#xD;
- 利用参考模型：任何路径步骤的执行时间均会采用各步骤的行动类（ACTION）时间属性。&#xD;
- 原始型化数据元：“所排程的日期/时间”（Scheduled date/time）数据元旨在用于记录当时预定执行此项服务的时间。注：“已排程”（Scheduled）路径步骤相应的行动类时间属性，将记录的是当时将此项临床活动排程到系统当中的时间，而并非预定开展/执行此项活动的预定日期/时间。&#xD;
&#xD;
在实际工作中，部分的服务（如门诊照护/诊疗过程中）为即时开展，仅会发生一次，无需提前下达医嘱。关于此类服务的详情，将会在“服务已完成”（Service completed）路径步骤下录入相关的数据。在某些情况下，会下达关于重复型服务的医嘱，而此时，对于此类服务的每次重复，将会在“服务已提供”（Service delivered）路径步骤下记录相关的数据，并保持服务医嘱处于有效状态。当记录最后一次的服务提供情况时，则记录的是“服务已完成”行动，以表明此项服务医嘱已处于已完成状态。&#xD;
&#xD;
在其他的情况下（如二级照护/诊疗服务），可能会利用相应的指令类请求原始型（INSTRUCTION.request）来表达针对特定服务的正式医嘱。随后，则可以利用这一行动类原始型来记录关于开展/执行此项医嘱的时间和方式等工作流信息。&#xD;
&#xD;
采用这一行动类原始型来记录信息，表明已实际发生某项活动；此项活动通常为相应的服务提供过程本身，但也可能是一次失败的尝试，或者是其他的活动（如服务提供的延期）。若此项服务存在正式的医嘱，则会采用相应的“路径”步骤来表达该项医嘱的状态。例如，在每个“路径”步骤当中，可以在电子健康档案（EHR）病程/进展记录里，采用单独的条目来记录转诊请求的进展状态：&#xD;
- 记录转诊的已排程的开始日期/时间（“服务已排程”）；&#xD;
- 记录转诊已完成，并且有可能包括所提供服务的相关信息（“服务已完成”）。&#xD;
&#xD;
当活动遵循的是“计划中（Planned）&gt; 已排程（Scheduled）&gt; 进行中（Active）&gt; 已完成（Completed）”的常规状态流程时，通常无需记录“原因”（Reason）；该原因字段通常用于记录偏离常规诊疗/照护服务路径的原因。&#xD;
&#xD;
请注意，在openEHR参考模型当中，存在“时间”（Time）属性，旨在用于记录相应“行动”（Action）之中每个路径步骤的执行日期和时间。而且，服务开始时间（需采用“服务已提供”路径步骤）或服务中止时间（需采用“服务已中止”路径步骤）也都将采用该属性来记录。</use>
      <misuse>并非旨在用于记录关于所开展/执行的那些需要采用专用行动类原始型的活动的数据，因为此类活动有着非常特殊的数据记录要求或路径步骤要求。例如：行动类操作原始型（ACTION.procedure）或行动类健康宣教原始型（ACTION.health_education）。</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nl</code_string>
      </language>
      <purpose>Om gegevens vast te leggen over een eenvoudige gezondheidsgerelateerde dienst of activiteit geleverd door een arts, organisatie of instantie.</purpose>
      <keywords>verwijzing</keywords>
      <keywords>bezoek</keywords>
      <use>Om gegevens vast te leggen over een eenvoudige gezondheidsgerelateerde dienst of activiteit geleverd door een arts, organisatie of instantie. Dit omvat het bijhouden van de voortgang van planning, via het maken van afspraken en levering tot voltooiing, evenals afwijkingen van het geplande zorgpad zoals uitstel of annulering. Dit wordt bereikt door het vastleggen van relevante gegevenselementen over specifieke activiteiten, die in dit archetype elk worden beschreven als de zorgstroomstappen 'Pathway'.&#xD;
&#xD;
De reikwijdte van dit archetype omvat bewust activiteiten voor een breed scala aan klinische diensten, om te fungeren als een niet-specifiek archetype voor alle niet-complexe use cases. Voorbeelden zijn onder andere&#xD;
- zelfverwijzing door een patiënt voor een controlebezoek aan een tandarts voor preventieve zorg&#xD;
- een reeks bezoeken aan een fysiotherapeut voor de behandeling van een overbelasting van het bewegingsapparaat; en&#xD;
- een verwijzing van een aanvragende zorgverlener, zoals een huisarts, naar een ontvangende zorgverlener, zoals een specialist, om de patiënt een specifieke dienst, advies of zorg te laten ontvangen.&#xD;
&#xD;
Aanvullende gestructureerde en gedetailleerde informatie over de dienst kan worden vastgelegd met behulp van doel-specifieke archetypes die waar nodig worden ingevoegd in de sleuf "Dienstinformatie".&#xD;
&#xD;
Dit archetype mag slechts op twee manieren worden gebruikt:&#xD;
- als een volledig verslag van de geleverde dienst; of&#xD;
- als een kader om voornamelijk de status van de gevraagde dienst vast te leggen, met afzonderlijke OBSERVATION-archetypes die gebruikt worden om de eigenlijke testresultaten voor de geleverde dienst vast te leggen - bijvoorbeeld OBSERVATION.hearing_screening_result.&#xD;
&#xD;
Timings met betrekking tot servicebeheer kunnen op twee manieren worden beheerd:&#xD;
- Met behulp van het referentiemodel - de tijd voor de uitvoering van elke padstap zal het ACTION tijd-attribuut voor elke stap gebruiken.&#xD;
- Archetypische gegevenselementen - het gegevenselement "Geplande datum/tijd" is bedoeld om het tijdstip vast te leggen waarop de dienst uitgevoerd zou worden. Opmerking: het overeenkomstige ACTION tijd-attribuut voor de stap Geplande route registreert het tijdstip waarop de klinische activiteit in een systeem werd gepland, niet de beoogde datum/tijd waarop de activiteit zou worden uitgevoerd.&#xD;
&#xD;
In de praktijk zullen sommige diensten (bijvoorbeeld in de ambulante zorg) eenmalig plaatsvinden en niet vooraf besteld worden. De gegevens over de dienst worden toegevoegd aan de stap 'Dienst voltooid'. In sommige gevallen wordt een terugkerende dienst besteld, en in deze situatie worden de gegevens voor de stap "Geleverde dienst" bij elke gelegenheid geregistreerd, waardoor de instructie in de actieve status blijft. Wanneer de laatste levering van de dienst wordt geregistreerd, wordt de actie 'Dienst voltooid' geregistreerd, wat aangeeft dat deze opdracht nu in de status 'voltooid' staat.&#xD;
&#xD;
In andere situaties, zoals secundaire zorg, kan er een formele opdracht zijn voor een dienst met behulp van een overeenkomstig INSTRUCTION.request archetype. Dit ACTION archetype kan dan worden gebruikt om de workflow vast te leggen van wanneer en hoe de opdracht is uitgevoerd.&#xD;
&#xD;
Het vastleggen van informatie met behulp van dit ACTION archetype geeft aan dat een of andere activiteit daadwerkelijk heeft plaatsgevonden; dit zal meestal de dienstlevering zelf zijn, maar het kan ook een mislukte poging zijn of een andere activiteit zoals uitstel van de dienstlevering. Als er een formele order is voor de dienst, wordt de status van deze order weergegeven door de Pathway stap waartegen de gegevens worden geregistreerd. Bij gebruik van dit archetype kan de voortgang van een verwijzingsverzoek bijvoorbeeld worden vastgelegd door middel van afzonderlijke vermeldingen in de voortgangsnotities van het EPD bij elke stap van het pad:&#xD;
- de geplande begindatum/tijd voor de verwijzing vastleggen (dienst gepland); en&#xD;
- vastleggen dat de verwijzing voltooid is, eventueel met informatie over de geleverde dienst (dienst voltooid).&#xD;
&#xD;
Als de activiteiten de gebruikelijke Gepland &gt; Afspraak gemaakt &gt; Actief &gt; Voltooid toestanden volgen, is het vastleggen van een 'Reden' meestal niet nodig - het wordt eerder gebruikt om de reden voor afwijking van het typische zorgpad vast te leggen.&#xD;
&#xD;
Let op dat er in het openEHR Referentiemodel een attribuut 'Tijd' is, dat bedoeld is om de datum en tijd vast te leggen waarop elke stap in het zorgpad van de Actie werd uitgevoerd. Dit is het te gebruiken attribuut voor het vastleggen van de start van de dienst (bij gebruik van de stap 'Geleverde dienst') of de tijd dat de dienst werd afgebroken (bij gebruik van de stap 'Dienst afgebroken').</use>
      <misuse>Niet te gebruiken om gegevens vast te leggen over uitgevoerde activiteiten voor activiteiten waarvoor een speciaal gebouwd ACTION-archetype nodig is omdat zij zeer specifieke vereisten inzake gegevensregistratie of trajectstappen hebben. Bijvoorbeeld: ACTION.procedure of ACTION.health_education.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Eva-Maria Rieß, Natalia Strauch</author>
    <author id="organisation">Universitätsmedizin Göttingen, Medizinische Hochschule Hannover</author>
    <author id="email">eva-maria.riess@med.uni-goettingen.de, Strauch.Natalia@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Manna Vosta</author>
    <author id="organisation">Karolinska University Hospital</author>
    <author id="email">manna.vosta@regionstockholm.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Silje Ljosland Bakke, John Tore Valand, Terje Sagmyr</author>
    <author id="organisation">Helse Vest IKT AS</author>
    <author id="email">silje.ljosland.bakke@helse-vest-ikt.no, john.tore.valand@helse-vest-ikt.no, terje.sagmyr@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">Ana Paula Pannuti, Débora Farage, Adriana Kitajima, Fernanda Maia e Clóvis Puttini.</author>
    <author id="organisation">Core Consulting</author>
    <author id="email">ana.andrade@coreconsulting.com.br</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fr</code_string>
    </language>
    <author id="name">Jonas Bucher</author>
    <author id="organisation">Cistec AG</author>
    <author id="email">jonas.bucher@cistec.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>zh-cn</code_string>
    </language>
    <author id="name">Lin Zhang</author>
    <author id="organisation">Freelancer</author>
    <author id="email">linforest@163.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nl</code_string>
    </language>
    <author id="name">Mattijs Kuhlmann</author>
    <author id="organisation">Nedap</author>
    <author id="email">mattijs.kuhlmann@nedap.com</author>
  </translations>
  <uid>
    <value>472b238c-4432-44f0-9847-9990924f6196</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-ACTION.service.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>ACTION</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_SINGLE_ATTRIBUTE">
      <rm_attribute_name>ism_transition</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>ISM_TRANSITION</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_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>526</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0002</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0026</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>526</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0026</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0035</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>526</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0035</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0008</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>527</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0008</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0009</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>528</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0009</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0003</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>529</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0003</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0004</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>245</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0004</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0010</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>530</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0010</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0006</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>531</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0006</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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>at0023</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>533</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0023</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
      <children xsi:type="C_COMPLEX_OBJECT">
        <rm_type_name>ISM_TRANSITION</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_SINGLE_ATTRIBUTE">
          <rm_attribute_name>current_state</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>1</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>DV_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>openehr</value>
                </terminology_id>
                <code_list>532</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
          <rm_attribute_name>careflow_step</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_CODED_TEXT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>1</lower>
              <upper>1</upper>
            </occurrences>
            <node_id />
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>defining_code</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_CODE_PHRASE">
                <rm_type_name>CODE_PHRASE</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <terminology_id>
                  <value>local</value>
                </terminology_id>
                <code_list>at0005</code_list>
              </children>
            </attributes>
          </children>
        </attributes>
      </children>
    </attributes>
    <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>at0001</node_id>
        <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
          <rm_attribute_name>items</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>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>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0014</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>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_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>at0027</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/.*/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>.*</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0032</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_DATE_TIME</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_INTERVAL&lt;DV_DATE_TIME&gt;</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <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 />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_INTERVAL&lt;DV_DURATION&gt;</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0025</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>at0021</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_COUNT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>magnitude</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_PRIMITIVE_OBJECT">
                    <rm_type_name>INTEGER</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                    <item xsi:type="C_INTEGER">
                      <range>
                        <lower_included>true</lower_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>true</upper_unbounded>
                        <lower>1</lower>
                      </range>
                    </item>
                  </children>
                </attributes>
              </children>
            </attributes>
          </children>
          <children xsi:type="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>at0029</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.media_file(-[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\.media_file(-[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>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_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>at0036</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/.*/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>.*</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>at0028</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <cardinality>
            <is_ordered>false</is_ordered>
            <is_unique>false</is_unique>
            <interval>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </interval>
          </cardinality>
        </attributes>
      </children>
    </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>at0015</node_id>
        <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
          <rm_attribute_name>items</rm_attribute_name>
          <existence>
            <lower_included>true</lower_included>
            <upper_included>true</upper_included>
            <lower_unbounded>false</lower_unbounded>
            <upper_unbounded>false</upper_unbounded>
            <lower>0</lower>
            <upper>1</upper>
          </existence>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>ELEMENT</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <upper_included>true</upper_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>false</upper_unbounded>
              <lower>0</lower>
              <upper>1</upper>
            </occurrences>
            <node_id>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_IDENTIFIER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="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>at0017</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.organisation(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.organisation(-[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>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_IDENTIFIER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="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>at0019</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.organisation(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.organisation(-[a-zA-Z0-9_]+)*\.v1</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="ARCHETYPE_SLOT">
            <rm_type_name>CLUSTER</rm_type_name>
            <occurrences>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>0</lower>
            </occurrences>
            <node_id>at0031</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">Service</items>
        <items id="description">A simple health-related service or activity delivered by a clinician, organisation or agency.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Service planned</items>
        <items id="description">Service request to healthcare provider is planned.</items>
      </items>
      <items code="at0003">
        <items id="text">Service scheduled</items>
        <items id="description">An appointment for the service has been made.</items>
      </items>
      <items code="at0004">
        <items id="text">Service carried out</items>
        <items id="description">The service, or a single activity in a sequence of recurring service activities, has been carried out.</items>
      </items>
      <items code="at0005">
        <items id="text">Service activity complete</items>
        <items id="description">All service activities have been completed.</items>
      </items>
      <items code="at0006">
        <items id="text">Service abandoned</items>
        <items id="description">The referral has been ceased before the service has been completed.</items>
      </items>
      <items code="at0008">
        <items id="text">Service postponed</items>
        <items id="description">The planned service has been postponed.</items>
      </items>
      <items code="at0009">
        <items id="text">Service cancelled</items>
        <items id="description">The planned service has been cancelled prior to commencement.</items>
      </items>
      <items code="at0010">
        <items id="text">Service suspended</items>
        <items id="description">The service has been suspended without completion.</items>
      </items>
      <items code="at0011">
        <items id="text">Service name</items>
        <items id="description">Identification of the clinical service carried out.</items>
        <items id="comment">For example: 'Sarcoma MDT meeting' or 'Physiotherapy referral'. Coding of the specific service name with a terminology is preferred, where possible.</items>
      </items>
      <items code="at0012">
        <items id="text">Reason</items>
        <items id="description">Reason that the activity or care pathway step for the identified service was carried out.</items>
        <items id="comment">For example: the reason for the cancellation or suspension of the service. It is not necessary to record the reason for each pathway step that is expected. Rather this data element is intended to capture the reason for any divergence from a typical service provision process, such as 'Postponed' due to 'Patient had a fever', or a scheduled provision as part of a series may be 'Cancelled' due to 'Patient changed their mind'. Note: The clinical indication for triggering the service provision process may be recorded using the INSTRUCTION.service_request archetype.</items>
      </items>
      <items code="at0013">
        <items id="text">Description</items>
        <items id="description">Narrative description about the service, as appropriate for the pathway step.</items>
      </items>
      <items code="at0014">
        <items id="text">Service type</items>
        <items id="description">Type of service carried out.</items>
        <items id="comment">For example: 'MDT meeting' or 'Referral'</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Requestor identifier</items>
        <items id="description">The local ID assigned to the order by the healthcare provider or organisation requesting the service.</items>
        <items id="comment">This is equivalent to Placer Identifier in FHIR.</items>
      </items>
      <items code="at0017">
        <items id="text">Requestor</items>
        <items id="description">Details about the healthcare provider or organisation requesting the service.</items>
      </items>
      <items code="at0018">
        <items id="text">Service provider identifier</items>
        <items id="description">The ID assigned to the order by the provider fulfilling the service.</items>
        <items id="comment">This is equivalent to Filler Identifier in FHIR.</items>
      </items>
      <items code="at0019">
        <items id="text">Receiver</items>
        <items id="description">Details about the healthcare provider or organisation receiving the service request.</items>
      </items>
      <items code="at0021">
        <items id="text">Sequence</items>
        <items id="description">The sequence of the specified clinical service.</items>
        <items id="comment">Only for use in association with the 'Service delivered' pathway step. For example: record that this is the 3rd physiotherapy appointment in a planned sequence.</items>
      </items>
      <items code="at0023">
        <items id="text">Service expired</items>
        <items id="description">The referral has expired before the referral episode has been completed.</items>
      </items>
      <items code="at0025">
        <items id="text">Scheduled date/time</items>
        <items id="description">The date and/or time on which the service is intended to be performed.</items>
        <items id="comment">Only for use in association with the 'Service scheduled' pathway step.</items>
      </items>
      <items code="at0026">
        <items id="text">Service request sent</items>
        <items id="description">Request for service sent.</items>
      </items>
      <items code="at0027">
        <items id="text">Service detail</items>
        <items id="description">Structured information about the service.</items>
        <items id="comment">Use to capture detailed, structured information about specified aspects of the service.</items>
      </items>
      <items code="at0028">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the activity or care pathway step not captured in other fields.</items>
      </items>
      <items code="at0029">
        <items id="text">Multimedia representation</items>
        <items id="description">Digital image, video, diagram or other media representing the service.</items>
      </items>
      <items code="at0031">
        <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 equivalents.</items>
      </items>
      <items code="at0032">
        <items id="text">Planned date/time</items>
        <items id="description">The estimated date and/or time on which the service is intended to be performed.</items>
        <items id="comment">The planned date/time can be expressed as a date/time, interval of date/time, duration or interval of duration from the time of planning, or free or coded text. Only for use in association with the 'Service planned' pathway step.</items>
      </items>
      <items code="at0035">
        <items id="text">Service request received</items>
        <items id="description">Request for service received by the service provider.</items>
      </items>
      <items code="at0036">
        <items id="text">Additional details</items>
        <items id="description">Additional structured details about the service.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Serviço</items>
        <items id="description">*A health-related service or activity delivered by a clinician, organisation or agency. (en)</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Serviço planejado</items>
        <items id="description">A solicitação de serviço para o provedor de serviços de saúde está planejada.</items>
      </items>
      <items code="at0003">
        <items id="text">Serviço agendado</items>
        <items id="description">*An appointment for the service has been made. (en)</items>
      </items>
      <items code="at0004">
        <items id="text">Serviço prestado</items>
        <items id="description">*The service, or a subactivity in a multicomponent service, has been delivered. (en)</items>
      </items>
      <items code="at0005">
        <items id="text">Atividade de serviço concluída</items>
        <items id="description">Todas as atividades de serviço foram concluídas.</items>
      </items>
      <items code="at0006">
        <items id="text">Serviço abandonado</items>
        <items id="description">O encaminhamento foi encerrado antes que o serviço estivesse concluído.</items>
      </items>
      <items code="at0008">
        <items id="text">Serviço adiado</items>
        <items id="description">O serviço planejado foi adiado.</items>
      </items>
      <items code="at0009">
        <items id="text">Serviço cancelado</items>
        <items id="description">O serviço planejado foi cancelado antes do início.</items>
      </items>
      <items code="at0010">
        <items id="text">Serviço suspenso</items>
        <items id="description">O serviço foi suspenso sem conclusão.</items>
      </items>
      <items code="at0011">
        <items id="text">Nome do serviço</items>
        <items id="description">*Identification of the clinical service carried out. (en)</items>
        <items id="comment">*For example: 'Sarcoma MDT meeting' or 'Physiotherapy referral'. Coding of the specific service name with a terminology is preferred, where possible. (en)</items>
      </items>
      <items code="at0012">
        <items id="text">Razão</items>
        <items id="description">Motivo pelo qual a atividade ou a etapa do caminho do cuidado para o serviço identificado foi realizada.</items>
        <items id="comment">*For example: the reason for the cancellation or suspension of the service. It is not necessary to record the reason for each pathway step that is expected. Rather this data element is intended to capture the reason for any divergence from a typical service provision process, such as 'Postponed' due to 'Patient had a fever', or a scheduled provision as part of a series may be 'Cancelled' due to 'Patient changed their mind'. Note: The clinical indication for triggering the service provision process may be recorded using the INSTRUCTION.service_request archetype. (en)</items>
      </items>
      <items code="at0013">
        <items id="text">Descrição</items>
        <items id="description">Descrição narrativa sobre o serviço, conforme apropriado para a etapa do percurso.</items>
      </items>
      <items code="at0014">
        <items id="text">Tipo do serviço</items>
        <items id="description">*Type of service carried out. (en)</items>
        <items id="comment">*For example: 'MDT meeting' or 'Referral' (en)</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Identificador do solicitante</items>
        <items id="description">*The local ID assigned to the order by the healthcare provider or organisation requesting the service. (en)</items>
        <items id="comment">*This is equivalent to Placer Identifier in FHIR. (en)</items>
      </items>
      <items code="at0017">
        <items id="text">Solicitante</items>
        <items id="description">Detalhes sobre o prestador de cuidados de saúde ou organização que solicita o serviço.</items>
      </items>
      <items code="at0018">
        <items id="text">*Service provider identifier (en)</items>
        <items id="description">*The ID assigned to the order by the provider fulfilling the service. (en)</items>
        <items id="comment">*This is equivalent to Filler Identifier in FHIR. (en)</items>
      </items>
      <items code="at0019">
        <items id="text">Receptor</items>
        <items id="description">*Details about the healthcare provider or organisation receiving the service request. (en)</items>
      </items>
      <items code="at0021">
        <items id="text">Sequência</items>
        <items id="description">A sequência do serviço clínico especificado.</items>
        <items id="comment">Apenas para uso em associação com a etapa 'Serviço entregue'. Por exemplo: registre que esta é a terceira consulta de fisioterapia em uma seqüência planejada.</items>
      </items>
      <items code="at0023">
        <items id="text">Serviço expirado</items>
        <items id="description">O encaminhamento expirou antes do episódio de encaminhamento ter sido concluído.</items>
      </items>
      <items code="at0025">
        <items id="text">Data/hora agendada</items>
        <items id="description">A data e/ou hora em que o serviço deve ser executado.</items>
        <items id="comment">Apenas para uso em associação com a etapa 'Serviço agendado'.</items>
      </items>
      <items code="at0026">
        <items id="text">Solicitação de serviço enviada</items>
        <items id="description">Solicitação de serviço enviada.</items>
      </items>
      <items code="at0027">
        <items id="text">Detalhes do serviço</items>
        <items id="description">Informações estruturadas sobre o serviço.</items>
        <items id="comment">Use para capturar informações detalhadas e estruturadas sobre aspectos específicos do serviço.</items>
      </items>
      <items code="at0028">
        <items id="text">Comentário</items>
        <items id="description">Narrativa adicional sobre a atividade ou o caminho da assistência não capturado em outros campos.</items>
      </items>
      <items code="at0029">
        <items id="text">*Multimedia representation (en)</items>
        <items id="description">*Digital image, video, diagram or other media representing the service. (en)</items>
      </items>
      <items code="at0031">
        <items id="text">*Extension (en)</items>
        <items id="description">*Additional information required to capture local content or to align with other reference models/formalisms. (en)</items>
        <items id="comment">*For example: local information requirements or additional metadata to align with FHIR equivalents. (en)</items>
      </items>
      <items code="at0032">
        <items id="text">*Planned date/time (en)</items>
        <items id="description">*The estimated date and/or time on which the service is intended to be performed. (en)</items>
        <items id="comment">*The planned date/time can be expressed as a date/time, interval of date/time, duration or interval of duration from the time of planning, or free or coded text. Only for use in association with the 'Service planned' pathway step. (en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Service request received (en)</items>
        <items id="description">*Request for service received by the service provider. (en)</items>
      </items>
      <items code="at0036">
        <items id="text">*Additional details (en)</items>
        <items id="description">*Additional structured details about the service. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Dienstleistung</items>
        <items id="description">Eine einfache gesundheitsbezogene Dienstleistung oder Aktivität, die von einem Kliniker, einer Organisation oder einer Behörde bereitgestellt wird.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Dienstleistung geplant</items>
        <items id="description">Eine Dienstleistungsanforderung an den Gesundheitsdienstleister ist geplant.</items>
      </items>
      <items code="at0003">
        <items id="text">Dienstleistung angesetzt</items>
        <items id="description">Ein Termin für die Dienstleistung wurde vereinbart.</items>
      </items>
      <items code="at0004">
        <items id="text">Dienstleistung erbracht</items>
        <items id="description">Die Dienstleistung oder eine Teilaktivität in einer mehrkomponentigen Dienstleistung wurde durchgeführt.</items>
      </items>
      <items code="at0005">
        <items id="text">Dienstleistung abgeschlossen</items>
        <items id="description">Alle Dienstleistungsaktivitäten wurden abgeschlossen.</items>
      </items>
      <items code="at0006">
        <items id="text">Dienstleistung eingestellt</items>
        <items id="description">Die Überweisung wurde vor Abschluss der Dienstleistung beendet.</items>
      </items>
      <items code="at0008">
        <items id="text">Dienstleistung verschoben</items>
        <items id="description">Die geplante Dienstleistung wurde verschoben.</items>
      </items>
      <items code="at0009">
        <items id="text">Dienstleistung storniert</items>
        <items id="description">Die geplante Dienstleistung wurde vor ihrem Beginn storniert.</items>
      </items>
      <items code="at0010">
        <items id="text">Dienstleistung ausgesetzt</items>
        <items id="description">Die Dienstleistung wurde ohne Fertigstellung ausgesetzt.</items>
      </items>
      <items code="at0011">
        <items id="text">Name der Dienstleistung</items>
        <items id="description">Identifikation der erbrachten klinischen Leistung.</items>
        <items id="comment">Beispiel: "Sarkom-MDT-Meeting" oder "Physiotherapie-Überweisung". Die Kodierung des spezifischen Namens der Dienstleistung mit einer Terminologie ist, wo möglich, bevorzugt.</items>
      </items>
      <items code="at0012">
        <items id="text">Grund</items>
        <items id="description">Grund, warum die Aktivität oder der Pfadschritt für die identifizierte Dienstleistung durchgeführt wurde.</items>
        <items id="comment">Beispiel: Der Grund für die Stornierung oder Unterbrechung der Dienstleistung. Es ist nicht erforderlich, den Grund für jeden erwarteten Pfadschritt aufzuzeichnen. Vielmehr soll dieses Datenelement den Grund für jede Abweichung vom typischen Servicebereitstellungsprozess erfassen, wie z.B. "Verschoben" aufgrund von "Patient hatte Fieber", oder eine geplante Bereitstellung als Teil einer Serie kann "Storniert" werden, aufgrund von "Patient hat seine Meinung geändert". Hinweis: Die klinische Indikation zur Auslösung des Bereitstellungsprozesses der Dienstleistung kann mithilfe des INSTRUCTION.service_request Archetyps aufgezeichnet werden.</items>
      </items>
      <items code="at0013">
        <items id="text">Beschreibung</items>
        <items id="description">Beschreibung der Dienstleistung entsprechend dem jeweiligen Schritt im Pfad.</items>
      </items>
      <items code="at0014">
        <items id="text">Art der Dienstleistung</items>
        <items id="description">Art der durchgeführten Dienstleistung.</items>
        <items id="comment">Beispiel: "MDT-Meeting" oder "Überweisung".</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Anforderer ID</items>
        <items id="description">Die lokale ID, die der Anforderung vom Gesundheitsdienstleister oder der Organisation zugewiesen wurde, die den Service anfordert.</items>
        <items id="comment">Dies entspricht dem "Placer Identifier" in FHIR.</items>
      </items>
      <items code="at0017">
        <items id="text">Antragsteller</items>
        <items id="description">Angaben über den Gesundheitsdienstleister oder die Organisation, die die Dienstleistung anfordert.</items>
      </items>
      <items code="at0018">
        <items id="text">Service Provider Identifier</items>
        <items id="description">Die ID, die dem Auftrag vom Dienstleister zugewiesen wird, der die Dienstleistung erfüllt.</items>
        <items id="comment">Dies entspricht dem "Filler Identifier" in FHIR.</items>
      </items>
      <items code="at0019">
        <items id="text">Empfänger</items>
        <items id="description">Details über den Gesundheitsdienstleister oder die Organisation, die den Dienstleistungsantrag erhalten hat.</items>
      </items>
      <items code="at0021">
        <items id="text">Abfolge</items>
        <items id="description">Die Reihenfolge der angegebenen klinischen Dienstleistung.</items>
        <items id="comment">Nur in Verbindung mit "Dienstleistung erbracht" verwenden. Zum Beispiel: Aufzeichnung, dass es sich um den 3. Physiotherapietermin einer geplanten Abfolge handelt.</items>
      </items>
      <items code="at0023">
        <items id="text">Dienstleistung abgelaufen</items>
        <items id="description">Die Überweisung ist abgelaufen, bevor der Überweisungs-Zeitraum beendet war.</items>
      </items>
      <items code="at0025">
        <items id="text">Angesetztes Datum/angesetzte Uhrzeit</items>
        <items id="description">Das Datum und/oder die Uhrzeit, zu der die Dienstleistung durchgeführt werden soll.</items>
        <items id="comment">Nur zusammen mit dem Schritt "Dienstleistung angesetzt" verwenden.</items>
      </items>
      <items code="at0026">
        <items id="text">Dienstleistungsanforderung versendet</items>
        <items id="description">Dienstleistungsanforderung an den Gesundheitsdienstleister ist versendet.</items>
      </items>
      <items code="at0027">
        <items id="text">Dienstleistungsdetails</items>
        <items id="description">Strukturierte Informationen über die Dienstleistung.</items>
        <items id="comment">Verwenden um ausführliche, strukturierte Informationen über spezielle Aspekte der Dienstleistung festzuhalten.</items>
      </items>
      <items code="at0028">
        <items id="text">Kommentar</items>
        <items id="description">Zusätzliche Beschreibung über die Aktivität oder den Pfadschritt, die in anderen Feldern nicht erfasst wurde.</items>
      </items>
      <items code="at0029">
        <items id="text">Multimediale Darstellung</items>
        <items id="description">Digitales Bild, Video, Diagramm oder andere Medien, die die Dienstleistung darstellen.</items>
      </items>
      <items code="at0031">
        <items id="text">Erweiterung</items>
        <items id="description">Zusätzliche Informationen, die zur Erfassung lokaler Inhalte oder zur Anpassung an andere Referenzmodelle/Formalismen erforderlich sind.</items>
        <items id="comment">Zum Beispiel: Lokale Informationsanforderungen oder zusätzliche Metadaten, um Verknüpfungen mit FHIR herzustellen.</items>
      </items>
      <items code="at0032">
        <items id="text">Geplantes Datum/geplante Uhrzeit</items>
        <items id="description">Das geschätzte Datum und/oder die geschätzte Uhrzeit, zu der die Dienstleistung durchgeführt werden soll.</items>
        <items id="comment">Das geplante Datum/Uhrzeit kann als Datum/Uhrzeit, Intervall von Datum/Uhrzeit, Dauer oder Intervall von Dauer ab dem Zeitpunkt der Planung oder als freier oder codierter Text ausgedrückt werden. Nur in Verbindung mit dem Schritt "Dienstleistung geplant" zu verwenden.</items>
      </items>
      <items code="at0035">
        <items id="text">Dienstleistungsanforderung erhalten</items>
        <items id="description">Anfrage für eine Dienstleistung wurde vom Gesundheitsdienstleister erhalten.</items>
      </items>
      <items code="at0036">
        <items id="text">Zusätzliche Angaben</items>
        <items id="description">Zusätzliche strukturierte Details zur Dienstleistung.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Helsetjenesteaktivitet</items>
        <items id="description">En helserelatert tjeneste eller aktivitet utført av en kliniker, organisasjon eller virksomhet.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tjeneste planlagt</items>
        <items id="description">Tjenesteforespørsel er planlagt.</items>
      </items>
      <items code="at0003">
        <items id="text">Tjeneste tidfestet</items>
        <items id="description">Tjenesten er tidfestet, for eksempel ved timebestilling.</items>
      </items>
      <items code="at0004">
        <items id="text">Tjeneste utført</items>
        <items id="description">Helsetjenesteaktiviteten, eller én enkelt aktivitet av en serie gjentagende tjenesteaktiviteter, er utført.</items>
      </items>
      <items code="at0005">
        <items id="text">Tjeneste fullført</items>
        <items id="description">Alle aktivitetene i tjenesteforespørselen er fullført.</items>
      </items>
      <items code="at0006">
        <items id="text">Tjeneste avbrutt</items>
        <items id="description">Tjenesten har blitt avbrutt før fullføring.</items>
      </items>
      <items code="at0008">
        <items id="text">Tjeneste utsatt</items>
        <items id="description">Den planlagte tjenesten er utsatt.</items>
      </items>
      <items code="at0009">
        <items id="text">Tjeneste avlyst</items>
        <items id="description">Den planlagte tjenesten har blitt avlyst før den startet.</items>
      </items>
      <items code="at0010">
        <items id="text">Tjeneste midlertidig stanset</items>
        <items id="description">Tjenesten er suspendert/midlertidig satt på vent.</items>
      </items>
      <items code="at0011">
        <items id="text">Tjenestenavn</items>
        <items id="description">Den kliniske tjenesten som utføres.</items>
        <items id="comment">For eksempel "Sarkom MDT-møte" eller "Henvisning til fysioterapi". Koding av det spesifikke tjenestenavnet med en terminologi foretrekkes, der det er mulig.</items>
      </items>
      <items code="at0012">
        <items id="text">Årsak</items>
        <items id="description">Begrunnelse for at aktiviteten eller prosesstrinnet for den aktuelle tjenesten ble utført.</items>
        <items id="comment">For eksempel årsaken til at tjenesten ble avlyst eller satt på vent. Det er ikke nødvendig å registrere en årsak for hvert prosesstrinn når forløpet går som planlagt. Dette dataelementet er ment for å kunne registrere årsaken til avvik fra et typisk forløp, som for eksempel "Utsatt" med årsaken "Pasienten hadde feber", eller "Avlyst" med årsaken "Pasienten ombestemte seg". Merk: Den kliniske indikasjonen for at tjenesten er ordinert kan registreres i arketypen INSTRUCTION.service_request (Helsetjenesteforespørsel).</items>
      </items>
      <items code="at0013">
        <items id="text">Beskrivelse</items>
        <items id="description">Fritekstbeskrivelse av tjenesten, som passer for prosesstrinnet.</items>
      </items>
      <items code="at0014">
        <items id="text">Tjenestetype</items>
        <items id="description">Typen tjeneste som utføres.</items>
        <items id="comment">For eksempel "MDT-møte" eller "Henvisning".</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Rekvisisjonsidentifikator</items>
        <items id="description">Den lokale IDen tilordnet rekvisisjonen av helsepersonellet eller organisasjonen som rekvirerer helsetjenesteaktiviteten.</items>
        <items id="comment">Dette tilsvarer "Placer Identifier" i FHIR.</items>
      </items>
      <items code="at0017">
        <items id="text">Rekvirent</items>
        <items id="description">Detaljer om helsepersonellet eller organisasjonen som har rekvirert helsetjenesteaktiviteten.</items>
      </items>
      <items code="at0018">
        <items id="text">Utførers identifikator</items>
        <items id="description">IDen tilordnet rekvisisjonen av helsepersonellet eller organisasjonen som utfører tjenesten.</items>
        <items id="comment">Dette tilsvarer "Filler Identifier" i FHIR.</items>
      </items>
      <items code="at0019">
        <items id="text">Mottaker</items>
        <items id="description">Detaljer om helsepersonellet eller organisasjonen som mottar helsetjenesteforespørselen.</items>
      </items>
      <items code="at0021">
        <items id="text">Sekvens</items>
        <items id="description">Sekvensen av den kliniske tjenesten.</items>
        <items id="comment">Kun for bruk i forbindelse med prosesstrinnet "Tjeneste utført". For eksempel: angi at dette er 3. fysioterapitime i planlagt sekvens.</items>
      </items>
      <items code="at0023">
        <items id="text">Tjeneste utløpt</items>
        <items id="description">Tjenesteforespørselen har utløpt før tjenesten var fullført.</items>
      </items>
      <items code="at0025">
        <items id="text">Planlagt dato/tid</items>
        <items id="description">Dato og/eller klokkeslett tjenesten er ment å utføres på.</items>
        <items id="comment">Elementet skal kun brukes i forbindelse med prosesstrinnet "Tjeneste tidfestet".</items>
      </items>
      <items code="at0026">
        <items id="text">Tjenesteforespørsel sendt</items>
        <items id="description">Tjenesteforespørsel sendt.</items>
      </items>
      <items code="at0027">
        <items id="text">Tjenestedetaljer</items>
        <items id="description">Strukturert informasjon om tjenesten.</items>
        <items id="comment">Bruk for å registrere detaljert, strukturert informasjon om spesifikke aspekter av tjenesten.</items>
      </items>
      <items code="at0028">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligere fritekst om helsetjenesteaktiviteten eller prosesstrinnet som ikke fanges opp i andre felt.</items>
      </items>
      <items code="at0029">
        <items id="text">Multimediarepresentasjon</items>
        <items id="description">Digitalt bilde, video, diagram eller andre media som representerer helsetjenesten.</items>
      </items>
      <items code="at0031">
        <items id="text">Tilleggsinformasjon</items>
        <items id="description">Ytterligere informasjon som trengs for å kunne registrere lokalt definert innhold eller for å tilpasse til andre referansemodeller/formalismer.</items>
        <items id="comment">For eksempel lokale informasjonsbehov eller ytterligere metadata for å kunne tilpasse til tilsvarende konsepter i FHIR.</items>
      </items>
      <items code="at0032">
        <items id="text">Ønsket dato/tid</items>
        <items id="description">Den estimerte datoen og/eller tidspunktet for når tjenesten ønskes utført.</items>
        <items id="comment">Den ønskede dato/tiden kan uttrykkes som en dato/tid, et intervall av dato/tid, varighet eller intervall av varighet fra planleggingstidspunktet, eller fri eller kodet tekst. Elementet skal kun brukes i forbindelse med prosesstrinnet "Tjeneste planlagt".</items>
      </items>
      <items code="at0035">
        <items id="text">Tjenesteforespørsel mottatt</items>
        <items id="description">Tjenesteforespørsel mottatt av tjenesteutføreren.</items>
      </items>
      <items code="at0036">
        <items id="text">Ytterligere detaljer</items>
        <items id="description">Ytterligere strukturerte detaljer om tjenesten.</items>
      </items>
    </term_definitions>
    <term_definitions language="nl">
      <items code="at0000">
        <items id="text">Dienst</items>
        <items id="description">Een eenvoudige gezondheidsgerelateerde dienst of activiteit geleverd door een arts, organisatie of instantie.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Dienst gepland</items>
        <items id="description">Dienstverzoek aan zorgverlener is gepland.</items>
      </items>
      <items code="at0003">
        <items id="text">Dienstafspraak gemaakt</items>
        <items id="description">Een afspraak voor het uitvoeren van de dienst is gemaakt.</items>
      </items>
      <items code="at0004">
        <items id="text">Dienst geleverd</items>
        <items id="description">De service, of een enkele activiteit in een reeks terugkerende serviceactiviteiten, is uitgevoerd.</items>
      </items>
      <items code="at0005">
        <items id="text">Dienstenactiviteit voltooid</items>
        <items id="description">Alle diensten zijn voltooid.</items>
      </items>
      <items code="at0006">
        <items id="text">Dienst stopgezet</items>
        <items id="description">De verwijzing is stopgezet voordat de dienst is voltooid.</items>
      </items>
      <items code="at0008">
        <items id="text">Dienst uitgesteld</items>
        <items id="description">De geplande dienst is uitgesteld.</items>
      </items>
      <items code="at0009">
        <items id="text">Dienst geannuleerd</items>
        <items id="description">De geplande dienst is voor de aanvang geannuleerd.</items>
      </items>
      <items code="at0010">
        <items id="text">Dienst opgeschort</items>
        <items id="description">De dienst is opgeschort zonder voltooiing.</items>
      </items>
      <items code="at0011">
        <items id="text">Naam van de dienst</items>
        <items id="description">Identificatie van de uitgevoerde klinische dienst.</items>
        <items id="comment">Bijvoorbeeld: 'Fysiotherapie verwijzing'. Waar mogelijk wordt de voorkeur gegeven aan het coderen van de specifieke servicenaam met een terminologie.</items>
      </items>
      <items code="at0012">
        <items id="text">Reden</items>
        <items id="description">Reden dat de activiteit of zorgpadstap voor de geïdentificeerde dienst is uitgevoerd.</items>
        <items id="comment">Bijvoorbeeld: de reden voor de annulering of opschorting van de dienst. Het is niet nodig om de reden vast te leggen voor elke stap in het traject dat verwacht wordt. Dit gegevenselement is eerder bedoeld om de reden vast te leggen voor elke afwijking van een typisch dienstverleningsproces, zoals 'Uitgesteld' vanwege 'De patiënt had koorts', of een geplande voorziening als onderdeel van een reeks kan 'Geannuleerd' zijn vanwege 'De patiënt is van gedachten veranderd'. NB: De klinische indicatie voor het triggeren van het dienstverleningsproces kan worden vastgelegd met behulp van het archetype INSTRUCTION.service_request.</items>
      </items>
      <items code="at0013">
        <items id="text">Beschrijving</items>
        <items id="description">Verhalende beschrijving over de dienst, zoals passend bij de stap van het traject.</items>
      </items>
      <items code="at0014">
        <items id="text">Type dienst</items>
        <items id="description">Type dienst die is uitgevoerd.</items>
        <items id="comment">Bijvoorbeeld: "Verwijzing".</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Identificatiecode aanvrager</items>
        <items id="description">De lokale ID die aan de opdracht is toegewezen door de zorgverlener of organisatie die de dienst aanvraagt.</items>
        <items id="comment">Dit is gelijkwaardig aan Placer Identifier in FHIR.</items>
      </items>
      <items code="at0017">
        <items id="text">Aanvrager</items>
        <items id="description">Gegevens over de zorgverlener of organisatie die de dienst aanvraagt.</items>
      </items>
      <items code="at0018">
        <items id="text">Identificatiecode serviceprovider</items>
        <items id="description">Het ID dat aan de bestelling is toegewezen door de dienstverlener die de dienst uitvoert.</items>
        <items id="comment">Dit is gelijkwaardig aan Filler Identifier in FHIR.</items>
      </items>
      <items code="at0019">
        <items id="text">Ontvanger</items>
        <items id="description">Gegevens over de zorgverlener of organisatie die de dienstaanvraag ontvangt.</items>
      </items>
      <items code="at0021">
        <items id="text">Volgorde</items>
        <items id="description">De volgorde van de gespecificeerde klinische dienst.</items>
        <items id="comment">Alleen te gebruiken in combinatie met de stap "Dienst geleverd". Bijvoorbeeld: Registreer dat dit de 3de fysiotherapie afspraak is in een geplande reeks.</items>
      </items>
      <items code="at0023">
        <items id="text">Dienst verlopen</items>
        <items id="description">De verwijzing is verlopen voordat de verwijzingsepisode is afgerond.</items>
      </items>
      <items code="at0025">
        <items id="text">Geplande datum/tijd</items>
        <items id="description">De datum en/of het tijdstip waarop de dienst zal worden verricht.</items>
        <items id="comment">Alleen te gebruiken in combinatie met de stap "Dienstafspraak gemaakt".</items>
      </items>
      <items code="at0026">
        <items id="text">Dienstverzoek verzonden</items>
        <items id="description">Verzoek om dienst verstuurd.</items>
      </items>
      <items code="at0027">
        <items id="text">Details over dienst</items>
        <items id="description">Gestructureerde informatie over de dienst.</items>
        <items id="comment">Voor het vastleggen van gedetailleerde, gestructureerde informatie over specifieke aspecten van de dienst.</items>
      </items>
      <items code="at0028">
        <items id="text">Opmerking</items>
        <items id="description">Aanvullende informatie over de activiteit of zorgtrajectstap die niet in andere velden is opgenomen.</items>
      </items>
      <items code="at0029">
        <items id="text">Multimedia-representatie</items>
        <items id="description">Digitale afbeelding, video, diagram of andere media die de service weergeven.</items>
      </items>
      <items code="at0031">
        <items id="text">Uitbreiding</items>
        <items id="description">Aanvullende informatie die nodig is om lokale inhoud vast te leggen of om aan te sluiten bij andere referentiemodellen/formaliseringen.</items>
        <items id="comment">Bijvoorbeeld: lokale informatievereisten of aanvullende metadata om aan te sluiten bij FHIR-equivalenten.</items>
      </items>
      <items code="at0032">
        <items id="text">Geplande datum/tijd</items>
        <items id="description">De geschatte datum en/of tijd waarop de dienst zal worden uitgevoerd.</items>
        <items id="comment">De geplande datum/tijd kan worden uitgedrukt als een datum/tijd, datum/tijd interval, duur of interval van duur vanaf het moment van planning, of vrije of gecodeerde tekst. Alleen te gebruiken in combinatie met de stap "Dienst gepland".</items>
      </items>
      <items code="at0035">
        <items id="text">Dienstverzoek ontvangen</items>
        <items id="description">Verzoek om dienst ontvangen door de uitvoerder.</items>
      </items>
      <items code="at0036">
        <items id="text">Extra details</items>
        <items id="description">Extra gestructureerde details over de service.</items>
      </items>
    </term_definitions>
    <term_definitions language="zh-cn">
      <items code="at0000">
        <items id="text">服务</items>
        <items id="description">临床医务人员、组织机构或代理机构/服务机构所提供的，简单的，与健康相关的服务或活动。</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">服务已编制计划</items>
        <items id="description">目前已经为针对健康医疗服务提供者提出的服务请求编制了计划。</items>
      </items>
      <items code="at0003">
        <items id="text">服务已排程</items>
        <items id="description">目前已经为此项服务安排了预约。</items>
      </items>
      <items code="at0004">
        <items id="text">服务已执行</items>
        <items id="description">目前已经开展/执行此项服务（或一系列定期重复服务之中的某次单项服务）。</items>
      </items>
      <items code="at0005">
        <items id="text">服务活动已完成</items>
        <items id="description">所有的服务活动目前均已完成。</items>
      </items>
      <items code="at0006">
        <items id="text">服务已终止</items>
        <items id="description">在完成此项服务之前已停止了相应的转诊介绍。</items>
      </items>
      <items code="at0008">
        <items id="text">服务已延期</items>
        <items id="description">所计划的服务已推迟。</items>
      </items>
      <items code="at0009">
        <items id="text">服务已取消</items>
        <items id="description">所计划的服务在开始前已被取消。</items>
      </items>
      <items code="at0010">
        <items id="text">服务已暂停</items>
        <items id="description">目前已经中止了此项尚未完成的服务。</items>
      </items>
      <items code="at0011">
        <items id="text">服务名称</items>
        <items id="description">对所执行临床服务的标识。</items>
        <items id="comment">例如：“肉瘤多学科团队（MDT）会诊” 或 “物理治疗转诊”。尽可能优先采用指定的术语标准对具体的服务名称加以编码。</items>
      </items>
      <items code="at0012">
        <items id="text">原因</items>
        <items id="description">关于当时开展/执行针对所标识服务的活动或诊疗/照护服务路径步骤的原因。</items>
        <items id="comment">例如：关于取消或暂停此项服务的原因。并不一定要为预期的每个路径步骤记录相应的原因。本数据元旨在记录偏离典型服务提供流程的原因，例如：因 “患者发烧” 导致服务 “延期”，或系列服务之中的某次已排程的服务因 “患者改变主意” 而 遭到“取消”。注：可以利用指令类服务请求原始型（INSTRUCTION.service_request）来记录触发服务提供流程的临床适应证/指征。</items>
      </items>
      <items code="at0013">
        <items id="text">描述</items>
        <items id="description">适合于相应路径步骤的，关于此项服务的叙述性说明。</items>
      </items>
      <items code="at0014">
        <items id="text">服务类型</items>
        <items id="description">所执行服务的类型。</items>
        <items id="comment">例如：“多学科团队（MDT）会诊” 或 “转诊”。</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">请求方标识符</items>
        <items id="description">请求此项服务的健康医疗服务提供者或机构为其医嘱所分配的本地标识符。</items>
        <items id="comment">该标识符等同于健康医疗服务互操作型资源规范（FHIR）之中的 “申请方/委托方标识符”（Placer Identifier）。</items>
      </items>
      <items code="at0017">
        <items id="text">请求方</items>
        <items id="description">关于请求此项服务的健康医疗服务提供者或机构的相关详情。</items>
      </items>
      <items code="at0018">
        <items id="text">服务提供方标识符</items>
        <items id="description">提供此项服务的机构为其医嘱所分配的标识符。</items>
        <items id="comment">该标识符等同于健康医疗服务互操作型资源规范（FHIR）之中的 “执行方标识符”（Filler Identifier）。</items>
      </items>
      <items code="at0019">
        <items id="text">接收方</items>
        <items id="description">关于接收此项服务请求的健康医疗服务提供者或机构的相关详情。</items>
      </items>
      <items code="at0021">
        <items id="text">序号</items>
        <items id="description">此项指定临床服务的序号。</items>
        <items id="comment">仅仅旨在与 “服务已提供” 路径步骤联合运用。例如：记录本次为所计划序列之中的第 3 次物理治疗预约。</items>
      </items>
      <items code="at0023">
        <items id="text">服务已过期</items>
        <items id="description">在转诊流程/服务节段（referral episode）完成之前相应的转诊介绍已失效。</items>
      </items>
      <items code="at0025">
        <items id="text">所排程的日期/时间</items>
        <items id="description">预定执行此项服务的日期和/或时间。</items>
        <items id="comment">仅仅旨在与 “服务已排程” 路径步骤联合运用。</items>
      </items>
      <items code="at0026">
        <items id="text">服务请求已发送</items>
        <items id="description">目前已经发送了服务请求。</items>
      </items>
      <items code="at0027">
        <items id="text">服务详情</items>
        <items id="description">关于服务的结构化信息。</items>
        <items id="comment">用于记录此项服务特定方面的结构化详情。</items>
      </items>
      <items code="at0028">
        <items id="text">注释</items>
        <items id="description">未在其他字段中记录的、与相关活动或诊疗路径步骤有关的补充文字说明。</items>
      </items>
      <items code="at0029">
        <items id="text">多媒体表现形式</items>
        <items id="description">用于呈现此项服务的数字图像、视频、图表或其他媒体资料。</items>
      </items>
      <items code="at0031">
        <items id="text">扩展</items>
        <items id="description">采集本地内容或者实现与其他参考模型/形式化体系之间进行协调统一所额外需的其他信息。</items>
        <items id="comment">例如：旨在满足本地信息需求或实现与FHIR或CIMI等效项进行协调统一的额外元数据。</items>
      </items>
      <items code="at0032">
        <items id="text">所计划的日期/时间</items>
        <items id="description">预定执行服务的预计日期和/或时间。</items>
        <items id="comment">所计划的日期 / 时间可表示为具体日期/时间、日期/时间区间、自计划编制之时起的持续时长或持续时长区间，或自由文本型/编码型文本。仅可结合 “服务计划中” 路径步骤使用。</items>
      </items>
      <items code="at0035">
        <items id="text">服务请求已接收</items>
        <items id="description">相应的服务提供者已收到服务请求。</items>
      </items>
      <items code="at0036">
        <items id="text">其他详情</items>
        <items id="description">关于此项服务的其他结构化详情。</items>
      </items>
    </term_definitions>
    <term_definitions language="fr">
      <items code="at0000">
        <items id="text">Service</items>
        <items id="description">Un service ou une activité simple lié(e) à la santé, fourni(e) par un professionnel de santé, une organisation ou une autorité.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Service planifié</items>
        <items id="description">Une demande de service auprès d'un prestataire de soins de santé est planifié.</items>
      </items>
      <items code="at0003">
        <items id="text">Service programmé</items>
        <items id="description">Un rendez-vous a été pris pour ce service.</items>
      </items>
      <items code="at0004">
        <items id="text">Service effectué</items>
        <items id="description">Le service, ou une activité unique faisant partie d'une série d'activités récurrentes, a été réalisé.</items>
      </items>
      <items code="at0005">
        <items id="text">Activité de service achevée</items>
        <items id="description">Toutes les activités de service ont été menées à bien.</items>
      </items>
      <items code="at0006">
        <items id="text">Service abandonné</items>
        <items id="description">La prise en charge a été interrompue avant la fin de la prestation.</items>
      </items>
      <items code="at0008">
        <items id="text">Service reporté</items>
        <items id="description">Le service prévu a été reporté.</items>
      </items>
      <items code="at0009">
        <items id="text">Service annulé</items>
        <items id="description">Le service prévu a été annulé avant son début.</items>
      </items>
      <items code="at0010">
        <items id="text">Service suspendu</items>
        <items id="description">Le service a été suspendu avant d’avoir été mené à son terme.</items>
      </items>
      <items code="at0011">
        <items id="text">Nom du service</items>
        <items id="description">Identification du service clinique fourni.</items>
        <items id="comment">Par exemple : « Réunion de l'équipe multidisciplinaire sur le sarcome » ou « Orientation vers un physiothérapeute ». Dans la mesure du possible, il est préférable de coder le nom spécifique du service à l'aide d'une terminologie.</items>
      </items>
      <items code="at0012">
        <items id="text">Raison</items>
        <items id="description">Raison pour laquelle l'activité ou l'étape du parcours de soins correspondant au service identifié a été réalisée.</items>
        <items id="comment">Par exemple : la raison de l’annulation ou de la suspension du service. Il n’est pas nécessaire d’enregistrer la raison pour chaque étape prévue du parcours de soins. Cet élément de données vise plutôt à saisir la raison de tout écart par rapport à un processus de prestation de service habituel, tel que « Reporté » en raison de « Le patient avait de la fièvre », ou une prestation programmée dans le cadre d’une série pouvant être « Annulée » en raison de « Le patient a changé d’avis ». Remarque : l’indication clinique à l’origine du déclenchement du processus de prestation de service peut être enregistrée à l’aide de l’archétype INSTRUCTION.service_request.</items>
      </items>
      <items code="at0013">
        <items id="text">Description</items>
        <items id="description">Description narrative du service, adaptée à l'étape du parcours de soins.</items>
      </items>
      <items code="at0014">
        <items id="text">Type de service</items>
        <items id="description">Type de service fourni.</items>
        <items id="comment">Par exemple : « Réunion de l'équipe pluridisciplinaire » ou « Orientation vers un spécialiste ».</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Identifiant du demandeur</items>
        <items id="description">Identifiant local attribué à la demande par le prestataire de soins ou l'organisation qui sollicite le service.</items>
        <items id="comment">Cela correspond à l’identifiant « Placer » dans FHIR.</items>
      </items>
      <items code="at0017">
        <items id="text">Demandeur</items>
        <items id="description">Informations détaillées concernant le prestataire de soins ou l'organisation qui sollicite le service.</items>
      </items>
      <items code="at0018">
        <items id="text">Identifiant du prestataire de services</items>
        <items id="description">L'identifiant attribué à la demande par le prestataire qui assure le service.</items>
        <items id="comment">Cela correspond à l’identifiant « Filler » dans FHIR.</items>
      </items>
      <items code="at0019">
        <items id="text">Destinataire</items>
        <items id="description">Informations concernant le prestataire de soins ou l'organisation destinataire de la demande de service.</items>
      </items>
      <items code="at0021">
        <items id="text">Séquence</items>
        <items id="description">Déroulement du service clinique spécifié.</items>
        <items id="comment">À utiliser uniquement en association avec l'étape « Service fourni » du parcours. Par exemple : enregistrer qu'il s'agit du 3ème rendez-vous de physiothérapie dans une série planifiée.</items>
      </items>
      <items code="at0023">
        <items id="text">Service expiré</items>
        <items id="description">La demande d'orientation a expiré avant la fin de l'épisode d'orientation.</items>
      </items>
      <items code="at0025">
        <items id="text">Date programmée/heure programmée</items>
        <items id="description">La date et/ou l'heure auxquelles le service est censé être fourni.</items>
        <items id="comment">À utiliser uniquement en association avec l'étape « Service programmé » du parcours.</items>
      </items>
      <items code="at0026">
        <items id="text">Demande de service envoyée</items>
        <items id="description">Demande de service envoyée.</items>
      </items>
      <items code="at0027">
        <items id="text">Détails du service</items>
        <items id="description">Informations structurées sur le service.</items>
        <items id="comment">À utiliser pour saisir des informations détaillées et structurées sur des aspects spécifiques du service.</items>
      </items>
      <items code="at0028">
        <items id="text">Commentaire</items>
        <items id="description">Description complémentaire de l’activité ou de l’étape du parcours de soins non mentionnée dans les autres champs.</items>
      </items>
      <items code="at0029">
        <items id="text">Représentation multimédia</items>
        <items id="description">Image numérique, vidéo, schéma ou tout autre support illustrant ce service.</items>
      </items>
      <items code="at0031">
        <items id="text">Extension</items>
        <items id="description">Informations supplémentaires nécessaires pour représenter un contenu local ou pour assurer l’alignement avec d’autres modèles de référence ou formalismes.</items>
        <items id="comment">Par exemple : exigences d’information locales ou métadonnées supplémentaires permettant l’alignement avec des équivalents FHIR.</items>
      </items>
      <items code="at0032">
        <items id="text">Date planifiée/heure planifiée</items>
        <items id="description">Date et/ou heure estimées auxquelles le service est censé être fourni.</items>
        <items id="comment">La date et l’heure prévues peuvent être exprimées sous forme de Date/heure, d’intervalle de Date/heure, de durée ou d’intervalle de durée à compter du moment de la planification, ou encore sous forme de texte libre ou codé. À utiliser uniquement en association avec l’étape « Service prévu » du parcours de soins.</items>
      </items>
      <items code="at0035">
        <items id="text">Demande de service reçue</items>
        <items id="description">Demande de prestation reçue par le prestataire de services.</items>
      </items>
      <items code="at0036">
        <items id="text">Détails supplémentaires</items>
        <items id="description">Détails supplémentaires concernant le service.</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Tjänst</items>
        <items id="description">En enkel hälsorelaterad tjänst eller aktivitet som utförs av vårdpersonal, organisation eller verksamhet.</items>
      </items>
      <items code="at0001">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tjänst planerad</items>
        <items id="description">En begäran om tjänst till vårdgivare är planerad.</items>
      </items>
      <items code="at0003">
        <items id="text">Tjänst bokad</items>
        <items id="description">En tid för tjänsten har bokats.</items>
      </items>
      <items code="at0004">
        <items id="text">Tjänst utförd</items>
        <items id="description">Tjänsten, eller en enskild aktivitet i en serie av återkommande tjänster, har utförts.</items>
      </items>
      <items code="at0005">
        <items id="text">Tjänst slutförd</items>
        <items id="description">Alla tjänst har slutförts.</items>
      </items>
      <items code="at0006">
        <items id="text">Tjänst avslutad utan slutförande / Tjänst avslutad i förtid</items>
        <items id="description">Remissen har avslutats innan tjänsten har slutförts.</items>
      </items>
      <items code="at0008">
        <items id="text">Tjänst uppsjukten</items>
        <items id="description">Den planerade tjänsten har stjutits upp.</items>
      </items>
      <items code="at0009">
        <items id="text">Tjänst avbokad</items>
        <items id="description">Den planerade tjänsten har avbokats innan den påbörjades.</items>
      </items>
      <items code="at0010">
        <items id="text">Tjänst avbruten</items>
        <items id="description">Tjänsten har avbrutits utan att slutföras.</items>
      </items>
      <items code="at0011">
        <items id="text">Tjänstens namn</items>
        <items id="description">Identifiering av den kliniska tjänst som har utförts.</items>
        <items id="comment">Till exempel: ”Sarkom-MDT-möte” eller ”Remiss till fysioterapi”. Kodning av tjänstens namn till en terminologi är att föredra i de fall det är möjligt.</items>
      </items>
      <items code="at0012">
        <items id="text">Orsak</items>
        <items id="description">Orsak till att aktiviteten eller vårdflödessteget för den angivna tjänsten har utförts.</items>
        <items id="comment">Till exempel orsaken till att tjänsten har avbokats eller avbrutits. Det är inte nödvändigt att registrera orsak för varje förväntat vårdflödessteg. Detta datafält är avsett att registrera orsaken till avvikelser från den typiska processen för tillhandahållande av tjänster, till exempel att en tjänst har markerats som Uppskjuten på grund av ”Patienten hade feber”, eller att ett schemalagt tillfälle i en serie har markerats som Avbokad på grund av ”Patienten ångrade sig”. Observera: Den kliniska indikationen som initierar processen för tillhandahållande av tjänsten kan registreras med hjälp av arketypen INSTRUCTION.service_request.</items>
      </items>
      <items code="at0013">
        <items id="text">Beskrivning</items>
        <items id="description">En beskrivning om tjänsten, lämplig för aktuellt vårdflödessteg.</items>
      </items>
      <items code="at0014">
        <items id="text">Tjänstetyp</items>
        <items id="description">Typ av tjänst som har utförts.</items>
        <items id="comment">Till exempel: ”MDT-möte” eller ”Remiss”.</items>
      </items>
      <items code="at0015">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0016">
        <items id="text">Identifierare för beställare</items>
        <items id="description">Det lokala ID som tilldelats beställningen av den vårdgivare eller organisation som begär tjänsten.</items>
        <items id="comment">Detta motsvarar Placer Identifier i FHIR.</items>
      </items>
      <items code="at0017">
        <items id="text">Beställare</items>
        <items id="description">Uppgifter om den vårdgivare eller organisation som begär tjänsten.</items>
      </items>
      <items code="at0018">
        <items id="text">Identifierare för tjänsteutförare</items>
        <items id="description">Det ID som tilldelats beställningen av den vårdgivare eller organisation som utför tjänsten.</items>
        <items id="comment">Detta motsvarar Filler Identifier i FHIR.</items>
      </items>
      <items code="at0019">
        <items id="text">Mottagare</items>
        <items id="description">Uppgifter om den vårdgivare eller organisation som mottar begäran om tjänst.</items>
      </items>
      <items code="at0021">
        <items id="text">Sekvens</items>
        <items id="description">Sekvens för den angivna kliniska tjänsten.</items>
        <items id="comment">Endast avsett att användas i samband med vårdflödessteget Tjänst utförd (DET FINNS INGEN "SERVICE DELIVERED"). Till exempel: registrera att detta är det tredje besöket hos fysioterapeut i en planerad sekvens.</items>
      </items>
      <items code="at0023">
        <items id="text">Tjänst förfallen</items>
        <items id="description">Remissen har förfallit innan remissperioden har slutförts.</items>
      </items>
      <items code="at0025">
        <items id="text">Schemalagd datum/tid</items>
        <items id="description">Det datum eller den tidpunkt då tjänsten är avsedd att utföras.</items>
        <items id="comment">Endast avsett att användas i samband med vårdflödessteget Tjänst bokad.</items>
      </items>
      <items code="at0026">
        <items id="text">Begäran om tjänst skickad</items>
        <items id="description">Begäran om tjänst har skickats.</items>
      </items>
      <items code="at0027">
        <items id="text">Tjänstedetalj</items>
        <items id="description">Strukturerad information om tjänsten.</items>
        <items id="comment">Används för att registrera detaljerad, strukturerad information om specificerade aspekter av tjänsten.</items>
      </items>
      <items code="at0028">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligare beskrivning av aktiviteten eller vårdflödessteget som inte fångas i andra datafält.</items>
      </items>
      <items code="at0029">
        <items id="text">Multimedierepresentation</items>
        <items id="description">Digital bild, video, diagram eller annan media som representerar tjänsten.</items>
      </items>
      <items code="at0031">
        <items id="text">Extension</items>
        <items id="description">Plats för tilläggsinformation som krävs för lokala anpassningar eller anpassning till andra referensmodeller eller formella krav.</items>
        <items id="comment">Exempelvis lokala informationskrav eller metadata för anpassning till FHIR.</items>
      </items>
      <items code="at0032">
        <items id="text">Planerat datum/tid</items>
        <items id="description">Det uppskattade datumet och/eller den tidpunkt då tjänsten är avsedd att utföras.</items>
        <items id="comment">Planerat datum/tid kan anges som ett datum/tid, ett datum/tidsintervall, en varaktighet eller ett varaktighetsintervall räknat från planeringstillfället, eller som fri eller kodad text. Endast avsett att användas i samband med vårdflödessteget Tjänst planerad.</items>
      </items>
      <items code="at0035">
        <items id="text">Begäran om tjänst mottagen</items>
        <items id="description">Begäran om tjänst har mottagits av utföraren.</items>
      </items>
      <items code="at0036">
        <items id="text">Ytterligare detaljer</items>
        <items id="description">Ytterligare strukturerade uppgifter om tjänsten.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
