HL7.TERMINOLOGY\ActRelationshipHasComponent

HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ActRelationshipHasComponent

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasComponent

Version:

2.0.0

Name:

ActRelationshipHasComponent

Status:

Active

Title:

ActRelationshipHasComponent

Definition:

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

OID:

2.16.840.1.113883.1.11.10318 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

Include codes from http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a COMP

Expansion

This value set contains 7 concepts

Expansion based on ActRelationshipType v2.0.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType

Lvl	Code	Display	Definition
0	COMP	has component	The target act is a component of the source act, with no semantics regarding composition or aggregation implied.
1	CTRLV	has 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.
1	MBR	has 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
2	STEP	has 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.
3	ARR	arrival	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.
3	DEP	departure	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.
1	PART	has 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

Source

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

2020-05-06

revise