How can an ABA practice enroll with Arizona AHCCCS and submit ABA prior authorization? Use APEP to choose the correct provider and screening category, complete entity and professional enrollment, and establish each contracted-plan relationship. Verify the member's plan or fee-for-service route before submitting authorization. Use current policy and coding resources for production, while proposed Policy 320-S changes remain in a future-state register until AHCCCS adopts them.

Start with the controlling delivery route

AHCCCS's APEP resources page links the provider-enrollment policy manual, screening glossary, and training. The screening glossary connects provider type and service to enrollment type, NPI, fee, site-visit, fingerprint, and risk-category requirements. A practice should select the enrollment type from current facts rather than copying a peer's category.

The ASD and ABA page links current member resources alongside 2026 proposed Policy 320-S materials. The proposal labels matter. Current plan or fee-for-service requirements control production. AHCCCS's FFS PA page says the online portal is preferred, PA is provisional evidence rather than a payment guarantee, and some behavioral-health requests belong to another entity. The coding resources page supplies dated edits and guides.

Keep enrollment and service gates separate

Maintain Arizona rows by entity, professional or technician role, site, AHCCCS plan or FFS program, service, and setting. Track APEP enrollment type, screening, NPI, license or credential, contract, roster, member assignment, authorization receiver, coding-source version, claim profile, and revalidation. Mark Policy 320-S proposal elements as future, proposed, or adopted with an effective date.

Use verified, pending, held, and expired as the four Arizona workflow states. Each state should identify the decision owner, authoritative source, scope, effective period, last check, evidence, and next action. Automated checks can detect missing or conflicting values. Enrollment staff, plans, qualified clinicians, billing specialists, and legal or compliance owners make the decisions assigned to their roles.

Build the provider enrollment file

Build the APEP record from the current screening glossary. Preserve ownership, tax identity, NPI and taxonomy, provider type, risk category, fees when applicable, fingerprint or site-visit evidence when required, licenses, locations, group relationships, approval, and effective date. Add every contracted health-plan agreement, credentialing decision, roster, product, location, rate, and effective date. Test eligibility, authorization, claim, and remittance access by route.

42 CFR 455.410 requires state Medicaid agencies to screen enrolled providers and enroll covered ordering or referring professionals. 42 CFR 438.602(b) assigns state enrollment, screening, and periodic revalidation duties for managed-care network providers. Its one limited pending-network-agreement period can last up to 120 days, though it supplies no billing effective date or payment promise for an Arizona provider. The CMS NPI fact sheet explains that an NPI identifies an individual or organization; licensing, credentialing, enrollment, contracting, roster status, authorization, and payment each need separate proof.

Make the configuration record usable

Give each Arizona row a durable identifier. Use one row for every relevant combination of billing entity, rendering role, location, payer or program, product, service, setting, and submission route. Fields should cover legal name, NPI, tax identifier where needed, taxonomy, license or certification, state provider number, screening, revalidation, contract, credentialing, roster, directory, portal role, authorization receiver, claim receiver, effective dates, source version, and responsible owner. Attach the document or transaction supporting every release-critical field.

Build three operational views from the same Arizona record. The launch view shows incomplete provider, plan, access, and claim-test work. The client release view joins member eligibility, delivery route, provider and location, qualified clinical decision, authorization, schedule, and units. The reconciliation view links the original claim, acknowledgments, adjudication, remittance, deposit, correction, refund, and recoupment. Restrict sensitive data by role, preserve change history, and hold only the affected configuration when evidence conflicts.

Configure authorization for the member

Verify member eligibility and the responsible contracted plan, RBHA, tribal route, or fee-for-service entity. Use that receiver's current policy, form, and portal. Capture the qualified assessment, diagnosis and referral evidence, treatment plan, provider and setting, requested dates and units, supervision, and continued-stay information. Retain receipt, questions, decision, approved scope, and renewal. Proposed documentation thresholds stay outside the live checklist.

Release claims from the service record

Arizona release logic should compare APEP and plan status, member assignment, authorization, billing and rendering identities, location, actual service and time, code and modifier, units, supervision, documentation, and dated coding resources. Separate a portal authorization number from coverage, clean-claim status, adjudication, and payment. Reconcile every response and preserve the original claim through corrections or voids.

A fictional launch review

A fictional Mesa practice reviews 19 APEP-plan-site rows. Thirteen are ready. One provider type uses the wrong screening category, two plan rosters are pending, one FFS request went to the wrong behavioral-health receiver, one configuration applies proposed 320-S terms, and one code edit is undated. Readiness is 13 of 19, or 68.4%.

The Arizona example fixes its denominator before review begins. A submitted application, user account, directory listing, unrelated approval, or successful claim at another site leaves the held row in the denominator. The owner records the exception, responsible person, due date, next action, and evidence required for release.

Monitor the live workflow

Review APEP policy and training, ASD and Policy 320-S status, FFS PA, coding resources, and contracted-plan sources monthly. Measure enrollment decisions over applications due, screening tasks complete over tasks due, plan rosters effective over plan rows due, authorization packets accepted over submissions, and mature first claims adjudicated without resubmission over mature first claims.

Build an Arizona receiver map for each plan, RBHA, tribal program, and fee-for-service population the practice accepts. Record the provider contract, member group, authorization channel, urgent route, claim receiver, remittance source, and support contact. Test the map with fictional data and preserve the response. When eligibility shows a route outside the map, hold scheduling until an authorized staff member verifies participation and obtains the current submission instructions.

Keep a dated Arizona change register. For each new notice, manual, fee file, form, contract, or portal instruction, record whether it is current, future, proposed, superseded, or archived; identify affected configurations; test the change on approved fictional data; and document who approved production use. This keeps source maintenance observable instead of relying on staff memory.

Go/no-go review before covered service

  • APEP enrollment type and screening category match the provider and service.
  • Member plan, tribal, RBHA, or FFS route is verified.
  • The authorization receiver and packet match the exact route.
  • Proposed Policy 320-S provisions remain outside production.
  • Coding and claim controls carry a current effective date.

A go result applies only to the named Arizona configuration and service period. When a license, enrollment, contract, roster, authorization, source, or claim control expires, pause new covered-service commitments for that row. Route current clients through qualified clinical, payer, access, and continuity review under the applicable rules.

Related resources

Sources