Universal Resource Locator Scheme

{
  "description" : "A Universal Resource Locator (URL) is a type of telecommunications address specified as Internet standard RFC 1738 \\[http://www.isi.edu/in-notes/rfc1738.txt\\]. The URL specifies the protocol and the contact point defined by that protocol for the resource.",
  "date" : "2019-03-20",
  "publisher" : "Health Level Seven International",
  "content" : "complete",
  "property" : [ {
    "description" : "A code that indicates the status of the concept",
    "type" : "code",
    "code" : "status",
    "uri" : "http://hl7.org/fhir/concept-properties#status"
  } ],
  "name" : "URLScheme",
  "copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
  "experimental" : false,
  "resourceType" : "CodeSystem",
  "title" : "Universal Resource Locator Scheme",
  "extension" : [ {
    "extension" : [ {
      "valueString" : "concept",
      "url" : "path"
    }, {
      "url" : "count",
      "valueInteger" : 14
    } ],
    "url" : "http://health-samurai.io/extensions/excised-data"
  }, {
    "url" : "http://health-samurai.io/extensions/source",
    "valueCode" : "db"
  } ],
  "status" : "active",
  "language" : "en",
  "hierarchyMeaning" : "is-a",
  "id" : "v3-URLScheme",
  "url" : "http://terminology.hl7.org/CodeSystem/v3-URLScheme",
  "identifier" : [ {
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.5.143"
  } ],
  "caseSensitive" : true,
  "version" : "4.0.0",
  "contact" : [ {
    "telecom" : [ {
      "system" : "url",
      "value" : "http://hl7.org"
    }, {
      "system" : "email",
      "value" : "hq@HL7.org"
    } ]
  } ],
  "text" : {
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem v3-URLScheme</b></p><a name=\"v3-URLScheme\"> </a><a name=\"hcv3-URLScheme\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class=\"grid\"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Status</td><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>code</td><td>Designation of a concept's state.  Normally is not populated unless the state is retired..</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v3-URLScheme</code> defines the following codes in a Is-A hierarchy:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>Status</b></td></tr><tr><td style=\"white-space:nowrap\">cid<a name=\"v3-URLScheme-cid\"> </a></td><td>Content ID</td><td><div><p><strong>Description:</strong> cid: is the most common mechanism used in webservices. A cid: reference points from the SOAP body to other content in the mime package in which the SOAP envelope is wrapped</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">file<a name=\"v3-URLScheme-file\"> </a></td><td>File</td><td><div><p>Host-specific local file names [RCF 1738]. Note that the file scheme works only for local files. There is little use for exchanging local file names between systems, since the receiving system likely will not be able to access the file.</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">ftp<a name=\"v3-URLScheme-ftp\"> </a></td><td>FTP</td><td><div><p>The File Transfer Protocol (FTP) [RFC 1738].</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">hl7-att<a name=\"v3-URLScheme-hl7-att\"> </a></td><td>HL7 Attachment</td><td><div><p><strong>Description:</strong> A reference to an HL7 attachment by it's identifier, which takes the form hl7-att:[II.literal], such as hl7-att:2.1.16.3.9.12345.2.39.3:ABC123</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">http<a name=\"v3-URLScheme-http\"> </a></td><td>HTTP</td><td><div><p>Hypertext Transfer Protocol [RFC 2068].</p>\n<p>http://www.ietf.org/rfc/rfc2068.txt</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">mailto<a name=\"v3-URLScheme-mailto\"> </a></td><td>Mailto</td><td><div><p>Electronic mail address [RFC 2368]</p>\n<p>http://www.ietf.org/rfc/rfc2368.txt</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">mllp<a name=\"v3-URLScheme-mllp\"> </a></td><td>MLLP</td><td><div><p><strong>Description:</strong> Mimimal Lower Layer Protocol. See Transport Specification: MLLP, Release 2 (HL7 V3 Transport specification).</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">nfs<a name=\"v3-URLScheme-nfs\"> </a></td><td>NFS</td><td><div><p>Network File System protocol [RFC 2224]. Some sites use NFS servers to share data files.</p>\n<p>http://www.ietf.org/rfc/rfc2224.txt</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">tel<a name=\"v3-URLScheme-tel\"> </a></td><td>Telephone</td><td><div><p>A voice telephone number [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt].</p>\n</div></td><td>active</td></tr><tr><td style=\"white-space:nowrap\">telnet<a name=\"v3-URLScheme-telnet\"> </a></td><td>Telnet</td><td><div><p>Reference to interactive sessions [RFC 1738]. Some sites, (e.g., laboratories) have TTY based remote query sessions that can be accessed through telnet.</p>\n<p>http://www.ietf.org/rfc/rfc1738.txt</p>\n</div></td><td>active</td></tr><tr style=\"background-color: #ffeeee\"><td style=\"white-space:nowrap\">fax<a name=\"v3-URLScheme-fax\"> </a></td><td>Fax</td><td><div><p>A telephone number served by a fax device [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt].</p>\n</div></td><td>retired</td></tr><tr style=\"background-color: #ffeeee\"><td style=\"white-space:nowrap\">modem<a name=\"v3-URLScheme-modem\"> </a></td><td>Modem</td><td><div><p>A telephone number served by a modem device [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt].</p>\n</div></td><td>retired</td></tr><tr style=\"background-color: #ffeeee\"><td style=\"white-space:nowrap\">x-text-fax<a name=\"v3-URLScheme-x-text-fax\"> </a></td><td>Fax</td><td><div><p><strong>Description:</strong> A telephone number served by a fax device [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt]</p>\n</div></td><td>retired</td></tr><tr style=\"background-color: #ffeeee\"><td style=\"white-space:nowrap\">x-text-tel<a name=\"v3-URLScheme-x-text-tel\"> </a></td><td>Text Telephone</td><td><div><p><strong>Description:</strong> A text telephone - a telephone which is designed for use by the hearing-impaired</p>\n<p><strong>Notes:</strong></p>\n<ul>\n<li>x-text-fax is required to replace fax, since this has been deprecated by W3C.</li>\n<li>hl7-att is associated with a series of rules that must be followed. These rules are documented in Datatypes R2</li>\n<li>This domain is external and extensible, so documenting this simply clarifies consistent usage for these use cases.</li>\n</ul>\n</div></td><td>retired</td></tr></table></div>",
    "status" : "generated"
  }
}