To build a Georgia Medicaid ABA claim correction and CMO dispute workflow, verify the member's program and the care management organization or fee-for-service receiver that adjudicated the claim. Preserve the original claim, explanation of payment, authorization, provider and service evidence, correction or dispute reason, submission receipt, decision, and cash effect. Apply the responsible receiver's current contract and manual instead of moving every payment problem through one generic corrected-claim path.
Define Georgia's correction episode
Zane 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 Georgia Medicaid and Georgia Families authority
Georgia Medicaid's autism-services page anchors the ABA benefit. The Georgia Families page and Georgia Families 360 page describe different managed-care populations and plan relationships. Zane verifies the member's service-date program before using any plan correction or dispute instruction.
Choose the responsible Georgia receiver
The current Georgia Families contract requires CMO procedures for claim-adjustment requests and payment disputes. It distinguishes positive and negative adjustments and preserves appeal rights. Zane records the plan, contract version, payment month, explanation of payment, supporting documents, completeness response, and appeal state rather than applying that CMO process to a different receiver.
Classify the claim state before acting
Zane uses the register to classify fee-for-service hold, CMO rejection, denied claim correction, positive adjustment, negative adjustment, payment dispute, provider appeal, administrative hearing route, 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 Georgia CMO correction and dispute register
Capture member and program; CMO or fee-for-service receiver; provider and location; service and authorization; original claim; explanation of payment; adjustment direction; disputed amount; contract deadline; documentation; completeness response; correction receipt; appeal or hearing state; remittance; cash effect; owner; 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
Zane 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, Zane 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 Georgia clocks and versions
Zane 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
Zane searches the complete Georgia 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
Zane 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 Zane's fictional cohort
Zane locks 19 fictional Georgia episodes at a Macon group practice. Twelve initially have member program, receiver, claim state, explanation of payment, authorization match, adjustment or dispute route, deadline, receipt, and cash owner. One Georgia Families 360 claim uses another CMO's portal, one positive adjustment lacks payment evidence, one negative adjustment has no amount, one incomplete request misses its cure date, one denial is mislabeled as a dispute, and two lack service-date program proof. 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 Zane's measures
Initial readiness is 12 of 19, or 63.2%. Seventeen episodes reach valid action or accountable hold, or 17 of 19, or 89.5%. 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 Georgia failure mode
A Georgia CMO contract can define a payment-dispute path without authorizing the CMO to rewrite clinical documentation or guaranteeing a particular adjustment. Keep the clinical record, claim correction, payment dispute, and appeal authored separately.
Test Zane's workflow
Zane tests a positive adjustment, negative adjustment, incomplete request, Georgia Families 360 member, fee-for-service claim, authorization mismatch, appeal after denial, and later offset on the remittance. 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
Zane 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
Zane 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 Georgia CMO correction and dispute register
Zane 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 Georgia page remains draft and noindex until the named reviewers clear it.
Related resources
- Build an Illinois Medicaid ABS Claim Adjustment and Void Workflow
- Build a Connecticut HUSKY ABA Claim Adjustment Workflow
- Build a Kentucky Medicaid ABA Claim Correction and Appeal Workflow
- Build an Arkansas Medicaid ABA Claim Adjustment and Void Workflow