Quick answer: Manual checklists and EHR hard-stops work for a practice with low volume and mostly structured data, but software to detect missing patient data wins once fax and outside-record intake, rising referral volume, or multiple locations make manual chasing the bottleneck. The deciding factors are how much of your incoming information is unstructured, how many items you process each day, and how many people it takes to check them. Most mid-to-large independent practices land on a hybrid: a written checklist as the standard, and software to enforce it.
What are the two options, really?
"Build" and "buy" are loose terms here, so define them before comparing.
Build means you rely on your own people and your existing systems. A written checklist for each referral and visit type. EHR required fields and hard-stops that block an order or a scheduled visit until the field is filled. A staff member assigned to review new referrals and chase what's missing. Some practices add light tooling, such as shared-inbox rules, a spreadsheet tracker, or a task queue in the EHR.
Buy means dedicated software that reads incoming documents and records, compares them to your requirements, and flags or retrieves the gaps. That software can be a focused detection product or one agent inside a broader back-office automation platform.
The two aren't opposites. Every buy decision still needs the build work of defining what "complete" means. The real question is who enforces the checklist on every item: a person, the EHR, or software.
When do manual checklists and EHR hard-stops work well?
Manual approaches are underrated, and a fair comparison starts with where they win.
They work well when volume is low enough that one or two people can review every inbound item the day it arrives. They work when most of your data is structured, entered by your own staff into fields the EHR can validate. They also work when the cost of a gap is low, meaning a missed field causes a short delay rather than a lost referral or a denied claim.
EHR hard-stops are strong for exactly the data your staff create. If a scheduler can't book a new-patient visit without an insurance ID, the system enforces it with no extra effort. That's cheap, reliable, and already paid for.
Manual checklists also cost almost nothing to start. You can write one this week. For a practice that hasn't defined what complete means for its top referral types, doing that by hand first is the right move whether or not you buy anything later.
Where do manual approaches break down?
The trouble starts with the information that doesn't come through an EHR field. Faxes, scanned PDFs, outside records, and referral letters arrive as images and unstructured text. An EHR hard-stop can't see them. A person has to read each one, find the patient, and spot what's absent.
That creates four pressure points as a practice grows.
Volume. A reviewer can check a modest number of referrals a day carefully. As volume climbs well past that, corners get cut, and the check slides from "verify every field" to "glance for obvious problems."
Consistency. Two reviewers apply the checklist differently. A third, covering for sick leave, applies it hardly at all. Manual enforcement varies with who's working.
Timing. Items that arrive after hours or on a Friday afternoon wait. The delay between arrival and review is where patients drift away. Industry research cited by MGMA puts the share of faxed referrals that never become scheduled appointments at roughly 45%, and slow handling is one likely contributor.
Locations. Once you have several sites, each tends to build its own version of the checklist. A patient referred to one location gets a different experience than one referred to another, and no one has a view across all of them.
Staff cost compounds all of this. The AMA's 2024 prior authorization survey found physicians and staff spend about 13 hours a week on prior authorization, and a share of that is rework caused by incomplete information going in.
What does detection software add?
Software changes who does the checking. It reads every document as it arrives, extracts the fields, and compares them to the requirements you've defined. Complete items pass through with no human touch. Incomplete ones go to the right person with the gap named.
What that buys you, specifically:
- Coverage of unstructured documents. It reads faxes and PDFs that EHR rules can't touch.
- Consistency. The same rules apply to every item, at 4 p.m. or 9 p.m., regardless of who's on shift.
- Speed. The check happens within minutes of arrival, so outreach starts the same day.
- Retrieval, in stronger products. Some tools go beyond flagging and fetch the missing record from your EHR or an outside source, so staff handle fewer gaps.
- Visibility. You can see gaps by source, location, and referring office, which manual processes rarely produce.
Honey Health's referral intake and data fetching agents are one example of this approach. They read inbound referrals, extract the required fields, route what's incomplete, and retrieve records instead of waiting on a request. They're one option among several ways to automate the check, and the same evaluation questions apply to any of them.
What are the honest drawbacks of buying?
Software isn't free of tradeoffs, and a practice administrator should weigh them.
Cost. Pricing is usually per document or per volume, plus implementation. For a low-volume practice, the math may not clear.
Setup effort. You still have to define your requirements, and integration with your EHR takes time. Cloud EHRs with open APIs go live faster. Epic and on-prem systems take longer because of interface work.
False positives and tuning. Early on, the system will flag items that don't need flagging. Expect a tuning period and a human review queue. A product that can't show you why it flagged something is hard to trust.
Dependence on vendor quality. A weak extraction model that misreads poor faxes can produce confident wrong answers. Test with your own messy documents before you commit.
Change management. Staff accustomed to reading every page have to trust an exception queue. That shift takes a few weeks.
How do the options compare side by side?
Here's the short version of the tradeoffs across the dimensions operators usually care about.
- Setup effort: Manual checklists take days. EHR hard-stops take a few configuration changes. Software takes weeks, including integration and tuning.
- Coverage of faxes and outside records: Manual depends on staff reading each page. EHR hard-stops don't cover it at all. Software reads it directly.
- Staff time per item: Manual is highest and grows with volume. EHR hard-stops add almost none. Software reduces review to exceptions.
- Error rate: Manual varies with fatigue and staffing. EHR rules are consistent but narrow. Software is consistent, with its own error profile you need to test.
- Cost scaling: Manual cost scales with headcount. EHR rules are close to fixed. Software scales with volume.
- Visibility across locations: Manual is patchy. EHR reporting helps for structured fields. Software typically reports gaps by source and site.
No row decides it on its own. The question is which rows matter most for your practice, and for most groups the fax and outside-record row is the one that tips it.
What should you ask a vendor before you buy?
Whatever you decide, run the same short test on any product you consider.
Show me a bad fax. Give the vendor your worst scans, with cut-off IDs and handwritten notes, and see what the system reads and what it admits it can't.
What happens on low confidence? You want a system that surfaces uncertainty to a person. A system that guesses can create duplicate charts or false completeness.
Who edits the rules? Payers change requirements often. If every change needs a vendor ticket, your rule set will lag behind.
Does it fetch or only flag? Flagging shortens discovery. Fetching and outreach shorten resolution too.
What does the exception queue look like? Ask to see it with real volume. If it's cluttered, your staff will end up reviewing everything anyway.
How should you decide? A simple framework
Use four questions. Answer them honestly, in general terms, rather than hunting for a precise breakeven number.
- What share of your inbound information is unstructured? If most arrives as faxes, PDFs, and outside records, EHR rules will leave most gaps uncovered. That points toward software.
- Can one or two people review every item on the day it arrives? If yes, manual works. If reviews routinely slip a day or more, you've outgrown it.
- How costly is a gap? If gaps lead to lost referrals, stalled authorizations, or denied claims, the cost of missing them is higher than the software.
- How many locations or intake channels do you run? More of either makes consistent manual enforcement harder.
If you answered "mostly structured, low volume, one location," build. If three or four answers point to software, buy or pilot. If it's mixed, the hybrid is usually best: keep the written checklist and EHR hard-stops, and add software for the unstructured intake where manual review is weakest.
Why does the hybrid usually win?
For a mid-to-large independent practice, the answer is rarely all one or all the other. The checklist is the standard, and it belongs to you. The EHR enforces it for data your staff enter. Software enforces it for what arrives from outside.
That split plays to each tool's strength. It also protects you from lock-in, because your requirements live in your own documented process, not in a vendor's black box. If you switch tools later, the checklist moves with you.
One practical way to start is a pilot. Take one high-volume referral type, define its checklist, and run software against a sample of real documents for a few weeks. Compare gaps caught, time to complete, and staff minutes against your manual baseline. That gives you your own numbers instead of a vendor's.
Frequently Asked Questions
Should a practice build manual checklists or buy software to detect missing patient data?
Build checklists first, since you need a definition of "complete" either way. Buy software once unstructured intake, volume, or multiple locations make manual review the bottleneck. Most mid-to-large practices end up with a hybrid of the two.
Are EHR hard-stops enough?
They work for data your staff enter into structured fields. They can't read faxes, scanned PDFs, or outside records, which is where most missing information originates. For those, you need a person or software reading the document.
How much does missing data detection software cost?
Pricing varies by vendor and is usually based on document volume plus implementation. Ask for pricing against your actual volume, and compare it to the staff time you spend on follow-up today.
How long does implementation take?
It depends on your EHR. Cloud systems with open APIs can go live in a few weeks, while Epic and on-prem deployments take longer because of interface work. Defining your requirements checklist is often the slowest step.
Can we start with software and skip the checklist?
Not effectively. Software enforces requirements, so you have to define them. Writing a short checklist for your five busiest referral types is the best first step before any vendor demo.
