HL7 Terminology
1.0.0 - Publication

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

ActRelationshipDocumentHQMF

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-ActRelationshipDocumentHQMF
Version:2.0.0
Name:ActRelationshipDocumentHQMF
Status:Active
Title:ActRelationshipDocumentHQMF
Definition:

The reasons that may be used when relating a Quality Measure Document to other document types.

OID:2.16.840.1.113883.1.11.20522 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
    CodeDisplay
    COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
    DRIVis derived fromAssociates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.
    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.
    USEusesIndicates that the source act makes use of (or will make use of) the information content of the target act.

    *UsageNotes:* A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.

    *Rationale:* There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference.
    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

This value set contains 6 concepts

Expansion based on ActRelationshipType v2.0.0 (CodeSystem)

All codes from 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.
DRIVis derived fromAssociates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.
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.
USEusesIndicates that the source act makes use of (or will make use of) the information content of the target act. *UsageNotes:* A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate. *Rationale:* There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference.
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.)

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
Source 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-07reviseCQI (Marc Hadley) (no record of original request)2014T2_2014-08-07_001293 (RIM release ID)Create a new value set which defines the reasons (type code values) that may be used when relating a Quality Measure Document to other document types.