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-ActRelationshipDocumentHQMF | Version: 3.0.0 | |||
Active as of 2014-08-07 | Responsible: Health Level Seven International | Computable Name: ActRelationshipDocumentHQMF | ||
Other Identifiers: OID:2.16.840.1.113883.1.11.20522 | ||||
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 |
The reasons that may be used when relating a Quality Measure Document to other document types.
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-ActRelationshipDocumentHQMF
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. |
DRIV | is derived from | Associates 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. |
RPLC | replaces | 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. |
USE | uses | Indicates 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. |
XCRPT | Excerpts | The source is an excerpt from the target. |
XFRM | transformation | 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.) |
Generated Narrative: ValueSet
Language: en
Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)
This value set contains 6 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. |
DRIV | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | is derived from | Associates 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. |
RPLC | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | replaces | 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. |
USE | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | uses | Indicates 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. |
XCRPT | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | Excerpts | The source is an excerpt from the target. |
XFRM | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | transformation | 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
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2022-10-18 | revise | TSMG | Marc Duteau | Fixing missing metadata; up-349 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |
2014-08-07 | revise | 2014T2_2014-08-07_001293 (RIM release ID) | CQI (Marc Hadley) (no record of original request) | 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. |