CO-12: Diagnosis Inconsistent with Provider Type
Provider responsibility — correct the issue and resubmit the claim. The patient is not liable for this amount.
What Does CO-12 Mean?
With CO (Contractual Obligation), the CARC 12 adjustment is the provider's responsibility. The payer denied or reduced payment because of the diagnosis code is not typically within the scope of practice for the billing provider's specialty. The patient is not liable for this amount. If the denial is in error, the provider can correct and resubmit the claim or file an appeal with supporting documentation.
CARC 12 appears on a remittance when the payer identifies an issue related to diagnosis inconsistent with provider type. This is a technical billing or coding problem that must be corrected before the claim can be processed for payment. The denial indicates the claim data did not meet the payer's adjudication requirements.
Common scenarios that trigger this adjustment include: the diagnosis code is not typically within the scope of practice for the billing provider's specialty; Provider taxonomy code on file with payer does not match the type of diagnosis being treated; Incorrect rendering provider NPI listed, causing specialty mismatch. The group code paired with CARC 12 determines who bears the financial responsibility — CO places it on the provider as a contractual obligation, OA indicates a coordination of benefits or other payer adjustment, PR shifts it to the patient.
Common Causes
| Cause | Frequency |
|---|---|
| Diagnosis outside provider's scope The diagnosis code is not typically within the scope of practice for the billing provider's specialty | Most Common |
| Incorrect provider taxonomy Provider taxonomy code on file with payer does not match the type of diagnosis being treated | Common |
| Wrong rendering provider Incorrect rendering provider NPI listed, causing specialty mismatch | Common |
| Credentialing data outdated Provider's specialty or taxonomy not updated with the payer | Occasional |
How to Resolve
- Review the remittance details Examine the CO-12 adjustment and any accompanying RARC codes to identify the specific reason for the denial.
- Identify the root cause Determine which issue applies: diagnosis outside provider's scope, incorrect provider taxonomy, wrong rendering provider, among others.
- Correct the claim Address the identified issue — update the claim data in your billing system to resolve the diagnosis inconsistent with provider type problem.
- Resubmit the corrected claim Submit the corrected claim following the payer's resubmission guidelines. Include any supporting documentation that addresses the denial reason.
- Appeal if the original claim was correct If the provider is qualified and the diagnosis is within their scope, appeal with credentialing documentation, board certifications, and clinical records. Resubmission with corrected NPI is faster for data errors.
If the provider is qualified and the diagnosis is within their scope, appeal with credentialing documentation, board certifications, and clinical records. Resubmission with corrected NPI is faster for data errors.
Common RARC Pairings
The RARC code tells you exactly what triggered the CO-12:
| RARC | Description |
|---|---|
| N290 | Missing/incomplete/invalid rendering provider information Update provider taxonomy or NPI → |
| MA130 | Missing/incomplete/invalid information can be resubmitted Correct provider data and resubmit → |
How to Prevent CO-12
- Keep provider taxonomy codes current with all payers
- Verify rendering provider matches the diagnosis treated
- Train billing staff on provider-diagnosis scope requirements
- Implement pre-submission edits for provider-diagnosis validation
- Regularly audit provider credentialing data
Also Filed As
The same CARC 12 may appear with different Group Codes:
Related Denial Codes
Sources
- https://x12.org/codes/claim-adjustment-reason-codes
- https://revenuecyclemgmt.com/claim-adjustment-reason-codes/
- https://www.rivethealth.com/blog/carcs-rarcs-claim-adjustment-remittance-advice-codes
- Codes maintained by X12. Visit x12.org for official definitions.