HL7 Terminology (THO)
3.1.0 - Publication International flag

This page is part of the HL7 Terminology (v3.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: ActRelationshipActProvenance

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipActProvenance Version: 2.0.0
Active as of 2014-08-07 Computable Name: ActRelationshipActProvenance
Other Identifiers: : urn:oid:2.16.840.1.113883.1.11.20529

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.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
    CodeDisplayDefinition
    COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
    SUBJhas subjectRelates 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.
    SUCCsucceeds**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.
    UPDTupdates (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.
    XCRPTExcerptsThe source is an excerpt from the target.

 

Expansion

This value set contains 5 concepts

Expansion based on ActRelationshipType v3.1.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType

CodeDisplayDefinition
COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
SUBJhas subjectRelates 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.
SUCCsucceeds**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.
UPDTupdates (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.
XCRPTExcerptsThe 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

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-08-07reviseFHIR (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].