Currently the request process waits for all organizations to answer with a result in form of a MeasureReport before it is stored and referenced in the original Task resource.
In order to support live updates perceivable by the requester, we have to store each MeasureReport immediately and update the Task resource by adding a reference as output. Both operations should be done in a transaction via a transaction bundle.
The output type will be measure-report-reference and we need an extension of the output backbone element in order to reference the organization from which the result originated.
In contrast the current approach, I would not only use one MeasureReport to store all results in groups. I would keep the original MeasureReport from each organization and reference all that reports in a separate Task output.
Currently the
requestprocess waits for all organizations to answer with a result in form of a MeasureReport before it is stored and referenced in the original Task resource.In order to support live updates perceivable by the requester, we have to store each MeasureReport immediately and update the Task resource by adding a reference as output. Both operations should be done in a transaction via a transaction bundle.
The output type will be
measure-report-referenceand we need an extension of the output backbone element in order to reference the organization from which the result originated.In contrast the current approach, I would not only use one MeasureReport to store all results in groups. I would keep the original MeasureReport from each organization and reference all that reports in a separate Task output.