RequestOrchestration behavior underdefined

What happens/how to log the results of the clinician choosing from the different options provided by the resource. Will create a change request w/ pull request that CDS document on the OrchestrationRequest page that there is no expectation for systems to specifically identify their "choices" within the options presented by a RequestOrchestration, but that if workflow needs this to occur, it could be accomplished with a 'filler-order' RequestOrchestration basedOn the 'original-order' RequestOrchestration that narrows the order to reflect the filling clinician's choices. 2. How to track the resulting events back to the source RequestOrchastration. We will identify places where Request pattern resources don't support RequestOrchestration in their basedOn element and submit change requests to ask this to be addressed (possibly along with other alignment issues) 3. Indicate whether the intent of the component requests will still be 'option' after they have been chosen/accepted. Will create a change request w/ pull request that CDS make clear that 'choosing' to follow a path does not change the 'intent' of the resource chosen.  However, a new Request instance with a different intent can be 'basedOn' the original.   4. When is the resource 'completed' when the clinicians made his/hers choice or when all resulting requests are finished. Will document that a RequestOrchestration is marked as `completed` when the author or business rules deem the needed/appropriate actions described in the orchestration have been fully executed. 5. Are groupIdentifiers used to group the requests related to a RequestOrchestration? Will make explicit that groupIdentifier and RequestOrchestration are different and independent concepts and the RequestOrchestration.groupIdentifier is used when the RequestOrchestration was ordered as part of a group of other things.  It does not group anything within the orchestration. 6. When to use which compound request pattern. Will provide additional guidance on when to use groupIdentifier vs. RequestOrchestration.  Specifically, groupIdentifier is for multiple things ordered/signed at once whose status can change independently.  RequestOrchestration is for a single order with multiple interdependent parts but which has a single status and where individual parts can't be cancelled or suspended independently.