Product
Map the estate, prove every change, run interfaces that don’t drop messages.
Map
Turn the configuration your interface engine already holds into a live map of the estate.
Estate mapping
Drop the configuration exports from a supported interface engine onto Ivren. It reads them and shows every interface: source, destinations, protocols, and which fields carry patient identifiers.
Impact analysis
See what breaks downstream if a field changes, before you change it. Credentials found inside exports are stripped at import and reported so they can be rotated. A malformed or truncated export is reported as a located finding, never silently skipped.
The console
A local web console served by the binary itself, bound to 127.0.0.1 only: overview, interfaces with a detail panel, live status, and a health summary. One click loads bundled synthetic sample data so you can see the whole product without supplying a file. Keyboard-accessible, with no external network requests.
Prove
Interfaces as provable artifacts: versioned, tested against recorded traffic, and gated on evidence.
Regression testing & the deployment gate
ivren run compares two output sets and decides PASS or FAIL. ivren gate decides whether a change may deploy, with an exit-code vocabulary built for CI: 0 PASS, 1 FAIL, 2 could-not-complete, 3 INDETERMINATE, 4 REFUSED.
Replay & probe
ivren replay replays a recorded corpus against approved, pinned, non-production targets only — a production-class target is structurally refused. ivren probe shows exactly what a connector would do without doing it.
Message tooling
ivren parse prints an HL7 message's field tree with spec names, backed by an embedded HL7 dictionary spanning multiple versions.
Wire-format depth
Parsers and conformance machinery for HL7 v2 (multiple versions), FHIR R4, DICOM metadata and worklists (pixel data is structurally never stored), X12 claims envelopes, NCPDP pharmacy claims, and HL7 batch files (FHS/BHS), plus database-to-database connector modeling and SFTP/MLLP/HTTP transports.
Run
Ivren runs interfaces itself — durable, crash-safe, and honest about failure.
Local engine
Durable queues (fsync-before-ack, crash-safe), MLLP/HTTP/file listeners, per-destination retry lanes with backoff, dead-letter handling, and alert-on-silence — an alert when an expected feed goes quiet.
Transforms
Declarative field mapping with static “silent drop” analysis — finding fields a mapping loses before it runs.
Message search & resend
Search the archive by time, interface, and type, and resend from the console — with a permission model that separates metadata, masked view, full view, and export.
Offline licensing
License keys with air-gapped activation: an activation request can be carried out on paper or USB and the signed license pasted back. An expired license never locks you out of activate, help, or uninstall.
Migrate
Prove a migration is safe before you commit to it — one interface at a time.
Shadow-run migration
Run a proposed Ivren route beside your existing engine on the same traffic, deliver nothing, and produce a signed divergence report: what Ivren would have sent versus what the incumbent actually sent, day by day, with any difference located to the exact field. Cut over one interface at a time when the report reads zero.
Role-based access
A closed role set (admin, engineer, operator, revenue, auditor) with server-side enforcement and a hash-chained audit trail; every sensitive view and change recorded.
Money
Give revenue-cycle and compliance staff their own reasons to care about the interface layer.
Charge reconciliation
Hospital charges travel as interface messages. When a feed drops them, that's unbilled revenue nobody connects to the IT queue. Ivren counts both ends and reports exactly what didn't arrive, by interface and by day.
Claims pre-flight
X12 and NCPDP claims validation before submission — catch a rejectable claim before the clearinghouse does.
Try it against your own exports.
Or skip the file entirely — every install ships with sample data.