Claim rejection triage before resubmission

Why the first retry matters

A rejected claim is usually not solved by pressing submit again. The first useful step is to decide what kind of problem the adjudicator is describing. Identity errors, eligibility errors, timing errors, quantity limits, coordination failures, and documentation edits all require different responses. Treating them as the same problem wastes time and can create a confusing claim history.

A practical triage approach starts with the least clinical information first. Confirm the carrier, group, certificate number, relationship code, date of birth, and patient name. These are not glamorous checks, but they often explain a claim that appears to be a coverage problem. A single missing suffix, an old group number, or a card copied from the health side instead of the drug side can make the rest of the response meaningless.

Once identity is clean, the pharmacy can decide whether the rejection is about eligibility, timing, quantity, coordination, product coverage, or clinical review. That classification should be recorded in the note if the pharmacy takes an action beyond simple data correction.

A useful order of operations

Identity should be confirmed before coverage. Coverage should be confirmed before intervention codes. Intervention codes should be considered only after the pharmacy understands why the claim failed and why the selected action is appropriate.

For timing edits, the key question is whether the service date, previous fill date, day supply, or patient possession calculation is wrong. For quantity edits, the question is whether the submitted quantity matches the product package, the prescription, and the plan limit. For coordination edits, the question is whether the right payor is being billed in the right order.

When a plan asks for a specific document, authorization, or exception process, repeating the claim rarely helps. The next task is usually prescriber contact, patient instruction, manual submission, or plan help desk confirmation.

What to document

Documentation should explain the reason for the action, not merely the code used. A note that says “MV used” is weaker than a note that says the patient is travelling outside the province from a stated date to a stated date and requires supply to cover the absence. A note that says “duplicate override” is weaker than a note explaining that two strengths are intentionally being used to make a prescribed dose.

The goal is not to write a novel. The goal is to leave enough context that another pharmacist, an auditor, or the same pharmacy six months later can understand why the claim was submitted the way it was.