@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

<http://terminology.hl7.org/NamingSystem/v3-loinc> a fhir:NamingSystem ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "v3-loinc"] ; # 
  fhir:text [
     fhir:status [ fhir:v "generated" ] ;
     fhir:div "<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>\n</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>"
  ] ; # 
  fhir:extension ( [
     fhir:url [ fhir:v "http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.url"^^xsd:anyURI ] ;
     fhir:value [ fhir:v "http://terminology.hl7.org/NamingSystem/v3-loinc"^^xsd:anyURI ]
  ] [
     fhir:url [ fhir:v "http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.version"^^xsd:anyURI ] ;
     fhir:value [ fhir:v "3.1.0" ]
  ] [
     fhir:url [ fhir:v "http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.title"^^xsd:anyURI ] ;
     fhir:value [ fhir:v "Logical Observation Identifier Names and Codes (LOINC)" ]
  ] ) ; # 
  fhir:name [ fhir:v "LOINC"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:kind [ fhir:v "codesystem"] ; # 
  fhir:date [ fhir:v "2022-12-15"^^xsd:date] ; # 
  fhir:publisher [ fhir:v "LOINC and Health Data Standards, Regenstrief Institute, Inc."] ; # 
  fhir:contact ( [
     fhir:name [ fhir:v "LOINC and Health Data Standards, Regenstrief Institute, Inc." ]
  ] ) ; # 
  fhir:responsible [ fhir:v "LOINC and Health Data Standards, Regenstrief Institute, Inc."] ; # 
  fhir:description [ fhir:v "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."] ; # 
  fhir:uniqueId ( [
     fhir:type [ fhir:v "oid" ] ;
     fhir:value [ fhir:v "2.16.840.1.113883.6.1" ] ;
     fhir:preferred [ fhir:v "true"^^xsd:boolean ]
  ] [
     fhir:type [ fhir:v "uri" ] ;
     fhir:value [ fhir:v "http://loinc.org" ] ;
     fhir:preferred [ fhir:v "true"^^xsd:boolean ]
  ] [
     fhir:type [ fhir:v "other" ] ;
     fhir:value [ fhir:v "http://loinc.org/rdf/" ] ;
     fhir:preferred [ fhir:v "false"^^xsd:boolean ] ;
     fhir:comment [ fhir:v "This uniqueId should have a type of 'iri-stem', which we will change once https://jira.hl7.org/browse/FHIR-39604 has been merged." ]
  ] ) . # 

# -------------------------------------------------------------------------------------