HL7 Terminology (THO)
5.2.0 - Publication International flag

This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

: null - XML Representation

Active as of 2022-12-15

Raw xml | Download



<NamingSystem xmlns="http://hl7.org/fhir">
  <id value="v3-loinc"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><h3>Summary</h3><table class="grid"><tr><td>Defining URL</td><td>http://terminology.hl7.org/NamingSystem/v3-loinc</td></tr><tr><td>Version</td><td>3.1.0</td></tr><tr><td>Name</td><td>LOINC</td></tr><tr><td>Title</td><td>Logical Observation Identifier Names and Codes (LOINC)</td></tr><tr><td>Status</td><td>active</td></tr><tr><td>Definition</td><td><div><p>LOINC provides a set of universal names and ID codes for identifying laboratory and clinical test results.1,2 LOINC facilitates the exchange and pooling of results, such as blood hemoglobin, serum potassium, or vital signs, for clinical care, outcomes management, and research. LOINC's universal identifiers (names and codes) can be used in the context of order and observation exchanges between information systems that use syntax standards such as HL73, CEN TC251, ISO TC215, ASTM4, and DICOM. Specifically, the identifier can be used as the coded value for an observation in any other standard that uses the observation/observation value paradigm, whether messages, documents, application programming interface (API), etc. For example, LOINC codes are used widely in the OBX segment Observation Identifier field (OBX-3) of an ORU HL7 (HL7 version 2.x or ASTM 1238-9410) message that may be sent between a Clinical Laboratory Information Management Systems (LIMS) and Electronic Health Record Systems (EHR).5, 6 In this way, LOINC codes provide universal identifiers that allow the exchange of clinical data between heterogeneous computing environments.</p>
</div></td></tr><tr><td>Publisher</td><td>LOINC and Health Data Standards, Regenstrief Institute, Inc.</td></tr></table><h3>Identifiers</h3><table class="grid"><tr><td><b>Type</b></td><td><b>Value</b></td><td><b>Preferred</b></td><td><b>Comment</b></td></tr><tr><td>OID</td><td>2.16.840.1.113883.6.1</td><td>true</td><td/></tr><tr><td>URI</td><td>http://loinc.org</td><td>true</td><td/></tr><tr><td>Other</td><td>http://loinc.org/rdf/</td><td>false</td><td>This uniqueId should have a type of 'iri-stem', which we will change once https://jira.hl7.org/browse/FHIR-39604 has been merged.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.url">
    <valueUri value="http://terminology.hl7.org/NamingSystem/v3-loinc"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.version">
    <valueString value="3.1.0"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.title">
    <valueString
                 value="Logical Observation Identifier Names and Codes (LOINC)"/>
  </extension>
  <name value="LOINC"/>
  <status value="active"/>
  <kind value="codesystem"/>
  <date value="2022-12-15"/>
  <publisher
             value="LOINC and Health Data Standards, Regenstrief Institute, Inc."/>
  <contact>
    <name
          value="LOINC and Health Data Standards, Regenstrief Institute, Inc."/>
  </contact>
  <responsible
               value="LOINC and Health Data Standards, Regenstrief Institute, Inc."/>
  <description
               value="LOINC provides a set of universal names and ID codes for identifying laboratory and clinical test results.1,2 LOINC facilitates the exchange and pooling of results, such as blood hemoglobin, serum potassium, or vital signs, for clinical care, outcomes management, and research. LOINC's universal identifiers (names and codes) can be used in the context of order and observation exchanges between information systems that use syntax standards such as HL73, CEN TC251, ISO TC215, ASTM4, and DICOM. Specifically, the identifier can be used as the coded value for an observation in any other standard that uses the observation/observation value paradigm, whether messages, documents, application programming interface (API), etc. For example, LOINC codes are used widely in the OBX segment Observation Identifier field (OBX-3) of an ORU HL7 (HL7 version 2.x or ASTM 1238-9410) message that may be sent between a Clinical Laboratory Information Management Systems (LIMS) and Electronic Health Record Systems (EHR).5, 6 In this way, LOINC codes provide universal identifiers that allow the exchange of clinical data between heterogeneous computing environments."/>
  <uniqueId>
    <type value="oid"/>
    <value value="2.16.840.1.113883.6.1"/>
    <preferred value="true"/>
  </uniqueId>
  <uniqueId>
    <type value="uri"/>
    <value value="http://loinc.org"/>
    <preferred value="true"/>
  </uniqueId>
  <uniqueId>
    <type value="other"/>
    <value value="http://loinc.org/rdf/"/>
    <preferred value="false"/>
    <comment
             value="This uniqueId should have a type of 'iri-stem', which we will change once https://jira.hl7.org/browse/FHIR-39604 has been merged."/>
  </uniqueId>
</NamingSystem>