To build a Connecticut HUSKY ABA claim adjustment workflow, separate the claim-processing evidence from the behavioral-health authorization evidence. Confirm the member's HUSKY benefit, service-date provider and authorization, original claim state, payer control number, remittance, and current filing clock. Use the Connecticut portal's appropriate resubmission or adjustment route, keep any Carelon clinical decision attached to the episode, and reconcile the later remittance without treating authorization as payment approval.

Define Connecticut's correction episode

Yara 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 Connecticut HUSKY and CT BHP authority

The Connecticut Medical Assistance Program provider-services page identifies Gainwell's portal functions for claim submission, status, eligibility, and prior-authorization inquiry while reserving policy and payment methodology to DSS. Provider Manual Chapter 10 directs users to the applicable web claim guide for submission, resubmission, adjustments, and inquiry. Yara records the exact guide and claim type used.

Choose the responsible Connecticut receiver

The CT BHP ASD provider page carries autism-provider clinical and authorization resources, while the DSS ASD program page describes the Medicaid service. Yara stores Carelon or CT BHP authorization evidence beside Gainwell claim evidence. One artifact cannot substitute for the other.

Classify the claim state before acting

Yara uses the register to classify eligibility or provider hold, portal rejection, suspended claim, denied claim correction, paid-claim adjustment, authorization review, coverage appeal, other-insurance resubmission, 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 HUSKY ABA adjustment and authorization register

Capture member and HUSKY benefit; Gainwell and CT BHP identifiers; provider and taxonomy; service and authorization; original claim and payer control number; claim type; portal response; remittance; correction reason; current filing clock; attachment; receipt; clinical decision; new remittance; cash effect; owner; and close date. 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

Yara 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, Yara 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 Connecticut clocks and versions

Yara 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

Yara searches the complete Connecticut 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

Yara 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 Yara's fictional cohort

Yara locks 21 fictional episodes at a New Haven practice. Fourteen initially have benefit, provider, authorization, claim state, control number, portal route, current clock, receipt, and remittance owner. One authorization issue is sent as a claim adjustment, one paid claim is copied as a new original, one HUSKY benefit is wrong, one other-insurance result is missing, one record lacks its control number, and two lack current filing dates. 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 Yara's measures

Initial readiness is 14 of 21, or 66.7%. Nineteen episodes reach valid action or documented hold, or 19 of 21, or 90.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 Connecticut failure mode

Connecticut uses separate operational and clinical systems. A claim visible in the Gainwell portal does not prove CT BHP authorization, and an authorization does not prove that Gainwell accepted or paid the claim.

Test Yara's workflow

Yara tests a portal rejection, suspended claim, paid adjustment, HUSKY benefit mismatch, CT BHP authorization gap, TPL result, filing-clock edge, and remittance take-back. 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

Yara 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

Yara 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 HUSKY ABA adjustment and authorization register

Yara 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 Connecticut page remains draft and noindex until the named reviewers clear it.

Related resources

Sources