What Is ROPA And Why Is It Denying Your Medicaid Claims?

ROPA is a provider enrollment rule that turns into a health plan data problem. The field that caused the denial is not in the directory.

Federal rule requires the ordering or referring professional on a Medicaid claim to be enrolled with the state, even when that person never bills. States pulled prescribing and attending into the same net. Florida and Arizona call the category ROPA. New York calls it OPRA.

Denials are running now. Florida has rejected fee-for-service claims naming an unenrolled ROPA provider since October 1, 2021. Arizona started with referring, ordering, and attending in August 2025. As of September 1, 2026, an unregistered prescriber on an Arizona fee-for-service claim denies as well.

Those NPIs arrive in the same enrollment feeds that update the plan’s provider record. They are not contracted renderers. Mix the two and the plan overstates the network it submits and still takes a denial on a field the directory doesn’t show.

Two Rules. One Feed.

Anyone who orders or refers Medicaid services has to enroll with the state; the floor is 42 CFR 455.410(b). A National Provider Identifier (NPI) in NPPES is not enough.

Florida made it operational on October 1, 2021. An AHCA alert (January, 2021) had laid out the rule: if the referring, ordering, prescribing, or attending NPI on a fee-for-service claim is not enrolled with Florida Medicaid, the claim denies.

Arizona did the same work in two steps. Referring, ordering, and attending denials on fee-for-service claims started August 1, 2025. Then, effective September 1, 2026, prescribers joined the net. Claims Clues, the AHCCCS bulletin read by fee-for-service providers and by health plans, confirmed that date in June and August.

Managed care comes through a second door. Under 42 CFR 438.602(b), the state has to screen, enroll, and revalidate the plan’s network providers. The “Network provider” definition at 42 CFR 438.2, already includes people who order or refer, not only people who treat members. So, the file the state sends the plan is doing two jobs at once: who is contracted to render, and who is allowed to appear in a referring, ordering, prescribing, or attending field.

A ROPA enrollment is partial by design. The professional can sit on the claim. They cannot bill as the renderer unless they fully enroll. Florida is explicit that an enrollment type of “Registered” does not satisfy 455.410(b). Arizona built a short application for the rest: providers who already hold an NPI, are enrolled in Medicare or another state’s Medicaid program, and do not intend to bill AHCCCS at all.

Why the Plan Feels it as a Data Problem

The contracted roster is built for adequacy, the directory, and payment. ROPA names sit one layer out. They show up on claims and encounters, often on the same state master list as the contracted network. Florida tells plans those rows will appear on the Provider Master List and will not count toward adequacy.

Mix the two populations and the file starts to describe two networks. That is the same break our provider data post tracks between the list sent to the state and the directory a member uses.

The denial is easy to misread as claims hygiene or a provider-relations miss. Both are looking at a record that never tagged the NPI as enrollment-only, stored the enrollment type, or kept the as-of date.

“Identity resolution will match the name. It will not tell you whether that name was legal on the claim that day.”

— Bret Randolph, COO, CureIS Healthcare

The File Has to Hold a Three-Way Split

For any NPI, as of a date, a Medicaid plan needs three facts that are easy to collapse and expensive to untangle later.

Those are three attributes of one identifier. Call all of them “on the state file” and the plan will count a referring pediatrician as capacity, or pay a claim that names an attending professional who was never enrolled. Neither miss shows up when someone shops the directory.

Arizona: Registered, Excepted, or Neither.

Where to Start

Take a recent 90-day claims or encounter population. Pull the referring, ordering, prescribing, and attending NPIs. Match them to the latest state enrollment extract and to the contracted roster. Count three piles: contracted and enrolled, enrolled only, and on the claim with no qualifying enrollment.

The third pile is the denial queue. In Arizona you can find it faster by edit: H313.1 and H313.3 for the attending provider ID, L232.4 for an invalid referring or ordering provider. Some of that is recoverable. A provider can request a retroactive enrollment date, attach the denied claim, and resubmit, subject to timely-filing rules.

The second pile is the adequacy risk: names that look like network because they arrived in the same feed. Decide which source wins for enrollment type and keep the date. That’s the same conformance work as described here. ROPA is not a fifth system the plan uses. It is a reason the state enrollment feed is load-bearing.

The Takeaway

ROPA is not an acronym problem, and it’s not a Florida-only edit. Arizona’s September 1 expansion is simply the latest state move to stop warning and start denying. These NPIs belong in the provider record. They do not belong in the network count. If the file cannot say which is which, on which date, the plan will overstate the network the state attests from and still lose the claim.

Clean matching doesn’t fix that. A tagged, dated enrollment status does.

About CureIS

CureIS has spent the past 20 years helping managed care organizations spend less to do more. 

CureIS UniSync is a powerful conformance-and-reconciliation platform that operates alongside your existing systems, creating the trusted data foundation needed for audit response, network adequacy reporting, encounter improvement, eligibility reconciliation, and claims operations. It provides a point-in-time provider view with lineage across credentialing, contracting, prior authorization, claims, directories, encounters, and delegated feeds.

Discover what needs to be fixed before a reviewer does. Request our free Defensibility Assessment on one high-risk population. 

Frequently Asked Questions

What does ROPA stand for in Medicaid?
Referring, ordering, prescribing, and attending. It’s the class of professional that must be enrolled with the state Medicaid program even when they never submit a bill. Arizona and Florida use ROPA. New York uses OPRA. Several other states use ORP or OPR, which generally covers ordering, referring, and prescribing without attending.

When did Arizona start denying claims for unregistered ROPA providers?
In two steps. Referring, ordering, and attending denials on fee-for-service claims began August 1, 2025. Prescribers were added effective September 1, 2026, per AHCCCS Claims Clues (June and August 2026).

Why did my Medicaid claim deny for an unregistered referring provider?
Because the professional named in the referring, ordering, prescribing, or attending field is not enrolled with that state Medicaid program. The denial lands on the billing provider, not on the professional who failed to enroll. In Arizona the fee-for-service edits are H313.1 and H313.3 for the attending provider ID and L232.4 for an invalid referring or ordering provider.

Can a provider enroll retroactively after a claim has already denied?
In Arizona, yes. The provider requests a retroactive enrollment date during the application and uploads a letter stating the date needed, with a copy of the denied claim. Once approved, the claim is resubmitted. Timeliness rules still apply.

Do ROPA providers count toward network adequacy?
No. Florida states directly that ROPA rows appear on the Provider Master List and do not count toward adequacy. They are enrolled with the state, not contracted to render for the plan.

Does the ROPA requirement apply to Medicaid managed care or only fee-for-service?
The current claim edits in Florida and Arizona are fee-for-service. Managed care arrives separately: 42 CFR 438.602(b) makes the state responsible for screening, enrolling, and revalidating the plan’s network providers, and 42 CFR 438.2 defines a network provider to include those who order or refer, not only those who render.

What if the referring provider is a resident, intern, or pharmacist?
In Arizona those are not registerable provider types. They are handled through an exception process and appear on a separately published excepted-provider list.

How often does a ROPA enrollment have to be renewed?
Every four years in Arizona, the same revalidation cycle that applies to all AHCCCS providers. A registration current today will not stay current on its own.

How do we tell a contracted provider from an enrollment-only NPI in our own data?
You need a per-NPI, per-date attribute that records enrollment type, contract status, exclusion status, and source, with the lineage behind each. Most plans have those facts spread across credentialing, contracting, and state enrollment feeds with no governed way to reconcile them.

Sources & References

42 CFR 455.410(b). Enrollment of ordering or referring providers with the state Medicaid agency.

42 CFR 455.440. National Provider Identifier required on claims for items and services that were ordered or referred.

42 CFR 438.2. Definition of network provider, covering those who order, refer, or render covered services under the plan’s contract.

42 CFR 438.602(b) and (d). State screening, enrollment, and revalidation of MCO, PIHP, and PAHP network providers, and state checks against federal exclusion databases.

AHCCCS. Claims Clues, Division of Fee-for-Service Management, June 2026 and August 2026 repeat. Effective September 1, 2026, fee-for-service claims that include a referring, ordering, attending, or prescribing provider not registered with AHCCCS will be denied.

AHCCCS. Referring, Ordering, Prescribing, Attending (ROPA) Providers Required to Register with AHCCCS, provider page and FAQs Q1–Q18. Confirms fee-for-service denials; does not carry the September 1, 2026 date. Source for streamlined registration, the two published listings, excepted types, edits H313.1, H313.3 and L232.4, retroactive enrollment, four-year revalidation, and Q14–Q15.

AHCCCS tribal consultation presentations, May 2026 and August 4, 2026. ROA denials effective August 1, 2025; ROPA including prescribers effective September 1, 2026.

AHCCCS. Active, Registered Providers by NPI who may Refer, Order, Prescribe, or Attend, and ROPA Excepted Providers List (Residents, Interns, Pharmacists).

Florida AHCA Health Care Alert, January 6, 2021. Effective October 1, 2021, fee-for-service claims deny if the ROPA NPI is not enrolled. Confirmed on the Florida Medicaid ROPA portal and professional-claims QRG, including that “Registered” does not satisfy 455.410(b) and that ROPA rows appear on the Provider Master List without counting toward adequacy.

MACPAC. Provider Enrollment and Credentialing in Medicaid, Chapter 7, June 2026 Report to Congress. (Administrative burden most acute for small practices and for providers required to enroll across multiple states and managed care plans.) Used for framing only.

State terminology (naming and framing only, not dates): New York eMedNY OPRA; South Carolina ORP; Texas TMHP Provider Procedures Manual Vol. 1, March 2026; Missouri OPR; North Carolina OPR.