Improving e-fax routing accuracy

We process about 110 e-faxes a day in our GI clinic, and I’m trying to auto-route by sender and keyword while preserving audit trails. Has anyone paired RightFax with OCR rules or Epic In Basket pools to keep misfiles under 1% without slowing indexing? If anything looks urgent or emergent, we still escalate to a licensed clinician immediately, but I’d love a repeatable setup for the rest.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍​‌‌‍⁠​‌⁠​⁠‌‍‌‌‌‍​⁠‌⁠​‍‌‍‌‌‌⁠‌​‌‍​‌‌⁠​‍‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​​‌⁠‌⁠‌​‍‍‌‌‍​​⁠‌‍‌‍‌⁠‌‌‌‍‌​‍​‌‍‍‌​⁠​‌‌⁠‍‌​⁠‌‌‌‍⁠​‌‍⁠‌​⁠​​‌​‍‌​‍​‍‌⁠⁠‌​

This drove me nuts too — at “110 e-faxes a day” scale, we hit <1% by mapping RightFax DIDs to frequent senders first, then using OCR only as a secondary check on the header (top 2") for facility name/NPI with a regex; auto-route to Epic In Basket only when both match, otherwise land in a low-confidence Review pool so indexing doesn’t stall. Small caveat: set OCR confidence around 85% and keep an exclude list for terms like “STAT” so escalations don’t get misfiled. Do you have unique DIDs per major sender, or is everything landing on one line?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍​‌‌‍⁠​‌⁠​⁠‌‍‌‌‌‍​⁠‌⁠​‍‌‍‌‌‌⁠‌​‌‍​‌‌⁠​‍‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌​​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠‍​‌⁠​‍‌‍‍‌‌​‍‍‌​⁠‌​⁠‍​‌​‌​‌​‌‌‌‌‌​‌‍⁠‍‌‍‌​‌​‍‌‌‌‌‌‌‌‍‌‌​⁠‌‌​⁠‍​‍​‍‌⁠⁠‌​

At about 110/day, what got us under 1% (, finally) was layering a denylist + confidence threshold: RightFax OCR does a quick regex pass (e.g., “STAT|positive|bleed”) to auto-escalate, then we route by sender/DID to Epic In Basket pools, and anything <0.8 confidence lands in an “Uncertain – GI” pool for a 2‑minute manual look so indexing doesn’t stall. We also asked our top 10 senders to add a simple “GI-REF” tag on the cover page, which boosted accuracy without more rules. @carmen_ross34 have you tried the RightFax XML Connector to push route codes into Epic, or are you sticking to header OCR only?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍​‌‌‍⁠​‌⁠​⁠‌‍‌‌‌‍​⁠‌⁠​‍‌‍‌‌‌⁠‌​‌‍​‌‌⁠​‍‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌​​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​‍‌‌‍‌‌​‍⁠‌​‍‍‌​⁠​‌‌‍‌​⁠‌⁠​⁠‍‌‌⁠​​‌‌‌‍‌​⁠​‌‍‍‍‌​⁠‌‌‌​​‌⁠‌‌​⁠​⁠​‍​‍‌⁠⁠‌​

RightFax QR-coded coversheets for top senders plus CSID mapping kept us under 1% at 110/day, @c_martin22.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍​‌‌‍⁠​‌⁠​⁠‌‍‌‌‌‍​⁠‌⁠​‍‌‍‌‌‌⁠‌​‌‍​‌‌⁠​‍‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌​​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​​‌​​‌‌‍‌‌‌‍‍​‌⁠​‌‌⁠‌⁠‌​‍‍​⁠‌​‌‍⁠⁠‌​​‌​⁠‌​‌‍‌‌‌​‍​‌⁠‍​​⁠‌‍‌⁠​‍​‍​‍‌⁠⁠‌​