How can an ABA practice enroll with Texas Medicaid and submit Autism Services authorization? Enroll the organization, qualified professionals, and required service locations through the applicable Texas Medicaid process, then establish managed-care plan participation or fee-for-service routing. For eligible members age 20 and younger, treat evaluation authorization and treatment authorization as separate stages, using the current Children's Services Handbook and release notes for each service date.

Start with the controlling delivery route

Texas publishes the current Medicaid Provider Procedures Manual by monthly effective date. The Children's Services Handbook contains the Autism Services section for eligible members age 20 and younger and separates an initial evaluation route from later treatment-plan and service authorization. Store the exact manual version with each configuration.

The 2026 release notes identify monthly changes. A policy sentence can move, change, or take effect after a claim configuration was built. Treat release notes as a change signal and the operative handbook as the service rule. Managed-care plans may add product-specific submission instructions, while state enrollment, plan contract, roster, authorization, and payment remain separate decisions.

Keep enrollment and service gates separate

Create Texas rows by billing entity, individual provider role, service location, managed-care plan or fee-for-service route, evaluation or treatment stage, service, and authorization period. Track enrollment, professional authority, plan contract and roster, member eligibility, referral or order when applicable, evaluation authorization, treatment authorization, claim receiver, manual version, and revalidation.

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

Build the provider enrollment file

Complete Texas Medicaid enrollment for the actual provider types, specialties, affiliations, and locations. Retain ownership, tax, NPI, taxonomy, license or certification, screening, group relationship, EFT, decision, effective date, and revalidation. For each MCO, preserve contract, credentialing, billing and rendering roster, product, site, rate, directory result, and effective dates. Test evaluation and treatment authorization roles separately and complete a claim-remittance test for each receiver.

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 limited pending-network-agreement period supplies neither a billing effective date nor a payment promise for a Texas provider. The CMS NPI fact sheet explains that an NPI identifies an individual or organization. Licensure, Medicaid enrollment, plan credentialing, contract, roster, authorization, and payment each require their own evidence.

Make the configuration record usable

Give each Texas row a durable identifier. Use one row for every material combination of billing entity, rendering role, service 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.

Texas needs a launch view for incomplete enrollment, MCO rosters, portal roles, manual updates, and claim tests. Its client view should separate evaluation and treatment while joining age, payer route, provider, location, authorization, dates, and units. The revenue view traces each claim through acknowledgment, adjudication, remittance, deposit, correction, and recovery. Limit field access by role and retain the monthly rule history.

Configure authorization for the member

For evaluation, verify member age and route, provider eligibility, referral or order when required, requested evaluation service, provider, location, dates, and current supporting evidence. After the qualified clinician completes the evaluation and recommends care, build a separate treatment request with the plan, goals, clinical rationale, service, setting, dates and units, staff, supervision, and family participation. Preserve both decisions and prevent one stage's approval from releasing the other.

Release claims from the service record

Before a Texas claim leaves the practice, compare member route, enrollment and plan roster, correct authorization stage, billing and rendering identities, location, actual service time, code and modifier, units, supervision, and completed documentation. Apply the manual version for the service date. Track clearinghouse response, plan acceptance, adjudication, remittance, and deposit separately, then age corrections by original claim episode.

A fictional launch review

A fictional San Antonio practice reviews 18 provider-route-stage rows. Twelve are ready. One provider location is pending, two MCO rosters omit practitioners, one evaluation approval is being used for treatment, one request uses a superseded manual month, and one receiver lacks a remittance test. Readiness is 12 of 18, or 66.7%.

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

Monitor the live workflow

Review the current TMPPM, Children's Services Handbook, release notes, MCO manuals, and provider notices every month. Measure enrollment decisions over applications due, MCO rosters active over plan rows due, evaluation decisions over evaluation requests due, treatment decisions over treatment requests due, and mature first claims adjudicated without resubmission over mature first claims. Segment evaluation, treatment, plan, and fee-for-service work.

Keep a dated Texas change register. For each notice, manual, fee file, form, contract, or portal instruction, record whether it is current, future, proposed, superseded, or archived. Identify affected configurations, test changes on approved fictional data, and document the production approval. This makes source maintenance observable.

Use separate work queues for evaluation and treatment. The evaluation queue closes only when the authorized assessment is completed, the record is signed under applicable requirements, and findings are routed to the qualified clinician. The treatment queue opens from the resulting recommendation and current payer instructions. Track each queue's requested, received, approved, used, and remaining units. This prevents unused evaluation units, an evaluation reference number, or a draft plan from being presented as treatment approval.

Review both queues whenever the member, plan, provider, location, or service date changes.

Go/no-go review before covered service

  • The member is within the current Autism Services age scope.
  • Provider enrollment and plan participation cover the role and location.
  • Evaluation and treatment authorization records remain separate.
  • Service, plan, dates, units, staff, and setting match the decision.
  • The manual version was operative for the service date.

A go result applies only to the named Texas 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 applicable requirements.

Related resources

Sources