Map the workflow
Document the trigger, current workaround, inputs, and acceptance criteria.
PRICE TRANSPARENCY FILE QA · HEALTHCARE ADMIN
A public-data validation and monitoring concept for hospital machine-readable files: format, required fields, completeness signals, change history, and review evidence—without patient data or clinical decisions.
Currently: research preview · synthetic data · no customer claims
FREE / LOCAL FILE SCREEN
Select a hospital JSON or CSV MRF. The browser reads only the first 1 MB locally; the file does not leave your device. This is an early screen, not full schema validation.
01 / THE TRIGGER
Teams combine vendor exports, technical scripts, CMS guidance, spreadsheets, and manual review. A malformed or incomplete file can create rework, leadership uncertainty, and regulatory follow-up even when the underlying pricing process is legitimate.
02 / SAMPLE OUTPUT
This preview shows the shape of the output with synthetic inputs. Nothing here is personalized advice or production evidence.
03 / HOW A PILOT WORKS
Document the trigger, current workaround, inputs, and acceptance criteria.
Use synthetic or explicitly approved sample data in a scoped report.
Continue only if the workflow helps and a buyer makes a commercial commitment.
04 / FIT
✓ Hospital compliance and revenue-cycle teams responsible for public MRFs
✓ Consultants and vendors preparing hospital price-transparency files
✓ Health systems seeking timestamped validation evidence across facilities
— Legal advice or a CMS compliance determination
— Validation of patient-level claims or protected health information
— A guarantee against warnings, corrective actions, or penalties
05 / FOUNDING OFFER
06 / WHAT IS TRUE TODAY
MRF Preflight is a validation-stage administrative QA concept, not legal advice, certification, or a determination of CMS compliance.
The public form accepts no files, credentials, claims, patient information, payer contracts, or confidential pricing material; the proposed review begins with a publicly posted MRF URL.
Whether HIPAA, contractual, security, or other obligations apply depends on the final workflow and data handled and must be reviewed before any production engagement.
07 / STRAIGHT ANSWERS
No. The proposed report organizes technical findings and evidence for human review; CMS guidance and qualified advisers remain authoritative.
CMS states that updated requirements are effective in 2026 and enforcement began April 1, including attestation and additional machine-readable-file data elements.
Not in this validation test. The initial scope is limited to public files and non-confidential review context.
2026 / PRACTICAL GUIDES
08 / YOUR SIGNAL
We use these details to separate useful buyer evidence from general curiosity.