This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
. Page versions: R5 R4B R4 R3

This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/linkage-type |
| Name: | LinkageType |
| Definition: | Used to distinguish different roles a resource can play within a set of linked resources |
| Committee: | Patient Care Work Group |
| OID: | 2.16.840.1.113883.4.642.2.525 (for OID based terminology systems) |
| Source Resource | XML / JSON |
This value set is used in the following places:

This value set includes codes from the following code systems:

This expansion generated 11 Aug 2016
This value set contains 3 concepts
All codes from system http://hl7.org/fhir/linkage-type
| Code | Display | Definition |
| source | Source of truth | The record represents the "source of truth" (from the perspective of this Linkage resource) for the underlying event/condition/etc. |
| alternate | Alternate record | The record represents the alternative view of the underlying event/condition/etc. The record may still be actively maintained, even though it is not considered to be the source of truth. |
| historical | Historical/obsolete record | The record represents an obsolete record of the underlyng event/condition/etc. It is not expected to be actively maintained. |
See the full registry of value sets defined as part of FHIR.
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 |