The following post highlights one of iNTERFACEWARE’s many partners. We love to learn and share what others are doing with IGUANA, or in this case, how one organization – Caristix
– is helping companies migrate away from legacy engines in a pain-free and timely manner. Caristix was kind enough to present parts of their solution at our 2014 IGUANA User Conference and since then we’ve had a number of customers ask to learn more. We also partnered with Caristix to support the development and release of the first ever interface converter: the Mirth Connect to IGUANA converter. So, if you’re looking to migrate away from a legacy engine, I recommend you read below and consider speaking with our friends at Caristix. At the end of the post I’ll also include some links to our recommendations on setting up your newly migrated IGUANA server. But for now, let’s get on with the post.
The problem is quite simple: healthcare providers and vendors need more than legacy engines can deliver.
Whatever the specific motivating factor (meaningful use, population health management, analytics, new data sources, etc.), organizations who are looking to expand their interoperability are faced with major migration projects.
While there’s plenty of advice on selecting a new interface engine, there’s not enough on the actual migration process itself.