<status value="active"/> <experimental value="false"/> <date value="2026-03-17T21:02:03.8104715+00:00"/> <publisher value="FHIR Infrastructure"/> <contact> <name value="FHIR Infrastructure"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/fiwg"/> </telecom> </contact> <description value="This cross-version ValueSet represents content from `http://hl7.org/fhir/ValueSet/v3-ActRelationshipHasComponent|2014-03-26` for use in FHIR R4B."/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> <display value="World"/> </coding> </jurisdiction> <purpose value="This value set is part of the cross-version definitions generated to enable use of the value set `http://hl7.org/fhir/ValueSet/v3-ActRelationshipHasComponent|2014-03-26` as defined in FHIR STU3 in FHIR R4B. The source value set is bound to the following FHIR STU3 elements: * Across FHIR versions, the value set has been mapped as: * `http://hl7.org/fhir/ValueSet/v3-ActRelationshipHasComponent|2014-03-26` * `http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasComponent|2014-03-26` Note that all concepts are included in this cross-version definition because no concepts have compatible representations Following are the generation technical comments: All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (7). FHIR ValueSet `http://hl7.org/fhir/ValueSet/v3-ActRelationshipHasComponent|2014-03-26`, defined in FHIR STU3 does not have any mapping to FHIR R4B"/> <compose> <include> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <concept> <code value="ARR"/> <display value="arrival"/> </concept> <concept> <code value="COMP"/> <display value="has component"/> </concept> <concept> <code value="CTRLV"/> <display value="has control variable"/> </concept> <concept> <code value="DEP"/> <display value="departure"/> </concept> <concept> <code value="MBR"/> <display value="has member"/> </concept> <concept> <code value="PART"/> <display value="has part"/> </concept> <concept> <code value="STEP"/> <display value="has step"/> </concept> </include> </compose> <expansion> <timestamp value="2026-03-17T21:02:03.8104715+00:00"/> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="ARR"/> <display value="arrival"/> </contains> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="COMP"/> <display value="has component"/> </contains> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="CTRLV"/> <display value="has control variable"/> </contains> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="DEP"/> <display value="departure"/> </contains> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="MBR"/> <display value="has member"/> </contains> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="PART"/> <display value="has part"/> </contains> <contains> <system value="http://hl7.org/fhir/v3/ActRelationshipType"/> <version value="2016-11-11"/> <code value="STEP"/> <display value="has step"/> </contains> </expansion> </ValueSet>

Generated Narrative: ValueSet R3-v3-ActRelationshipHasComponent-for-R4B

This value set expansion contains 7 concepts.

System	Version	Code	Display	Definition
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	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.
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	COMP	has component	The target act is a component of the source act, with no semantics regarding composition or aggregation implied.
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	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.
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	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.
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	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`
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	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."`
`http://hl7.org/fhir/v3/ActRelationshipType`	2016-11-11	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.`