On our next release, a platform version upgrade will be deployed and will require a server restart. During the release window our servers might be intermittent or offline for a few minutes.

New "Approved" Status

This release also introduces a new status/queue for encounters: "Approved". When a physician approves an encounter, it'll now go to the Approved status before going to Processing. Most encounters will be moved to Processing automatically as they won't require additional actions to be taken manually, so this change will be largely transparent to most of our partners.

This new status is part of a larger feature, coming in the weeks after, for Prior Authorization. The new ePA flow will enable support users to process prior auth requests directly from MDI. Encounters that require prior auth will be tagged in the Approved queue for Support users to process them manually (that's the reason we had to add a new status to the encounter life-cycle). Once approved by the patient's insurance company, these encounters will be moved to Processing and sent to the pharmacy automatically. Specific details on how support users will interact with the Approved queue will be shared at a later date by our operations team.

Encounter life-cycle

1. Encounter gets created;
2. A physician is assigned to it;
3. Physician approves its prescription(s);
4. Encounter goes to the new Approved queue;
5. When in approved:
6. If any prescription requires insurance approval, Support users will be able to initiate the ePA flow for them;
7. If any prescription is set to be manually released by Support (which enables ePA flows to be initiated outside of MDI), Support users will be able to move the encounter to Processing manually;
8. All other encounters will automatically go to the Processing status as it is today;
9. Once in Processing, the encounter will be completed as soon as we receive a successful response back from Surescripts.

Next steps

You are not required to update your existing integration for this new status. Most of the workflow changes will happen internally and you should receive the exact same responses from the same webhooks you have been using so far. A webhook for the Approved status will also be added for partners that want to build additional workflows.