This page is part of the HL7 Terminology (v1.0.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

ActRelationshipDocumentProvenance - XML Representation

(back to description)

Raw xml

Source view

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-ActRelationshipDocumentProvenance"/>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><h2>ActRelationshipDocumentProvenance</h2><div><p>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.</p>
<p>For example, a predecessor Clinical Summary Document from which a successor Clinical Summary Document is derived.</p>
</div><ul><li>Include these codes as defined in <a href="CodeSystem-v3-ActRelationshipType.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType</code></a><table class="none"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-APND">APND</a></td><td>is appendage</td><td>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.</td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-COMP">COMP</a></td><td>has component</td><td>The target act is a component of the source act, with no semantics regarding composition or aggregation implied.</td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RPLC">RPLC</a></td><td>replaces</td><td>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.</td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XCRPT">XCRPT</a></td><td>Excerpts</td><td>The source is an excerpt from the target.</td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XFRM">XFRM</a></td><td>transformation</td><td>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.)</td></tr></table></li></ul></div>
  </text>
  <url
       value="http://terminology.hl7.org/ValueSet/v3-ActRelationshipDocumentProvenance"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.1.11.20528"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="ActRelationshipDocumentProvenance"/>
  <title value="ActRelationshipDocumentProvenance"/>
  <status value="active"/>
  <date value="2014-08-07T00:00:00-04:00"/>
  <description
               value="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."/>
  <compose>
    <include>
      <system
              value="http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType"/>
      <concept>
        <code value="APND"/>
      </concept>
      <concept>
        <code value="COMP"/>
      </concept>
      <concept>
        <code value="RPLC"/>
      </concept>
      <concept>
        <code value="XCRPT"/>
      </concept>
      <concept>
        <code value="XFRM"/>
      </concept>
    </include>
  </compose>
</ValueSet>