HL7 Terminology (THO)
6.1.0 - Publication International flag

This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. 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_ActRelationshipExternalReference

Official URL: http://terminology.hl7.org/ValueSet/v3-xActRelationshipExternalReference Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: XActRelationshipExternalReference
Other Identifiers: OID:2.16.840.1.113883.1.11.19000

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

Used to enumerate the relationships between a CDA entry and an externally referenced act.

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)

Generated Narrative: ValueSet v3-xActRelationshipExternalReference

Language: en

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
    CodeDisplayDefinition
    ELNKepisodeLinkExpresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter.
    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.
    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.
    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

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

This value set contains 6 concepts

CodeSystemDisplayDefinition
  ELNKhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeepisodeLink

Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter.

  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.

  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.

  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

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-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26