Guides / PA request

PA request Prior authorization request (PAR) — items on the Required Prior Authorization List

Preparing and submitting a DMEPOS prior authorization request

Citations verified against the CMS Medicare Coverage Database · Reviewed September 2026

For items on CMS's Required Prior Authorization List — power mobility devices, certain orthoses, lower limb prosthetics, pressure reducing support surfaces, and pneumatic compression devices — submitting a prior authorization request (PAR) before delivery is a condition of payment. The DME MAC reviews the order and clinical records and returns a provisional affirmation or non-affirmation with a unique tracking number (UTN) that must appear on the claim.

This guide walks through what the request has to contain, the four submission channels and which ones the MACs recommend, the organization habits that avoid rejections, the decision timeframes, and how to carry the UTN onto the claim.

How this gets reviewed: The MAC reviews only what you send. CMS's operational guide lists the identifiers it wants on every PAR to avoid processing delays, and both Noridian and CGS say a properly completed coversheet and a thorough intake process prevent most rejections. Requests missing an identifier or sent to the wrong jurisdiction are returned or delayed before anyone looks at the clinical record.

The requirements, with citations

The elements below are drawn from the cited CMS and DME MAC sources, not from AffirmDME's rules engine.

Required

Beneficiary, supplier, requestor, and practitioner identifiers

CMS asks for the beneficiary's name, Medicare number (MBI), date of birth, address, place of service, and diagnosis code; the supplier's name, NPI, PTAN, address, and phone; the requestor's contact details; and the HCPCS code(s). The coversheet also marks whether the request is initial, a resubmission, or expedited (with the reason), whether it includes an upgrade, and whether a beneficiary decision letter is requested. CGS's coversheet adds the treating practitioner's name and NPI.

CMS DMEPOS PA Operational Guide §4.1; CGS PA coversheet
Required

The order, the encounter, and the item-specific records

Beyond identifiers, the request needs documentation from the medical record supporting medical necessity: the Standard Written Order, the face-to-face encounter note dated within six months before the order, and whatever the item's policy requires — for power mobility devices, Noridian lists the mobility evaluation, the specialty evaluation, and documentation of the RESNA-certified ATP's in-person involvement.

CMS DMEPOS PA Operational Guide §4.1; Noridian PMD page
Required

Four submission channels: portal, esMD, fax, or mail

PARs can be sent by mail, fax, electronic submission of medical documentation (esMD, content type 8.4), or the MAC's portal — the Noridian Medicare Portal for Jurisdictions A and D, myCGS for B and C. Portal submissions need no coversheet; CGS calls its myCGS Prior Authorization Smart Submission the fastest route, and CMS encourages fax, esMD, or the portal for expedited requests to avoid mailing delays. Route by the beneficiary's permanent address.

CMS DMEPOS PA Operational Guide §4.1.1; CGS PMD prior authorization
Required

Organization habits the MACs publish

Noridian's guidance: complete every field on the coversheet or portal form, send one request per fax transmission, do not submit duplicates to the same jurisdiction, and send legible copies. For ADR responses the same MAC asks for the letter on top of the packet, each claim faxed separately, and full one-sided sheets — habits worth applying to PARs too.

Noridian — Prior Authorization for PMDs; How to Respond to ADR
Required

Decision within five business days, seven calendar days at most

The MAC issues a decision within five business days (not to exceed seven calendar days) of receiving complete documentation, and resubmissions follow the same timeframe; expedited requests target two business days. Decision letters are sent by fax, mail, esMD, or portal to the supplier address on file with National Provider Enrollment, not the address written on the request.

CMS DMEPOS PA Operational Guide §5, §15
Required

The UTN goes on the claim — every claim in a series

The 14-byte UTN from the decision letter goes in the first 14 positions of Item 23 on the CMS-1500, or in the 2300 (or 2400) loop REF segment with qualifier G1 on electronic claims, and on each claim in a rental series. A claim for a required-PA item submitted without a UTN is automatically denied, typically with reason code 197 and remark N210. Affirmations are valid for a period that varies by program — from about a month for support surfaces to six months for mobility devices — so deliver inside the window.

CMS DMEPOS PA Operational Guide §18; Noridian reason code 197 / N210

What usually sinks these claims

Build the packet from the checklist, not from memory

Upload what you have and AffirmDME reads it, shows the per-item readiness checklist with citations, and tells you what is still missing before the request goes to Noridian or CGS. Free in sandbox mode.

Try a sample case

FAQ

How long does a DMEPOS prior authorization decision take?

Five business days, not to exceed seven calendar days, from the MAC's receipt of complete documentation — for initial requests and resubmissions alike under the current operational guide. Expedited requests, justified by a documented risk to life or health, target two business days.

Which items need a prior authorization request?

Only items on CMS's Required Prior Authorization List, which CMS publishes on its DMEPOS prior authorization page and in the Federal Register. Everything else is reviewed after submission through prepayment review, ADRs, or post-payment audits against the same documentation rules.

Can I submit through the portal instead of faxing?

Yes. The Noridian Medicare Portal (Jurisdictions A and D) and myCGS (Jurisdictions B and C) both accept PARs, need no coversheet, and let you check request status and view decision letters. esMD is the other electronic option.

How does AffirmDME help assemble the packet?

AffirmDME's document extraction reads the order, chart notes, and evaluations you upload, builds a per-item readiness checklist with citations, and flags what is missing before you submit. Prescriber outreach by fax and SWO e-signature through DocuSign cover the pieces that have to come from the practitioner's office. You can try the whole flow on a sample case in the free sandbox.

Get an email when the Required PA List changes.

CMS adds codes, the DME MACs revise LCDs, cycle deadlines arrive. We send a short note the week it happens, with what to do about it. No drip campaign. Unsubscribe in one click.

This guide summarizes Medicare requirements as implemented in AffirmDME's compliance engine, with citations to the governing sources. It is not legal or billing advice; LCDs and CMS policy change — always confirm against the current policy text linked above.

Also drawn on: Noridian — claim review preparation .

More guides

Unfamiliar term? The glossary defines ADR, SWO, UTN, PTAN and the rest; the PA List lookup checks any HCPCS code.