Eclipse Open Integration Engine

Every hospital, clinic, and lab runs on a patchwork of software systems that were never designed to talk to each other. A patient's record might live in one application, their lab results in another, their imaging in a third, and their billing in a fourth - each speaking a different digital language, often built decades apart. Getting these systems to share information reliably is one of the most persistent and expensive problems in healthcare, and it is the problem the Eclipse Open Integration Engine exists to solve.

Eclipse Open Integration Engine sits between healthcare systems and translates between them. When one system needs to send information to another, the engine receives the message, converts it into a format the receiving system understands, applies any rules the organization has defined, and delivers it. It does this thousands or millions of times a day in production environments around the world, quietly handling the flow of clinical and administrative data that keeps a healthcare organization running. Healthcare IT teams use it to connect electronic health records to laboratory systems, to route imaging orders, to feed data warehouses, to exchange information with public health registries, and to bridge older systems with modern, standards-based interfaces.

The project provides three things: the engine itself, an administrator application for designing and monitoring message flows, and the documentation needed to operate both. Implementers organize their work into channels, each representing a single integration between systems. A channel defines where messages come from, what should happen to them along the way (filtering, transformation, enrichment, routing), and where they should go. Channel logic is expressed in a combination of configuration and JavaScript, which gives integration teams enough flexibility to handle the unusual real-world cases that healthcare data is famous for, without forcing them to build and deploy custom applications.

Under the hood, Eclipse Open Integration Engine is a cross-platform integration engine (written in Java) that acts as an interpreter for healthcare systems, translating message standards into formats that target systems can process. The engine allows health IT teams to manage message pathways (channels) through filtering, transformation, extraction, and routing stages. It supports bidirectional conversion between standards like HL7, JSON, and XML. The project features a modular architecture with custom JavaScript-based scripting and connectors for protocols like HTTP/S, FTP, and direct database connectivity. It also includes a management administrator interface for channel development and operational monitoring.