ActRelationshipHasMember - HL7 Terminology (THO) v6.1.0

HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: ActRelationshipHasMember

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasMember		Version: 3.0.0
Active as of 2014-03-26	Responsible: Health Level Seven International	Computable Name: ActRelationshipHasMember
Other Identifiers: OID:2.16.840.1.113883.1.11.20500
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

No description

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

Language: en

Include codes fromhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipType where concept is-a MBR

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

This value set contains 4 concepts

Level	Code	System	Display	Definition
1	MBR	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType	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.

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

Custodian

Author

Comment

2023-11-14

revise