What changed
FACT (per the cited Federal Register rule): federal IDR operations rules now require standardized, machine-readable CARC/RARC denial and payment reason codes plus disclosures in out-of-network remittances. FACT (per cited sources): sub-35M-parameter 50-language OCR (PP-OCRv6) is self-hostable on CPU, and frontier reasoning cost-per-task dropped (GPT-5.6 performance-per-dollar claim). Together these make automated parsing of EOBs/remittances and rules-based IDR-eligibility judgment technically cheap for the first time.
Why now
The rule creates a discrete compliance-driven data-format change: payers must emit standardized codes, so provider-side tooling can finally parse denials deterministically instead of via manual coder interpretation. Tools built now ride the enforcement window. HYPOTHESIS: incumbent RCM vendors will absorb this within 6-18 months, so any solo window is short.
Converging signals
(1) Regulation: mandatory CARC/RARC codes in OON remittances (federalregister.gov 2026-11140). (2) AI capability: PP-OCRv6 self-hostable OCR removes cloud-OCR cost/BAA friction for scanned EOBs (huggingface.co). (3) AI economics: cheaper frontier reasoning makes per-claim eligibility judgment viable (openai.com). The convergence is genuine: standardized input + cheap extraction + cheap reasoning.
Customer pain
HYPOTHESIS (no demand_evidence supplied in input): provider billing teams and RCM firms struggle to identify which denied/underpaid OON claims are IDR-eligible within the statutory window and to assemble compliant dispute packages; this is widely believed to be manual, coder-intensive work. The rule itself proves the workflow must change, but NO pain complaints, forum posts, or hiring data were provided to prove buyers feel urgent pain today.
Who pays
HYPOTHESIS: (a) small/mid OON-heavy specialty groups (ER staffing, anesthesia, radiology, air ambulance) and their third-party billing companies; (b) certified IDR entities and IDR consultancies needing throughput tools. Critically, the mandate binds PAYERS (plans/issuers) to emit codes — it does NOT compel providers to buy anything. This is NOT the ELDT forced-filer shape: the compelled party and the prospective customer are different entities, so there is no forced buyer for this tool.
Solved today
HYPOTHESIS: manual review by certified coders/billers reading 835s and EOB PDFs; spreadsheets tracking IDR deadlines; specialized IDR service firms handling disputes on contingency; large RCM platforms (Waystar, Availity, Adonis, Candid) handling denial management generally. No supplied evidence of current spend — flagged as unproven.
Why current solutions are bad
HYPOTHESIS: manual triage misses statutory deadlines and eligible claims; contingency IDR firms take large cuts; big RCM suites are expensive and slow to adopt the new code standards. Plausible but unevidenced in the input.
Proposed product
A narrow micro-SaaS: upload 835 remittances / scanned EOBs → self-hosted OCR + deterministic CARC/RARC parser → rules engine (from the IDR rule text) flags IDR-eligible claims with deadline clocks → LLM drafts the open-negotiation notice and IDR initiation package. Priced per claim screened or per dispute package, not per seat.
MVP version
CLI/web tool: PP-OCRv6 + X12 835 parser + hardcoded eligibility ruleset from the final rule + deadline calculator + templated dispute-package generator. Buildable solo in 2-4 weeks. The hard part is not the software — it is PHI handling (HIPAA/BAA) and getting a stranger's claims data to demo against.
30-day build
Do NOT build yet. Validate demand first: mine r/CodingandBilling, r/HealthInsurance, HFMA/AAPC forums, and billing-company job postings for IDR-triage pain; interview 5 OON-heavy billing companies; confirm whether the CARC/RARC requirement has an enforcement date payers are actually meeting. Build only a de-identified demo on synthetic 835s.
60-day build
If (and only if) validation surfaces buyers: sign one billing company as design partner under a BAA, run their backlog through the screener, measure recovered-dollar lift. Otherwise kill.
90-day revenue plan
HYPOTHESIS: $500-2,000/mo from 1-3 billing companies at per-claim pricing, or a rev-share on recovered IDR awards. Low confidence — healthcare buying cycles plus HIPAA setup routinely exceed 90 days for an outsider with no RCM relationships.
Distribution path
Weak for this founder: no existing healthcare-billing audience. Possible channels are billing-company communities (AAPC, HFMA), Reddit complaint-mining, and partnering with IDR consultancies as a white-label tool. All are trust-gated; none are the demonstrated-value self-serve motion he prefers.
Pricing hypothesis
Per-claim screening fee ($0.50-2) plus per-dispute package fee ($25-75), or contingency share via a partner IDR firm. Per-transaction pricing matches his ELDT model, but only after a BAA-gated sales process the ELDT business never required.
Technical difficulty
Low-moderate: 835/EDI parsing is well-trodden, OCR is solved per the cited signal, the eligibility rules are published. Difficulty is regulatory-operational, not technical.
Legal / regulatory risk
HIGH: EOBs/remittances are PHI → HIPAA applies, BAAs required, breach liability real. Sending PHI to a frontier LLM API requires a BAA-covered deployment. Also risk of the IDR rule's timelines shifting (the IDR regime has been litigated repeatedly — HYPOTHESIS based on general knowledge, not supplied sources).
Platform dependency
Low platform risk (no app store, no scraping). Moderate regulatory dependency: product value is tied to the IDR rule surviving as written.
Founder fit
LOW-MODERATE (3/10) despite the surface resemblance to ELDT. The ELDT edge was: mandate compels a party to FILE into a government portal, and he charges that compelled party per filing. Here the mandate compels payers to EMIT codes; the tool's buyer (providers/billers) acts voluntarily, in a HIPAA-regulated domain he explicitly avoids (heavily regulated medical), with trust-gated distribution and entrenched funded competitors. He has zero healthcare-billing credibility or network.
Breakout potential
If it worked, expansion into general denial management is large — but that path runs directly into well-funded incumbents (Adonis, Anomaly, Waystar) and becomes an enterprise-sales business, which he avoids.
Final recommendation
PASS for the 30-90-day cash goal. The convergence is real and the technical build is easy, but demand is unevidenced in the input, the buyer is not compelled, HIPAA compliance violates his stated avoid-list, and distribution is trust-gated. Revisit only if complaint-mining surfaces billing companies explicitly asking for IDR triage tools, or if a partnership with an existing IDR consultancy (they hold the BAAs and clients) lets him sell the tool B2B2B without touching PHI sales himself.
Next action
Spend ≤4 hours complaint-mining (r/CodingandBilling, AAPC forums, HFMA, LinkedIn/Indeed postings for 'IDR specialist' or 'No Surprises Act analyst') to test whether real PAIN/HIRING evidence exists; log findings and re-score before writing any code.