AI-Driven Automation Tools
Resupply, Rental, and POS Workflows
Delivery Management and Mobile App
For DMEPOS suppliers, a prior authorization requirement should never be discovered after equipment is already on the delivery schedule.
Yet that is exactly what can happen when coverage rules, documentation requirements, and order status live in separate places. A referral looks ready. Inventory is available. A delivery is planned. Then someone realizes the item requires prior authorization, or that a required document is still missing.
At that point the order is not simply delayed. The team is managing a preventable exception across intake, clinical documentation, authorization, scheduling, delivery, and billing.
Medicare’s expansion of the Required Prior Authorization List, effective October 28, 2026, is a timely reminder that prior authorization is not only a reimbursement process. It is a pre-delivery workflow.
CMS added six DMEPOS HCPCS codes to the Required Prior Authorization List nationwide:
CMS is also phasing in required prior authorization for two upper-limb orthoses:
The rollout for these two codes runs in three phases:
With this update, the Required Prior Authorization List contains 82 items, and the Required Face-to-Face Encounter and Written Order Prior to Delivery (WOPD) List contains 105 items.
The two lists are not interchangeable, but they create the same operational reality: teams need to identify requirements before an order reaches fulfillment.
Prior authorization is often treated as a back-office responsibility. That framing is incomplete.
The authorization decision depends on information that begins at referral intake, moves through documentation collection, and determines whether an item can be delivered. When a requirement is identified too late, every downstream team inherits the problem.
A missed requirement can lead to:
The core issue is not that requirements exist. It is whether the workflow recognizes them early enough for the team to act.
A reliable process begins when the order enters the system.
At intake, the workflow should surface the conditions that matter: the HCPCS code, payer, patient location, item category, and any supplier-specific status that affects the order. That does not replace experienced review. It ensures reviewers start from a visible, consistent baseline.
For orders that require prior authorization, the team should be able to see:
This is the difference between a checklist in a shared folder and an active workflow. A checklist tells people what should happen. A workflow shows what has happened, what is blocked, and who needs to act next.
Intake accuracy matters here too. If the ordering provider or item details are captured incorrectly, every rule that depends on them is checked against the wrong data. (We covered one example in verifying the ordering provider NPI earlier in DME intake.)
The delivery team should not have to interpret payer requirements on the day of delivery.
Instead, the order should move through a clear release process. Before fulfillment is confirmed, the required prerequisites should be complete, visible, and tied to the specific item being delivered. That may include confirmation of:
The goal is not to add unnecessary gates. It is to put the right gate in the right place.
If an order is missing something, it should enter a defined exception state rather than move forward on assumption. A visible hold is easier to resolve than a hidden risk discovered after the fact.
Every operation encounters incomplete documentation, pending decisions, expiring authorizations, and unexpected payer questions. What separates a resilient process from a fragile one is how those exceptions are managed.
A useful exception workflow answers five questions immediately:
When those answers live only in inboxes or free-text notes, the order depends on whoever touched it last. When they are part of a shared workflow, any qualified team member can understand the situation and continue the work.
October also brought a separate CMS requirement for certain newly enrolled DMEPOS suppliers and suppliers undergoing certain changes of ownership.
Starting October 15, 2026, suppliers with an enrollment date or qualifying ownership change on or after that date must obtain prior authorization before delivering items on the Probationary Prior Authorization List during a one-year probationary period.
This process does not replace the existing DMEPOS prior authorization program. Suppliers subject to probationary prior authorization must still meet the established requirements for items on the Required Prior Authorization List.
For operations leaders, the lesson is clear: prior authorization cannot be managed as a single static list. The requirements that apply can depend on the item, the payer, the state, the supplier’s enrollment circumstances, and the date of service.
Medicare requirements will keep evolving. The practical response is not a one-time scramble every time a list changes. It is a workflow that can absorb changes.
Review whether your team can:
The best compliance workflow is not the one that generates the most alerts. It is the one that gives the right person the right signal early enough to protect both the patient experience and the payment.
In Curasev, prior authorization is part of the order, not a separate spreadsheet. Fee schedule rules open an authorization request when a product that needs one is added to an order. Each request carries its diagnosis codes, ordering physician, payer, and products, and assigned follow-up tasks with due dates give every open request an owner and a next step. Authorization status and expiration dates are visible on each order line, and approved authorization numbers are applied to claims automatically.
Learn more about DME prior authorization software in Curasev and how AI-driven sales order orchestration keeps orders moving from intake to delivery.
DMEPOS operations work best when clinical, administrative, and fulfillment steps move as one connected process.
Medicare’s October 28 prior authorization expansion raises the stakes for getting that process right. Suppliers that treat authorization as a pre-delivery control, not a late-stage billing task, will be better prepared to absorb changing requirements without creating avoidable work for their teams or delays for their patients.
For a broader view of the prior authorization burden on DME providers, read Prior Authorization Reform Is Overdue.
This article is for general operational education and is not legal or billing advice. Suppliers should review the current CMS lists and guidance from their DME Medicare Administrative Contractor (MAC) for the requirements that apply to their specific orders.
Sources: CMS Master List of DMEPOS Items Potentially Subject to Conditions of Payment (Required Prior Authorization List and Required Face-to-Face Encounter and WOPD List); Federal Register notice, July 30, 2026; CGS Medicare, Prior Authorization for DMEPOS; CMS Probationary Prior Authorization Process.
Stop forcing your team to work around outdated software. Our end-to-end platform is built to mirror your specific HME workflow—from the first referral intake to the final collection.
.png){kind=icon}
