HL7 Terminology (THO)
6.0.2 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipActProvenance | Version: 3.0.0 | |||
Active as of 2014-08-07 | Responsible: Health Level Seven International | Computable Name: ActRelationshipActProvenance | ||
Other Identifiers: OID:2.16.840.1.113883.1.11.20529 | ||||
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 convey the relationship between two or more Acts for purpose of tracking provenance relationships such as the following:
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.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet v3-ActRelationshipActProvenance
Language: en
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
Code | Display | Definition |
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. |
Generated Narrative: ValueSet
Language: en
Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)
This value set contains 5 concepts
Code | System | Display | Definition |
COMP | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | has component | The target act is a component of the source act, with no semantics regarding composition or aggregation implied. |
SUBJ | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | has subject | Relates an Act to its subject Act that the first Act is primarily concerned with. Examples
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 | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | 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 | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | 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 | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | Excerpts | The source is an excerpt from the target. |
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 | Marc Duteau | TSMG | Add standard copyright and contact to internal content; up-476 |
2022-10-18 | revise | Marc Duteau | TSMG | Fixing missing metadata; up-349 |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
2014-08-07 | revise | FHIR (Kathleen Connor) (no record of original request) | 2014T2_2014-08-07_001303 (RIM release ID) | Create v:ActRelationshipActProvenance by adding five ActRelationshipType codes [COMP, SUBJ, SUCC, ,UPDT and XCRPT]. |