Release 4 5 Preview #3
This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions Code System

Structured Documents Work Group   Maturity Level : 3 Trial Use Use Context : Any

This is a code system defined by the FHIR project.


Defining URL:
Version: 4.0.1 4.5.0
Name: DocumentRelationshipType
Title: DocumentRelationshipType

The type of relationship between documents.

Committee: Structured Documents Work Group
OID: 2.16.840.1.113883.4.642.4.245 2.16.840.1.113883.4.642.1.245 (for OID based terminology systems)
Source Resource XML / JSON

This Code system is used in the following value sets:

  • ValueSet: DocumentRelationshipType (The type of relationship between documents.)
  • ValueSet: DocumentRelationshipType (The type of relationship between documents.) DocumentRelationshipType

The type of relationship between documents. This code system defines the following codes:

Code Display Definition
replaces Replaces This document logically replaces or supersedes the target document.
transforms Transforms This document was generated by transforming the target document (e.g. format or language conversion).
signs Signs This document is a signature of the target document.
appends Appends This document adds additional information to the target document.


See the full registry of code systems 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. See Code System for further information.
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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