How can an ABA practice enroll with Maryland Medicaid and submit ABA prior authorization? Use Maryland's EPSDT ABA program sources to establish provider and practitioner requirements, complete the applicable Medicaid and Carelon registration, and configure the current authorization and billing route. Verify member eligibility, clinical evidence, provider, setting, dates, units, and service before release. Route sentinel events through the separate safety process on time.

Map the operative program route first

Maryland Medicaid's ABA program page is the current state index for EPSDT ABA services for eligible members under 21. It links provider resources, forms, notices, contacts, and the program manual. The linked ABA Provider Manual displays an effective date of July 1, 2024 and an update date of April 2025 in the document even though file metadata may use draft language. Record both the visible document version and retrieval date, then confirm later program notices.

The manual assigns significant authorization, provider-registration, and billing operations to Carelon. That contractor route belongs in the configuration along with Maryland Medicaid enrollment. The manual also sets a 24-hour route for specified sentinel events. Safety reporting, prior authorization, and claim submission are three separate workflows with separate owners and clocks.

Separate every readiness gate

Create Maryland rows by billing organization, professional role, site, Carelon relationship, member route, and ABA service. Track professional and entity authority, Medicaid enrollment, Carelon registration, portal access, member eligibility, EPSDT scope, authorization, claim setup, sentinel-event route, manual version, and revalidation. A successful Carelon login supplies access evidence, while provider approval and authorization require their own decisions.

Use four operational states for each Maryland 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

Prepare the Maryland application file with ownership, tax data, NPI and taxonomy, licenses or certifications, professional and group relationships, locations, screening, EFT, approval, and effective date. Complete any Carelon registration and credentialing steps required for the role and route. Preserve portal roles, delegate access, correspondence, approval, and revalidation. Keep current contact information beside each task so a staff change does not strand an application or safety report.

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 Maryland 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 Maryland 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 Maryland 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, Medicaid eligibility, provider status, and the current Carelon authorization route. Build the packet from the qualified assessment, diagnosis and referral or recommendation evidence, treatment plan, measurable goals, requested service, provider and setting, dates and units, supervision, and continued-stay data. Retain receipt, information requests, decision, approved scope, and renewal lead time. When clinical needs change, the clinician determines the recommendation and operations routes any required authorization update.

Release claims from verified evidence

Maryland claim release should compare Medicaid and Carelon provider status, member eligibility, authorization, billing and rendering identities, site, actual date and time, code and modifier, units, supervision, and completed documentation. Use the current manual and fee source for the service date rather than an old rate table. Reconcile receiver responses, adjudication, remittance, recoupment, and payment. A sentinel event follows its own urgent reporting path while claim and clinical follow-up continue under their respective rules.

A fictional readiness review

A fictional Frederick practice locks 14 Carelon-provider rows. Ten are ready. One professional lacks a confirmed registration, one site has no tested authorization access, one configuration cites only ambiguous file metadata instead of the visible manual version, and one safety route has no backup owner. Readiness is 10 of 14, or 71.4%.

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

Review the Maryland ABA page, manual, program notices, forms, fee sources, and Carelon materials monthly. Trigger review after a contractor, portal, provider, site, policy, form, contact, or sentinel-event rule changes. Measure registrations confirmed over rows due, authorization packets accepted over packets submitted, urgent reports made by their applicable clock over reports due, and mature first claims adjudicated without resubmission over mature first claims. Report safety and revenue measures separately.

Use a Maryland contact drill to verify urgent and routine routes. A designated staff member should be able to locate the current sentinel-event contact, the Carelon authorization channel, the provider-registration contact, and the claim-support route without relying on one employee's inbox. Record the test date and any failed route. Correct contact evidence promptly, while preserving the prior version for events and submissions already in progress.

Go/no-go checks before the first covered service

  • The EPSDT ABA source covers the member and service date.
  • Maryland Medicaid and Carelon provider states are both documented where required.
  • Authorization matches provider, site, service, dates, and units.
  • The visible manual version and later notices support the configuration.
  • The 24-hour sentinel-event route has a primary and backup owner.

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