<status value="active"/> <experimental value="false"/> <date value="2014-03-26"/> <publisher value="Health Level Seven International"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> <telecom> <system value="email"/> <value value="hq@HL7.org"/> </telecom> </contact> <description value="Used to enumerate the relationships between two clinical documents for document management."/> <copyright value="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"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType"/> <concept> <code value="APND"/> </concept> <concept> <code value="RPLC"/> </concept> <concept> <code value="XFRM"/> </concept> </include> </compose> </ValueSet>

Generated Narrative: ValueSet v3-xActRelationshipDocument

Language: en

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