HL7.TERMINOLOGY\URLScheme

HL7 Terminology (THO)
3.0.0 - Publication

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

ValueSet: URLScheme

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-URLScheme

Version:

2.0.0

Name:

URLScheme

Status:

Active as of 3/26/14

Definition:

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.

OID:

2.16.840.1.113883.1.11.14866 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

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)

Include all codes defined in http://terminology.hl7.org/CodeSystem/v3-URLScheme

Expansion

This value set contains 14 concepts

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

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-URLScheme

Code	Display	Definition
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
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.
ftp	FTP	The File Transfer Protocol (FTP) \[RFC 1738\].
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
http	HTTP	Hypertext Transfer Protocol \[RFC 2068\]. http://www.ietf.org/rfc/rfc2068.txt
mailto	Mailto	Electronic mail address \[RFC 2368\] http://www.ietf.org/rfc/rfc2368.txt
mllp	MLLP	Description: Mimimal Lower Layer Protocol. See Transport Specification: MLLP, Release 2 (HL7 V3 Transport specification).
nfs	NFS	Network File System protocol \[RFC 2224\]. Some sites use NFS servers to share data files. http://www.ietf.org/rfc/rfc2224.txt
tel	Telephone	A voice telephone number \[http://www.ietf.org/rfc/rfc3966.txt and http://www.ietf.org/rfc/rfc2806.txt\].
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
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\].
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\].
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\]
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.

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

Source

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

Date

Action

Author

Custodian

Comment

2020-05-06

revise