What changed
FACT (from source text): CMS published a CY2027 OPPS/ASC proposed rule on 2026-07-07 that includes a Request for Information on 'potential approaches to improve comparability and standardization' of Hospital Price Transparency data reported in machine-readable files and consumer-friendly displays. The same rule proposes expanding prior authorization to additional Botulinum Toxin Injection services, updates the Hospital OQR and ASCQR quality reporting programs, and would have accrediting organizations assess EMTALA administrative compliance during surveys.
Why now
HYPOTHESIS: an RFI is the conventional precursor to a schema/standard change in a later final rule, so a vendor who builds against the signaled direction now has a 12-24 month head start. Counter-fact: an RFI creates NO new obligation, NO new schema, and NO deadline. The source text does not state a comment-close date or any effective date for a changed MRF schema. The only *live* obligation here (hospital MRF publication) has existed since the 2021 Hospital Price Transparency rule — it is a five-year-old mandate, not a new one.
Converging signals
Weak convergence. There is exactly ONE signal in the input: the proposed rule itself, which is also the sole demand-evidence item. The 'convergence' of rule + filer class + portal is structurally present but is an artifact of how the opportunity was derived from the document, not of independent signals meeting. No complaint data, no hiring data, no pricing data was supplied.
Customer pain
HYPOTHESIS (not evidenced in input): hospitals must maintain a conforming MRF and a consumer-friendly display, face per-day civil monetary penalties for noncompliance, and their chargemaster/payer-contract data changes constantly, so the file drifts out of conformance between annual refreshes. CMS has historically issued warning letters and corrective action plans before penalties. None of this is in the provided source text; it is background inference and must be verified before any build.
Who pays
Hospital revenue-cycle / compliance departments (~6,000 US hospitals — inference, no count in source). ASCs for the ASCQR and prior-auth pieces. This is the fatal problem: a hospital compliance buyer is a committee purchase running through IT security review, a BAA, vendor risk assessment, and often a GPO contract. That is the enterprise-procurement-only channel the founder explicitly avoids. It is categorically unlike the ELDT registry precedent, where the buyer was an individual training provider paying a per-upload fee with a credit card.
Solved today
Well and thoroughly. HYPOTHESIS based on market knowledge, not the input: Turquoise Health, Serif Health, Panacea, Cleverley + Associates, Health Catalyst/Vitalware, and Craneware all sell MRF generation, validation, and monitoring. CMS itself publishes a free open-source MRF validator and a required CMS template layout. Hospital chargemaster vendors bundle transparency output into contracts hospitals already hold. Several vendors give the validated data away free to fund a downstream analytics business.
Why current solutions are bad
Honestly? It mostly isn't. The strongest genuine complaint is that validation is point-in-time rather than continuous, and that consumer-display and MRF drift apart. That is a feature gap inside existing products, not an unserved market — and it is a feature any of the six incumbents ships in a quarter once a final rule names a schema.
Proposed product
A continuous MRF conformance monitor: ingest the hospital's posted file, validate against the CMS template + published schema, diff every refresh, alert on drift, and produce an audit trail sized for a CMS corrective action plan. Priced per facility per year.
MVP version
Schema validator wrapping the CMS open-source validator, a crawler that fetches each hospital's posted MRF from its .well-known/ location weekly, a diff engine, and an alert/report layer. Technically a 30-45 day build for this founder — the build is not the constraint.
30-day build
Do NOT build. Spend 30 days killing or resurrecting the thesis: read the actual RFI text at the cited URL to see whether CMS names a candidate schema; count how many hospital MRFs currently fail the CMS validator (this is free, public, and scriptable — it is the one asset here worth producing); and cold-call 15 hospital compliance officers to learn who they already pay and what they pay.
60-day build
If and only if the failure-rate scan shows widespread nonconformance AND interviews show the incumbents are not already contracted, file an RFI comment under your own name to establish standing, and build the validator against the current template.
90-day revenue plan
No credible 90-day revenue path. Hospital contracting alone consumes 90-180 days after a verbal yes. Any revenue in this window would come from selling the compliance-failure scan as a one-off data report — a $2-5k report, not a business.
Distribution path
Poor. There is no self-serve motion into hospital compliance. The founder's stated distribution strength — demonstrated value, no relationship sales — does not function against a buyer that requires a security questionnaire before the demo.
Pricing hypothesis
$3,000-12,000 per hospital per year is the plausible band, which is exactly where incumbents sit and where a solo vendor has no cost advantage that matters to a hospital.
Technical difficulty
Low. This is the least interesting thing about the opportunity.
Legal / regulatory risk
Low. MRF data is public by mandate; no PHI. But hospitals will demand a BAA and SOC 2 anyway, and SOC 2 is a real cost and a real calendar.
Platform dependency
None. Correctly, no platform-policy risk applies — CMS cannot deplatform a compliance tool.
Founder fit
Mixed, and the mandate shape is misleading here. The system's own heuristic (confidence 0.80) says government-portal mandate opportunities fit this founder best. That heuristic is doing the work of a prior, and fresh evidence overrides it: the heuristic's causal mechanism is that a compelled filer is an individually-reachable buyer with a credit card. A hospital is not. The ELDT registry analogy breaks precisely where it matters — on the buyer, not on the mandate.
Breakout potential
Low as a compliance tool. The genuinely valuable asset in this space is the aggregated negotiated-rate dataset assembled from all 6,000 MRFs — and that is a data business with real network effects, real capital requirements, and incumbents three years ahead. It is a different company than the one proposed here.
Final recommendation
KILL as a product. The mandate shape that normally earns a high founder-fit score is, in this instance, a false positive: the compelling document is an RFI (no obligation, no deadline, no schema), the underlying MRF rule is five years old and thoroughly vendored, and the buyer is a hospital procurement committee rather than an individually-reachable filer. The one salvageable artifact is a free, public, scriptable scan of how many of the ~6,000 hospital MRFs currently fail the CMS validator — that is cheap to produce, generates attention, and would tell you in three weeks whether any version of this thesis is real. Do that, publish it, and let the response decide. Do not build the monitor. Revisit only if CMS publishes a FINAL rule naming a new schema with a compliance date, and even then only if the buyer turns out to be someone other than a hospital.
Next action
Write a 200-line script that fetches every hospital MRF from the public CMS-required locations and runs the free CMS open-source validator against each. Publish the pass/fail rate. Total cost: one weekend. It either produces a number that makes an incumbent want to acquire the dataset, or it confirms the market is served and you have spent a weekend instead of six months.