Regulated workflow
Pharmacist Verification at Scale
$1.5M+ additional revenue. $150K+ legacy API cost removed to date; $500K+ projected.
At a glance
- Problem
- Pharmacist time was spent on data entry and legacy API friction, not verification. Volume could not grow without more licensed labor or more error.
- My ownership
- I defined the problem, wrote the workflow requirements, and prioritized what should leave licensed time. I led product requirements from framing through release.
- Constraints
- Licensed verification cannot be removed. The product had to speed the path around judgment without weakening auditability or accuracy.
- Decision
- I made the product decision to remove repeatable data entry and costly legacy API processing from the verification path, and to leave the pharmacist decision in human hands.
- Collaboration
- I worked with engineering through delivery and release, and with pharmacists and operations on adoption. Without a change in daily work, the product did not count.
- Result
- $1.5M+ additional revenue. $150K+ API processing cost reduced to date, $500K+ projected. Higher throughput. Related dispensing work helped bring misfill/dispensing errors below 1%.
System
Workflow around licensed verification
Before
Rx
Manual processing
Legacy / external dependency
Verification
Pharmacist
After
Rx
Automated processing
Pass / exception path
Pharmacist review
Licensed judgment stays with the pharmacist. The product work is the path around it: less manual entry, an explicit exception path, and capacity that can grow.
$1.5M+
additional revenue
$150K+
legacy API cost reduced
$500K+
projected savings
01
Problem
Verification is a control point. Manual prescription data entry and a costly legacy API sat in front of it. Pharmacists paid in time; the business paid in unit cost and lost capacity.
02
What I owned
I specified the workflow, wrote the requirements, and ran delivery with engineering through release. I worked with pharmacists and operations on adoption: daily work had to change, or the product did not count.
03
Product decisions
Specify the work that should never require licensed time. Do not “optimize” verification by removing the pharmacist.
Write requirements against the operational path, not a screen list. Treat first release as the start of adoption.
04
Result
Manual data entry dropped. Legacy API processing costs fell more than $150K, with projected savings above $500K. Processing capacity rose and contributed to more than $1.5M in additional revenue.
The same change moved cost, capacity, and revenue together because capacity was the constraint.