RenniLink Integration Engine is original software, written from the ground up by RenniLink — not a reskin, fork, or wrapper of another integration product. It is a native Windows healthcare message platform: an embedded routing engine plus a full administrator console in one install. Connect devices and systems that speak HL7 v2, FHIR R4, MLLP, HTTP, file, serial and more; tag by vendor; store; transform; and route to EHR and other destinations — with optional Windows Service for 24/7 headless operation.
Original engineering, from the ground up. Designed as a single-host clinical edge gateway with its own channel pipeline, connectors, and native Windows console. No Java required — no JRE/JDK install, no JVM stack to patch or size for. No browser admin farm, and no multi-node cluster as the default footprint.
Messages move through JSON-defined channels: source → filter / transform → destination(s) with retries, ACK timing, ordered or parallel delivery, and operator-visible health. Channels can be designed, tested, deployed, enabled, and disabled from the desktop console.
Full connector set for clinical edge and common cloud/message-bus paths — see the complete list in Connectors below.
Message-type filters, field maps, sandboxed JavaScript (incl. LDAP helpers),
vendor presets, and HL7 ↔ FHIR paths. A vendor-tag transform stamps
vendor identity from MSH-3 or channel settings for multi-vendor routing.
Full inbound payload store with prune, export / import (.rlbak + CRC),
integrity checks, auto-backup, and quarantine. Operators can reprocess and dry-run
from Failed Messages with live DNS / ping / TCP diagnostics.
Validate HL7, English decode, send MLLP, dry-run a channel, range replay, bedside simulator, and clinical toolbox (multicast discovery, connectivity, hosts).
Application password (PBKDF2), DPAPI channel secrets, credential vault, certificate inventory, optional inbound API keys (header / Bearer), localhost Admin API fail-closed with required API key, body size caps, factory reset.
Sources and destinations you can wire into channels. Optional packs can be left off; core clinical paths (especially MLLP) stay first-class.
Connectors are used as channel sources and destinations. Exact options depend on channel JSON configuration and which optional packs are enabled on the host.
| Capability | Integration Engine |
|---|---|
| Channel model | JSON channels · receive → filter/transform → route → retry/ACK |
| HL7 v2 / MLLP | First-class TCP/MLLP (optional TLS) |
| FHIR R4 | Receiver / sender + transforms |
| Multi-vendor | Vendor catalog · vendor-tag · multi-vendor sample channels |
| Reliability | Circuit breaker · connection pool · poison handling · reprocess |
| Admin | Native WPF — no browser admin console |
| Runtime | No Java required · no JVM · .NET 8 self-contained |
| Install | Single Setup.exe · runtime bundled |
Native blues-and-whites UI — engine health, channels, connectors, and diagnostics without leaving the desktop. Click any screen for a larger view.
Demos, site packs, and commercial terms — not a public web download.