FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)

Agenda

Motion to approve Mar 7 minutes: Jose/Chethan - unanymous

There are situations where there's tight coupling between the authorization and the workflow and where state changes of the authorization may be tied to workflow state. In other cases, the authorization might be changed independently of knowledge of workflow state
Challenge of having a "parent" order in that it has a state that cannot be automatically propagated down to child orders - every child order must have its state changed independently (just as a change to a child order doesn't automatically trigger a change to the parent)
- With Observation, we have a bottom-up propagation of status: changes to leaf results may result in a change to a parent result, managed by a separate update
- With DiagnosticRequest (and other requests), that can happen, but there's a top-down piece too. The parent order status can be changed with an expectation of change to the child orders. In REST, these updates will have to be done separately - which means there could be a period of time where the parent is cancelled/suspended but the child orders are not.
Cancelling an authorization is not retroactive - actions may well have taken place while the authorization was active.
Next call will look at use-cases where not having an electronic record for the "parent" order but only having an identifier is insufficient