HL7 Terminology (THO)
5.5.0 - Publication International flag

This page is part of the HL7 Terminology (v5.5.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet: ActRelationshipDocumentProvenance

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipDocumentProvenance Version: 3.0.0
Active as of 2014-08-07 Responsible: Health Level Seven International Computable Name: ActRelationshipDocumentProvenance
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.1.11.20528

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

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.

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
    APNDis appendageAn 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.
    COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
    RPLCreplacesA 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.
    XCRPTExcerptsThe source is an excerpt from the target.
    XFRMtransformationUsed 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.)

 

Expansion

Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

This value set contains 5 concepts.

CodeSystemDisplayDefinition
  APNDhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeis appendage

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.

  COMPhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas component

The target act is a component of the source act, with no semantics regarding composition or aggregation implied.

  RPLChttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypereplaces

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.

  XCRPThttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeExcerpts

The source is an excerpt from the target.

  XFRMhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypetransformation

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.)

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
2023-11-14reviseMarc DuteauTSMGAdd standard copyright and contact to internal content; up-476
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
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_001301 (RIM release ID)Create v: ActRelationshipDocumentProvenance that includes five ActRelationshipType codes [APND, COMP, RPLC,,XCRPT, and XFRM].
2014-08-07reviseFHIR (Kathleen Connor) (no record of original request)2014T2_2014-08-07_001308 (RIM release ID)Fix misspellings and bad 'smartquotes' in ProvenanceEventCurrentState value set names and descriptioni text.