Design a Prior-Authorization Worklist and Digest
Add reliable status, pharmacist assignment, and end-of-day follow-up workflows to a prior-authorization platform.
Problem statement
A healthcare platform creates a prior authorization when an insurer indicates that a prescribed medication requires one. It retrieves the payer-specific form, pre-fills it from patient records, lets a pharmacist review and edit it, submits it, and receives payer responses asynchronously.
Design three additions: current status lookup, a pharmacist worklist with assignment semantics, and an end-of-workday digest containing meaningfully changed or stale authorizations. Users are pharmacists; authentication is provided by an existing service. A filled PDF can be as large as 50 MB.
Protect clinical data throughout the design.
What to build
- A pharmacist can retrieve the current prior-authorization status and a trustworthy transition history.
- A pharmacist can add or claim an authorization on a personal worklist without conflicting assignments.
- The platform can idempotently apply asynchronous payer responses and request additional information.
- At the pharmacist's workday end, the platform sends one digest of meaningfully changed worklist items and items with no update for one day.
At scale
- The source specifies 100 pharmacy organizations, 100 pharmacists per organization, and 10 prior authorizations worked per pharmacist per day.
- The source specifies filled prior-authorization PDFs up to 50 MB with embedded images.
- The source defines stale digest membership as no update for one day.
- For this exercise, assume payer callbacks may be duplicated, delayed, or arrive out of order, and meaningful status changes should be visible within one minute.
- For this exercise, retain an auditable transition history and keep protected health information encrypted and tenant-isolated.