<?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-07-20</original_author>
    <original_author id="name">Ian McNicoll</original_author>
    <original_author id="organisation">freshEHR Clinical Informatics</original_author>
    <original_author id="email">ian@freshehr.com</original_author>
    <other_contributors>Andreas Abildgaard, OUS, Norway</other_contributors>
    <other_contributors>Yaser Abuhajjaj, United Arab Emirates</other_contributors>
    <other_contributors>Marit Alice Venheim, Helse Vest IKT, Norway</other_contributors>
    <other_contributors>Tomas Alme, DIPS ASA, Norway</other_contributors>
    <other_contributors>Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Koray Atalag, University of Auckland, New Zealand</other_contributors>
    <other_contributors>Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Ryan Julius Banez, AC Health, Philippines</other_contributors>
    <other_contributors>Marcos Barreto, Universidade Federal da Bahia, Brazil</other_contributors>
    <other_contributors>Kristian Berg, Vestvågøy kommune - Fagutviklingsavdelingen, Norway</other_contributors>
    <other_contributors>SB Bhattacharyya, Sudisa Consultancy Services, India</other_contributors>
    <other_contributors>Sharmila Biswas, Dr Sharmila Biswas GP, Australia</other_contributors>
    <other_contributors>Johan Bjerner, Fürst, Norway</other_contributors>
    <other_contributors>Greg Burch, Tiny Medical Apps, United Kingdom</other_contributors>
    <other_contributors>Fatemeh Chalabianloo, Helse Bergen, Norway</other_contributors>
    <other_contributors>Doug Chesher, PaLMS, Australia</other_contributors>
    <other_contributors>Bjørn Christensen, Helse Bergen HF, Norway</other_contributors>
    <other_contributors>Stephen Chu, NEHTA, Australia (Editor)</other_contributors>
    <other_contributors>Matthew Cordell, NEHTA, Australia</other_contributors>
    <other_contributors>Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway</other_contributors>
    <other_contributors>Andre de Wolf, NeHTA, Australia</other_contributors>
    <other_contributors>Gail Easterbrook, Flinders Medical Centre, Australia</other_contributors>
    <other_contributors>Stig Erik Hegrestad, Helse Førde, Norway</other_contributors>
    <other_contributors>David Evans, Queensland Health, Australia</other_contributors>
    <other_contributors>David Fallas, Sysmex NZ Ltd, New Zealand</other_contributors>
    <other_contributors>Shahla Foozonkhah, Iran ministry of health and education, Iran</other_contributors>
    <other_contributors>Hildegard Franke, freshEHR Clinical Informatics Ltd., United Kingdom</other_contributors>
    <other_contributors>Heath Frankel, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Frode Gilberg, PRIDOK AS, Norway</other_contributors>
    <other_contributors>Rosane Gotardo, Systema Ltda., Brazil</other_contributors>
    <other_contributors>Heather Grain, Llewelyn Grain Informatics, Australia</other_contributors>
    <other_contributors>Grahame Grieve, Health Intersections Pyty Ltd, Australia (Editor)</other_contributors>
    <other_contributors>Åshild Halvorsen, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>martin hanlon, Careworks, United Kingdom</other_contributors>
    <other_contributors>Sam Heard, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Anca Heyd, DIPS ASA, Norway</other_contributors>
    <other_contributors>Geir Hoff, Sykehuset Telemark HF, Norway</other_contributors>
    <other_contributors>Evelyn Hovenga, EJSH Consulting, Australia</other_contributors>
    <other_contributors>Silje Kaada, Helse-Bergen, Avdeling for immunologi og transfusjonsmedisin, Norway</other_contributors>
    <other_contributors>Lars Morgan Karlsen, DIPS ASA, Norway</other_contributors>
    <other_contributors>Mary Kelaher, NEHTA, Australia</other_contributors>
    <other_contributors>Nils Kolstrup, Skansen Legekontor og Nasjonalt Senter for samhandling og telemedisin, Norway</other_contributors>
    <other_contributors>Anne Kristin Strand, Sykehuspartner HF, Norway</other_contributors>
    <other_contributors>Tomi Laptoš, Marand, Slovenia</other_contributors>
    <other_contributors>Liv Laugen, Oslo universitetssykehus, Norway</other_contributors>
    <other_contributors>Michael Legg, Michael Legg &amp; associates, Australia</other_contributors>
    <other_contributors>Sabine Leh, Haukeland University Hospital, Department of Pathology, Norway</other_contributors>
    <other_contributors>Heather Leslie, Atomica Informatics, Australia (openEHR Editor)</other_contributors>
    <other_contributors>Neranga Liyanaarachchi, Ministry of Health, Postgraduate Institute of Medicine, Sri Lanka</other_contributors>
    <other_contributors>Zijian Li, China</other_contributors>
    <other_contributors>Jan-Arne Ludvigsen, DIPS AS, Norway</other_contributors>
    <other_contributors>Hallvard Lærum, Direktoratet for e-helse, Norway</other_contributors>
    <other_contributors>Manisha Mantri, C-DAC, India</other_contributors>
    <other_contributors>Siv Marie Lien, DIPS ASA, Norway</other_contributors>
    <other_contributors>Ole Martin Sand, DIPS ASA, Norway</other_contributors>
    <other_contributors>Mike Martyn, The Hobart Anaesthetic Group, Australia</other_contributors>
    <other_contributors>James McClay, University of Nebraska Medical Center, United States</other_contributors>
    <other_contributors>Andrew McIntyre, Medical-Objects, Australia</other_contributors>
    <other_contributors>David McKillop, NEHTA, Australia</other_contributors>
    <other_contributors>Hildegard McNicoll, freshEHR Clinical Informatics Ltd., United Kingdom</other_contributors>
    <other_contributors>Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)</other_contributors>
    <other_contributors>Angela Merzweiler, University Hospital of Heidelberg, Germany</other_contributors>
    <other_contributors>Paul Miller, SCIMP NHS Scotland, United Kingdom</other_contributors>
    <other_contributors>Chris Mitchell, RACGP, Australia</other_contributors>
    <other_contributors>Stewart Morrison, NEHTA, Australia</other_contributors>
    <other_contributors>George Nikolaidis, Ergobyte Informatics S.A., Greece</other_contributors>
    <other_contributors>Bjørn Næss, DIPS AS, Norway</other_contributors>
    <other_contributors>Bjørn Odvar Eriksen, UNN, Norway</other_contributors>
    <other_contributors>Masafumi Okada, University of Tokyo, Japan</other_contributors>
    <other_contributors>Andrej Orel, Marand d.o.o., Slovenia</other_contributors>
    <other_contributors>Michael Osborne, Mater Health Services, Australia</other_contributors>
    <other_contributors>Vaclav Papez, University of West Bohemia, Czech Republic</other_contributors>
    <other_contributors>Anne Pauline Anderssen, Helse Nord RHF, Norway</other_contributors>
    <other_contributors>Ana Pereira, CINTESIS, CUF-Porto, Portugal</other_contributors>
    <other_contributors>Vladimir Pizzo, Hospital Sírio Libanês, Brazil</other_contributors>
    <other_contributors>Navin Ramachandran, NHS, United Kingdom</other_contributors>
    <other_contributors>Lars Retterstøl, OUS, Norway</other_contributors>
    <other_contributors>Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil</other_contributors>
    <other_contributors>David Rowed, VAMC Clinic, Australia (Editor)</other_contributors>
    <other_contributors>Marcus vinicius de Régis, NUTES, Brazil</other_contributors>
    <other_contributors>Mona Saleh (Translator)</other_contributors>
    <other_contributors>Diogo Schmidt, UNISINOS, Brazil</other_contributors>
    <other_contributors>Gro-Hilde Severinsen, Norwegian center for ehealthresearch, Norway</other_contributors>
    <other_contributors>Anoop Shah, University College London, United Kingdom</other_contributors>
    <other_contributors>Kyle Shore, Charm Health, Australia</other_contributors>
    <other_contributors>Hildegunn Siv Aase, Helse Bergen, Norway</other_contributors>
    <other_contributors>Niclas Skyttberg, Karolinska Institutet, Sweden</other_contributors>
    <other_contributors>Matt Stibbs, Digi-M Ltd., United Kingdom</other_contributors>
    <other_contributors>Iztok Stotl, UKCLJ, Slovenia</other_contributors>
    <other_contributors>Norwegian Review Summary, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Line Sæle, Nasjonal IKT HF, Norway</other_contributors>
    <other_contributors>Sveinung Sørbye, UNN HF, Norway</other_contributors>
    <other_contributors>Nyree Taylor, Ocean Informatics, Australia</other_contributors>
    <other_contributors>Tesfay Teame, Folkehelseinstittutet, Norway</other_contributors>
    <other_contributors>Rowan Thomas, St. Vincent's Hospital Melbourne, Australia</other_contributors>
    <other_contributors>Michael Thompson, Queensland Health, Australia</other_contributors>
    <other_contributors>Gordon Tomes, Australian Institute of Health and Welfare, Australia</other_contributors>
    <other_contributors>Richard Townley-O'Neill, NEHTA, Australia</other_contributors>
    <other_contributors>Katrin Troeltzsch, Nationales Centrum für Tumorerkrankungen (NCT); Universitätsklinikum Heidelberg, Germany</other_contributors>
    <other_contributors>Torleif Trydal, Fürst AS, Norway</other_contributors>
    <other_contributors>Gro-Hilde Ulriksen, Norwegian center for ehealthresearch, Norway</other_contributors>
    <other_contributors>John Tore Valand, Helse Bergen, Norway (openEHR Editor)</other_contributors>
    <other_contributors>Wouter Zanen, Eurotranplant, Netherlands</other_contributors>
    <other_contributors>Lin Zhang, Taikang Insurance Group, China</other_contributors>
    <lifecycle_state>published</lifecycle_state>
    <other_details id="licence">This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.</other_details>
    <other_details id="custodian_organisation">openEHR Foundation</other_details>
    <other_details id="references">Based on Pathology Test Result, Draft Archetype [Internet]. Australian Digital Health Agency, Australian Digital Health Agency Clinical Knowledge Manager [cited: 2017-05-04]. Available from: http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.839&#xD;
&#xD;
Pathology (Data Specifications) Version 1.0 [Internet]. Sydney, Australia: National E-Health Transition Authority; 2007 May 29 [cited 2011 Jul 11]; Available at http://www.nehta.gov.au/component/docman/doc_download/962-pathology-v10.&#xD;
&#xD;
Laboratory Technical Framework, Volume 3: Content, Revision 3.0 [Internet]. USA: IHE International; 2011 May 19; [cited 2011 Jul 11]. Available from: http://www.ihe.net/Technical_Framework/index.cfm#laboratory&#xD;
&#xD;
Hl7 FHIR Diagnostic Report resource: HL7 fhir; Available from http://www.hl7.org/implement/standards/fhir/diagnosticreport.html</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">F272444B9B04B593AE9BA76751065626</other_details>
    <other_details id="build_uid">f4a7641f-8b09-4a06-b0d8-306eaa56b9af</other_details>
    <other_details id="revision">1.2.8</other_details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>de</code_string>
      </language>
      <purpose>Zur Dokumentation des Ergebnisses - einschließlich der Befunde und der Interpretation des Labors - einer Untersuchung, die an Proben durchgeführt wurde, die von einer Einzelperson stammen oder mit dieser Person zusammenhängen.</purpose>
      <keywords>Labor</keywords>
      <keywords>Pathologie</keywords>
      <keywords>Biochemie</keywords>
      <keywords>Hämatologie</keywords>
      <keywords>Mikrobiologie</keywords>
      <keywords>Immunologie</keywords>
      <keywords>Laboratorium</keywords>
      <keywords>anatomisch</keywords>
      <keywords>chemisch</keywords>
      <keywords>klinisch</keywords>
      <keywords>Immunpathologie</keywords>
      <keywords>Zytologie</keywords>
      <keywords>Histopathologie</keywords>
      <keywords>Untersuchung</keywords>
      <keywords>Biopsie</keywords>
      <keywords>Probe</keywords>
      <keywords>forensisch</keywords>
      <keywords>genetisch bedingt</keywords>
      <keywords>Labormedizin</keywords>
      <keywords>Ergebnisse</keywords>
      <keywords>Analyse</keywords>
      <use>Zur Dokumentation des Ergebnisses - einschließlich der Befunde und der Interpretation des Labors - einer Untersuchung, die an Proben durchgeführt wurde, die von einer Einzelperson stammen oder mit dieser Person zusammenhängen. Dies geschieht in der Regel in einem Labor, kann aber auch in anderen Bereichen, wie z.B. am Point of Care, durchgeführt werden. &#xD;
&#xD;
Dieser Archetyp soll das Ergebnis einer erforderlichen Einzeluntersuchung abdecken, bei der die Probe(n) über ein Einzelverfahren gesammelt werden, und kann mehrere Ergebnisse zu Analyten oder andere Komponenten enthalten. Beispiele hierfür könnte das „Vollblutbild“ sein, das ein separates Analyseergebnis für die Zählung jedes Blutzelltyps liefert, oder „Nierenbiopsie nicht neoplastisch“, das Ergebnisse aus der Mikroskopie, Immunhistochemie und Elektronenmikroskopie liefern würde.&#xD;
&#xD;
Dieser Archetyp wurde als Framework konzipiert, das in der Regel um CLUSTER-Archetypen erweitert wird, um eine angemessene Aufzeichnung spezifischer Labor-Testergebnismuster zu ermöglichen. Einschließlich aber nicht beschränkt auf: Tests für Biochemie, Hämatologie, Immunologie und Blutspendendienste etc. sowie spezifische Muster für die besonderen Anforderungen an Mikrobiologie und anatomische Pathologie. Wenn die in Auftrag gegebenen Tests oder Untersuchungen nicht gewöhnlich in einer benannten Gruppe oder einem benannten Panel zusammengehören, wird jedes Testergebnis in der Regel durch separate Instanzen dieses Archetyps dargestellt. Es gibt jedoch erhebliche Unterschiede in der tatsächlichen Berichts-/Messaging-Praxis, und dieser Archetyp/diese verwandten Archetypen sind so konzipiert, dass sie mit diesen Abweichungen umgehen können. &#xD;
&#xD;
Dieser Archetyp unterstützt mehrere Ansätze zur Erfassung von Proben und spiegelt die aktuelle, sehr unterschiedliche Praxis wieder. Ein Laborergebnis hat einen hohen Grad an Übereinstimmung mit einer HL7 FHIR Diagnoseberichtsquelle. &#xD;
&#xD;
Es wird erwartet, dass ein oder mehrere Exemplare dieses Archetyps oder dieser Archetypfamilie an einen anfragenden Arzt innerhalb eines Labordokuments zurückgeschickt werden, das COMPOSITION.report_result Archetyp, oder ähnliche und andere relevante ENTRY Archetypen.&#xD;
&#xD;
Die Erfassung von Störfaktoren kann inkonsistent sein, weil es oft vom Quelllabor und von den klinischen Informationen, die angefordert worden, abhängt. Im State-Abschnitt des Archetyps gibt es ein einfaches Datenelement "Confounding factors", das optional ist und als eine Möglichkeit wiederholt werden kann, eine Vielzahl von einfachen Faktoren zu erfassen, die explizit gemacht werden müssen, da sie die Interpretation der Ergebnisse beeinflussen können. Wenn die Störfaktoren komplexer sind, kann es sinnvoll sein, einen lokalen/gemeinsamen CLUSTER-Archetyp zu erstellen, der im SLOT "Confounding factors details" ergänzt werden kann. &#xD;
Hinweis 1: Bekannte oder erforderliche Voraussetzungen, wie z.B. "Fasten" oder "Tag 1 des Menstruationszyklus", sollten im Datenelement "Probenbedingungen" im Archetyp CLUSTER.Probe, verschachtelt innerhalb des OBSERVATION Archetypes, angegeben werden.&#xD;
Hinweis 2: Bekannte Probleme bei der Probenentnahme oder Behandlung, wie z.B. "Probe hämolysiert" oder "verlängerter Gebrauch von Tourniquet", sollten unter "Probenqualität" im Archetyp CLUSTER.Probe, verschachtelt innerhalb des OBSERVATION Archetypes, angegeben werden.&#xD;
&#xD;
Werden vom Labor "Reflextests" durchgeführt, können diese gemäß den US/FHIR-Richtlinien (siehe https://www.hl7.org/fhir/2015may/uslabreportguide.html) oder anderen lokalen Richtlinien durchgeführt werden. Zum Beispiel eine der folgenden Punkte.... &#xD;
1. Protokollierung der Reflextestergebnisse zusätzliche "Testergebnisse" innerhalb derselben "openEHR-EHROBSERVATION.Laborergebnis". &#xD;
2. Protokollierung der Reflextestergebnisse zusätzliche "Testergebnisse" innerhalb derselben "openEHR-EHROBSERVATION.Laborergebnis", verweisen Sie aber über "Testerforderungsdetails" auf den ursprünglichen Labortestantrag. &#xD;
3. Protokollierung der Reflextestergebnisse zusätzliche "Testergebnisse" innerhalb derselben "openEHR-EHROBSERVATION.Laborergebnis" festhalten, aber über "Testerforderungsdetails" auf einen neuen Labortestantrag sowie den ursprünglichen Labortestantrag verweisen.</use>
      <misuse>Nicht zur Dokumentation eines Autopsieberichts oder eines forensischen Berichts verwenden. Einzelne Proben, die bei einer Autopsie oder einem forensischen Bericht entnommen werden, können jedoch mit diesem Archetyp dargestellt werden. Für diese sind zusätzliche spezialisierte Archetypen erforderlich, um die Daten zu dokumentieren.&#xD;
&#xD;
Dieser Archetyp eignet sich zur Darstellung allgemeiner Labortestergebnisse, jedoch nicht für vollständige synoptische Berichte. Für diese sind zusätzliche spezialisierte Archetypen erforderlich, um die Daten zu dokumentieren.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>sv</code_string>
      </language>
      <purpose>För att registrera resultat, fynd och laboratoriets tolkning av en laboratorieundersökning utförd på provmaterial från en individ eller relaterad till individen.</purpose>
      <keywords>labb</keywords>
      <keywords>lab</keywords>
      <keywords>patologi</keywords>
      <keywords>biokemi</keywords>
      <keywords>hematologi</keywords>
      <keywords>mikrobiologi</keywords>
      <keywords>immunologi</keywords>
      <keywords>laboratorium</keywords>
      <keywords>anatomisk</keywords>
      <keywords>kemisk</keywords>
      <keywords>klinisk</keywords>
      <keywords>klinisk kemi</keywords>
      <keywords>immunopatologi</keywords>
      <keywords>cytologi</keywords>
      <keywords>histopatologi</keywords>
      <keywords>test</keywords>
      <keywords>biopsi</keywords>
      <keywords>prov</keywords>
      <keywords>provmaterial</keywords>
      <keywords>rättsmedicin</keywords>
      <keywords>forensisk</keywords>
      <keywords>genetisk</keywords>
      <keywords>laboratoriemedicin</keywords>
      <keywords>resultat</keywords>
      <keywords>analys</keywords>
      <keywords>flödescytometri</keywords>
      <keywords>immunoflourescens</keywords>
      <use>Används för att registrera resultatet, inklusive fynd och laboratoriets tolkning, av en laboratorieundersökning utförd på provmaterial från en individ eller relaterad till individen. Detta görs vanligtvis i ett laboratorium, men kan även göras i andra miljöer såsom patientnära analys vid provtagningstillfället.&#xD;
&#xD;
Denna arketyp är avsedd att täcka resultatet av en enda beställd undersökning där flera prov tas i ett enda förfarande och som kan innehålla flera analysresultat eller andra komponenter. &#xD;
Exempel på detta kan inkludera "fullständig blodstatus", vilket skulle ge ett separat analysresultat för räkningen av varje typ av blodkropp, eller "njurbiopsi - inget malignt", vilket skulle ge resultat från mikroskopi, immunhistokemi och elektronmikroskopi.&#xD;
&#xD;
Denna arketyp är utformad för att utgöra ett ramverk som vanligtvis kommer att utökas med CLUSTER-arketyper för registrering och rapportering av specifika mönster för laboratorieresultat. Detta inkluderar analyser inom biokemi, klinisk kemi, hematologi, immunologi och transfusionstjänster samt specifika mönster för de unika behoven inom mikrobiologi och patologi. Om de beställda analyserna eller undersökningarna inte tillhör en namngiven grupp, ska varje testresultat normalt representeras med separata instanser av denna arketyp. Det finns dock stor variation i hur svarsrapportering sker och denna arketyp är utformad för att hantera den typen av variation.&#xD;
&#xD;
Den här arketypen stöder olika tillvägagångssätt för att kunna fånga den mångfald av analyser och metoder som finns tillgängliga. Ett resultat från ett laboratorium är idag i hög grad anpassat till HL7 FHIR-resursen Diagnostic Report.&#xD;
&#xD;
Det är troligt att hela eller delar av denna arketyp, tillsammans med relaterade arketyper, kommer att utgöra remissvar till remitterande läkare. Exempel på detta är COMPOSITION.report_result-arketypen eller motsvarande, och med relevanta ENTRY-arketyper.&#xD;
&#xD;
Denna arketyp stöder flera metoder för att registrera information om provmaterialet, vilket återspeglar de stora variationerna inom nuvarande praxis. Arketypen för laboratoriesvar har en hög grad av överensstämmelse med HL7 FHIR-resursen "Diagnostic Report".&#xD;
&#xD;
Registrering av möjliga felkällor görs i praktiken oftast inte på ett konsekvent sätt. Detta kan bero både på avsändarlaboratoriet och på den kliniska information som skickats med från den vårdpersonal som skickat förfrågan. I "State"-delen av arketypen finns det ett enkelt dataelement, "Möjliga felkällor", som är valfritt och kan återupprepas som ett sätt att registrera en mängd olika enkla faktorer som måste göras tydliga eftersom de kan påverka tolkningen av resultaten. Om möjliga felkällor är av det mer komplexa slaget, kan det vara lämpligt att skapa en CLUSTER-arketyp som kan användas i SLOT ''Möjliga felkällor''.&#xD;
&#xD;
Anmärkning 1: Kända förhållanden eller förutsättningar för provtagning, såsom "fasta" eller "dag 1 i menstruationscykeln", bör registreras i dataelementet "Provtagningsförhållanden" i arketypen CLUSTER.Specimen (Provmaterial) nästlad i denna OBSERVATION-arketyp.&#xD;
Anmärkning 2: Kända problem med provtagning eller hantering av prover, såsom "hemolys" eller "förlängd användning av stas", bör registreras i "Provkvalitetsproblem" -elementet i CLUSTER.Specimen-arketypen och nästlas i denna OBSERVATION-arketyp.&#xD;
&#xD;
Om laboratoriet ändrar analyser eller lägger till analyser som uppföljning kan dessa hanteras enligt riktlinjer från HL7 FHIR (https://www.hl7.org/fhir/2015may/uslabreport-guide.html), eller enligt lokala förfaranden. Till exempel något av följande:&#xD;
1. Registrera de ändrade analyserna/tilläggsanalyserna inom samma instans av denna arketyp.&#xD;
2. Registrera de ändrade analyserna/tilläggsanalyserna i en ny instans av denna arketyp, men hänvisa till den ursprungliga beställningen via "Beställningsdetaljer".&#xD;
3. Registrera de ändrade analyserna/tilläggsanalyserna i en ny instans av den här arketypen, men hänvisa till en ny beställning utöver den ursprungliga via "Beställningsdetaljer".</use>
      <misuse>Bör inte användas för att lagra en obduktionsrapport eller rättsmedicinsk undersökningsrapport, även om analysresultat för vissa provmaterial som tagits vid en obduktion kan representeras i denna arketyp. För att skapa den verkliga obduktions- eller kriminaltekniska rapporten måste man använda specialiserade arketyper.&#xD;
&#xD;
Denna arketyp är lämplig för att representera allmänna laboratoriesvar men är inte avsedd för sammanfattande rapporter, där specialiserade arketyper bör användas istället.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fi</code_string>
      </language>
      <purpose>*To record the result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual.(en)</purpose>
      <keywords>*lab(en)</keywords>
      <keywords>*pathology(en)</keywords>
      <keywords>*biochemistry(en)</keywords>
      <keywords>*haematology(en)</keywords>
      <keywords>*microbiology(en)</keywords>
      <keywords>*immunology(en)</keywords>
      <keywords>*laboratory(en)</keywords>
      <keywords>*anatomical(en)</keywords>
      <keywords>*chemical(en)</keywords>
      <keywords>*clinical(en)</keywords>
      <keywords>*immunopathology(en)</keywords>
      <keywords>*cytology(en)</keywords>
      <keywords>*histopathology(en)</keywords>
      <keywords>*test(en)</keywords>
      <keywords>*biopsy(en)</keywords>
      <keywords>*specimen(en)</keywords>
      <keywords>*forensic(en)</keywords>
      <keywords>*genetic(en)</keywords>
      <keywords>*laboratory medicine(en)</keywords>
      <keywords>*results(en)</keywords>
      <keywords>*analysis(en)</keywords>
      <use>*Use to record the result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. This is typically done in a laboratory, but may be done in other environments such as at the point of care.&#xD;
&#xD;
This archetype is intended to cover the result of a single ordered investigation where the specimen(s) are collected as a single procedure, and may include multiple analyte results or other components. Examples of this could include 'Full blood count', which would yield a separate analyte result for the count of each type of blood cell, or 'kidney biopsy non-neoplastic', which would yield findings from microscopy, immunohistochemistry and electron microscopy.&#xD;
&#xD;
This archetype has been designed to be a framework that will usually be extended with CLUSTER archetypes to enable appropriate recording of specific laboratory test result patterns. This includes, but is not limited to, tests for biochemistry, haematology, immunology and transfusion services etc and specific patterns for the unique requirements for microbiology and anatomical pathology. If the ordered tests or investigations do not commonly belong together in a named group or panel, each test result would normally be represented using separate instances of this archetype. There is, however, considerable variation in actual reporting/messaging practice and this archetype/related archetypes are designed to handle such variation.&#xD;
&#xD;
This archetype supports multiple approaches to recording of specimen, reflecting current practice which varies enormously. A Laboratory test result has a high degree of alignment to an HL7 FHIR Diagnostic Report resource.&#xD;
&#xD;
It is anticipated that one or more instances of this archetype, or archetype family, will be sent back to a requesting clinician within a laboratory report document comprising COMPOSITION.report_result archetype, or similar, and other relevant ENTRY archetypes.&#xD;
&#xD;
The recording of confounding factors may be inconsistent, often depending on the analysing laboratory and on clinical information sent by the requester. In the State section of the archetype there is a simple 'Confounding factors' data element that is optional and can be repeated as one way to record a variety of simple factors that need to be made explicit as they may influence interpretation of the results. If the confounding factors are more complex, it may be appropriate to create a local/shared CLUSTER archetype that can be nested in the 'Confounding factors details' SLOT. &#xD;
Note 1: Known or required pre-conditions, such as 'fasting' or 'Day 1 of menstrual cycle', should be reported in the 'Sampling conditions' data element in the CLUSTER.specimen archetype, nested within this OBSERVATION archetype.&#xD;
Note 2: Known issues with specimen collection or handling, such as 'sample haemolysed' or 'prolonged use of tourniquet' should be reported within 'Specimen quality' in the CLUSTER.specimen archetype, nested within this OBSERVATION archetype.&#xD;
&#xD;
Where 'reflex tests' are performed by the laboratory, these may be handled as per US/FHIR guidance (see https://www.hl7.org/fhir/2015may/uslabreport-guide.html) or other local policy. For example, one of the following ...&#xD;
1. Record the reflex test results additional 'Test findings' within the same 'openEHR-EHR-OBSERVATION.laboratory_test_result'&#xD;
2. Record the reflex test results as 'Test findings' within a new 'openEHR-EHR-OBSERVATION.laboratory_test_result' but refer to the original lab test request via 'Test request details'.&#xD;
3. Record the reflex test results as 'Test findings' within a new 'openEHR-EHR-OBSERVATION.laboratory_test_result' but reference a new lab test request as well as the original lab test request via 'Test request details'.(en)</use>
      <misuse>*Not to be used to record an Autopsy or a Forensic report, although tests on some specimens that are taken in such situations may be represented using this archetype. For these, additional or specialised archetypes will be required to represent the data.&#xD;
&#xD;
This archetype is suitable for representation of general laboratory test results, but not intended to cover full synoptic reports. For these, additional specialising archetypes are required to represent the data.(en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>pt-br</code_string>
      </language>
      <purpose>Documentar o resultado, incluindo achados e a interpretação do laboratório, de uma investigação realizada em amostras coletadas de um indivíduo ou relacionadas a esse indivíduo.</purpose>
      <keywords>lab</keywords>
      <keywords>laboratório</keywords>
      <keywords>patologia</keywords>
      <keywords>bioquímica</keywords>
      <keywords>hematologia</keywords>
      <keywords>microbiologia</keywords>
      <keywords>imunologia</keywords>
      <keywords>anatomia</keywords>
      <keywords>química</keywords>
      <keywords>clínico</keywords>
      <keywords>imunopatologia</keywords>
      <keywords>citologia</keywords>
      <keywords>histopatologia</keywords>
      <keywords>teste</keywords>
      <keywords>biópsia</keywords>
      <keywords>espécimen</keywords>
      <keywords>forense</keywords>
      <keywords>genético</keywords>
      <keywords>laboratório médico</keywords>
      <keywords>laboratório clínico</keywords>
      <keywords>resultados</keywords>
      <keywords>análises</keywords>
      <keywords>análises clínicas</keywords>
      <use>Use para documentar o resultado, incluindo achados e a interpretação do laboratório, de uma investigação realizada em amostras coletadas de um indivíduo ou relacionadas a esse indivíduo. Isso normalmente é feito em um laboratório, mas pode ser feito em outros ambientes, como no próprio local de atendimento (point of care).&#xD;
&#xD;
Este arquétipo se destina a cobrir o resultado de uma única investigação solicitada, onde a(s) amostra(s) é(são) coletada(s) como um único procedimento e pode(m) incluir múltiplos resultados de analitos ou outros componentes. Exemplos disso podem incluir 'hemograma completo', que produziria um resultado separado (analito) para a contagem de cada tipo de célula sanguínea, ou 'biópsia renal não neoplásica', que produziria resultados de microscopia, imunohistoquímica e microscopia eletrônica.&#xD;
&#xD;
Este arquétipo foi projetado para ser uma estrutura que normalmente será ampliada com os arquétipos CLUSTER para permitir o registro apropriado de padrões de resultados de testes laboratoriais específicos. Isso inclui, mas não está limitado a, testes de bioquímica, hematologia, imunologia e serviços de transfusão, entre outros e padrões específicos para as solicitações de microbiologia e anatomia patológica. Se os testes ou investigações solicitados não pertencerem comumente a um grupo ou painel nomeado, cada resultado do teste será representado usando instâncias separadas deste arquétipo. Há, no entanto, uma variação considerável na prática real de relatórios/mensagens e esse arquétipo/arquétipos relacionados são projetados para lidar com essa variação.&#xD;
&#xD;
Este arquétipo oferece suporte a várias abordagens para o registro de espécimes, refletindo a prática atual que varia enormemente. Um resultado de teste de laboratório tem um alto grau de alinhamento com um recurso de relatório de diagnóstico HL7 FHIR (HL7 FHIR Diagnostic Report resource).&#xD;
&#xD;
É esperado que uma ou mais instâncias deste arquétipo, ou família de arquétipos, sejam enviadas de volta a um médico solicitante em um documento de relatório de laboratório compreendendo o arquétipo COMPOSITION.report_result, ou semelhante, e outros arquétipos de ENTRY relevantes.&#xD;
&#xD;
O registro de fatores de confusão pode ser inconsistente, geralmente dependendo do laboratório de análise e das informações clínicas enviadas pelo solicitante. Na seção Estado (State) do arquétipo, há um elemento de dados simples de 'Fatores de confusão' que é opcional e pode ser repetido como uma forma de registrar uma variedade de fatores simples que precisam ser explicitados, pois podem influenciar a interpretação dos resultados. Se os fatores de confusão forem mais complexos, pode ser apropriado criar um arquétipo CLUSTER local/compartilhado que pode ser aninhado no SLOT 'Detalhes dos fatores de confusão'.&#xD;
Nota 1: Pré-condições conhecidas ou exigidas, como 'jejum' ou 'Dia 1 do ciclo menstrual', devem ser relatadas no elemento de dados 'Condições de amostragem' no arquétipo CLUSTER.specimen, contido neste arquétipo de OBSERVAÇÃO (OBSERVATION).&#xD;
Nota 2: Problemas conhecidos com a coleta ou manuseio de amostras, como 'amostra hemolisada' ou 'uso prolongado de torniquete', devem ser relatados em 'Qualidade da amostra' no arquétipo de CLUSTER.specimen, contido neste arquétipo de OBSERVAÇÃO (OBSERVATION).&#xD;
&#xD;
Onde 'testes de reflexo' são realizados pelo laboratório, eles podem ser realizados de acordo com a orientação dos US/FHIR (consulte https://www.hl7.org/fhir/2015may/uslabreport-guide.html) ou outra política local. Por exemplo, um dos seguintes ...&#xD;
1. Registre os resultados adicionais do teste de reflexo nos 'Resultados do teste' dentro do mesmo 'openEHR-EHR-OBSERVATION.laboratory_test_result'&#xD;
2. Registre os resultados do teste de reflexo como 'Resultados do teste' em um novo 'openEHR-EHR-OBSERVATION.laboratory_test_result', mas referencie à solicitação de teste de laboratório original em 'Detalhes da solicitação de teste'.&#xD;
3. Registre os resultados do teste de reflexo como 'Resultados do teste' em um novo 'openEHR-EHR-OBSERVATION.laboratory_test_result', mas referencie uma nova solicitação de teste de laboratório, bem como a solicitação de teste de laboratório original por meio de 'Detalhes da solicitação de teste'.</use>
      <misuse>Não deve ser usado para registrar uma Autópsia ou Relatório Forense, embora os testes em alguns espécimes que são tirados em tais situações possam ser representados usando este arquétipo. Para estes fins, arquétipos adicionais ou especializados serão necessários.&#xD;
&#xD;
Este arquétipo é adequado para representação de resultados de testes laboratoriais gerais, mas não se destina a cobrir relatórios sinópticos completos. Para representar estes dados, arquétipos especializados adicionais são necessários.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ar-sy</code_string>
      </language>
      <purpose>لتسجيل نتيجة اختبار المعمل, و التي قد يتم استخدامها لتسجيل اختبار ذي قيمة واحدة, و عادة ما يتم بعد ذلك المزيد من التخصيص أو الوضع في قالب لتمثيل اختبار متعدد القيم أو رتل من الاختبارات.&#xD;
و يمثل هذا النموذج كوالد (أب) للتخصيصات الأخرى لاختبارات معملية أكثر تحديدا مثل الميكروبيولوجيا و الهيستوباثولوجيا.</purpose>
      <keywords>المعمل - المختبر</keywords>
      <keywords>الباثولوجيا - المرضية</keywords>
      <keywords>الكيمياء الحيوية</keywords>
      <keywords>الدمويات</keywords>
      <keywords>الميكروبيولوجيا</keywords>
      <keywords>المناعيات - علم المناعة</keywords>
      <use>قد يستخدم لتسجيل نتيجة اختبار المعمل, و التي قد يتم استخدامها لتسجيل اختبار ذي قيمة واحدة, و عادة ما يتم بعد ذلك المزيد من التخصيص أو الوضع في قالب لتمثيل اختبار متعدد القيم أو رتل من الاختبارات.&#xD;
&#xD;
يتم بعد ذلك تقديم التقرير للطبيب السريري الذي قام بطلب الاختبار في سياق تقرير معملي متكامل.</use>
      <misuse>قد تكون التخصيصات أكثر مناسبة للتقارير المركبة مثل حالات الميكروبيولوجيا أو الهيستوباثولوجيا.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>en</code_string>
      </language>
      <purpose>To record the result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual.</purpose>
      <keywords>lab</keywords>
      <keywords>pathology</keywords>
      <keywords>biochemistry</keywords>
      <keywords>haematology</keywords>
      <keywords>microbiology</keywords>
      <keywords>immunology</keywords>
      <keywords>laboratory</keywords>
      <keywords>anatomical</keywords>
      <keywords>chemical</keywords>
      <keywords>clinical</keywords>
      <keywords>immunopathology</keywords>
      <keywords>cytology</keywords>
      <keywords>histopathology</keywords>
      <keywords>test</keywords>
      <keywords>biopsy</keywords>
      <keywords>specimen</keywords>
      <keywords>forensic</keywords>
      <keywords>genetic</keywords>
      <keywords>laboratory medicine</keywords>
      <keywords>results</keywords>
      <keywords>analysis</keywords>
      <use>Use to record the result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. This is typically done in a laboratory, but may be done in other environments such as at the point of care.&#xD;
&#xD;
This archetype is intended to cover the result of a single ordered investigation where the specimen(s) are collected as a single procedure, and may include multiple analyte results or other components. Examples of this could include 'Full blood count', which would yield a separate analyte result for the count of each type of blood cell, or 'kidney biopsy non-neoplastic', which would yield findings from microscopy, immunohistochemistry and electron microscopy.&#xD;
&#xD;
This archetype has been designed to be a framework that will usually be extended with CLUSTER archetypes to enable appropriate recording of specific laboratory test result patterns. This includes, but is not limited to, tests for biochemistry, haematology, immunology and transfusion services etc and specific patterns for the unique requirements for microbiology and anatomical pathology. If the ordered tests or investigations do not commonly belong together in a named group or panel, each test result would normally be represented using separate instances of this archetype. There is, however, considerable variation in actual reporting/messaging practice and this archetype/related archetypes are designed to handle such variation.&#xD;
&#xD;
This archetype supports multiple approaches to recording of specimen, reflecting current practice which varies enormously. A Laboratory test result has a high degree of alignment to an HL7 FHIR Diagnostic Report resource.&#xD;
&#xD;
It is anticipated that one or more instances of this archetype, or archetype family, will be sent back to a requesting clinician within a laboratory report document comprising COMPOSITION.report_result archetype, or similar, and other relevant ENTRY archetypes.&#xD;
&#xD;
The recording of confounding factors may be inconsistent, often depending on the analysing laboratory and on clinical information sent by the requester. In the State section of the archetype there is a simple 'Confounding factors' data element that is optional and can be repeated as one way to record a variety of simple factors that need to be made explicit as they may influence interpretation of the results. If the confounding factors are more complex, it may be appropriate to create a local/shared CLUSTER archetype that can be nested in the 'Confounding factors details' SLOT. &#xD;
Note 1: Known or required pre-conditions, such as 'fasting' or 'Day 1 of menstrual cycle', should be reported in the 'Sampling conditions' data element in the CLUSTER.specimen archetype, nested within this OBSERVATION archetype.&#xD;
Note 2: Known issues with specimen collection or handling, such as 'sample haemolysed' or 'prolonged use of tourniquet' should be reported within 'Specimen quality' in the CLUSTER.specimen archetype, nested within this OBSERVATION archetype.&#xD;
&#xD;
Where 'reflex tests' are performed by the laboratory, these may be handled as per US/FHIR guidance (see https://www.hl7.org/fhir/2015may/uslabreport-guide.html) or other local policy. For example, one of the following ...&#xD;
1. Record the reflex test results additional 'Test findings' within the same 'openEHR-EHR-OBSERVATION.laboratory_test_result'&#xD;
2. Record the reflex test results as 'Test findings' within a new 'openEHR-EHR-OBSERVATION.laboratory_test_result' but refer to the original lab test request via 'Test request details'.&#xD;
3. Record the reflex test results as 'Test findings' within a new 'openEHR-EHR-OBSERVATION.laboratory_test_result' but reference a new lab test request as well as the original lab test request via 'Test request details'.</use>
      <misuse>Not to be used to record an Autopsy or a Forensic report, although tests on some specimens that are taken in such situations may be represented using this archetype. For these, additional or specialised archetypes will be required to represent the data.&#xD;
&#xD;
This archetype is suitable for representation of general laboratory test results, but not intended to cover full synoptic reports. For these, additional specialising archetypes are required to represent the data.</misuse>
      <copyright>© openEHR Foundation</copyright>
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>it</code_string>
      </language>
      <purpose>Registrare il risultato, compresi i riscontri e l'interpretazione del laboratorio, di un'indagine effettuata su campioni raccolti su un individuo o relativi a quell'individuo.</purpose>
      <keywords>lab, patologia, biochimica, ematologia, microbiologia, immunologia, laboratorio, anatomia, chimica, clinica, immunopatologia, citologia, istopatologia, test, biopsia, campione, medicina legale, genetica, medicina di laboratorio, risultati, analisi</keywords>
      <use>Utilizzato per registrare il risultato, compresi i riscontri e l'interpretazione del laboratorio, di un'indagine effettuata su campioni raccolti su un individuo o relativi a quell'individuo. Questo è tipicamente fatto in un laboratorio, ma può essere fatto in altri ambienti, come ad esempio al punto di cura.&#xD;
&#xD;
Questo archetipo è inteso per coprire il risultato di una singola indagine ordinata in cui il campione o i campioni sono raccolti come un'unica procedura, e può includere risultati di analiti multipli o altri componenti. Esempi di ciò potrebbero includere l' "emocromo completo", che darebbe un risultato dell'analisi separato per il conteggio di ciascun tipo di cellula del sangue, o la "biopsia renale non neoplastica", che darebbe risultati da microscopia, immunoistochimica e microscopia elettronica.&#xD;
&#xD;
Questo archetipo è stato progettato per essere un quadro di riferimento che di solito viene esteso con archetipi CLUSTER per consentire la registrazione appropriata di specifici modelli di risultati di test di laboratorio. Questo include, ma non si limita ai test per la biochimica, l'ematologia, l'immunologia e i servizi trasfusionali, ecc. e pattern specifici per i requisiti specializzati per microbiologia e anatomia patologica. Se i test o le indagini ordinati non appartengono comunemente a un gruppo o a un panel, ogni risultato di test verrebbe normalmente rappresentato utilizzando istanze separate di questo archetipo. Vi è, tuttavia, una notevole variazione nella pratica effettiva di refertazione/comunicazione e questo archetipo e gli archetipi correlati sono progettati per gestire tale variazione.&#xD;
&#xD;
Questo archetipo supporta approcci multipli alla registrazione dei campioni, riflettendo la pratica corrente che varia enormemente. Il risultato di un test di laboratorio ha un alto grado di allineamento con la risorsa HL7 FHIR Diagnostic Report.&#xD;
&#xD;
Si prevede che una o più istanze di questo archetipo, o famiglia di archetipi, saranno inviate ad un clinico richiedente all'interno di un documento di rapporto di laboratorio che comprende l'archetipo COMPOSITION.report_result, o simile, e altri archetipi ENTRY rilevanti.&#xD;
&#xD;
La registrazione dei fattori di confusione può essere incoerente, spesso a seconda del laboratorio di analisi e delle informazioni cliniche inviate dal richiedente. Nella sezione Stato dell'archetipo c'è un semplice elemento ("fattori di confondimento"), che è facoltativo e può essere ripetuto come un modo per registrare una varietà di semplici fattori che devono essere resi espliciti in quanto possono influenzare l'interpretazione dei risultati. Se i fattori confondenti sono più complessi, può essere opportuno creare un archetipo CLUSTER locale o condiviso, che può essere annidato nello SLOT "Dettagli dei fattori confondenti".&#xD;
Nota 1: Le precondizioni conosciute o richieste, come il 'digiuno' o il 'Giorno 1 del ciclo mestruale', devono essere riportate nell'elemento di dati 'Condizioni di campionamento' dell'archetipo CLUSTER.specimen, annidato all'interno di questo archetipo OSSERVAZIONE.&#xD;
Nota 2: I problemi noti relativi alla raccolta o al trattamento dei campioni, come "emolisi del campione" o "uso prolungato del laccio emostatico", devono essere riportati in "Qualità del campione" nell'archetipo CLUSTER.specimen, annidato all'interno di questo archetipo OBSERVATION.&#xD;
&#xD;
Se i "reflex test" vengono eseguiti dal laboratorio, questi possono essere gestiti secondo le linee guida US/FHIR (vedi https://www.hl7.org/fhir/2015may/uslabreport-guide.html) o altre politiche locali. Ad esempio, uno dei seguenti ...&#xD;
1. Registrare i risultati addizionali dei reflex test come 'Risultati dei test' all'interno dello stesso 'openEHR-EHR-OBSERVATION.laboratory_test_result'.&#xD;
2. 2. Registrare i risultati del reflex test come 'Risultati del test' all'interno di un nuovo 'openEHR-EHR-OBSERVATION.laboratory_test_result', ma fare riferimento alla richiesta originale del test di laboratorio tramite 'Dettagli della richiesta di test'.&#xD;
3. 3. Registrare i risultati del reflex test come 'Risultati del test' all'interno di un nuovo 'openEHR-EHR-OBSERVATION.laboratory_test_result', ma fare riferimento alla nuova richiesta di test di laboratorio insieme alla richiesta originale di test di laboratorio tramite 'Dettagli della richiesta di test'.</use>
      <misuse>Da non utilizzare per registrare un'autopsia o un rapporto forense, anche se i test su alcuni campioni prelevati in tali situazioni possono essere rappresentati utilizzando questo archetipo. Per questi, saranno necessari archetipi aggiuntivi o specializzati per rappresentare i dati.&#xD;
&#xD;
Questo archetipo è adatto per la rappresentazione dei risultati generali dei test di laboratorio, ma non è destinato a coprire i rapporti sinottici completi. Per questi, sono necessari ulteriori archetipi specializzati per rappresentare i dati.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>fr</code_string>
      </language>
      <purpose>Pour enregistrer les résultats, y compris les conclusions et l'interprétation du laboratoire, d'un examen réalisé sur des échantillons prélevés sur une personne ou liés à celle-ci.</purpose>
      <keywords>labo</keywords>
      <keywords>pathologie</keywords>
      <keywords>biochimie</keywords>
      <keywords>hématologie</keywords>
      <keywords>microbiologie</keywords>
      <keywords>immunologie</keywords>
      <keywords>laboratoire</keywords>
      <keywords>anatomique</keywords>
      <keywords>chimique</keywords>
      <keywords>clinique</keywords>
      <keywords>immunopathologie</keywords>
      <keywords>cytologie</keywords>
      <keywords>histopathologie</keywords>
      <keywords>test</keywords>
      <keywords>biopsie</keywords>
      <keywords>échantillon</keywords>
      <keywords>médico-légal</keywords>
      <keywords>génétique</keywords>
      <keywords>médecine de laboratoire</keywords>
      <keywords>résultats</keywords>
      <keywords>analyse</keywords>
      <use>À utiliser pour enregistrer le résultat, y compris les conclusions et l’interprétation du laboratoire, d’un examen réalisé sur des échantillons prélevés sur un individu ou liés à celui-ci. Cet examen est généralement effectué en laboratoire, mais peut également l’être dans d’autres environnements, tels que le lieu de soins.&#xD;
&#xD;
Cet archétype est destiné à couvrir le résultat d’un examen prescrit unique, pour lequel le ou les échantillons sont prélevés au cours d’une seule procédure, et peut inclure plusieurs résultats d’analytes ou d’autres éléments. On peut citer comme exemples la « Formule sanguine complète », qui donne un résultat distinct pour chaque type de cellule sanguine, ou la « biopsie rénale non néoplasique », qui fournit des résultats issus de l’examen microscopique, de l’immunohistochimie et de la microscopie électronique.&#xD;
&#xD;
Cet archétype a été conçu comme un cadre qui sera généralement étendu à l’aide d’archétypes CLUSTER afin de permettre l’enregistrement approprié de modèles spécifiques de résultats d’analyses de laboratoire. Cela inclut, sans s’y limiter, les examens de biochimie, d’hématologie, d’immunologie et des services de transfusion, etc., ainsi que des modèles spécifiques répondant aux exigences particulières de la microbiologie et de l’anatomopathologie. Si les examens ou analyses prescrits ne sont généralement pas regroupés au sein d’un groupe ou d’un panel nommé, chaque résultat d’examen serait normalement représenté à l’aide d’instances distinctes de cet archétype. Il existe toutefois une grande variabilité dans les pratiques réelles de rapport et de messagerie, et cet archétype ainsi que les archétypes associés sont conçus pour gérer cette variabilité.&#xD;
&#xD;
Cet archétype prend en charge plusieurs approches pour enregistrer les échantillons, reflétant ainsi les pratiques actuelles qui varient considérablement. Un résultat d’analyse de laboratoire présente un haut degré d’alignement avec la ressource « Diagnostic Report » de HL7 FHIR.&#xD;
&#xD;
Il est prévu qu’une ou plusieurs instances de cet archétype, ou de cette famille d’archétypes, seront renvoyées au clinicien demandeur dans un document de rapport de laboratoire comprenant l’archétype COMPOSITION.report_result, ou similaire, ainsi que d’autres archétypes de type ENTRY pertinents.&#xD;
&#xD;
L’enregistrement des facteurs de confusion peut manquer de cohérence, dépendant souvent du laboratoire d’analyse et des informations cliniques transmises par le demandeur. Dans la section « State » de l’archétype, il existe un élément de données simple intitulé « Facteurs de confusion », qui est facultatif et peut être répété afin d’enregistrer divers facteurs simples devant être explicitement mentionnés, s'ils sont susceptibles d’influencer l’interprétation des résultats. Si les facteurs de confusion sont plus complexes, il peut être approprié de créer un archétype CLUSTER local ou partagé pouvant être imbriqué dans le slot « Détails des facteurs de confusion ». &#xD;
Remarque 1 : Les conditions préalables connues ou requises, telles que « à jeun » ou « 1er jour du cycle menstruel », doivent être indiquées dans l’élément de données « Conditions de prélèvement » de l’archétype CLUSTER.specimen, imbriqué dans le présent archétype OBSERVATION.&#xD;
Remarque 2 : Les problèmes connus liés au prélèvement ou à la manipulation de l’échantillon, tels que « échantillon hémolysé » ou « utilisation prolongée du garrot », doivent être signalés dans la section « Problèmes de qualité de l'échantillon » de l’archétype CLUSTER.specimen, imbriqué dans cet archétype OBSERVATION.&#xD;
&#xD;
Lorsque des « tests réflexes » sont effectués par le laboratoire, ceux-ci peuvent être traités conformément aux recommandations US/FHIR (voir https://www.hl7.org/fhir/2015may/uslabreport-guide.html) ou à toute autre directive locale. Par exemple, l’une des options suivantes…&#xD;
1. Enregistrer les résultats des tests réflexes dans la section supplémentaire « Résultats des tests » au sein du même « openEHR-EHR-OBSERVATION.laboratory_test_result »&#xD;
2. Enregistrer les résultats des tests réflexes en tant que « Résultats des tests » dans un nouvel « openEHR-EHR-OBSERVATION.laboratory_test_result », mais faire référence à la demande d’analyse de laboratoire d’origine via « Détails de la demande d’analyse ».&#xD;
3. Enregistrer les résultats des tests de réflexion en tant que « Résultats des tests » dans un nouvel élément « openEHR-EHR-OBSERVATION.laboratory_test_result », mais faire référence à une nouvelle demande d’analyse de laboratoire ainsi qu’à la demande d’analyse de laboratoire d’origine via les « Détails de la demande d’analyse ».</use>
      <misuse>À ne pas utiliser pour enregister un rapport d’autopsie ou un rapport médico-légal, bien que les analyses portant sur certains échantillons prélevés dans de telles situations puissent être représentées à l’aide de cet archétype. Dans ces cas, des archétypes supplémentaires ou spécialisés seront nécessaires pour représenter les données.&#xD;
&#xD;
Cet archétype convient à la représentation des résultats d’analyses de laboratoire générales, mais n’est pas destiné à couvrir l’intégralité des rapports synoptiques. Pour ces derniers, des archétypes spécialisés supplémentaires sont nécessaires pour représenter les données.</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>
      <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>
      <keywords>报告项目</keywords>
      <keywords>活组织检查</keywords>
      <keywords>活检</keywords>
      <keywords>标本</keywords>
      <keywords>样本</keywords>
      <keywords>样品</keywords>
      <keywords>试样</keywords>
      <keywords>法医学</keywords>
      <keywords>遗传学</keywords>
      <keywords>结果</keywords>
      <keywords>分析</keywords>
      <use>旨在用于记录对于从个人身上所采集的标本或者与该个人相关的标本进行检验的结果，包括结果所见/发现和实验室的解释。通常会在实验室中完成此项工作，但也可能会在其他环境下完成，如床旁一线。&#xD;
&#xD;
本原始型旨在涵盖医嘱/申请所开立的单个检验项目的结果，其中采用的是单项操作所采集的标本（一份或多份），并且还可能包括多项分析物结果或若干其他的成分/组成部分。此类的例子可能包括“全血细胞计数”，其中会分别产生关于每种类型血细胞计数的，单独的分析物结果；又如“非肿瘤肾活检”，其中可能会产生显微镜检查、免疫组织化学检查和电子显微镜检查的结果。&#xD;
&#xD;
本原始型在设计上已经成为一种框架，通常会借助于群簇型原始型（CLUSTER）对其加以扩展，以便能够恰当地记录特定的实验室检验结果模式。其中包括但不仅限于生物化学、血液学、免疫学和输血服务等方面的检验项目，以及针对微生物学和解剖病理学方面独特要求的特定模式。如果医嘱/申请所开立的检验项目通常并不属于具名的组合或组套，正常情况下则利用本原始型的单独实例来表达每项检验结果。不过，实际的报告/消息传递实践存在着相当大的差异，而本原始型及其相关的原始型则正是旨在应对此类的变化。&#xD;
&#xD;
本原始型可支持多种的标本记录方法，反映了当前差异巨大的实践。实验室检验结果与 HL7 FHIR 诊断报告资源高度一致。&#xD;
&#xD;
预计一般会将本原始型或原始型家族的一个或多个实例包含在由组合式文书型报告结果原始型（COMPOSITION.report_result）或类似的原始型以及若干其他相关的条目型原始型（ENTRY）所构成的实验室检验报告文档之中，回报给作为申请方的临床医生。&#xD;
&#xD;
混杂因素的记录可能会缺乏一致性，且通常取决于分析实验室，以及申请方所发送的临床信息。在本原始型的状态（State） 之中，有一个简单的可选型混杂因素数据元“Confounding factors”，可以将其重复用作记录各种需要予以明确的简单因素的一种方式，因为这些因素可能会影响对于结果的解释。如果混杂因素较为复杂，则可能适合创建一个可以嵌套在混杂因素详细信息槽位“Confounding factors details”之中的本地/共享性群簇型原始型。&#xD;
&#xD;
注 1：对于已知或必需的前提条件，如“禁食”或“月经周期的第1天”，应当将其嵌套在这个观察型原始型之中的群簇型标本原始型（CLUSTER.specimen）里的采样条件数据元“Sampling conditions”中加以报告。&#xD;
&#xD;
注 2：对于标本采集或处理方面的已知问题，如“标本溶血”或“止血带使用时间过长”，应当将其嵌套在这个观察型原始型之中的群簇型标本原始型（CLUSTER.specimen）里的标本质量数据元“Specimen quality”中加以报告。&#xD;
&#xD;
如果实验室进行的是“伺机追加型检验项目”（reflex tests），则可以根据美国基于 FHIR 的检验报告指南（参见 https://www.hl7.org/fhir/2015may/uslabreport-guide.html）或其他当地政策来进行处理，如下列情况之一：&#xD;
&#xD;
1. 在同一个观察型实验室检验结果原始型“openEHR-EHR-OBSERVATION.laboratory_test_result”当中将若干的伺机追加型检验项目结果记录为额外的“检验结果所见/发现”&#xD;
2. 将若干的伺机追加型检验项目结果记录为新的观察型实验室检验结果原始型“openEHR-EHR-OBSERVATION.laboratory_test_result”之中的“检验结果所见/发现”，而同时又利用检验项目申请详情槽位“Test request details”来引用原始的实验室检验申请。&#xD;
3. 将若干的伺机追加型检验项目结果记录为新的观察型实验室检验结果原始型“openEHR-EHR-OBSERVATION.laboratory_test_result”之中的“检验结果所见/发现”，而同时又利用检验项目申请详情槽位“Test request details”来引用新的实验室检验项目申请以及原始的实验室检验申请。</use>
      <misuse>并非旨在用于记录尸检或法医报告，尽管在这种情况下可以采用本原始型来表达针对某些标本的检验项目。对于此类的项目，将需要额外的或专门的原始型来表达相应的数据。&#xD;
&#xD;
本原始型适用于表示一般实验室检验结果，但并非旨在用于涵盖/表达完整的概要报告（synoptic report）。对于此类的情况，将需要额外的或专门的原始型来表达相应的数据。</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>es</code_string>
      </language>
      <purpose>Registrar el resultado, incluidas las conclusiones y la interpretación del laboratorio, de una investigación realizada con muestras recogidas de un individuo o relacionadas con él.</purpose>
      <keywords>laboratorio</keywords>
      <keywords>patología</keywords>
      <keywords>bioquímica</keywords>
      <keywords>hematología</keywords>
      <keywords>microbiología</keywords>
      <keywords>inmunología</keywords>
      <keywords>anatómico</keywords>
      <keywords>químico</keywords>
      <keywords>clínico</keywords>
      <keywords>inmunopatología</keywords>
      <keywords>citología</keywords>
      <keywords>histopatología</keywords>
      <keywords>prueba</keywords>
      <keywords>biopsia</keywords>
      <keywords>muestra</keywords>
      <keywords>forense</keywords>
      <keywords>genético</keywords>
      <keywords>medicina de laboratorio</keywords>
      <keywords>resultados</keywords>
      <keywords>análisis</keywords>
      <use>Se utiliza para registrar el resultado, incluidos los hallazgos y la interpretación del laboratorio, de una investigación realizada en muestras recolectadas de un individuo o relacionadas con ese individuo. Esto normalmente se hace en un laboratorio, pero se puede hacer en otros entornos, como en el lugar de atención.&#xD;
&#xD;
Este arquetipo pretende cubrir el resultado de una única investigación ordenada en la que las muestras se recogen como un único procedimiento y puede incluir múltiples resultados de analitos u otros componentes. Ejemplos de esto podrían incluir un "conteo sanguíneo completo", que arrojaría un resultado de analito separado para el recuento de cada tipo de célula sanguínea, o una "biopsia renal no neoplásica", que arrojaría resultados mediante microscopía, inmunohistoquímica y microscopía electrónica.&#xD;
&#xD;
Este arquetipo ha sido diseñado para ser un borrador que generalmente se irá ampliando con arquetipos CLUSTER para permitir el registro apropiado de patrones de resultados de pruebas de laboratorio específicos. Esto incluye, entre otros, pruebas de bioquímica, hematología, inmunología y servicios de transfusión, etc., y patrones específicos para los requisitos únicos de microbiología y anatomía patológica. Si las pruebas o investigaciones solicitadas no están englobadas en ningún grupo, cada resultado de la prueba normalmente se representaría utilizando instancias separadas de este arquetipo. Sin embargo, existe una variación considerable en la práctica real de informes/mensajería y este arquetipo/arquetipos relacionados están diseñados para manejar dicha variación.&#xD;
&#xD;
Este arquetipo admite múltiples enfoques para el registro de muestras, lo que refleja la práctica actual que varía enormemente. El resultado de una prueba de laboratorio tiene un alto grado de alineación con un recurso de Informe de diagnóstico HL7 FHIR.&#xD;
&#xD;
Se prevé que una o más instancias de este arquetipo, o familia de arquetipos, se enviarán de vuelta al médico solicitante dentro de un documento de informe de laboratorio que comprenda el arquetipo COMPOSITION.report_result, o similar, y otros arquetipos ENTRY relevantes.&#xD;
&#xD;
El registro de factores de confusión puede ser inconsistente, dependiendo a menudo del laboratorio analizador y de la información clínica enviada por el solicitante. En la sección Estado del arquetipo hay un elemento de datos simple de 'Factores de confusión', que es opcional y puede repetirse como una forma de registrar una variedad de factores simples que deben hacerse explícitos, ya que pueden influir en la interpretación de los resultados. Si los factores de confusión son más complejos, puede ser apropiado crear un arquetipo de tipo CLUSTER local/compartido, que pueda anidarse en el SLOT 'Detalles de los factores de confusión'.&#xD;
Nota 1: Las condiciones previas conocidas o requeridas, como "ayuno" o "Día 1 del ciclo menstrual", deben informarse en el elemento de datos "Condiciones de muestreo" en el arquetipo CLUSTER.specimen, anidado dentro de este arquetipo OBSERVATION.&#xD;
Nota 2: Los problemas conocidos con la recolección o manipulación de muestras, como "muestra hemolizada" o "uso prolongado de torniquete", deben informarse en "Calidad de la muestra" en el arquetipo CLUSTER.specimen, anidado dentro de este arquetipo OBSERVATION.&#xD;
&#xD;
Cuando el laboratorio realiza "pruebas de reflejos", estas pueden manejarse según la guía US/FHIR (consulte https://www.hl7.org/fhir/2015may/uslabreport-guide.html) u otra política local. Por ejemplo, uno de los siguientes...&#xD;
1. Registre los resultados de la prueba reflejo adicional 'Resultados de la prueba' dentro del mismo 'openEHR-EHR-OBSERVATION.laboratory_test_result'&#xD;
2. Registre los resultados de la prueba reflejo, tales como 'Resultados de la prueba', dentro de un nuevo 'openEHR-EHR-OBSERVATION.laboratory_test_result' pero consulte la solicitud de prueba de laboratorio original a través de 'Detalles de la solicitud de prueba'.&#xD;
3. Registre los resultados de la prueba reflejo, tales como como 'Resultados de la prueba' dentro de un nuevo 'openEHR-EHR-OBSERVATION.laboratory_test_result' pero haga referencia a una nueva solicitud de prueba de laboratorio, así como a la solicitud de prueba de laboratorio original a través de 'Detalles de la solicitud de prueba'.</use>
      <misuse>No debe utilizarse para registrar una autopsia o un informe forense, aunque las pruebas de algunas muestras que se toman en tales situaciones pueden representarse utilizando este arquetipo. En estos casos, se necesitarán arquetipos adicionales o especializados para representar los datos.&#xD;
&#xD;
Este arquetipo es adecuado para la representación de resultados generales de pruebas de laboratorio, pero no pretende abarcar informes sinópticos completos. En estos casos, se necesitarán arquetipos especializados adicionales para representar los datos.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nb</code_string>
      </language>
      <purpose>For å registrere resultat, funn og laboratoriets tolkning, av en laboratorieundersøkelse utført på prøvemateriale fra et individ eller relatert til individet.</purpose>
      <keywords>medisinsk biokjemi</keywords>
      <keywords>medisinsk mikrobiologi</keywords>
      <keywords>medisinsk genetikk</keywords>
      <keywords>klinisk farmakologi</keywords>
      <keywords>patologi</keywords>
      <keywords>immunologi og transfusjonsmedisin</keywords>
      <keywords>laboratorie</keywords>
      <keywords>lab</keywords>
      <keywords>anatomisk</keywords>
      <keywords>prøve</keywords>
      <keywords>rettsmedisinsk</keywords>
      <keywords>laboratoriemedisin</keywords>
      <keywords>generell kjemi</keywords>
      <keywords>materiale</keywords>
      <keywords>prøvemateriale</keywords>
      <keywords>lokalisasjon</keywords>
      <keywords>undersøkelse</keywords>
      <keywords>analyse</keywords>
      <keywords>metode (analysemetode)</keywords>
      <keywords>laboratoriespesialitet</keywords>
      <keywords>blodprøve</keywords>
      <keywords>serum</keywords>
      <keywords>plasma</keywords>
      <keywords>fullblod</keywords>
      <keywords>analytt</keywords>
      <keywords>kapillærprøver</keywords>
      <keywords>venøse prøver</keywords>
      <keywords>arterielle prøver</keywords>
      <keywords>prøvetaking</keywords>
      <keywords>immunopatologi</keywords>
      <keywords>cytologi</keywords>
      <keywords>histopatologi</keywords>
      <keywords>biopsi</keywords>
      <keywords>preparat</keywords>
      <keywords>immunhistokjemi</keywords>
      <keywords>immuncytokjemi</keywords>
      <keywords>molekylærgenetiske analyser</keywords>
      <keywords>histologi</keywords>
      <keywords>cytologi</keywords>
      <keywords>cervixcytologi</keywords>
      <keywords>obduksjon</keywords>
      <keywords>flowcytometri</keywords>
      <keywords>molekylær patologi</keywords>
      <keywords>elektronmikroskopi</keywords>
      <keywords>neuropatologi</keywords>
      <keywords>frysesnitt</keywords>
      <keywords>punksjonscytologi</keywords>
      <keywords>makrobeskjæring</keywords>
      <keywords>makroskopisk undersøkelse</keywords>
      <keywords>mikrobiologi</keywords>
      <keywords>bakteriologi</keywords>
      <keywords>virologi</keywords>
      <keywords>serologi</keywords>
      <keywords>molekylærdiagnostikk</keywords>
      <keywords>parasittologi</keywords>
      <keywords>mykologi</keywords>
      <keywords>protozologi</keywords>
      <keywords>immunologi</keywords>
      <keywords>medisinsk immunologi</keywords>
      <keywords>transfusjonsmedisin</keywords>
      <keywords>immunhematologi</keywords>
      <keywords>transplantasjonsimmunologi</keywords>
      <keywords>cellulær immunologi</keywords>
      <keywords>ex vivo cellelaboratorium</keywords>
      <keywords>hormonanalyser</keywords>
      <keywords>endokrinologi</keywords>
      <keywords>blodbank</keywords>
      <keywords>blodkomponenter</keywords>
      <keywords>hematologi</keywords>
      <keywords>kjemisk</keywords>
      <keywords>klinisk</keywords>
      <keywords>kjemi</keywords>
      <keywords>klinisk kjemi</keywords>
      <keywords>klinisk biokjemi</keywords>
      <keywords>metabolsk molekylærbiologi</keywords>
      <keywords>homeostase og trombose</keywords>
      <keywords>koagulasjon</keywords>
      <keywords>klinisk farmakologi</keywords>
      <keywords>farmakologi</keywords>
      <keywords>doping analyser</keywords>
      <keywords>klinisk fysiologi</keywords>
      <keywords>toksikologi</keywords>
      <keywords>rusmiddelanalyse</keywords>
      <keywords>misbruksdiagnostikk</keywords>
      <keywords>genetisk</keywords>
      <keywords>genetikk</keywords>
      <keywords>HTS-diagnostikk</keywords>
      <keywords>genpaneler</keywords>
      <keywords>farmakogenetikk</keywords>
      <keywords>cancer cytogenetikk</keywords>
      <keywords>preparat</keywords>
      <keywords>rettsmedisinsk</keywords>
      <use>Brukes for å registrere resultat, funn og laboratoriets tolkning, av en laboratorieundersøkelse utført på prøvemateriale fra et individ eller relatert til individet. Dette utføres typisk i et laboratorium, men kan også gjøres i andre miljøer, som for eksempel ved pasientnær analysering.&#xD;
&#xD;
Denne arketypen er ment å dekke resultatet av én rekvirert undersøkelse der prøvene er tatt i én prosedyre, og som kan ha flere analyseresultater eller andre komponenter. Eksempler på dette kan være "Differensialtelling av leukocytter", som gir et separat resultat for antallet av hver type hvite blodceller, eller "Nyrebiopsi ikke-neoplastisk", som gir resultater fra mikroskopi, immunohistokjemi og elektronmikroskopi.&#xD;
&#xD;
Denne arketypen er laget for å være et rammeverk som vanligvis vil utvides med CLUSTER-arketyper for å få en hensiktsmessig registrering og rapportering av spesifikke mønstre for laboratorieresultater. Dette kan omfatte analyser og undersøkelser innen kjemi (medisinsk biokjemi, hematologi, immunologi og transfusjonsmedisin, med mer), samt spesifikke mønstre for de unike behovene innenfor mikrobiologi og patologi. Hvis de rekvirerte analysene eller undersøkelsene ikke tilhører en navngitt gruppe, vil hvert resultat normalt representeres ved en separat instans av denne arketypen. Imidlertid er det stor variasjon på hvordan svarrapportering/meldingsformidling skjer, og denne arketypen er designet for å ivareta disse variasjonene.&#xD;
&#xD;
Denne arketypen støtter flere tilnærminger til å registrere informasjon om prøvematerialet, noe som reflekterer de store variasjonene innenfor dagens praksis. Laboratoriesvar-arketypen har høy grad av samsvar med HL7 FHIR-ressursen "Diagnostic Report".&#xD;
&#xD;
Det forventes at en eller flere instanser av denne arketypen, eller arketypefamilen vil bli sendt tilbake til rekvirenten i en laboratoriesvarrapport, for eksempel i arketypen COMPOSITION.report_result eller tilsvarende, og sammen med relevante ENTRY-arketyper.&#xD;
&#xD;
Registrering av konfunderende faktorer gjøres i praksis ikke på en konsistent måte, og avhenger av avsenderlaboratoriet og av den kliniske informasjonen som ble sendt med fra rekvirenten. I "State"-delen av arketypen er det et valgfritt og repeterbart element for "Konfunderende faktorer" som kan brukes til å registrere enkle faktorer, som fordi de kan påvirke tolkningen av resultatet må registreres eksplisitt. Dersom de konfunderende faktorene er mer komplekse kan det være hensiktsmessig å lage en CLUSTER-arketype som kan brukes i SLOTet "Strukturerte konfunderende faktorer".&#xD;
NB 1: Kjente eller nødvendige forutsetninger, som for eksempel "fastende" eller "dag 1 av menstruasjonssyklusen" bør registreres i elementet "Prøvetakingsforhold" i arketypen CLUSTER.specimen, og nøstes inn i denne OBSERVATION-arketypen.&#xD;
NB 2: Kjente problemer med prøvetaking eller prøvehåndtering, som for eksempel "hemolyse" eller "forlenget stase" bør registreres i elementet "Prøvekvalitet" i arketypen CLUSTER.specimen, og nøstes inn i denne OBSERVATION-arketypen.&#xD;
&#xD;
Der laboratoriet endrer analyser eller legger til analyser som oppfølging, kan disse håndteres etter veilledning fra HL7 FHIR (https://www.hl7.org/fhir/2015may/uslabreport-guide.html), eller etter lokale prosedyrer. For eksempel en av følgende:&#xD;
1. Registrer de endrede analysene/tilleggsanalysene innenfor samme instans av denne arketypen.&#xD;
2. Registrer de endrede analysene/tilleggsanalysene i en ny instans av denne arketypen, men referer til den opprinnelige rekvisisjonen ved hjelp av "Rekvisisjonsdetaljer".&#xD;
3. Registrer de endrede analysene/tilleggsanalysene i en ny instans av denne arketypen, men referer til en ny rekvisisjon i tillegg til den opprinnelige rekvisisjonen, ved hjelp av "Rekvisisjonsdetaljer".</use>
      <misuse>Skal ikke brukes for å lagre en sammenstilling etter obduksjon eller rettsmedisinsk undersøkelse, selv om prøver av noen prøvematerialer som blir tatt i en obduksjon kan bli representert i denne arketypen. For å lage selve obduksjons- eller den rettsmedisinske rapporten må man bruke spesialiserte arketyper.&#xD;
&#xD;
Denne arketypen er passende for å representere generelle laboratoriesvar, men er ikke ment å dekke komplette sammendragsrapporter ("synoptic reports") innenfor patologi. For disse trengs det i tillegg spesialiserte arketyper.</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>nl</code_string>
      </language>
      <purpose>Voor het vastleggen van de uitslag, inclusief bevindingen en de interpretatie van het laboratorium, van een onderzoek uitgevoerd op een specimen van een individu of gerelateerd aan een individu.</purpose>
      <use>*Use to record the result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. This is typically done in a laboratory, but may be done in other environments such as at the point of care.&#xD;
&#xD;
This archetype is intended to cover the result of a single ordered investigation where the specimen(s) are collected as a single procedure, and may include multiple analyte results or other components. Examples of this could include 'Full blood count', which would yield a separate analyte result for the count of each type of blood cell, or 'kidney biopsy non-neoplastic', which would yield findings from microscopy, immunohistochemistry and electron microscopy.&#xD;
&#xD;
This archetype has been designed to be a framework that will usually be extended with CLUSTER archetypes to enable appropriate recording of specific laboratory test result patterns. This includes, but is not limited to, tests for biochemistry, haematology, immunology and transfusion services etc and specific patterns for the unique requirements for microbiology and anatomical pathology. If the ordered tests or investigations do not commonly belong together in a named group or panel, each test result would normally be represented using separate instances of this archetype. There is, however, considerable variation in actual reporting/messaging practice and this archetype/related archetypes are designed to handle such variation.&#xD;
&#xD;
This archetype supports multiple approaches to recording of specimen, reflecting current practice which varies enormously. A Laboratory test result has a high degree of alignment to an HL7 FHIR Diagnostic Report resource.&#xD;
&#xD;
It is anticipated that one or more instances of this archetype, or archetype family, will be sent back to a requesting clinician within a laboratory report document comprising COMPOSITION.report_result archetype, or similar, and other relevant ENTRY archetypes.&#xD;
&#xD;
The recording of confounding factors may be inconsistent, often depending on the analysing laboratory and on clinical information sent by the requester. In the State section of the archetype there is a simple 'Confounding factors' data element that is optional and can be repeated as one way to record a variety of simple factors that need to be made explicit as they may influence interpretation of the results. If the confounding factors are more complex, it may be appropriate to create a local/shared CLUSTER archetype that can be nested in the 'Confounding factors details' SLOT. &#xD;
Note 1: Known or required pre-conditions, such as 'fasting' or 'Day 1 of menstrual cycle', should be reported in the 'Sampling conditions' data element in the CLUSTER.specimen archetype, nested within this OBSERVATION archetype.&#xD;
Note 2: Known issues with specimen collection or handling, such as 'sample haemolysed' or 'prolonged use of tourniquet' should be reported within 'Specimen quality' in the CLUSTER.specimen archetype, nested within this OBSERVATION archetype.&#xD;
&#xD;
Where 'reflex tests' are performed by the laboratory, these may be handled as per US/FHIR guidance (see https://www.hl7.org/fhir/2015may/uslabreport-guide.html) or other local policy. For example, one of the following ...&#xD;
1. Record the reflex test results additional 'Test findings' within the same 'openEHR-EHR-OBSERVATION.laboratory_test_result'&#xD;
2. Record the reflex test results as 'Test findings' within a new 'openEHR-EHR-OBSERVATION.laboratory_test_result' but refer to the original lab test request via 'Test request details'.&#xD;
3. Record the reflex test results as 'Test findings' within a new 'openEHR-EHR-OBSERVATION.laboratory_test_result' but reference a new lab test request as well as the original lab test request via 'Test request details'.(en)</use>
      <misuse>*Not to be used to record an Autopsy or a Forensic report, although tests on some specimens that are taken in such situations may be represented using this archetype. For these, additional or specialised archetypes will be required to represent the data.&#xD;
&#xD;
This archetype is suitable for representation of general laboratory test results, but not intended to cover full synoptic reports. For these, additional specialising archetypes are required to represent the data.(en)</misuse>
      <copyright />
    </details>
    <details>
      <language>
        <terminology_id>
          <value>ISO_639-1</value>
        </terminology_id>
        <code_string>ca</code_string>
      </language>
      <purpose>Registrar el resultat, incloses les conclusions i la interpretació del laboratori, d'una investigació realitzada amb mostres recollides o relacionades amb un individu.</purpose>
      <keywords>laboratori</keywords>
      <keywords>patologia</keywords>
      <keywords>bioquímica</keywords>
      <keywords>hematologia</keywords>
      <keywords>microbiologia</keywords>
      <keywords>immunologia</keywords>
      <keywords>anatòmic</keywords>
      <keywords>químic</keywords>
      <keywords>clínic</keywords>
      <keywords>immunopatologia</keywords>
      <keywords>citologia</keywords>
      <keywords>histopatologia</keywords>
      <keywords>prova</keywords>
      <keywords>biòpsia</keywords>
      <keywords>mostra</keywords>
      <keywords>forense</keywords>
      <keywords>genètic</keywords>
      <keywords>medicina de laboratori</keywords>
      <keywords>resultats</keywords>
      <keywords>anàlisi</keywords>
      <use>S'utilitza per registrar el resultat, incloses les troballes i la interpretació del laboratori, d'una investigació realitzada en mostres recol·lectades d'un individu o relacionades amb aquest individu. Això normalment es fa en un laboratori, però es pot fer en altres entorns, com ara el lloc d'atenció.&#xD;
&#xD;
Aquest arquetip pretén cobrir el resultat d'una única investigació ordenada on les mostres es recullen com un únic procediment i pot incloure múltiples resultats d'analits o altres components. Exemples d'això podrien incloure un "compte sanguini complet", que donaria un resultat d'anàlit separat per al recompte de cada tipus de cèl·lula sanguínia, o una "biòpsia renal no neoplàsica", que donaria resultats mitjançant microscòpia, immunohistoquímica i microscòpia electrònica.&#xD;
&#xD;
Aquest arquetip ha estat dissenyat per ser un esborrany que generalment s'anirà ampliant amb arquetips CLUSTER per permetre el registre apropiat de patrons de resultats de proves de laboratori específics. Això inclou, entre d'altres, proves de bioquímica, hematologia, immunologia i serveis de transfusió, etc. i patrons específics per als requisits únics de microbiologia i anatomia patològica. Si les proves o les investigacions sol·licitades no estan englobades en cap grup, cada resultat de la prova normalment es representaria utilitzant instàncies separades d'aquest arquetip. No obstant això, hi ha una variació considerable a la pràctica real d'informes/missatgeria i aquest arquetip/arquetips relacionats estan dissenyats per manejar aquesta variació.&#xD;
&#xD;
Aquest arquetip admet múltiples enfocaments per al registre de mostres, cosa que reflecteix la pràctica actual que varia enormement. El resultat d‟una prova de laboratori té un alt grau d‟alineació amb un recurs d‟Informe de diagnòstic HL7 FHIR.&#xD;
&#xD;
Es preveu que una o més instàncies d'aquest arquetip o família d'arquetips s'enviaran de tornada al metge sol·licitant dins d'un document d'informe de laboratori que comprengui l'arquetip COMPOSITION.report_result, o similar, i altres arquetips ENTRY rellevants.&#xD;
&#xD;
El registre de factors de confusió pot ser inconsistent, depenent sovint del laboratori analitzador i de la informació clínica enviada pel sol·licitant. A la secció Estat de l'arquetip hi ha un element de dades simple de 'Factors de confusió', que és opcional i es pot repetir com una forma de registrar una varietat de factors simples que s'han de fer explícits, ja que poden influir en la interpretació dels resultats . Si els factors de confusió són més complexos, pot ser apropiat crear un arquetip de tipus CLUSTER local/compartit, que es pugui niar al SLOT 'Detalls dels factors de confusió'.&#xD;
Nota 1: Les condicions prèvies conegudes o requerides, com "dejuni" o "Dia 1 del cicle menstrual", s'han d'informar a l'element de dades "Condicions de mostreig" a l'arquetip CLUSTER.specimen, niat dins d'aquest arquetip OBSERVATION.&#xD;
Nota 2: Els problemes coneguts amb la recol·lecció o manipulació de mostres, com ara "mostra hemolitzada" o "ús prolongat de torniquet", s'han d'informar a "Qualitat de la mostra" a l'arquetip CLUSTER.specimen, niat dins d'aquest arquetip OBSERVATION.&#xD;
&#xD;
Quan el laboratori realitza "proves de reflexos", aquestes es poden manejar segons la guia US/FHIR (consulteu https://www.hl7.org/fhir/2015may/uslabreport-guide.html) o una altra política local. Per exemple, un dels següents...&#xD;
1. Registreu els resultats de la prova reflex addicional 'Resultats de la prova' dins del mateix 'openEHR-EHR-OBSERVATION.laboratory_test_result'&#xD;
2. Registreu els resultats de la prova reflex, com ara 'Resultats de la prova', dins d'un nou 'openEHR-EHR-OBSERVATION.laboratory_test_result' però consulteu la sol·licitud de prova de laboratori original a través de 'Detalls de la sol·licitud de prova'.&#xD;
3. Registreu els resultats de la prova reflex, com ara 'Resultats de la prova' dins d'un nou 'openEHR-EHR-OBSERVATION.laboratory_test_result' però feu referència a una nova sol·licitud de prova de laboratori, així com a la sol·licitud de prova de laboratori original a través de 'Detalls de la sol·licitud de prova'.</use>
      <misuse>No s'ha d'utilitzar per registrar una autòpsia o informe forense, encara que les proves d'algunes mostres que es prenen en aquestes situacions es poden representar utilitzant aquest arquetip. En aquests casos, caldrà arquetips addicionals o especialitzats per representar les dades.&#xD;
&#xD;
Aquest arquetip és adequat per a la representació de resultats generals de proves de laboratori, però no pretén abastar informes sinòptics complets. En aquests casos, caldrà arquetips especialitzats addicionals per representar les dades.</misuse>
      <copyright />
    </details>
  </description>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>de</code_string>
    </language>
    <author id="name">Sarah Ballout</author>
    <author id="organisation">MHH-Hannover</author>
    <author id="email">ballout.sarah@mh-hannover.de</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>sv</code_string>
    </language>
    <author id="name">Linda Aulin, Åsa Skagerhult, Linda Aulin Lundeqvist</author>
    <author id="organisation">Region Stockholm, Region Östergötland, Karolinska University Hospital, Region Stockholm</author>
    <author id="email">linda.aulin@sll.se, linda.aulin@regionstockholm.se, asa.skagerhult@regionostergotland.se, linda.aulin-lundeqvist@regionstockholm.se</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>fi</code_string>
    </language>
    <author id="name">Riikka Lahtela</author>
    <author id="organisation">Istekki</author>
    <author id="email">riikka.lahtela@istekki.fi</author>
    <other_details id="other_contributors">Henri Huttunen, UNA Oy, Finland; Heidi Koikkalainen, FreshEHR</other_details>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nb</code_string>
    </language>
    <author id="name">Vebjørn Arntzen/Silje Ljosland Bakke/Liv Laugen</author>
    <author id="organisation">Oslo universitetssykehus HF/Nasjonal IKT HF/Oslo universitetssykehus, Norway</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>pt-br</code_string>
    </language>
    <author id="name">Vladimir Pizzo</author>
    <author id="organisation">Clínica Parente Pizzo</author>
    <author id="email">vrppizzo@gmail.com</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ar-sy</code_string>
    </language>
    <author id="name">Mona Saleh</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>it</code_string>
    </language>
    <author id="name">Alessandro Sulis/Francesca Frexia/Cecilia Mascia</author>
    <author id="organisation">CRS4 - Center for advanced studies, research and development in Sardinia, Pula (Cagliari), Italy</author>
    <author id="email">alessandro.sulis@crs4.it/francesca.frexia@crs4.it/cecilia.mascia@crs4.it</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>
    <accreditation>N/A</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>nl</code_string>
    </language>
    <author id="name">Joost Holslag</author>
    <author id="organisation">Nedap</author>
    <author id="email">joost.holslag@nedap.com</author>
    <accreditation>MD</accreditation>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>es</code_string>
    </language>
    <author id="name">Julio de Sosa</author>
    <author id="organisation">Servei Català de la Salut</author>
    <author id="email">juliodesosa@catsalut.cat</author>
  </translations>
  <translations>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>ca</code_string>
    </language>
    <author id="name">Julio de Sosa</author>
    <author id="organisation">Servei Català de la Salut</author>
    <author id="email">juliodesosa@catsalut.cat</author>
  </translations>
  <uid>
    <value>90225e36-20a8-403a-8172-77e53b9990b2</value>
  </uid>
  <archetype_id>
    <value>openEHR-EHR-OBSERVATION.laboratory_test_result.v1</value>
  </archetype_id>
  <adl_version>1.4</adl_version>
  <concept>at0000</concept>
  <definition>
    <rm_type_name>OBSERVATION</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>data</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>HISTORY</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>events</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>EVENT</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>at0002</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>data</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>at0003</node_id>
                <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
                  <rm_attribute_name>items</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>0</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0005</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>value</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>0</lower>
                        <upper>1</upper>
                      </existence>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_TEXT</rm_type_name>
                        <occurrences>
                          <lower_included>true</lower_included>
                          <upper_included>true</upper_included>
                          <lower_unbounded>false</lower_unbounded>
                          <upper_unbounded>false</upper_unbounded>
                          <lower>1</lower>
                          <upper>1</upper>
                        </occurrences>
                        <node_id />
                      </children>
                    </attributes>
                  </children>
                  <children xsi:type="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>at0065</node_id>
                    <includes>
                      <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.specimen(-[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\.specimen(-[a-zA-Z0-9_]+)*\.v1</pattern>
                          </item>
                          <reference_type>constraint</reference_type>
                        </right_operand>
                      </expression>
                    </includes>
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>0</lower>
                    </occurrences>
                    <node_id>at0073</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_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>at0107</code_list>
                            <code_list>at0037</code_list>
                            <code_list>at0120</code_list>
                            <code_list>at0038</code_list>
                            <code_list>at0040</code_list>
                            <code_list>at0115</code_list>
                            <code_list>at0119</code_list>
                            <code_list>at0074</code_list>
                            <code_list>at0116</code_list>
                          </children>
                        </attributes>
                      </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>at0075</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>at0077</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>at0100</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>at0097</node_id>
                    <includes>
                      <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.laboratory_test_analyte(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.laboratory_test_panel(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.laboratory_test_panel(-[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\.laboratory_test_analyte(-[a-zA-Z0-9_]+)*\.v1|openEHR-EHR-CLUSTER\.laboratory_test_panel(-[a-zA-Z0-9_]+)*\.v0|openEHR-EHR-CLUSTER\.laboratory_test_panel(-[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>at0057</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>value</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>0</lower>
                        <upper>1</upper>
                      </existence>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_TEXT</rm_type_name>
                        <occurrences>
                          <lower_included>true</lower_included>
                          <upper_included>true</upper_included>
                          <lower_unbounded>false</lower_unbounded>
                          <upper_unbounded>false</upper_unbounded>
                          <lower>1</lower>
                          <upper>1</upper>
                        </occurrences>
                        <node_id />
                      </children>
                    </attributes>
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>0</lower>
                    </occurrences>
                    <node_id>at0098</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>at0122</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="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>at0118</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>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>0</lower>
                    </occurrences>
                    <node_id>at0101</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>value</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>0</lower>
                        <upper>1</upper>
                      </existence>
                      <children xsi:type="C_COMPLEX_OBJECT">
                        <rm_type_name>DV_TEXT</rm_type_name>
                        <occurrences>
                          <lower_included>true</lower_included>
                          <upper_included>true</upper_included>
                          <lower_unbounded>false</lower_unbounded>
                          <upper_unbounded>false</upper_unbounded>
                          <lower>1</lower>
                          <upper>1</upper>
                        </occurrences>
                        <node_id />
                      </children>
                    </attributes>
                  </children>
                  <cardinality>
                    <is_ordered>false</is_ordered>
                    <is_unique>false</is_unique>
                    <interval>
                      <lower_included>true</lower_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>1</lower>
                    </interval>
                  </cardinality>
                </attributes>
              </children>
            </attributes>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>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>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>at0112</node_id>
                <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
                  <rm_attribute_name>items</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>0</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>ELEMENT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>true</upper_unbounded>
                      <lower>0</lower>
                    </occurrences>
                    <node_id>at0113</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>at0114</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>
          </children>
          <cardinality>
            <is_ordered>false</is_ordered>
            <is_unique>false</is_unique>
            <interval>
              <lower_included>true</lower_included>
              <lower_unbounded>false</lower_unbounded>
              <upper_unbounded>true</upper_unbounded>
              <lower>1</lower>
            </interval>
          </cardinality>
        </attributes>
      </children>
    </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>at0004</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="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\.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\.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>at0068</node_id>
            <attributes xsi:type="C_SINGLE_ATTRIBUTE">
              <rm_attribute_name>value</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_IDENTIFIER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>1</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id />
              </children>
            </attributes>
          </children>
          <children xsi:type="C_COMPLEX_OBJECT">
            <rm_type_name>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>at0094</node_id>
            <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
              <rm_attribute_name>items</rm_attribute_name>
              <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>1</lower>
                <upper>1</upper>
              </existence>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>ELEMENT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </occurrences>
                <node_id>at0106</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>at0062</node_id>
                <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>value</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>0</lower>
                    <upper>1</upper>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>DV_IDENTIFIER</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>DV_TEXT</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>1</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id />
                  </children>
                </attributes>
              </children>
              <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>ELEMENT</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0063</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>
                  <upper_included>true</upper_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>false</upper_unbounded>
                  <lower>0</lower>
                  <upper>1</upper>
                </occurrences>
                <node_id>at0090</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
                  <expression xsi:type="EXPR_BINARY_OPERATOR">
                    <type>Boolean</type>
                    <operator>2007</operator>
                    <precedence_overridden>false</precedence_overridden>
                    <left_operand xsi:type="EXPR_LEAF">
                      <type>String</type>
                      <item xsi:type="xsd:string">archetype_id/value</item>
                      <reference_type>attribute</reference_type>
                    </left_operand>
                    <right_operand xsi:type="EXPR_LEAF">
                      <type>C_STRING</type>
                      <item xsi:type="C_STRING">
                        <pattern>openEHR-EHR-CLUSTER\.person(-[a-zA-Z0-9_]+)*\.v1</pattern>
                      </item>
                      <reference_type>constraint</reference_type>
                    </right_operand>
                  </expression>
                </includes>
              </children>
              <children xsi:type="ARCHETYPE_SLOT">
                <rm_type_name>CLUSTER</rm_type_name>
                <occurrences>
                  <lower_included>true</lower_included>
                  <lower_unbounded>false</lower_unbounded>
                  <upper_unbounded>true</upper_unbounded>
                  <lower>0</lower>
                </occurrences>
                <node_id>at0035</node_id>
                <includes>
                  <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.distribution(-[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\.distribution(-[a-zA-Z0-9_]+)*\.v1</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>1</lower>
                </interval>
              </cardinality>
            </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>at0111</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_BOOLEAN</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>at0121</node_id>
          </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>at0110</node_id>
            <includes>
              <string_expression>archetype_id/value matches {/openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1/}</string_expression>
              <expression xsi:type="EXPR_BINARY_OPERATOR">
                <type>Boolean</type>
                <operator>2007</operator>
                <precedence_overridden>false</precedence_overridden>
                <left_operand xsi:type="EXPR_LEAF">
                  <type>String</type>
                  <item xsi:type="xsd:string">archetype_id/value</item>
                  <reference_type>attribute</reference_type>
                </left_operand>
                <right_operand xsi:type="EXPR_LEAF">
                  <type>C_STRING</type>
                  <item xsi:type="C_STRING">
                    <pattern>openEHR-EHR-CLUSTER\.device(-[a-zA-Z0-9_]+)*\.v1</pattern>
                  </item>
                  <reference_type>constraint</reference_type>
                </right_operand>
              </expression>
            </includes>
          </children>
          <children xsi:type="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>at0117</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="ar-sy">
      <items code="at0000">
        <items id="text">*Laboratory test result(en)</items>
        <items id="description">*The result, including findings and interpretation, of a laboratory investigation performed on specimens from individuals or related materials(en)</items>
      </items>
      <items code="at0001">
        <items id="text">*Event Series(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0002">
        <items id="text">إحدى الوقائع</items>
        <items id="description">إحدى الوقائع</items>
      </items>
      <items code="at0003">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0004">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0005">
        <items id="text">*Test name(en)</items>
        <items id="description">*Name of the laboratory investigation performed on the specimen(s). (en)</items>
        <items id="comment">*A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'. (en)</items>
      </items>
      <items code="at0017">
        <items id="text">*Receiving laboratory(en)</items>
        <items id="description">*Details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.(en)</items>
        <items id="comment">*This slot is intended to carry details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.&#xD;
&#xD;
The receiving laboratory may either perform the test or refer it to another laboratory. Where a different laboratory is responsible for performing the testing on specific analytes, it would be expected that these details would be carried in the 'Analyte result detail' SLOT within the CLUSTER.laboratory_test_analyte archetype.&#xD;
&#xD;
 (en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Distribution list(en)</items>
        <items id="description">*Details of additional clinicians or organisations who require a copy of the test result.(en)</items>
        <items id="comment">*The 'Distribution list' is for information-only, and that the primary recipient of the report is the person intended to act on the information.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Partial(en)</items>
        <items id="description">*This is a partial (e.g. initial, interim or preliminary) Test Result: data in the Test Result may be incomplete or unverified.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Final(en)</items>
        <items id="description">*The Test result is complete and verified by an authorised person.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Amended(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist, and result data has been changed.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">*Conclusion(en)</items>
        <items id="description">*Narrative description of the key findings. (en)</items>
        <items id="comment">*For example: 'Pattern suggests significant renal impairment'. The content of the conclusion will vary, depending on the investigation performed. This conclusion should be aligned with the coded 'Test diagnosis'. (en)</items>
        <items id="fhir_mapping">*DiagnosticReport.conclusion(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Requester Order Identifier(en)</items>
        <items id="description">*The local ID assigned to the test order by the order requester.(en)</items>
        <items id="comment">*Equivalent to the HL7 Placer Order Identifier.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Receiver Order Identifier(en)</items>
        <items id="description">*The local ID assigned to the test order by the order filler, usually by the Laboratory Information System (LIS).(en)</items>
        <items id="comment">*Assigning an identifier to a request by the Laboratory lnformation System (LIS) enables tracking progress of the request and enables linking results to requests. It also provides a reference to assist with enquiries and it is usually equivalent to the HL7 Filler Order Identifier.(en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Specimen detail(en)</items>
        <items id="description">*Details about the physical substance that has been analysed, in the situation where all results in this test are derived from the same specimen.(en)</items>
        <items id="comment">*If the specimen type is sufficiently specified with a code in the Test name, then this additional data is not required. If there are multiple specimens, these may be represented per 'Result group'.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Laboratory internal identifier(en)</items>
        <items id="description">*A local identifier assigned by the receiving Laboratory Information System (LIS) to track the test process. (en)</items>
        <items id="comment">*This identifier is an internal tracking number assigned by the LIS, and it not intended to be the name of the test. (en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Overall test status(en)</items>
        <items id="description">*The status of the laboratory test result as a whole.(en)</items>
        <items id="comment">*The values have been specifically chosen to match those in the HL7 FHIR Diagnostic report, historically derived from HL7v2 practice. Other local codes/terms can be used via the Text 'choice'.&#xD;
&#xD;
This element is multiple occurrence to cater for the use cases where statuses for different aspects of the result have been split into several elements. (en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Cancelled(en)</items>
        <items id="description">*The result is unavailable because the test was not started or not completed (also sometimes called 'aborted').(en)</items>
      </items>
      <items code="at0075">
        <items id="text">*Overall test status timestamp(en)</items>
        <items id="description">*The date and/or time that ‘Overall test status’ was issued.(en)</items>
      </items>
      <items code="at0077">
        <items id="text">*Diagnostic service category(en)</items>
        <items id="description">*The diagnostic service or discipline that is responsible for the laboratory test result. (en)</items>
        <items id="comment">*This is intended to be a general categorisation and not to capture the organisational name of the laboratory. For example: anatomical pathology, immunology and transfusion medicine, medical microbiology, clinical pharmacology, medical genetics, medical biochemistry. Alternatively more granular sub categories or sub disciplines, such as endocrinology, haematology, and allergology services, may be used. This may assist clinicians in filtering between categories of results. Coding with a terminology is desirable, where possible.  (en)</items>
      </items>
      <items code="at0090">
        <items id="text">*Requester(en)</items>
        <items id="description">*Details of the clinician or organisation requesting the laboratory test result.(en)</items>
      </items>
      <items code="at0094">
        <items id="text">*Test request details(en)</items>
        <items id="description">*Details about the test request.(en)</items>
        <items id="comment">*In most situations there is one test request and a single corresponding test result, however this repeating cluster allows for the situation where there may be multiple test requests reported using a single test result. As an example: 'a clinician asks for blood glucose in one request and Urea/electrolytes in a second request, but the lab analyser does both and the lab wishes to report these together'.(en)</items>
      </items>
      <items code="at0097">
        <items id="text">*Test result (en)</items>
        <items id="description">*Results of the test performed on the specimen(s). (en)</items>
        <items id="comment">*This SLOT may carry an individual analyte, a group, panel or battery of multiple analytes, or a more complex and specific structure. (en)</items>
      </items>
      <items code="at0098">
        <items id="text">*Test diagnosis(en)</items>
        <items id="description">*Single word, phrase or brief description that represents the clinical meaning and significance of the laboratory test result. (en)</items>
        <items id="comment">*For example: 'Severe hepatic impairment', 'Salmonella contamination'. Coding of the diagnosis with a terminology is strongly recommended, where possible. This diagnosis should be aligned with the narrative in the 'Conclusion'. (en)</items>
      </items>
      <items code="at0100">
        <items id="text">*Clinical information provided(en)</items>
        <items id="description">*Description of clinical information available at the time of interpretation of results.(en)</items>
        <items id="comment">*This data element may include a link to the original clinical information provided in the test request.(en)</items>
        <items id="fhir_mapping">*DiagnosticReport.requestDetail.clinicalNotes(en)</items>
      </items>
      <items code="at0101">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the test result not captured in other fields.(en)</items>
      </items>
      <items code="at0106">
        <items id="text">*Original test requested name(en)</items>
        <items id="description">*Name of the original laboratory test requested. (en)</items>
        <items id="comment">*This data element is to be used when the test requested differs from the test actually performed by the laboratory. (en)</items>
      </items>
      <items code="at0107">
        <items id="text">*Registered(en)</items>
        <items id="description">*The existence of the test is registered in the Laboratory Information System, but there is nothing yet available.(en)</items>
      </items>
      <items code="at0110">
        <items id="text">*Testing details (en)</items>
        <items id="description">*Structured details about the method of analysis, device or interpretation used.(en)</items>
        <items id="comment">*For example: 'details of ELISA/nephelometry'.(en)</items>
      </items>
      <items code="at0111">
        <items id="text">*Point-of-care test(en)</items>
        <items id="description">*This indicates whether the test was performed directly at Point-of-Care (POCT) as opposed to a formal result from a laboratory or other service delivery organisation.(en)</items>
        <items id="comment">*True if the test was performed directly at Point-of-Care (POCT).(en)</items>
      </items>
      <items code="at0112">
        <items id="text">*Tree(en)</items>
        <items id="description">*@ internal @(en)</items>
      </items>
      <items code="at0113">
        <items id="text">*Confounding factors(en)</items>
        <items id="description">*Issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
        <items id="comment">*'Confounding factors' should be reserved for uncontrolled/unplanned issues of patient state/physiology that might affect interpretation, for example 'recent exercise' or 'recent tobacco smoking'.&#xD;
&#xD;
Known or required preconditions, such as 'fasting' should be carried in the 'Sampling conditions' element within the CLUSTER.specimen archetype . In some cases preconditions are captured as part of the test name, for example 'Fasting blood glucose'.&#xD;
&#xD;
Known issues with specimen collection or handling, such as 'prolonged use of tourniquet' or 'sample haemolysed', should be carried in the 'Specimen quality' elements within CLUSTER.specimen archetype.&#xD;
&#xD;
Coding with a terminology is desirable, where possible.  (en)</items>
      </items>
      <items code="at0114">
        <items id="text">*Structured confounding factors (en)</items>
        <items id="description">*Details of patient state that may alter interpretation of the laboratory test.(en)</items>
        <items id="comment">*For example: Last Normal Menstrual Period (LNMP). (en)</items>
      </items>
      <items code="at0115">
        <items id="text">*Corrected(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0116">
        <items id="text">*Entered in error(en)</items>
        <items id="description">*The Test Result has been withdrawn following previous Final release.(en)</items>
      </items>
      <items code="at0117">
        <items id="text">*Extension(en)</items>
        <items id="description">*Slot to allow extension to support localisation or alignment with other standards/ reference models.(en)</items>
      </items>
      <items code="at0118">
        <items id="text">*Multimedia representation(en)</items>
        <items id="description">*Digital image, video or diagram representing the test result.(en)</items>
        <items id="comment">*Multiple formats are allowed but they should represent equivalent clinical content.(en)</items>
        <items id="fhir_mapping">*DiagnosticReport.presentedForm(en)</items>
      </items>
      <items code="at0119">
        <items id="text">*Appended(en)</items>
        <items id="description">*Subsequent to being final, the report has been modified by adding new content. The existing content is unchanged. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0120">
        <items id="text">*Preliminary(en)</items>
        <items id="description">*Verified early results are available, but not all results are final. This is a sub-category of 'Partial'.(en)</items>
      </items>
      <items code="at0121">
        <items id="text">*Test method (en)</items>
        <items id="description">*</items>
        <items id="comment">*Coding with a terminology is desirable, where possible.  (en)</items>
      </items>
      <items code="at0122">
        <items id="text">*Structured test diagnosis (en)</items>
        <items id="description">*A structured or complex diagnosis for the laboratory test. (en)</items>
        <items id="comment">*For example: Anatomical pathology diagnoses consisting of several different axes such as morphology, etiology and function. (en)</items>
      </items>
    </term_definitions>
    <term_definitions language="en">
      <items code="at0000">
        <items id="text">Laboratory test result</items>
        <items id="description">The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Any event</items>
        <items id="description">Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Test name</items>
        <items id="description">Name of the laboratory investigation performed on the specimen(s).</items>
        <items id="comment">A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'.</items>
      </items>
      <items code="at0017">
        <items id="text">Receiving laboratory</items>
        <items id="description">Details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.</items>
        <items id="comment">This slot is intended to carry details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.&#xD;
&#xD;
The receiving laboratory may either perform the test or refer it to another laboratory. Where a different laboratory is responsible for performing the testing on specific analytes, it would be expected that these details would be carried in the 'Analyte result detail' SLOT within the CLUSTER.laboratory_test_analyte archetype.</items>
      </items>
      <items code="at0035">
        <items id="text">Distribution list</items>
        <items id="description">Details of additional clinicians or organisations who require a copy of the test result.</items>
        <items id="comment">The 'Distribution list' is for information-only, and that the primary recipient of the report is the person intended to act on the information.</items>
      </items>
      <items code="at0037">
        <items id="text">Partial</items>
        <items id="description">This is a partial (e.g. initial, interim or preliminary) Test Result: data in the Test Result may be incomplete or unverified.</items>
      </items>
      <items code="at0038">
        <items id="text">Final</items>
        <items id="description">The Test result is complete and verified by an authorised person.</items>
      </items>
      <items code="at0040">
        <items id="text">Amended</items>
        <items id="description">The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist, and result data has been changed.</items>
      </items>
      <items code="at0057">
        <items id="text">Conclusion</items>
        <items id="description">Narrative description of the key findings.</items>
        <items id="comment">For example: 'Pattern suggests significant renal impairment'. The content of the conclusion will vary, depending on the investigation performed. This conclusion should be aligned with the coded 'Test diagnosis'.</items>
      </items>
      <items code="at0062">
        <items id="text">Requester order identifier</items>
        <items id="description">The local identifier assigned by the requesting clinical system.</items>
        <items id="comment">Equivalent to the HL7 Placer Order Identifier.</items>
      </items>
      <items code="at0063">
        <items id="text">Receiver order identifier</items>
        <items id="description">The local identifier assigned to the test order by the order filler, usually by the Laboratory Information System (LIS).</items>
        <items id="comment">Assigning an identifier to a request by the Laboratory lnformation System (LIS) enables tracking progress of the request and enables linking results to requests. It also provides a reference to assist with enquiries and it is usually equivalent to the HL7 Filler Order Identifier.</items>
      </items>
      <items code="at0065">
        <items id="text">Specimen detail</items>
        <items id="description">Details about the physical substance that has been analysed.</items>
        <items id="comment">If the specimen type is sufficiently specified with a code in the Test name, then this additional data is not required. Linking results to specific specimens may be recorded using 'Specimen identifier' elements in both the CLUSTER.specimen and the various results CLUSTER archetypes.</items>
      </items>
      <items code="at0068">
        <items id="text">Laboratory internal identifier</items>
        <items id="description">A local identifier assigned by the receiving Laboratory Information System (LIS) to track the test process.</items>
        <items id="comment">This identifier is an internal tracking number assigned by the LIS, and it not intended to be the name of the test.</items>
      </items>
      <items code="at0073">
        <items id="text">Overall test status</items>
        <items id="description">The status of the laboratory test result as a whole.</items>
        <items id="comment">The values have been specifically chosen to match those in the HL7 FHIR Diagnostic report, historically derived from HL7v2 practice. Other local codes/terms can be used via the Text 'choice'.&#xD;
&#xD;
This element is multiple occurrence to cater for the use cases where statuses for different aspects of the result have been split into several elements.</items>
      </items>
      <items code="at0074">
        <items id="text">Cancelled</items>
        <items id="description">The result is unavailable because the test was not started or not completed (also sometimes called 'aborted').</items>
      </items>
      <items code="at0075">
        <items id="text">Overall test status timestamp</items>
        <items id="description">The date and/or time that ‘Overall test status’ was issued.</items>
      </items>
      <items code="at0077">
        <items id="text">Diagnostic service category</items>
        <items id="description">The diagnostic service or discipline that is responsible for the laboratory test result.</items>
        <items id="comment">This is intended to be a general categorisation and not to capture the organisational name of the laboratory. For example: anatomical pathology, immunology and transfusion medicine, medical microbiology, clinical pharmacology, medical genetics, medical biochemistry. Alternatively more granular sub categories or sub disciplines, such as endocrinology, haematology, and allergology services, may be used. This may assist clinicians in filtering between categories of results. Coding with a terminology is desirable, where possible.</items>
      </items>
      <items code="at0090">
        <items id="text">Requester</items>
        <items id="description">Details of the clinician or organisation requesting the laboratory test result.</items>
      </items>
      <items code="at0094">
        <items id="text">Test request details</items>
        <items id="description">Details about the test request.</items>
        <items id="comment">In most situations there is one test request and a single corresponding test result, however this repeating cluster allows for the situation where there may be multiple test requests reported using a single test result.&#xD;
&#xD;
As an example: 'a clinician asks for blood glucose in one request and Urea/electrolytes in a second request, but the lab analyser does both and the lab wishes to report these together'.</items>
      </items>
      <items code="at0097">
        <items id="text">Test result</items>
        <items id="description">Results of the test performed on the specimen(s).</items>
        <items id="comment">This SLOT may carry an individual analyte, a group, panel or battery of multiple analytes, or a more complex and specific structure.</items>
      </items>
      <items code="at0098">
        <items id="text">Test diagnosis</items>
        <items id="description">Single word, phrase or brief description that represents the clinical meaning and significance of the laboratory test result.</items>
        <items id="comment">For example: 'Severe hepatic impairment', 'Salmonella contamination'. Coding of the diagnosis with a terminology is strongly recommended, where possible. This diagnosis should be aligned with the narrative in the 'Conclusion'.</items>
      </items>
      <items code="at0100">
        <items id="text">Clinical information provided</items>
        <items id="description">Description of clinical information available at the time of interpretation of results.</items>
        <items id="comment">This data element may include a link to the original clinical information provided in the test request.</items>
      </items>
      <items code="at0101">
        <items id="text">Comment</items>
        <items id="description">Additional narrative about the test result not captured in other fields.</items>
      </items>
      <items code="at0106">
        <items id="text">Original test requested name</items>
        <items id="description">Name of the original laboratory test requested.</items>
        <items id="comment">This data element is to be used when the test requested differs from the test actually performed by the laboratory.</items>
      </items>
      <items code="at0107">
        <items id="text">Registered</items>
        <items id="description">The existence of the test is registered in the Laboratory Information System, but there is nothing yet available.</items>
      </items>
      <items code="at0110">
        <items id="text">Testing details</items>
        <items id="description">Structured details about the method of analysis, device or interpretation used.</items>
        <items id="comment">For example: 'details of ELISA/nephelometry'.</items>
      </items>
      <items code="at0111">
        <items id="text">Point-of-care test</items>
        <items id="description">This indicates whether the test was performed directly at Point-of-Care (POCT) as opposed to a formal result from a laboratory or other service delivery organisation.</items>
        <items id="comment">True if the test was performed directly at Point-of-Care (POCT).</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Confounding factors</items>
        <items id="description">Issues or circumstances that impact on the accurate interpretation of the measurement or test result.</items>
        <items id="comment">'Confounding factors' should be reserved for uncontrolled/unplanned issues of patient state/physiology that might affect interpretation, for example 'recent exercise' or 'recent tobacco smoking'.&#xD;
&#xD;
Known or required preconditions, such as 'fasting' should be carried in the 'Sampling conditions' element within the CLUSTER.specimen archetype . In some cases preconditions are captured as part of the test name, for example 'Fasting blood glucose'.&#xD;
&#xD;
Known issues with specimen collection or handling, such as 'prolonged use of tourniquet' or 'sample haemolysed', should be carried in the 'Specimen quality' elements within CLUSTER.specimen archetype.&#xD;
&#xD;
Coding with a terminology is desirable, where possible.</items>
      </items>
      <items code="at0114">
        <items id="text">Structured confounding factors</items>
        <items id="description">Details of issues or circumstances that impact on the accurate interpretation of the measurement or test result.</items>
        <items id="comment">For example: Last Normal Menstrual Period (LNMP).</items>
      </items>
      <items code="at0115">
        <items id="text">Corrected</items>
        <items id="description">The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist. This is a sub-category of 'Amended'.</items>
      </items>
      <items code="at0116">
        <items id="text">Entered in error</items>
        <items id="description">The Test Result has been withdrawn following previous Final release.</items>
      </items>
      <items code="at0117">
        <items id="text">Extension</items>
        <items id="description">Additional information required to capture local content or to align with other reference models/formalisms.</items>
        <items id="comment">For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.</items>
      </items>
      <items code="at0118">
        <items id="text">Multimedia representation</items>
        <items id="description">Digital image, video or diagram representing the test result.</items>
        <items id="comment">Multiple formats are allowed but they should represent equivalent clinical content.</items>
      </items>
      <items code="at0119">
        <items id="text">Appended</items>
        <items id="description">Subsequent to being final, the report has been modified by adding new content. The existing content is unchanged. This is a sub-category of 'Amended'.</items>
      </items>
      <items code="at0120">
        <items id="text">Preliminary</items>
        <items id="description">Verified early results are available, but not all results are final. This is a sub-category of 'Partial'.</items>
      </items>
      <items code="at0121">
        <items id="text">Test method</items>
        <items id="description">Description about the method used to perform the test.</items>
        <items id="comment">Coding with a terminology is desirable, where possible.</items>
      </items>
      <items code="at0122">
        <items id="text">Structured test diagnosis</items>
        <items id="description">A structured or complex diagnosis for the laboratory test.</items>
        <items id="comment">For example: Anatomical pathology diagnoses consisting of several different axes such as morphology, etiology and function.</items>
      </items>
    </term_definitions>
    <term_definitions language="nb">
      <items code="at0000">
        <items id="text">Laboratorieresultat</items>
        <items id="description">Resultat, inkludert funn og laboratoriets tolkning, av en laboratorieundersøkelse utført på prøvemateriale fra et individ eller relatert til individet.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Uspesifisert hendelse</items>
        <items id="description">Standard, uspesifisert tidspunkt eller tidsintervall som kan defineres mer eksplisitt i en templat eller i en applikasjon.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Undersøkelsesnavn</items>
        <items id="description">Navn på laboratorieundersøkelsen som er utført på prøvematerialet.</items>
        <items id="comment">Undersøkelsesnavnet kan dekke ett enkelt resultat eller en gruppe av resultater. Undersøkelsesnavnet kan kodes med medisinsk kodeverk som for eksempel NLK (Norsk laboratoriekodeverk), LOINC, SNOMED CT eller lokale laboratoriekodeverk. Eksempler kan være "Glukose", "Elektrolytter", "Blodgass", "Differensialtelling", "Dyrkning", "Kortisol (morgen)" eller "histologi melanom". Navnet kan noen ganger inneholde typen prøvemateriale og/eller pasientstatus, for eksempel "fastende blodglukose" "Kalium i svette", eller inneholde annen informasjon, som "Kalium (PNA blodgass)".</items>
      </items>
      <items code="at0017">
        <items id="text">Ansvarlig laboratorium</items>
        <items id="description">Detaljer om laboratoriet som mottok den opprinnelige rekvisisjonen og har det overordnede ansvaret for prøven, selv om det er andre laboratorier som utfører de enkelte analysene.</items>
        <items id="comment">Dette SLOTet er ment for detaljer om laboratoriet som mottok rekvisisjonen og har det overordnede ansvaret for å sende en svarrapport, selv om andre laboratorier utfører spesifikke deler av den.&#xD;
&#xD;
Det ansvarlige laboratoriet kan enten utføre undersøkelsene selv, eller videresende til andre laboratorier. Hvis et annet laboratorium har utført spesifikke undersøkelser bør informasjon om dette bli beskrevet i SLOTet "Detaljer om analyseresultat" i arketypen "Analyseresultat".&#xD;
&#xD;
"Ansvarlig laboratorium" kalles ofte "Tjenesteyter".</items>
      </items>
      <items code="at0035">
        <items id="text">Kopimottakere</items>
        <items id="description">Detaljert informasjon knyttet til kliniker eller organisatorisk enhet som skal motta en kopi av laboratoriesvaret.</items>
        <items id="comment">Personene eller organisasjonene på distribusjonslisten mottar svaret kun til informasjon, og det er hovedmottakeren av rapporten som forventes å agere på den.</items>
      </items>
      <items code="at0037">
        <items id="text">Ufullstendig</items>
        <items id="description">Dette er et delvis (dvs initalt, foreløpig eller preliminært) svar: Data i svaret kan være ukomplett eller ubekreftet.</items>
      </items>
      <items code="at0038">
        <items id="text">Endelig</items>
        <items id="description">Svaret er komplett og er bekreftet av ansvarlig person.</items>
      </items>
      <items code="at0040">
        <items id="text">Revidert</items>
        <items id="description">Svaret har blitt modifisert etter å ha vært i status "Endelig", og er komplett og verifisert av ansvarlig person, og svardata er endret.</items>
      </items>
      <items code="at0057">
        <items id="text">Konklusjon</items>
        <items id="description">Fritekstbeskrivelse av de viktigste funnene.</items>
        <items id="comment">For eksempel "mønsteret indikerer betydelig nedsatt nyrefunksjon". Innholdet av konklusjonen vil variere, basert på hvilken undersøkelse som er utført. Konklusjonen bør være i overensstemmelse med kodene brukt i elementet "Diagnose".</items>
      </items>
      <items code="at0062">
        <items id="text">Rekvirentens rekvisisjonsID</items>
        <items id="description">Rekvirentens/bestillers lokale ID for rekvisisjonen.</items>
        <items id="comment">Tilsvarende HL7 "Placer Order Identifier".</items>
      </items>
      <items code="at0063">
        <items id="text">Rekvisisjonsmottakers rekvisisjonsID</items>
        <items id="description">Bestillingens/rekvisisjonens lokale identifikator/referansenummer tildelt av tjenesteyter/mottaker, som regel av LIMS.</items>
        <items id="comment">Når Laboratorieinformasjonssystemet (LIMS) tildeler en identifikator, åpnes det for sporing av fremdriften/prosessforløpet på bestillingen av undersøkelsen/rekvisisjonen og for å koble undersøkelsesresultatet til rekvisisjonen/bestillingen. Som regel tilsvarer dette HL7 "Filler Order Identifier".&#xD;
&#xD;
Denne identifikatoren kalles også ofte "rekvisisjonsnummer" eller "remissenummer".</items>
      </items>
      <items code="at0065">
        <items id="text">Prøvedetaljer</items>
        <items id="description">Detaljer om den fysiske substansen som er analysert.</items>
        <items id="comment">Hvis prøvematerialet er tilstrekkelig spesifisert med en kode i analysenavnet er ikke dette dataelementet nødvendig. Det er mulig å koble svar med spesifikke prøver ved hjelp av elementene "ID for prøvemateriale" i både CLUSTER.specimen og de forskjellige CLUSTER-arketypene for laboratoriesvar.</items>
      </items>
      <items code="at0068">
        <items id="text">Laboratorieintern identifikator</items>
        <items id="description">En lokal identifikator tildelt av det mottagende laboratoriesystemet (LIMS), for å kunne spore analyseprosessen.</items>
        <items id="comment">Denne identifikatoren er et internt sporingsnummer tildelt av LIMS, og det er ikke ment å være navnet på undersøkelsen.</items>
      </items>
      <items code="at0073">
        <items id="text">Overordnet resultatstatus</items>
        <items id="description">Den overordnede statusen for hele laboratorieresultatet/prøven.</items>
        <items id="comment">Verdiene er valgt spesifikt for å samsvare med verdiene i HL7 FHIR-ressursen "Diagnostic report", som historisk sett kommer fra HL7 v2. Andre lokale koder eller termer kan brukes ved å bruke datatypen "Fri eller kodet tekst.&#xD;
&#xD;
Dette elementet kan repeteres for å understøtte bruksområdene der statuser for forskjellige aspekter av resultatet er delt opp i flere elementer. Et eksempel på dette er de norske standard labsvarmeldingene i HIS 1.4-standarden, der status for svaret og status for laboratorieprosessen håndteres separat.</items>
      </items>
      <items code="at0074">
        <items id="text">Kansellert</items>
        <items id="description">Svaret er utilgjengelig fordi analysen ikke ble påbegynt eller ferdigstilt (også kalt "avbrutt").</items>
      </items>
      <items code="at0075">
        <items id="text">Tidsangivelse for overordnet resultatstatus</items>
        <items id="description">Tidspunktet for utstedelsen av "Overordnet resultatstatus".</items>
      </items>
      <items code="at0077">
        <items id="text">Laboratoriedisiplin</items>
        <items id="description">Laboratoriefagområdet, -disiplinen eller subdisiplinen som er ansvarlig for resultatet.</items>
        <items id="comment">Dette er ikke ment for å gjenspeile laboratoriets interne organisering, men for å angi hvilken laboratoriedisiplin analysene tilhører. For eksempel patologi, immunologi og transfusjonsmedisin, medisinsk mikrobiologi, klinisk farmakologi, medisinsk genetikk og medisinsk biokjemi. Eventuelt enda mer findelte subkategorier eller subdisipliner som f.eks. hormoner/endokrinologi, hematologi, allergologi. Dette hjelper klinikere med å filtrere mellom resultatkategorier i henhold til lokalt oppsett. Koding med en terminologi er ønskelig, der det er mulig.</items>
      </items>
      <items code="at0090">
        <items id="text">Rekvirent</items>
        <items id="description">Detaljert informasjon knyttet til kliniker eller organisatorisk enhet som har rekvirert/bestilt analysen.</items>
      </items>
      <items code="at0094">
        <items id="text">Rekvisisjonsdetaljer</items>
        <items id="description">Detaljer knyttet til rekvisisjonen.</items>
        <items id="comment">I de fleste situasjoner finnes det én rekvisisjon og ett korresponderende svar, men under noen omstendigheter kan flere rekvisisjoner representeres ved hjelp av en enkelt laboratorieresultat-arketype.&#xD;
&#xD;
For eksempel kan en kliniker bestille "glukose" i en rekvisisjon og "urea og elektrolytter" i en ytterligere rekvisisjon, mens laboratoriet utfører begge analysene og sender en samlet rapport.</items>
      </items>
      <items code="at0097">
        <items id="text">Undersøkelsesresultat</items>
        <items id="description">Resultat av undersøkelsen som er utført på prøvematerialet.</items>
        <items id="comment">Dette SLOTet kan inneholde resultat for ett enkelt analyseresultat, for en gruppe analyseresultater, eller for en mer kompleks og spesifikk struktur.</items>
      </items>
      <items code="at0098">
        <items id="text">Diagnose</items>
        <items id="description">Enkeltord, frase eller kort beskrivelse som representerer den kliniske betydningen og signifikansen av laboratorieresultatet.</items>
        <items id="comment">For eksempel "Betydelig nedsatt leverfunksjon" eller "Salmonella". Koding med en terminologi foretrekkes, der det er mulig. Diagnosen bør være i overensstemmelse med teksten i "Konklusjon".</items>
      </items>
      <items code="at0100">
        <items id="text">Tilgjengelig klinisk informasjon</items>
        <items id="description">Beskrivelse av klinisk informasjon som er tilgjengelig på tolkningstidspunktet.</items>
        <items id="comment">Dette dataelementet kan inkludere en lenke til den opprinnelige kliniske informasjonen som ble angitt i rekvisisjonen.</items>
      </items>
      <items code="at0101">
        <items id="text">Kommentar</items>
        <items id="description">Tekstlig tilleggsinformasjon om analyseresultatet, som ikke er registrert i andre felt.</items>
      </items>
      <items code="at0106">
        <items id="text">Navn på opprinnelig rekvirert analyse</items>
        <items id="description">Navn på undersøkelsen som opprinnelig ble rekvirert.</items>
        <items id="comment">Dette dataelementet er tenkt brukt dersom det er forskjell mellom undersøkelsen som er rekvirert og den som faktisk er utført.</items>
      </items>
      <items code="at0107">
        <items id="text">Registrert</items>
        <items id="description">Analysen er registrert i laboratoriesystemet, men svaret er ikke tilgjengelig per nå.</items>
      </items>
      <items code="at0110">
        <items id="text">Undersøkelsesdetaljer</items>
        <items id="description">Strukturert tilleggsinformasjon om hvilken analysemetode, utstyr eller tolkning som er benyttet.</items>
        <items id="comment">For eksempel "detaljer om ELISA/nefelometri".</items>
      </items>
      <items code="at0111">
        <items id="text">Pasientnær analysering</items>
        <items id="description">Dette indikerer hvorvidt analysen ble utført gjennom pasientnær analysering (PNA) i stedet for en mer formell laboratorietjeneste.</items>
        <items id="comment">Sann dersom analysen ble utført ved pasientnær analysering (PNA).</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Konfunderende faktorer</items>
        <items id="description">Forhold eller omstendigheter som påvirker tolkningen av laboratorieresultatet.</items>
        <items id="comment">"Konfunderende faktorer" bør være reservert for ukontrollerte eller uplanlagte forhold hos pasienten som kan påvirke tolkningen av laboratorieresultatet. For eksempel "nylig fysisk aktivitet", "nylig røykt tobakk". &#xD;
&#xD;
Kjente forutsetninger som "fastende" bør dokumenteres i elementet "Prøvetakingsforhold" i arketypen CLUSTER.specimen. I noen tilfeller er slike forutsetninger del av undersøkelsesnavnet, for eksempel "Fastende blodsukker".&#xD;
&#xD;
Kjente forhold knyttet til prøvetaking eller håndtering av prøven, som "langvarig stase" eller "hemolyse" (preanalytiske forhold) bør dokumenteres i elementet "Prøvekvalitet" i arketypen CLUSTER.specimen.&#xD;
&#xD;
Koding med en terminologi er ønskelig, der det er mulig.</items>
      </items>
      <items code="at0114">
        <items id="text">Strukturerte konfunderende faktorer</items>
        <items id="description">Ytterligere detaljer om forhold i tilstand eller omstendigheter som kan påvirke tolkningen av laboratorieresultatet.</items>
        <items id="comment">For eksempel siste normale menstruasjonsperiode.</items>
      </items>
      <items code="at0115">
        <items id="text">Korrigert</items>
        <items id="description">Svaret har blitt modifisert etter å ha vært i status "Endelig" og er komplett og verifisert. Dette er en underkategori til "Revidert".</items>
      </items>
      <items code="at0116">
        <items id="text">Feilregistrert</items>
        <items id="description">Analysesvaret har blitt trukket tilbake etter å ha vært i status "Endelig".</items>
      </items>
      <items code="at0117">
        <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 eller CIMI.</items>
      </items>
      <items code="at0118">
        <items id="text">Multimediarepresentasjon</items>
        <items id="description">Digitalt bilde, video eller diagram som representerer analyseresultatet.</items>
        <items id="comment">Flere formater tillates, men innholdet i de forskjellige formatene må representere det samme innholdet.</items>
      </items>
      <items code="at0119">
        <items id="text">Tillegg</items>
        <items id="description">Etter å ha vært satt som status "Endelig", har det blitt lagt nytt innhold til rapporten. Det eksisterende innholdet er uendret. Dette er en underkategori av "Revidert".</items>
      </items>
      <items code="at0120">
        <items id="text">Foreløpig</items>
        <items id="description">Verifiserte tidlige svar er tilgjengelige, men ikke alle svar er endelige. Dette er en underkategori av "Ufullstendig".</items>
      </items>
      <items code="at0121">
        <items id="text">Undersøkelsesmetode</items>
        <items id="description">Beskrivelse av metoden som ble brukt for å utføre undersøkelsen.</items>
        <items id="comment">Koding med en terminologi er ønskelig, der det er mulig.</items>
      </items>
      <items code="at0122">
        <items id="text">Strukturert diagnose</items>
        <items id="description">En strukturert eller kompleks diagnose for laboratorieundersøkelsen.</items>
        <items id="comment">For eksempel patologidiagnoser bestående av flere forskjellige akser som morfologi, etiologi og funksjon.</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">Event Series</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">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">检验项目名称</items>
        <items id="description">针对标本所进行的实验室检验项目的名称。</items>
        <items id="comment">检验结果可能代表的是单独一种分析物或者是一组项目/分析物，包括成套的检验项目（组套检验项目）。强烈建议采用特定的术语标准（如 LOINC 或 SNOMED CT）对“检验项目名称”加以编码。例如：“葡萄糖”、“尿素和电解质”、“拭子”、“皮质醇 （上午）”、“汗液钾离子”或“黑色素瘤组织病理学”。检验项目名称之中有时可能会包括标本类型和患者状态，如“空腹血糖”，或者是包括其他的信息，如“钾（PNA 血气）”。</items>
      </items>
      <items code="at0017">
        <items id="text">接收方实验室</items>
        <items id="description">关于当时接收了相应的检验申请并整体负责管理当前检验项目的报告工作的实验室的详情，即使其他实验室执行其中的特定方面。</items>
        <items id="comment">此槽位旨在记录关于当时接收了相应的检验申请并整体负责管理当前检验项目的报告工作的实验室的详情，即使其他实验室执行其中的特定方面。&#xD;
&#xD;
接收方实验室可能会自身来执行当前的检验项目，或者也可能将其转交给其他的实验室。如果其他实验室负责检测特定的分析物，则应当期望这些详情包含在群簇型实验室检验项目分析物原始型（CLUSTER.laboratory_test_analyte）里的分析物结果详情槽位“Analyte result detail”之中。</items>
      </items>
      <items code="at0035">
        <items id="text">分发列表</items>
        <items id="description">其他那些要求获得当前实验室检验结果的临床医生或组织机构。</items>
        <items id="comment">“分发列表”仅供参考，报告的首要接收方则是意在依据当前的实验室检验结果采取行动的人员。</items>
      </items>
      <items code="at0037">
        <items id="text">部分</items>
        <items id="description">当前还属于部分的（比如，初始的、暂时的或初步的）检验结果：检验结果之中的数据可能不完整或者未经核对。</items>
      </items>
      <items code="at0038">
        <items id="text">最终</items>
        <items id="description">检验结果完整且经过授权人员的核对或者说审核。</items>
      </items>
      <items code="at0040">
        <items id="text">经过修正</items>
        <items id="description">结果在达到最终状态之后已被修改，是完整的结果，经过了负责的病理学工作人员的核对，且已经更改了结果数据。</items>
      </items>
      <items code="at0057">
        <items id="text">结论</items>
        <items id="description">关于关键所见/发现的文字叙述型描述。</items>
        <items id="comment">例如：“[所观察到的]模式表明存在显著的肾脏损害”。结论的内容会根据所进行的检查而有所不同。此项结论应当与编码型的检验项目诊断数据元“Test diagnosis”保持一致。</items>
        <items id="fhir_mapping">*DiagnosticReport.conclusion(en)</items>
      </items>
      <items code="at0062">
        <items id="text">申请方医嘱标识符</items>
        <items id="description">申请方临床系统所赋予当前检验项目医嘱/申请的本地标识符。</items>
        <items id="comment">等价于HL7申请方医嘱标识符（ Placer Order Identifier）。</items>
      </items>
      <items code="at0063">
        <items id="text">接收方医嘱标识符</items>
        <items id="description">医嘱执行方赋予当前检验项目医嘱/申请的本地标识符。其中，医嘱执行方通常为实验室信息系统（ Laboratory Information System，LIS）。</items>
        <items id="comment">实验室信息系统（ Laboratory Information System，LIS）为检验项目医嘱/申请赋予标识符，将便于实现对于申请进展情况的跟踪以及结果与相应医嘱/申请的链接。同时，这也是有助于查询的一种参考信息（reference），且通常等价于HL7执行方医嘱标识符（Filler Order Identifier）。</items>
      </items>
      <items code="at0065">
        <items id="text">标本详情</items>
        <items id="description">关于所已经分析的物质的详情。</items>
        <items id="comment">如果利用检验项目名称之中的代码可以充分明确相应的标本类型，则不需要此项附加的数据。可以采用群簇型标本原始型（CLUSTER.specimen）和各种的群簇型结果原始型之中的标本标识符元素“Specimen identifier”元素来记录关于将结果链接到特定标本的信息。</items>
      </items>
      <items code="at0068">
        <items id="text">实验室内部标识符</items>
        <items id="description">接收方实验室信息系统（Laboratory Information System，LIS）所分配的本地标识符，用于跟踪检验过程。</items>
        <items id="comment">该标识符属于是实验室信息系统（Laboratory Information System，LIS）所分配的内部追踪编号，但并非旨在作为检验项目的名称。</items>
      </items>
      <items code="at0073">
        <items id="text">检验项目总体状态</items>
        <items id="description">当前的实验室检验项目作为整体的状态</items>
        <items id="comment">这些编码型取值是经过专门挑选的，以与 HL7 FHIR 诊断报告资源之中的取值相匹配，而在历史上这些取值源自 HL7v2 实践。另外，可以借助于文本型选项“choice”来使用其他的本地代码/术语。&#xD;
&#xD;
本数据元可以多次出现，以适应那些将结果不同方面的状态拆分成多个数据元的用例。</items>
      </items>
      <items code="at0074">
        <items id="text">已撤销</items>
        <items id="description">当前结果不可用，因为该检验项目并未开始或者并未完成（有时又称为“取消”、“已中止”或“已放弃”）。</items>
      </items>
      <items code="at0075">
        <items id="text">检验项目总体状态时间戳</items>
        <items id="description">发布检验项目总体状态时的日期和/或时间。</items>
      </items>
      <items code="at0077">
        <items id="text">诊断服务类别</items>
        <items id="description">负责当前实验室检验结果的诊断服务或学科。</items>
        <items id="comment">本数据元旨在进行一般的分类，而并非旨在记录实验室的组织结构名称。例如：解剖病理学、免疫学、输血医学、医学微生物学、临床药理学、医学遗传学、医学生物化学。或者，还可以采用粒度更精细的子类别或子学科，如内分泌学、血液学和变态反应学服务。此项数据可能有助于临床医生在结果类别之间进行筛选。最好尽可能采用特定的术语标准加以编码。</items>
      </items>
      <items code="at0090">
        <items id="text">申请方</items>
        <items id="description">关于申请当前实验室检验项目（结果）的临床医生或组织机构的详情。</items>
      </items>
      <items code="at0094">
        <items id="text">检验申请详情</items>
        <items id="description">关于检验申请的详情。</items>
        <items id="comment">在大多数情况下，每份检验请求分别会有相应的单独一项检验结果。不过，这个可重复的群簇允许存在检验结果只有一份[报告]而报告所针对的却是多份检验请求的情况。&#xD;
&#xD;
例如：医生在一份申请当中要求检测血糖，而在另一份申请中则要求检测尿素/电解质，而实验室分的析仪则会同时处理这两份申请，并且实验室希望将二者一并加以报告。</items>
      </items>
      <items code="at0097">
        <items id="text">检验结果</items>
        <items id="description">针对标本所进行的检验项目的结果。</items>
        <items id="comment">此槽位之中可以包含的是单个的分析物、多个分析物所构成的组合或组套，或者是更为复杂的特定结构。</items>
      </items>
      <items code="at0098">
        <items id="text">检验项目诊断</items>
        <items id="description">代表实验室测试结果的临床含义和意义/重要性的单词、短语或简短描述。</items>
        <items id="comment">例如：“严重肝脏损害”、“沙门菌污染”。强烈建议尽可能采用特定的术语标准对此项诊断加以编码。此项诊断应当与结论数据元“Conclusion”之中的文字叙述保持一致。</items>
      </items>
      <items code="at0100">
        <items id="text">已提供的临床信息</items>
        <items id="description">关于解释结果时可用的临床信息的描述。</items>
        <items id="comment">本数据元之中可以包含指向相应检验项目申请之中所提供的原始临床信息的链接。</items>
        <items id="fhir_mapping">*DiagnosticReport.requestDetail.clinicalNotes(en)</items>
      </items>
      <items code="at0101">
        <items id="text">注释</items>
        <items id="description">关于其他字段之中并未采集/记录的，关于当前检验结果的其他文字叙述型内容。</items>
      </items>
      <items code="at0106">
        <items id="text">原始申请检验项目名称</items>
        <items id="description">所申请的原始实验室检验项目的名称。</items>
        <items id="comment">当所申请的检验项目与实验室实际执行的检验项目不同时，应当会用到本数据元。</items>
      </items>
      <items code="at0107">
        <items id="text">已登记</items>
        <items id="description">表示当前检验项目的存在情况已在实验室信息系统之中进行了登记，但目前尚无任何可用的信息。</items>
      </items>
      <items code="at0110">
        <items id="text">检验详情</items>
        <items id="description">关于所采用的分析方法、仪器设备或解释的结构化详情。</items>
        <items id="comment">例如：关于ELISA/散射比浊法的详情。</items>
      </items>
      <items code="at0111">
        <items id="text">床旁检验项目</items>
        <items id="description">此项数据元旨在表明当前的检验项目究竟是床旁（Point-of-Care，POCT）直接进行的检验项目，而不是实验室或其他服务机构/部门/科室所提供的正式结果。</items>
        <items id="comment">如果当前的检验项目是在是床旁（Point-of-Care，POCT）直接进行的，则取值为真（True）。</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">混杂因素</items>
        <items id="description">影响当前监测/测量结果或检验结果准确解释的问题或情况。</items>
        <items id="comment">应当将混杂因素数据元“”保留用于那些可能影响结果解释的，患者状态/生理[机能]的未加控制/意外的问题，如 '近期的锻炼' 或 '近期的吸烟'。&#xD;
&#xD;
对于已知或所需的前提条件，如“禁食”，应当采用群簇型标本原始型（CLUSTER.specimen）之中的采样条件数据元'Sampling conditions' 来加以记录。在某些情况下，可能会将前提条件作为检验项目名称的一部分来加以记录，如 '空腹血糖'。&#xD;
&#xD;
对于标本采集或处理方面的已知问题，如“止血带使用时间过长”或“标本溶血”，应当采用群簇型标本原始型（CLUSTER.specimen）之中的标本质量数据元'Sampling conditions'元素来加以记录。&#xD;
&#xD;
最好尽可能采用特定的术语标准来加以编码。</items>
      </items>
      <items code="at0114">
        <items id="text">结构化混杂因素</items>
        <items id="description">关于那些影响检测/测量结果或检验结果准确解释的问题或情况的详情。</items>
        <items id="comment">例如：最后一次正常的月经周期 (Last Normal Menstrual Period，LNMP)。</items>
      </items>
      <items code="at0115">
        <items id="text">经过更正</items>
        <items id="description">结果在达到最终状态之后已被修改，是完整的结果，经过了负责的病理学工作人员的核对。这是“经过修正”类别的一个子类别。</items>
      </items>
      <items code="at0116">
        <items id="text">错误录入</items>
        <items id="description">当前检验结果在此前最终发布之后已被撤销。</items>
      </items>
      <items code="at0117">
        <items id="text">扩展</items>
        <items id="description">采集本地内容或者实现与其他参考模型/形式化体系之间进行协调统一所额外需的其他信息。</items>
        <items id="comment">例如：旨在实现与FHIR或CIMI等效项进行协调统一的，本地信息需求或额外的元数据。</items>
      </items>
      <items code="at0118">
        <items id="text">多媒体表现</items>
        <items id="description">表现当前检验结果的数字图像、视频或图表。</items>
        <items id="comment">允许采用多种的格式，但它们应当都表现的是等价的临床内容。</items>
        <items id="fhir_mapping">*DiagnosticReport.presentedForm(en)</items>
      </items>
      <items code="at0119">
        <items id="text">经过追加</items>
        <items id="description">在达到最终状态之后，因为添加新的内容而造成报告的修改。已有的内容并未发生变更。这是“经过修正”类别的一个子类别。</items>
      </items>
      <items code="at0120">
        <items id="text">初步</items>
        <items id="description">已有经过核对的早期/初步结果可用，但并非所有的结果都属于是最终结果。这是“部分”类别的一个子类别。</items>
      </items>
      <items code="at0121">
        <items id="text">检验方法</items>
        <items id="description">关于进行当前检验项目时所采用的方法的描述。</items>
        <items id="comment">最好尽可能采用特定的术语标准来加以编码。</items>
      </items>
      <items code="at0122">
        <items id="text">结构化检验项目诊断</items>
        <items id="description">当前实验室检验项目的结构化诊断或复杂诊断。</items>
        <items id="comment">例如：由多个不同的轴（如形态学、病因学和功能）所组成的解剖病理学诊断。</items>
      </items>
    </term_definitions>
    <term_definitions language="de">
      <items code="at0000">
        <items id="text">Laborergebnis</items>
        <items id="description">Das Ergebnis - einschließlich der Befunde und der Interpretation des Labors - einer Untersuchung, die an Proben durchgeführt wurde, die von einer Einzelperson stammen oder mit dieser Person zusammenhängen.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Jedes Ereignis</items>
        <items id="description">Jeder Zeitpunkt oder jedes Intervall, das in einem Template oder zur Laufzeit definiert werden kann.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Labortest-Bezeichnung</items>
        <items id="description">Name der Laboruntersuchung, die an der/den Probe(n) durchgeführt wurde.</items>
        <items id="comment">Ein Laborergebnis kann sich auf ein einzelnes Analyt oder eine Analytgruppe beziehen. Dazu zählen auch komplette Panel an Parametern. &#xD;
Es wird dringend empfohlen, die "Labortest-Bezeichnung" anhand einer Terminologie zu kodiereren, wie zum Beispiel LOINC oder SNOMED CT. Beispiel: "Glukose", "Harnstoff", "Abstrich", "Cortisol", "Leberbiopsie". Der Name kann u.U. auch das Probenmaterial oder den Patientenstatus (z.B. "Blutzuckerspiegel nüchtern") oder andere Informationen beinhalten wie "Kalium (Blutgas)".</items>
      </items>
      <items code="at0017">
        <items id="text">Labor, welches den Untersuchungsauftrag annimmt</items>
        <items id="description">Angaben zu dem Labor, das die Anfrage erhalten hat und die Hauptverantwortung für die Verwaltung der Berichterstattung über den Test trägt, auch wenn andere Labore bestimmte Aspekte ausführen.</items>
        <items id="comment">Dieser Slot gibt die Details des Labors an, dass die Anforderung erhalten hat und die Gesamtverantwortung für die Berichterstellung des Tests trägt, selbst wenn andere Labore bestimmte Aspekte ausführen.&#xD;
&#xD;
Das Empfangslabor kann den Test entweder durchführen oder an ein anderes Labor verweisen. Wenn ein anderes Labor für die Durchführung der Tests mit bestimmten Analyten zuständig ist, ist zu erwarten, dass diese Details im SLOT 'Analyte result detail' innerhalb des Archetyps CLUSTER.laboratory_test_analyte enthalten sind.</items>
      </items>
      <items code="at0035">
        <items id="text">Verteilerliste</items>
        <items id="description">Details über weitere Kliniker oder Organisationen, die eine Kopie der Analyseergebnisse benötigen.</items>
        <items id="comment">Die "Verteilerliste" dient nur zu Informationszwecken. Der Hauptempfänger des Berichts ist die Person, die dazu bestimmt ist, auf die Information zu reagieren.</items>
      </items>
      <items code="at0037">
        <items id="text">Teilweise</items>
        <items id="description">Das Testergebnis ist als ein Teilergebnis (z.B. Initial, vorübergehend oder vorläufig) bestätigt: Daten im Testergebnis können unvollständig oder nicht verifiziert sein.</items>
      </items>
      <items code="at0038">
        <items id="text">Final</items>
        <items id="description">Das Testergebnis ist vollständig und durch eine autorisierte Person bestätigt.</items>
      </items>
      <items code="at0040">
        <items id="text">Abgeändert</items>
        <items id="description">Das Ergebnis wurde nach der Finalisierung modifiziert und ist vollständig von dem verantwortlichen Untersucher verifiziert. Die Ergebnisdaten wurden geändert.</items>
      </items>
      <items code="at0057">
        <items id="text">Schlussfolgerung</items>
        <items id="description">Beschreibung der wichtigsten Ergebnisse.</items>
        <items id="comment">Zum Beispiel: "Das Muster lässt auf eine erhebliche Nierenfunktionsstörung schließen". Der Inhalt der Zusammenfassung unterscheidet sich je nach durchgeführter Untersuchung. Diese Zusammenfassung sollte mit der kodierten "Testdiagnose" übereinstimmen.</items>
      </items>
      <items code="at0062">
        <items id="text">Auftrags-ID des anfordernden/einsendenden Systems</items>
        <items id="description">Lokale Auftrags-ID des anfordernden/einsendenden Systems.</items>
        <items id="comment">Äquivalent zur "HL7 Placer Order Identifier".</items>
      </items>
      <items code="at0063">
        <items id="text">Auftrags-ID (Empfänger)</items>
        <items id="description">Lokale Auftrags-ID, die vom auftragsempfangendem System, gewöhnlich dem Laborinformationssystem (LIS) zugewiesen wird.</items>
        <items id="comment">Die Vergabe einer solchen ID ermöglicht das Nachverfolgen des Auftragsstatus und das Verlinken der Ergebnisse zum Auftrag. Es erlaubt auch das Verwalten von weiteren Erkundigungen und Nachfragen und ist äquivalent zum "HL7 Filler Order Identifier".</items>
      </items>
      <items code="at0065">
        <items id="text">Probendetail</items>
        <items id="description">Angaben über die Beschaffenheit der analysierten Probe.</items>
        <items id="comment">Wenn der Probentyp mit einem Code in der Testbezeichnung ausreichend spezifiziert ist, sind diese zusätzlichen Daten nicht erforderlich. Die Verknüpfung von Ergebnissen mit bestimmten Proben kann sowohl in einem CLUSTER.Probe als auch in den verschiedenen CLUSTER Archetypen mit Hilfe von Elementen mit der Bezeichnung "Probe" dokumentiert werden.</items>
      </items>
      <items code="at0068">
        <items id="text">Laborinterne Kennzeichnung</items>
        <items id="description">Eine lokale Kennung, die vom empfangenden Laborinformationssystem (LIS) vergeben wird, um den Testvorgang zu verfolgen.</items>
        <items id="comment">Diese Kennung ist eine vom LIS vergebene interne Trackingnummer und ist nicht als Bezeichnung für den Test gedacht.</items>
      </items>
      <items code="at0073">
        <items id="text">Gesamtteststatus</items>
        <items id="description">Der Status des gesamten Laborprüfergebnisses.</items>
        <items id="comment">Die Werte wurden so ausgewählt, dass sie mit denen im HL7 FHIR Diagnosebericht übereinstimmen, der historisch aus der HL7v2Praxis stammt. Andere lokale Codes/Begriffe können über den Text "Auswahl" verwendet werden. &#xD;
&#xD;
Dieses Element kann mehrfach vorkommen, um Fälle abzudecken, bei denen der Status für verschiedene Aspekte des Ergebnisses in mehrere Elemente unterteilt wurde.</items>
      </items>
      <items code="at0074">
        <items id="text">Abgebrochen</items>
        <items id="description">Das Ergebnis ist nicht verfügbar, weil der Test nicht gestartet oder nicht abgeschlossen wurde (manchmal auch als "gescheitert" bezeichnet).</items>
      </items>
      <items code="at0075">
        <items id="text">Zeitstempel des gesamten Teststatus</items>
        <items id="description">Zeitpunkt an dem das Ergebnis für den oben genannten "Gesamtteststatus" ausgegeben wurde.</items>
      </items>
      <items code="at0077">
        <items id="text">Diagnostische Organisationseinheit</items>
        <items id="description">Die diagnostische Organisationseinheit oder die Labordisziplin, die für das Laborergebnis verantwortlich ist.</items>
        <items id="comment">Dies soll eine allgemeine Kategorisierung sein und nicht den organisatorischen Namen des Labors erfassen. Zum Beispiel anatomische Pathologie, Immunologie und Transfusionsmedizin, medizinische Mikrobiologie, klinische Pharmakologie, medizinische Genetik, medizinische Biochemie. Alternativ noch granuläre Subkategorien, wie z.B. Hormone/Endokrinologie, Hämatologie, Autoantikörper, Allergologie. Diese Datenelemente helfen bei der Filterung nach breiten Kategorien von Ergebnissen gemäß den lokalen Gegebenheiten. Dieses Datenelement sollte, wenn möglich, mit einer Terminologie kodiert werden.</items>
      </items>
      <items code="at0090">
        <items id="text">Einsender</items>
        <items id="description">Details über den Kliniker oder die Abteilung, die das Labortestergebnis angefordert hat.</items>
      </items>
      <items code="at0094">
        <items id="text">Details der Testanforderung</items>
        <items id="description">Details zur Testanforderung.</items>
        <items id="comment">In den meisten Fällen gibt es eine Testanfrage und ein einzelnes entsprechendes Testergebnis. Jedoch ermöglicht dieser wiederholte Cluster die Situation, dass mehrere Testanfragen mit einem einzigen Testergebnis gemeldet werden können.&#xD;
&#xD;
Als Beispiel: "Ein Arzt fordert in einer Anfrage Blutzucker und in einer zweiten Anfrage Harnstoff/Elektrolyte an, aber das Laboranalysegerät führt beides durch und das Labor möchte diese zusammen melden".</items>
      </items>
      <items code="at0097">
        <items id="text">Testergebnis</items>
        <items id="description">Ergebnisse der durchgeführten Untersuchungen an der/den Probe(n).</items>
        <items id="comment">Dieser SLOT kann einen einzelnen Analyt, eine Gruppe, ein Panel oder eine Reihe von mehreren Analyten oder eine komplexere und spezifischere Struktur tragen.</items>
      </items>
      <items code="at0098">
        <items id="text">Testdiagnose</items>
        <items id="description">Kurze Beschreibung der klinischen Bedeutung und der Aussagekraft des Laborergebnisses.</items>
        <items id="comment">Zum Beispiel: "Schwere hepatische Beeinträchtigung", "Salmonellenbefall". Die Kodierung der Diagnose mit einer Terminologie, wird nach Möglichkeit dringend empfohlen. Die Diagnose soll zu der Beschreibung im Datenelement "Zusammenfassung" passen.</items>
      </items>
      <items code="at0100">
        <items id="text">Vorhandene klinische Information</items>
        <items id="description">Beschreibung der klinischen Informationen, die zum Zeitpunkt der Auswertung der Ergebnisse verfügbar sind.</items>
        <items id="comment">Dieses Datenelement kann einen Link zu den ursprünglichen klinischen Informationen enthalten, die in der Testanforderung angegeben sind.</items>
      </items>
      <items code="at0101">
        <items id="text">Kommentar</items>
        <items id="description">Weitere Informationen über das Laborergebnis, welche bisher nicht in den anderen Feldern erfasst wurden.</items>
      </items>
      <items code="at0106">
        <items id="text">Originaler Name der angeforderten Testung</items>
        <items id="description">Name des ursprünglich angeforderten Tests.</items>
        <items id="comment">Dieses Datenelement ist zu verwenden, wenn die angeforderte Testung von der tatsächlich vom Labor durchgeführten Testung abweicht.</items>
      </items>
      <items code="at0107">
        <items id="text">Registriert</items>
        <items id="description">Der Labortest wurde im Laborinformationssystem registriert, aber es ist derzeit noch nichts verfügbar.</items>
      </items>
      <items code="at0110">
        <items id="text">Test Details</items>
        <items id="description">Strukturierte Details über die beim Labortest verwendete Methodik, das Gerät oder die Auswertung.</items>
        <items id="comment">Zum Beispiel: "Details der ELISA/Nephelometrie".</items>
      </items>
      <items code="at0111">
        <items id="text">Point-of-care Test</items>
        <items id="description">Dies gibt an, ob der Test direkt am Point-of-Care (POCT) durchgeführt wurde, im Gegensatz zu einem formalen Ergebnis eines Labors oder einer anderen Dienstleistungsorganisation.</items>
        <items id="comment">Wahr, wenn der Test direkt am Point-of-Care (POCT) durchgeführt wurde.</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Störfaktoren</items>
        <items id="description">Probleme oder Umstände, die sich auf die genaue Interpretation der Messung oder des Testergebnisses auswirken.</items>
        <items id="comment">"Störfaktoren", die die Interpretation beeinflussen könnten wie z.B. "kürzliches Training" oder "neuer Tabakkonsum" sollten für unkontrollierte/ungeplante Probleme des Patientenzustands/ der Physiologie vorgesehen werden.&#xD;
&#xD;
Bekannte oder erforderliche Voraussetzungen, wie z.B. "Fasten", sollten im Element "Probenbedingungen" innerhalb des CLUSTER.Probe-Archetyps aufgeführt werden. In einigen Fällen werden Voraussetzungen als Teil des Testnamens erfasst, z.B. "Nüchternblutzucker".&#xD;
&#xD;
Bekannte Schwierigkeiten bei der Probenentnahme oder -behandlung, wie z.B. die "verlängerte Anwendung von Tourniquet" oder "hämolysierte Probe", sollten in den Elementen "Probenqualität" innerhalb des CLUSTER.Probe-Archetyps aufgeführt werden.</items>
      </items>
      <items code="at0114">
        <items id="text">Strukturierte Erfassung der Störfaktoren</items>
        <items id="description">Einzelheiten zu Problemen oder Umständen, die sich auf die genaue Interpretation der Messung oder des Prüfergebnisses auswirken.</items>
        <items id="comment">Zum Beispiel: Letzte normale Menstruationsperiode (LNMP).</items>
      </items>
      <items code="at0115">
        <items id="text">Korrigiert</items>
        <items id="description">Das Ergebnis wurde nach der Finalisierung modifiziert und ist vollständig vom verantwortlichen Untersucher verifiziert. Dies ist eine Unterkategorie von "Abgeändert".</items>
      </items>
      <items code="at0116">
        <items id="text">Irrtümlich eingegeben</items>
        <items id="description">Das Testergebnis wurde nach der vorherigen Endfreigabe zurückgezogen.</items>
      </items>
      <items code="at0117">
        <items id="text">Erweiterung</items>
        <items id="description">Weitere Informationen, die erforderlich sind, um lokale Inhalte abzubilden oder das Modell an andere Referenzmodelle anzupassen.</items>
        <items id="comment">Zum Beispiel: Lokaler Informationsbedarf oder zusätzliche Metadaten, um ein Mapping auf FHIR oder CIMI Modelle zu ermöglichen.</items>
      </items>
      <items code="at0118">
        <items id="text">Multimedia-Darstellung</items>
        <items id="description">Bild, Video oder Diagramm zur Visualisierung des Testergebnisses.</items>
        <items id="comment">Mehrere Formate sind erlaubt - diese sollten aber einen äquivalenten klinischen Inhalt darstellen.</items>
      </items>
      <items code="at0119">
        <items id="text">Hinzugefügt</items>
        <items id="description">Nach der endgültigen Fassung wurde der Bericht durch Hinzufügen neuer Inhalte aktualisiert. Der bestehende Inhalt bleibt unverändert. Dies ist eine Unterkategorie von "Abgeändert".</items>
      </items>
      <items code="at0120">
        <items id="text">Vorläufig</items>
        <items id="description">Es sind erste, bestätigte Ergebnisse verfügbar, aber nicht alle Ergebnisse sind final. Dies ist eine Unterkategorie von "Teilweise".</items>
      </items>
      <items code="at0121">
        <items id="text">Testmethode</items>
        <items id="description">Die Beschreibung der Methode, mit dem der Test durchgeführt wurde.</items>
        <items id="comment">Wenn möglich, ist eine Kodierung mit einer Terminologie wünschenswert.</items>
      </items>
      <items code="at0122">
        <items id="text">Strukturierte Testdiagnostik</items>
        <items id="description">Eine strukturierte oder komplexe Diagnose für die Laboruntersuchung.</items>
        <items id="comment">Zum Beispiel: Anatomische Pathologiediagnosen, die aus mehreren verschiedenen Schwerpunkten wie Morphologie, Ätiologie und Funktion zusammengesetzt sind.</items>
      </items>
    </term_definitions>
    <term_definitions language="it">
      <items code="at0000">
        <items id="text">Risultato di esame di laboratorio</items>
        <items id="description">L'esito, inclusi i risultati e l'interpretazione, di una indagine di laboratorio effettuata su campioni provenienti da individui o relativi materiali.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Qualunque evento</items>
        <items id="description">Predefinito, non specificato istante o intervallo di tempo, che può essere esplicitamente dettagliato in un template o in esecuzione (tempo reale)</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Nome dell'esame</items>
        <items id="description">Nome dell' indagine di laboratorio effettuata sul campione/i.</items>
        <items id="comment">Il risultato di un esame può essere relativo ad un singolo analita, oppure and un gruppo di elementi, inclusi i panel test. Si raccomanda vivamente di codificare il nome dell'esame tramite utilizzo di una terminologia, come ad esempio LOINC o SNOMED CT. Ad esempio: 'Glucosio', 'Urea ed elettroliti', 'Tampone', 'Cortisolo (am)', 'Potassio nella traspirazione' o 'Istopatologia del melanoma'. Il nome può talvolta includere il tipo di campione e lo stato del paziente, ad esempio 'Glucosio a digiuno' o includere altre informazioni, come 'Potassio (gas sanguigni PNA).</items>
      </items>
      <items code="at0017">
        <items id="text">Laboratorio ricevente</items>
        <items id="description">Dettagli riguardanti il laboratorio che ha ricevuto la richiesta ed ha la piena responsabilità di gestione del risultato dell'esame, anche nel caso in cui altri laboratori abbiano  eseguito specifiche parti.</items>
        <items id="comment">Questo campo viene utilizzato per indicare i dettagli riguardanti il laboratorio che ha ricevuto la richiesta ed ha la piena responsabilità di gestione del risultato dell'esame, anche nel caso  in cui altri laboratori ne abbiano eseguito delle specifiche parti. Il laboratorio ricevente potrebbe sia effettuare l'esame, oppure delegarlo verso un altro laboratorio. Quando un altro laboratorio è responsabile dell'esecuzione del test su degli specifici analiti, ci si aspetta che  i relativi dettagli vengano riportati nello SLOT "Dettagli del risultato dell'analita", all'interno dell'archetipo CLUSTER.laboratory_test_analyte.</items>
      </items>
      <items code="at0035">
        <items id="text">Lista di distribuzione</items>
        <items id="description">Dettagli su eventuale altro personale sanitario o organismi che hanno richiesto una copia del risultato dell'esame.</items>
        <items id="comment">La "Lista di distribuzione" ha soltanto scopo informativo, ed il destinatario principale della lista è la persona ritenuta quella preposta ad agire sulle informazioni.</items>
      </items>
      <items code="at0037">
        <items id="text">Parziale</items>
        <items id="description">E' un risltato parziale(iniziale, provvisorio o preliminare) dell'esame: la data nel risultato dell'esame potrebbe essere incompleta, oppure non verificata.</items>
      </items>
      <items code="at0038">
        <items id="text">Definitivo</items>
        <items id="description">Il risultato dell'esame è completo ed è stato verificato da una persona autorizzata.</items>
      </items>
      <items code="at0040">
        <items id="text">Modificato</items>
        <items id="description">Il risultato è stato modificato dopo essere stato dichiarato come Definitivo, ed è completo e verificato dal patologo responsabile e data dell'esito è stata cambiata.</items>
      </items>
      <items code="at0057">
        <items id="text">Conclusioni</items>
        <items id="description">Descrizione relativa agli esiti principali.</items>
        <items id="comment">Per esempio: "l'esito indica una significativa compromissione renale". Il contenuto delle conclusioni può variare, a seconda dell'indagine effettuata. Queste conclusioni dovrebbero essere allineate con quanto riportato nel campo "Diagnosi dell'esame".</items>
      </items>
      <items code="at0062">
        <items id="text">Identificativo del richiedente l'ordine</items>
        <items id="description">ID locale assegnato all'ordine dell'esame dal sistema che lo ha richiesto</items>
        <items id="comment">E' equivalente al campo HL7 "Placer Order Identifier"</items>
      </items>
      <items code="at0063">
        <items id="text">Identificativo del ricevente l'ordine</items>
        <items id="description">Identificativo locale assegnato all'ordine dell'esame dall'order filler, solitamente dal Sistema Informativo di Laboratorio (LIS).</items>
        <items id="comment">L'identificativo assegnato alla richiesta dal Sistema Informativo di Laboratorio (LIS) permette di tracciare lo stato di avanzamento della richiesta e di associare i risultati alle richieste. Fornisce anche un riferimento utile nelle indagini e di solito è equivalente al campo HL7 "Filler Order Identifier".</items>
      </items>
      <items code="at0065">
        <items id="text">Dettagli sul campione</items>
        <items id="description">Dettagli sulla sostanza fisica che è stata analizzata.</items>
        <items id="comment">Se il tipo del campione è specificato in maniera esaustiva all'interno del nome dell'esame, allora non è richiesto alcun dettaglio. Nel caso di campioni multipli, questi possono essere rappresentati mediante "gruppo di risultati" ("Result group").</items>
      </items>
      <items code="at0068">
        <items id="text">Identificativo interno del laboratorio</items>
        <items id="description">Identificativo locale assegnato dal Sistema Informativo di Laboratorio (LIS) ricevente, allo scopo di tracciare il processo dell'esame.</items>
        <items id="comment">Questo identivicativo è un numero di tracciabilità interno assegnato dal LIS, e non il nome dell'esame.</items>
      </items>
      <items code="at0073">
        <items id="text">Stato complessivo dell'esame</items>
        <items id="description">Lo stato relativo all'esame di laboratorio nel suo complesso.</items>
        <items id="comment">I valori sono stati specificatamente scelti in moto tale da corrispondere a quelli del "FHIR Diagnostic Report" di HL7, a loro volta storicamente derivanti dal HL7 v2. Altre codifiche/terminologie locali possono essere utilizzare tramite la scelta "Text". Questo elemento ha occorrenze multiple al fine di soddisfare le esigenze di quegli use case in cui gli stati relativi a differenti aspetti del risultato sono stati divisi in più componenti.</items>
      </items>
      <items code="at0074">
        <items id="text">Cancellato</items>
        <items id="description">Il risultato non è disponibile perché il test non è stato avviato o non è stato completato (talvolta chiamato anche 'abortito').</items>
      </items>
      <items code="at0075">
        <items id="text">Timestamp dello stato generale del test</items>
        <items id="description">La data e/o l'ora in cui è stato rilasciato lo "Stato complessivo dell'esame".</items>
      </items>
      <items code="at0077">
        <items id="text">Categoria di servizio diagnostico</items>
        <items id="description">Il servizio diagnostico o la disciplina che è responsabile del risultato del test di laboratorio.</items>
        <items id="comment">Questa vuole essere una categorizzazione generale e non registrare il nome organizzativo del laboratorio. Per esempio: anatomia patologica, immunologia e medicina trasfusionale, microbiologia medica, farmacologia clinica, genetica medica, biochimica medica. In alternativa possono essere utilizzate sottocategorie o sottodiscipline più granulari, come endocrinologia, ematologia e servizi di allergologia. Questo può aiutare i medici a filtrare tra le categorie di risultati. La codifica con una terminologia è auspicabile, ove possibile.</items>
      </items>
      <items code="at0090">
        <items id="text">Richiedente</items>
        <items id="description">Dettagli del clinico o dell'organizzazione che richiede il risultato dell'esame di laboratorio.</items>
      </items>
      <items code="at0094">
        <items id="text">Dettagli della richiesta di test</items>
        <items id="description">Dettagli sulla richiesta di test.</items>
        <items id="comment">Nella maggior parte delle situazioni c'è una richiesta di test e un singolo risultato di test corrispondente, tuttavia questo cluster di ripetizione permette la situazione in cui ci possano essere richieste di test multipli segnalati utilizzando un singolo risultato di test.&#xD;
&#xD;
Come esempio: "un clinico chiede il glucosio nel sangue in una richiesta e gli urei/elettroliti in una seconda richiesta, ma l'analizzatore di laboratorio fa entrambe le cose e il laboratorio desidera riportare queste richieste insieme".</items>
      </items>
      <items code="at0097">
        <items id="text">Risultati del test</items>
        <items id="description">Risultati del test eseguito sul campione o sui campioni.</items>
        <items id="comment">Questo SLOT può riportare un singolo analita, un gruppo, un pannello o una batteria di più analiti, o una struttura più complessa e specifica.</items>
      </items>
      <items code="at0098">
        <items id="text">Diagnosi del test</items>
        <items id="description">Singola parola, frase o breve descrizione che rappresenta il significato clinico e la significatività del risultato del test di laboratorio.</items>
        <items id="comment">Per esempio: 'Grave insufficienza epatica', 'Contaminazione da Salmonella'. Si raccomanda vivamente, ove possibile, di codificare la diagnosi con una terminologia. Questa diagnosi dovrebbe essere allineata con la narrazione nella 'Conclusione'.</items>
      </items>
      <items code="at0100">
        <items id="text">Informazioni cliniche fornite</items>
        <items id="description">Descrizione delle informazioni cliniche disponibili al momento dell'interpretazione dei risultati.</items>
        <items id="comment">Questo elemento di dati può includere un link alle informazioni cliniche originali fornite nella richiesta di test.</items>
      </items>
      <items code="at0101">
        <items id="text">Commento</items>
        <items id="description">Narrativa aggiuntiva sul risultato del test non catturato in altri campi.</items>
      </items>
      <items code="at0106">
        <items id="text">Nome del test originale richiesto</items>
        <items id="description">Nome del test di laboratorio originale richiesto.</items>
        <items id="comment">Questo elemento deve essere utilizzato quando il test richiesto differisce da quello effettivamente eseguito dal laboratorio.</items>
      </items>
      <items code="at0107">
        <items id="text">Registrato</items>
        <items id="description">L'esistenza del test è registrata nel Sistema Informativo di Laboratorio, ma non c'è ancora nulla di disponibile.</items>
      </items>
      <items code="at0110">
        <items id="text">Dettagli del test</items>
        <items id="description">Dettagli strutturati sul metodo utilizzato relativamente ad analisi, dispositivi o interpretazione.</items>
        <items id="comment">Ad esempio: 'dettagli di ELISA/nefelometria'.</items>
      </items>
      <items code="at0111">
        <items id="text">Test al punto di assistenza</items>
        <items id="description">Questo elemento indica se il test è stato eseguito direttamente presso il punto di assistenza (Point-of-Care, POCT), rispetto a un risultato formale di un laboratorio o di un'altra organizzazione che fornisce servizi.</items>
        <items id="comment">Vero se il test è stato eseguito direttamente al punto di assistenza (Point-of-Care, POCT).</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Fattori di confusione</items>
        <items id="description">Problemi o circostanze che influiscono sull'interpretazione accurata del risultato della misurazione o del test.</items>
        <items id="comment">I "fattori di confusione" dovrebbero essere riservati a questioni incontrollate/non pianificate di stato del paziente/fisiologia che potrebbero influenzare l'interpretazione, ad esempio "esercizio fisico recente" o "fumo di tabacco recente".&#xD;
&#xD;
Le precondizioni conosciute o richieste, come ad esempio il "digiuno", dovrebbero essere riportati nell'elemento "Condizioni di campionamento" all'interno dell'archetipo CLUSTER.specimen archetype. In alcuni casi le precondizioni vengono catturate come parte del nome del test, ad esempio "Glucosio nel sangue a digiuno".&#xD;
&#xD;
Problemi noti di raccolta o manipolazione dei campioni, come "uso prolungato del laccio emostatico" o "campione emolizzato", devono essere riportati negli elementi "Qualità del campione" all'interno di CLUSTER.specimen archetype.&#xD;
Ove possibile, è auspicabile una codifica con una terminologia.</items>
      </items>
      <items code="at0114">
        <items id="text">Fattori di confusione strutturati</items>
        <items id="description">Dettagli dello stato del paziente che possono alterare l'interpretazione del test di laboratorio.</items>
        <items id="comment">Per esempio: Ultimo periodo mestruale normale (Last Normal Menstrual Period, LNMP).</items>
      </items>
      <items code="at0115">
        <items id="text">Corretto</items>
        <items id="description">Il risultato è stato modificato in seguito all'essere stato dichiarato definitivo, ed è completo e verificato dal patologo responsabile. Questa è una sottocategoria di "Modificato"</items>
      </items>
      <items code="at0116">
        <items id="text">Inserito in errore</items>
        <items id="description">Il Risultato del Test è stato ritirato dopo un precedente rilascio Finale.</items>
      </items>
      <items code="at0117">
        <items id="text">Estensione</items>
        <items id="description">Informazioni aggiuntive necessarie per acquisire contenuti locali o per allinearsi con altri modelli/formalismi di riferimento.</items>
        <items id="comment">Ad esempio: requisiti informativi locali o metadati aggiuntivi per allinearsi agli equivalenti FHIR o CIMI.</items>
      </items>
      <items code="at0118">
        <items id="text">Rappresentazione multimediale</items>
        <items id="description">Immagine digitale, video o diagramma che rappresenta il risultato del test.</items>
        <items id="comment">Sono consentiti più formati, ma dovrebbero rappresentare un contenuto clinico equivalente.</items>
      </items>
      <items code="at0119">
        <items id="text">Addizionato</items>
        <items id="description">Dopo essere stato dichiarato definitivo, il rapporto è stato modificato con l'aggiunta di nuovi contenuti. Il contenuto pre-esistente è rimasto invariato. Questa è una sottocategoria di "Modificato".</items>
      </items>
      <items code="at0120">
        <items id="text">Preliminare</items>
        <items id="description">I primi risultati verificati sono disponibili, ma non tutti i risultati sono definitivi. Questa è una sottocategoria di 'Parziale'.</items>
      </items>
      <items code="at0121">
        <items id="text">Metodo di test</items>
        <items id="description">Descrizione del metodo utilizzato per eseguire il test.</items>
        <items id="comment">E' auspicabile, ove possibile, codificare con una terminologia.</items>
      </items>
      <items code="at0122">
        <items id="text">Diagnosi strutturata per il test</items>
        <items id="description">Una diagnosi strutturata o complessa per il test di laboratorio.</items>
        <items id="comment">Per esempio: Le diagnosi di anatomia patologica che consistono in molteplici assi diversi, come la morfologia, l'eziologia e la funzione.</items>
      </items>
    </term_definitions>
    <term_definitions language="nl">
      <items code="at0000">
        <items id="text">*Laboratory test result(en)</items>
        <items id="description">*The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">*Any event(en)</items>
        <items id="description">*Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Naam van de Test</items>
        <items id="description">Naam van het laboratorium onderzoek dat vericht is op het specimen.</items>
      </items>
      <items code="at0017">
        <items id="text">*Receiving laboratory(en)</items>
        <items id="description">*Details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.(en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Distribution list(en)</items>
        <items id="description">*Details of additional clinicians or organisations who require a copy of the test result.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Partial(en)</items>
        <items id="description">*This is a partial (e.g. initial, interim or preliminary) Test Result: data in the Test Result may be incomplete or unverified.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Final(en)</items>
        <items id="description">*The Test result is complete and verified by an authorised person.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Amended(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist, and result data has been changed.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">*Conclusion(en)</items>
        <items id="description">*Narrative description of the key findings.(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Requester order identifier(en)</items>
        <items id="description">*The local identifier assigned by the requesting clinical system.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Receiver order identifier(en)</items>
        <items id="description">*The local identifier assigned to the test order by the order filler, usually by the Laboratory Information System (LIS).(en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Specimen detail(en)</items>
        <items id="description">*Details about the physical substance that has been analysed.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Laboratory internal identifier(en)</items>
        <items id="description">*A local identifier assigned by the receiving Laboratory Information System (LIS) to track the test process.(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Overall test status(en)</items>
        <items id="description">*The status of the laboratory test result as a whole.(en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Cancelled(en)</items>
        <items id="description">*The result is unavailable because the test was not started or not completed (also sometimes called 'aborted').(en)</items>
      </items>
      <items code="at0075">
        <items id="text">*Overall test status timestamp(en)</items>
        <items id="description">*The date and/or time that ‘Overall test status’ was issued.(en)</items>
      </items>
      <items code="at0077">
        <items id="text">*Diagnostic service category(en)</items>
        <items id="description">*The diagnostic service or discipline that is responsible for the laboratory test result.(en)</items>
      </items>
      <items code="at0090">
        <items id="text">*Requester(en)</items>
        <items id="description">*Details of the clinician or organisation requesting the laboratory test result.(en)</items>
      </items>
      <items code="at0094">
        <items id="text">*Test request details(en)</items>
        <items id="description">*Details about the test request.(en)</items>
      </items>
      <items code="at0097">
        <items id="text">*Test result(en)</items>
        <items id="description">*Results of the test performed on the specimen(s).(en)</items>
      </items>
      <items code="at0098">
        <items id="text">*Test diagnosis(en)</items>
        <items id="description">*Single word, phrase or brief description that represents the clinical meaning and significance of the laboratory test result.(en)</items>
      </items>
      <items code="at0100">
        <items id="text">*Clinical information provided(en)</items>
        <items id="description">*Description of clinical information available at the time of interpretation of results.(en)</items>
      </items>
      <items code="at0101">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the test result not captured in other fields.(en)</items>
      </items>
      <items code="at0106">
        <items id="text">*Original test requested name(en)</items>
        <items id="description">*Name of the original laboratory test requested.(en)</items>
      </items>
      <items code="at0107">
        <items id="text">*Registered(en)</items>
        <items id="description">*The existence of the test is registered in the Laboratory Information System, but there is nothing yet available.(en)</items>
      </items>
      <items code="at0110">
        <items id="text">*Testing details(en)</items>
        <items id="description">*Structured details about the method of analysis, device or interpretation used.(en)</items>
      </items>
      <items code="at0111">
        <items id="text">*Point-of-care test(en)</items>
        <items id="description">*This indicates whether the test was performed directly at Point-of-Care (POCT) as opposed to a formal result from a laboratory or other service delivery organisation.(en)</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">*Confounding factors(en)</items>
        <items id="description">*Issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
      </items>
      <items code="at0114">
        <items id="text">*Structured confounding factors(en)</items>
        <items id="description">*Details of issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
      </items>
      <items code="at0115">
        <items id="text">*Corrected(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0116">
        <items id="text">*Entered in error(en)</items>
        <items id="description">*The Test Result has been withdrawn following previous Final release.(en)</items>
      </items>
      <items code="at0117">
        <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>
      <items code="at0118">
        <items id="text">*Multimedia representation(en)</items>
        <items id="description">*Digital image, video or diagram representing the test result.(en)</items>
      </items>
      <items code="at0119">
        <items id="text">*Appended(en)</items>
        <items id="description">*Subsequent to being final, the report has been modified by adding new content. The existing content is unchanged. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0120">
        <items id="text">*Preliminary(en)</items>
        <items id="description">*Verified early results are available, but not all results are final. This is a sub-category of 'Partial'.(en)</items>
      </items>
      <items code="at0121">
        <items id="text">*Test method(en)</items>
        <items id="description">*Description about the method used to perform the test.(en)</items>
      </items>
      <items code="at0122">
        <items id="text">*Structured test diagnosis(en)</items>
        <items id="description">*A structured or complex diagnosis for the laboratory test.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="sv">
      <items code="at0000">
        <items id="text">Laboratorieresultat</items>
        <items id="description">Resultatet av en undersökning, inklusive fynd och laboratoriets tolkning, utförd på provmaterial från en individ eller relaterad till individen. Exempel på provmaterial relaterat till individen kan vara fostervattenprov där provet tas från mammans kropp men provet avser fostret.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Ospecificerad händelse</items>
        <items id="description">Ospecificerad standardhändelse vid en tidpunkt eller inom ett tidsintervall som explicit kan definieras i en mall eller genereras automatiskt av vissa IT-system.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Undersökningsnamn</items>
        <items id="description">Namnet på den laboratorieundersökning eller -analys som utförts på provmaterialet.</items>
        <items id="comment">Undersökningsnamnet kan täcka ett enda resultat eller en grupp resultat. Analysnamnet kan kodas med medicinska kodningssystem som NPU, LOINC, SNOMED CT eller lokala laboratoriekodningssystem. Exempel kan vara "P-Glukos", "Blodgas", "Klorid i svett", "Kortisol (morgon)" eller "Histopatologi malignt melanom". Namnet kan ibland innehålla typen av provmaterial och patientstatus, såsom "fP-Glukos" eller innehålla annan information, såsom "pO2 (PNA-blodgas)".</items>
      </items>
      <items code="at0017">
        <items id="text">Ansvarigt laboratorium</items>
        <items id="description">Detaljer om det laboratorium som har mottagit beställningen och som har det övergripande ansvaret för att hantera rapporteringen av undersökningen, även om andra laboratorier utför specifika delar av beställningen.</items>
        <items id="comment">Denna SLOT är avsedd för detaljer om det laboratorium som har mottagit beställningen och som har det övergripande ansvaret för att lämna in en resultatrapport, även om andra laboratorier utför specifika delar av den.&#xD;
&#xD;
Det ansvariga laboratoriet kan antingen utföra undersökningarna själv eller vidarebefordra dem till andra laboratorier. Om ett annat laboratorium har utfört specifika undersökningar ska information om detta beskrivas i SLOT "Detaljer om analysresultat" i arketypen CLUSTER.laboratory_test_analyte.</items>
      </items>
      <items code="at0035">
        <items id="text">Distributionslista</items>
        <items id="description">Detaljer om ytterligare kliniker eller organisationer som behöver en kopia av undersökningsresultatet.</items>
        <items id="comment">Personerna eller organisationerna på distributionslistan får endast svaret för information, och det är huvudmottagaren av rapporten som förväntas agera på den.</items>
      </items>
      <items code="at0037">
        <items id="text">Partiell</items>
        <items id="description">Detta är ett partiellt undersökningsresultat, dvs. initialt, interim eller preliminärt. Resultatdata kan vara ofullständiga eller obekräftade.</items>
      </items>
      <items code="at0038">
        <items id="text">Slutgiltig</items>
        <items id="description">Undersökningsresultatet är fullständigt och verifierat av ansvarig person alternativt autoverifierat maskinellt.</items>
      </items>
      <items code="at0040">
        <items id="text">Reviderad</items>
        <items id="description">Det slutgiltiga undersökningsresultatet har reviderats. Denna status har underkategorierna "Rättad" och "Utökad".</items>
      </items>
      <items code="at0057">
        <items id="text">Tolkning av resultat</items>
        <items id="description">Berättande textuell beskrivning av de viktigaste resultaten.</items>
        <items id="comment">Till exempel "resultat indikerar signifikant nedsatt njurfunktion". Tolkningen av resultatet kommer att variera beroende på vilken undersökning som har genomförts. Slutsatsen ska vara i enlighet med de koder som används i dataelementet "Undersökningsdiagnos".</items>
      </items>
      <items code="at0062">
        <items id="text">Beställarens beställningsidentifierare</items>
        <items id="description">Den lokala identifierare som tilldelats av det begärande kliniska systemet.</items>
        <items id="comment">Denna identifierare benämns ofta som remissidentifierare, och motsvarar HL7 "Placer Order Identifier".</items>
      </items>
      <items code="at0063">
        <items id="text">Mottagarens beställningsidenitifierare</items>
        <items id="description">Den lokala identifierare som tilldelats beställningen av ordermottagningssystemet, vanligtvis av laboratorieinformationssystemet (LIS).</items>
        <items id="comment">Tilldelningen av en identifierare i LIS möjliggör spårning av beställningens status och länkning av resultaten till beställningen. Det tillåter också hantering av ytterligare förfrågningar och motsvarar "HL7 Filler Order Identifier".</items>
      </items>
      <items code="at0065">
        <items id="text">Detaljer om provmaterialet</items>
        <items id="description">Detaljer om det provmaterial som har analyserats.</items>
        <items id="comment">Om provmaterialet är tillräckligt specificerat med en kod i undersökningssnamnet är detta dataelement inte nödvändigt. Det är möjligt att länka svar till specifika prover med hjälp av dataelementen för prov-ID i både CLUSTER.Specimen och olika CLUSTER-arketyper för laboratoriesvar.</items>
      </items>
      <items code="at0068">
        <items id="text">Laboratoriets interna identifierare</items>
        <items id="description">En lokal identifierare som tilldelats av det mottagande laboratorieinformationssystemet (LIS) för att spåra analysprocessen.</items>
        <items id="comment">Denna identifierare är ett internt spårningsnummer som tilldelats av LIS och är inte avsett att vara namnet på undersökningen.</items>
      </items>
      <items code="at0073">
        <items id="text">Status undersökningsresultat</items>
        <items id="description">Status för undersökningsresultaten som helhet.</items>
        <items id="comment">Värdena har valts specifikt för att motsvara värdena i HL7 FHIR-resursen "Diagnostic Report", som historiskt kommer från HL7 v2. Andra lokala koder eller termer kan användas med datatypen "Fri eller kodad text".&#xD;
&#xD;
Detta element kan upprepas för att stödja applikationer där status för olika aspekter av resultatet delas in i flera element.</items>
      </items>
      <items code="at0074">
        <items id="text">Avbruten</items>
        <items id="description">Resultatet är inte tillgängligt eftersom undersökningen inte har startats eller inte slutförts.</items>
      </items>
      <items code="at0075">
        <items id="text">Tidpunkt för status undersökningsresultat</items>
        <items id="description">Datum och tid för utfärdandet av övergripande resultatstatus.</items>
      </items>
      <items code="at0077">
        <items id="text">Laboratoriedisciplin</items>
        <items id="description">Den diagnostiska organisationsenhet, laboratoriedisciplin eller underdisciplin som ansvarar för laboratorieresultatet.</items>
        <items id="comment">Detta är tänkt att vara en allmän kategorisering och inte att fånga laboratoriets interna organisation. Till exempel: patologi, immunologi och transfusionsmedicin, medicinsk mikrobiologi, klinisk farmakologi, medicinsk genetik, medicinsk biokemi. Alternativt kan mer detaljerade underkategorier eller underdiscipliner såsom endokrinologi, hematologi och allergologitjänster användas. Detta kan hjälpa kliniker att filtrera mellan resultatkategorier. Kodning med en terminologi är önskvärd, där det är möjligt.</items>
      </items>
      <items code="at0090">
        <items id="text">Beställare</items>
        <items id="description">Uppgifter om den kliniker eller organisation som beställt undersökningen.</items>
      </items>
      <items code="at0094">
        <items id="text">Beställningsdetaljer</items>
        <items id="description">Detaljer om beställningen.</items>
        <items id="comment">I de flesta situationer finns det en beställning och ett motsvarande svar, men under vissa omständigheter kan flera beställningar representeras med en enda arketyp för laboratorieresultat.&#xD;
&#xD;
Till exempel kan en kliniker beställa "glukos" och "urea och elektrolyter" i separata beställningar och laboratoriet utför båda analyserna, men skickar endast en övergripande resultatrapport.</items>
      </items>
      <items code="at0097">
        <items id="text">Undersökningsresultat</items>
        <items id="description">Resultatet av den undersökning eller analys som utförts på provmaterialet.</items>
        <items id="comment">Denna SLOT kan innehålla resultat för en enda analys, för en grupp analyser eller för en mer komplex och specifik struktur.</items>
      </items>
      <items code="at0098">
        <items id="text">Undersökningsdiagnos</items>
        <items id="description">Ett ord, en fras eller en kort beskrivning som representerar den kliniska betydelsen eller konsekvensen av laboratorietestresultatet.</items>
        <items id="comment">Till exempel: "Allvarligt nedsatt leverfunktion", "Akut hepatit B". Kodning med en terminologi är att föredra där det är möjligt. Undersökningsdiagnosen bör vara i enlighet med texten i "Tolkning av resultat".</items>
      </items>
      <items code="at0100">
        <items id="text">Tillgänglig klinisk information</items>
        <items id="description">Beskrivning av den kliniska information som finns tillgänglig vid tolkningen av resultaten.</items>
        <items id="comment">Detta dataelement kan innehålla en länk till den ursprungliga kliniska informationen i beställningen.</items>
      </items>
      <items code="at0101">
        <items id="text">Kommentar</items>
        <items id="description">Ytterligare textuell beskrivning som inte registrerats i andra fält.</items>
      </items>
      <items code="at0106">
        <items id="text">Ursprungligt undersökningsnamn</items>
        <items id="description">Namn på den ursprungligen beställda undersökningen eller analysen.</items>
        <items id="comment">Detta dataelement ska användas när den begärda undersökningen eller analysen skiljer sig från det som faktiskt har utförts av laboratoriet.</items>
      </items>
      <items code="at0107">
        <items id="text">Registrerad</items>
        <items id="description">Undersökningen är registrerad i laboratorieinformationssystemet, men resultatet finns för närvarande inte.</items>
      </items>
      <items code="at0110">
        <items id="text">Detaljer om undersökningsmetod</items>
        <items id="description">Strukturerade detaljer om undersökningsmetoden, utrustningen eller tolkningen.</items>
        <items id="comment">Exempelvis "detaljer om ELISA-analys".</items>
      </items>
      <items code="at0111">
        <items id="text">Patientnära analys</items>
        <items id="description">Indikerar om analysen utfördes som en patientnära analys (PNA), det vill säga på vårdenhet, istället för en mer formell laboratorietjänst.</items>
        <items id="comment">Sant om analysen utfördes genom patientnära analys (PNA).</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Möjliga felkällor</items>
        <items id="description">Villkor eller omständigheter som påverkar tolkningen av laboratorieresultatet.</items>
        <items id="comment">"Möjliga felkällor" bör reserveras för okontrollerade eller oplanerade förhållanden hos patienten som kan påverka tolkningen av laboratorieresultatet. Till exempel "nyligen fysisk aktivitet", "nyligen rökt tobak".&#xD;
&#xD;
Kända antaganden såsom "fasta" bör dokumenteras i dataelementet "Provtagningskontext" i arketypen CLUSTER.specimen. I vissa fall är sådana antaganden en del av studiens namn, såsom "Fastande blodglukos".&#xD;
&#xD;
Kända förhållanden relaterade till provtagning eller hantering av provet, såsom "förlängd stas" eller "hemolys" bör dokumenteras i elementet "Provkvalitet" i arketypen CLUSTER.specimen.&#xD;
&#xD;
Kodning med en terminologi är önskvärt där det är möjligt.</items>
      </items>
      <items code="at0114">
        <items id="text">Strukturerade möjliga felkällor</items>
        <items id="description">Mer information om problem eller omständigheter som kan påverka tolkningen av mätningen eller testresultatet.</items>
        <items id="comment">Till exempel den sista normala menstruationsperioden.</items>
      </items>
      <items code="at0115">
        <items id="text">Rättad</items>
        <items id="description">Det slutgiltiga undersökningsresultatet har rättats. Detta är en underkategori av "Reviderad".</items>
      </items>
      <items code="at0116">
        <items id="text">Felregistrerad</items>
        <items id="description">Undersökningsresultatet har dragits tillbaka efter att ha varit i status "Slutgiltig".</items>
      </items>
      <items code="at0117">
        <items id="text">Ytterligare information</items>
        <items id="description">Ytterligare information som krävs för att registrera lokalt definierat innehåll eller för anpassning till andra referensmodeller.</items>
        <items id="comment">Exempelvis lokala informationsbehov eller ytterligare metadata för att möjliggöra mappning till FHIR- eller CIMI-modeller.</items>
      </items>
      <items code="at0118">
        <items id="text">Multimedia</items>
        <items id="description">Digital bild, video eller diagram som representerar undersökningsresultatet.</items>
        <items id="comment">Flera format är tillåtna, men innehållet i de olika formaten måste representera samma kliniska innehåll.</items>
      </items>
      <items code="at0119">
        <items id="text">Utökat</items>
        <items id="description">Det slutgiltiga undersökningsresultatet har ändrats genom att nytt innehåll har inkluderats. Det befintliga innehållet är oförändrat. Detta är en underkategori av "Reviderad".</items>
      </items>
      <items code="at0120">
        <items id="text">Preliminär</items>
        <items id="description">Verifierade tidiga resultat är tillgängliga, men inte alla resultat är slutgiltiga. Detta är en underkategori av status "Partiell".</items>
      </items>
      <items code="at0121">
        <items id="text">Undersökningsmetod</items>
        <items id="description">Beskrivning av den metod som använts för att utföra undersökningen eller analysen.</items>
        <items id="comment">Kodning med en terminologi är önskvärt där det är möjligt.</items>
      </items>
      <items code="at0122">
        <items id="text">Strukturerad undersökningsdiagnos</items>
        <items id="description">En strukturerad eller komplex diagnos för laboratorieundersökningen.</items>
        <items id="comment">Exempelvis patologisk anatomisk diagnos bestående av flera olika komponenter som morfologi, etiologi och funktion.</items>
      </items>
    </term_definitions>
    <term_definitions language="pt-br">
      <items code="at0000">
        <items id="text">Resultado de exame de laboratório</items>
        <items id="description">O resultado, incluindo achados e a interpretação do laboratório, de uma investigação realizada em amostras coletadas de um indivíduo ou relacionadas a esse indivíduo.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">*Any event(en)</items>
        <items id="description">*Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">*Test name(en)</items>
        <items id="description">*Name of the laboratory investigation performed on the specimen(s).(en)</items>
        <items id="comment">*A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'.(en)</items>
      </items>
      <items code="at0017">
        <items id="text">*Receiving laboratory(en)</items>
        <items id="description">*Details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.(en)</items>
        <items id="comment">*This slot is intended to carry details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.&#xD;
&#xD;
The receiving laboratory may either perform the test or refer it to another laboratory. Where a different laboratory is responsible for performing the testing on specific analytes, it would be expected that these details would be carried in the 'Analyte result detail' SLOT within the CLUSTER.laboratory_test_analyte archetype.&#xD;
&#xD;
(en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Distribution list(en)</items>
        <items id="description">*Details of additional clinicians or organisations who require a copy of the test result.(en)</items>
        <items id="comment">*The 'Distribution list' is for information-only, and that the primary recipient of the report is the person intended to act on the information.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Partial(en)</items>
        <items id="description">*This is a partial (e.g. initial, interim or preliminary) Test Result: data in the Test Result may be incomplete or unverified.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Final(en)</items>
        <items id="description">*The Test result is complete and verified by an authorised person.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Amended(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist, and result data has been changed.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">*Conclusion(en)</items>
        <items id="description">*Narrative description of the key findings.(en)</items>
        <items id="comment">*For example: 'Pattern suggests significant renal impairment'. The content of the conclusion will vary, depending on the investigation performed. This conclusion should be aligned with the coded 'Test diagnosis'.(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Requester order identifier(en)</items>
        <items id="description">*The local identifier assigned by the requesting clinical system.(en)</items>
        <items id="comment">*Equivalent to the HL7 Placer Order Identifier.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Receiver order identifier(en)</items>
        <items id="description">*The local identifier assigned to the test order by the order filler, usually by the Laboratory Information System (LIS).(en)</items>
        <items id="comment">*Assigning an identifier to a request by the Laboratory lnformation System (LIS) enables tracking progress of the request and enables linking results to requests. It also provides a reference to assist with enquiries and it is usually equivalent to the HL7 Filler Order Identifier.(en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Specimen detail(en)</items>
        <items id="description">*Details about the physical substance that has been analysed.(en)</items>
        <items id="comment">*If the specimen type is sufficiently specified with a code in the Test name, then this additional data is not required. Linking results to specific specimens may be recorded using 'Specimen identifier' elements in both the CLUSTER.specimen and the various results CLUSTER archetypes.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Laboratory internal identifier(en)</items>
        <items id="description">*A local identifier assigned by the receiving Laboratory Information System (LIS) to track the test process.(en)</items>
        <items id="comment">*This identifier is an internal tracking number assigned by the LIS, and it not intended to be the name of the test.(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Overall test status(en)</items>
        <items id="description">*The status of the laboratory test result as a whole.(en)</items>
        <items id="comment">*The values have been specifically chosen to match those in the HL7 FHIR Diagnostic report, historically derived from HL7v2 practice. Other local codes/terms can be used via the Text 'choice'.&#xD;
&#xD;
This element is multiple occurrence to cater for the use cases where statuses for different aspects of the result have been split into several elements.(en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Cancelled(en)</items>
        <items id="description">*The result is unavailable because the test was not started or not completed (also sometimes called 'aborted').(en)</items>
      </items>
      <items code="at0075">
        <items id="text">*Overall test status timestamp(en)</items>
        <items id="description">*The date and/or time that ‘Overall test status’ was issued.(en)</items>
      </items>
      <items code="at0077">
        <items id="text">*Diagnostic service category(en)</items>
        <items id="description">*The diagnostic service or discipline that is responsible for the laboratory test result.(en)</items>
        <items id="comment">*This is intended to be a general categorisation and not to capture the organisational name of the laboratory. For example: anatomical pathology, immunology and transfusion medicine, medical microbiology, clinical pharmacology, medical genetics, medical biochemistry. Alternatively more granular sub categories or sub disciplines, such as endocrinology, haematology, and allergology services, may be used. This may assist clinicians in filtering between categories of results. Coding with a terminology is desirable, where possible.(en)</items>
      </items>
      <items code="at0090">
        <items id="text">*Requester(en)</items>
        <items id="description">*Details of the clinician or organisation requesting the laboratory test result.(en)</items>
      </items>
      <items code="at0094">
        <items id="text">*Test request details(en)</items>
        <items id="description">*Details about the test request.(en)</items>
        <items id="comment">*In most situations there is one test request and a single corresponding test result, however this repeating cluster allows for the situation where there may be multiple test requests reported using a single test result.&#xD;
&#xD;
As an example: 'a clinician asks for blood glucose in one request and Urea/electrolytes in a second request, but the lab analyser does both and the lab wishes to report these together'.(en)</items>
      </items>
      <items code="at0097">
        <items id="text">*Test result(en)</items>
        <items id="description">*Results of the test performed on the specimen(s).(en)</items>
        <items id="comment">*This SLOT may carry an individual analyte, a group, panel or battery of multiple analytes, or a more complex and specific structure.(en)</items>
      </items>
      <items code="at0098">
        <items id="text">*Test diagnosis(en)</items>
        <items id="description">*Single word, phrase or brief description that represents the clinical meaning and significance of the laboratory test result.(en)</items>
        <items id="comment">*For example: 'Severe hepatic impairment', 'Salmonella contamination'. Coding of the diagnosis with a terminology is strongly recommended, where possible. This diagnosis should be aligned with the narrative in the 'Conclusion'.(en)</items>
      </items>
      <items code="at0100">
        <items id="text">*Clinical information provided(en)</items>
        <items id="description">*Description of clinical information available at the time of interpretation of results.(en)</items>
        <items id="comment">*This data element may include a link to the original clinical information provided in the test request.(en)</items>
      </items>
      <items code="at0101">
        <items id="text">*Comment(en)</items>
        <items id="description">*Additional narrative about the test result not captured in other fields.(en)</items>
      </items>
      <items code="at0106">
        <items id="text">*Original test requested name(en)</items>
        <items id="description">*Name of the original laboratory test requested.(en)</items>
        <items id="comment">*This data element is to be used when the test requested differs from the test actually performed by the laboratory.(en)</items>
      </items>
      <items code="at0107">
        <items id="text">*Registered(en)</items>
        <items id="description">*The existence of the test is registered in the Laboratory Information System, but there is nothing yet available.(en)</items>
      </items>
      <items code="at0110">
        <items id="text">*Testing details(en)</items>
        <items id="description">*Structured details about the method of analysis, device or interpretation used.(en)</items>
        <items id="comment">*For example: 'details of ELISA/nephelometry'.(en)</items>
      </items>
      <items code="at0111">
        <items id="text">*Point-of-care test(en)</items>
        <items id="description">*This indicates whether the test was performed directly at Point-of-Care (POCT) as opposed to a formal result from a laboratory or other service delivery organisation.(en)</items>
        <items id="comment">*True if the test was performed directly at Point-of-Care (POCT).(en)</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">*Confounding factors(en)</items>
        <items id="description">*Issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
        <items id="comment">*'Confounding factors' should be reserved for uncontrolled/unplanned issues of patient state/physiology that might affect interpretation, for example 'recent exercise' or 'recent tobacco smoking'.&#xD;
&#xD;
Known or required preconditions, such as 'fasting' should be carried in the 'Sampling conditions' element within the CLUSTER.specimen archetype . In some cases preconditions are captured as part of the test name, for example 'Fasting blood glucose'.&#xD;
&#xD;
Known issues with specimen collection or handling, such as 'prolonged use of tourniquet' or 'sample haemolysed', should be carried in the 'Specimen quality' elements within CLUSTER.specimen archetype.&#xD;
&#xD;
Coding with a terminology is desirable, where possible.(en)</items>
      </items>
      <items code="at0114">
        <items id="text">*Structured confounding factors(en)</items>
        <items id="description">*Details of issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
        <items id="comment">*For example: Last Normal Menstrual Period (LNMP).(en)</items>
      </items>
      <items code="at0115">
        <items id="text">*Corrected(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0116">
        <items id="text">*Entered in error(en)</items>
        <items id="description">*The Test Result has been withdrawn following previous Final release.(en)</items>
      </items>
      <items code="at0117">
        <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 or CIMI equivalents.(en)</items>
      </items>
      <items code="at0118">
        <items id="text">*Multimedia representation(en)</items>
        <items id="description">*Digital image, video or diagram representing the test result.(en)</items>
        <items id="comment">*Multiple formats are allowed but they should represent equivalent clinical content.(en)</items>
      </items>
      <items code="at0119">
        <items id="text">*Appended(en)</items>
        <items id="description">*Subsequent to being final, the report has been modified by adding new content. The existing content is unchanged. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0120">
        <items id="text">*Preliminary(en)</items>
        <items id="description">*Verified early results are available, but not all results are final. This is a sub-category of 'Partial'.(en)</items>
      </items>
      <items code="at0121">
        <items id="text">*Test method(en)</items>
        <items id="description">*Description about the method used to perform the test.(en)</items>
        <items id="comment">*Coding with a terminology is desirable, where possible.(en)</items>
      </items>
      <items code="at0122">
        <items id="text">*Structured test diagnosis(en)</items>
        <items id="description">*A structured or complex diagnosis for the laboratory test.(en)</items>
        <items id="comment">*For example: Anatomical pathology diagnoses consisting of several different axes such as morphology, etiology and function.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="es">
      <items code="at0000">
        <items id="text">Resultado de pruebas de laboratorio</items>
        <items id="description">El resultado, incluidas las conclusiones y la interpretación del laboratorio, de una investigación realizada con muestras recogidas de una persona o relacionadas con ella.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Cualquier evento</items>
        <items id="description">Evento predeterminado, no especificado, en un punto del tiempo o intervalo que puede definirse explícitamente en una plantilla o en tiempo de ejecución.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Nombre de la prueba</items>
        <items id="description">Nombre de la investigación de laboratorio realizada en la(s) muestra(s).</items>
        <items id="comment">El resultado de una prueba puede corresponder a un único analito o a un grupo de elementos, incluidas las pruebas de panel. Se recomienda encarecidamente que "Nombre de la prueba" se codifique con una terminología, por ejemplo LOINC o SNOMED CT. Por ejemplo: "Glucosa", "Urea y electrolitos", "Hisopo", "Cortisol (am)", "Potasio en la transpiración" o "Histopatología del melanoma". El nombre puede incluir a veces el tipo de muestra y el estado del paciente, por ejemplo 'Glucosa en sangre en ayunas' o incluir otra información, como 'Potasio (gasometría PNA)'.</items>
      </items>
      <items code="at0017">
        <items id="text">Laboratorio receptor</items>
        <items id="description">Datos del laboratorio que ha recibido la solicitud y tiene la responsabilidad general de gestionar la notificación de la prueba, aunque otros laboratorios realicen aspectos específicos.</items>
        <items id="comment">Este slot está destinado a llevar los datos del laboratorio que recibió la solicitud y tiene la responsabilidad general de gestionar la notificación de la prueba, aunque otros laboratorios realicen aspectos específicos.&#xD;
&#xD;
El laboratorio receptor puede realizar la prueba o remitirla a otro laboratorio. En caso de que un laboratorio diferente sea responsable de realizar las pruebas de analitos específicos, se espera que estos datos se incluyan en el slot "Detalle del resultado del analito" del arquetipo CLUSTER.laboratory_test_analyte.</items>
      </items>
      <items code="at0035">
        <items id="text">Lista de distribución</items>
        <items id="description">Datos de otros médicos u organizaciones que necesiten una copia del resultado de la prueba.</items>
        <items id="comment">La "Lista de distribución" es meramente informativa, y el destinatario principal del informe es la persona destinada a actuar en función de la información.</items>
      </items>
      <items code="at0037">
        <items id="text">Parcial</items>
        <items id="description">Se trata de un resultado parcial (por ejemplo, inicial, provisional o preliminar): los datos del resultado pueden estar incompletos o sin verificar.</items>
      </items>
      <items code="at0038">
        <items id="text">Definitivo</items>
        <items id="description">El resultado de la prueba está completo y ha sido verificado por una persona autorizada.</items>
      </items>
      <items code="at0040">
        <items id="text">Modificado</items>
        <items id="description">El resultado ha sido modificado con posterioridad a ser Definitivo, y está completo y verificado por el patólogo responsable, y los datos del resultado han sido modificados.</items>
      </items>
      <items code="at0057">
        <items id="text">Conclusión</items>
        <items id="description">Descripción narrativa de las principales conclusiones.</items>
        <items id="comment">Por ejemplo: "El patrón sugiere una insuficiencia renal significativa". El contenido de la conclusión variará en función de la investigación realizada. Esta conclusión debe coincidir con el "Diagnóstico de la prueba" codificado.</items>
      </items>
      <items code="at0062">
        <items id="text">Identificador del pedido del solicitante</items>
        <items id="description">El identificador local asignado por el sistema clínico solicitante.</items>
        <items id="comment">Equivalente al Depósito de Identificador de Orden de HL7.</items>
      </items>
      <items code="at0063">
        <items id="text">Identificador de la orden del receptor</items>
        <items id="description">El identificador local asignado a la orden de prueba por el cumplimentador de la orden, normalmente por el Sistema de Información del Laboratorio (SIL).</items>
        <items id="comment">La asignación de un identificador a una solicitud por parte del Sistema de Información de Laboratorio (SIL) permite seguir el progreso de la solicitud y relacionar los resultados con las solicitudes. También proporciona una referencia para ayudar con las consultas y suele ser equivalente al identificador HL7 Filler Order Identifier.</items>
      </items>
      <items code="at0065">
        <items id="text">Detalles de la muestra</items>
        <items id="description">Datos sobre la sustancia física analizada.</items>
        <items id="comment">Si el tipo de muestra está suficientemente especificado con un código en el nombre de la prueba, estos datos adicionales no son necesarios. La vinculación de los resultados a muestras específicas puede registrarse utilizando elementos de "Identificador de muestra" tanto en CLUSTER.specimen como en los distintos arquetipos CLUSTER de resultados.</items>
      </items>
      <items code="at0068">
        <items id="text">Identificador interno del laboratorio</items>
        <items id="description">Identificador local asignado por el Sistema de Información del Laboratorio receptor (SIL) para seguir el proceso de la prueba.</items>
        <items id="comment">Este identificador es un número de seguimiento interno asignado por el SIL, y no pretende ser el nombre de la prueba.</items>
      </items>
      <items code="at0073">
        <items id="text">Estado general de las pruebas</items>
        <items id="description">El estado del resultado de la prueba de laboratorio en su conjunto.</items>
        <items id="comment">Los valores se han elegido específicamente para que coincidan con los del informe HL7 FHIR Diagnostic, derivados históricamente de la práctica HL7v2. Pueden utilizarse otros códigos/términos locales mediante el texto "choice".&#xD;
&#xD;
Este elemento es de ocurrencia múltiple para atender a los casos de uso en los que los estados para diferentes aspectos del resultado se han dividido en varios elementos.</items>
      </items>
      <items code="at0074">
        <items id="text">Cancelado</items>
        <items id="description">El resultado no está disponible porque la prueba no se ha iniciado o no se ha completado (a veces también se denomina "abortada").</items>
      </items>
      <items code="at0075">
        <items id="text">Registro de tiempo del estado general de la prueba</items>
        <items id="description">La fecha y/o la hora en que se emitió el "Estado general de las pruebas".</items>
      </items>
      <items code="at0077">
        <items id="text">Especialidad médica/clínica</items>
        <items id="description">El servicio o disciplina de diagnóstico responsable del resultado de la prueba de laboratorio.</items>
        <items id="comment">Se trata de una categorización general y no del nombre organizativo del laboratorio. Por ejemplo: anatomía patológica, inmunología y medicina transfusional, microbiología médica, farmacología clínica, genética médica, bioquímica médica. También pueden utilizarse subcategorías o subdisciplinas más granulares, como endocrinología, hematología y servicios de alergología. Esto puede ayudar a los clínicos a filtrar entre categorías de resultados. Siempre que sea posible, es deseable codificar con una terminología.</items>
      </items>
      <items code="at0090">
        <items id="text">Solicitante</items>
        <items id="description">Datos del clínico u organización que solicita el resultado de la prueba de laboratorio.</items>
      </items>
      <items code="at0094">
        <items id="text">Detalles de la solicitud de la prueba</items>
        <items id="description">Detalles sobre la solicitud de la prueba.</items>
        <items id="comment">En la mayoría de las situaciones hay una solicitud de prueba y un único resultado de prueba correspondiente, sin embargo, este grupo de repetición permite la situación en la que puede haber varias solicitudes de prueba notificadas utilizando un único resultado de prueba.&#xD;
&#xD;
Por ejemplo: "un clínico solicita glucosa en sangre en una petición y urea/electrolitos en una segunda petición, pero el técnico del laboratorio realiza ambas y el laboratorio desea notificarlas juntas".</items>
      </items>
      <items code="at0097">
        <items id="text">Resultado de la prueba</items>
        <items id="description">Resultados de la prueba realizada en la(s) muestra(s).</items>
        <items id="comment">Este SLOT puede transportar un analito individual, un grupo, panel o batería de múltiples analitos, o una estructura más compleja y específica.</items>
      </items>
      <items code="at0098">
        <items id="text">Dignóstico de la prueba</items>
        <items id="description">Palabra única, frase o breve descripción que representa el significado clínico y la importancia del resultado de la prueba de laboratorio.</items>
        <items id="comment">Por ejemplo: 'Insuficiencia hepática grave', 'Contaminación por Salmonella'. Se recomienda encarecidamente codificar el diagnóstico con una terminología, siempre que sea posible. Este diagnóstico debe estar alineado con la información registrada en la 'Conclusión'.</items>
      </items>
      <items code="at0100">
        <items id="text">Información clínica facilitada</items>
        <items id="description">Descripción de la información clínica disponible en el momento de la interpretación de los resultados.</items>
        <items id="comment">Este elemento de datos puede incluir un enlace a la información clínica original facilitada en la solicitud de prueba.</items>
      </items>
      <items code="at0101">
        <items id="text">Comentarios</items>
        <items id="description">Información adicional sobre el resultado de la prueba no recogida en otros campos.</items>
      </items>
      <items code="at0106">
        <items id="text">Nombre de la prueba original solicitada</items>
        <items id="description">Nombre de la prueba de laboratorio original solicitada.</items>
        <items id="comment">Este dato se utilizará cuando la prueba solicitada difiera de la prueba realmente realizada por el laboratorio.</items>
      </items>
      <items code="at0107">
        <items id="text">Registrado</items>
        <items id="description">La existencia de la prueba está registrada en el Sistema de Información del Laboratorio, pero aún no hay nada disponible.</items>
      </items>
      <items code="at0110">
        <items id="text">Detalles de la prueba</items>
        <items id="description">Detalles estructurados sobre el método de análisis, dispositivo o interpretación utilizado.</items>
        <items id="comment">Por ejemplo: 'detalles de ELISA/nefelometría'.</items>
      </items>
      <items code="at0111">
        <items id="text">Prueba en el punto de atención sanitaria</items>
        <items id="description">Indica si la prueba se realizó directamente en el punto de atención (POCT), en contraposición a un resultado formal de un laboratorio u otra organización de prestación de servicios.</items>
        <items id="comment">Verdadero si la prueba se realizó directamente en el punto de atención (POCT).</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Factores de confusión</items>
        <items id="description">Cuestiones o circunstancias que influyen en la interpretación exacta de la medición o del resultado de la prueba.</items>
        <items id="comment">Los "factores de confusión" deben reservarse para cuestiones no controladas/no planificadas del estado/fisiología del paciente que puedan afectar a la interpretación, por ejemplo "ejercicio reciente" o "tabaquismo reciente".&#xD;
&#xD;
Las condiciones previas conocidas o requeridas, como "ayuno", deben incluirse en el elemento "Condiciones de muestreo" del arquetipo CLUSTER.specimen. En algunos casos, las condiciones previas forman parte del nombre de la prueba, por ejemplo "Glucosa en sangre en ayunas".&#xD;
&#xD;
Los problemas conocidos de recogida o manipulación de muestras, como "uso prolongado de torniquete" o "muestra hemolizada", deben incluirse en los elementos "Calidad de la muestra" del arquetipo CLUSTER.specimen.&#xD;
&#xD;
Siempre que sea posible, es deseable codificar con una terminología.</items>
      </items>
      <items code="at0114">
        <items id="text">Factores de confusión estructurados</items>
        <items id="description">Detalles de los problemas o circunstancias que influyen en la interpretación exacta de la medición o del resultado del ensayo.</items>
        <items id="comment">Por ejemplo: Última menstruación normal (LNMP).</items>
      </items>
      <items code="at0115">
        <items id="text">Corregida</items>
        <items id="description">El resultado ha sido modificado con posterioridad a ser Definitivo, y está completo y verificado por el patólogo responsable. Se trata de una subcategoría de "Modificado".</items>
      </items>
      <items code="at0116">
        <items id="text">Añadido por error</items>
        <items id="description">El resultado de la prueba se ha retirado tras la publicación final anterior.</items>
      </items>
      <items code="at0117">
        <items id="text">Ampliación</items>
        <items id="description">Información adicional necesaria para captar el contenido local o para alinearse con otros modelos/formalismos de referencia.</items>
        <items id="comment">Por ejemplo: requisitos locales de información o metadatos adicionales para alinearse con los equivalentes de FHIR o CIMI.</items>
      </items>
      <items code="at0118">
        <items id="text">Representación multimedia</items>
        <items id="description">Imagen digital, vídeo o diagrama que representa el resultado de la prueba.</items>
        <items id="comment">Se permiten múltiples formatos, pero deben representar contenidos clínicos equivalentes.</items>
      </items>
      <items code="at0119">
        <items id="text">Anexo</items>
        <items id="description">Tras ser definitivo, el informe se ha modificado añadiendo nuevos contenidos. El contenido existente no se ha modificado. Se trata de una subcategoría de "Modificado".</items>
      </items>
      <items code="at0120">
        <items id="text">Preliminar</items>
        <items id="description">Se dispone de resultados preliminares verificados, pero no todos los resultados son definitivos. Se trata de una subcategoría de "Parcial".</items>
      </items>
      <items code="at0121">
        <items id="text">Método de prueba</items>
        <items id="description">Descripción del método utilizado para realizar la prueba.</items>
        <items id="comment">En la medida de lo posible, es deseable codificar con una terminología.</items>
      </items>
      <items code="at0122">
        <items id="text">Diagnóstico de prueba estructurado</items>
        <items id="description">Un diagnóstico estructurado o complejo para la prueba de laboratorio.</items>
        <items id="comment">Por ejemplo: Diagnósticos anatomopatológicos que constan de varios ejes diferentes, como la morfología, la etiología y la función.</items>
      </items>
    </term_definitions>
    <term_definitions language="ca">
      <items code="at0000">
        <items id="text">Resultat de proves de laboratori</items>
        <items id="description">El resultat, incloses les conclusions i la interpretació del laboratori, d'una investigació realitzada amb mostres recollides o relacionades amb una persona.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Qualsevol esdeveniment</items>
        <items id="description">Esdeveniment predeterminat, no especificat, en un punt del temps o interval que es pot definir explícitament en una plantilla o en temps d'execució.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Nom de la prova</items>
        <items id="description">Nom de la investigació de laboratori realitzada a la(es) mostra(s).</items>
        <items id="comment">El resultat d'una prova pot correspondre a un únic analit o grup d'elements, incloses les proves de panell. Es recomana que "Nom de la prova" es codifiqui amb una terminologia, per exemple LOINC o SNOMED CT. Per exemple: "Glucosa", "Urea i electròlits", "Hisop", "Cortisol (am)", "Potasi en la transpiració" o "Histopatologia del melanoma". El nom pot incloure de vegades el tipus de mostra i l'estat del pacient, per exemple 'Glucosa en sang en dejú' o incloure una altra informació, com 'Potasi (gasometria PNA)'.</items>
      </items>
      <items code="at0017">
        <items id="text">Laboratori receptor</items>
        <items id="description">Dades del laboratori que ha rebut la sol·licitud i té la responsabilitat general de gestionar la notificació de la prova, encara que altres laboratoris facin aspectes específics.</items>
        <items id="comment">Aquest slot està destinat a portar les dades del laboratori que va rebre la sol·licitud i té la responsabilitat general de gestionar la notificació de la prova, encara que altres laboratoris facin aspectes específics.&#xD;
&#xD;
El laboratori receptor pot fer la prova o remetre-la a un altre laboratori. En cas que un laboratori diferent sigui responsable de fer les proves d'analits específics, s'espera que aquestes dades s'incloguin a l'slot "Detall del resultat de l'analit" de l'arquetip CLUSTER.laboratory_test_analyte.</items>
      </items>
      <items code="at0035">
        <items id="text">Llista de distribució</items>
        <items id="description">Detalls de metges o organitzacions addicionals que requereixen una còpia del resultat de la prova.</items>
        <items id="comment">La "Llista de distribució" és merament informativa i el destinatari principal de l'informe és la persona destinada a actuar en funció de la informació.</items>
      </items>
      <items code="at0037">
        <items id="text">Parcial</items>
        <items id="description">És un resultat parcial (per exemple, inicial, provisional o preliminar): les dades del resultat poden estar incomplets o sense verificar.</items>
      </items>
      <items code="at0038">
        <items id="text">Definitiu</items>
        <items id="description">El resultat de la prova és complet i ha estat verificat per una persona autoritzada.</items>
      </items>
      <items code="at0040">
        <items id="text">Modificat</items>
        <items id="description">El resultat ha estat modificat amb posterioritat a ser definitiu, i està complet i verificat pel patòleg responsable, i les dades del resultat han estat modificades.</items>
      </items>
      <items code="at0057">
        <items id="text">Conclusió</items>
        <items id="description">Descripció narrativa de les conclusions principals.</items>
        <items id="comment">Per exemple: “El patró suggereix una insuficiència renal significativa”. El contingut de la conclusió variarà en funció de la investigació realitzada. Aquesta conclusió ha de coincidir amb el “Diagnòstic de la prova” codificat.</items>
      </items>
      <items code="at0062">
        <items id="text">Identificador de la comanda del sol·licitant</items>
        <items id="description">L'identificador local assignat pel sistema clínic sol·licitant.</items>
        <items id="comment">Equivalent al Dipòsit d'identificador d'ordre d'HL7.</items>
      </items>
      <items code="at0063">
        <items id="text">Identificador de l'ordre del receptor</items>
        <items id="description">L'identificador local assignat a l'ordre de prova per l'emplenador de l'ordre, normalment pel Sistema d'Informació del Laboratori (SIL).</items>
        <items id="comment">L'assignació d'un identificador a una sol·licitud per part del Sistema d'Informació de Laboratori (SIL) permet seguir el progrés de la sol·licitud i relacionar els resultats amb les sol·licituds. També proporciona una referència per ajudar amb les consultes i sol ser equivalent a l'identificador HL7 Filler Order Identifier.</items>
      </items>
      <items code="at0065">
        <items id="text">Detalls de la mostra</items>
        <items id="description">Detalls sobre la substància física analitzada.</items>
        <items id="comment">Si el tipus de mostra està suficientment especificat amb un codi al nom de la prova, aquestes dades addicionals no són necessàries. La vinculació dels resultats a mostres específiques es pot registrar utilitzant elements de "Identificador de mostra" tant a CLUSTER.specimen com als diferents arquetips CLUSTER de resultats.</items>
      </items>
      <items code="at0068">
        <items id="text">Identificador intern del laboratori</items>
        <items id="description">Identificador local assignat pel sistema d'informació del laboratori receptor (SIL) per seguir el procés de la prova.</items>
        <items id="comment">Aquest identificador és un número de seguiment intern assignat pel SIL, i no vol ser el nom de la prova.</items>
      </items>
      <items code="at0073">
        <items id="text">Estat general de les proves</items>
        <items id="description">L'estat del resultat de la prova de laboratori en conjunt.</items>
        <items id="comment">Els valors han estat escollits específicament perquè coincideixin amb els de l'informe HL7 FHIR Diagnostic, derivats històricament de la pràctica HL7v2. Poden utilitzar altres codis/termes locals mitjançant el text "choice".&#xD;
&#xD;
Aquest element és de ocurrència múltiple per atendre els casos d'ús en què els estats per a diferents aspectes del resultat s'han dividit en diversos elements.</items>
      </items>
      <items code="at0074">
        <items id="text">Cancel·lat</items>
        <items id="description">El resultat no està disponible perquè la prova no s'ha iniciat o no s'ha completat (de vegades també s'anomena “avortada”).</items>
      </items>
      <items code="at0075">
        <items id="text">Registre de temps de l'estat general de la prova</items>
        <items id="description">La data i/o hora en què es va emetre l'estat general de les proves.</items>
      </items>
      <items code="at0077">
        <items id="text">Especialitat mèdica/clínica</items>
        <items id="description">El servei o la disciplina de diagnòstic responsable del resultat de la prova de laboratori.</items>
        <items id="comment">És una categorització general i no del nom organitzatiu del laboratori. Per exemple: anatomia patològica, immunologia i medicina transfusional, microbiologia mèdica, farmacologia clínica, genètica mèdica, bioquímica mèdica. També es poden utilitzar subcategories o subdisciplines més granulars, com ara endocrinologia, hematologia i serveis d'al·lergologia. Això pot ajudar els clínics a filtrar entre categories de resultats. Sempre que sigui possible, és desitjable codificar amb una terminologia.</items>
      </items>
      <items code="at0090">
        <items id="text">Sol·licitant</items>
        <items id="description">Detalls del metge o organització que sol·licita el resultat de la prova de laboratori.</items>
      </items>
      <items code="at0094">
        <items id="text">Detalls de la sol·licitud de la prova</items>
        <items id="description">Detalls sobre la sol·licitud de la prova.</items>
        <items id="comment">En la majoria de situacions hi ha una sol·licitud de prova i un únic resultat de prova corresponent, però, aquest grup de repetició permet la situació en què hi pot haver diverses sol·licituds de prova notificades utilitzant un únic resultat de prova.&#xD;
&#xD;
Per exemple: "un clínic sol·licita glucosa en sang en una petició i urea/electròlits en una segona petició, però el tècnic del laboratori realitza totes dues i el laboratori vol notificar-les juntes".</items>
      </items>
      <items code="at0097">
        <items id="text">Resultat de la prova</items>
        <items id="description">Resultats de la prova realitzada a la(es) mostra(s).</items>
        <items id="comment">Aquest SLOT pot transportar un analit individual, un grup, panell o bateria de múltiples analits, o una estructura més complexa i específica.</items>
      </items>
      <items code="at0098">
        <items id="text">Dignòstic de la prova</items>
        <items id="description">Paraula única, frase o breu descripció que representa el significat clínic i la importància del resultat de la prova de laboratori.</items>
        <items id="comment">Per exemple: 'Insuficiència hepàtica greu', 'Contaminació per Salmonella'. Es recomana encaridament codificar el diagnòstic amb una terminologia, sempre que sigui possible. Aquest diagnòstic ha d'estar alineat amb la informació registrada a la 'Conclusió'.</items>
      </items>
      <items code="at0100">
        <items id="text">Informació clínica facilitada</items>
        <items id="description">Descripció de la informació clínica disponible al moment de la interpretació dels resultats.</items>
        <items id="comment">Aquest element de dades pot incloure un enllaç a la informació clínica original facilitada a la sol·licitud de prova.</items>
      </items>
      <items code="at0101">
        <items id="text">Comentaris</items>
        <items id="description">Informació addicional sobre el resultat de la prova no recollida a altres camps.</items>
      </items>
      <items code="at0106">
        <items id="text">Nom de la prova original sol·licitada</items>
        <items id="description">Nom de la prova de laboratori original sol·licitada.</items>
        <items id="comment">Aquesta dada s'utilitza quan la prova sol·licitada difereixi de la prova realment realitzada pel laboratori.</items>
      </items>
      <items code="at0107">
        <items id="text">Registrat</items>
        <items id="description">L'existència de la prova està registrada al Sistema d'Informació del Laboratori, però encara no hi ha res disponible.</items>
      </items>
      <items code="at0110">
        <items id="text">Detalls de la prova</items>
        <items id="description">Detalls estructurats sobre el mètode danàlisi, dispositiu o interpretació utilitzat.</items>
        <items id="comment">Per exemple: 'detalls d'ELISA/nefelometria'.</items>
      </items>
      <items code="at0111">
        <items id="text">Prova al punt d'atenció sanitària</items>
        <items id="description">Indica si la prova es va fer directament al punt d'atenció (POCT), en contraposició a un resultat formal d'un laboratori o una altra organització de prestació de serveis.</items>
        <items id="comment">'Verdadero' si la prova es va realitzar directament al punt d'atenció.</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Factors de confusió</items>
        <items id="description">Qüestions o circumstàncies que influeixen en la interpretació exacta del mesurament o del resultat de la prova.</items>
        <items id="comment">Els "factors de confusió" s'han de reservar per a qüestions no controlades/no planificades de l'estat/fisiologia del pacient que puguin afectar la interpretació, per exemple "exercici recent" o "tabaquisme recent".&#xD;
&#xD;
Les condicions prèvies conegudes o requerides, com "dejuni", s'han d'incloure a l'element "Condicions de mostreig" de l'arquetip CLUSTER.specimen. En alguns casos, les condicions prèvies formen part del nom de la prova, per exemple "Glucosa en sang en dejú".&#xD;
&#xD;
Els problemes coneguts de recollida o manipulació de mostres, com "ús prolongat de torniquet" o "mostra hemolitzada", s'han d'incloure als elements "Qualitat de la mostra" de l'arquetip CLUSTER.specimen.&#xD;
&#xD;
Sempre que sigui possible, és desitjable codificar amb una terminologia.</items>
      </items>
      <items code="at0114">
        <items id="text">Factors de confusió estructurats</items>
        <items id="description">Detalls dels problemes o circumstàncies que influeixen en la interpretació exacta de la mesura o del resultat de l'assaig.</items>
        <items id="comment">Per exemple: Última menstruació normal (LNMP).</items>
      </items>
      <items code="at0115">
        <items id="text">Corregit</items>
        <items id="description">El resultat ha estat modificat amb posterioritat a ser definitiu, i està complet i verificat pel patòleg responsable. Es tracta d'una subcategoria de "modificat".</items>
      </items>
      <items code="at0116">
        <items id="text">Afegit per error</items>
        <items id="description">El resultat de la prova ha estat retirat després de la publicació final anterior.</items>
      </items>
      <items code="at0117">
        <items id="text">Ampliació</items>
        <items id="description">Informació addicional necessària per captar el contingut local o per alinear-se amb altres models/formalismes de referència.</items>
        <items id="comment">Per exemple: requisits locals d'informació o metadades addicionals per alinear-se amb els equivalents de FHIR o CIMI.</items>
      </items>
      <items code="at0118">
        <items id="text">Representació multimèdia</items>
        <items id="description">Imatge digital, vídeo o diagrama que representa el resultat de la prova.</items>
        <items id="comment">Es permeten múltiples formats, però han de representar continguts clínics equivalents.</items>
      </items>
      <items code="at0119">
        <items id="text">Annex</items>
        <items id="description">Després de ser definitiu, l'informe s'ha modificat afegint-hi continguts nous. No s'ha modificat el contingut existent. Es tracta d'una subcategoria de "modificat".</items>
      </items>
      <items code="at0120">
        <items id="text">Preliminar</items>
        <items id="description">Es disposen de resultats preliminars verificats, però no tots els resultats són definitius. Es tracta d'una subcategoria de “Parcial”.</items>
      </items>
      <items code="at0121">
        <items id="text">Mètode de prova</items>
        <items id="description">Descripció sobre el mètode utilitzat per fer la prova.</items>
        <items id="comment">Sempre que sigui possible, és desitjable codificar amb una terminologia.</items>
      </items>
      <items code="at0122">
        <items id="text">Diagnòstic de prova estructurat</items>
        <items id="description">Un diagnòstic estructurat o complex per a la prova de laboratori.</items>
        <items id="comment">Per exemple: Diagnòstics anatomopatològics que consten de diversos eixos diferents, com ara la morfologia, l'etiologia i la funció.</items>
      </items>
    </term_definitions>
    <term_definitions language="fi">
      <items code="at0000">
        <items id="text">Laboratoriokokeen tulos</items>
        <items id="description">*The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual.(en)</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Mikä tahansa tapahtuma</items>
        <items id="description">*Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.(en)</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Tutkimusnimi</items>
        <items id="description">*Name of the laboratory investigation performed on the specimen(s).(en)</items>
        <items id="comment">*A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'.(en)</items>
      </items>
      <items code="at0017">
        <items id="text">*Receiving laboratory(en)</items>
        <items id="description">*Details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.(en)</items>
        <items id="comment">*This slot is intended to carry details of the laboratory which received the request and has overall responsibility to manage reporting of the test, even if other labs perform specific aspects.&#xD;
&#xD;
The receiving laboratory may either perform the test or refer it to another laboratory. Where a different laboratory is responsible for performing the testing on specific analytes, it would be expected that these details would be carried in the 'Analyte result detail' SLOT within the CLUSTER.laboratory_test_analyte archetype.&#xD;
&#xD;
(en)</items>
      </items>
      <items code="at0035">
        <items id="text">*Distribution list(en)</items>
        <items id="description">*Details of additional clinicians or organisations who require a copy of the test result.(en)</items>
        <items id="comment">*The 'Distribution list' is for information-only, and that the primary recipient of the report is the person intended to act on the information.(en)</items>
      </items>
      <items code="at0037">
        <items id="text">*Partial(en)</items>
        <items id="description">*This is a partial (e.g. initial, interim or preliminary) Test Result: data in the Test Result may be incomplete or unverified.(en)</items>
      </items>
      <items code="at0038">
        <items id="text">*Final(en)</items>
        <items id="description">*The Test result is complete and verified by an authorised person.(en)</items>
      </items>
      <items code="at0040">
        <items id="text">*Amended(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist, and result data has been changed.(en)</items>
      </items>
      <items code="at0057">
        <items id="text">*Conclusion(en)</items>
        <items id="description">*Narrative description of the key findings.(en)</items>
        <items id="comment">*For example: 'Pattern suggests significant renal impairment'. The content of the conclusion will vary, depending on the investigation performed. This conclusion should be aligned with the coded 'Test diagnosis'.(en)</items>
      </items>
      <items code="at0062">
        <items id="text">*Requester order identifier(en)</items>
        <items id="description">*The local identifier assigned by the requesting clinical system.(en)</items>
        <items id="comment">*Equivalent to the HL7 Placer Order Identifier.(en)</items>
      </items>
      <items code="at0063">
        <items id="text">*Receiver order identifier(en)</items>
        <items id="description">*The local identifier assigned to the test order by the order filler, usually by the Laboratory Information System (LIS).(en)</items>
        <items id="comment">*Assigning an identifier to a request by the Laboratory lnformation System (LIS) enables tracking progress of the request and enables linking results to requests. It also provides a reference to assist with enquiries and it is usually equivalent to the HL7 Filler Order Identifier.(en)</items>
      </items>
      <items code="at0065">
        <items id="text">*Specimen detail(en)</items>
        <items id="description">*Details about the physical substance that has been analysed.(en)</items>
        <items id="comment">*If the specimen type is sufficiently specified with a code in the Test name, then this additional data is not required. Linking results to specific specimens may be recorded using 'Specimen identifier' elements in both the CLUSTER.specimen and the various results CLUSTER archetypes.(en)</items>
      </items>
      <items code="at0068">
        <items id="text">*Laboratory internal identifier(en)</items>
        <items id="description">*A local identifier assigned by the receiving Laboratory Information System (LIS) to track the test process.(en)</items>
        <items id="comment">*This identifier is an internal tracking number assigned by the LIS, and it not intended to be the name of the test.(en)</items>
      </items>
      <items code="at0073">
        <items id="text">*Overall test status(en)</items>
        <items id="description">*The status of the laboratory test result as a whole.(en)</items>
        <items id="comment">*The values have been specifically chosen to match those in the HL7 FHIR Diagnostic report, historically derived from HL7v2 practice. Other local codes/terms can be used via the Text 'choice'.&#xD;
&#xD;
This element is multiple occurrence to cater for the use cases where statuses for different aspects of the result have been split into several elements.(en)</items>
      </items>
      <items code="at0074">
        <items id="text">*Cancelled(en)</items>
        <items id="description">*The result is unavailable because the test was not started or not completed (also sometimes called 'aborted').(en)</items>
      </items>
      <items code="at0075">
        <items id="text">*Overall test status timestamp(en)</items>
        <items id="description">*The date and/or time that ‘Overall test status’ was issued.(en)</items>
      </items>
      <items code="at0077">
        <items id="text">*Diagnostic service category(en)</items>
        <items id="description">*The diagnostic service or discipline that is responsible for the laboratory test result.(en)</items>
        <items id="comment">*This is intended to be a general categorisation and not to capture the organisational name of the laboratory. For example: anatomical pathology, immunology and transfusion medicine, medical microbiology, clinical pharmacology, medical genetics, medical biochemistry. Alternatively more granular sub categories or sub disciplines, such as endocrinology, haematology, and allergology services, may be used. This may assist clinicians in filtering between categories of results. Coding with a terminology is desirable, where possible.(en)</items>
      </items>
      <items code="at0090">
        <items id="text">*Requester(en)</items>
        <items id="description">*Details of the clinician or organisation requesting the laboratory test result.(en)</items>
      </items>
      <items code="at0094">
        <items id="text">*Test request details(en)</items>
        <items id="description">*Details about the test request.(en)</items>
        <items id="comment">*In most situations there is one test request and a single corresponding test result, however this repeating cluster allows for the situation where there may be multiple test requests reported using a single test result.&#xD;
&#xD;
As an example: 'a clinician asks for blood glucose in one request and Urea/electrolytes in a second request, but the lab analyser does both and the lab wishes to report these together'.(en)</items>
      </items>
      <items code="at0097">
        <items id="text">Tutkimustulos</items>
        <items id="description">*Results of the test performed on the specimen(s).(en)</items>
        <items id="comment">*This SLOT may carry an individual analyte, a group, panel or battery of multiple analytes, or a more complex and specific structure.(en)</items>
      </items>
      <items code="at0098">
        <items id="text">*Test diagnosis(en)</items>
        <items id="description">*Single word, phrase or brief description that represents the clinical meaning and significance of the laboratory test result.(en)</items>
        <items id="comment">*For example: 'Severe hepatic impairment', 'Salmonella contamination'. Coding of the diagnosis with a terminology is strongly recommended, where possible. This diagnosis should be aligned with the narrative in the 'Conclusion'.(en)</items>
      </items>
      <items code="at0100">
        <items id="text">*Clinical information provided(en)</items>
        <items id="description">*Description of clinical information available at the time of interpretation of results.(en)</items>
        <items id="comment">*This data element may include a link to the original clinical information provided in the test request.(en)</items>
      </items>
      <items code="at0101">
        <items id="text">Kommentti</items>
        <items id="description">*Additional narrative about the test result not captured in other fields.(en)</items>
      </items>
      <items code="at0106">
        <items id="text">*Original test requested name(en)</items>
        <items id="description">*Name of the original laboratory test requested.(en)</items>
        <items id="comment">*This data element is to be used when the test requested differs from the test actually performed by the laboratory.(en)</items>
      </items>
      <items code="at0107">
        <items id="text">*Registered(en)</items>
        <items id="description">*The existence of the test is registered in the Laboratory Information System, but there is nothing yet available.(en)</items>
      </items>
      <items code="at0110">
        <items id="text">*Testing details(en)</items>
        <items id="description">*Structured details about the method of analysis, device or interpretation used.(en)</items>
        <items id="comment">*For example: 'details of ELISA/nephelometry'.(en)</items>
      </items>
      <items code="at0111">
        <items id="text">*Point-of-care test(en)</items>
        <items id="description">*This indicates whether the test was performed directly at Point-of-Care (POCT) as opposed to a formal result from a laboratory or other service delivery organisation.(en)</items>
        <items id="comment">*True if the test was performed directly at Point-of-Care (POCT).(en)</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Haittaavat tekijät</items>
        <items id="description">*Issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
        <items id="comment">*'Confounding factors' should be reserved for uncontrolled/unplanned issues of patient state/physiology that might affect interpretation, for example 'recent exercise' or 'recent tobacco smoking'.&#xD;
&#xD;
Known or required preconditions, such as 'fasting' should be carried in the 'Sampling conditions' element within the CLUSTER.specimen archetype . In some cases preconditions are captured as part of the test name, for example 'Fasting blood glucose'.&#xD;
&#xD;
Known issues with specimen collection or handling, such as 'prolonged use of tourniquet' or 'sample haemolysed', should be carried in the 'Specimen quality' elements within CLUSTER.specimen archetype.&#xD;
&#xD;
Coding with a terminology is desirable, where possible.(en)</items>
      </items>
      <items code="at0114">
        <items id="text">*Structured confounding factors(en)</items>
        <items id="description">*Details of issues or circumstances that impact on the accurate interpretation of the measurement or test result.(en)</items>
        <items id="comment">*For example: Last Normal Menstrual Period (LNMP).(en)</items>
      </items>
      <items code="at0115">
        <items id="text">*Corrected(en)</items>
        <items id="description">*The result has been modified subsequent to being Final, and is complete and verified by the responsible pathologist. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0116">
        <items id="text">*Entered in error(en)</items>
        <items id="description">*The Test Result has been withdrawn following previous Final release.(en)</items>
      </items>
      <items code="at0117">
        <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 or CIMI equivalents.(en)</items>
      </items>
      <items code="at0118">
        <items id="text">*Multimedia representation(en)</items>
        <items id="description">*Digital image, video or diagram representing the test result.(en)</items>
        <items id="comment">*Multiple formats are allowed but they should represent equivalent clinical content.(en)</items>
      </items>
      <items code="at0119">
        <items id="text">*Appended(en)</items>
        <items id="description">*Subsequent to being final, the report has been modified by adding new content. The existing content is unchanged. This is a sub-category of 'Amended'.(en)</items>
      </items>
      <items code="at0120">
        <items id="text">*Preliminary(en)</items>
        <items id="description">*Verified early results are available, but not all results are final. This is a sub-category of 'Partial'.(en)</items>
      </items>
      <items code="at0121">
        <items id="text">*Test method(en)</items>
        <items id="description">*Description about the method used to perform the test.(en)</items>
        <items id="comment">*Coding with a terminology is desirable, where possible.(en)</items>
      </items>
      <items code="at0122">
        <items id="text">*Structured test diagnosis(en)</items>
        <items id="description">*A structured or complex diagnosis for the laboratory test.(en)</items>
        <items id="comment">*For example: Anatomical pathology diagnoses consisting of several different axes such as morphology, etiology and function.(en)</items>
      </items>
    </term_definitions>
    <term_definitions language="fr">
      <items code="at0000">
        <items id="text">Résultat d'un examen de laboratoire</items>
        <items id="description">Le résultat, y compris les conclusions et l'interprétation du laboratoire, d'un examen réalisé sur des échantillons prélevés sur une personne ou liés à celle-ci.</items>
      </items>
      <items code="at0001">
        <items id="text">Event Series</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0002">
        <items id="text">Tout événement</items>
        <items id="description">Par défaut, événement ponctuel ou d’intervalle non spécifié, pouvant être défini explicitement dans un template ou au moment de l’exécution.</items>
      </items>
      <items code="at0003">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0004">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0005">
        <items id="text">Nom de l'analyse</items>
        <items id="description">Nom de l'examen de laboratoire effectué sur le ou les échantillons.</items>
        <items id="comment">Un résultat d’analyse peut concerner un seul analyte ou un ensemble d’éléments, y compris des panels d’analyses. Il est fortement recommandé de coder le « nom de l’analyse » à l’aide d’une terminologie, par exemple LOINC ou SNOMED CT. Par exemple : « Glucose », « Urée et électrolytes », « Prélèvement par écouvillon », « Cortisol (matin) », « Potassium dans la transpiration » ou « Histopathologie du mélanome ». Le nom peut parfois inclure le type d’échantillon et l’état du patient, par exemple « Glycémie à jeun », ou comporter d’autres informations, comme « Potassium (gaz sanguin PNA) ».</items>
      </items>
      <items code="at0017">
        <items id="text">Laboratoire destinataire</items>
        <items id="description">Coordonnées du laboratoire qui a reçu la demande et qui assume la responsabilité globale de la gestion de la communication des résultats de l'examen, même si d'autres laboratoires se chargent de certains aspects spécifiques.</items>
        <items id="comment">Ce slot est destiné à contenir les coordonnées du laboratoire qui a reçu la demande et qui assume la responsabilité globale de la gestion de la communication des résultats de l'analyse, même si d'autres laboratoires se chargent de certains aspects spécifiques.&#xD;
&#xD;
Le laboratoire destinataire peut soit réaliser l’examen lui-même, soit le transmettre à un autre laboratoire. Lorsqu’un autre laboratoire est chargé de réaliser les analyses portant sur des analytes spécifiques, ces informations devraient figurer dans le slot « Détails du résultat de l’analyte » de l’archétype CLUSTER.laboratory_test_analyte.</items>
      </items>
      <items code="at0035">
        <items id="text">Liste de diffusion</items>
        <items id="description">Coordonnées des autres professionnels de santé ou organismes devant recevoir une copie du résultat de l'examen.</items>
        <items id="comment">La « liste de diffusion » est fournie à titre indicatif uniquement, et le destinataire principal du rapport est la personne censée donner suite à ces informations.</items>
      </items>
      <items code="at0037">
        <items id="text">Partiel</items>
        <items id="description">Il s'agit d'un résultat d'analyse partiel (par exemple, initial, intermédiaire ou préliminaire) : les données figurant dans ce résultat d'analyse peuvent être incomplètes ou non vérifiées.</items>
      </items>
      <items code="at0038">
        <items id="text">Final</items>
        <items id="description">Le résultat de l'examen est complet et a été vérifié par une personne autorisée.</items>
      </items>
      <items code="at0040">
        <items id="text">Modifié</items>
        <items id="description">Le résultat a été modifié après avoir été déclaré « définitif » ; il est complet et a été vérifié par le pathologue responsable, et les données du résultat ont été modifiées.</items>
      </items>
      <items code="at0057">
        <items id="text">Conclusion</items>
        <items id="description">Description narrative des principaux résultats.</items>
        <items id="comment">Par exemple : « Les résultats suggèrent une insuffisance rénale significative ». Le contenu de la conclusion variera en fonction de l'examen réalisé. Cette conclusion doit correspondre au « diagnostic d'examen » codé.</items>
      </items>
      <items code="at0062">
        <items id="text">Identifiant de la demande</items>
        <items id="description">L'identifiant local attribué par le système clinique demandeur.</items>
        <items id="comment">Équivalent à l'identifiant de demande « Placer » de la norme HL7.</items>
      </items>
      <items code="at0063">
        <items id="text">Identifiant de la demande du destinataire</items>
        <items id="description">Identifiant local attribué à la demande d'analyse par le responsable du traitement des demandes, généralement par le système d'information de laboratoire (LIS).</items>
        <items id="comment">L'attribution d'un identifiant à une demande par le système d'information de laboratoire (LIS) permet de suivre l'avancement de la demande et d'associer les résultats aux demandes. Il sert également de référence pour faciliter les demandes de renseignements et correspond généralement à l'identifiant de demande HL7 (Filler Order Identifier).</items>
      </items>
      <items code="at0065">
        <items id="text">Détails de l'échantillon</items>
        <items id="description">Informations détaillées sur la substance physique qui a été analysée.</items>
        <items id="comment">Si le type d’échantillon est suffisamment précisé par un code dans le nom de l'analyse, ces données supplémentaires ne sont pas requises. L’association des résultats à des échantillons spécifiques peut être enregistrée à l’aide des éléments « Identifiant de l’échantillon » tant dans l’archétype CLUSTER.specimen que dans les différents archétypes CLUSTER relatifs aux résultats.</items>
      </items>
      <items code="at0068">
        <items id="text">Identifiant interne du laboratoire</items>
        <items id="description">Identifiant local attribué par le système d'information de laboratoire (LIS) destinataire afin d'assurer le suivi du processus d'analyse.</items>
        <items id="comment">Cet identifiant est un numéro de suivi interne attribué par le LIS ; il ne s'agit pas du nom de l'analyse.</items>
      </items>
      <items code="at0073">
        <items id="text">Statut global de l'analyse</items>
        <items id="description">Statut global du résultat de l'analyse de laboratoire.</items>
        <items id="comment">Les valeurs ont été spécifiquement choisies pour correspondre à celles du rapport diagnostique HL7 FHIR, issues historiquement de la norme HL7v2. D’autres codes ou termes locaux peuvent être utilisés via l’option « Texte ».&#xD;
&#xD;
Cet élément peut apparaître plusieurs fois afin de répondre aux cas d’utilisation où les statuts relatifs à différents aspects du résultat ont été répartis en plusieurs éléments.</items>
      </items>
      <items code="at0074">
        <items id="text">Annulé</items>
        <items id="description">Le résultat n'est pas disponible car le test n'a pas été lancé ou n'a pas été mené à terme (ce que l'on appelle parfois « test interrompu »).</items>
      </items>
      <items code="at0075">
        <items id="text">Horodatage du statut global de l'analyse</items>
        <items id="description">Date et/ou heure à laquelle le « Statut global de l'analyse » a été établi.</items>
      </items>
      <items code="at0077">
        <items id="text">Catégorie du service de diagnostic</items>
        <items id="description">Le service ou la discipline de diagnostic responsable du résultat de l'examen de laboratoire.</items>
        <items id="comment">Il s’agit d’une classification générale qui ne vise pas à mentionner le nom de l’organisation gestionnaire du laboratoire. Par exemple : anatomopathologie, immunologie et médecine transfusionnelle, microbiologie médicale, pharmacologie clinique, génétique médicale, biochimie médicale. Il est également possible d’utiliser des sous-catégories ou des sous-disciplines plus précises, telles que les services d’endocrinologie, d’hématologie et d’allergologie. Cela peut aider les cliniciens à filtrer les résultats par catégorie. Dans la mesure du possible, il est souhaitable d’utiliser une terminologie spécifique pour le codage.</items>
      </items>
      <items code="at0090">
        <items id="text">Demandeur</items>
        <items id="description">Coordonnées du clinicien ou de l'organisation ayant demandé le résultat de l'analyse de laboratoire.</items>
      </items>
      <items code="at0094">
        <items id="text">Détails de la demande d'analyse</items>
        <items id="description">Détails concernant la demande d'examen.</items>
        <items id="comment">Dans la plupart des cas, il y a une seule demande d’analyse et un seul résultat correspondant ; toutefois, ce groupe répétitif permet de prendre en compte les situations où plusieurs demandes d’analyse peuvent être rapportées à l’aide d’un seul résultat d’analyse.&#xD;
&#xD;
Par exemple : « un clinicien demande une glycémie dans une première demande et un dosage de l’urée et des électrolytes dans une deuxième demande, mais l’analyseur du laboratoire effectue les deux analyses et le laboratoire souhaite les rapporter ensemble ».</items>
      </items>
      <items code="at0097">
        <items id="text">Résultat de l'analyse</items>
        <items id="description">Résultats de l'examen réalisé sur le ou les échantillons.</items>
        <items id="comment">Ce slot peut porter sur un analyte individuel, un groupe, un panel ou une batterie de plusieurs analytes, ou encore une structure plus complexe et spécifique.</items>
      </items>
      <items code="at0098">
        <items id="text">Diagnostic de l'analyse</items>
        <items id="description">Mot, expression ou brève description représentant la signification et l'importance cliniques du résultat d'un examen de laboratoire.</items>
        <items id="comment">Par exemple : « Insuffisance hépatique sévère », « Contamination par Salmonella ». Il est fortement recommandé, dans la mesure du possible, de coder le diagnostic à l’aide d’une terminologie. Ce diagnostic doit correspondre au texte figurant dans la rubrique « Conclusion ».</items>
      </items>
      <items code="at0100">
        <items id="text">Informations cliniques fournies</items>
        <items id="description">Description des informations cliniques disponibles au moment de l'interprétation des résultats.</items>
        <items id="comment">Cet élément de données peut inclure un lien vers les informations cliniques d'origine fournies dans la demande d'analyse.</items>
      </items>
      <items code="at0101">
        <items id="text">Remarque</items>
        <items id="description">Commentaire supplémentaire concernant le résultat de l'examen qui n'est pas renseigné dans d'autres champs.</items>
      </items>
      <items code="at0106">
        <items id="text">Nom initial de l'examen demandé</items>
        <items id="description">Nom de l'examen de laboratoire initial demandé.</items>
        <items id="comment">Cet élément de données doit être utilisé lorsque l'examen demandé diffère de celui effectivement réalisé par le laboratoire.</items>
      </items>
      <items code="at0107">
        <items id="text">Enregistré</items>
        <items id="description">L'existence de l'examen est enregistrée dans le système d'information du laboratoire, mais aucun résultat n'est encore disponible.</items>
      </items>
      <items code="at0110">
        <items id="text">Détails de l'analyse</items>
        <items id="description">Informations structurées concernant la méthode d'analyse, le dispositif ou l'interprétation utilisés.</items>
        <items id="comment">Par exemple : « détails du test ELISA/néphélométrie ».</items>
      </items>
      <items code="at0111">
        <items id="text">Analyse au chevet du patient</items>
        <items id="description">Cela permet d’indiquer si l'analyse a été réalisé directement au point de soins (POCT), par opposition à un résultat officiel provenant d’un laboratoire ou d’un autre prestataire de services.</items>
        <items id="comment">Vrai si le test a été réalisé directement au point de soins (POCT).</items>
      </items>
      <items code="at0112">
        <items id="text">Tree</items>
        <items id="description">@ internal @</items>
      </items>
      <items code="at0113">
        <items id="text">Facteurs de confusion</items>
        <items id="description">Problèmes ou circonstances ayant une incidence sur l'interprétation exacte de la mesure ou du résultat de l'analyse.</items>
        <items id="comment">Le terme « facteurs de confusion » doit être réservé aux éléments non contrôlés ou imprévus liés à l’état ou à la physiologie du patient susceptibles d’influencer l’interprétation, par exemple « effort physique récent » ou « consommation récente de tabac ».&#xD;
&#xD;
Les conditions préalables connues ou requises, telles que « à jeun », doivent être indiquées dans l’élément « Conditions de prélèvement » de l’archétype CLUSTER.specimen. Dans certains cas, les conditions préalables sont intégrées au nom de  l'analyse, par exemple « glycémie à jeun ».&#xD;
&#xD;
Les problèmes connus liés au prélèvement ou à la manipulation de l’échantillon, tels que « utilisation prolongée d’un garrot » ou « échantillon hémolysé », doivent être indiqués dans les éléments « Problèmes de qualité de l'échantillon » de l’archétype CLUSTER.specimen.&#xD;
&#xD;
Dans la mesure du possible, il est souhaitable d’utiliser une terminologie standardisée pour le codage.</items>
      </items>
      <items code="at0114">
        <items id="text">Facteurs de confusion structurés</items>
        <items id="description">Détails des problèmes ou circonstances ayant une incidence sur l'interprétation précise de la mesure ou du résultat de l'analyse.</items>
        <items id="comment">Par exemple : date des dernières règles (LNMP).</items>
      </items>
      <items code="at0115">
        <items id="text">Corrigé</items>
        <items id="description">Le résultat a été modifié après avoir été déclaré « définitif » ; il est complet et a été vérifié par le pathologue responsable. Il s'agit d'une sous-catégorie de « Modifié ».</items>
      </items>
      <items code="at0116">
        <items id="text">Saisi par erreur</items>
        <items id="description">Le résultat de l'analyse a été retiré après sa publication définitive.</items>
      </items>
      <items code="at0117">
        <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 ou CIMI.</items>
      </items>
      <items code="at0118">
        <items id="text">Représentation multimédia</items>
        <items id="description">Image numérique, vidéo ou schéma représentant le résultat de l'analyse.</items>
        <items id="comment">Plusieurs formats sont autorisés, mais ils doivent présenter un contenu clinique équivalent.</items>
      </items>
      <items code="at0119">
        <items id="text">Ajouté</items>
        <items id="description">Après avoir été finalisé, le rapport a été modifié par l'ajout de nouveaux éléments. Le contenu existant reste inchangé. Il s'agit d'une sous-catégorie de « Modifié ».</items>
      </items>
      <items code="at0120">
        <items id="text">Preliminaire</items>
        <items id="description">Des résultats préliminaires vérifiés sont disponibles, mais tous les résultats ne sont pas définitifs. Il s'agit d'une sous-catégorie de « Partiel ».</items>
      </items>
      <items code="at0121">
        <items id="text">Méthode d'analyse</items>
        <items id="description">Description de la méthode utilisée pour réaliser le test.</items>
        <items id="comment">Dans la mesure du possible, il est souhaitable d'utiliser une terminologie de codage.</items>
      </items>
      <items code="at0122">
        <items id="text">Diagnostic par test structuré</items>
        <items id="description">Diagnostic structuré ou complexe issu de l'examen de laboratoire.</items>
        <items id="comment">Par exemple : les diagnostics de pathologie anatomique comprenant plusieurs aspects différents, tels que la morphologie, l’étiologie et la fonction.</items>
      </items>
    </term_definitions>
  </ontology>
</archetype>
