Before dispensing a refill of recurring DMEPOS supplies, the supplier must contact the beneficiary or representative and obtain an affirmative response confirming that the refill is needed.
The contact and response must occur within 30 calendar days of the expected end of the current supply. The refill cannot be delivered sooner than 10 calendar days before the current product is expected to run out or reach the end of its usage period. Automatic shipments based only on a predetermined schedule are not permitted.
Why Refill Documentation Matters
Recurring supplies can generate predictable monthly or quarterly orders, but predictable usage does not remove the supplier’s responsibility to confirm each refill.
Patients may:
- Stop using the product
- Change the frequency of use
- Enter a hospital or facility
- Receive supplies from another company
- Change products
- Accumulate unused supplies
- Lose Medicare eligibility
- Ask to delay or cancel delivery
A refill workflow should therefore verify present need rather than assume continued need from a previous order.
The Core Medicare Refill Rules
No Automatic Shipment
A supplier should not automatically ship refills on a predetermined schedule, even when the beneficiary previously agreed to recurring deliveries.
The patient or representative must actively confirm the need for the specific refill before it is dispensed.
Contact Within the 30-Day Window
The contact and affirmative response must occur within 30 calendar days of the expected end of the current supply.
The patient does not have to physically count every remaining item. The purpose is to confirm that the existing supply is expected to end and that another shipment is needed.
Do Not Deliver Too Early
The supplier must not deliver the refill sooner than 10 calendar days before the expected end of usage for the current product.
Multiple Communication Methods Are Allowed
Suppliers may obtain refill confirmation through:
- Telephone calls
- Text messages
- Online portals
- Other communication methods that capture the required information
Automated communication can be used when the record clearly shows the beneficiary’s identity, the item, the date of contact and an affirmative response.
What Must Be Documented for Shipped Refills?
Before shipping, the refill record should include:
- Beneficiary’s name
- Date of contact
- Item requested
- Confirmation from the beneficiary or representative
- An explanation showing why the refill is needed
CMS specifically requires these elements for shipped refill items.
A strong record should also include:
- Name and relationship of the representative, when applicable
- Quantity requested
- Expected end date of the current supply
- Communication method
- Staff member or system that captured the response
- Shipment date
- Delivery date
- Tracking or proof-of-delivery information
- Any reported change in usage
These additional details help connect the refill request, shipment and claim into one clear timeline.
What Counts as Documentation for an In-Person Refill?
For supplies obtained in person from a retail location, CMS considers either of the following sufficient as refill-request documentation:
- A delivery slip signed by the beneficiary or representative
- A copy of the itemized sales receipt
The receipt or slip should identify the item and date clearly enough to support the transaction.
A Practical Seven-Step Refill Workflow
Step 1: Calculate the Expected End Date
Use the previous delivery date, quantity supplied and prescribed frequency to estimate when the current supply is expected to end.
The system should generate a contact window based on that date, not simply on a fixed calendar shipment schedule.
Step 2: Contact the Beneficiary
Contact the patient or authorized representative within the permitted 30-day period.
The request should identify the actual items rather than ask a vague question such as, “Do you need your usual order?”
Step 3: Obtain an Affirmative Response
The beneficiary must actively confirm the refill.
Silence, an unanswered message, a previously checked consent box or the absence of a cancellation request should not be treated as confirmation.
Step 4: Confirm the Specific Items
Ask whether each item is still required.
For example, a patient may need one supply but no longer need another product that was previously shipped in the same order.
Step 5: Document the Response
Record the required information immediately.
Avoid copying the previous month’s note or entering a generic statement that does not identify the patient, item and response.
Step 6: Schedule the Delivery
Make sure the shipment or delivery will not occur earlier than the permitted 10-day period.
Shipping time should be considered when selecting the dispatch date.
Step 7: Retain Proof of Delivery
Keep the shipping record, tracking confirmation, delivery ticket, itemized receipt or other applicable proof of delivery with the refill documentation.
The dates should form a logical sequence:
- Refill contact
- Affirmative response
- Shipment
- Delivery
- Claim submission
Sample Refill Documentation Note
On [contact date], [beneficiary or representative name] confirmed the continued need for [specific item and quantity]. The current supply is expected to end on [date]. The beneficiary reported [brief explanation of need or usage status]. Refill delivery is scheduled for [date]. Confirmation was received through [telephone, text, email or portal].
The wording can be adjusted to the supplier’s workflow, but the final record should clearly demonstrate who requested the refill, what was requested, when confirmation occurred and why the refill was needed.
Common Refill Compliance Mistakes
Shipping Without a Response
A message sent to the patient is not the same as an affirmative response from the patient.
Using Negative-Option Language
Instructions such as “We will ship unless you cancel” do not establish affirmative need.
Contacting Too Early
Contact made outside the permitted window may not support the refill.
Delivering Too Early
Even when the confirmation date is valid, the delivery date must also meet the timing requirement.
Using a Generic Monthly Note
A note that says “patient needs supplies” without identifying the item, date and response may be insufficient.
Failing to Separate Items
A patient’s confirmation for one product should not automatically be applied to every item in a recurring order.
Keeping Conflicting Dates
The contact date, expected exhaustion date, shipment date and delivery date should support the same refill timeline.
Refill Audit Checklist
Before submitting a claim, confirm that the file contains:
- Valid order
- Applicable medical-necessity documentation
- Beneficiary or representative name
- Refill contact date
- Specific item requested
- Affirmative response
- Explanation of need
- Expected end date of current supply
- Shipment or pickup date
- Proof of delivery
- Correct quantity
- Correct HCPCS code
- Required modifiers
- Valid date of service
Frequently Asked Questions
Can a supplier use automated text messages?
Yes, provided the captured record identifies the beneficiary, item, contact date and affirmative response.
Must the patient count every remaining supply?
No. CMS states that the patient does not have to count the remaining supply. The supplier must still obtain confirmation that the refill is needed within the required period.
Can supplies be delivered more than 10 days before the expected end date?
Medicare’s current refill guidance states that delivery must not occur sooner than 10 calendar days before the end of usage for the current product.
Do the same rules apply to every commercial or Medicaid plan?
Not necessarily. Commercial insurers and state Medicaid programs may maintain different refill, quantity and authorization policies. Suppliers should verify the requirements of each payer.
Final Takeaway
A compliant refill workflow should prove that the patient needed the supplies at the time they were dispensed.
The safest approach is to calculate the expected end date, obtain item-specific confirmation within the permitted window, control the delivery date and retain a complete record connecting the request to the claim.
