Used to convey the relationship between two or more Acts for purpose of tracking provenance relationships such as the following:
\nUsageConstraint: 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.
\nhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
Code | Display | |
COMP | has component | The target act is a component of the source act, with no semantics regarding composition or aggregation implied. |
SUBJ | has subject | Relates an Act to its subject Act that the first Act is primarily concerned with. Examples 1. The first Act may be a ControlAct manipulating the subject Act 2. The first act is a region of interest (ROI) that defines a region within the subject Act. 3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. Constraints An Act may have multiple subject acts. Rationale 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. |
SUCC | succeeds | **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. |
UPDT | updates (condition) | 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. |
XCRPT | Excerpts | The source is an excerpt from the target. |