To build a Maryland Medicaid ABA claim adjustment and void workflow, start with the Carelon or Medicaid claim result and verify whether provider action is required. Preserve the original claim number, remittance, authorization, service record, correction reason, complete replacement data, submission receipt, and new adjudication. Use the current Carelon route for an adjustment or void, while keeping automatic reprocessing, authorization review, payment dispute, and appeal as separate states.

Define Maryland's correction episode

Cora defines one episode as the original claim or local hold plus every transmission, rejection, adjudication, remittance, payment, correction, void, replacement, appeal, recoupment, refund, and closure event tied to it. The episode preserves raw evidence and the author of each clinical, coding, billing, payer, and financial decision.

Use the current Maryland Medicaid ABA and Carelon authority

Maryland's Carelon transition FAQ says ProviderConnect accepts claim adjustments and voids and describes electronic frequency 7 and 8 handling with the original claim number in the specified reference segment. Cora treats those values as Carelon route instructions and confirms the current guide before release.

Choose the responsible Maryland receiver

The Maryland Medicaid ABA page identifies Carelon as the ABA administrator and links the current ABA Provider Manual. A December 2025 transmittal changed 2026 combination-of-service rules, discontinued H2012 on February 1, 2026, and identified certain claims for automatic reprocessing with no provider action. Cora prevents duplicate resubmission while reprocessing is pending.

Classify the claim state before acting

Cora uses the register to classify local hold, Carelon rejection, denied claim correction, adjustment, void, automatic reprocessing, authorization issue, payment dispute, appeal, refund, or reconciled close. Staff save the artifact that proves the state and receiver. A portal label, clearinghouse message, authorization number, claim-frequency value, directory entry, or call note establishes only what that source actually reports.

Build the Maryland Carelon ABA adjustment and void register

Capture member; Carelon provider and location; ABA service, code-year and authorization; original claim and reference number; remittance; correction or void reason; automatic-reprocessing flag; complete replacement data; submission route; receipt; new decision; take-back or payment; owner; deadline; and closure. Structured fields drive routing, aging, and reconciliation. A short narrative records the source-record issue, permitted change, uncertainty, payer instruction, client impact, disagreement, and reason the accountable reviewer selected the action.

Keep clinical and billing authority distinct

Cora never changes clinical content merely to obtain payment. A qualified clinician makes any permitted late entry, addendum, or correction under the practice's documentation policy, preserving original content, authorship, dates, and reason. A qualified coding or billing reviewer maps verified evidence to the current receiver's route. Operations coordinates without authoring a clinical judgment or payer decision.

Run a source-to-claim comparison

Before release, Cora compares member and payer, provider identity, service location, authorization, completed record, actual date and time, code and units, prior claim state, requested change, reference identifier, attachment set, route, and deadline. The reviewer also states what should happen to the earlier claim and payment. Unknowns remain held with an owner and escalation path.

Preserve Maryland clocks and versions

Cora stores separate clocks for original filing, correction, adjustment, appeal, authorization, response, refund, and overpayment work. Each clock has a named start event, due event, source, timezone when relevant, and exception evidence. The register also keeps the manual, plan, form, portal, fee, code, and alert version used on the action date. Later guidance triggers review without erasing the earlier source.

Prevent duplicate action

Cora searches the complete Maryland episode before another transmission. The check covers clearinghouse controls, payer references, remittances, replacements, voids, disputes, appeals, refunds, recoupments, and manual workarounds. A valid release states whether the earlier claim should remain, reverse, replace, or await payer action. A pending reprocessing event is never treated as permission to submit another claim.

Protect clients and honest records

Cora separates financial follow-up from the family's care plan. A claim hold does not silently cancel clinically appropriate care, and a coverage decision does not become a clinical recommendation. The practice follows its lawful notice, continuity, record, collection, and emergency policies. Staff never shift a provider-correctable denial or prohibited charge to a member merely because correction is slow.

Work through Cora's fictional cohort

Cora locks 23 fictional Maryland episodes at a Frederick practice. Sixteen initially have claim state, original reference, authorization, code-year check, correct route, reprocessing check, receipt, and finance owner. Two claims scheduled for automatic reprocessing are queued as replacements, one adjustment lacks its reference, one void omits original charges, one H2012 line uses a post-sunset date, and two records lack remittances. Five repair. Two remain held. The example is synthetic. It tests workflow and denominator logic and establishes no coverage, authorization, claim, appeal, compliance, legal, or payment conclusion for a real practice or member.

Calculate Cora's measures

Initial readiness is 16 of 23, or 69.6%. Twenty-one episodes reach valid action or documented hold, or 21 of 23, or 91.3%. Report local holds, front-end rejects, adjudicated denials, paid claims, adjustments, voids, replacements, disputes, appeals, recoupments, refunds, and final payments as separate cohorts. Every held or failed episode remains in its declared denominator.

Address the central Maryland failure mode

Automatic reprocessing and provider-initiated replacement can collide. Cora records the state notice, affected claim, expected action, wait point, and escalation path before another transmission. She closes the wait only after a remittance, Carelon status, or written escalation response resolves the claim.

Test Cora's workflow

Cora tests an adjustment, full void, missing original reference, automatic reprocessing, H2012 after February 1, 2026, authorization mismatch, payment dispute, and take-back that does not match the replacement. Each test preserves its starting state, expected route, evidence, observed result, owner, correction, retest, and disposition. A successful submission passes the transmission check only. Adjudication, remittance, payment, and reconciliation require their own artifacts.

Reconcile remittance and cash

Cora links each payer decision to the remittance and each remittance to the actual deposit, debit, recoupment, refund, or accounts-receivable balance. Partial effects remain open. A new payment does not erase an unresolved earlier overpayment, and a zero-dollar remittance still needs review. Finance records claim-level allocation before closing the episode.

Run independent acceptance

Cora gives an independent reviewer the locked cohort, official sources, original claims, source records, authorizations, payer artifacts, routes, receipts, remittances, and cash reconciliation. The reviewer reproduces one correction and one hold. A changed cohort, missing failure, unsupported route, or unexplained financial difference fails acceptance.

Maintain the Maryland Carelon ABA adjustment and void register

Cora reviews sources monthly and after program, plan, manual, code, form, portal, contract, authorization, fee, edit, appeal, or contact changes. Each source retains owner, effective and checked dates, scope, supersession, and next review. This Maryland page remains draft and noindex until the named reviewers clear it.

Related resources

Sources