We use Chameleon as a toolkit – how would we migrate to use Iguana?

A common scenario for customers using Chameleon is to have Chameleon populate a set table objects that are then manipulated in a language like C#, Java, C++ etc. and inserted into a database.

Chameleon is used to perform the ‘normalization’ of that incoming HL7 via changing the mapping and python to massage the inputs into the expected outputs.

This is an easy code base to transition to using the Translator.

All that is required is to use the existing code and make a minimal web service application that accepts XML in the table short tags format. This requires minimal amounts of code in this service.

Another strategy is use the Translator to front end a Chameleon application with straight HL7 transformation.  That’s an easy approach also.

The Translator then takes responsibility for doing the normalization of data from external sources into that table format which is consumed by the native code in C#, Java, C++ etc.  Very little changes except that there is now a much more flexible tool for doing the mapping that gives:

  1. Ability to deal with many more modern formats, web services, XML, adhoc SQL queries, weird proprietary formats.
  2. A full dashboard, superb logging, error tracing.
  3. Email alerts.
  4. All much more visibly integrated using a modern web based GUI.

So you can relax – there is an easy way to quickly transition your company from the 90’s to the present day.

Leave A Comment?