DME Billing: A Revenue Integrity Guide to DMEPOS Documentation, Claims, and Compliance
Updated: Sep 16
A patient needs a wheelchair. The physician agrees. The supplier delivers it. The claim gets denied.
That sequence is the defining frustration of DME billing, and it happens because Medicare doesn't pay for equipment being necessary — it pays for equipment being necessary and documented in a specific way, coded correctly, delivered with proof, and claimed within the rules that applied on that date of service. Any one of those can fail independently of the clinical facts.
The DMEPOS revenue cycle runs documentation → coding → coverage → delivery → claim → payment, and a break anywhere upstream surfaces as a denial downstream, usually weeks later and usually attributed to the wrong cause. This guide works through each link, with particular attention to what changed in 2026 — because two significant CMS changes took effect this year that alter how suppliers maintain billing privileges and which items require prior authorization.
Key Takeaways
• CMS requires four things to justify payment on a DMEPOS claim: a Standard Written Order, supporting medical record information, correct coding, and proof of delivery.
• Effective January 1, 2026, DMEPOS accreditation moved from a 36-month cycle to at least every 12 months — the most consequential operational change for suppliers this year.
• Effective April 13, 2026, CMS added items to the Required Face-to-Face/WOPD List and Required Prior Authorization List, including oxygen and pneumatic compression codes.
• Proof of delivery must be retained 7 years from the date of service, and requirements differ by delivery method — direct, shipped, or to a nursing facility.
• Being on the Master List is not the same as being subject to a requirement; only items named on a Required List carry the condition of payment.
• A paid claim is not necessarily a correctly paid claim — underpayments and contractual variances hide inside claims that never denied.
• Requirements vary by item, payer, and coverage policy; no single checklist applies to every DME product.
What Changed in 2026
MAJOR CHANGE — ACCREDITATION CYCLE Under the CY 2026 Home Health Prospective Payment System Final Rule, effective January 1, 2026, DMEPOS suppliers must be surveyed and reaccredited at least once every 12 months, replacing the long-standing 36-month cycle. Suppliers already inside a three-year term finish that term; the annual requirement begins when it expires. Suppliers first accredited on or after January 1, 2026 move to annual reaccreditation one year after their initial effective date. The rule also removed the provision letting a new location operate under temporary accreditation without a survey — all locations must now be surveyed before accreditation. |
There's a second piece worth knowing: a change in majority ownership (more than 50% direct) within 36 months of Medicare enrollment can require enrolling as a new DMEPOS supplier and completing a full survey and accreditation, unless an exception applies. For suppliers planning a sale or acquisition, that timing matters.
MAJOR CHANGE — PRIOR AUTHORIZATION AND F2F/WOPD CMS published updates to the Master List, the Required Face-to-Face and Written Order Prior to Delivery List, and the Required Prior Authorization List in the Federal Register on January 13, 2026, effective April 13, 2026. Additions included oxygen HCPCS codes to the F2F/WOPD List and pneumatic compression device and orthotic codes to the Required Prior Authorization List. Further orthotic and prosthetic additions carry dates of service on or after October 28, 2026, some phased by state. The CY 2026 Home Health PPS Final Rule also includes a provision allowing temporary exclusion from mandatory prior authorization for suppliers maintaining a prior authorization approval rate of 90 percent or greater. |
Confirm current list contents and effective dates against CMS and your DME MAC before relying on any of this operationally — these lists are updated periodically and were accurate as of this review.
The DME Revenue Cycle, Stage by Stage
Referral |
↓
Order (SWO) |
↓
Documentation & Medical Necessity |
↓
Eligibility & Coverage Review |
↓
Coding |
↓
Prior Authorization |
↓
Delivery |
↓
Proof of Delivery |
↓
Claim Submission |
↓
Adjudication |
↓
Payment or Denial |
↓
Appeal & Account Resolution |
Stage | Common Failure | Quality Check Before Moving On |
Referral | Item ordered that the payer doesn't cover for this patient | Confirm coverage before committing inventory |
Order (SWO) | Missing a required element or an unsigned order | All SWO elements present and signed |
Documentation | Medical record doesn't independently support necessity | Record supports the item, not just the diagnosis |
Eligibility & coverage | Benefit checked but policy criteria never reviewed | Both eligibility and the item's coverage policy confirmed |
Coding | HCPCS selected by product name rather than verified description | Code matches item, quantity, and coverage policy |
Prior authorization | Item on a Required List delivered without approval | PA status confirmed against current Required List |
Delivery | Item delivered before a required WOPD was on file | Order complete and on file before delivery, where required |
Proof of delivery | POD missing an element or unlinked to shipping records | POD complete per the method used |
Claim submission | Date of service doesn't match delivery documentation | DOS aligns with POD and delivery method rules |
Payment | Paid amount assumed correct because it wasn't denied | Payment compared against expected allowable |
The Four Pillars of a Payable DMEPOS Claim
CMS states that to justify payment, suppliers must meet four requirements: a Standard Written Order, medical record information (including continued need and use where applicable), correct coding, and proof of delivery. Every denial-prevention control worth building maps back to one of those four.
Pillar 1 — The Standard Written Order
All DMEPOS claims billed to Medicare require a written order or prescription from the treating practitioner as a condition of payment. The SWO replaced the older patchwork of order types — the Detailed Written Order, Five and Seven Element Orders, and Detailed Product Description — with a single format, codified at 42 CFR 410.38(d)(1).
Required SWO Element | Detail Worth Getting Right |
Patient's name or Medicare Beneficiary Identifier | Either is acceptable; must match the claim |
Order date | A single date — when the order was communicated to the supplier |
General description of the item | Narrative description, HCPCS code, code narrative, or brand and model number all qualify |
Quantity dispensed, if applicable | Include separately billed options, accessories, or supplies as individual line items |
Treating practitioner's name or NPI | Either identifier is acceptable |
Treating practitioner's signature | Signature and date stamps are not permitted, with limited exceptions |
COMMON MISTAKE Treating the SWO as a billing formality rather than a clinical order. Where the treating practitioner is also the supplier and permitted to fill both roles, a separate SWO isn't required — but the medical record must still contain every required SWO element. The elements don't disappear; only the separate document does. | |
Pillar 2 — Medical Record Information
The SWO establishes what was ordered. The medical record has to establish why. For many items that means documentation of the clinical condition, the functional limitation the equipment addresses, and — for continuing rentals and recurring supplies — evidence of continued need and continued use. A record that names a diagnosis without connecting it to the specific item ordered is the single most common source of “insufficient documentation” findings.
Some items add a face-to-face encounter requirement. For items on the Required F2F/WOPD List, the encounter must be documented in the medical record itself history, physical exam, diagnostic tests, progress notes, or treatment plans rather than asserted on the order. Items newly added effective April 13, 2026 carry a face-to-face encounter within six months prior to the written order.
Pillar 3 — Correct Coding
HCPCS Level II codes identify DMEPOS items, and selecting one is a verification task, not a lookup. The code has to match the item actually furnished — including features, accessories, and upgrades that carry their own codes — and the units billed have to match what was delivered. Pricing, coverage criteria, and jurisdictional interpretation can all differ, so codes should be validated against current HCPCS files and the applicable DME MAC's policy article rather than carried forward from a prior claim or a product catalog.
Modifiers carry meaning that changes both payment and liability. A few that appear routinely on DMEPOS claims:
Modifier | General Purpose | Documentation Consideration |
KX | Attests that specified coverage criteria in the applicable policy have been met | Only append when the record actually contains the required documentation |
GA | Waiver of liability on file — an ABN was issued for an expected denial | The signed ABN must exist before delivery |
GY | Item is statutorily excluded or doesn't meet the definition of a Medicare benefit | Used to generate a denial for secondary payer purposes |
GZ | Expected to be denied as not reasonable and necessary, no ABN on file | Signals the supplier expects denial and holds liability |
NU / RR / UE | New purchase, rental, or used equipment | Must match how the item was actually furnished |
RT / LT | Right and left side | Laterality must be supported and billed per payer instruction |
COMPLIANCE ALERT A KX modifier is an attestation, not a payment tool. Appending it to move a claim past an edit without the underlying documentation is a misrepresentation — and it's the kind of pattern post-payment review is built to find. | ||
Pillar 4 — Proof of Delivery
Proof of delivery is a supplier standard under 42 CFR 424.57(c)(12), and CMS's CERT Task Force has repeatedly identified missing or incomplete POD as a top DMEPOS deficiency. Every POD, regardless of delivery method, needs the beneficiary's name, the delivery address, the quantity delivered, the date delivered, and a description of the item — narrative, HCPCS code, long code description, or brand and model.
Beyond that baseline, requirements differ by method:
Delivery Method | Additional Requirements | Date of Service on the Claim |
Method 1 — Direct delivery by supplier | Signature of the beneficiary or designee | The date the beneficiary received the item |
Method 2 — Shipping or mail order | Package tracking number, supplier invoice number, or another method linking supplier records to the delivery service's records, plus evidence of delivery | Ship date, label creation date, shipping service pickup date, or delivery date |
Method 3 — To a nursing facility | Method 1 or 2 requirements, plus documentation from the facility showing the items were provided to and used by the beneficiary | Per the underlying method used |
COMPLIANCE ALERT Suppliers, their employees, and anyone with a financial interest in the delivery are prohibited from signing for an item as the beneficiary's designee. When a designee does sign, the relationship to the beneficiary should be noted and the signature legible — if it isn't, the name should be printed on the delivery slip. | ||
RETENTION Proof of delivery and claims documentation must be kept for 7 years from the date of service and produced to the DME MAC on request. Store it indexed and retrievable — an audit response is only as fast as the filing system behind it. | ||
Master List vs. Required Lists: A Distinction That Costs Money
These are frequently conflated, and the confusion runs both directions — suppliers either apply requirements that don't exist yet, or miss ones that do.
List | What It Means | Operational Effect |
Master List | A library of DMEPOS items CMS has identified as potential vulnerabilities to the Trust Fund, per criteria at 42 CFR 414.234(b) | No direct requirement — inclusion only makes an item eligible for selection later |
Required F2F/WOPD List | Items selected and announced via Federal Register notice requiring a documented face-to-face encounter and a written order before delivery | Condition of payment — delivery before a compliant order can mean denial |
Required Prior Authorization List | Items requiring pre-approval before the claim will be paid | Condition of payment — affects scheduling, not just billing |
Power mobility devices sit on both the Master List and the F2F/WOPD List by statute. Everything else moves between lists by Federal Register notice, which is why a quarterly check against the current lists belongs in the compliance calendar rather than in anyone's memory.
Enrollment, Accreditation, Licensing, and Billing Privileges
Four distinct requirements, four different overseers, and failing any one of them can stop payment regardless of how clean the claims are.
Requirement | Purpose | Who Oversees It |
Medicare enrollment | Establishes the supplier in Medicare's systems via PECOS, with an NPI | CMS and its National Provider Enrollment contractors |
Accreditation | Independent verification against DMEPOS quality standards | CMS-approved accrediting organizations |
State licensing | Legal authority to operate and furnish specific items in a state | State licensing authorities |
Surety bond | Financial protection for the Medicare program under 42 CFR 424.57(d) | CMS contractor, via an authorized surety |
Billing privileges | The right to submit and be paid on claims — contingent on the above | CMS, administered through the DME MACs |
On the bond specifically: the base requirement is $50,000, and a supplier enrolling a new practice location generally needs that location covered by an additional base bond or a rider. CMS contractors can prescribe an elevated bond of $50,000 per occurrence of an adverse legal action in the preceding 10 years. Exceptions to the bond and accreditation requirements exist for certain supplier types — verify whether one applies rather than assuming.
EXPERT INSIGHT Enrollment and accreditation are often managed by different people in the same organization, on different calendars, with no shared view. With accreditation now on an annual cycle, that split is a genuine risk — one owner should be able to answer, on any given day, when every location's next survey and revalidation falls. |
Twelve Places DME Revenue Leaks
Leak | Where It Enters | How to Detect It |
Missing or incomplete documentation | Intake and order collection | Pre-billing documentation audit on a claim sample |
Incorrect HCPCS coding | Charge entry | Code-to-item verification against the delivery record |
Incorrect or unsupported modifiers | Charge entry | Sample review of KX, GA, GY, and GZ usage against documentation |
Eligibility errors | Intake | Denial codes clustered around coverage and eligibility |
Coverage policy mismatch | Referral acceptance | Denials citing policy criteria not met |
Authorization gaps | Scheduling and delivery | Denials on items appearing on a Required PA List |
Invalid or unsigned orders | Order intake | Order completeness check before delivery |
Proof of delivery problems | Delivery and logistics | POD completeness audit by delivery method |
Incorrect units or quantities | Charge entry | Billed quantity compared to delivered quantity |
Untimely filing | Claim submission and rework queues | Aging report for unsubmitted or held claims |
Underpayments | Post-payment | Expected-versus-actual payment variance report |
Poor denial follow-up | AR management | Denials with no work activity past 30 days |
BEST PRACTICE Don't wait for a denial to discover a documentation problem. Every leak above is detectable before submission except underpayment — and that one is detectable within days of remittance if anyone is comparing payment to the expected allowable. | ||
Denial Root-Cause Analysis
Resubmitting a denial fixes one claim. Finding the root cause fixes the next fifty. The sequence:
Denial |
↓
Categorize |
↓
Identify Root Cause |
↓
Correct the Upstream Failure |
↓
Appeal or Resubmit |
↓
Track Result |
↓
Prevent Recurrence |
Denial Category | Likely Root Cause | Where to Fix It |
Insufficient documentation | Medical record doesn't connect the condition to the item | Referral intake — request the record before accepting the order |
No proof of delivery | POD incomplete, or unlinked to shipping records | Delivery workflow and POD form design |
Item not medically necessary | Coverage policy criteria not documented | Pre-delivery coverage verification |
Prior authorization not obtained | Item newly added to a Required List | Quarterly review of current Required Lists |
Invalid order | Missing SWO element, or delivery before a required WOPD | Order completeness gate before delivery |
Timely filing | Claim held in a rework queue with no aging alert | AR workflow with submission-age monitoring |
Supplier not eligible | Lapsed accreditation, enrollment, or bond at a location | Compliance calendar with a single owner |
Paid Is Not the Same as Paid Correctly
Underpayments don't announce themselves. A claim that adjudicates and pays looks successful in every dashboard, which is exactly why contractual variance goes unnoticed for months. The fix is a routine comparison of expected allowable against actual payment — not a review of denials.
Variance Pattern | Possible Cause | Action |
Paid below the fee schedule or contracted rate | Fee schedule update not loaded, or contract terms not configured | Reconcile against the current fee schedule and contract |
Paid for fewer units than billed | Quantity edit, or units not supported by delivery documentation | Compare billed, delivered, and paid quantities |
Rental paid as purchase, or vice versa | Modifier mismatch (NU, RR, UE) | Verify how the item was furnished against the modifier used |
Line item bundled into another | Accessory or supply not separately payable for that item | Check the applicable policy article before billing separately |
Patient responsibility appears too high | Deductible, coinsurance, or secondary payer not applied correctly | Verify secondary coverage and coordination of benefits |
EXPERT INSIGHT A clean claim is not necessarily a correctly reimbursed claim. DME revenue integrity continues after payment, because underpayments and contractual variances stay hidden inside claims that never denied. | ||
Requirements Vary by Product — Substantially
Oxygen equipment, CPAP, power mobility, hospital beds, enteral nutrition, diabetic supplies, orthotics, prosthetics, surgical dressings, and compression garments each sit under their own coverage policy, with their own documentation expectations, their own recurring-need rules, and in some cases their own face-to-face or prior authorization requirements. Oxygen codes moving onto the F2F/WOPD List in April 2026 is a good example: a workflow that was compliant in March needed to change in April, for that product line only.
COMMON MISTAKE Building one universal documentation checklist and applying it across the whole catalog. A checklist is only useful when it's product-specific — the general pillars are shared, but the criteria underneath them are not. |
Four Scenarios
Scenario 1 — Delivered Before the Order Was Complete
What happened: a supplier delivers an item on the Required F2F/WOPD List, then obtains the completed written order two days later.
Why it happened: the workflow treated the order as a billing document to collect before submission rather than a condition to satisfy before delivery.
Revenue risk: the claim can be denied even though the order eventually existed and the item was necessary.
Prevention: an order-completeness gate that blocks delivery scheduling for items on the current Required List.
Scenario 2 — Right Product, Wrong Code
What happened: a supplier furnishes an item with an upgraded feature but bills the base HCPCS code.
Why it happened: the code was carried forward from a prior similar order rather than verified against what was actually delivered.
Revenue risk: underpayment on every affected claim, invisible because nothing denied.
Prevention: code verification against the delivery record at charge entry, not against the product catalog.
Scenario 3 — POD That Doesn't Link
What happened: a shipped item's delivery confirmation exists, but nothing connects the carrier's record to the supplier's invoice.
Why it happened: the delivery form was designed for direct delivery and reused for shipping without the linking element.
Revenue risk: denial as insufficient documentation on audit, potentially across a batch of similar claims.
Prevention: separate POD templates by delivery method, each carrying the elements that method requires.
Scenario 4 — Accreditation Lapse at One Location
What happened: claims from a single location begin denying while other locations pay normally.
Why it happened: that location's accreditation term expired under the new annual cycle and reaccreditation wasn't scheduled.
Revenue risk: every claim from that location during the gap, with reinstatement timing outside the supplier's control.
Prevention: a compliance calendar tracking survey, revalidation, and bond dates per location with one named owner.
A 30-Day DME Revenue Review
Window | Focus | What You're Looking For |
Days 1–7 | Documentation audit | Sample claims by product line; check SWO completeness, medical record support, and POD by delivery method |
Days 8–14 | Denial analysis | Categorize 90 days of denials by root cause, not by denial code text |
Days 15–21 | Coding and payment accuracy | Verify HCPCS and modifier accuracy against delivery records; run expected-versus-actual payment variance |
Days 22–30 | Corrective workflow | Fix the two highest-volume root causes at their origin point and assign owners |
The output that matters isn't the audit findings — it's which upstream step changed as a result. An audit that ends in a report rather than a workflow change tends to produce the same findings next quarter.
Signals Worth Tracking
Signal | What It Measures | What a Change Can Indicate |
Clean claim rate | Share submitted without error requiring rework | A drop often traces to one product line or one intake source |
First-pass resolution rate | Share paid on initial submission | Falls before denial rate rises — an early warning |
Documentation error rate | Share of sampled claims with a documentation gap | The leading indicator behind most insufficient-documentation denials |
POD error rate | Share of PODs missing a required element | Frequently concentrated in one delivery method |
Authorization failure rate | Share of PA-required items delivered without approval | A spike often follows a Required List update |
Days in AR | How long receivables stay outstanding | Rising days with flat denials can mean unworked follow-up |
Underpayment rate | Share paid below expected allowable | Often a fee schedule or contract configuration issue |
Appeal success rate | Share of appeals overturned | A high rate suggests avoidable denials upstream |
Compare these against your own prior periods. Published DME industry benchmarks vary widely in definition and rarely transfer cleanly between suppliers with different product mixes and payer mixes.
Revenue Optimization vs. Improper Billing
These are sometimes discussed as if they sit on a spectrum. They don't. Revenue optimization means collecting everything a supplier is properly owed — correct codes, complete documentation, accurate units, timely submission, and payment verified against contracted rates. Improper billing means submitting claims the documentation doesn't support.
The practical test is simple: would this claim survive a post-payment review by someone reading only the record? If the answer depends on the reviewer not looking closely, it isn't optimization. Upcoding, unbundling, unsupported modifier use, billing undelivered items, and inflated units all carry fraud and abuse exposure well beyond a recoupment.
Internal, Software, Outsourced, or Hybrid
Factor | Internal Team | Software | Outsourced RCM | Hybrid |
Best suited to | Narrow product mix, stable volume | Teams needing workflow structure | Complex product or payer mix | Growth with internal oversight |
Expertise | Depends on who you hire | Encodes rules, not judgment | Specialist depth across payers | Internal ownership, external depth |
Scalability | Limited by headcount | Scales well | Scales with volume | Scales with clear division |
Key risk | Single point of failure | False confidence in automation | Weak handoffs if ownership unclear | Gaps if roles aren't documented |
None is universally better. What consistently fails in all four is unclear ownership of the compliance calendar and the denial root-cause loop.
Where Technology Helps — and Where It Doesn't
Billing Stage | Technology Can Assist With | Requires Human Review |
Documentation | Flagging missing elements and expiring orders | Whether the record actually supports necessity |
Coding | Suggesting codes and catching unit mismatches | Verifying the code matches what was furnished |
Modifiers | Flagging missing or conflicting modifiers | Whether documentation supports the attestation |
Authorization | Tracking status and Required List changes | Interpreting whether a specific item qualifies |
Denials | Categorizing and routing by reason code | Determining the actual root cause |
Payment | Calculating expected-versus-actual variance | Deciding whether to appeal or renegotiate |
How MedCloudMD Supports DME Suppliers
DME billing fails upstream more often than it fails at the claim. Our DME billing team works across that chain — eligibility and coverage verification, documentation and order review, HCPCS and modifier validation, authorization tracking against current Required Lists, claim scrubbing, denial root-cause analysis, AR follow-up, payment posting, underpayment detection, and KPI reporting.
We don't control payer decisions or audit outcomes, and no billing partner can guarantee reimbursement. What a disciplined process does is stop avoidable denials — incomplete orders, unlinked PODs, stale codes, missed authorizations, and payments nobody checked.
Pre-Submission Checklist
☐ Standard Written Order complete with all required elements and signed
☐ Written order on file before delivery, for items requiring it
☐ Face-to-face encounter documented in the medical record, where applicable
☐ Medical record connects the clinical condition to the specific item
☐ Continued need and continued use documented, where applicable
☐ Current Required Lists checked for this HCPCS code
☐ Prior authorization obtained and on file, where required
☐ HCPCS code verified against the item actually delivered
☐ Units billed match units delivered
☐ Modifier usage supported by documentation
☐ Proof of delivery complete for the delivery method used
☐ Date of service consistent with the delivery method's rules
☐ Payer-specific coverage requirements confirmed
Requirements vary by item, payer, coverage policy, and applicable Medicare rules. Use this as a starting framework and build product-specific versions underneath it.
Frequently Asked Questions
What is DME billing?
DME billing is the process of submitting and collecting payment for durable medical equipment, prosthetics, orthotics, and supplies — covering order documentation, coverage verification, HCPCS coding, delivery documentation, claim submission, and denial management.
How does DME billing work?
An order and supporting documentation are collected, coverage and eligibility verified, the item coded and — where required — authorized, then delivered with proof of delivery captured before the claim is submitted and adjudicated.
What documentation is required for DME billing?
CMS identifies four requirements to justify payment: a Standard Written Order, medical record information (including continued need and use where applicable), correct coding, and proof of delivery. Specific requirements vary by item and payer.
What is a Standard Written Order for DME?
The single order format required for DMEPOS claims, containing the patient's name or MBI, the order date, a general description of the item, the quantity if applicable, and the treating practitioner's name or NPI and signature.
What is Proof of Delivery in DME billing?
Documentation confirming the beneficiary received the item. It must include the beneficiary's name, delivery address, quantity, date delivered, and item description, with additional requirements depending on whether the item was delivered directly, shipped, or sent to a nursing facility.
How long must DME suppliers keep proof of delivery?
Seven years from the date of service, available to the DME MAC on request.
What causes DME claim denials?
Most commonly: documentation that doesn't support necessity, missing or incomplete proof of delivery, invalid or late orders, coding and modifier errors, missed prior authorization, timely filing lapses, and supplier eligibility problems.
Does Medicare require prior authorization for DME?
For items on the Required Prior Authorization List, yes. That list is updated by Federal Register notice — most recently effective April 13, 2026, with further additions carrying dates of service on or after October 28, 2026 — so it should be checked rather than assumed.
What is DMEPOS accreditation, and what changed in 2026?
Accreditation is independent verification that a supplier meets DMEPOS quality standards. Effective January 1, 2026, CMS moved suppliers from a 36-month accreditation cycle to at least every 12 months, and removed the allowance for new locations to operate under temporary accreditation without a survey.
What's the difference between the Master List and the Required Lists?
The Master List is a library of items CMS has flagged as potential program vulnerabilities — inclusion carries no requirement by itself. Only items named on the Required F2F/WOPD List or Required Prior Authorization List carry conditions of payment.
How can DME suppliers reduce claim denials?
By moving controls upstream: verify coverage before accepting the referral, gate delivery on order completeness for items that require it, design proof-of-delivery forms by delivery method, and check current Required Lists quarterly.
Should a DME supplier outsource medical billing?
It depends on product and payer complexity, volume, and whether someone internally owns the compliance calendar and denial root-cause loop. Internal, software-supported, outsourced, and hybrid models all work — what fails in each is unclear ownership.
Sources & References
Disclaimer
This resource is provided for general educational purposes for DMEPOS suppliers, healthcare organizations, and revenue cycle professionals. It is not legal, regulatory, coding, or compliance advice for any specific claim, item, supplier, or payer contract, and it does not replace the official HCPCS code set, CMS regulations and manuals, DME MAC local coverage determinations and policy articles, or a specific payer's medical and reimbursement policies. DMEPOS documentation, coding, coverage, enrollment, accreditation, and prior authorization requirements vary by item, payer, state, and date of service, and they change — including the 2026 changes described here. Verify current requirements with CMS, the applicable DME MAC, and the relevant payer before submitting claims. MedCloudMD does not guarantee reimbursement, claim approval, audit outcomes, or accreditation results. For guidance on a specific compliance or billing question, consult a qualified coder, compliance officer, or healthcare attorney.
Last Reviewed: September 2026 — Reviewed by MedCloudMD Revenue Cycle Experts. Regulatory details referenced here were current as of that review and should be re-verified against current CMS and payer guidance over time.
Comments