• Include these codes as defined in http://hl7.org/fhir/v3/ActRelationshipType version 📍2016-11-11

  Code	Display	Definition
  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.
  COMP	has component	The target act is a component of the source act, with no semantics regarding composition or aggregation implied.
  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.
  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.
  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
  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."
  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.

This value set expansion contains 7 concepts.

                       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

                       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."

                       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.