Book a call

Choose who to talk to

Pick who you’d like to speak with and book a time that works for you.

Dima Blyshchyk, CEO & Founder at Mitrix

Dima Blyshchyk

CEO & Founder

Max Fedaraka, Head of Business Development at Mitrix

Max Fedaraka

Head of Business Development

By Dzmitry Blyshchyk · Mitrix Technology
HealthcareSoftware development

DME software development: from order intake to proof of delivery

Mitrix's team walks through the DME workflow we have built for a US equipment network: intake, eligibility, supplier sourcing, delivery, proof of delivery, billing and resupply.

A DME order looks small on paper: a walker, a hospital bed, an oxygen concentrator. The work behind it is not small. Someone confirms the referral, checks coverage, finds a supplier with stock, schedules delivery, collects a signature at the door, records the serial number, and turns the visit into a clean claim. Then the patient needs resupply, and the loop starts again.

Many DME platforms cover one or two of those steps. The failures show up at the handoffs, where an order leaves the EMR, enters a supplier portal, comes back as a delivery note and ends up in billing as a re-keyed line item. This article maps the full loop and the modules that keep it from breaking.

The loop, step by step

  1. Referral and intake. Capture the referral source, patient, caregiver, prescriber, equipment, diagnosis and documentation. Validate that the order is complete before it reaches a supplier.
  2. Eligibility and authorization. Check the payer, plan, coverage and prior authorization. Store the response, the timestamp and the reference number.
  3. Supplier sourcing. Match the item to a supplier that serves the patient’s area, has stock and accepts the payer. Record substitutions and who approved them.
  4. Order confirmation. Confirm quantities, rental or purchase, delivery address, contact details and special instructions. Send the confirmation to the patient and the supplier.
  5. Scheduling and dispatch. Assign a delivery window, route and technician. Notify the patient. Handle rescheduling without losing the original commitment.
  6. Delivery and proof of delivery. Capture the recipient, signature, timestamp, location, items, serial or lot numbers, setup check and any refusal. Work offline when the address has no signal.
  7. Billing and reconciliation. Turn the delivery into claims-ready data. Reconcile what was ordered, delivered and billed.
  8. Resupply. Track eligibility windows, patient contact, equipment changes and recurring orders. Start the next cycle before the patient runs out.

Model the order as a chain, not a row

A lot of the pain in DME starts in the data model. An order is not a single record with a status field. One order can include several items, each with its own supplier, availability, authorization and delivery. A delivery can be partial. A claim can be split. A resupply can reuse the original order or start a new episode.

The entities worth separating:

  • patient and caregiver
  • referral source and prescriber
  • payer, plan and authorization
  • supplier and service area
  • item, SKU, rental or purchase
  • order and order line
  • delivery, route and proof
  • document and claim
  • resupply schedule

Each entity needs an external ID, a source system and a last-verified timestamp. When two systems disagree, the team needs to know which record is authoritative and when it was last confirmed.

Status transitions with reasons

When a status only says “Pending”, support has to ask what is missing. The label can mean missing documentation, an unverified payer, an out-of-stock item or a patient who has not answered the phone. Store the reason code, the owner and the next action. Report on reasons as well as counts.

Where the loop breaks

Patient identity

Referrals arrive with a name, date of birth and sometimes a member ID. The EMR has one ID, the payer another, the supplier a third. Matching on name and date of birth alone creates duplicates and, worse, merges two patients. Build a crosswalk with deterministic rules, keep the source IDs, and send ambiguous matches to a human queue. Never overwrite the source record with the merged one.

Eligibility at the wrong moment

Eligibility checked at intake can be wrong by the time the equipment ships. Coverage changes, authorizations expire, and the payer may require a different code. Check at intake, before dispatch and before billing. Keep the response and the timestamp. A stale check is often worse than no check because it looks like evidence.

Inventory across suppliers

Availability is not a number in a table. It depends on service area, delivery capacity, rental pool, purchase stock, substitutions and supplier contracts. Show the supplier’s confirmed availability, not a hopeful estimate. When a substitution is allowed, record who approved it and why.

Proof of delivery

Proof of delivery is where paper survives longest. A signature on a phone is not enough. Capture the recipient, relationship to the patient, timestamp, location, items, serial or lot numbers, setup check and a photo when policy allows. Support offline capture, because home deliveries happen in basements and rural areas. A failed delivery needs a reason code and a next action, not a blank note.

Billing handoff

Every re-keyed field is a chance to lose margin. The order should produce claims-ready data: payer, authorization, item, quantity, rental period, delivery date, proof and documentation. If billing lives in another system, send a structured payload and reconcile the response. Do not ask the billing team to reconstruct the story from PDFs.

Resupply

Resupply is a separate workflow with its own rules. Medicare and commercial payers set different intervals. The patient may have changed address, plan or equipment. The original order may no longer be valid. A resupply queue should show eligibility, last delivery, next eligible date, patient contact status and the reason for the call. Recurring orders without those checks create denials and wasted deliveries.

What the patient sees

Patients experience the loop through a few surfaces: the confirmation call, the delivery window, the equipment handover and the resupply reminder. A portal can improve all four, but only if it reflects the same order state the operations team sees. A portal that shows “processing” while the supplier has no stock creates more calls than it prevents.

Keep patient-facing status simple and honest. “Scheduled for Tuesday, 9am to 12pm” beats a five-stage tracker that nobody updates. Give patients one place to change an address, request resupply or report a problem, and route those changes back into the order with an audit trail.

Integrations that decide the project

Four integrations carry most of the value:

  • EMR and referral sources. Admissions, discharge and transfer events, orders and documentation. HL7 v2 is common; flat files and vendor APIs are common too.
  • Payer and eligibility. Real-time checks, authorization status and claim responses. In the public Mitrix DME case, this is Waystar.
  • ERP and accounting. Pricing, purchasing, invoices and payments. Sage, Dynamics GP, QuickBooks and Infor Lawson appear in the same case.
  • Delivery and logistics. Routes, driver apps, proof of delivery and tracking.

Start with the EMR and eligibility. They remove the most manual work and produce the data the rest of the loop needs. A patient portal is valuable, but it will not fix a broken intake process.

Metrics to instrument

Dashboards should answer operational questions:

  • How long from referral to first delivery?
  • What share of orders ship within the promised window?
  • How many deliveries fail on the first attempt, and why?
  • What share of claims are denied for missing documentation?
  • How many days in accounts receivable?
  • What is equipment spend per order, including substitutions and rentals?
  • How many resupply orders are due, and how many are actually reached?

The public Mitrix case reported 93% of delivery orders completed by suppliers within 6 hours, 64% faster order creation, up to 25% lower equipment spend and 2x settlement velocity. Those numbers map to the loop above: faster intake, better delivery coverage, lower spend and faster settlement.

Build versus buy

Homecare and hospice EHRs often include a DME module. It can be the right start when your workflow matches the vendor’s assumptions and you do not run a supplier network. It becomes a constraint when you need custom rules per payer, consolidated billing, delivery tracking or a patient portal that the EHR does not offer.

A standalone DME platform brings breadth, but integration and customization costs are real, and migration is slow. The middle path is common: keep the EHR as the clinical record, build an orchestration layer for intake, supplier sourcing, delivery and billing, and integrate instead of replace.

Questions that clarify the decision:

  • Does the workflow differentiate your business, or is it standard?
  • How many payers, suppliers and service areas do you support?
  • Do you need multi-tenant isolation for network partners?
  • Is the EHR vendor shipping the missing module in the next 12 months?
  • Can you expose the data your partners need without giving them your whole database?

If the workflow differentiates the business, a custom layer usually pays for itself. If the workflow is standard and the volume is low, configure the platform you already own.

QA for delivery workflows

Test the paths that operations teams know by heart: partial deliveries, substitutions, duplicate orders, expired authorizations, failed deliveries, offline signatures, time zones and patients who refuse equipment. Check data consistency across UI, API and database. Run a release gate on proof-of-delivery capture and billing handoff, because those failures are expensive and hard to reverse.

How Mitrix built a DME network

Mitrix built a DME network for a US healthcare provider that connects hospitals, hospices and equipment suppliers in one process. The work covered EMR integration, HL7 XML, insurance checking, a medical device catalog, custom EMR rules, prescription workflows, visits and utilization reports, and ERP integrations.

The stack included .NET, Angular, Azure Functions, Azure SQL, Service Bus and Blob Storage. The outcome is public: faster order creation, more deliveries inside the promised window, lower equipment spend and faster settlement. You can read the DME case study or see the wider healthcare practice.

If you are replacing paper intake or a legacy DME module, book a healthcare call. Bring the order flow that hurts most, and we will map it against the loop above.

A 90-day starting plan

Week 1 to 3: map the current loop, count the handoffs and pick one order type. Measure the baseline.

Week 4 to 8: build intake, eligibility and a status model with reasons. Connect the EMR read-only.

Week 9 to 12: add delivery and proof of delivery, then the billing payload. Reconcile daily.

Leave the portal for later. Intake and delivery carry the first month of value.



You might also like

FAQ

Frequently asked questions

What does DME software need to do?

DME software should cover referral intake, eligibility and authorization, supplier sourcing, order confirmation, delivery, proof of delivery, billing and resupply. The handoffs between those steps matter more than any single screen.

Can we use our EHR’s DME module instead of custom software?

Often, yes, if your workflow is standard and you do not run a supplier network. A custom layer makes more sense when you need payer-specific rules, consolidated billing, multi-supplier delivery tracking or a patient resupply portal the EHR does not offer.

How do you handle proof of delivery for home equipment?

Capture the recipient, signature, timestamp, location, items, serial or lot numbers and setup check. Support offline capture, and give failed deliveries a reason code and a next action.

Which integrations matter most in a DME platform?

EMR and referral sources, payer eligibility and authorization, ERP and accounting, and delivery logistics. Start with the EMR and eligibility because they remove the most manual work.

Do you have DME experience?

Yes. Mitrix built a US DME network connecting hospitals, hospices and equipment suppliers, with EMR integration, HL7 XML, insurance checking, custom rules, reporting and ERP integrations. The public case reports 93% of delivery orders completed within 6 hours and 64% faster order creation.