Six Branches, Six Fax Lines, One Lost Referral. Centralizing DME Intake Without Breaking Location Rules.
When a DME supplier grows to several locations, intake usually grows with it: one fax number per branch, one shared inbox per branch, and a different habit at every desk. Pulling all of that into one queue saves real time. It also raises billing questions that a branch-by-branch setup never had to answer.
Why this matters right now: Year-end is when a lot of suppliers close on an acquisition, open a branch or consolidate staff before January. If your intake is about to cover more locations, decide how referrals will be routed and which location bills them before the first combined fax queue goes live. Untangling it after a revalidation letter or an audit request is much harder.
How a three-branch supplier ends up with nine intake processes
Nobody designs it this way. A supplier opens a second location and gives it its own fax number so local physician offices have someone nearby to call. A third branch comes through an acquisition and keeps the fax line and billing habits it already had. A year later, a referral for a hospital bed might land in any of three fax inboxes, a shared email box that one branch still uses for discharge planners, or a phone message left at the front desk.
Each branch then builds its own way of handling what arrives. One location prints every fax and works from a paper tray. Another renames PDFs by patient last name. The acquired branch logs everything in a spreadsheet the regional manager set up in 2023. Ask the operations director how many referrals came in last Tuesday across all locations and you'll get an estimate, not a number.
That's the cost most multi-location suppliers feel first. The faxes themselves get handled. What's missing is any view across the branches: which referrals are waiting, which are stuck on a missing face-to-face note, and which ones nobody picked up because each branch assumed another one had it.
Where referrals leak between branches
The leaks follow a pattern. A referral that reaches the wrong branch sits until somebody notices it doesn't belong there. A physician's office faxes the same order to two locations "to be safe," and two coordinators open two charts. A request for additional documentation goes back to the office from one branch, and the reply comes in at another. None of this shows up as a denial right away. It shows up as a patient who waited four extra days for a delivery, or as a claim that went out with a note from the wrong date because the newer one was sitting in a different inbox.
| Where it breaks | What actually happens | Downstream cost | Risk |
|---|---|---|---|
| Wrong-branch fax | Referral lands at a location outside the patient's service area and waits for someone to forward it | Delayed delivery, lost referral if the office gives up and calls a competitor | High |
| Duplicate submissions | Same order faxed to two branches, two charts created, two coordinators chasing the same physician | Split patient history, double outreach, same-or-similar confusion later | High |
| Split documentation | Order arrives at Branch A, the updated chart notes arrive at Branch B | Claim submitted with incomplete or outdated support; exposure on post-payment review | High |
| Wrong billing location | Central team intakes the order, but the claim goes out under a PTAN that didn't dispense the item | Enrollment and supplier-standard questions, recoupment risk | Moderate |
| No shared status | Each branch tracks its own pending list in its own format | Nobody can answer "where's my order?" without calling around | Moderate |
"Most of the referrals a multi-branch supplier loses never get denied. They go stale in an inbox at a location that had no reason to look for them."
Centralized intake is allowed. The billing still has to follow the location.
The usual answer to branch sprawl is a central intake team, sometimes called hub and spoke: one team receives every referral, checks eligibility and documentation, and hands each order to the branch that will deliver it. Plenty of suppliers run it this way. The thing to get right is that Medicare doesn't enroll your intake team. It enrolls locations.
Each enrolled DMEPOS location has its own PTAN and has to meet the supplier standards on its own, including posted hours and a listed business phone that patients can actually reach. Health care attorney Jeffrey Baird of Brown & Fortunato has written in Medtrade that routing calls and faxes to a main location can be workable for locations under one Tax ID, provided some safeguards stay in place. The ones he lists include keeping each location's local phone number, letting callers reach someone at that location if they ask, assigning patients to the nearest location by zip code, having the dispensing location bill under its own PTAN, and shipping from that location's inventory. He also notes that CMS and the NSC haven't issued much formal guidance on what "intake and assessment" covers, so suppliers are working from limited direction.
Locations under separate Tax IDs are treated as separate suppliers, which adds steps. Use this as a starting point for a conversation with your own counsel and compliance lead.
"One team can receive every fax. The claim still has to come from the location that set the patient up and delivered the equipment."
What the referral path looks like before and after
The central queue is where the time comes back. Duplicate faxes get caught once instead of at two desks. A chart note that arrives three days after the order attaches to the same patient record, whichever branch number it came in on. And the operations director gets one list of what's pending across every location.
Routing is where the compliance work sits. Each order needs a clear dispensing location before it moves to billing, and that location needs to be the one that delivers. If your central team sets that field by hand on every order, it will drift. Make it a rule tied to the patient's address and the branch service areas, and have a person confirm the exceptions.
Before you consolidate: a checklist
Start with two branches, not all of them
Pick two locations with overlapping service areas, since that's where duplicate faxes and wrong-branch referrals are most common. Point both fax lines at one queue for a month and keep the branch teams doing what they do today in parallel. Count how many referrals arrived twice, how many landed at the wrong branch and how long each sat before someone owned it. Those three numbers will tell you whether a full rollout is worth it and which rules your routing needs before you add the next location.
Then add branches one at a time. The first two take the longest because you're writing the service-area rules and the exception handling. After that, each new location mostly needs its fax line pointed at the queue and its zip codes added to the map.
One intake queue for every branch, with the right location on every order
DocuFindr pulls faxes from all of your locations into one queue, splits and classifies each packet, flags duplicates across branches and checks documentation before the order moves to billing. Your team reviews what it extracts. We're happy to walk through how it would fit your locations.