To build a Pennsylvania IBHS ABA PROMISe claim adjustment workflow, verify whether fee-for-service PROMISe or the member's Behavioral HealthChoices plan adjudicated the claim. For a fee-for-service rejection or adjustment, follow the current IBHS professional-claim instructions and preserve the original or last-approved ICN, line, authorization number, remittance, and supporting record. Use the plan's own correction and appeal path for managed-care claims, then reconcile the resulting remittance and payment.

Define Pennsylvania's claim-correction episode

Rosa 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 keeps raw evidence and preserves who made each clinical, coding, billing, payer, and financial decision.

Use the current Pennsylvania Medical Assistance and IBHS authority

Pennsylvania's current IBHS CMS-1500 completion guide distinguishes a rejected-claim resubmission from an adjustment of a previously approved claim. Its Block 22 instructions use the original rejected ICN for the former and the last approved 13-digit ICN plus line for the latter. Block 23 carries the authorization number when applicable. Rosa preserves the distinction at claim-line level.

Choose the correct Pennsylvania payer route

The PROMISe resource page identifies the system as the fee-for-service claims, provider-enrollment, and user-management platform and links error-status and billing resources. The IBHS page anchors agency and ABA requirements, while the billing page routes providers to current professional guides. Behavioral HealthChoices claims follow the responsible BH-MCO rather than PROMISe FFS correction fields.

Classify the current claim state before action

Rosa uses the register to classify county and payer, then local hold, PROMISe rejection, FFS denied claim, approved-claim adjustment, BH-MCO corrected claim, BH-MCO dispute, appeal, overpayment return, or reconciled close. Staff record the actual artifact and receiver. A portal label, clearinghouse status, authorization number, frequency code, or customer-service note cannot establish a later adjudication or payment state by itself.

Build the IBHS PROMISe adjustment episode register

Capture member, county and payer; licensed IBHS agency and service; provider and location; authorization; claim and line; original or last-approved ICN; error-status or remittance; corrected source evidence; Block 22 and 23 values when applicable; attachments; submission route; receipt; new decision; payment effect; owner; and deadline. Structured fields support routing, deadlines, reconciliation, and reporting. Narrative fields preserve the source-record issue, permitted correction, uncertainty, payer instruction, client impact, disagreement, and why the accountable reviewer selected the route.

Keep the source record and claim change separate

Rosa never edits 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 the verified record to the current payer route. Operations can coordinate evidence and status without authoring clinical judgment.

Run a pre-release comparison

Before release, Rosa 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 checks what will happen to the earlier claim and payment. Unknowns stay held with an owner and escalation path.

Preserve Pennsylvania clocks and source versions

Rosa records a separate start and end event for the original filing limit, corrected-claim window, adjustment period, appeal deadline, authorization span, response target, and any overpayment action. A generic age field cannot safely represent all of those clocks. The IBHS PROMISe adjustment episode register also stores the manual or plan version that supported the route on the action date. When later guidance changes, open episodes retain the earlier evidence and receive a documented current-source review instead of a silent overwrite.

Control duplicate and financial effects

Rosa searches the full Pennsylvania episode before another transmission. The check covers clearinghouse control numbers, payer claim references, remittances, earlier replacements, voids, appeals, refunds, recoupments, and manual workarounds. When a new submission is valid, the release record states whether the earlier claim should remain, reverse, replace, or await payer action. Finance receives the expected debit, credit, or zero-payment result and compares it with the later remittance and bank activity. Any difference remains open with a named owner.

Work through Rosa's fictional example

Rosa locks 21 fictional Pennsylvania episodes. Fourteen initially have county and payer, IBHS service authority, claim state, correct ICN basis, line, authorization, route, receipt, and payment owner. Two BH-MCO claims enter PROMISe, one rejected claim uses a last-approved ICN rule, one adjustment omits the line, one claim mixes authorized and nonauthorized services, and two lack remittance evidence. 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 Rosa's measures honestly

Initial readiness is 14 of 21, or 66.7%. Nineteen episodes reach valid action or accountable hold, or 19 of 21, or 90.5%. Report initial submissions, front-end rejects, adjudicated denials, paid claims, adjustments, voids, replacements, appeals, recoupments, refunds, and final payments as separate cohorts. Keep every held or failed episode in its declared denominator.

Address the main Pennsylvania risk

The word resubmission can describe different claim states. Using an approved-claim adjustment reference on a rejected claim can send accurate data through the wrong PROMISe path. Preserve whether the referenced ICN was rejected or last approved in the episode.

Test Rosa's workflow against hard cases

Rosa tests an original rejection, a previously approved line, a multi-line claim, missing authorization, a BH-MCO claim, an agency license mismatch, an error-status code, and an overpayment. Each test preserves the starting state, expected route, evidence, observed result, owner, correction, retest, and disposition. A successful portal submission passes only the transmission check; adjudication, remittance, payment, and reconciliation require their own evidence.

Reconcile remittance and cash

Rosa links each payer decision to the remittance and each remittance to the actual deposit, debit, recoupment, refund, or accounts-receivable balance. Partial effects stay open. A new payment does not erase an unresolved prior overpayment, and a zero-dollar remittance is still a claim result that needs review.

Run independent acceptance

Rosa gives an independent reviewer the locked episode list, sources, original claims, clinical evidence, authorization, payer artifacts, selected 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 IBHS PROMISe adjustment episode register

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

Related resources

Sources