How can an ABA practice enroll with Georgia Medicaid and submit ABA prior authorization? Complete the Georgia Medicaid provider application for the correct organization and practitioner roles, then establish the member's Georgia Families, Georgia Families 360, or other route. Verify each plan relationship and roster, gather the required diagnostic recommendation and clinical packet, obtain authorization, and release claims from matching provider, member, service, location, and date evidence.

Map the operative program route first

Georgia Medicaid's Autism Spectrum Disorder page states that the benefit serves eligible members under age 21, calls for a DSM-5 diagnosis and recommendation from a licensed practitioner, and points providers to enrollment coversheets, prior-authorization instructions, and a submission guide. Those links should be stored with their access and effective dates because a landing page can outlive a form revision.

Georgia Families and Georgia Families 360 are distinct delivery routes. A practice should identify the member's actual program and care-management organization before selecting a network, authorization, or claim workflow. State enrollment, plan contracting, roster acceptance, authorization, and payment remain separate states.

Separate every readiness gate

Build Georgia rows by billing entity, BCBA or other rendering role, location, program, care-management organization, and service. Include state enrollment, license or credential, contract, credentialing, roster, directory, portal, member eligibility, diagnostic and recommendation evidence, authorization, claim profile, and revalidation. Treat Georgia Families 360 as its own route instead of copying a standard Georgia Families configuration.

Use four operational states for each Georgia row: verified, pending, held, and expired. Store the source, scope, owner, effective date, last check, next action, and evidence link with the state. Software can surface omissions and contradictions. State agencies, plans, qualified clinicians, privacy or legal owners, and billing specialists retain decisions within their authority.

Build a source-backed enrollment file

Use the Georgia coversheet and enrollment path that matches the organization or practitioner. Preserve the submitted application, ownership and control disclosures, NPI, taxonomy, tax data, license or certification, service locations, group relationships, screening, approval, and effective date. Then create one file per targeted plan or program, with contract, credentialing, group and individual roster, product, location, rate, directory, and effective date. A plan directory entry is useful dated evidence, while the executed contract and roster control the practice's representation.

42 CFR 455.410 requires state Medicaid agencies to screen enrolled providers and to enroll covered ordering or referring professionals. For managed care, 42 CFR 438.602(b) assigns states enrollment, screening, and periodic revalidation duties for network providers. A single pending-network-agreement period may reach 120 days under the federal managed-care provision, yet that period supplies neither a billing effective date nor a payment promise for a Georgia practice. The CMS NPI fact sheet draws another practical boundary: an NPI identifies an individual or organization. Licensure, credentialing, Medicaid enrollment, network status, authorization, and payment require their own evidence.

Use a build-ready configuration record

Assign every Georgia configuration a durable identifier. Keep one row per billing entity, rendering professional or role, location, payer or program, product, service, and submission route. Recommended fields include legal name, NPI, tax identifier where applicable, taxonomy, license or certification, state enrollment number, screening and revalidation dates, contract, credentialing, roster, directory result, portal role, authorization path, claim receiver, effective period, source version, and named owner. Link the evidence that supports each field and preserve a change history. Broad free-text status notes make contradictions hard to detect and age poorly.

Create three useful Georgia views from the same controlled data. A launch view lists incomplete enrollment, contract, roster, portal, and claim-test work. A client release view joins member eligibility, delivery route, provider and site, qualified clinical decision, authorization, scheduled service, dates, and units. A reconciliation view links the original claim, acknowledgments, adjudication, remittance, deposit, corrections, refunds, and recoupments. Restrict sensitive fields by role. When two sources conflict, hold the affected configuration, preserve both versions, and ask the responsible agency or plan for written clarification.

Configure authorization by member and route

At intake, verify age, eligibility, assigned program and plan, provider participation, and current authorization route. The clinical packet should reflect the current diagnostic and licensed-practitioner recommendation requirements, qualified assessment, individualized treatment plan, requested service, dates and units, provider, setting, supervision, and any continuation data. Preserve the exact form version, submission receipt, information requests, decision, approved scope, and renewal trigger. Route clinical revisions to the responsible clinician.

Release claims from verified evidence

A Georgia claim release should join state enrollment, plan roster, member program, authorization, billing group, rendering professional, location, actual date and time, code and modifier, units, supervision, and completed record. Use separate receiver profiles for Georgia Families, Georgia Families 360, and other applicable routes. Distinguish acknowledgment, claim-level acceptance, adjudication, remittance, and deposit. If the member's program changes, hold the next service configuration until participation and authorization are rechecked.

A fictional readiness review

A fictional Savannah practice reviews 15 provider-plan-location rows. Ten are ready. Two clinicians remain absent from a care-management roster, one Georgia Families 360 configuration uses a standard-plan form, one site has no written network effective date, and one claim path has not produced a matched remittance. Readiness is 10 of 15, or 66.7%.

The Georgia denominator is locked before the review begins. Applications, portal accounts, directory entries, approvals at other sites, and unrelated claim tests cannot remove a held row. Each exception receives a responsible owner, next action, due date, and the exact evidence needed for release.

Measure the workflow after launch

Check the Georgia autism, Georgia Families, and Georgia Families 360 pages monthly, along with each applicable plan's current provider material. Trigger review after a new location, clinician, plan, product, enrollment decision, form revision, or member-program change. Measure enrollment decisions over applications due, rostered configurations over network rows due, authorization packets accepted over packets submitted, and mature first claims reaching adjudication without resubmission over mature first claims. Report each program separately.

Add a Georgia transfer check whenever a member moves between delivery routes or plans. Verify the last approved service date under the old route, the effective date under the new route, the provider's network status, and any new authorization requirements. Record family communication and continuity ownership. A copied authorization number should remain historical evidence until the receiving plan confirms that it applies to the new configuration.

Go/no-go checks before the first covered service

  • The enrollment coversheet matches the entity or practitioner role.
  • The member's Georgia program and plan are verified for the service date.
  • Contract, roster, location, and effective-date evidence support participation claims.
  • The authorization packet uses current diagnostic, recommendation, and form requirements.
  • The claim receiver matches Georgia Families, Georgia Families 360, or the other named route.

A go decision in Georgia applies to the named configuration and service period. An expired approval, credential, roster, authorization, source, or claim control pauses new covered-service promises on that row. Existing clients move through qualified clinical, payer, and continuity review under the applicable rules.

Related resources

Sources