HL7 Terminology (THO)
6.0.2 - Publication International flag

This page is part of the HL7 Terminology (v6.0.2: 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: ActRelationshipHasComponent

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

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

A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.

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-ActRelationshipHasComponent

Language: en

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

This value set contains 7 concepts

LevelCodeSystemDisplayDefinition
1  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.

2    CTRLVhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas control variable

A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation.

2    MBRhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas member

The target Acts are aggregated by the source Act. Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source.

UsageNotes: This explicitly represents the conventional notion of aggregation. The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts).

It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST

3      STEPhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas step

A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.

UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode.

OpenIssue: Need Additional guidelines on when each approach should be used.

4        ARRhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypearrival

The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act.

4        DEPhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypedeparture

The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act.

2    PARThttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas part

The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act.

UsageNote: In UML 1.1, this is a "composition" defined as:
"A form of aggregation with strong ownership and coincident lifetime as part of the whole. Parts with non-fixed multiplicity may be created after the composite itself, but once created they live and die with it (i.e., they share lifetimes). Such parts can also be explicitly removed before the death of the composite. Composition may be recursive."

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