How can an ABA practice join TennCare and submit ABA prior authorization? Register the organization and individual providers through the applicable TennCare routes, keep CAQH information current, confirm Tennessee professional authority, and contract and roster with each targeted managed-care organization. Verify the member's plan and setting, then use that plan's current ABA authorization and claim workflow. School-specific rules apply only to their stated context.

Start with the controlling delivery route

TennCare's individual registration portal says individual providers register electronically and use an attested CAQH profile for enrollment or updates. Organizational providers use the corresponding organization route. Treat state registration, CAQH data, MCO credentialing, contract, roster, and effective date as separate milestones.

TennCare members use managed-care organizations listed on the current MCO page. The Tennessee licensure page supplies the professional-authority checkpoint. The school-based billing manual explains a specific school workflow, including Tennessee-licensed BCBA and MCO conditions. That manual expressly leaves other TennCare policy in place, so home, clinic, and community configurations use the member MCO's current sources.

Keep enrollment and service gates separate

Create Tennessee rows by organization, individual provider, service location, MCO, product, setting, and service. Track Medicaid ID, CAQH attestation, license, contract, credentialing, roster, directory, member plan, authorization, claim receiver, re-verification, and source version. A school district row also needs its education-plan and school-billing evidence, without extending those fields to every clinic case.

Use verified, pending, held, and expired as the four Tennessee 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

Complete the organization registration and each applicable individual registration with accurate NPI, taxonomy, ownership, tax, location, license, credential, EFT, and contact data. Keep CAQH service locations and attestations current before TennCare retrieves the profile. For every MCO, retain the executed agreement, credentialing decision, billing and rendering roster, product, location, rate, and effective date. Verify the Medicaid ID and secondary-provider claim mapping in a controlled test.

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 a Tennessee 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 Tennessee 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 Tennessee 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

At intake, verify the member's MCO, provider network status, service, setting, and current authorization route. Assemble the qualified clinician's assessment, order or referral when required, individualized plan, requested dates and units, staff and supervision, setting evidence, and continued-stay data. For school-based services, use only the current school requirements that apply to the student's situation. Preserve the receipt, questions, decision, approved scope, and renewal trigger.

Release claims from the service record

Before a Tennessee claim leaves the practice, compare the MCO, contract and roster dates, member eligibility, authorization, billing and rendering identities, Tennessee license, site, actual time, service, code and modifier, units, supervision, and completed note. TennCare's online systems and MCO portals are distinct receivers. Reconcile front-end rejection, adjudicated denial, remittance, and payment separately, then retain each correction with the original episode.

A fictional launch review

A fictional Knoxville practice reviews 17 organization-provider-MCO rows. Eleven are ready. Two clinicians have stale CAQH attestations, one license renewal is pending, one MCO roster lacks a service location, one school row uses clinic authorization evidence, and one claim profile has no matched remittance. Readiness is 11 of 17, or 64.7%.

The Tennessee 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 TennCare registration, MCO, licensure, provider memo, and setting-specific sources monthly. Measure registration decisions over applications due, current CAQH attestations over profiles due, MCO rosters effective over plan rows due, authorizations decided before target over requests due, and mature first claims adjudicated without resubmission over mature first claims. Segment school, home, clinic, and community configurations.

Run a Tennessee roster reconciliation after every CAQH or practice-location update. Compare the TennCare registration record, CAQH profile, executed MCO agreement, plan roster, directory, and internal scheduling location for every affected clinician. A matching address alone is insufficient; retain the product, provider role, effective date, and source. Keep each discrepancy open until the party responsible for that record confirms the correction in writing.

Archive the confirmed response with the row.

Keep a dated Tennessee 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

  • Organization and individual TennCare registration records are current.
  • CAQH and Tennessee license evidence match the provider and locations.
  • The targeted MCO supplied contract, roster, and effective-date evidence.
  • The authorization route matches the member, setting, service, dates, and units.
  • School-specific rules remain scoped to school-based billing.

A go result applies only to the named Tennessee 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