We integrate systems (e.g., legacy systems) with minimal invasiveness to each system, across platform, programming language and protocols. And, the solutions offered are scalable.

In 1998, we started brainstorming and designing how two highly disparate systems could be integrated. We chose to attempt an  integration between a monolithic patient journal system with a video game about a barbarian warrior. Twenty years later, integration has become one of our main focuses, with several successful projects integrating highly disparate systems.

Integrated systems have the following properties:

  • Interoperability: systems should not only be able to communicate with each other, but there must be actual interaction.
  • ¬†Minimal Invasiveness: If the systems to be integrated are legacy, then coding an interface with them needs to be minimally invasive, namely as little change as possible to that system. The integration needs to speak the language of the legacy systems.
  • Fault Tolerance: If one system fails, some functionality is lost, but the other systems should be tolerant.
  • Security and privacy: We not added security as an afterthought. The integration is secure by design.
  • have a security model for the architecture as it is currently being used to integrate medical systems as well.