HL7.TERMINOLOGY\ActRelationshipReason

HL7 Terminology (THO)
5.2.0 - Publication International flag

This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: ActRelationshipReason

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipReason		Version: 2.0.0
Active as of 2014-03-26	Computable Name: ActRelationshipReason
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.19376

The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action.

Discussion: In prior releases, the code “SUGG” (suggests) was expressed as “an inversion of the reason link.” That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.

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 codes from http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a RSON

Expansion

This value set contains 14 concepts

Expansion based on ActRelationshipType v3.1.0 (CodeSystem)

Level	Code	System	Display	Definition
1	RSON	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	has reason	Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication. Discussion: In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.
2	BLOCK	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	blocks	Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring.
2	DIAG	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	diagnoses	Description: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
2	IMM	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	immunization against	Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease)
3	ACTIMM	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	active immunization against	Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease)
3	PASSIMM	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	passive immunization against	Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease).
2	MITGT	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	mitigates	The source act removes or lessens the occurrence or effect of the target act.
3	RCVY	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	recovers	Definition: The source act is performed to recover from the effects of the target act.
2	PRYLX	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	prophylaxis of	Description: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
2	TREAT	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	treats	Description: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
3	ADJUNCT	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	adjunctive treatment	Description: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified.
3	MTREAT	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	maintenance treatment	Description: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature.
3	PALLTREAT	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	palliates	Description: The source act is intended to provide palliation for the effects of the target act.
3	SYMP	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	symptomatic relief	Description: The source act is intented to provide symptomatic relief for the effects of the target act.

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

2022-10-18

revise