Pivotal Health

A full-service IDR platform — technology plus hands-on service — that manages out-of-network payment disputes end-to-end. It integrates with all major Revenue Cycle Management (RCM) platforms and runs in the background. Three core capabilities:

• Claim Identification (eligibility engine) — surfaces high-value, often-overlooked IDR-eligible claims while filtering out ineligible / non-compliant ones to avoid risk. (Notably, ~20% of all disputes filed industry-wide are actually ineligible — a real pain point.)
• Custom Position Statements — a proprietary engine analyzing millions of data points to build data-backed arguments tailored by payer, billing code, and arbitrator (IDRE) to maximize win rates.
• Intelligent Batching — automatically groups eligible claims per federal and state rules to cut IDR filing fees while staying compliant.

Customers: Emergency medicine, anesthesiology, radiology, surgery, air ambulance groups, plus hospitals & health systems — "providers of all sizes."

Pivotal's paying customer is the healthcare provider — physician groups (emergency medicine, anesthesiology, radiology, surgery, air ambulance) and hospitals / health systems, from small practices to large PE-backed groups. Not the patient, and not the insurer.

How the money flows

1. A provider treats an out-of-network patient → the insurer underpays the claim.
2. Pivotal files an IDR dispute on the provider's behalf and (usually) wins a higher payment.
3. The insurer pays the provider the recovered amount.
4. Pivotal takes a success fee — a cut of what it recovered — from the provider, after the provider has been paid.

Net effect: the provider is the customer, but on a contingency model — Pivotal earns only when it recovers dollars the provider wouldn't otherwise have collected, which makes it a low-friction sale. It also means Pivotal's revenue is a slice of recovered dollars — which is precisely why the Financial Systems role exists.

Finding the opportunities — integration, not manual flagging

Pivotal doesn't wait for providers to hand-pick cases. The provider sets up a simple 835/837 file feed (837 = the claim submitted; 835 = the remittance showing what the insurer actually paid or denied). Pivotal's eligibility engine continuously scans that feed, compares billed vs. paid, and automatically flags underpaid, IDR-eligible out-of-network claims — filtering out ineligible / risky ones. Setup takes ~2 weeks, no IT overhaul, then it runs in the background.

What Pivotal manages — "from open negotiation to final payment collection"

Pivotal runs the entire arc, not just arbitration. Four stages per flagged claim:

1. Identification — eligibility engine surfaces the underpaid OON claim from the 835/837 feed.
2. Open negotiation — Pivotal initiates and runs the mandatory 30-business-day negotiation directly with the payer. Many claims resolve here, before IDR.
3. IDR filing — if negotiation fails, Pivotal files within the 4-business-day window, batches similar claims to cut fees, and builds the data-backed position statement for the arbitrator.
4. Final payment collection — tracks the dispute through to recovered dollars landing with the provider.

Why this matters for your role: because Pivotal touches a claim from negotiation through final collection, the financial systems you'd own must attribute outcomes accurately at every stage — recovered in negotiation vs. won at IDR vs. still pending — across batched, multi-payer claims. That stage-by-stage tracking is the product problem behind the title.

What "cutting fees" means — the two IDR fees

Every IDR dispute incurs two distinct fees (2025 figures):

Batching turns a fixed per-dispute cost into a near-fixed per-batch cost. Filing 100 similar claims separately = 100 × $115 admin ($11,500) + 100 individual IDRE fees. Batching them into one dispute = a single $115 admin fee + one batched IDRE fee. The per-dispute admin fee is the biggest, most direct saving.

The No Surprises Act (effective 2022) protects patients from surprise out-of-network bills (ER visits, anesthesiologists, etc.). It removes the patient from the fight and instead sends provider–insurer payment disputes to Independent Dispute Resolution (IDR): a certified third-party arbitrator picks one side's "final offer" (baseball-style arbitration).

The catch: the law cut provider out-of-network reimbursements by ~40%, and the IDR process is administratively brutal — strict eligibility rules, tight deadlines, per-claim fees, state vs. federal variation. Most providers leave money on the table because filing well is hard. That gap is the entire business.

Providers initiate 99.9% of disputes and win the vast majority — but two-thirds of decisions blow past the 30-day deadline. A market that's huge, growing, provider-favorable, and operationally messy.

The space splits into three groups. Pivotal competes most directly with the middlemen — third-party firms that file IDR on providers' behalf.

When Pivotal sends an open negotiation notice or files an IDR case, who responds? Nominally the health plan / insurer — UnitedHealthcare, Aetna, Cigna, Elevance (Anthem), the BCBS plans, plus self-funded employer plans and their TPAs. In practice, insurers rarely use their own staff: they outsource negotiation and dispute defense to specialized out-of-network "cost-containment" vendors — the structural mirror image of Pivotal.

How does the team think about defending against HaloMD's scale — is the wedge product depth, RCM distribution, or service quality?

What's the product roadmap risk if the No Surprises Act or IDR rules get reformed? How diversified is the revenue beyond federal IDR?

For the Financial Systems role specifically — what's broken or manual today in how you track and report recovered dollars to customers?

How does CMS's new centralized IDR Gateway change the platform strategy?

What does success look like for this role in the first 6–12 months, and who are the key cross-functional partners (finance, eng)?

Post-rebrand, what's the next chapter — staying focused on IDR, or expanding into the broader provider-underpayment space?