Stream: implementers
Topic: PlanDefinition action input/output context
Rob Dingwell (Feb 03 2021 at 21:49):
PlanDefinitions have actions and possibly sub-actions. Actions may also contain input and output dataRequirements. My question is if there is a defined mechanism for context between actions?
For instance, if I have a trigger event on an action and that trigger can provide me with the Resource that it was created for is there a way to share that Resource information (context) with other actions. So if the event fired because of a new Condition and the input requirements for additional actions contained a Condition is there a means to set the Condition that triggered the event to that which is required as the input for the other actions?
Another example comes from a project that I am working on where there are actions that are defined to create different types of reports (FHIR Bundles). The output dataRequirement for that action is Bundle. Is there a way to share that with other actions such as validate-report, encrypted-report, send-report .... ?
Or is this something that is left to IG's to define how they use PlanDefintion for workflow and eca-rules?
Rob Dingwell (Feb 09 2021 at 20:33):
Bumping this back up to the top incase anyone has ideas
Lloyd McKenzie (Feb 10 2021 at 00:06):
@Bryn Rhodes
Bryn Rhodes (Feb 10 2021 at 03:37):
@Rob Dingwell , the input/output data elements were introduced to support this type of data flow between actions, but the base specification isn't prescriptive about how it works. There's an example here of a registration process that does similar things to what you are describing and uses the input/output data elements to coordinate data between the actions. A lot of the behavior is implied though, so would welcome feedback on how to make that more explicit.
Bryn Rhodes (Feb 10 2021 at 03:40):
We've also agreed to introduce the notion of a "name" to the input/output data requirements in the PlanDefinition: https://jira.hl7.org/browse/FHIR-27752
Rob Dingwell (Feb 10 2021 at 19:31):
Thanks @Bryn Rhodes . I'll take a look at the jira issue and see what is being proposed
Last updated: Apr 12 2022 at 19:14 UTC
