What changed
FACT: On 2026-06-04 the tri-agencies (IRS/DOL/HHS) published final rules on 'Federal Independent Dispute Resolution Operations' under the No Surprises Act. The rules finalize new disclosure requirements (plans/issuers must communicate using claim adjustment reason codes (CARCs) and remittance advice remark codes (RARCs) as specified in guidance on any paper or electronic remittance advice sent to a non-contracted entity), and amend the open-negotiation period, IDR initiation, dispute eligibility review, and batching procedures. Source: federalregister.gov/documents/2026/06/04/2026-11140.
Why now
FACT: These are FINAL rules just published (2026-06-04). INFERENCE: Final rules trigger a compliance scramble — payers must reconfigure remittance advice to carry mandated CARC/RARC codes, and providers must adapt open-negotiation and IDR-initiation workflows to the amended eligibility/batching procedures. That reconfiguration window is the sales window.
Converging signals
FACT: Three signals meet at one point — (1) a federal rule change, (2) a defined forced class (group health plans, issuers, and out-of-network providers/facilities that initiate or respond to disputes), and (3) an existing government portal (the CMS Federal IDR portal) that filings flow through. INFERENCE: CARC/RARC standardization + batching eligibility rules make the paperwork newly machine-structurable, which is exactly what software can exploit.
Customer pain
HYPOTHESIS (not in source): OON providers report the Federal IDR process is slow, procedurally unforgiving (a mis-scoped batch or a missed eligibility criterion gets the dispute thrown out), and gated by non-trivial per-dispute administrative fees — so a rejected filing wastes both the fee and staff time. The source proves the process and its amended eligibility/batching rules exist; it does NOT itself document complaint volume, so treat pain magnitude as unproven.
Who pays
OON provider groups (physician staffing, ER/anesthesia/radiology/pathology practices, ambulatory surgery centers, air-ambulance and lab providers) and the revenue-cycle-management (RCM) firms and billing teams that file on their behalf. Secondary: payers needing CARC/RARC remittance-advice compliance. Primary wedge = the provider/RCM side, which files to WIN money and therefore has direct ROI per dispute.
Solved today
FACT (from rule): filers interact directly with the CMS Federal IDR portal and manual open-negotiation notices. INFERENCE: today this is done manually by billing staff, by RCM outsourcers, or by specialist IDR-consulting firms that take a percentage of recovered amounts. Existing vendors (e.g. IDR-management / OON reimbursement specialists) already charge for this.
Why current solutions are bad
INFERENCE: manual portal filing is error-prone against strict eligibility/batching rules; percentage-of-recovery consultants are expensive (a cut of every award); billing staff lack tooling to auto-detect which line items are IDR-eligible, to legally batch them, and to apply the exact CARC/RARC codes the new rule mandates. Deadlines (open-negotiation window, initiation window) are easy to miss and non-recoverable.
Proposed product
A micro-SaaS that ingests a provider's remittance/denial data (835/ERA or CSV upload), (1) flags IDR-eligible items using the finalized eligibility criteria, (2) auto-groups them into rule-compliant batches, (3) generates open-negotiation notices and tracks the statutory open-negotiation/initiation clocks with alerts, (4) validates/auto-applies required CARC/RARC codes, and (5) assembles the eligibility package and files/tracks status against the CMS Federal IDR portal. Monetize per dispute filed + per-seat subscription for billing teams.
MVP version
Start narrow and read-only-plus-assemble before full auto-submit: a deadline-tracker + eligibility/batching engine + CARC/RARC validator that ingests an ERA/CSV, outputs a ready-to-file eligibility package and a filled open-negotiation notice, and emails deadline alerts. Charge per package assembled. Add portal auto-submission (the founder's proven government-portal-integration pattern from the FMCSA ELDT app) as v2.
30-day build
Read the final rule + CMS IDR portal guidance and the CARC/RARC code guidance end-to-end. Map the exact eligibility, batching, open-negotiation, and initiation data fields. Build the eligibility-classifier + batching + CARC/RARC validator on sample ERA data. Interview 8-12 OON billing managers / small RCM firms to confirm pain, current spend, and willingness to pay; recruit 2-3 design partners.
60-day build
Ship the assemble-and-alert MVP (ingest → eligible-item detection → compliant batch → open-negotiation notice + deadline tracker → exportable eligibility package). Onboard design partners on real disputes. Instrument every rejection reason to harden the eligibility engine.
90-day revenue plan
Convert design partners to paid: per-package/per-dispute fee + per-seat billing-team subscription. Add CMS portal auto-submission. Sell outward to comparable OON specialty practices and small RCM firms via demonstrated recovery/time-saved, not relationship sales.
Distribution path
Content + tool-led: publish a free 'IDR eligibility & CARC/RARC checker' and a deadline calculator as lead magnets; target RCM/medical-billing communities, OON specialty billing forums, medical-billing LinkedIn/associations, and RCM outsourcers who can white-label. Demonstrated value (packages that win) is the sales motion.
Pricing hypothesis
Per-dispute/per-package filing fee (est. $15-60/dispute) + per-seat subscription for billing teams (est. $99-399/seat/mo). Wedge = undercut percentage-of-recovery IDR consultants with flat, cheaper software.
Technical difficulty
Moderate. Core logic (eligibility rules, batching constraints, CARC/RARC mapping, deadline math) is deterministic and solo-buildable. Real work is ingesting 835/ERA formats and integrating the CMS Federal IDR portal — but the founder has already shipped a per-filing federal-portal submission product (FMCSA ELDT), so this is squarely in his proven wheelhouse.
Legal / regulatory risk
Moderate. This touches PHI/claims data → HIPAA obligations (BAAs, encryption, access controls) apply; that is a build cost, not a blocker, and is itself part of the moat. Founder does not need to become a licensed clinician or attorney. Filing is submitting on the customer's behalf to a government system — the same pattern already operated for ELDT. Do NOT treat CMS as a 'platform' that can deplatform the tool.
Platform dependency
Low platform-policy risk: the counterparty is a government portal (CMS Federal IDR), not a commercial platform with ToS deplatform power. Dependency is on portal stability/format changes, manageable.
Founder fit
VERY HIGH / MAXIMAL. Exact shape of the founder's proven edge: a federal rule compels a defined class to file/report/register with a government portal, and a solo operator builds the submission/automation layer and charges per transaction + per seat — identical to his shipped FMCSA ELDT product. Systems-thinking, public-records, and compliance-monitoring strengths all apply. Only novel demand is HIPAA handling of claims data.
Breakout potential
Strong. INFERENCE: hundreds of thousands of Federal IDR disputes are filed annually across thousands of provider groups and payers (PIE is inferred, not stated). Expansion paths: payer-side CARC/RARC remittance compliance, state surprise-billing/arbitration equivalents (state pass-through replication into ~dozens of near-identical markets), and adjacent OON reimbursement analytics.
Final recommendation
PURSUE — high-conviction, high founder-fit. This is the founder's exact proven pattern (federal rule → forced filer class → government-portal submission tool → per-filing + per-seat monetization) on a just-finalized rule. De-risk by starting with the assemble-and-alert MVP (no PHI-heavy auto-submit yet) and validating price/pain with design partners before building full portal auto-submission.
Next action
Read the final rule (2026-11140) plus CMS Federal IDR portal + CARC/RARC guidance, extract the exact eligibility/batching/open-negotiation/initiation data fields, and line up 8-12 OON billing-manager/RCM interviews to confirm current spend and price for a filing-assembly tool.