All termsSystems
Integration Engine
An interface engine (e.g. Mirth, Rhapsody, Cloverleaf) that routes, filters, and transforms messages between systems.
When to use it
Use one whenever systems don't speak each other's dialect directly, or to consolidate many point-to-point feeds into managed channels.
In plain terms
The switchboard and translator of the hospital: every message passes through, gets reshaped, and is routed onward.
Common gotchas
- The engine is where most transformation logic lives — document the mappings, not just the connections.
- A single engine can be a single point of failure; understand its high-availability setup.
- "The interface works" often means "the channel is deployed", not "the data maps correctly".