Follow up on prior auth data flow (focus: landing status details in the EHR) 

In our initial discussion ( • How does Prior Auth wo... ), the Cambia and Multicare teams expressed a need to “write back” data from an app into specific fields of their EHR's prior authz dashboard. In this follow-up, we talk through data requirements for the inputs and outputs of a prior authz check, including areas where a "lightweight check" (i.e., tied into the ordering workflow) might differ from a "formal check" (i.e., structured as a task item on an authorization queue).
* Call notes from live discussion: hackmd.io/ZvL7...
* Pending task to use ".systemActions" feature of CDS Hooks to automate workflow: jira.hl7.org/b...
Thanks to the teams from Argonaut, Cambia, DaVinci, Epic, and Multicare for joining in this discussion!