HL7.TERMINOLOGY\Universal Resource Locator Scheme

HL7 Terminology (THO)
5.0.0 - Publication International flag

This page is part of the HL7 Terminology (v5.0.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

CodeSystem: Universal Resource Locator Scheme

Official URL: http://terminology.hl7.org/CodeSystem/v3-URLScheme		Version: 2.1.0
Active as of 2019-03-20	Responsible: Health Level 7	Computable Name: URLScheme
Other Identifiers: : urn:oid:2.16.840.1.113883.5.143

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.

This Code system is referenced in the content logical definition of the following value sets:

Properties

Code

URL

Type

Description

Specializes

Coding

The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.

Generalizes

Coding

Inverse of Specializes. Only included as a derived relationship.

internalId

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id

code

The internal identifier for the concept in the HL7 Access database repository.

status

http://hl7.org/fhir/concept-properties#status

code

Designation of a concept's state. Normally is not populated unless the state is retired..

This code system http://terminology.hl7.org/CodeSystem/v3-URLScheme defines the following codes:

Code	Display	Definition	internalId	status
cid	Content 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	22603	active
file	File	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.	14872	active
ftp	FTP	The File Transfer Protocol (FTP) \[RFC 1738\].	14871	active
hl7-att	HL7 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	22604	active
http	HTTP	Hypertext Transfer Protocol \[RFC 2068\]. http://www.ietf.org/rfc/rfc2068.txt	14870	active
mailto	Mailto	Electronic mail address \[RFC 2368\] http://www.ietf.org/rfc/rfc2368.txt	14869	active
mllp	MLLP	Description: Mimimal Lower Layer Protocol. See Transport Specification: MLLP, Release 2 (HL7 V3 Transport specification).	21461	active
nfs	NFS	Network File System protocol \[RFC 2224\]. Some sites use NFS servers to share data files. http://www.ietf.org/rfc/rfc2224.txt	14873	active
tel	Telephone	A voice telephone number \[http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt\].	14867	active
telnet	Telnet	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	14874	active
fax	Fax	A telephone number served by a fax device \[http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt\].	14868	retired
modem	Modem	A telephone number served by a modem device \[http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt\].	14875	retired
x-text-fax	Fax	Description: A telephone number served by a fax device \[http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt\]	22605	retired
x-text-tel	Text Telephone	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.	22606	retired