Notable Health AI Agents reduce faxed referral turnaround from 48 hours to 10 minutes at Florida health system
A large Florida health system relied on manual fax processing by 12.5 full-time employees, with an average turnaround of 48 hours that could reach five business days when staff were absent. Fifteen percent of referrals were handwritten, and faxes arrived across multiple queues making volume and throughput tracking difficult.
source quote
source quote
source quote
source quote
source quote
Notable's AI Agents automated over 10,000 faxed orders to date, saving 8,000 hours annually with a 2.6x ROI, reducing average turnaround from 48 hours to 10 minutes, achieving an 85% referral completion rate, and enabling 5 FTEs to upskill for higher-value work.
Show all 11 reported metrics
Compare to your context
Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.
Frequently asked questions
What did this team achieve with this AI workflow?
Notable's AI Agents automated over 10,000 faxed orders to date, saving 8,000 hours annually with a 2.6x ROI, reducing average turnaround from 48 hours to 10 minutes, achieving an 85% referral completion rate, and enab…
What tools did this team use?
Notable's Referrals Coordinator AI Agent, Notable's AI Platform, RightFax, OnBase, Epic.
What results were reported?
Faxed orders automated to date: over 10,000; Projected total faxed orders automated in 2025: 60,000; Staff hours saved annually: 8,000 hours annually; ROI on referral transcription: 2.6x (source-reported, not independently verified).
How is this medical records processing AI workflow structured?
Faxed referral received → AI data extraction → Order validation and flagging → Complex case routing to humans → Order transcription completed.
Related medical records processing cases
Now compare it to your context
This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.