How can an ABA practice enroll with the Oregon Health Plan and submit prior authorization? Enroll every provider role and location required by OHP, establish each coordinated care organization relationship or fee-for-service route, verify member assignment, and follow the current behavioral-health and authorization guidance. Schedule and bill only when requesting, referring, performing, location, authorization, service, and claim records match.

Map the operative program route first

The Oregon Health Authority's behavioral-health policy page is the source index for OHP rules and guidance, including the ABA program material. The prior-authorization page says requesting, performing, and referring providers must all be enrolled OHP providers for requests sent to OHA. It also directs CCO-covered services to the CCO and fee-for-service services to OHA's handbook and portal route.

Use the state's eligibility-verification page to identify the member's benefit and delivery arrangement, then use the CCO page to confirm the current organization and contact route. Enrollment with OHP, CCO contracting, member assignment, authorization, and payment remain separate states.

Separate every readiness gate

An Oregon configuration row should identify organization, professional, role, location, OHP enrollment, CCO contract and roster or fee-for-service route, referring provider, member eligibility and CCO, Chapter 172 or other current policy source, authorization, claim setup, and revalidation. The requesting, performing, and referring parties each need their own identity and enrollment evidence when the OHA route requires it.

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 Oregon 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

Store entity and practitioner NPIs, taxonomy, ownership, licenses, certifications, locations, insurance, EFT, OHP application, enrollment decision, program and specialty, revalidation, and portal access. For each CCO, keep the contract, credentialing, roster, product, location, and effective date. Validate which provider relationships belong on the authorization and claim rather than assuming the group enrollment covers every named role.

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 an Oregon 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 Oregon 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 Oregon 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

Before submission, verify member OHP eligibility and CCO assignment. For a CCO-covered service, follow that CCO's current instructions. For OHA fee for service, the authorization page identifies the portal or updated MSC 3971 route and asks providers to attach only the clinical documents needed for review. Record the authorization number on updates so added material connects to the existing request. Preserve the receipt, notices, decision, approved scope, and status checks.

Release claims from verified evidence

The claim release should verify all provider identities, active OHP enrollment, CCO participation when applicable, member assignment, authorization, place of service, actual time, code and modifier, units, supervision, and documentation. Build separate payer profiles for each CCO and OHA fee for service. If a clinician, referral source, or location changes, reopen the relevant enrollment and authorization checks. Match the receiver's claim acknowledgment, adjudication, remittance, and EFT as separate steps.

A fictional readiness review

A fictional Eugene practice reviews 16 provider-role-CCO rows. Eleven are ready. One referring provider lacks verified OHP enrollment, two clinicians are absent from a CCO roster, one fee-for-service portal role cannot submit an update, and one location has no validated claim path. Readiness is 11 of 16, or 68.8%. The practice delays those five configurations and keeps the approved rows available rather than freezing the entire launch.

The Oregon 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

Review OHA policy, eligibility, CCO, and authorization pages monthly and after any provider, referral, location, or plan change. Measure OHP enrollment decisions received over applications due, CCO rosters effective over configurations due, complete authorization submissions accepted over submissions, updates attached to the original request over updates due, and mature first claims adjudicated without resubmission over mature first transmissions. Segment OHA fee for service and every CCO. Also age unresolved provider-role mismatches from the first verified conflict date and show how many scheduled services remain affected. That view exposes referral or performing-provider gaps that a group-level enrollment rate can hide.

Go/no-go checks before the first covered service

  • Requesting, performing, and referring providers meet the current enrollment rule for the route.
  • The member's OHP eligibility and CCO assignment are current for the scheduled service.
  • CCO instructions or the OHA fee-for-service handbook controls the request.
  • Authorization updates reference the existing request and preserve the complete history.
  • The claim profile matches provider roles, location, service, units, and authorization.

A go decision in Oregon 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