Release 4B Snapshot #1

This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

4.3.14.129 Code System http://hl7.org/fhir/document-relationship-type

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

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/document-relationship-type
Version:4.3.0-snapshot1
Name:DocumentRelationshipType
Title:DocumentRelationshipType
Definition:

The type of relationship between documents.

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

This Code system is used in the following value sets:

The type of relationship between documents.

This code system http://hl7.org/fhir/document-relationship-type 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:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code