Built by people who read the exports nobody else would.

Every hospital runs on interfaces. Orders, admissions, results, and charges move between clinical systems as HL7, FHIR, DICOM, X12, and NCPDP messages, around the clock, largely unwatched. The teams responsible for them are small, and the tooling they inherited was built to move messages — not to explain them.

Ivren exists because that gap is where the expensive failures live. A field changes and three systems downstream break. A feed goes quiet and nobody notices until someone asks where their results went. A migration gets deferred for years because no one can prove it is safe.

So we built the tool we wanted: it reads the configuration your engine already has, shows you the estate as it actually is, proves a change is safe before it ships, and runs entirely on your own machine — no account, no upload, no telemetry. That last constraint is not a feature we added. It is the premise we started from.

“We do not claim what we cannot prove. If you catch this site saying something the product can’t do, we want to know.”