HL7 Terminology
2.1.0 - Publication
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 xmlns="http://hl7.org/fhir">
<id value="v3-ActRelationshipActProvenance"/>
<language value="en"/>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><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><td><b>Definition</b></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-SUBJ">SUBJ</a></td><td>has subject</td><td>Relates an Act to its subject Act that the first Act is primarily concerned with.<br/><br/>Examples<br/><br/>1. The first Act may be a ControlAct manipulating the subject Act<br/>2. The first act is a region of interest (ROI) that defines a region within the subject Act.<br/>3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.<br/><br/>Constraints<br/><br/>An Act may have multiple subject acts.<br/><br/>Rationale<br/><br/>The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship.</td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SUCC">SUCC</a></td><td>succeeds</td><td>**Definition:** A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act.</td></tr><tr><td><a href="CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-UPDT">UPDT</a></td><td>updates (condition)</td><td>A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread.</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></table></li></ul></div>
</text>
<url
value="http://terminology.hl7.org/ValueSet/v3-ActRelationshipActProvenance"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.1.11.20529"/>
</identifier>
<version value="2.0.0"/>
<name value="ActRelationshipActProvenance"/>
<title value="ActRelationshipActProvenance"/>
<status value="active"/>
<date value="2014-08-07"/>
<description
value="Used to convey the relationship between two or more Acts for purpose of tracking provenance relationships such as the following:
* A predecessor Act and a successor Act (e.g., a predecessor Lab Result from which a successor Lab Result in derived)
* A ProvenanceEvent Act and a target Act for which it records the Provenance (e.g., a target Act is an update of a predecessor Act)
* A predecessor ProvenanceEvent Act and a successor ProvenanceEvent Act
*UsageConstraint:* The v:ActRelationshipActProvenance is intended to limit the types of relationships that could be conveyed by the ActRelationshipType codes to a subset that pertains to these provenance relations."/>
<compose>
<include>
<system
value="http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType"/>
<concept>
<code value="COMP"/>
</concept>
<concept>
<code value="SUBJ"/>
</concept>
<concept>
<code value="SUCC"/>
</concept>
<concept>
<code value="UPDT"/>
</concept>
<concept>
<code value="XCRPT"/>
</concept>
</include>
</compose>
</ValueSet>