TennCare ABA individual and group registration Medicaid IDs and MCO credentialing requires separate professional, state, and plan records. A behavior analyst or assistant behavior analyst first needs the applicable active Tennessee professional license. Individual providers register electronically and maintain their profile through Data Spring, formerly CAQH, while groups and entities use the TennCare Provider Registration Portal for the organization, ownership, addresses, and rosters. A valid active Medicaid ID is still separate from each MCO's network contract, credentialing, roster, authorization, and payment rules. TennCare enrollment FAQ Tennessee behavior analyst licensing

Build three layers: professional, TennCare, and MCO

The practice should be mapped before anyone registers. Create one row for the legal organization, one for each licensed behavior analyst or licensed assistant behavior analyst, one for every service location, and one for each TennCare managed care product the practice intends to serve. Preserve the legal name, NPI, taxonomy, tax identity, license, supervisor when applicable, employer or group, address, and intended billing relationship.

The TennCare provider page separates provider enrollment from managed care contractor resources. The enrollment FAQ says providers must contract separately with each TennCare MCO to become in network. TennCare enrollment and MCO boundary

These layers need explicit boundaries. A Tennessee professional license does not create a Medicaid ID. A Medicaid ID does not create a BlueCare, Wellpoint, UnitedHealthcare Community Plan, or TennCare Select contract. A plan credentialing approval does not automatically establish a roster, location, authorization, or payable claim.

Enrollment staff can assemble evidence and route questions. Qualified clinical leaders decide scope and supervision. Legal and ownership reviewers approve disclosures. Billing owners determine supported transaction identities. No administrative user should collapse all three layers into one “credentialed” status.

Confirm the Tennessee professional license first

The Tennessee Applied Behavior Analyst Licensing Committee licenses qualified candidates to practice applied behavior analysis in the state. Its current page provides online and paper application routes, verification, renewal, background-check information, and the applicable rules and statutes. Tennessee behavior analyst licensing committee

The May 2025 LBA and LABA application packet separates Licensed Behavior Analyst and Licensed Assistant Behavior Analyst applications and describes the supporting materials. It also requires ongoing supervision evidence for a licensed assistant behavior analyst applicant. Use the current online process and board guidance for the actual applicant rather than copying an old checklist.

The license record should preserve the type and number, status, verification source, checked and expiration dates, application or renewal evidence, BACB credential when applicable, supervisor record for an assistant role, and the locations in which the professional will work. Keep those records separate from TennCare and plan determinations.

Administrative staff may collect and compare evidence and monitor deadlines. They should not decide whether a person may practice, whether supervision is adequate, or whether a license exception applies. Those questions belong with the Committee, qualified professional leadership, and counsel as applicable.

Route individuals through registration and Data Spring

TennCare's current FAQ says individual providers register electronically through the Provider Registration path and are placed on the Data Spring roster, formerly CAQH. Existing individuals with a valid active Medicaid ID also use the electronic process so TennCare can receive profile updates. TennCare individual registration

The individual evidence file belongs ahead of submission. It should support legal identity, Type 1 NPI and taxonomy, tax and practice information, professional license, Data Spring profile, service locations, group affiliations, disclosures, and any applicant-specific attachment displayed by the live process.

Each source system needs a named controller and a last-attested date. A complete Data Spring profile is not itself a TennCare approval, and a TennCare registration does not prove the profile is current. Preserve the registration receipt, Medicaid ID, state notice, Data Spring attestation, and any returned questions separately.

If an individual receives an unexpected new Medicaid ID, the FAQ directs providers to TennCare Provider Services for review. Do not choose which ID to use by convenience, merge records internally, or submit claims until TennCare confirms the correct identity.

Register the group or entity and maintain its roster

The TennCare FAQ says group and entity providers register through the Provider Registration process for “All Other Provider Registration Information.” The account supports address changes, individual-provider roster updates, and ownership disclosures, and a new group receives a Medicaid ID after successful completion and approval. TennCare group and entity registration Applicants should enter through the current TennCare Provider Registration Portal rather than a saved or third-party login URL.

The group file should support the legal and DBA names, Type 2 NPI when applicable, tax identity, ownership and managing employees, service and correspondence addresses, EFT, authorized signer, portal administrator, and every professional and location relationship the practice intends to use.

Do not treat an employment roster as an approved TennCare roster. Preserve the submitted version, tracking record, returned questions, approval, actual effective date, and subsequent additions and removals. A person may have an active individual record and still lack the group or location relationship needed for a specific configuration.

Named users should have their own access and least-necessary permissions. When staff leave, review portal access and open tasks promptly. Sensitive ownership, identity, tax, credential, and banking evidence belongs in role-limited storage.

Preserve the active Medicaid ID and exact effective configuration

A submitted registration, portal login, or profile entry is not the same as an active Medicaid ID. For each transaction, preserve the applicant, NPI and taxonomy, entity or individual category, group and location relationships, supporting evidence, submitter, tracking number, submission date, correspondence, response deadlines, and written determination.

Compare the approved result with the intended configuration. Confirm the person or entity, Medicaid ID, locations, group roster, effective date, and any limitations before a plan application or service-release record relies on it.

If TennCare returns an item, preserve the exact reason and original submission. Correct only supported facts. Do not create a duplicate identity to bypass an error or backdate a license, group affiliation, location, ownership change, or effective date to support prior services.

The TennCare contact page and provider-services channels are the appropriate routes for applicant-specific questions. Keep written guidance with the affected configuration so a later reviewer can see why the practice acted.

Contract and credential separately with each MCO

TennCare's FAQ says providers must contract with each MCO separately and provides current plan contact routes. TennCare MCO contracting contacts Maintain one state provider record and a separate plan-product record for BlueCare, Wellpoint, UnitedHealthcare Community Plan, TennCare Select, or any other applicable product.

For each plan, the evidence packet needs its network request, credentialing disposition, countersigned contract, and reimbursement terms. Add accepted clinicians and sites, directory verification, user access, authorization channel, claim routing, participation start date, recredentialing deadline, and termination conditions. A contract for one product or region should not be copied to another.

Before a covered start, verify current member eligibility and plan, professional license, TennCare ID, group and location relationship, plan contract and roster, authorization, rendering and billing identities, supervisor, code and modifier, units, place of service, and documentation. The existing plan-specific owner guides remain the place for plan operations details.

When state and plan instructions conflict, hold the affected configuration and request written clarification. Do not infer a plan effective date from the TennCare approval or treat a directory result as the contract.

Revalidate and update licenses, locations, ownership, and users

TennCare providers must revalidate at least every three years, with off-cycle work possible under current program instructions. The state requires a unique NPI for each enrolled service location and provider type and sends notices before the applicable deadline. TennCare revalidation

The TennCare Provider Resource Board says registrations that include a license upload must maintain an active license. Individual providers update and reattest in Data Spring, while applicable group or entity work occurs in the Provider Registration Portal. A board renewal, profile update, state acceptance, and plan recredentialing are separate records.

Calendar professional licenses, Data Spring attestations, TennCare revalidation, ownership and managing employees, group rosters, service locations, EFT, portal administrators, MCO recredentialing, rosters, and directories. The live notice controls the due date; an internal calendar is a prompt.

When a person, site, owner, or portal user changes, preserve the old value and effective date, identify every dependent state and plan record, and close access that is no longer needed. Historical services and claims should remain understandable.

Run a person-group-location-product readiness review

A review of TennCare ABA individual and group registration Medicaid IDs and MCO credentialing should end at the person-group-location-product level. Imagine a fictional Tennessee ABA practice with one group, two LBAs, one LABA, and two locations. The group has an active Medicaid ID. One LBA is current in Data Spring, the second has renewed the professional license but has not reattested, the LABA's supervisor is not yet reflected on one plan roster, and the second location is missing from the UnitedHealthcare product record.

The practice holds only the affected rows. It does not label every clinician and site active, assume the board renewal updated TennCare, or copy another plan's effective date. Qualified clinicians decide supervision, scope, and continuity for existing members.

The recurring review should reconcile license verifications, Data Spring profiles, TennCare determinations, group rosters, location records, plan agreements, roster status, authorizations, schedules, and claim exceptions. Each exception needs a source, owner, due date, evidence request, disposition, and a defined review cadence.

The Finni provider services page describes bounded administrative support for ABA organizations. A Tennessee engagement can organize evidence, coordinate registration and maintenance, track profile and license tasks, reconcile plan rosters, and surface exceptions. It cannot issue a professional license, approve a Medicaid ID, create an MCO effective date, decide supervision or scope, authorize care, select unsupported billing data, or guarantee payment.

Related resources

Sources