How to Resolve CO-50 Denials and Appeal Medical Necessity Claims?

A CO-50 denial means a payer has classified a service as noncovered because it does not consider it medically necessary. The official X12 Claim Adjustment Reason Code list defines CARC 50 this way; “CO” identifies the Contractual Obligation adjustment group.

But does a CO-50 denial always mean the service was medically unnecessary?

No. The code records the payer’s determination; it does not prove that the decision is correct or reveal exactly what triggered it. Noridian’s CO-50 guidance lists a missing diagnosis that supports medical necessity as one possible reason and directs providers to review the medical documentation and applicable Medicare coverage policy.

That distinction matters. A medical necessity denial may involve a coding mismatch, missing evidence, a coverage criterion the record does not establish, or a determination worth challenging. The appropriate response depends on the claim, the supporting clinical documentation, and the payer’s applicable policy.

A CO-50 denial resolution checklist for medical billing teams should therefore start with the full electronic remittance advice (ERA), including any RARC and policy reference, rather than jumping straight to an appeal letter. Let's start by understanding what the remittance says and which details require closer review.

The remittance can provide more than a denial code. An accompanying remark or policy reference may help identify the basis of the payer's decision.

How Can You Verify the Basis of a CO-50 Denial?

To assess whether a CO-50 denial can be challenged, examine the adjustment on the affected service line, review any accompanying remarks, and identify any policy reference supplied with the remittance. These details can point you toward the payer's rationale, but they do not establish whether the determination is correct.

1. Match the Adjustment Details to the Denied Service Line

Record the adjustment group code and CARC 50 separately. Do not treat the combined code as a complete explanation of why the payer denied the service.

The official X12 Claim Adjustment Group Code list defines the adjustment categories. Its Claim Adjustment Reason Code list states that, when present, the ASC X12 835 transaction's Healthcare Policy Identification Segment (Loop 2110 Service Payment Information REF) should be referenced for CARC 50.

Before investigating further, capture the details needed to trace the adjustment:

• The claim identifier, affected service line, and date of service.
• The adjustment group code, reason code, and associated adjustment amount.
• Any policy identifier or reference supplied with the remittance.

These details create a reliable record of what the payer actually reported, rather than relying on a code copied into a denial work queue.

2. Review Accompanying Remark Codes and Policy References

A Remittance Advice Remark Code (RARC) provides additional context for an adjustment or explains remittance processing. The official X12 RARC list defines these messages. Read the actual remark alongside the denial rather than assuming it identifies a specific error or appeal requirement.

For Medicare claims, one remark N115 deserves particular attention when investigating a CO-50 denial. So,

What does N115 mean when it appears with CO-50?

N115 means the decision was based on a Local Coverage Determination (LCD) according to official X12 definition of N115. An LCD provides guidance for determining whether a particular item or service is covered under applicable Medicare rules.

According to Noridian's CO-50 guidance, the billing team should review the medical documentation and check the CMS Medicare Coverage Database for the applicable LCD. N115 identifies the policy basis, but it does not prove that the payer applied the policy correctly.

To support medicare CO-50 LCD diagnosis code validation, capture the details needed to identify the correct policy:

• The exact remark code and its accompanying message.
• Any policy identifier or reference included in the remittance.
• The denied service, date of service, and relevant Medicare contractor.

Use these details to locate the applicable payer medical policy and verify its requirements before deciding whether a medical necessity appeal has a sound basis. Do not assume that every CO-50 denial includes N115 or refers to an LCD.

When teams review uploaded remittance files, Bill Matters' claim denial decoder and document & EOB Processing capabilities can help extract claim-level details and interpret a CARC alongside its paired RARC. This can support the initial review, while the billing team still needs to verify the referenced policy and assess the payer's decision.

What Causes a CO-50 Denial?

A CO-50 denial can occur when a payer determines that a service does not meet its applicable medical necessity requirements. The underlying reason may involve an unsupported diagnosis, missing clinical records, unmet coverage criteria, or a payer determination that does not reflect the information submitted.

Noridian's Medicare Part B guidance identifies a missing diagnosis that supports medical necessity as one possible cause. Other reasons vary by service and applicable payer policy.

1. The Reported Diagnosis Does Not Support the Billed Service

A diagnosis-related issue can trigger a medical necessity denial when the diagnosis reported on the claim does not support the service under the applicable coverage requirements. The issue may concern a missing diagnosis or a diagnosis that does not meet the policy's covered indications.

For example, Noridian's guidance for medicare durable medical equipment claims identifies specific diagnosis or modifier requirements under related Local Coverage Determinations as possible reasons for CO-50.

The discrepancy may involve:

• A missing or unsupported diagnosis code.
• A diagnosis that does not meet the applicable policy's coverage requirements.
• A mismatch between the reported diagnosis and the billed service's coverage criteria.

These are possible coding-related issues, not proof that every CO-50 denial involves an incorrect code.

2. Required Clinical Documentation Is Missing or Insufficient

Insufficient medical necessity documentation can also contribute to a CO-50 denial. A payer may not have enough information to establish that the service meets its coverage requirements, even when the claim includes a diagnosis.

The distinction lies in what information was available to support the determination. Noridian's DME denial guidance identifies several documentation-related circumstances:

• An order required for the billed item is missing.
• Requested supporting records were not received or arrived outside the specified timeframe.
• The available clinical documentation does not establish the required clinical facts.

Missing records and insufficient records are not the same. In the first case, the requested evidence may never have reached the payer. In the second, the submitted information may not establish the relevant requirement.

3. The Service Does Not Meet the Applicable Coverage Criteria

A claim can include a valid diagnosis and supporting records yet still fall outside the payer's coverage requirements. The medical necessity criteria may restrict coverage to particular diagnoses, clinical findings, indications, or service circumstances.

For Medicare, coverage requirements may be defined through a Local Coverage Determination (LCD), a National Coverage Determination (NCD), or other applicable coverage rules. The relevant requirements depend on the service and policy.

For example: Noridian's CO-50 guidance for Medicare DME claims identifies an item that does not meet medical necessity requirements as a possible reason for denial. Its separate denial guidance also identifies services that fall outside Medicare coverage or fail applicable category requirements.

A service may therefore receive CO-50 because the applicable policy does not cover it under the circumstances documented, or because a required coverage condition is not established. The precise reason depends on the policy governing that claim.

4. The Payer's Determination Does Not Reflect the Submitted Evidence

A CO-50 denial may also warrant scrutiny when the payer's stated rationale appears inconsistent with the claim information, clinical record, or applicable coverage requirements. This is a potential explanation, not something the code alone can establish.

For example: the submitted CPT and HCPCS codes, diagnosis information, or clinical records may contain evidence relevant to a coverage requirement that the payer's stated rationale does not appear to account for. A determination may also warrant scrutiny if it relies on a coverage criterion that does not apply to the service.

This is distinct from a genuine documentation gap or an unmet coverage requirement. The concern is that the payer's decision may not accurately reflect the information or rules applicable to the claim.

A CO-50 denial root-cause analysis spreadsheet should preserve these distinctions instead of classifying every case simply as a medical necessity issue. The code identifies the payer's stated reason; it does not establish the exact underlying cause.

Also Read: Why was a Health Insurance Claim Denied? 10 Common Denial Reasons Explained

How Do You Investigate and Resolve a CO-50 Denial?

To investigate and resolve a CO-50 denial, confirm the affected claim, verify the policy that applied to the service, compare the claim against its requirements, and select the appropriate next action. Effective claim denial resolution depends on the facts of the individual claim, not the denial code alone.

1. Establish the Claim and Coverage Context

Start with the specific claim or service line. Confirm the payer, plan, provider details, and date of service. These details establish which coverage rules and claim handling procedures apply.

Keep the following information together before reviewing the applicable requirements:

• Claim and service-line identifiers.
• Payer and plan details, including the relevant Medicare contractor when applicable.
• Date of service and the determination being reviewed.

This context matters because coverage requirements and correction or review procedures can differ across payers and may change over time.

2. Verify the Policy That Applied on the Date of Service

The next step is to establish which coverage rules governed the service when it was provided. So,

How do you find the payer policy relevant to a denied service?

For original Medicare, search the CMS medicare coverage database using the service details and any available policy reference. Check the relevant Local Coverage Determination (LCD), related billing and coding articles, and applicable policy dates. CMS explains that LCDs apply within the jurisdiction of the Medicare Administrative Contractor that issues them.

For commercial claims, consult the payer's current medical policy, provider manual, and applicable plan requirements. Confirm that the policy was effective for the date of service and applies to the service being reviewed.

Do not assume that a policy currently available online governed an older claim. The relevant version and its scope must match the service under review.

3. Compare the Policy Requirements with the Submitted Claim

Once the applicable policy is established, compare its requirements with the information submitted for the claim. The purpose is to determine which requirements the available record supports and whether the payer's determination aligns with them.

Record each relevant criterion using a simple status:

This comparison gives the team a documented basis for choosing the next action. It also helps distinguish a disagreement with the payer's determination from a claim that lacks sufficient support.

4. Choose the Appropriate Resolution Path

The next action should follow from the documented review, not from a standard response applied to every denial.

When should a billing team correct a claim rather than appeal?

• Use a correction process when claim information contains a verifiable error, and the applicable payer rules permit correction.
• Consider an appeal when the provider disputes the determination and can support that position under the relevant coverage criteria.
• If the review remains inconclusive, further investigation may be necessary before either route is appropriate.

For Medicare, the distinction has a specific procedural consequence. CMS's Medicare Claims Processing Manual, Chapter 34 explains that:

• qualifying minor clerical errors and omissions are handled through reopening and redetermination procedures rather than automatically entering the formal appeal process.
• CMS also describes a specific situation involving a CO-50 denial with RARC M127 for missing medical records when the requested records are later submitted with an appeal request, the contractor treats that request as a reopening.

This rule applies to the specified Medicare circumstances, not every missing-documentation denial.

Use the following decision table to distinguish the available routes:

The distinction between a corrected claim and an appeal is procedural, not merely a choice of wording. Follow the relevant payer's instructions rather than assuming that one route applies to all CO-50 denials.

5. Record the Decision, Responsible Owner, and Deadline

Once the team selects a route, document the reason for that decision and assign responsibility for the next action. A clear record helps the team avoid missed handoffs and provides an audit trail of how the claim was handled.

Which deadline applies to a CO-50 appeal?

There is no single deadline that applies to every CO-50 denial. You should:

• check the denial notice, applicable payer rules, and the stage of review
• For Original Medicare fee-for-service redeterminations, CMS specifies a 120-day period from receipt of the initial claim determination
• CMS generally presumes receipt five calendar days after the notice date unless evidence indicates otherwise. Commercial payer and other program deadlines may differ.

For claims proceeding to an appeal, a CO-50 appeal submission tracking template can record the selected route, assigned owner, submission deadline, submission date, confirmation, and follow-up status.

Consistent records also support medical billing denial management by making responsibility and pending actions clear across the team. The goal is to ensure that every reviewed claim has a documented decision and an accountable next step.

Also Read: How to Appeal Utilization Review Denials Under State Rules

How Do You Prepare an Evidence-Backed Appeal for a CO-50 Denial?

To prepare a strong CO-50 denial appeal, identify the payer’s specific reason for denial, connect it to the applicable medical necessity criteria, and support your argument with relevant clinical records. The appeal should explain how the documented evidence addresses the disputed requirement and why the payer’s determination warrants reconsideration.

1. Connect the Denial Rationale to the Specific Coverage Criterion

An appeal should challenge the actual basis of the determination, not simply restate the provider's position. Identify the disputed requirement and explain how the available evidence addresses it.

The argument should establish three clear connections:

• Payer's rationale: What specific aspect of medical necessity did the payer question?
• Applicable requirement: Which coverage criterion is relevant to that concern?
• Supporting evidence: What documented fact supports the provider's position?

For example: if the payer questions whether the record establishes a particular clinical finding, the appeal should identify the applicable requirement and cite the record containing that finding. A broad statement that the treatment was necessary does not establish that connection.

2. Select Clinical Records That Support the Appeal

Once the argument is clear, the next task is selecting records that substantiate it.

Which clinical records are most relevant to a medical necessity appeal?

The most relevant records are those that directly support the disputed medical necessity criteria under the applicable policy. Their relevance depends on the service, the payer's rationale, and the specific facts the provider needs to establish.

Depending on the case, supporting evidence may include:

• Progress notes documenting symptoms, examination findings, functional limitations, or clinical status.
• Relevant diagnostic reports, test results, or imaging findings.
• Treatment plans, orders, or documented treatment history when the applicable criteria require them.
• Records supporting the reported diagnosis and the diagnosis-to-procedure relationship.

Do not attach records simply because they are available. A record should have a clear purpose in the appeal. If the documentation does not support a required criterion, the letter should not claim otherwise.

3. Build the Appeal Argument Around Verifiable Evidence

The appeal letter should turn the evidence into a clear explanation of why the determination warrants review.

What should a medical necessity appeal explain to the payer?

A medical claim appeal letter should identify the determination being challenged, state the basis for disagreement, connect relevant clinical evidence to the applicable coverage criteria, and specify the review or outcome being requested.

A useful way to organize the supporting argument is an evidence-to-policy matrix. This is a practical preparation tool, not an official payer form.

This matrix helps keep the appeal grounded in the record. It also makes gaps visible before the letter is finalized.

Our experience from building Bill Matters reinforces why this matters. Appeal generation is not simply a matter of turning a denial code into a polished letter. The difficult part is establishing a defensible connection between the payer's rationale, the applicable rule, and the evidence available for that particular claim.

That principle informs Bill Matters' multi agent AI workflow for appeal preparation. It analyzes the denial rationale, applicable policy, and claim records to identify relevant evidence and gaps. Its billing evidence finder organizes supporting documentation and then drafts an evidence-backed appeal while keeping the draft for quality checks before human review and submission.

Also Read: How to Write a Medical Necessity Appeal Letter

4. Check the Appeal for Accuracy and Completeness

Before submission, review the draft against the underlying records. The aim is to ensure that every material assertion is supported and that the package addresses the determination being challenged.

CMS's official guidance for the first-level Original Medicare fee-for-service redetermination instructs appellants to identify the specific service and date of service, explain why they disagree with the determination, and include supporting documentation. Other payers may have different forms and submission requirements.

The final review should confirm that:

• Every clinical statement matches the source record.
• Policy references apply to the service and relevant date.
• Supporting documents are consistent with the appeal's claims.
• Required forms and attachments are present.
• An authorized reviewer has checked the package before submission.

The goal is not to make the letter sound more persuasive than the evidence allows. It is to make the argument clear, traceable, and supported by the facts.

How Can RCM Teams Use CO-50 Denial Outcomes to Reduce Repeat Denials?

RCM teams can reduce repeat CO-50 denials by tracking final claim outcomes, comparing patterns across payers and services, and using verified findings to improve upstream reviews. A recurring denial pattern is a signal worth investigating, not proof that every affected claim has the same underlying cause.

1. Track the Final Outcome of Each Denial

Recording that a claim was appealed is not enough. Teams need to know what happened after the appeal and whether the claim ultimately resulted in payment, a partial payment, or an upheld denial.

A consistent appeal outcome tracking and audit trail should connect each case's original denial with its final disposition. Where the information is available, record:

• Whether an appeal was submitted and the date of submission.
• The payer's decision, including whether the denial was upheld, reversed, or partially overturned.
• Any resulting payment adjustment and the amount recovered.
• The time between the initial denial and the final outcome.

These records help distinguish appeals that recover payment from those that do not. They also give managers a more useful view of recovery performance than the number of appeals submitted alone.

2. Compare Outcomes Across Payers and Services

Once outcome data accumulates, denial root-cause analysis can help teams identify patterns that deserve further examination. The comparison should go beyond counting denials and consider whether particular payers, services, or claim groups show recurring outcomes.

Useful comparisons include:

• Denial and appeal outcomes by payer and service or procedure.
• Reversal patterns associated with Claim Adjustment Reason Code (CARC) 50.
• Payer response times and recovery amounts, where available.
• Recurring patterns in the diagnosis-to-procedure relationship across affected claims.

For example, if one payer repeatedly denies a particular service but reverses a substantial share of those denials on appeal, the pattern may warrant a closer review. It does not, by itself, prove that the payer made an error or that every similar claim should be appealed.

Bill Matters' Payer Insights addresses this analysis at the payer level. While building Bill Matters, we treated payer-specific patterns as distinct from overall averages. Its payer insights workflow tracks denial patterns, response times, and recovery outcomes separately for each payer, helping teams spot recurring issues that individual claim reviews may not reveal.

3. Use Verified Patterns to Improve Future Reviews

Tracking becomes useful when teams act on findings that have been validated. If a recurring pattern points to an issue with documentation, coding, or a payer-specific requirement, the relevant team can examine that pattern and decide whether an upstream review needs to change.

This makes denial prevention more targeted. Instead of applying the same intervention to every CO-50 denial, teams can focus on recurring issues supported by their own claim and outcome data.

For RCM head and denial specialists considering denial management workflow automation for repeated CO-50 denials, the key is to connect payer-level patterns with actual outcomes. A dashboard that counts denials is less useful than a workflow that helps teams understand which patterns recur, what happens when they are appealed, and where further review is justified.

After a process change, continue tracking outcomes to determine whether the pattern changes. Do not assume that an intervention worked simply because it was introduced.

Make Every CO-50 Decision Count

A CO-50 denial is an opportunity to bring greater clarity and accountability to claim decisions. The work behind Bill Matters has reinforced a key lesson: a credible medical necessity denial appeal process depends on sound reasoning, reliable evidence, and careful review, not persuasive wording alone. It reflects this evidence-led approach to appeal preparation. For billing teams, doctor practices and practice owners, maintaining that standard means treating every claim as a decision that must be defensible, with the applicable appeal filing deadline and supporting records properly accounted for.

Works Cited (information last verified October 26, 2026)

Centers for Medicare & Medicaid Services. “Chapter 34: Reopening and Revision of Claim Determinations and Decisions.” Medicare Claims Processing Manual, rev. 4219, 25 Jan. 2019, https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/clm104c34

Centers for Medicare & Medicaid Services. “First Level of Appeal: Redetermination by a Medicare Contractor.” CMS.gov, https://www.cms.gov/medicare/appeals-grievances/fee-for-service/first-level-appeal-redetermination-medicare-contractor

Centers for Medicare & Medicaid Services. “MCD Search.” Medicare Coverage Database, https://www.cms.gov/medicare-coverage-database/search.aspx

Noridian Healthcare Solutions, LLC. “Medical Necessity/No Payable Diagnosis.” Noridian Medicare, 30 Apr. 2025, https://med.noridianmedicare.com/web/jeb/topics/claim-submission/reason-code-guidance/med-nec-no-pay-dx

Noridian Healthcare Solutions, LLC. “Reason Code 50.” Noridian Medicare, 6 June 2025, https://med.noridianmedicare.com/web/jadme/topics/ra/denial-resolution/50

Noridian Healthcare Solutions, LLC. “Reason Code 50 | Remark Code N115.” Noridian Medicare, 15 Dec. 2023, https://med.noridianmedicare.com/web/jadme/topics/ra/denial-resolution/n115-50

X12. “Claim Adjustment Group Codes.” https://x12.org/codes/claim-adjustment-group-codes

X12. “Claim Adjustment Reason Codes.” https://x12.org/codes/claim-adjustment-reason-codes

X12. “Remittance Advice Remark Codes.” https://x12.org/codes/remittance-advice-remark-codes