---
title: "Patient resupply: the workflow that decides DME retention"
description: "Why DME resupply breaks, how to design the queue, what to automate, and which metrics show whether patients stay equipped and retained."
url: "https://mitrix.io/blog/patient-resupply-workflow-dme-retention/"
author: "Dzmitry Blyshchyk"
date: 2026-11-10
---

# Patient resupply: the workflow that decides DME retention

Resupply is the quiet revenue engine in DME. The first order gets attention. The second, third and twelfth orders decide whether the patient stays equipped and whether the provider gets paid.

It is also where operations teams spend a surprising amount of time. Eligibility goes stale, patients change addresses, payers change intervals, and the original order no longer matches the equipment in the home. Software that only creates a new order misses the work that makes the order correct.

## Why resupply breaks

**Eligibility changes.** A patient may have a new plan, a new member ID or a coverage gap. A resupply order created from the original record can be wrong before anyone calls.

**Intervals vary.** Medicare and commercial payers set different resupply intervals by item and circumstance. The interval is not a single date field; it depends on the item, the payer, the last delivery and the documentation.

**Contact is hard.** Patients do not answer unknown numbers. Caregivers change. Preferences change. A queue that does not show contact history and preferred channel produces repeated calls and missed orders.

**Equipment changes.** The patient may need a different size, a replacement, a repair or a discontinued item. The resupply order needs a way to capture the change without losing the original history.

**Delivery capacity.** Confirming the order is not the same as scheduling the delivery. A supplier with no capacity creates a promise the operations team cannot keep.

## A concrete resupply case

A patient has been using a nebulizer and disposable supplies for three months. The next resupply window opens in ten days. The original order has the right item, but the patient has moved to a new plan and the caregiver’s phone number has changed.

A queue that only looks at the last delivery date creates the order on time and sends it to the old address. A better workflow checks eligibility, confirms the address and contact, asks whether the equipment still works, and records the patient’s preferred channel. The order is created from the confirmed facts, not from the original record.

That sounds like more work. It is less work than a failed delivery, a returned order and a denial.

## The workflow

1. **Check eligibility.** Confirm the plan, member ID and resupply coverage before outreach.
2. **Calculate the window.** Use the item, payer, last delivery and documentation to determine the next eligible date.
3. **Contact the patient.** Use the preferred channel, record the outcome and schedule the next attempt.
4. **Confirm the order.** Confirm the item, quantity, address, equipment condition and any change.
5. **Create the order.** Reuse the original order as a template, not as the source of truth.
6. **Fulfil and deliver.** Reserve stock, schedule delivery and capture proof of delivery.
7. **Bill and reconcile.** Send claims-ready data and reconcile what was delivered with what was billed.
8. **Schedule the next cycle.** Update the next eligible date from the actual delivery, not the original plan.

## Designing the queue

The queue is the product. It should show the patient, item, next eligible date, eligibility status, last contact, last delivery, payer and the reason the order is blocked. Sort by urgency and revenue at risk, not by alphabetical order.

Every status needs a reason. “Pending” can mean no answer, stale eligibility, missing documentation, no stock or patient refusal. The reason determines the next action and the report that operations reviews on Monday.

Give the patient one place to confirm, reschedule or request a change. A portal that shows the same order state as the operations team reduces calls. A portal that shows “processing” while the supplier has no stock creates more work.

## Eligibility and interval logic

Treat eligibility and interval as rules, not fields. Eligibility depends on the payer, plan, member ID and date. The interval depends on the item, the payer, the last delivery and the documentation. Both can change between the first order and the twelfth.

Store the inputs and the rule version. When a payer changes a policy, you need to know which orders were calculated under the old rule. A single “next date” column cannot answer that question.

## Communication design

Patients ignore calls from unknown numbers and change channels between episodes. Capture the preferred channel, the best time and the caregiver’s authority. Log every attempt and outcome. If the patient asks to be contacted through the portal, do not keep calling.

Make the message specific: what is due, what will be delivered, when, and what the patient needs to do. A generic “your order is ready” creates a call. A specific window and item list reduces it.

## What to automate

Automate the repeatable checks: eligibility, interval calculation, address validation, order template creation, reminders and status updates. Keep a human on the exceptions: a changed equipment need, a coverage dispute, a caregiver who cannot be reached, a clinical question.

Do not automate outreach without consent and a communication preference. A missed call is a nuisance; a compliance complaint is worse.

## What good looks like

A good resupply workflow has a queue that explains itself, an eligibility check that is current, a patient contact history that is visible, an order that is easy to correct, a delivery status that is real and a next cycle that is calculated from the actual delivery. If any of those is missing, the team will compensate with calls and spreadsheets.

The test is simple: can a new coordinator pick up the queue on Monday and know what to do next without asking the person who built it?

## Metrics

- Resupply orders due versus completed.
- On-time resupply rate.
- Patient contact and confirmation rate.
- Denial rate by reason.
- Days from eligibility to delivery.
- Patient churn and revenue per patient.
- Cost to serve per resupply order.

These metrics connect the portal to the P&L. A beautiful portal that does not improve on-time resupply is a cost center.

## Integrations

Resupply touches the EMR, the payer, the DME ERP, the delivery system and the CRM. Start with the EMR and eligibility. Add delivery and billing after the queue is stable. Reconcile the next eligible date against the actual delivery, because the original order is not evidence that the equipment arrived.

## Build versus buy

DME ERP and EHR modules often include resupply. They can be the right start when the workflow is standard and the payer mix is simple. Build or extend when resupply is a retention engine, when the portal is part of the product, or when the existing system cannot show the reason an order is blocked.

The middle path is common: keep the ERP as the system of record and build the queue, patient portal and communication layer around it. Integrate the status back so operations sees one version of the truth.

## How Mitrix fits

Mitrix built a patient portal with resupply for a US DME network. Patients manage orders, resupply, documents, communication preferences and guest orders; a browser extension gives care teams patient context and clinical fields. The same program reported 93% of delivery orders completed by suppliers within 6 hours and 64% faster order creation.

Read the [DME case study](/portfolio/healthcare-medical-record-management/) or the broader [order-to-delivery guide](/blog/dme-software-development-order-intake-proof-of-delivery/). If resupply is where your operation leaks revenue, [talk to us](/contacts/).
