A general medical billing platform is built around an episode: a patient is seen, a service is coded, a claim goes out, payment comes back. DME/HME billing software doesn’t work that way. You’re billing for a physical asset that has to be purchased, tracked, delivered, documented, sometimes serviced, and often billed monthly for a year or more. The billing logic isn’t a variation on physician billing — it’s a different data model.
That distinction shows up in specific places.
Rentals aren’t a billing feature — they’re the core
A general platform bills a service once. DME software has to run capped rental schedules, know which month a claim is in, apply the right modifiers, and stop billing when the cap is reached. Oxygen runs on its own 36-month rule with separate maintenance logic. Get this wrong and you’re either leaving money uncollected or generating overpayments you’ll return with interest.
Claims route to different contractors
DMEPOS claims go to DME MACs — four jurisdictions with their own Local Coverage Determinations and policy articles. A platform built for physician billing routes to Part A/B MACs and doesn’t carry DME LCD edits.
Documentation requirements have no equivalent
A standard written order before delivery, proof of delivery with a signature, a face-to-face encounter for items on the CMS master list, prior authorization for specific HCPCS codes. There’s no field in a general billing platform for proof of delivery, because a general billing platform never delivers anything.
The claim depends on inventory
You can’t bill a serialized item you can’t confirm you delivered. Billing and inventory are the same record.
General medical billing platform | DME/HME-specific platform | |
Billing unit | Encounter or procedure | Item — purchased, rented, or resupplied |
Coding | CPT / ICD-10 | HCPCS + DMEPOS modifiers (KX, RR, NU, GA/GY/GZ) |
Recurring billing | Rare; usually add-on | Capped rentals, oxygen 36-month cap, resupply cadence |
Payer routing | Part A/B MACs, commercial | DME MACs (Jurisdictions A–D), DME LCDs |
Documentation | Chart notes, encounter records | SWO, proof of delivery, face-to-face, CMN |
Prior auth | Procedure-driven | HCPCS-driven, CMS master list, required before delivery |
Inventory | Not applicable | Serialized assets, service history, reorder logic |
Delivery | Not applicable | Routing, e-signature, field-to-office sync |
Same/similar checks | Not applicable | Required before dispensing |
Fee schedules | RVU-based | DMEPOS fee schedule, competitive bidding rates |
Why the gap costs money
CMS puts the FY2025 improper payment rate for DMEPOS at 24.12% — the highest of any Medicare fee-for-service claim type, against a 6.55% national rate (CMS CERT). Most improper payments across Medicare FFS aren’t fraud. They’re cases where a reviewer couldn’t determine whether a payment was proper because the documentation wasn’t there.
A general platform will happily submit a claim with a missing written order. It has no rule that says otherwise. The denial arrives weeks later, and by then the equipment is in a patient’s home.
The practical test: ask whether the system knows what month of a capped rental you’re in, and whether it will stop you from billing without proof of delivery. If it can’t, it isn’t DME software. It’s a billing tool that accepts DME claims.
