x_ActRelationshipDocument - HL7 Terminology (THO) v6.0.0

HL7 Terminology (THO)
6.0.0 - Publication International flag

This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: x_ActRelationshipDocument

Official URL: http://terminology.hl7.org/ValueSet/v3-xActRelationshipDocument		Version: 3.0.0
Active as of 2014-03-26	Responsible: Health Level Seven International	Computable Name: XActRelationshipDocument
Other Identifiers: OID:2.16.840.1.113883.1.11.11610
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

Used to enumerate the relationships between two clinical documents for document management.

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)

Generated Narrative: ValueSet v3-xActRelationshipDocument

Language: en

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.
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.
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

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

This value set contains 3 concepts

Code	System	Display	Definition
APND	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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.
RPLC	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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.
XFRM	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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

System

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

2023-11-14

revise