HL7 Terminology (THO)
5.4.13 - UTG Pro Forma Change Request UP-487 International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 5.4.13 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: URLScheme

Official URL: http://terminology.hl7.org/ValueSet/v3-URLScheme Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: URLScheme
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.1.11.14866

Copyright/Legal: 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

A Universal Resource Locator (URL) is a type of telecommunications address specified as Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The URL specifies the protocol and the contact point defined by that protocol for the resource.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

Expansion based on codesystem Universal Resource Locator Scheme v3.0.0 (CodeSystem)

This value set contains 14 concepts.

CodeSystemDisplayInactiveDefinition
  cidhttp://terminology.hl7.org/CodeSystem/v3-URLSchemeContent ID

Description: 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

  filehttp://terminology.hl7.org/CodeSystem/v3-URLSchemeFile

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.

  ftphttp://terminology.hl7.org/CodeSystem/v3-URLSchemeFTP

The File Transfer Protocol (FTP) [RFC 1738].

  hl7-atthttp://terminology.hl7.org/CodeSystem/v3-URLSchemeHL7 Attachment

Description: 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

  httphttp://terminology.hl7.org/CodeSystem/v3-URLSchemeHTTP

Hypertext Transfer Protocol [RFC 2068].

http://www.ietf.org/rfc/rfc2068.txt

  mailtohttp://terminology.hl7.org/CodeSystem/v3-URLSchemeMailto

Electronic mail address [RFC 2368]

http://www.ietf.org/rfc/rfc2368.txt

  mllphttp://terminology.hl7.org/CodeSystem/v3-URLSchemeMLLP

Description: Mimimal Lower Layer Protocol. See Transport Specification: MLLP, Release 2 (HL7 V3 Transport specification).

  nfshttp://terminology.hl7.org/CodeSystem/v3-URLSchemeNFS

Network File System protocol [RFC 2224]. Some sites use NFS servers to share data files.

http://www.ietf.org/rfc/rfc2224.txt

  telhttp://terminology.hl7.org/CodeSystem/v3-URLSchemeTelephone

A voice telephone number [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt].

  telnethttp://terminology.hl7.org/CodeSystem/v3-URLSchemeTelnet

Reference to interactive sessions [RFC 1738]. Some sites, (e.g., laboratories) have TTY based remote query sessions that can be accessed through telnet.

http://www.ietf.org/rfc/rfc1738.txt

  faxhttp://terminology.hl7.org/CodeSystem/v3-URLSchemeFaxinactive

A telephone number served by a fax device [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt].

  modemhttp://terminology.hl7.org/CodeSystem/v3-URLSchemeModeminactive

A telephone number served by a modem device [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt].

  x-text-faxhttp://terminology.hl7.org/CodeSystem/v3-URLSchemeFaxinactive

Description: A telephone number served by a fax device [http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt]

  x-text-telhttp://terminology.hl7.org/CodeSystem/v3-URLSchemeText Telephoneinactive

Description: A text telephone - a telephone which is designed for use by the hearing-impaired

Notes:

  • x-text-fax is required to replace fax, since this has been deprecated by W3C.
  • hl7-att is associated with a series of rules that must be followed. These rules are documented in Datatypes R2
  • This domain is external and extensible, so documenting this simply clarifies consistent usage for these use cases.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26