Your Billing System Isn't Your Process

A DME billing system records orders and claims. It doesn’t decide what your team is allowed to do next. For a national medical supply company we built for, that gap showed up as stalled intakes, reorders that slipped through, and months of training before every new offshore hire could work on their own.

The company ran on NikoHealth. It’s good software, and we didn’t replace it. We built the part it was never designed to be.

What are NikoHealth and Brightree good at?

Credit where it’s due. Both are built around the order, the claim and the paperwork a payer wants, and they do that well. NikoHealth advertises task management, instant order-status notifications for sales teams, referring providers attached to each order, an automated resupply engine and KPI reporting. Brightree offers intake and order automation, automated payment posting, and a full suite of analytics and reporting.

If your problem is billing, either one is a serious answer. Our client’s problem wasn’t billing.

Where did the process fall through?

The company had been through three ERP systems before we met, NikoHealth being the third. All three handled orders and revenue cycle management. None of them guided an offshore team through a defined, controlled process, and none gave management KPIs it could act on without building reports by hand.

In practice, that meant:

• The process depended on nobody making a mistake. It only worked if everyone on the team knew the system well and got every step right. Nothing stopped a patient moving to the next stage with insurance unverified or a checklist half done, and every manual entry was one more chance for an error.
• Management couldn’t see the flow as it happened. There was no real-time view of how many patients sat in each stage, how long each one had been there, or which accounts were going stale because nobody had acted on them.
• The automation didn’t know where anyone stood. It couldn’t tell which stage a patient was in, when they were last contacted or whether they’d answered. So it couldn’t warn management or the team when a patient started slipping through the cracks.
• New offshore staff took four to six months to get up to speed, and turnover meant someone was always new.
• Management spent more than 50 hours a month¹ on reporting, and the channel data underneath it was still imperfect.

Back office or running the company?

Switching ERPs three times didn’t close the gap, because the missing piece was never the ERP. It was the flow of work around it.

What does a process layer look like?

We kept NikoHealth for billing and orders and built a controlled process beside it:

• Leads that go straight in. The system takes in lead data from calls, web forms and ads and pushes it into NikoHealth, the backend system. No double entry, and no new patient typed in by hand.
• Stages and gates. Every patient moves through defined stages from intake to shipment. Each stage has a checklist, and the system forwards the patient or fails them back based on the answers.
• Exceptions on the record. A manager can approve a skip. The approval is logged.
• The pipeline on one screen. Management sees the patients in every stage in real time, including the ones going stale, instead of waiting for a month-end report.
• Compliance with a person in charge. GenHealth reviews each patient’s records against payer requirements, and a team member approves or declines.
• Reorders management can track. The system follows every reorder and shows management, in a simple table, which ones started on time and which are held up or delayed. Outreach by text and email begins 14 days before each date of service, so a reorder that stalls shows up with time to act.
• API first, RPA where the API can’t reach. Writing back to NikoHealth goes through its API wherever possible.

What changed?

Intake and reorder needed 30%² fewer offshore staff. The order error rate fell below 1%³. The month-end reporting went away, because the numbers were already live. And the company never changed its billing system. The full case study has the baseline, the build and the running cost.

Should you replace your billing system instead?

Probably not. Our client tried that twice. If your billing system handles orders, claims and documentation well, the cheaper and safer move is to keep it and build the process it lacks. Replacing a billing system is a large, risky project, and it rarely fixes a process problem. We cover the general version of that question in can you automate with the software you already have.

When isn’t it worth it?

If a small, experienced in-house team runs intake and nobody is new, the task list in your billing system may be enough. A process layer pays off when an offshore or high-turnover team does the work, or when mistakes are turning into denied claims.

The short answer is on its own page: how medical supply companies control intake and reorders. If your team is working around your billing system every day, bring us that one process.