Blog

Migration Guide: From Oracle eGate to Orion Health Rhapsody Interface Engine

By jeanluc.morin@caristix.com | Published: February 9th, 2015

Inteface Engine Migration Guide

In a previous post, we talked about reducing migration project risks and some of the drivers in interface engine selection. In particular, with DataGate/eGate and eBiz at the end-of-life mark, many hospitals and health systems are faced with major conversion and migration decisions. The interface engines now in place are responsible for the critical flow and orchestration of financial, administrative, and clinical data. Disrupting current critical data flow to take on a migration project is challenging.  And the smartest organizations are working to expand their interoperability particularly with the increased capabilities of contemporary EHRs.

Here at Caristix, we’re developing a series of Migration Guides with recommendations to ease the pain of migration projects and to look at the role Caristix Workgroup software takes in facilitating the process while reducing costs and project timelines. Our first release is the Interface Engine Migration Guide: From Oracle eGate to Orion Health Rhapsody Integration Engine.

It’s common that developers jump right into the code with incomplete requirements and a flawed knowledge of the data to be exchanged. Teams quickly run into problems with this reiterative trial and error loop. It’s impossible to predict project timelines and to guarantee complete coverage of issues before moving an interface into production.

How do you fix those problems? We’re proposing a step by step approach to speed up eGate to Rhapsody migration project execution throughout the five stages of interface engine migration.

    1. Gather interface requirements
    2. Setup the new interface
    3. Migrate the interface
    4. Validate the new interface
    5. Move into production

These workflow recommendations are scalable in terms of the number of interfaces addressed. We particularly focus on validation to increase overall team productivity. The recommended workflow remains valid even if you do not use the recommended tools and is applicable to migration to different integration engine technologies with some variance.

Download the Interface Engine Migration Guide: From Oracle eGate to Orion Health Rhapsody Integration Engine

Watch for our other Migration Guides in the near future!

  • Interface Engine Migration Guide: From Oracle eGate to Intersystems Ensemble Integration Engine
  • Interface Engine Migration Guide: From Oracle eGate to Microsoft BizTalk Integration Engine
  • Interface Engine Migration Guide: From Oracle eGate to Interfaceware Iguana Integration Engine
Categories : Migration/Conversion