PR-242 Denial Code Explained: Causes, Solutions, and Prevention in Medical Billing

PR-242 denial code is a network compliance denial code, indicating that services were rendered by a provider who is out of network or out of primary care requirements for the patient's insurance plan. The prefix “PR” represents Patient Responsibility. This indicates that at last, it is the patient who has to bear the cost of this service that has been denied. There is a direct correlation between billing teams’ accountability, patient responsibility, and revenue recovery.

‍

In this article, we will discuss what a PR-242 denial code is, its comparison with other denials, and what causes it. Most importantly, we will discuss how it can be resolved.

‍

What is a PR-242 Denial Code?

‍

The official definition of Claim Adjustment Reason Code (CARC) 242 under the X12/CMS Claim Adjustment Reason Code list is: "Services not provided by network/primary care providers." The PR (Patient Responsibility) group code prefix indicates that the balance is deemed to be the patient's responsibility and is not a contractual provider write-off or responsibility on the part of the payer.

‍

For a claim to be denied with a PR-242 Reason Code, a service is rendered to a patient by a healthcare provider who is not within the patient's insurance network or who is not an approved provider under the patient's health insurance plan's primary care requirements. The claim is then denied by the insurance company, leaving it up to the healthcare provider to make a decision regarding whether to collect from the patient or to appeal the decision.

‍

Comparison: PR-242 vs Similar Denial Codes

‍

PR-242 is one of several denial codes that involve network compliance, authorization, or coverage scope issues. Understanding how it differs from similar codes is essential for routing the denial to the correct resolution path and determining financial responsibility accurately.

Common Causes of PR-242 Denials

‍

The common causes of PR-242 denials always point back to the front end of the patient service. Knowing the common causes of PR-242 denials will allow billing teams to develop strategies to prevent them.

‍

Out-of-Network Provider Renders Services Without Patient Awareness

The most basic cause of the PR-242 denial is the fact that the provider or facility is out of network, and the patient was unaware of it before the provider or facility provided the service. 

‍

Missing or Invalid PCP Referral for Specialist Services

A patient self-referred to the provider or facility. A patient's referral was received by the provider or facility but expired before the patient received the service. A patient was referred by a provider who was not the patient's designated PCP for that plan year. 

‍

Provider Credentialing Gaps and Roster Delays

During the provider enrollment and credentialing window period, claims will be denied as PR-242 if the provider or facility is new and has an NPI, and the patient has an HMO or EPO.

‍

Cross-Plan Coverage Errors

If the billing team bills under the old plan and the patient is now covered by an HMO plan where the provider is out of network, then PR-242 is generated. 

‍

No Surprises Act Compliance Failures

The No Surprises Act is now effective as of January 2022. The law has imposed stringent consent and notification requirements before billing patients for non-emergency out-of-network services. For providers who work within a facility that has a high likelihood of mixed network situations, such as emergency department physicians within a hospital setting, failure to provide a Good Faith Estimate or obtain patient consent for out-of-network billing can result in a violation of NSA compliance as well as trigger denials for PR-242. NSA compliance is now synonymous with PR-242 compliance. 

‍

Incorrect Provider NPI or Taxonomy Code on the Claim

Incorrect billing practices that result from administrative billing errors, billing under a different provider's NPI, billing under a group's NPI for a provider who is not part of that group's out-of-network contract, or incorrect taxonomy codes that are not covered by a provider's classification can trigger a PR-242 denial despite the provider being technically within a network.

‍

Failure to Verify Network Status Before Service

Perhaps the most avoidable cause is the failure of the front desk and billing teams to verify the patient's network status for a specific payer-plan combination before scheduling the patient's service. This is the cause for PR-242 on a large scale, where the plan type and product are unknown.

‍

Steps To Appeal a PR-242 Denial

Not all PR-242 denials are final, and not all are accurate. There are several common errors that cause a PR-242 denial, and a structured appeal process will give your office the best opportunity for successful recovery.

‍

1. Verify the Details of the Denial and Obtain a Copy of the Full EOB

Carefully examine the entire Explanation of Benefits or Electronic Remittance Advice. Check the reason for the denial, which is PR-242. Look for any remark codes that may be associated with the denial, such as M80, N30, and MA130. Look for the date of service, the rendering provider's NPI, and the type of plan. These remark codes will assist in determining the reason for the denial, whether it is a referral that expired, a specific exclusion, or a credentialing problem.

‍

2. Verify the Actual Status of the Provider's Network

Log in to the payer's provider portal and search for the NPI under the type of plan, not the payer in general. HMO vs. PPO is significant. Confirm that the dates match those on file. If in-network, but incorrectly denied, a corrected processing can be requested based on the contract date and credentialing information.

‍

3. Check for a Valid Referral or Authorization

In the case of HMO and POS plan denial claims, the patient referral documents must be obtained. This includes checking to see if a referral existed, if the referral was from the patient's assigned PCP for the plan, if the referral was for the specific type of service rendered, and if the referral was valid for the date services were rendered. If a referral existed, a technical error may have occurred on the referral. A call to the patient's PCP must be made to request a new referral, and the claim resubmitted with the new referral.

‍

4. Investigate Retroactive Authorization Eligibility

Payers may allow a retroactive authorization for services if the denial was a result of an administrative error, especially for established patients and in urgent situations. A retroactive authorization must be requested from the payer within a specific window, usually 30-60 days from the date of service, and must be accompanied by a letter from the patient's physician explaining the medical necessity for the services.

‍

5. Assess No Surprises Act Protections

For emergency services or situations where the patient did not select the out-of-network provider (such as an out-of-network anesthesiologist or radiologist in an in-network facility), determine whether NSA protection is applicable to prohibit balance billing to the patient. If NSA protection is applicable, then IDR should be initiated with the payer rather than billing the patient because IDR has the potential to result in a much higher payment to the provider than the initial denial from PR-242.

‍

6. File Formal Appeal and Supporting Documentation

If the denial appears to be incorrect or if clinical extenuating circumstances support an exception to the policy, initiate the formal appeal within the timeframe established by the payer. This timeframe is generally between 60 and 180 days for commercial payers and 120 days for Medicare. Include the following supporting documentation in the appeal package: cover letter explaining the rationale for the appeal, provider credentialing and network contract documentation, referral documentation if applicable, clinical documentation supporting medical necessity of the service provided, and any retro-authorization approval that was obtained. 

‍

7. Communicate With the Patient Transparently

If the denial is due to a valid out-of-network encounter and cannot be recouped through the appeal/retro-auth process, the patient must be contacted and notified. A payment plan must be presented to the patient. This proactive communication will significantly lower the number of patient disputes and boost the percentage of payments received compared to sending the patient a bill without any context. 

‍

8. Log Root Cause and Update Prevention Workflows

Each time a PR-242 denial is resolved, the root cause of the denial must be recorded. Was the denial caused by a lag in the credentialing process? A lack of a referral? A lack of a plan-type verification? Every time a denial is resolved, it must flow back into the prevention workflow to prevent the same denial from occurring the following month. With the automated solution, the denial data is converted into process intelligence.

‍

How To Prevent PR-242 Denials

‍

The only way to eliminate both the cost and patient experience impact of PR-242 denials is through prevention. This is because, unlike other types of denials that result from documentation issues, which can be corrected after the fact, PR-242 denials are, in fact, pre-service denials, and the network status issue exists prior to the patient's service. This means that prevention must occur before the patient service occurs.

‍

Front-End Prevention

‍

• Plan-Specific Network Verification at Every Scheduling Call
• Referral Verification as a Scheduling Gate for HMO/POS Patients
• Proactive Patient Notification of Out-of-Network Status

Billing Best Practices

‍

• Maintain the current provider-payer network matrix
• Monitor new provider credentialing timelines actively
• Implement an annual open enrollment PR-242 surge protocol
• Audit claims for NPI and taxonomy accuracy before submission:
• Familiarize the team with the No Surprises Act obligations

‍

Technology Solutions

‍

The sheer volume and variety of network participation data, including dozens of payers, multiple types of plans, and multiple providers, create an inconsistent and unreliable method for manual prevention of PR-242 denials. For medical practices that are serious about eliminating PR-242 denials, technology is not optional. RapidClaims has developed a solution that addresses all facets of PR-242 prevention with our integrated RCM solution.

‍

Final Thoughts

‍

Of all the denial codes in medical billing, PR-242 is arguably one of the most operationally disruptive and patient relationship-damaging. It is also arguably one of the most preventable. At every level, every reason that leads to a PR-242 denial is related to front-end issues: network status not being verified, referrals not being confirmed, new providers not being tracked, and patient plan types not being updated and consequently not being re-verified. There is nothing in any of these scenarios that is not preventable. There is nothing in any of these scenarios that cannot be addressed with the right combination of workflow and technology.

‍

Practices that have effectively reduced their percentage of denied claims related to PR-242 to essentially zero have one thing in common: they have effectively combined front-end verification workflows with technology that enables those workflows. RapidClaims provides exactly that: front-end verification, referral and authorization, credentialing lag, and denial pattern analysis, all in one platform. 

‍

FAQs

‍

1. What is the PR-242 denial code description?

PR-242 denial code states that the service was not provided by an in-network or primary care provider, or lacked proper referral/authorization, making it the patient’s responsibility.

‍

2. What does the PR-242 reason code mean in medical billing?

PR-242 means the service was not covered because it was out-of-network or lacked the required referral/authorization, and the cost is the patient's responsibility.

‍

3. What is the CO-242 denial code description?

The CO-242 denial code description states that the service was denied because the patient’s insurance coverage is no longer active.

‍

4. Who is financially responsible for a PR-242 denial code?

The patient is financially responsible in cases of a PR-242 denial code because the insurance policy was no longer active.

‍

5. How can providers prevent PR242 or CO-242 denial codes?

The PR242 or CO-242 denial code can be prevented by verifying whether the patient’s insurance coverage is active or not.

‍