How can an ABA practice enroll with Delaware Medicaid and configure MCO workflows? Choose the full Delaware Medical Assistance Program enrollment path or the managed-care-only screening path that fits the intended billing route. Then complete each targeted MCO's contracting, credentialing, roster, authorization, portal, and claim requirements. Keep state screening registration, plan participation, member assignment, authorization, claim acceptance, and payment as separate states.

Start with the controlling delivery route

Delaware's provider enrollment page offers standard enrollment and a streamlined MCO-only application for federally required screening and continuing participation with a Delaware MCO. Select the route from the actual business and payment model. An MCO-only registration is not a fee-for-service billing approval.

The DMAP provider portal directs MCO and MCO-only providers to the relevant plan handbook or plan contact for plan-specific requirements. The registration selector distinguishes provider, clerical representative, trading partner, MCO, and MCO-only roles. Assign those identities deliberately so administrative access never becomes evidence of a contract, clinical authority, or payment status.

Keep enrollment and service gates separate

Create Delaware rows by entity, practitioner, location, DMAP or MCO-only enrollment route, plan, product, service, authorization receiver, and claim receiver. Track screening, state status, contract, credentialing, roster, directory, portal role, trading-partner access, eligibility, authorization, claim configuration, effective dates, and revalidation. A plan-specific rule belongs only to the plan and product it names.

Use verified, pending, held, and expired as the four Delaware workflow states. Each state should identify the decision owner, primary source, scope, effective period, last check, evidence, and next action. Software 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

Document why each entity and practitioner uses standard or MCO-only enrollment. Preserve ownership, tax, NPI, taxonomy, credential, screening level, affiliation, location, application number, approval, effective date, and revalidation. For every MCO, retain the executed contract, credentialing result, roster acceptance, product, site, rate, directory status, and effective period. Provision least-privilege portal and trading-partner roles, then test each operational route.

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 Delaware 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 Delaware row a stable key built from entity, enrollment route, provider, plan, product, and location. The operational view should expose whether the row is full DMAP or MCO-only, the plan roster and contract dates, portal role, trading partner, authorization receiver, and claim receiver. Store one explicit release decision per plan configuration so state screening never masquerades as network approval.

Build a Delaware route matrix before applications are submitted. For each planned plan and product, identify whether the entity needs full DMAP enrollment, MCO-only screening registration, or another documented state status; which individuals and locations must appear; who owns contracting and credentialing; and which portal and trading-partner roles support authorization, claims, and remittance. Record the plan handbook version beside every extracted rule. A roster file, directory result, or portal login should have its own verified date and should never populate the other states automatically. During testing, submit a fictional eligibility inquiry, walk a fictional authorization through the correct receiver, validate the billing and rendering identity combination, and retrieve the matching remittance. Document any plan-specific correction, appeal, or resubmission path. This matrix lets the practice see whether a hold comes from state screening, the plan contract, provider roster, member route, clinical evidence, transaction access, or claim configuration. Review role access after staffing changes and record each removed permission.

Scope Delaware access by enrollment, plan, clinical, and billing role. The client-release view should join the exact MCO product, roster, clinical packet, and authorization, while the transaction view retains the trading partner, original claim, payer response, remittance, and correction. A Delaware field without a dated plan or state source stays unresolved.

Configure authorization for the member

Verify the member's plan and product, active network configuration, provider and location, current plan handbook, qualified clinical evidence, requested service, dates and units, staff, supervision, and submission route. Preserve the request, reference, questions, decision, approved scope, expiration, and review rights. A portal user can transmit evidence; the payer owns its coverage decision and qualified clinicians own clinical content.

Release claims from the service record

Before a Delaware claim leaves the practice, match member assignment, state screening status, contract and roster, authorization, billing and rendering identities, service location, actual time, codes, modifiers, units, and completed record. Separate trading-partner acceptance from MCO adjudication and payment. Reconcile remittance and deposits by plan, and link every correction to the original transaction.

A fictional launch review

A fictional Dover practice reviews 18 entity-provider-plan rows. Twelve are ready. One MCO-only registration is pending, one full DMAP row uses the wrong route, two plan rosters omit practitioners, one authorization receiver changed, and one trading-partner account cannot retrieve remittance. Readiness is 12 of 18, or 66.7%.

The Delaware example locks its denominator before review. Every held row remains visible with reason, owner, due date, next action, and release evidence. Readiness describes the evidence available for that configuration; it predicts neither clinical benefit nor payer payment.

Monitor the live workflow

Review DMAP enrollment notices, MCO-only guidance, portal roles, each MCO handbook, authorization instructions, and claim updates monthly. Measure approved state registrations over rows due, plan rosters effective over plan rows due, complete authorization packets over packets submitted, matched remittances over claims paid, and mature first claims adjudicated without resubmission over mature first claims.

Keep a dated Delaware change register. Mark each notice, manual, form, fee file, contract, or portal instruction as current, future, proposed, superseded, paused, or archived. Identify affected rows, test changes with approved fictional data, and record the production approval.

Go/no-go review before covered service

  • The DMAP or MCO-only enrollment route matches the intended payment path.
  • Every plan contract, credentialing decision, roster, product, and location is current.
  • Portal and trading-partner access use the correct scoped role.
  • Clinical evidence, dates, units, staff, and setting match authorization.
  • Claim and remittance testing is complete for the named receiver.

A go result applies only to the named Delaware configuration and service period. When authority, 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.

Related resources

Sources