The PR-242 denial code appears on your 835 Electronic Remittance Advice as a pairing of two separate code components. PR is the Claim Adjustment Group Code, which X12 designates as Patient Responsibility.
The number 242 is the Claim Adjustment Reason Code (CARC), which X12 officially defines as “Services not provided by network/primary care providers.” CARC 242 has been active since January 1, 1995.
The CARC list status was last reviewed May 1, 2026, confirming CARC 242 remains unchanged and active.
When PR-242 appears on your remittance, the payer has determined that the service was rendered outside the patient’s network or primary care requirements, and the patient is responsible for the balance.
You can bill the patient for a PR group code adjustment after verifying the denial is accurate.
In 2026, UnitedHealthcare’s January 1 referral requirement for Medicare Advantage HMO and HMO-POS plans went fully into operational effect after the grace period expired on April 30, 2026.
Practices that haven’t updated their referral intake workflows are generating preventable pr 242 denial code denials right now.
This guide covers the official X12 definition, every root cause, the RARC crosswalk, the No Surprises Act compliance layer, and a seven-step resolution workflow.
This article is written for medical billers, AR specialists, and practice managers working PR-242 denials on managed care remittances right now.
What Is the PR-242 Denial Code? The Official X12 Definition and CARC History
The Official X12 Definition of CARC 242
“Services not provided by network/primary care providers.”
That is the complete official X12 definition of CARC 242. X12 (the American National Standards Institute-chartered body that maintains all HIPAA-mandated claim adjustment codes) is the sole authoritative source for this definition.
CARC 242 has been active since January 1, 1995. The CARC list was last reviewed May 1, 2026, and the code list was last modified November 1, 2025, confirming CARC 242 is active and unchanged.
See the X12 CARC official list for the complete active CARC list maintained by X12.
“Services not provided by network/primary care providers” means the payer has determined that the rendering provider doesn’t meet the patient’s plan requirements for covered care. The denial isn’t saying the service was medically unnecessary.
It’s not saying the service was a coding error. It’s saying the provider who delivered the service wasn’t the right provider under the patient’s network rules.
Like the PR-27 denial code, the PR prefix confirms the patient owes the balance on the remittance. The pr-242 denial code description falls under the Patient Responsibility group code, which means the adjustment is the patient’s financial obligation, not a provider write-off.
How PR-242 Appears on Your 835 ERA and EOB
PR-242 appears in the CAS (Claim Adjustment) segment of the 835 transaction. CAS01 is the group code (PR). CAS02 is the reason code (242). CAS03 is the adjustment dollar amount. Your billing software combines these and displays them as “PR-242” on your denial report or remittance summary.
On a paper EOB, it appears as “PR 242” or “PR-242” in the denial code column with payer-specific description language such as “Services not provided by network/primary care providers” or “Out-of-network provider.” The format differs by payer.
The meaning is identical across all payers using the X12 835 transaction standard.
The pr 242 remark code accompanying this denial on your remittance tells you what to investigate next, which the RARC crosswalk in Section 6 covers in detail.
The denial code pr 242 appears in this CAS segment format on every remittance that uses the X12 835 standard, regardless of payer. If you’re seeing different display formats across payers, the underlying code and financial consequence are the same.
CARC 38 Was Deactivated and Split Into CARC 242 and CARC 243
X12’s CARC records show that an older code, CARC 38, previously read: “Services not provided or authorized by designated (network/primary care) providers.” This combined code was deactivated and replaced by two more operationally precise codes.
CARC 242: “Services not provided by network/primary care providers.” This covers who rendered the service.
CARC 243: “Services not authorized by network/primary care providers.” This covers the authorization and referral pathway.
This split matters operationally. PR-242 sends your team to investigate network status, provider enrollment, and patient eligibility. PR-243 sends your team to investigate authorization records and referral documentation.
These are different people in most billing departments investigating different systems. Routing PR-242 to the PR-243 workflow wastes time on the wrong investigation.
The old CARC 38 language (“not provided or authorized”) is why some legacy EOB documents and older payer systems (including Alabama Medicaid’s EOB crosswalk) still display the combined phrase.
If you’re seeing that phrasing on an older remittance, it’s CARC 38 language. Current claims use CARC 242 or CARC 243 separately.
The pr 242 denial code descriptions you encounter today on current remittances are the post-split version only.
These descriptions appear differently by payer but the X12 CARC 242 definition is the authoritative source behind all pr 242 denial code descriptions in use.
Can You Bill the Patient for a PR-242 Denial?
Yes. When a PR group code accompanies CARC 242 on your remittance, the patient is responsible for the denied balance. You can bill the patient for a pr-242 denial. That’s not optional guidance. That is the X12 standard for Patient Responsibility codes.
This is the fundamental difference between PR-242 and CO-242. CO group codes (Contractual Obligation) assign the adjustment to the provider, who absorbs the write-off and can’t bill the patient. PR group codes assign the adjustment to the patient.
PR-242 = patient statement. CO-242 = provider write-off. They’re not interchangeable. When the CO-197 denial code appears, the provider absorbs the write-off. When the denial is PR-242, the patient owes the balance.
See the CMS group code financial responsibility guidance for the official CMS breakdown of group code financial assignment.
When PR-242 Definitively Means the Patient Owes the Balance
Scenario 1: Out-of-network provider on a restrictive plan. The patient went out of network on a plan that restricts coverage to in-network providers. The denial is accurate. The patient chose an out-of-network provider. The patient owes the balance. Generate the patient statement after verifying the denial.
Scenario 2: Self-referral on an HMO plan. The patient self-referred to a specialist on an HMO plan that requires PCP gatekeeper referrals. No referral existed. The denial is accurate. The patient bypassed the plan’s referral requirement. The patient owes the balance.
Scenario 3: Invalid referral source. The referral was issued by a provider who isn’t the patient’s designated PCP for the current plan year. The referral is invalid under plan rules. The denial is accurate. The patient owes the balance.
The Three Situations Where You Must Verify Before Billing
Situation 1: NSA remark codes accompany the denial. The PR-242 denial came with RARC N862, N878, or N879. These codes signal the No Surprises Act applies to this claim. If the service was emergency care or a non-emergency service at an in-network facility, patient cost-sharing can’t exceed the in-network level. Billing the patient for the full PR-242 balance without checking NSA remark codes is a compliance violation.
Situation 2: The denial may be a payer error. The provider was technically in-network but the claim was billed under the wrong NPI or taxonomy code. The denial may be a payer system error, not a legitimate network violation. Billing the patient for a correctable payer error costs patient trust and creates collections disputes.
Situation 3: Secondary insurance hasn’t been checked. The patient’s secondary insurance may cover part or all of the out-of-pocket balance before the patient statement goes out. Billing the patient before checking secondary insurance status is a billing sequence error.
One O Seven RCM’s billing team runs a three-point compliance check on every denial code pr 242 before a patient statement is generated, which means your patients don’t receive incorrect bills and your practice doesn’t create compliance exposure from legitimate errors.
PR-242 vs PR-243 vs CO-242: How to Tell These Codes Apart Before You Take Action
Four denial codes carry CARC 242 or 243 in medical billing. Each one changes financial responsibility, resolution path, and whether the patient can be billed. Getting the code wrong doesn’t just route the denial incorrectly.
It can mean billing a patient who shouldn’t pay or writing off a balance the patient actually owes. These pr 242 denial code descriptions are distinct at the group code level.
See the X12 CARC official list for the authoritative definitions confirming that all four codes below are X12-sourced and not payer-specific variations.
The Four-Code Comparison Table
| Code | Official X12 Description | Group Code Meaning | Who Owes | Resolution Path | Common Mistake |
|---|---|---|---|---|---|
| PR-242 | “Services not provided by network/primary care providers.” | Patient Responsibility | Patient | Verify network status. Generate patient statement after NSA check. Bill patient if denial is accurate. | Writing off as CO denial and not billing patient at all. |
| PR-243 | “Services not authorized by network/primary care providers.” | Patient Responsibility | Patient (in most scenarios) | Verify referral and authorization records. Patient may owe if authorization failure was their responsibility. | Treating PR-243 as the same denial as PR-242 and following network status investigation instead of auth investigation. |
| CO-242 | “Services not provided by network/primary care providers.” | Contractual Obligation | Provider absorbs. No patient billing. | Review managed care contract. Verify network status. Post contractual write-off if denial is accurate. | Billing patient for a CO group code adjustment. This is a compliance violation. |
| PI-242 | “Services not provided by network/primary care providers.” | Payer Initiated | Payer-initiated adjustment. Neither provider nor patient is automatically responsible. | Contact payer for clarification before any action. | Treating PI-242 as CO-242 and posting a write-off without investigating. |
CO-242 and PR-242 carry the same CARC number but opposite financial implications. billingfreedom.com defines CO-242 as a medical necessity denial and rapidclaims.ai defines it as a coverage termination denial.
Both definitions are factually wrong per the official X12 CARC list. The CO-24 denial code is a separate managed care coordination code that billers sometimes confuse with CO-242.
Why PR-242 and PR-243 Need Different Resolution Workflows
PR-242 investigates who rendered the service. PR-243 investigates who authorized the service. These are two different questions requiring two different investigations by two different people in most billing departments.
PR-242 investigation: Log into the payer’s provider portal and verify the rendering provider’s NPI under the specific plan type (HMO, PPO, EPO) on the date of service. Confirm the patient’s plan assignment and PCP designation.
PR-243 investigation: Pull authorization records and referral documentation. Verify whether the patient’s PCP issued a valid referral, whether the referral covered the specific CPT code and date, and whether the authorization number was included on the claim. When the authorization pathway is the issue, see the CO-197 denial code for the authorization failure comparison.
Routing PR-242 to the PR-243 workflow means investigating authorization records for a denial that’s actually about network status. The investigation fails. The appeal fails. The revenue is lost.
Common Reasons for PR-242 Denials: Six Root Causes and What They Mean for Your Workflow
Identifying the root cause of your PR-242 denial determines whether you generate a patient statement, investigate a payer error, appeal with documentation, or update your credentialing records.
Getting the pr 242 denial code reason wrong means working the wrong resolution path and potentially billing a patient for a denial that should have been corrected and resubmitted.
Cause 1 — Out-of-Network Provider Status
The most common cause. The rendering provider isn’t contracted with the patient’s specific insurance plan on the date of service. When a patient’s plan restricts coverage to network providers, services from out-of-network providers trigger PR-242 because the provider doesn’t meet the plan’s network requirements for covered care.
“In-network with the payer” doesn’t guarantee “in-network for every plan product that payer administers.” HMO, PPO, and EPO products within the same payer can have completely different network panels.
Confirm network status against the specific plan product, not the payer name. Our payer credentialing and enrollment services resolve persistent out-of-network PR-242 patterns at the contract level.
Cause 2 — UHC 2026 Plan Year Reset and Referral Expiration
This is the most urgent 2026-specific cause for pr 242 denial code unitedhealthcare situations and no competitor mentions it.
Effective January 1, 2026, UnitedHealthcare requires PCP referrals for all Medicare Advantage HMO and HMO-POS specialist visits, per UHC provider document PCA-1-25-02706-M&R (December 2025).
The grace period during which claims wouldn’t be denied for missing referrals ended April 30, 2026.
As of May 2026, specialist claims for UHC MA HMO/HMO-POS members without a valid 2026 PCP referral are denied as uhc denial code pr 242 and classified as provider liability.
Even for non-UHC plans, most HMO referrals reset at the plan year. A 2025 referral doesn’t carry over into the 2026 billing cycle.
Patients who saw the same specialist for years without issues in 2025 can generate PR-242 denials in 2026 simply because no one obtained a fresh referral.
See UnitedHealthcare 2026 Medicare Advantage HMO referral requirements for the PCA-1-25-02706-M&R policy documentation.
Cause 3 — Missing or Invalid Prior Authorization
Some managed care plans require pre-authorization for specific services in addition to referrals. When authorization wasn’t obtained, is expired, or doesn’t match the billed CPT code, date, or rendering provider, PR-242 fires.
Under CMS-0057-F, effective January 1, 2026, payers must provide a specific denial reason when denying prior authorization. For PR-242 denials rooted in missing authorization, that specific reason is now available for your appeal documentation. Every pr 242 denial code description tied to an authorization failure now has an addressable specific denial reason under CMS-0057-F.
A targeted appeal addressing the stated reason succeeds more often than a generic medical necessity letter. Our prior authorization services team manages these authorization workflows upstream before the denial fires.
Cause 4 — Patient Self-Referral Violation
On HMO and HMO-POS plans with gatekeeper requirements, patients must see their PCP first and receive a referral before seeing a specialist. When a patient self-refers without a PCP visit first, PR-242 fires because the service wasn’t directed through the required primary care channel.
The patient is responsible for the balance because they bypassed the plan’s referral protocol. The provider isn’t at fault but needs documentation of the self-referral to support patient billing.
This is one of the three definitive scenarios where billing the patient doesn’t require additional verification once you’ve confirmed the self-referral pattern.
Cause 5 — Provider Credentialing and NPI Enrollment Gaps
PR-242 can fire on claims where the provider is technically in-network but the claim was submitted under the wrong NPI, a group NPI for a provider not enrolled in that specific group’s HMO contract, or with an incorrect taxonomy code that places the provider outside the payer’s covered classification.
These administrative billing errors create network status misclassification on the payer’s adjudication system. The provider didn’t go out of network. The claim coded them that way. These denials are correctable on resubmission once the enrollment gap is identified.
Our provider enrollment and credentialing services identify which NPI enrollment records are generating systematic PR-242 patterns across specific plan products.
Cause 6 — New Provider Credentialing Window
When a new provider joins a practice and begins seeing patients during the credentialing application window (before the payer has completed enrollment), claims for that provider fire PR-242 even when the provider will eventually be in-network. The payer’s adjudication system can’t match the rendering NPI to an active enrollment record.
These denials aren’t errors in the traditional sense. They’re timing issues where the provider’s credentials haven’t cleared yet. Retroactive credentialing requests with the payer are the standard recovery path, typically available within 30 to 90 days from the original date of service depending on the payer’s retroactive enrollment policy.
PR-242 RARC Crosswalk: How the 242 Remark Code Tells You What to Do Next
The remark code accompanying PR-242 on your remittance is your investigation routing signal. It tells you whether the denial is about network status, missing PCP data, or No Surprises Act protections that change your patient billing rights.
Read it before taking any action. The pr 242 remark code is the first data point in the resolution sequence, not the denial code number itself.
The PR-242 RARC Reference Table
| RARC Code | Official X12 Description | What It Signals for PR-242 | Resolution Action | Patient Billing Impact |
|---|---|---|---|---|
| N130 | “Consult plan benefit documents/guidelines for information about restrictions for this service.” | Plan benefit design restricts this service to network or PCP-directed care. | Pull managed care contract and plan benefit grid for the specific CPT code. | Standard PR-242 patient billing after verifying denial is accurate. |
| N778 | “Missing Primary Care Physician Information.” | PCP data is missing on the claim. The referral may exist but wasn’t included. | Add PCP information and referral number to the claim. Resubmit before generating patient statement. | Verify corrected claim outcome before billing patient. |
| N862 | NSA cost-sharing compliance. | Service is subject to No Surprises Act protections. | Patient cost-sharing can’t exceed the in-network level. Do not bill patient beyond NSA-protected amount. | NSA-protected. Bill only in-network cost-sharing equivalent. |
| N878 | NSA notice-and-consent problem. | Balance billing prohibited under NSA for this service. | Do not balance-bill patient. NSA open negotiation or IDR process governs reimbursement dispute. | Prohibited. |
| N879 | NSA balance billing prohibited. | Confirms NSA protection applies. | Same as N878. Initiate IDR within four business days of failed open negotiation. | Prohibited. |
When N862, N878, or N879 accompanies PR-242, stop before generating a patient statement. These codes signal the No Surprises Act applies and patient billing rights are restricted regardless of the PR group code prefix.
See the X12 RARC official list for official descriptions and the CMS No Surprises Act balance billing protections for NSA compliance guidance.
The pr242 reason code investigation begins with this table, not with a patient statement queue. Routing PR-242 denials by RARC before taking any action is the one workflow change that prevents the highest-cost compliance errors in managed care billing.
When NSA Remark Codes Change Everything About Patient Billing
N862, N878, and N879 are the three remark codes that override the default PR-242 patient billing pathway. When any of these appears alongside PR-242, the No Surprises Act governs the reimbursement dispute rather than standard patient balance billing. The patient’s cost-sharing can’t exceed what they’d owe for in-network care.
For providers in emergency department settings or those delivering services at in-network facilities, these remark codes appear more often than billing teams realize. Missing them means billing patients for amounts they’re legally protected from owing.
The IDR process, not a patient statement, is the correct next step when NSA remark codes accompany PR-242. Providers have four business days after failed open negotiation to initiate IDR. Missing that window forfeits reimbursement rights permanently.
See the prior authorization guide for authorization and prior auth documentation workflows that connect to NSA compliance for non-emergency services.
One O Seven RCM’s AR team reads the RARC before routing any pr242 denial, which means NSA-protected claims never generate patient statements and network status investigations never get assigned to the wrong specialist.
How to Resolve a PR-242 Denial: Seven-Step Workflow for Billing Teams
PR-242 doesn’t resolve through generic resubmission. It resolves through a specific investigation sequence that starts with the RARC, not the denial code number. The step you skip determines the resolution path you get wrong.
Work these seven steps in sequence before routing any pr 242 denial code resolution path to a patient statement queue, a write-off, or an appeal.
Step 1 — Read the RARC Before Taking Any Action
Pull the 835 ERA and locate the remark code alongside the PR-242 adjustment. If N862, N878, or N879 appears, stop immediately. The No Surprises Act governs this claim and standard patient billing is restricted. If N778 appears, add PCP information and resubmit before generating any patient statement. If N130 appears, pull plan benefit documents for the CPT code before any other action. If no RARC accompanies PR-242, treat it as a network status investigation by default.
Step 2 — Verify Provider Network Status by Plan Type
Log into the payer’s provider portal and confirm the rendering provider’s network status on the date of service. Search by NPI under the specific plan type, not the payer generally. HMO, PPO, and EPO products within the same payer can have different network panels. Confirm that the enrollment dates match the date of service and that the billing NPI and rendering NPI match the payer’s enrolled records for the correct plan product.
Step 3 — Pull All Referral and Authorization Records
For HMO and HMO-POS denials, verify four things from your referral records: whether a referral existed, whether it came from the patient’s designated PCP for the current plan year, whether it covered the specific CPT code and service type billed, and whether it was valid on the date of service. A 2025 referral doesn’t carry over to the 2026 plan year.
Under CMS-0057-F (effective January 1, 2026), authorization denials must include a specific denial reason your team can address directly in the appeal. Use that specific reason in your retroactive authorization request rather than a generic medical necessity letter. Our prior authorization services team handles these authorization documentation workflows.
Step 4 — Check for NSA Remark Codes Before Generating Patient Statement
Before any patient statement goes out, confirm whether the service involved emergency care or a service delivered at an in-network facility by an out-of-network provider. Both scenarios may trigger No Surprises Act protections that cap patient cost-sharing at the in-network equivalent.
If N862, N878, or N879 accompanies PR-242, the patient can’t be billed beyond in-network cost-sharing regardless of the PR group code prefix. Initiate NSA open negotiation with the payer instead. This is the pr 242 denial code action that prevents the most costly compliance errors in emergency and facility-based billing.
Step 5 — Determine Your Resolution Path
Based on Steps 1 through 4, route the PR-242 into one of three paths.
Path 1 (Corrected Claim): The provider is in-network but the claim used the wrong NPI, taxonomy code, or missing PCP information. Correct the data error and resubmit. The denial was administrative, not a legitimate network violation.
Path 2 (Retroactive Authorization): The authorization or referral was missing due to an administrative oversight for an established patient. Contact the payer and request retroactive authorization within the payer’s allowed window, typically 30 to 60 days from the date of service.
Path 3 (Patient Billing or Write-Off): The denial is accurate and legitimate. The provider is out-of-network and the patient had no NSA protection. Generate the patient statement. For UHC MA HMO denials without a 2026 referral post-May 1, 2026, these are classified as provider liability. Don’t patient-bill. Post the write-off.
Step 6 — Resubmit, Correct, or File the Formal Appeal
For Path 1: Correct the NPI, taxonomy code, or PCP information. Confirm the payer’s corrected claim window before submission. Most managed care payers allow 90 to 180 days from the original date of service.
For Path 2: Submit the retroactive authorization request with the physician’s letter explaining medical necessity and why the authorization wasn’t obtained in advance. Most payers require this within 30 to 60 days of the denial date.
For a disputed denial where the provider believes they’re in-network: Submit a formal written appeal with proof of network participation, credentialing effective dates, and the specific plan product enrollment confirmation from the payer’s portal.
Submit all appeals before the payer’s deadline. A missed deadline turns a recoverable denial into a permanent timely filing denial write-off. See CMS-0057-F for the CMS-0057-F prior authorization final rule guidelines on specific denial reason requirements.
Step 7 — Handle Patient Billing and Secondary Insurance
Before generating the patient statement, check two things. First, confirm secondary insurance coverage. The patient’s secondary plan may cover part or all of the out-of-pocket balance before the patient owes anything directly. Second, confirm the patient received advance notice of potential out-of-network costs when the service was scheduled. If no advance notice was given in NSA-applicable scenarios, patient billing rights may be restricted regardless of the PR group code.
When the denial is legitimate, the patient statement is accurate, and there’s no secondary coverage, generate the statement with a clear explanation of the out-of-network cost responsibility and offer payment plan options for high-balance claims. This is the complete pr 242 denial code solution workflow from RARC to patient statement.
One O Seven RCM’s billing team works PR-242 denials through this exact seven-step sequence within 24 hours of ERA posting, which means correctable denials don’t age past timely filing windows and patient statements only go out after every verification step clears.
PR-242 Denial Code Examples: Two Real-World Scenarios and What Your Team Does Next
Two scenarios explain more about PR-242 resolution than any definition. Here’s what the pr 242 denial code example looks like in 2026 in practice and what your team’s next action should be in each situation.
Scenario 1 — UHC Medicare Advantage HMO Specialist Visit Without a 2026 Referral
A cardiologist’s billing team submits a claim for a UHC Medicare Advantage HMO patient seen in March 2026. The cardiologist treated this patient regularly through 2025. The claim returns with the pr-242 denial code description indicating “Services not provided by network/primary care providers” under UHC’s January 1, 2026 referral requirement.
The billing team checks: did the patient’s PCP submit a 2026 referral before the March appointment? No referral exists for the 2026 plan year.
Per UHC’s PCA-1-25-02706-M&R policy and the post-grace-period enforcement (May 1, 2026), this denial is classified as provider liability. The team posts a write-off. The patient isn’t billed.
They contact the PCP to establish a 2026 referral workflow for all future appointments. Our prior authorization services team handles the referral intake update that prevents the next billing cycle from repeating this pattern.
Scenario 2 — Emergency Department Physician at an In-Network Hospital
An emergency medicine physician bills for services at an in-network hospital for a patient with commercial insurance. The claim returns PR-242 with RARC N862 (NSA cost-sharing compliance). The billing team recognizes N862 signals No Surprises Act protection.
The patient was treated in an emergency setting at an in-network facility by an out-of-network physician, which triggers NSA protections. The patient’s cost-sharing is capped at the in-network equivalent.
The team doesn’t generate a patient statement for the full balance. They calculate the in-network cost-sharing equivalent and initiate NSA open negotiation with the payer for the remainder.
The IDR process, not the patient, covers the gap between what the payer paid and what the physician bills.
2026 Regulatory Updates That Affect Every PR-242 Denial You Work This Year
Three regulatory changes in 2025 and 2026 directly affect how PR-242 denials are generated, investigated, and appealed. Practices operating on pre-2026 workflows are creating preventable denials and missing appeal rights the new rules created.
UHC Medicare Advantage 2026 Referral Requirement — Grace Period Now Expired
UnitedHealthcare’s 2026 referral requirement for Medicare Advantage HMO and HMO-POS plans, detailed in provider document PCA-1-25-02706-M&R (December 2025), went into operational effect January 1, 2026. Specialists providing care to UHC MA HMO and HMO-POS members now require a PCP referral before providing care, even for established patients.
The grace period during which claims wouldn’t be denied for missing referrals ended April 30, 2026.
Claims for services delivered after May 1, 2026 without a valid 2026 PCP referral are denied as PR-242 and classified as provider liability.
Practices treating UHC MA HMO patients that haven’t updated their 2026 referral intake workflows are generating preventable denials every billing cycle right now. See UnitedHealthcare 2026 Medicare Advantage HMO referral requirements for the PCA-1-25-02706-M&R documentation.
CMS-0057-F — How the 2026 Prior Authorization Rule Changes PR-242 Appeals
CMS-0057-F, the CMS Interoperability and Prior Authorization Final Rule, went into operational effect January 1, 2026. Payers can no longer issue generic authorization denials. They must provide a specific denial reason.
For PR-242 denials rooted in missing or denied prior authorization, the specific denial reason is now available for use in retroactive authorization requests and formal appeals.
A targeted appeal addressing the specific stated reason is more likely to succeed than the generic medical necessity letters most billing teams still submit.
Our prior authorization services team builds appeals from the CMS-0057-F specific denial reason, not from generic documentation. See the CMS-0057-F prior authorization final rule for the full regulatory text.
CARC and RARC Code List Confirmation for 2026
The X12 Claim Adjustment Reason Code list was last modified November 1, 2025, and its status was last reviewed May 1, 2026. CARC 242 remains active and unchanged as of this review.
The X12 Remittance Advice Remark Code list was last modified March 4, 2026, confirming the NSA-related remark codes (N862, N878, N879) are current and active.
Both code sets are updated three times per year by CMS Transmittal R13666CP (Change Request 14410), with the next update cycle expected July 1, 2026.
Any billing guidance citing an older CARC or RARC list than November 1, 2025 is working from outdated code definitions for denial resolution decisions your team is making right now.
One O Seven RCM tracks CARC and RARC code set updates, UHC payer policy changes, and prior authorization regulatory shifts across every managed care payer we work with so your billing workflows reflect current 2026 rules, not last year’s denial patterns.
How to Prevent PR-242 Denials Before They Reach Your Remittance
Most PR-242 denials are preventable before the claim is ever submitted. These controls catch network status gaps, referral failures, and authorization errors before they become remittance adjustments and patient billing disputes.
Front-End Prevention (Before Service Delivery)
- Verify the patient’s specific insurance plan type (HMO, PPO, EPO) at scheduling and confirm the rendering provider is enrolled in that specific plan product, not just the payer generally. Being in-network with UHC commercial doesn’t guarantee participation in UHC Medicare Advantage HMO.
- Confirm the patient’s designated PCP for the current plan year and whether a valid referral for the specialist visit was issued by that specific PCP for the 2026 plan year. A 2025 referral doesn’t carry over.
- Obtain prior authorization for services that require pre-approval under the managed care plan before scheduling the appointment. Under CMS-0057-F (January 1, 2026), payers must respond with specific denial reasons, but only if you submitted the request first. See prior authorization and eligibility verification for the upstream authorization workflow.
- Educate the patient at the point of scheduling whether the planned provider is in-network and what the estimated out-of-pocket responsibility will be if care proceeds with an out-of-network provider, including any NSA protections that apply.
Mid-Cycle Prevention (Claim Preparation and Submission)
- Confirm the rendering NPI and billing NPI match the payer’s enrolled records for the specific plan product before claim submission. A group NPI submitted for a provider not enrolled in the specific HMO contract triggers PR-242 even when the provider is otherwise in-network.
- Include the referral number and PCP NPI on every HMO and HMO-POS claim that required a referral. Missing PCP information on the claim triggers RARC N778 and generates a preventable denial.
- Verify the taxonomy code for the rendering provider matches the payer’s approved classification for the service type. An incorrect taxonomy code can misclassify an in-network provider as out-of-network in the payer’s adjudication system.
- Run a pre-submission eligibility check against the specific plan type, not just general insurance eligibility. Plan type determines whether managed care referral and authorization rules apply. See patient registration and eligibility verification for the eligibility check workflow at the front end. The pr242 reason code most often caught at mid-cycle is the N778 PCP data gap.
Back-End Prevention (ERA Review and Pattern Management)
- Route PR-242 denials by RARC the same day the ERA posts. N862, N878, and N879 go to NSA compliance review. N778 goes to claim correction. N130 goes to contract and benefit document review. Generic denial queues mix PR-242 with CO-242 and delay both investigations.
- Build a PR-242 tracking report by payer and plan type and review it monthly. Patterns of PR-242 on the same payer plan product signal either a credentialing gap that needs enrollment correction or a referral workflow failure that needs a process update.
- Audit UHC Medicare Advantage HMO referral records monthly to confirm every specialist claim has a corresponding 2026 PCP referral on file. The UHC grace period ended April 30, 2026. There’s no second chance on missing referrals.
- Monitor for AmeriHealth and other regional managed care payers that have similar gatekeeper requirements. The pr 242 denial code amerihealth pattern signals the same referral compliance gap as UHC but with different payer-specific resolution paths.
One O Seven RCM builds plan-type-specific prevention workflows for every managed care payer we bill, with front-end eligibility controls, mid-cycle NPI validation, and back-end RARC routing that catches PR-242 patterns before the next billing cycle.
PR-242 vs Similar Denial Codes: How to Tell Them Apart in Your Denial Queue
PR-242 produces zero payment and assigns financial responsibility to the patient. So can PR-27, PR-243, and several other codes that appear alongside it in managed care billing queues. Knowing what distinguishes them determines the resolution path your team takes next.
| Code | Official X12 Description | Group Code | Who Owes | Resolution Path Difference From PR-242 |
|---|---|---|---|---|
| PR-242 | “Services not provided by network/primary care providers.” | Patient Responsibility | Patient owes. | Network status investigation. Patient statement after NSA check. This article. |
| PR-243 | “Services not authorized by network/primary care providers.” | Patient Responsibility | Patient may owe. | Referral and authorization investigation, not network investigation. Different workflow from PR-242. |
| CO-242 | “Services not provided by network/primary care providers.” | Contractual Obligation | Provider write-off. No patient billing. | Same CARC number as PR-242 but opposite financial consequence. |
| CO-197 denial code | “Precertification/authorization/notification/pre-treatment absent.” | Contractual Obligation | Provider write-off. No patient billing. | Authorization failure without the network compliance issue. |
| PR-27 denial code | “Expenses incurred after coverage terminated.” | Patient Responsibility | Patient owes. | Coverage termination investigation, not network investigation. Different CARC, same group code as PR-242. |
| CO-50 denial code | “These are non-covered services because this is not deemed a medical necessity by the payer.” | Contractual Obligation | Provider write-off. | Clinical appeal required. Not a network code at all. |
CO-242 and PR-242 carry the same X12 CARC description but opposite financial outcomes because of the group code prefix. Routing CO-242 to the patient billing workflow is a compliance violation.
Routing PR-242 to the write-off workflow loses patient revenue. See the CO-24 denial code for the managed care coordination code context that appears on the same remittances as PR-242 in HMO billing environments.
The Financial Impact of PR-242 Denials on Your Revenue Cycle
PR-242 denials don’t just delay individual claims. They generate patient billing disputes, compliance exposure from NSA violations, and systematic revenue leakage that compounds across the same managed care plans month after month without pattern recognition.
| Impact Area | Industry Figure | Source | What It Means for Your Practice |
|---|---|---|---|
| Per-claim rework cost | $43.84 per claim to overturn a denial | Premier Healthcare | Every PR-242 network investigation and appeal costs real administrative dollars before any patient revenue is collected. |
| Annual industry denial rework | $19.7 billion annual cost of claim rejection rework | Premier Healthcare | Managed care network denials like PR-242 are a measurable share of this national figure. |
| Preventable denial rate | 8 in 10 denials are preventable | Change Healthcare | Most PR-242 volume is a front-end verification failure, not an unavoidable network limitation. |
| Initial denial rate, 2024 | 11.8% initial denial rate | MDaudit Hospital Denial Report | PR-242 contributes disproportionately in practices with high HMO and managed care patient volume. |
See the Premier Healthcare claim denial cost analysis for the $43.84 per-claim and $19.7 billion industry rework figures.
The revenue risk from PR-242 isn’t the face value of one denied claim. It’s the compound effect of missing a systematic referral failure across 30 to 40 similar claims per billing cycle until someone identifies the pattern.
If your PR-242 denial volume by managed care plan is growing month over month without a dedicated referral verification and network status workflow, One O Seven RCM’s denial management team identifies the pattern within the first 30 days of onboarding and builds the front-end controls before the next billing cycle.
See our revenue cycle management services for the complete managed care denial prevention workflow.
Frequently Asked Questions About the PR-242 Denial Code
What Is a PR 242 Code?
PR-242 is a medical billing denial code that appears on the 835 Electronic Remittance Advice when the payer determines services were not provided by a network or primary care provider as required by the patient’s plan.
X12 defines CARC 242 as “Services not provided by network/primary care providers.” The PR prefix means Patient Responsibility, so the patient owes the denied balance rather than the provider absorbing a write-off.
CARC 242 has been active since January 1, 1995, and was last confirmed active on the X12 CARC list reviewed May 1, 2026.
What Is a PR Denial Code in Medical Billing?
PR stands for Patient Responsibility, one of four Claim Adjustment Group Codes defined by X12. A PR denial code means the payer has determined the patient, not the provider, is financially responsible for the denied amount.
Common PR codes include PR-1 (deductible), the PR-27 denial code (expenses after coverage terminated), and PR-242 (services not provided by network or primary care providers).
Unlike CO (Contractual Obligation) denials where the provider absorbs the adjustment, PR amounts can be billed to the patient after verifying the denial is accurate.
What Is PR 243 Patient Responsibility Services Not Authorized by Network Primary Care Providers?
PR-243 is the Patient Responsibility variant of CARC 243, which X12 defines as “Services not authorized by network/primary care providers.” It’s a separate code from PR-242. PR-242 covers who rendered the service (out-of-network or non-PCP provider).
PR-243 covers who authorized the service (referral or authorization was missing or invalid). Both codes existed as a single older code CARC 38 before X12 split them into two more operationally precise codes.
The resolution workflows are completely different and require separate investigations.
What Does CO 242 Mean?
CO-242 means the same service described by CARC 242 (“Services not provided by network/primary care providers”) was denied with the CO (Contractual Obligation) group code instead of the PR (Patient Responsibility) group code.
CO-242 means the provider absorbs the write-off. The patient can’t be billed. This is the exact opposite of PR-242, where the patient owes the balance.
billingfreedom.com defines CO-242 as a medical necessity denial, which is factually wrong per the X12 CARC official list. rapidclaims.ai defines it as a coverage termination denial. That definition is also wrong.
What Does PR 242 Mean on an EOB?
On a paper Explanation of Benefits, PR 242 appears in the denial code column with description language such as “Services not provided by network/primary care providers” or “Out-of-network provider.” On an electronic 835 remittance advice, it appears in the CAS segment as CAS01 = PR, CAS02 = 242, CAS03 = the adjustment dollar amount.
The PR prefix on an EOB or ERA always means the patient owes the listed adjustment amount after the provider verifies the denial is accurate.
What Does PR 242 Mean?
PR-242 means a claim was denied because the services were not provided by a network or primary care provider as required by the patient’s insurance plan.
The PR prefix means Patient Responsibility, so the patient is financially liable for the denied amount. The 242 is the Claim Adjustment Reason Code, which X12 officially defines as “Services not provided by network/primary care providers.”
What Is Denial Code N242?
N242 is not a standard X12 Claim Adjustment Reason Code. Some billing staff confuse N242 with PR-242, but RARC N-codes (beginning with the letter N) are Remittance Advice Remark Codes, not denial reason codes.
PR-242 is the correct notation for the CARC 242 denial with a Patient Responsibility group code prefix. If you’re seeing “N242” on a remittance, it’s likely either a payer-specific proprietary remark code or a notation error.
Check the payer’s EOB description field for clarification.
Can a Claim Be Denied With a PR-242 Reason Code?
Yes. A claim is denied with the pr-242 denial code when the payer determines the billed service was not provided by a network or primary care provider as required by the patient’s plan.
The denial doesn’t mean the claim was rejected for missing information or coding errors. It means the provider who rendered the service didn’t meet the plan’s network or PCP requirements.
The claim can be resubmitted if the denial was a payer error, appealed if the provider believes they were in-network, or handled as a patient balance if the denial is accurate.
The can we bill the patient for pr 242 denial code answer depends on whether the denial is legitimate and whether NSA remark codes accompany it.
What Is Denial Code PR-242 Description?
This is the most searched definitional query for the pr-242 denial code in the SERP.
The official pr-242 denial code description, as defined by X12 in the Claim Adjustment Reason Code list, is “Services not provided by network/primary care providers.” CARC 242 has been active since January 1, 1995, and was last confirmed unchanged on the CARC list reviewed May 1, 2026.
The PR prefix in PR-242 adds the Patient Responsibility group code designation, meaning the patient owes the denied balance under the claim adjustment standard.
The pr 242 denial code description is consistent across all payers using the X12 835 transaction standard.
Every valid pr 242 denial code description resolves to the same X12 CARC 242 text regardless of which payer issued the remittance.
What Is Denial Reason Code PR 242 in Medical Billing?
In medical billing, the denial reason code pr 242 indicates that the billed service was not provided by an in-network or primary care provider as required by the patient’s managed care plan.
It’s one of the most common managed care denial codes because it appears whenever patients access out-of-network providers, bypass referral requirements, or receive care from providers not enrolled in their specific plan product.
The resolution depends entirely on whether the denial is accurate, which requires verifying network status, referral records, and NSA remark codes before generating a patient statement or writing off the balance.
See our medical billing services for the complete managed care denial management workflow.
