HL7 Terminology (THO)
6.1.0 - Publication International flag

This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

: Uniform Resource Identifier (URI) - TTL Representation

Active as of 2022-02-07

Raw ttl | Download


@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 -------------------------------------------------------------------

 a fhir:NamingSystem ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "uri"] ; # 
  fhir:text [
fhir:status [ fhir:v "generated" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: NamingSystem uri</b></p><a name=\"uri\"> </a><a name=\"hcuri\"> </a><a name=\"uri-en-US\"> </a><h3>Summary</h3><table class=\"grid\"><tr><td>Defining URL</td><td>http://terminology.hl7.org/NamingSystem/uri</td></tr><tr><td>Version</td><td>1.0.0</td></tr><tr><td>Name</td><td>URI</td></tr><tr><td>Title</td><td>Uniform Resource Identifier (URI)</td></tr><tr><td>Status</td><td>active</td></tr><tr><td>Definition</td><td><div><p>As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt</p>\n<p>This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:</p>\n<p>Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.</p>\n<p>This OID may also be used in CD.codeSystem.</p>\n</div></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.4.873</td><td>true</td></tr><tr><td>URI</td><td>urn:ietf:rfc:3986</td><td>true</td></tr></table></div>"
  ] ; # 
  fhir:url [ fhir:v "http://terminology.hl7.org/NamingSystem/uri"^^xsd:anyURI] ; # 
  fhir:version [ fhir:v "1.0.0"] ; # 
  fhir:name [ fhir:v "URI"] ; # 
  fhir:title [ fhir:v "Uniform Resource Identifier (URI)"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:kind [ fhir:v "identifier"] ; # 
  fhir:date [ fhir:v "2022-02-07T00:00:00-00:00"^^xsd:dateTime] ; # 
  fhir:description [ fhir:v "As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt \r\n\r\nThis oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: \r\n\r\nNote that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.\r\n\r\nThis OID may also be used in CD.codeSystem."] ; # 
  fhir:uniqueId ( [
fhir:type [ fhir:v "oid" ] ;
fhir:value [ fhir:v "2.16.840.1.113883.4.873" ] ;
fhir:preferred [ fhir:v "true"^^xsd:boolean ]
  ] [
fhir:type [ fhir:v "uri" ] ;
fhir:value [ fhir:v "urn:ietf:rfc:3986" ] ;
fhir:preferred [ fhir:v "true"^^xsd:boolean ]
  ] ) . #