Dental PPO Networks Explained: Direct, Shared, Leased and TPA Participation

# Study Guide: Dental PPO Networks Explained

## How To Use This Guide

Read this before recording the core article. The goal is to help Joey explain direct, shared, leased, umbrella, and TPA participation in practical owner language without turning the recording into final article prose.

Use the guide to prepare definitions, examples, EOB walkthroughs, and source-needed cautions. The recording should capture how Joey thinks when a practice says, "I thought we were in network with one carrier, but this claim paid under something else."

Stay in investigation mode:

- Keep asking: "Through which contract path, for which payer/product/location/provider, at which fee schedule, as of what effective date?"

- Separate what the patient card says from what the contract path proves.

- Treat an unexpected discount as a clue, not automatically a payer error.

- Ask for documents before giving advice about opt-outs, termination, direct-contract priority, or claim correction.

- Preserve caveats around carrier-specific, state-law, ERISA, opt-out, and precedence claims.

## Article Thesis

PPO participation is not a simple in-network or out-of-network label. It is a contract-path question.

The article should teach owners and office managers that direct contracts, shared networks, leased networks, umbrella arrangements, and TPAs can affect which fee schedule loads and why an EOB may not match the participation story the practice thought it understood.

The practical owner takeaway: do not ask only, "Are we in network?" Ask, "What exact path gave this payer or product access to this provider, location, fee schedule, and effective date?"

## What To Understand Before Recording

### The Reader

The reader is a private-practice owner or office manager trying to make sense of a payment surprise, network list, participation report, or carrier conversation.

They are usually not trying to become a contract lawyer. They want to know why the office is being paid under a fee schedule or network name they did not expect, and what to do before renegotiating, opting out, terminating, or calling the payer wrong.

Common owner language from the broader audience profile:

- "I don't even know which PPOs we're actually tied into."

- "Are we direct with this plan, or accessing it through another network?"

- "We're busy, but the money isn't showing up."

- "My office manager is already overloaded."

- "I can see write-offs, but I can't tell which plan is actually hurting us."

### The Core Teaching Job

This article is the network-architecture pillar. It should make the reader safer and more precise when they:

- Read an EOB that paid lower than expected.

- Compare a patient card, payer, product, network name, and fee schedule.

- Decide whether a payment looks wrong or just undocumented.

- Ask a carrier which contract path controlled a claim.

- Build a participation map.

- Evaluate direct, shared, leased, umbrella, or TPA routes before changing PPO strategy.

- Decide whether an opt-out, termination, direct contract, or renegotiation is the next step.

### The Contract-Path Stack

Study this sequence until it is easy to explain aloud:

1. Patient presents a dental benefit plan or employer product.

2. Claim identifies payer/product, provider, TIN, NPI, service location, and date of service.

3. Payer or administrator determines whether the provider is participating through a direct, shared, leased, umbrella, TPA-related, or other access path.

4. That path points to a fee schedule or allowance logic.

5. Effective date, amendment date, provider credentialing, location scope, and product scope determine whether the path should apply.

6. The EOB shows the allowed amount, payment, patient responsibility, adjustment/write-off, network clues, and remark codes.

7. The practice compares the EOB to contracts, fee schedules, notices, portal records, and participation maps before deciding whether there is an error or a supported routing path.

### Terms Joey Should Define

| Term | Study Definition | What To Emphasize | Caveat |

| --- | --- | --- | --- |

| Direct PPO contract | A contract the practice or provider has directly with a payer or network entity. | It may control rates for a defined payer, product, provider, location, and effective date. | Do not say it always overrides shared or leased access. |

| Shared network | A relationship where one network or payer arrangement gives access to another payer/product or downstream plan. | The practice may recognize one network name but not the patient-facing brand. | Source-needed for specific carrier relationships and dates. |

| Leased network | A network access arrangement where discounts may be rented, leased, or made available to another entity. | The owner may experience it as an unexpected discount or unfamiliar network access. | Notice, opt-out, and legality vary by contract, state, plan type, and date. |

| Silent PPO | A term often used when a discount is applied through a network path the provider did not clearly expect or recognize. | It is a practical warning label, not a single uniform legal category. | Define carefully; usage varies. |

| Umbrella arrangement | A broader structure where affiliate, parent, or related network access may pull multiple products under one participation route. | A carrier name alone may hide product-level or affiliate-level variation. | Avoid implying every carrier umbrella works the same way. |

| TPA | A third-party administrator that may administer claims or benefits for an employer or plan. | Administration is not the same thing as owning the network rights. | Do not say TPA equals PPO network unless the source proves that role. |

| Participation map | A dated working record of every known payer/product/network path, provider/location scope, fee schedule, source document, and confidence level. | This is more useful than a simple payer list. | Needs maintenance; stale maps create bad decisions. |

| Effective date | The date a contract, fee schedule, amendment, opt-out, termination, or credentialing status begins to control claims. | Many surprises are timing problems, not strategy problems. | Claim date of service and processing date may both matter. Source-needed. |

## Research Briefing

### Strongest Supported Research Points

- PPO status should be explained as a contract-path question, not a binary in-network label.

- The safest operating frame is payer/product, provider or location, contract path, fee schedule, effective date, and evidence source.

- Patient cards, employer plan names, carrier names, and provider directories may not prove the fee schedule that will load.

- Direct, shared, leased, umbrella, and TPA pathways must stay distinct.

- A TPA may administer claims without being the source of network access.

- An unexpected discount is not automatically a claim error; the first task is to document the path.

- Direct-contract precedence, opt-out rights, and state network-leasing protections are not universal.

- Carrier-specific examples need current source review before naming a carrier, plan, routing rule, or effective date.

### Documents Joey Should Mention

An owner or office manager should gather:

- Recent EOBs or ERAs for the questioned claims.

- Direct contracts and amendments.

- Current and prior fee schedules.

- Payer notices, network leasing notices, affiliate notices, and opt-out confirmations.

- Provider portal screenshots showing participation, fee schedules, or network status.

- Participation lists or network maps from carriers and administrators.

- Credentialing records for provider, TIN, NPI, location, and effective dates.

- Practice-management software plan setup and fee schedule mapping.

- Any carrier correspondence about termination, opt-out, direct contract changes, or fee schedule updates.

### EOB Fields To Study

Have Joey walk through what she inspects first:

- Payer and product name.

- Employer group or plan identifier if visible.

- Network name or participation clue.

- Rendering provider, billing provider, TIN, NPI, and location.

- Date of service and processing date.

- CDT code.

- Submitted charge.

- Allowed amount or plan allowance.

- Contracted amount if separately shown.

- Insurance payment.

- Patient responsibility.

- Adjustment or write-off amount.

- Remark codes, denial notes, downcoding notes, or processing messages.

- Fee schedule reference if shown.

### Contract Clauses Or Evidence To Ask About

When Joey talks about precedence or "which contract wins," ask what proof she would want:

- Conflict or supersession language.

- Most-specific-contract language.

- Affiliate access clauses.

- Plan participation clauses.

- Network leasing or rental language.

- Product scope and excluded products.

- Provider, TIN, NPI, entity, and location scope.

- Effective date and notice language.

- Opt-out or carve-out terms.

- Payer processing manuals or provider bulletins.

## Competitive And SERP Briefing

### Search Intent

This article sits in the network-architecture cluster. The reader is trying to diagnose why a claim paid under a lower or different fee schedule, or how a practice can be treated as participating with a plan it did not directly sign.

Primary keyword cluster:

- dental PPO networks explained

- direct dental PPO contract

- shared PPO network

- leased PPO network

- silent PPO dental

- dental TPA meaning

- why did a dental PPO claim pay at a lower fee schedule

### Content Format That Can Win

The SEO pack recommends:

- Short definition blocks.

- A direct/shared/leased/TPA comparison table.

- The contract-path stack.

- An EOB-routing example.

- Owner audit questions.

- Clear source-needed caveats around legal, payer-specific, opt-out, and precedence claims.

The citation-magnet file identifies this question as weak in existing AI answers: "What is the difference between a silent PPO, leased network, shared network, umbrella network, and TPA?" A durable article should use a sourced glossary, relationship diagrams, contract examples where available, and effective-date history.

### Differentiation

Competitors already talk about negotiation, shared networks, direct contracts, and PPO optimization. Unlock's stronger angle is participation execution:

- A signed fee schedule is only a promise until EOBs prove the intended rate is governing claims.

- A payer list is not the same thing as a participation map.

- A network surprise should trigger evidence collection before payer blame or termination advice.

- Unlock can connect network-path diagnosis to fee schedule analysis, opt-out planning, renegotiation, PMS setup, and EOB verification.

The open position: help the owner move from vague network frustration to a dated, document-backed participation map.

## Examples And Scenarios To Study

### Scenario 1: The Patient Card Does Not Explain The Payment

Study setup:

An owner recognizes the carrier name on the card and assumes the claim should follow the practice's direct contract. The EOB pays at a different allowed amount than expected.

Questions for Joey:

- What does the card prove, and what does it not prove?

- Which payer/product actually adjudicated the claim?

- Was a network name, affiliate, or administrator visible on the EOB?

- Which provider, location, TIN, and date of service were used?

- What document would prove the fee schedule that should have loaded?

Study answer:

The card is a starting clue, not the contract path. Joey should slow the owner down until the EOB, contract, fee schedule, provider record, and effective date line up.

### Scenario 2: Direct Contract Exists, But The Practice Still Needs Precedence Evidence

Study setup:

The practice has a direct PPO contract and believes that direct contract should override a shared or leased network path.

Questions for Joey:

- Which contract is direct, and for which product?

- Does the direct contract cover this provider, TIN, location, and date of service?

- Does the contract say anything about affiliates, leased networks, product scope, conflict, supersession, or priority?

- Does the payer have a processing rule that routes some products differently?

- What would Joey refuse to say publicly without the contract language?

Study answer:

Do not record a blanket claim that direct always wins. The safer teaching point is that direct-contract priority is a document question.

### Scenario 3: Practice Thinks It Never Signed With The Patient-Facing Plan

Study setup:

The patient-facing plan name is unfamiliar, but the EOB applies a PPO adjustment.

Questions for Joey:

- Is the payer using access through a shared, leased, umbrella, affiliate, or TPA-related path?

- Is there a provider notice or participation map that names the downstream access?

- Was the practice given notice or an opt-out opportunity?

- Does state law matter?

- Is the plan fully insured, self-funded, ERISA-governed, or otherwise outside the assumed rule?

Study answer:

This is the heart of the article. The owner needs to trace how the discount traveled before deciding whether the situation is expected, opt-out eligible, ambiguous, or wrong.

### Scenario 4: The TPA Is Involved, But May Not Be The Network

Study setup:

An office manager sees a TPA or administrator name and assumes that entity is the PPO network.

Questions for Joey:

- Is the TPA administering claims, benefits, eligibility, payments, or network access?

- Which entity actually gives the payer access to the provider's discount?

- Does the EOB name a network separately from the administrator?

- What documentation distinguishes administrative role from network-rights role?

Study answer:

Joey should separate "who processed the claim" from "who had the right to use the discount." This is a simple distinction that prevents a lot of bad carrier calls.

### Scenario 5: Opt-Out Or Termination Did Not Behave As Expected

Study setup:

The practice opted out, terminated, or changed direct participation, but claims still appear to process through a discount path.

Questions for Joey:

- What was the notice date and effective date?

- Which products or affiliates were included or excluded?

- Was the opt-out at provider, TIN, entity, location, carrier, product, or network level?

- Were run-out claims or dates of service before the effective date involved?

- Did the payer confirm the change in writing?

Study answer:

The article should teach timing and scope discipline. A valid change in one path may not erase every path, every product, or every claim date.

### Scenario 6: Participation Map Beats A PPO List

Study setup:

The owner has a list of PPOs but cannot explain which contract path controls each plan.

Participation map fields to study:

| Field | Why It Matters |

| --- | --- |

| Payer/product | Carrier name alone is too broad. |

| Provider/TIN/location | Participation may attach differently by record. |

| Contract path | Direct, shared, leased, umbrella, TPA-related, or unknown. |

| Fee schedule | The economic result comes from the loaded schedule. |

| Effective date | Old or future dates can explain payment surprises. |

| Source document | The map should be auditable. |

| Confidence level | Not every path will be proven on first pass. |

| Follow-up owner | Someone must chase missing proof. |

Study answer:

A participation map is the practical tool that converts confusion into action.

## Claims And Caveats

### Safer Claims

- PPO participation can depend on payer/product, provider, location, contract path, fee schedule, and effective date.

- Direct, shared, leased, umbrella, and TPA pathways are different concepts.

- A patient card or carrier name may not identify the contract path that controlled payment.

- A TPA can administer claims without automatically being the network-access source.

- An unexpected EOB should be investigated before calling it a payer error.

- A participation map is more useful than a simple list of payer names.

- Effective dates often explain why expected and actual reimbursement do not match.

### Source-Needed Or High-Risk Claims

- "Direct contracts always override shared or leased access."

- "You can always opt out of leased or shared networks."

- "A TPA is the same thing as a PPO network."

- "Every unexpected discount is illegal or a payer error."

- "State network-leasing protections apply to every plan."

- "This carrier always routes claims through this network."

- "This payer uses the lowest available fee schedule."

- "An opt-out from one arrangement removes all downstream access."

- "Termination of a direct contract removes every shared-network pathway."

- Any carrier-specific routing rule, product relationship, fee schedule, opt-out right, notice deadline, or effective date.

### Publication Caveats To Preserve

- Public sources may show network complexity but not the exact fee schedule loaded for a specific practice.

- State law varies, and self-funded ERISA plans may not follow the same assumptions as fully insured plans.

- Carrier pages and provider manuals can lag operational reality.

- Contract language, amendments, provider records, and EOBs control practice-specific conclusions.

- Examples should stay de-identified and illustrative unless Joey approves the underlying documents.

- Do not encourage dentists to exchange fee schedules or contract details with peers.

## Open Research Questions

- Which current carrier examples can Joey support with documents before publication?

- Can Joey supply one de-identified EOB where the patient-facing brand did not reveal the contract path?

- Can Joey supply one de-identified example where a direct contract existed but precedence still required review?

- Which terms does Joey prefer: shared network, leased network, silent PPO, rental network, umbrella network, or another house phrase?

- What source standard should Unlock require before naming Delta Dental, Cigna, MetLife, Aetna, UnitedHealthcare, Humana, or any network intermediary?

- Which state-law examples are safe for a national educational article, and which require state-specific pages?

- What contract clauses has Joey seen decide direct-versus-shared precedence?

- What does Joey look for first when a practice says a payer paid wrong?

- Which PMS setup errors commonly mimic a network-path problem?

- What should the article avoid saying because it sounds too broad, too legal, or too carrier-specific?

## Connections To Tools And Offers

### Related Content And Tools

Connect this article to:

- `content/core/core-008-what-is-dental-third-party-administrator.md`

- `content/core/core-009-direct-contract-override-shared-network-agreement.md`

- `content/core/core-010-complete-dental-ppo-participation-map.md`

- `content/core/core-011-ppo-layering-contract-stacking.md`

- `content/core/core-012-opt-out-dental-ppo-shared-network-agreement.md`

- `content/core/core-013-dental-ppo-profitability-analysis.md`

- `content/core/core-023-direct-contracts-shared-network-opt-outs-ppo-termination.md`

- `content/core/core-034-verify-negotiated-ppo-fees-on-eobs.md`

- `content/free-tools/tool-007-shared-network-confusion-checker.md`

- `content/lead-magnets/magnet-005-shared-network-tpa-cheat-sheet.md`

- `content/lead-magnets/magnet-012-ppo-participation-glossary-for-dental-owners.md`

### Offer Connection

Unlock can help with:

- Participation mapping.

- Contract-path review.

- Shared or leased network investigation.

- Fee schedule tracing.

- EOB verification.

- Carrier follow-up.

- Opt-out or termination planning.

- Implementation tracking after participation changes.

Safe service language:

An owner who suspects a claim paid through the wrong path should gather EOBs, contracts, fee schedules, payer notices, provider records, and portal screenshots before deciding whether the next step is correction, renegotiation, opt-out, termination, or monitoring.

Avoid promising that a direct contract, opt-out, or carrier call will automatically fix the issue. Tie the service connection to documentation, execution, and verification.

## Suggested Study Path

1. Read the core article workspace and recording prompt.

2. Review the definitions table until each term can be explained without notes.

3. Practice the contract-path stack aloud.

4. Walk through one EOB scenario and name each document Joey would request.

5. Decide which terms Unlock should use consistently for shared, leased, silent, umbrella, and TPA paths.

6. Identify one de-identified client-style story about an unexpected contract path.

7. Identify one example where the right answer depended on effective date.

8. Mark carrier-specific and state-law statements as Source-needed unless Joey has current documents.

9. Choose the next-step asset: participation map, shared-network cheat sheet, TPA glossary, EOB tracer, or opt-out checklist.

10. Record the talk-through as practical investigation, not polished article copy.

This is the execution brief, not the research itself. The scope is to build a source-driven handoff for Article ID core-007 around one operating question: a practice's PPO status is not just "in" or "out," but depends on the contract path, payer or product, provider or location, fee schedule, and effective date. The uploaded brief defines that angle, the glossary targets, the need for carrier-specific examples, the need to test direct-contract precedence, and the need to map state network-leasing protections and real EOB or participation-map examples. fileciteturn0file0L5-L18

The brief also identifies the main risk areas that need verification before anything can be published: statements that direct contracts always override shared networks, that opt-out rights always exist, that TPA and PPO network mean the same thing, that a payer necessarily made an error, and that state protections apply to every plan. It specifically asks for source quality, confidence notes, practical examples, caveats for Joey's review, and questions that still require operator judgment. fileciteturn0file0L43-L56

## research goal and boundaries

The research handoff should answer four layers at once.

First, it needs a clean conceptual frame. The article must distinguish direct participation, shared network access, leased network access, umbrella arrangements, TPAs, and silent PPO behavior without collapsing those terms into each other.

Second, it needs current carrier-specific proof. The article is only as strong as its ability to show how major dental payers actually route network access today, with product-specific and carrier-specific evidence rather than generic definitions.

Third, it needs operational evidence. That means contractual language, provider manuals, network-overlap maps, payer notices, fee schedule references, EOBs, and state-law text that can show how a practice ends up treated as participating under a route the owner did not expect.

Fourth, it needs publication discipline. Every claim should be tagged internally as strong, qualified, weak, or unsuitable for publication unless Joey can confirm it from practice experience or proprietary materials.

The working thesis stays narrow: the article should not try to prove that every unexpected discount is wrongful. It should show that network access can travel through more than one contract path, that those paths can produce different fee schedules and EOB outcomes, and that the right question is path-specific rather than binary. fileciteturn0file0L9-L11

## evidence standards and research questions

The reporting standard should be strict because the topic sits between payer operations, contract law, and state insurance regulation.

Use this hierarchy for evidence:

| evidence tier | what counts | how it will be used | publication value |

|---|---|---|---|

| primary and current | carrier contracts, provider manuals, network participation pages, state statutes, regulations, agency bulletins, carrier notices, sample EOBs from official or authenticated sources | establish direct facts | highest |

| primary but older or limited | archived carrier materials, older manuals still cited by carriers, state legislative history, insurer form filings | confirm continuity or show prior practice | medium, with date caveat |

| credible secondary | law firm alerts, association summaries, industry explainers, regulator FAQs | explain terminology and point to primary sources | support only |

| anecdotal or forum material | de-identified office examples, consulting blog posts, discussion boards | generate leads, not proof | do not rely on alone |

The core research questions should be handled in this order:

| question | what the evidence must show | likely source classes |

|---|---|---|

| What is the contract path? | exact relationship among carrier, network, affiliate, TPA, and plan | contracts, participation maps, provider pages |

| For which payer and product? | branded plan or product family, not just parent company | plan documents, provider directories, participation grids |

| For which location or provider? | whether participation attaches at TIN, NPI, service location, state, or contracting entity level | contracts, amendments, credentialing notices |

| Which fee schedule applies? | direct fee schedule, leased fee schedule, affiliate fee schedule, or plan-specific variant | contract clauses, fee schedule attachments, EOB references |

| Effective when? | start date, amendment date, notice date, termination date, opt-out deadline | notices, amendments, statutes, provider bulletins |

| What overrides what? | precedence clauses, conflict clauses, election clauses, most-specific-contract language, or payer processing rules | contract text, carrier memos, adjudication guidance |

The article brief itself flags the reader questions that should drive evidence collection, especially how a practice can be treated as participating without signing directly, whether direct contracts always override shared-network rates, and how to identify every network accessing a PPO agreement. fileciteturn0file0L21-L30

## source priorities and collection strategy

The collection strategy should start with primary sources by carrier, then move to state law, then to authenticated examples.

### carrier source stack

For each target insurer or dental platform, collect in this order:

| source type | collection target | reason |

|---|---|---|

| provider network participation pages | official pages that describe network products, leasing, affiliate access, shared or rental arrangements | current public baseline |

| provider manuals and admin guides | dental manuals, reimbursement or network admin sections, coordination with third-party network administrators | operational detail |

| participation maps and comparison charts | plan-to-network crosswalks, affiliate network charts, product participation grids | best proof of path complexity |

| contract forms and amendments | participation agreements, schedule references, leasing notices, affiliate access clauses | strongest precedence evidence |

| EOBs or remittance examples | official training materials, litigation exhibits, regulator exhibits, authenticated de-identified samples | real-world adjudication proof |

| payer bulletins or provider notices | effective-date changes, network expansions, leasing elections, fee schedule changes | timing and change control |

The initial carrier list should center on the large national names the request identified: Delta Dental, Cigna, MetLife, Aetna, UnitedHealthcare, and Humana. The execution should stay open to network intermediaries that matter operationally, such as dental networks, rental-network administrators, and TPAs that appear inside those carrier relationships.

### state-law source stack

For the legal section, gather:

| source type | collection target | reason |

|---|---|---|

| statutory text | state statutes on rental networks, leased networks, silent PPOs, provider notice, opt-out, and assignment of network rights | controlling language |

| regulations and bulletins | insurance department rules, FAQs, enforcement guidance | practical interpretation |

| bill summaries and legislative history | short explanations of why a state enacted a protection | context and scope |

| carrier or law-firm implementation notes | how insurers and provider counsel interpret the statute | useful but secondary |

### real-world example stack

For Joey and Sandi-style examples, prioritize sources that show the chain rather than merely assert it:

| example type | preferred source | minimum standard |

|---|---|---|

| EOB showing unexpected discount | official or authenticated EOB with visible payer, network name, schedule note, and date | enough detail to identify product and network path |

| participation map showing indirect access | official carrier/network chart or provider portal screenshot | visible branding and date |

| provider notice announcing network lease or shared access | official notice with effective date and opt-out details | current or archived with date |

| litigation or regulatory exhibit | filed exhibit showing contract or adjudication behavior | use carefully, verify context |

## execution workflow

The research should run in six passes so the final handoff stays organized.

### pass one

Build the terminology and law baseline. Define silent PPO, leased network, shared network, umbrella network, TPA, and direct contract from legal or regulator sources first, then note where industry usage drifts. The output from this pass is a glossary with "use in article," "do not overstate," and "common confusion" notes.

### pass two

Map each major carrier's current public network structure. The point is not to collect every product. The point is to identify where the public record already shows more than one contract path or more than one fee schedule route.

### pass three

Collect precedence evidence. This is the hardest pass. Look for clauses that answer questions like these: if a provider has both a direct PPO agreement and access through an affiliate or leased network, which schedule applies; does the more specific contract control; is there language about supersession, priority, or conflict; is election at the contract, TIN, or location level; does the payer reserve unilateral routing for certain products.

### pass four

Collect state-law examples. Build a 50-state scan, but only elevate states with explicit, citable leasing or rental-network language into the core article table. For each state, record whether the law applies broadly or only to certain plans or policy forms, whether notice is required, whether the provider can opt out, and whether there are exceptions for affiliates or existing contract rights.

### pass five

Build the Joey and Sandi scenarios from evidence. These examples should be de-identified composites only if a direct example cannot be shown. Each example should have a documentary spine: one contract or participation map, one EOB or notice, and one explanation of the path that caused the payment.

### pass six

Rate the claims. Every potential article statement should be tagged with one of four statuses:

| rating | use standard | example use |

|---|---|---|

| strong | supported by current primary source and, where needed, a second confirming source | article body |

| qualified | supported, but only for a carrier, state, product, or time period | article body with caveat |

| weak | plausible, but evidence is indirect, old, or inconsistent | keep out unless Joey can verify |

| avoid | contradicted, overbroad, or depends on proprietary facts not in hand | do not publish |

## planned deliverables and report structure

The finished handoff should be structured so Joey can scan from high-confidence facts to edge cases.

### executive summary

A short top section with:

- the thesis in one sentence

- the strongest carrier examples

- the best state-law takeaways

- the main publication risks

- the top unresolved questions

### carrier comparison table

This should be the main operational table.

| carrier | payer or brand | product or network | contract path shown | evidence type | fee schedule identified | effective date shown | precedence evidence | confidence | notes for Joey |

|---|---|---|---|---|---|---|---|---|---|

The point of this table is not to prove a universal rule by carrier. It is to show that different paths exist and to tie each example to a specific product, schedule, and date.

### definitions table

| term | working definition | what it is not | best primary source | article-safe wording | risk note |

|---|---|---|---|---|---|

This table should solve the vocabulary problem before the article starts comparing claims.

### state-law summary table

| state | statute or regulation | applies to | notice required | opt-out right | exceptions or limits | latest effective date or amendment | source quality | publication note |

|---|---|---|---|---|---|---|---|---|

This table should favor statutes with explicit rental-network or leased-network language and should clearly mark plan-scope limits.

### Joey and Sandi scenario table

| scenario label | visible documents | payer and product | path that caused payment | what surprised the practice | best explanation supported by evidence | claim strength | image or screenshot candidate |

|---|---|---|---|---|---|---|---|

### claim-risk table

| proposed article claim | rating | reason | best support | missing proof | publish as written | safer wording |

|---|---|---|---|---|---|---|

### checklist

A short, practical verification checklist at the end:

| verification step | what to request | where it usually appears | why it matters |

|---|---|---|---|

## decision flow for the final handoff

```mermaid

flowchart TD

A[Start with a paid or discounted claim] --> B{Is there a direct contract for this payer or product?}

B -->|Yes| C[Identify payer, product, TIN, NPI, location, and effective date]

B -->|No or unclear| D[Check shared, leased, umbrella, or TPA access]

C --> E{Does contract contain precedence or conflict language?}

D --> F[Collect participation map, provider notice, network admin guide, and EOB]

E -->|Yes| G[Match fee schedule and effective date to clause language]

E -->|No| H[Look for payer memo, EOB notation, or product-specific processing rule]

F --> I{Can the indirect path be tied to a specific network and product?}

I -->|Yes| J[Classify as supported indirect participation example]

I -->|No| K[Mark as ambiguous and hold for Joey review]

G --> L{Is state law relevant to notice, leasing, or opt-out?}

H --> L

J --> L

L -->|Yes| M[Check statute scope, exceptions, notice, opt-out, and effective date]

L -->|No| N[Rate claim on carrier evidence alone]

M --> O[Assign claim rating: strong, qualified, weak, or avoid]

N --> O

```

## red flags, exclusions, and Joey review points

Several statements should be treated as presumptively unsafe until the evidence is in hand.

"Direct contracts always override shared or leased network fee schedules" is unsafe as a blanket statement. The research should assume the answer may vary by contract language, product, affiliate relationship, and adjudication rules until a clause proves otherwise. The uploaded brief flags this exact point as a risk area. fileciteturn0file0L43-L43

"You can always opt out" is also unsafe. State protections may vary by plan type, and some access routes may be embedded in existing contract rights or affiliate structures. That risk is also identified in the brief. fileciteturn0file0L44-L47

"A TPA is the same thing as a PPO network" should be treated as likely false or at least oversimplified. The research should separate administrative role from network-rights role unless a source uses the terms in a specific, limited way. The brief flags this as a risk area too. fileciteturn0file0L45-L45

"The payer made a claim error" should not appear in the article unless the documentation clearly shows a mismatch between contractual rights, product routing, and adjudication. Otherwise, the safer framing is that the payment appears inconsistent with the available records and needs contract-level review. fileciteturn0file0L46-L46

The final handoff should set aside a separate Joey-review section for four kinds of items:

| Joey review item | why it needs review |

|---|---|

| proprietary contracts or amendments not publicly available | strongest evidence may be private |

| office-specific EOB patterns | may show behavior not reflected in public documents |

| carrier relationship changes in progress | public pages can lag operational reality |

| statements about intent, error, or compliance failure | legal exposure is higher than for descriptive claims |

## ready-to-run research prompt

Use this exact research framing when execution begins:

Research current U.S. dental PPO network pathways for major carriers and related administrators. For each carrier example, identify the contract path, payer or product, provider or location scope, fee schedule reference, and effective date. Prioritize official English-language materials from the last five years, then supplement with state statutes, regulations, and authenticated EOB or participation-map examples. Do not draft article prose. Rate each possible article claim as strong, qualified, weak, or avoid. Build carrier and state-law tables, collect real-world Joey and Sandi examples where documentation supports them, and isolate all legal or evidentiary issues that require Joey's review before publication.

That prompt matches the uploaded article brief's core angle, source expectations, and risk controls. fileciteturn0file0L5-L18 fileciteturn0file0L50-L56