OA-B22: Payment Adjusted Based on Diagnosis

What Does OA-B22 Mean?

OA-B22 appears in coordination of benefits scenarios where the diagnosis-based adjustment interacts with multiple payer rules. Financial responsibility may not be clearly assigned when different payers have different diagnosis coverage criteria for the same procedure.

CARC B22 is a diagnosis-driven payment adjustment. The payer reviewed the ICD-10 diagnosis code on the claim and determined it does not meet the criteria for the billed service. This could mean the diagnosis does not support medical necessity for the procedure, the diagnosis code is incorrect or insufficiently specific, or the diagnosis-procedure pairing violates the payer's Local Coverage Determination (LCD) or National Coverage Determination (NCD) policies.

Unlike coding error denials that focus on procedure codes, B22 specifically targets the diagnosis side of the equation. The procedure code may be perfectly valid, but if the supporting diagnosis does not justify the service under the payer's rules, the payment is adjusted. Common examples include billing a screening test with a diagnosis code for an established condition (which changes the payment rate), using an unspecified diagnosis when the payer requires a specific ICD-10 code to the highest level of detail, or submitting a procedure that is only covered for certain diagnoses.

B22 appears with CO when the diagnosis-procedure mismatch is a coding issue the provider must absorb. Under PR, the diagnosis may indicate a non-covered condition where the patient bears the cost. Either way, resolution starts with comparing the diagnosis code on the claim against the medical record documentation and the payer's coverage rules. If the diagnosis was coded incorrectly, a corrected claim resolves the issue. If the diagnosis is correct but the payer disagrees on medical necessity, a clinical appeal is the next step.

How to Resolve

Verify the diagnosis code accuracy and payer coverage rules, then resubmit with corrected coding or appeal with medical necessity documentation.

1. Check coverage across payers Verify whether any of the patient's payers cover the procedure for the documented diagnosis.
2. Redirect the claim Submit to the payer whose coverage rules accept the diagnosis-procedure pairing.

Common RARC Pairings

The RARC code tells you exactly what triggered the OA-B22:

How to Prevent OA-B22

• Verify diagnosis-specific coverage with all payers in the patient's coverage chain before rendering services

General Prevention

• Ensure diagnosis codes are specific, current, and accurately reflect the patient's documented condition at the highest level of ICD-10 specificity
• Review payer-specific LCD/NCD policies before billing to verify the diagnosis supports the procedure's medical necessity
• Implement coding edit software that flags diagnosis-procedure mismatches before claim submission
• Train coders on accurate ICD-10 code selection and the importance of diagnostic specificity
• Conduct regular coding audits to identify patterns of diagnosis-related denials

Also Filed As

The same CARC B22 may appear with different Group Codes:

Related Denial Codes