General 8 min read

The Seven-Year File: What a Medicare-Ready DME Documentation Stack Actually Contains

The Seven-Year File: What a Medicare-Ready DME Documentation Stack Actually Contains
V

Virtual Nexgen Team

Published on November 16, 2026

A documentation request arrives for a Medicare claim paid two years ago. The response deadline is approaching, and the file was assembled across several systems by people who may no longer work for you.

That is the difference between having a file and having the retrievable file: complete, organized, and producible on demand years after the delivery. CMS’s DMEPOS General Documentation Requirements page was last modified November 25, 2025. It says suppliers must keep proof of delivery (POD) for seven years from the date of service and provide documents to the DME Medicare Administrative Contractor (MAC) when requested.

If you’re building a repeatable documentation workflow, Virtual Nexgen’s administrative support team can help manage file assembly and completeness checks within your existing systems. The compliance decisions still belong to your qualified clinical and billing leaders.

What CMS says a DME claim file must support

CMS identifies four elements suppliers must meet to justify payment:

  • Standard written order (SWO)
  • Medical record information, including continued need and use when applicable
  • Correct coding
  • Proof of delivery

These are requirements, not a suggestion to create a particular filing format. The Medicare Program Integrity Manual, Chapter 5, section 5.10 sets out supplier documentation and POD requirements, including seven-year retention from the date of service. CMS also points suppliers to Article A55426: Standard Documentation Requirements for All Claims Submitted to DME MACs, which provides broader guidance and notes that item-specific policies may add requirements.

Your file needs to support the claim as billed. A folder containing some paperwork is not enough if the order, medical record support, coding detail, or delivery evidence cannot be connected to that claim.

Check each standard written order element

CMS says an SWO must contain:

  1. The patient’s name or Medicare Beneficiary Identifier (MBI).
  2. The order date.
  3. A general item description. CMS allows a general description such as “wheelchair” or “hospital bed,” a HCPCS code, a HCPCS code narrative, or a brand name or model number.
  4. The dispensed quantity, if applicable. Prescriptions may be refillable.
  5. The treating practitioner’s name or NPI and signature.

For equipment, the SWO may also list separately each concurrently ordered option, accessory, or feature that is separately billed or requires an upgraded code. For supplies, it may list separately concurrently ordered supplies that are billed separately.

Two timing and signature checks deserve special attention. First, CMS says signature and date stamps are not allowed except in limited circumstances described in PIM Chapter 3, section 3.3.2.4. Second, the treating practitioner must communicate the SWO before the supplier submits a claim. For certain items, CMS requires the written order before delivery. The applicable item list and current policy matter; the order-before-delivery requirement is not universal for every item.

A signature that turns out to be a stamp is not fixed by filing it more neatly. It needs review and, where appropriate, action by the practitioner’s office. That is why catching the issue at intake is more useful than discovering it during an audit.

Five file failures, and the workflow that prevents each

1. The written order came after delivery.
A verbal order may have started the process, but the timeline shows the item left before a required written order was in hand. For categories where CMS requires a written order prior to delivery, add a hold point at dispatch: confirm the required document is present before the item is released.

2. The signature is stamped, undated, or missing.
Use an intake checklist to flag the signature and date for review. Route exceptions promptly to the practitioner’s team while the order is recent. Staff can identify and route a potential issue; they should not alter a signed document or decide whether a signature meets CMS policy.

3. The medical record supports the device but not the relevant continued need or use.
Set a recurring documentation trigger tied to the applicable rental, refill, or resupply workflow. Do not assume a general calendar reminder captures every item-specific requirement. The applicable coverage policy and claim circumstances determine what supporting information is needed.

4. POD is incomplete.
A delivery record may be missing the date, signature, or item detail needed to connect what arrived with what was billed. Use a delivery-complete checklist before a record is marked done. For shipped items, make sure the supplier’s delivery record is clearly linked to the carrier’s tracking information, consistent with applicable requirements.

5. The file is spread across systems.
A signed order in email, delivery evidence in a carrier portal, and item details in billing software make retrieval slow and error-prone. Create one indexed claim file or retrieval point with a consistent naming convention, appropriate permissions, and a clear owner for exceptions.

Treat TPE education as an operating change

Under CMS’s Targeted Probe and Educate (TPE) program, a MAC reviews a probe sample, gives the supplier education about identified errors, and may repeat the process for up to three rounds. If issues do not improve, the matter may be referred for further action. CMS describes variations in the process, so do not assume every review follows an identical pattern.

The practical lesson: record what the MAC identifies, assign an owner, revise the relevant checklist or training, and test whether the change works. Filing the education letter without changing the workflow leaves the same gap in place.

CMS’s Recovery Audit Program also publishes item-specific review topics. For example, approved topics include documentation and medical necessity reviews involving Negative Pressure Wound Therapy, Prefabricated Knee Orthoses, and Surgical Dressings. These examples are a reminder that the general file structure is only the starting point; review the relevant item policy as well.

Assign ownership without crossing clinical boundaries

An administrative assistant can own the repeatable parts of the process:

  • Assemble claim documentation and check completeness against an approved checklist.
  • Maintain signature-chase queues and follow up on missing records.
  • Index POD and support the retrieval process.
  • Track assigned documentation triggers and report exceptions.
  • Run retrieval drills and log gaps.

Clinical and billing leadership should own medical necessity determinations, coding sign-off, policy interpretation, and the response narrative to the MAC. An assistant does not certify medical necessity or interpret coverage. The role is to organize, check, route, and escalate, not make clinical or coding judgments.

Run a two-hour retrieval drill

Choose five Medicare claims paid eighteen months ago. Ask the team to produce the complete file for each within a two-hour target. Record:

  • Whether all required documents were found.
  • Which document or detail was missing.
  • Where the search stalled.
  • How long retrieval actually took.
  • Who resolved each gap.

The target is an internal test, not a CMS deadline. Its value is diagnostic: it shows whether the file can be retrieved before a real request puts pressure on your team.

Build a more retrievable file in 30 days

Week 1: Run the drill and group failures by category: order, medical record, coding, POD, or retrieval.
Week 2: Standardize file naming and establish a single retrieval point in your approved systems.
Week 3: Add the SWO and POD checks to intake and delivery workflows, with a clear exception owner.
Week 4: Pilot the process for one item category and one payer. Review exceptions with clinical and billing leadership before expanding it.

Track retrieval time per file, first-pass completeness, stamped or undated signature counts, orders released before a required written order arrived, recertification completion where applicable, POD gaps, and audit-response cycle time. Measures are useful only when someone reviews them and acts on recurring failures.

FAQs about Medicare DME audit documentation

How long must DME suppliers keep proof of delivery?

CMS says suppliers must keep POD for seven years from the date of service and provide documents to the DME MAC on request. The Medicare Program Integrity Manual also addresses supplier documentation retention.

What must a standard written order contain?

CMS lists the patient’s name or MBI, order date, a general item description, dispensed quantity if applicable, and the treating practitioner’s name or NPI and signature. Separately billed equipment options or supplies may need to be listed separately.

Can a signature stamp be used on an SWO?

CMS says signature and date stamps are not allowed except in limited circumstances. Check the current Medicare Program Integrity Manual signature guidance and escalate uncertain cases to compliance leadership.

What documents justify a Medicare DME claim?

CMS identifies the SWO, medical record information including continued need and use when applicable, correct coding, and POD. Applicable item-specific policy may require additional documentation.

What is Targeted Probe and Educate?

TPE is a Medicare medical review program in which a MAC reviews a probe sample, provides education, and may repeat the process for up to three rounds. The process and next steps can vary; see the current CMS TPE information.

Can a virtual assistant assemble audit documentation?

Yes. A trained assistant can organize records, run completeness checks against your approved checklist, manage follow-up queues, and help retrieve files. Qualified clinical and billing leaders should retain responsibility for coverage interpretation, coding, medical necessity decisions, and audit responses.

Make documentation easier to retrieve

A seven-year retention requirement only helps if your team can locate the right file and show how its records support the claim. Virtual Nexgen provides dedicated, 1-on-1 healthcare-trained virtual assistants who can support file assembly, completeness checks, and signature follow-up inside your existing workflows. Our structured five-step onboarding and quality assurance process helps define responsibilities, escalation points, and privacy-first handling for protected health information.

Explore Virtual Nexgen administrative support or schedule a 30-minute conversation.

Disclaimer: This article provides general information, not legal, clinical, or coding advice. Medicare requirements and item-specific policies can change. Confirm current rules with your DME MAC and compliance counsel before changing your procedures. The CMS DMEPOS General Documentation Requirements page cited here was last modified November 25, 2025.

CMS sources

Work With Virtual Nexgen Solutions

If your business needs dependable virtual assistant support, Virtual Nexgen Solutions can provide support around your existing workflow. Book a discovery call today.

Get in Touch Now!