How can an ABA practice enroll with Nevada Medicaid and submit prior authorization? Map each entity and clinician to provider type 85 and the correct specialty, complete Nevada Medicaid enrollment and any managed-care participation, verify the current Chapter 3700 and billing guide, then authorize and bill only when the member, provider, setting, dates, units, and claim configuration match.

Map the operative program route first

Nevada's Chapter 3700 page identifies the current Applied Behavior Analysis manual, effective April 1, 2024 when checked. The provider type 85 checklist separates entity or agency specialty 885, BCBA specialty 310, psychologist specialty 311, BCaBA specialty 312, and RBT specialty 314. Those mappings belong in the practice's configuration table rather than a free-text credential note.

The provider portal publishes current enrollment, prior-authorization, fee-schedule, billing, revalidation, and denial resources. Its August 2026 notice warns that a provider whose revalidation is not processed by the termination date becomes ineligible for services to fee-for-service and MCO members. The ABA FAQ routes detailed limits back to Chapter 3700 and the current PT 85 billing guide.

Separate every readiness gate

For Nevada, create a row for each organization, professional, specialty, service location, and payer route. The row should show license or certification, PT 85 specialty, state-enrollment status, revalidation date, managed-care contract and roster when applicable, authorization pathway, place of service, billing-guide version, and tested claim identity. A group enrollment does not fill an individual's specialty field, and a professional enrollment does not establish the group's network effective date.

Use four release states: verified, pending, held, and expired. Each state should carry the evidence source, scope, owner, effective date, last check, and next action for the Nevada configuration. Software may surface a missing field or contradiction. Authorized people still make enrollment, contracting, clinical, authorization, and billing decisions within their roles.

Build a source-backed enrollment file

Build the application packet from the specialty checklist that applies to each role. Preserve every upload, signed attestation, license, certification, ownership disclosure, site record, NPI, taxonomy, EFT record, submission confirmation, request for information, approval, and effective date. Calendar revalidation from the state's notice and keep the service stop date visible if completion remains unresolved.

42 CFR 455.410 requires state Medicaid agencies to screen enrolled providers and enroll covered ordering or referring professionals. For managed care, 42 CFR 438.602(b) requires the state to enroll, screen, and periodically revalidate network providers. A plan may use one pending-agreement period of up to 120 days, but that allowance does not create a billing effective date or payment guarantee for a Nevada practice. CMS's NPI fact sheet supplies another useful boundary: an NPI identifies an individual or organization and does not establish licensure, credentialing, health-plan enrollment, or payment.

Use a build-ready configuration record

Give every Nevada configuration a durable identifier and keep one row per billing entity, rendering professional or role, service location, payer or program, product, and service. The row should include the legal name, NPI, tax identifier when needed, taxonomy, license or certification, state enrollment number and effective date, revalidation date, contract status, credentialing decision, roster date, directory result, authorization route, claim route, and named owner. Store evidence links and source versions beside the fields they support. A free-text note cannot reliably drive release decisions or show which approval changed.

Create three practical views from the same Nevada record. The launch view shows incomplete enrollment, contract, roster, portal, and claim-test work. The client release view joins member eligibility, payer assignment, provider and location, clinical decision, authorization number, dates, units, and scheduled service. The reconciliation view joins the original claim, acknowledgments, adjudication, remittance, deposit, corrections, and refund or recoupment work. Use role-limited access for sensitive data and preserve who changed a field, when, why, and from which source. When evidence conflicts, hold only the affected configuration, keep both records, and obtain written clarification from the responsible state or payer source.

Configure authorization by member and route

First identify fee-for-service or the member's managed-care plan. Then map the request to Chapter 3700, the PT 85 billing guide, the exact specialty, place of service, assessment or treatment phase, dates, and units. Nevada's portal cautions that an authorization-criteria search returning no records can still miss a requirement after limits are exceeded. Use the governing manual and guide, preserve the request number, and read the written response before scheduling beyond the approved scope.

Release claims from verified evidence

A Nevada release check should compare the member and route, billing PT 85 identity, rendering specialty, service location, authorization, service date, actual time, code and modifier, units, supervision record, and documentation. Keep revalidation status in the same preflight because a pending or terminated enrollment can affect both fee-for-service and MCO work. Reconcile the 277CA or proprietary claim acknowledgment, adjudication result, remittance, and payment as separate evidence. A clean portal submission still can fail later edits.

A fictional readiness review

A fictional Reno practice inventories 18 provider-specialty-location rows. Thirteen are ready. Two RBT specialties remain unapproved, one group location lacks a plan roster date, one BCBA revalidation is near termination without a decision, and one fee-for-service configuration has never passed a claim test. Readiness is 13 of 18, or 72.2%. The practice pauses new assignments on the at-risk BCBA row while escalating the revalidation rather than assuming the submitted application preserves eligibility.

The Nevada example's denominator is locked before review. A submitted application, portal login, directory listing, or successful test at another site does not remove a held row. The release owner records the responsible party, next action, due date, and evidence required to move that exact configuration.

Measure the workflow after launch

Check the Nevada portal at least monthly and before any release involving a new provider, revalidated provider, new location, new plan, or revised Chapter 3700. Report PT 85 rows approved over rows due, revalidations completed before termination over revalidations due, authorization decisions received by target over complete requests, and mature first transmissions reaching adjudication over mature first transmissions. Keep portal incidents and planned maintenance in an operations log so technical delays are distinguished from payer decisions.

Go/no-go checks before the first covered service

  • Every clinician and entity has the correct PT 85 specialty and current effective date.
  • Revalidation is complete before the state's termination point.
  • The member's fee-for-service or managed-care route controls the submission channel.
  • Chapter 3700, the PT 85 guide, and the authorization all support the scheduled setting and units.
  • Claim identity, acknowledgment, adjudication, remittance, and payment are reconciled separately.

A go decision in Nevada applies only to the named configuration and service period. If a required approval, credential, roster, authorization, source, or claim control expires, pause new covered-service promises on that row and route existing clients through qualified clinical, payer, and continuity review.

Related resources

Sources