HL7 Terminology (THO)
5.4.0 - Publication International flag

This page is part of the HL7 Terminology (v5.4.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: x_ActRelationshipEntryRelationship

Official URL: http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntryRelationship Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: XActRelationshipEntryRelationship
Other Identifiers: id: Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.1.11.19447

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 enumerate the relationships between two CDA entries.

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
    CAUSis etiology for**Description:** An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.

    **Examples:**

    * a growth of Staphylococcus aureus may be considered the cause of an abscess
    * contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced
    * lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed
    COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
    GEVLevaluates (goal)A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a "goal distance" (e.g., goal to observation) can be "calculated" and need not be sent explicitly.
    MFSTis manifestation ofAn assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation.
    REFRrefers toA relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee.
    RSONhas 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.
    SASstarts after start ofThe source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).

    *UsageNote:* Inverse code is **SBS**
    SPRThas supportUsed to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post).
    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.
    XCRPTExcerptsThe source is an excerpt from the target.

 

Expansion

This value set contains 10 concepts

Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

CodeSystemDisplayDefinition
  CAUShttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeis etiology for

Description: An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.

Examples:

  • a growth of Staphylococcus aureus may be considered the cause of an abscess
  • contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced
  • lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed
  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.

  GEVLhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeevaluates (goal)

A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a "goal distance" (e.g., goal to observation) can be "calculated" and need not be sent explicitly.

  MFSThttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeis manifestation of

An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation.

  REFRhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTyperefers to

A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee.

  RSONhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas 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.

  SAShttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypestarts after start of

The source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).

UsageNote: Inverse code is SBS

  SPRThttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas support

Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post).

  SUBJhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas subject

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

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

The 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

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26