VMR Act Relationships
This is an area where the VMR intends to compromise to only include the relevant structural relationships rather than all possible relationships.
eg The "replaces" or "Fulfills" relationship is not critical for decision support as it is a snapshot in time.
Certainly all relationships that create hierarchical data structures should be represented. Component is the simplest of these but other relationships are also compositional as well as having other meanings as well (eg causes) The simple compositional relationship can be represented as a simple Sequence(Act), but we may need to use Sequence(ActRelationShip) to represent the semantics of the non component, but structural Act Relationships.
As many people will be mapping V2 lab data, the OBR of the Lab message will become an "Observation" with the OBX Segments components of that Observation, and in some cases the hierarchy will be more complex if templates are used eg The Differential WCC could have a grouping observation.
In GELLO "Observation -> Select(predicate = true)" will select from a flattened list of all Observations, but you could eg Select on the Code for "Full Blood Count" (In OBR Universal Service ID originally) and then select its component children to get the line items of a Full Blood Count (ie the OBX segments abstracted as V3 Observation)
