HL7 Terminology (THO)
3.1.0 - Publication
This page is part of the HL7 Terminology (v3.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Active as of 2020-11-03 |
<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>Name</td><td>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></tr><tr><td>OID</td><td>2.16.840.1.113883.6.1</td><td>true</td></tr><tr><td>URI</td><td>http://loinc.org</td><td>true</td></tr></table></div>
</text>
<extension url="http://hl7.org/fhir/tools/StructureDefinition/extension-title">
<valueString value="Logical Observation Identifier Names and Codes (LOINC)"/>
</extension>
<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://terminology.hl7.org/StructureDefinition/ext-namingsystem-version">
<valueString value="3.0.0"/>
</extension>
<name value="LOINC"/>
<status value="active"/>
<kind value="codesystem"/>
<date value="2020-11-03"/>
<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>
</NamingSystem>