E2 – Equivalent Engine

E2 connects application databases. Also referred to as “Babelfish” (we borrowed the term from Douglas Adams’ book “The Hitchhikers Guide to the Galaxy” for the fish’s ability to translate any kind of communication media), E2 allows for unidirectional intra- and extra-application integration at the data level within or between organizations. This systems integration product takes advantage of Microsoft’s .NET platform and SQL Server’s innate XML and legacy support. E2 provides tremendous flexibility in integration architecture. It is ideal for connecting legacy and web-based systems to each other. E2 cuts integration time by half to 1/10th the time it typically takes.

Collaboration through Integration: Within the server, the “context” of integration may be dynamically controlled. This allows for joint ventures and partnerships to share data while protecting sensitive corporate data depending on the context of the relationship and the staff using the data. In the healthcare world, this allows competing hospitals to participate in a federated model community health information exchange, retaining there own patient’s data without revealing it to other hospitals unless there is a patient need. This alleviates one of the major reasons communities have a hard time building community health information exchanges – perceived “theft of patients.”

E2’s Value:

* Makes data available to lots of end users, without the end user having access to each facility’s systems.

* For example - Master Patient Indexes (MPIs) are an ideal application provided by many different software and HIS companies, which feeds almost every other application within a hospital

* E2 can integrate all these MPIs so that the Health Information Exchange can report that these facilities have patients that match the information given in their individual MPI. The HIE user can then request the records. The HIM Director and their policies and procedures are still the gatekeeper on whether the record is released or not.