What changed
FACT (Federal Register, 2026-06-04 rule): the Federal IDR Operations rule standardizes out-of-network remittances with machine-readable CARC/RARC denial/payment codes and disclosures, making automated IDR-eligibility determination technically possible for the first time. FACT (HF blog posts): current open-weights models (GLM-5.2 long-horizon agent model) and sub-35M-parameter OCR (PP-OCRv6) now make self-hosted document extraction and long-horizon follow-up pipelines cheap enough to run inside a customer's infrastructure without frontier-API costs or PHI egress.
Why now
The rule creates a fresh, standardized data surface that legacy RCM vendors have not yet fully exploited; whoever ships CARC/RARC-native IDR triage in the next 6-12 months rides the compliance transition. Open-model economics simultaneously remove the main objection (PHI leaving the building) to LLM-based denial processing. HYPOTHESIS: incumbents will close this gap within 12-24 months, so the window is the transition period.
Converging signals
(1) Regulation: mandatory machine-readable CARC/RARC codes in OON remittances (federalregister.gov 2026-11140). (2) AI capability: GLM-5.2 open-weights long-horizon agentic model enables self-hosted multi-week dispute follow-up loops. (3) AI capability: PP-OCRv6 (1.5M-34.5M params) enables cheap on-prem extraction from scanned EOBs/remittances. The convergence is real: the regulation creates the structured input, the open models make private processing of it economical.
Customer pain
HYPOTHESIS (no demand_evidence supplied — this is inferred, not proven): out-of-network providers (emergency physician groups, anesthesia, radiology, labs, air ambulance) lose recoverable revenue because IDR eligibility determination, deadline tracking, and dispute-package assembly are manual, deadline-bound, and clerically expensive. The provided demand_evidence array is EMPTY: the system has zero captured complaints, job postings, or spend signals for this specific pain. That absence must be weighed (though a stored lesson, confidence 0.85, notes the engine is structurally demand-blind, so absence here is weak evidence of absence).
Who pays
HYPOTHESIS: medical billing companies / RCM firms serving OON-heavy specialties (the reachable wedge — one billing company aggregates dozens of provider groups), and secondarily mid-size physician groups directly. They monetize recovered denials, so a per-dispute or contingency-adjacent fee maps directly to recovered dollars.
Solved today
HYPOTHESIS: manual review of remittances by billing staff; specialist IDR services (e.g., HaloMD) and law firms handling disputes for a contingency cut; generic denial-management modules in RCM suites (Waystar et al.) that predate the machine-readable CARC/RARC mandate.
Why current solutions are bad
HYPOTHESIS: manual triage misses IDR-eligible claims and statutory deadlines; contingency services take a large cut; incumbent denial-management tools are payer-code-generic rather than IDR-workflow-native, and none currently exploit the new standardized code mandate end-to-end. Unverified — needs 5-10 billing-company interviews.
Proposed product
A pipeline that ingests 835s/EOBs (PP-OCRv6 for scanned docs), parses the now-mandatory CARC/RARC codes, applies deterministic IDR-eligibility rules (NSA scope, open-negotiation windows, deadlines), assembles the dispute package for the federal IDR portal, and runs agentic long-horizon follow-up (deadline tracking, negotiation-window letters, resubmission). Self-hosted open-model deployment as the PHI trust wedge. Note the founder-fit rhyme: like his shipped FMCSA ELDT product, this is 'read a federal rule, build the submission layer against a federal portal, charge per filing' — except here the filer is incentivized (money recovery) rather than compelled, which is a weaker demand structure than a true forced-buyer mandate.
MVP version
CLI/web tool: upload a batch of 835 remittance files → parsed CARC/RARC extraction → IDR-eligibility flag with rule citation and deadline calendar → generated dispute-package draft. Skip self-hosting initially; run cloud with a BAA. Defer the agentic follow-up. 4-8 weeks solo with AI assistance.
30-day build
Validate before building: mine r/medicalbilling, r/CodingandBilling, HBMA forums and billing-company job postings for IDR/denial-triage pain (fills the demand_evidence hole); read the rule's CARC/RARC technical spec end-to-end; build the 835 parser + eligibility rules engine against sample remittances; get 5 billing-company conversations.
60-day build
Pilot with 1-2 billing companies on historical remittance batches ('here are the IDR-eligible dollars you missed last quarter' — a demonstrated-value sale, which matches this founder's selling style). Sign BAAs. Harden the dispute-package generator against real federal IDR portal requirements.
90-day revenue plan
Convert pilots to per-dispute pricing ($25-75/package) or per-provider-group monthly ($300-800). Realistic first revenue at day 120-180 given healthcare BAA/pilot cycles — inside the founder's stated 180-day window but at the far end.
Distribution path
Direct outreach to billing companies with a free retrospective scan of their historical denials (demonstrated value, not relationship sales); HBMA/AAPC communities; content on the new CARC/RARC mandate. No low-friction self-serve channel exists — this is the weakest link.
Pricing hypothesis
Per-dispute package fee ($25-75) mirroring his ELDT per-upload model, or per-group SaaS. Contingency pricing maximizes revenue but adds collection complexity — avoid initially.
Technical difficulty
Moderate. 835/CARC/RARC parsing is deterministic and well-specified; IDR eligibility rules are codifiable; OCR and open-model hosting are commodity. The hard parts are per-customer self-hosted deployments (a support tax a solo founder should defer) and correctness liability on eligibility/deadline determinations.
Legal / regulatory risk
HIPAA (BAA required, breach liability); implicit reliance risk if the tool wrongly flags/misses eligibility and a provider forfeits a dispute deadline; possible unauthorized-practice concerns if packages drift into legal argumentation. Not prohibitive, but real — needs disclaimers and E&O insurance.
Platform dependency
Federal IDR portal process and fee structure change by rulemaking (they have changed repeatedly); CARC/RARC spec is stable. Moderate regulatory-drift dependency, low platform-ban risk.
Founder fit
Mixed. Strong pattern match to his proven edge (federal rule → parse who must act → build portal submission layer → per-filing fee) and to his systems/automation strengths. But it collides with his avoid-list: healthcare is a heavy-compliance, long-trust-cycle domain where he has no operational credibility (unlike trucking-adjacent ELDT), and self-hosted-in-customer-infra deployment is the opposite of low-touch. Stored lesson (confidence 0.80) favors government-portal mandate shapes — but that lesson describes FORCED filers; here the payer is forced to emit codes while the provider (the buyer) merely has a money incentive to dispute.
Breakout potential
High if it works: IDR triage expands naturally into full denial management, payer-behavior analytics, and negotiation benchmarking — a large RCM market. But that same size means funded incumbents (Waystar, Adonis, Akasa, Candid) can add CARC/RARC-native IDR triage as a feature.
Final recommendation
PARK pending demand validation — do not build yet. The convergence is technically real and the founder-fit rhyme with ELDT is genuine, but with an empty demand_evidence array, no healthcare credibility, and a crowded incumbent field, this scores as a B-/C+ 'revisit with evidence' rather than a build-now. Spend 2 weeks (not 2 months) on demand mining and 5 billing-company conversations; if billing companies confirm they pay humans for IDR triage today, upgrade to build; otherwise drop.
Next action
Add provider-side demand sources to the engine (r/medicalbilling, HBMA job boards, RCM job postings mentioning 'IDR'/'No Surprises Act') and re-score; in parallel, cold-contact 5 billing companies serving ER/anesthesia groups with the retrospective-scan offer to test willingness to pay.