HL7.TERMINOLOGY\ActRelationshipDocumentProvenance

This page is part of the HL7 Terminology (v2.1.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: ActRelationshipDocumentProvenance

Summary

Defining URL:

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

Version:

2.0.0

Name:

ActRelationshipDocumentProvenance

Status:

Active as of 2014-08-07

Definition:

Used to convey the relationship between two or more Documents for purpose of tracking provenance relationships such as a predecessor Document and a successor Document.

For example, a predecessor Clinical Summary Document from which a successor Clinical Summary Document is derived.

OID:

2.16.840.1.113883.1.11.20528 (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 these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType

Code	Display	Definition
APND	is appendage	An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered.
COMP	has component	The target act is a component of the source act, with no semantics regarding composition or aggregation implied.
RPLC	replaces	A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.
XCRPT	Excerpts	The source is an excerpt from the target.
XFRM	transformation	Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)

Expansion

This value set contains 5 concepts

Expansion based on ActRelationshipType v3.0.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType

Code	Display	Definition
APND	is appendage	An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered.
COMP	has component	The target act is a component of the source act, with no semantics regarding composition or aggregation implied.
RPLC	replaces	A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.
XCRPT	Excerpts	The source is an excerpt from the target.
XFRM	transformation	Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)

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