IGUANA Now a Leader in CIO/CMIO Mindshare

Charlie Rogers, CEO of Core Health Technologies, reached out to me on Friday with some great news. There has been a big upswing in the perception of Iguana in the marketplace for interface engines.

Every year Core Health does a major survey of IT professionals involved with integration within healthcare. Quoting from Corepoint Health’s report directly:

Significant growth in confidence for Corepoint, Iguana, and Rhapsody as Future Market Leaders. Corepoint (Corepoint Health) and Iguana (iNTERFACEWARE) each registered 17.1% of CIO/CMIO participants as their #1 choice for future market leader in the next 2-5 years. This is an increase in one year from 12.3% for Corepoint and 4.3% for Iguana. We also saw the corresponding decrease in CIO/CMIO confidence with Cloverleaf, decreasing from 19.8% (#1 choice) and 19.5% (1st-3rd choice) in 2012 to 15.7% (#1 choice) and 12.2%(1st-3rd choice) this year. Corepoint and Rhapsody (Orion Health) both had strong performance with the Manager participants, who selected them 17.1% and 15.2% respectively.

The following infographic nicely summarizes the change: HL7 Tech Survey

What’s the most crazy part? Look at the acceleration! We’ve come from 4.3%, which is practically within the margin of error, to 17.1% in one year! That is almost four times as many decision makers in the C-suite that see Iguana as the future market leader compared to 2012. In percentage terms that is just under 300%. By comparison our nearest competitor only grew by 39% from their position in 2012 – almost an order of magnitude less!

What’s driving the change?
It’s not just that interface developers can build traditional interfaces with Iguana up to 4 times faster than traditional engines .

  • It’s that Iguana can be used to solve whole new classes of problems that you couldn’t touch with a traditional interface engine.
  • It’s being able to do all the things like automating patient reminders, easily putting together dashboards and doing all sorts of non-traditional integration which makes the difference.  
  • It’s the fact that Iguana is redefining expectations of what an interface engine is and how it can help your business.

I think we are coming close to a tipping point in the market. Look at all the indicators. Our sales have grown 20% both for 2012 and 2013 and the projections for this year look even better. Last year we had our first user conference and based on the great ideas and value that people got from attending that event I expect we’ll see well over double the number of people attending our 2014 user conference. Our sales force is expanding and there some exciting technical innovations that we’ll be showing off soon.

Iguana is clearly no longer the best kept secret in healthcare integration! If you haven’t investigated Iguana yet then take the time to evaluate it and see how it could help your business. You can read the complete survey results at http://www.hl7x12.com/.

Controlling Interfaces via Cellphone

Imagine this:

  • One of your critical interfaces goes down (or is mistakenly shut down) one evening
  • You immediately receive a phone call alerting you
  • You press a button on your phone and the interface starts back up again
  • You continue <insert happy activity here> without having to run back to the office…

Does that sound like fiction to you?  It’s not, and today I’m going to show you how it’s done!

Watch this video to see all the steps required, then grab the project files to setup your own implementation.

Ready to try for yourself?

Unfortunately, there are a few gotchas/must haves if you want to set this up yourself…

  1. You must have a working copy of IGUANA.  Sorry, other engines just won’t cut it.
  2. The web service URL you create must be publically accessible
  3. You’ll need to create a free (or paid) Twilio account.

Once you’re sure you have those three things, you’re all set.  Just follow the instructions below and you’ll be on your way to a (slightly more) automated life.

Note: In order to provide a generic, extendible version of this solution, I have modified the scripts from the video to include placeholders and other parameters.

Step 1: Setting up the web service channel

The first thing you’ll need to do is create the web service that will receive requests from Twilio.  To do this, simply:

  1. Set up a channel with From HTTPS –> To Channel components
  2. Set the URL path (Source > URL Path) to “twilio”.
  3. Go to the translator (Source > Edit Script) and import this project: Twilio__Web_Service_From_HTTPS
  4. Complete the “Configuration Details” at the top of the script to match your setup.  (See the screenshot below)
  5. Save a milestone



STEP 2:  Setting up the monitoring channel

Next up you’ll need to create the channel that is responsible for monitoring your interface(s).  To do this:

  1. Set up a channel with From Translator –> To Channel components
  2. Go to the translator (Source > Edit Script) and import this project: Twilio__Monitor_From_Translator
  3. Complete the “Configuration Details” at the top of the script to match your setup.  (See the screenshot below)
    Be sure you use the full path / port of the web service you created in step #1
  4. Save a milestone



Step 3: You’re all done…

That’s all there is to it.  Once you’ve created and configured your channels, you’re all set.  All that’s left is for you to start both channels and then stop the interface you are monitoring.  As soon as you do this, you should receive a call from Twilio asking you whether or not you’d like to take action.

I hope you enjoyed this fun little example, and as always:  If there’s something you’d like to see accomplished with IGUANA, just leave a comment below describing your issue and I’ll do my best to demonstrate how to (or how not to) go about it.

Kind regards,
-Art Harrison


Title21 Software

We’re glad to hear that our technology not only makes integration easier for our
customers but that it also helps them achieve their mission and goals. Here’s the story of Title21 Software, a company that genuinely believes in delighting customers while delivering integrated technology that improves both the lives of their customers and their patients.

What is Title21 Software’s story?

Title21, founded in 2001, provides document control, processing, training, inventory and quality, workflow management to regulated health care companies. Though they have achieved success in automating blood centers, Title21 has branched out to service cellular therapy labs, cord blood facilities, tissue centers and hospital and testing laboratories.

Through continuous innovation, Title21 developed a successful integrated platform
capable of automating any form and workflow process from start to finish; everything from processing to quality control could now be easily done. All this was possible because of Title21’s strong commitment to their customers, which includes helping them achieve improved patient outcomes, error reductions, compliance, and increased efficiencies.

What was the main challenge Title21 faced and how did integration play a role in it?

As Title21 expanded into new markets — working with cancer centers, hospitals and cord blood and tissue labs — they realized that Health Level-7 (HL7) integration should be an integral component to their platform and a critical factor in providing a complete automation solution.

How is IGUANA being used?

Title21’s software is a fully integrated platform with a suite of modules that can work together or act as stand-alone solutions allowing customers to easily deploy the system in phases to meet their unique needs. With Title21’s partnership with iNTERFACEWARE, the platform now has the ability to integrate data from hospital systems including HIEs, EMRs, LIS, etc. using any standard including HL7, CDA, XML, X12, DICOM, eRX, Flat file and Web Services.

What integration engine were you using before?

HL7 integration capability is a new functionality to Title21. Initially they thought about developing their own and grappled with the build versus buy debate (for more read “The Economics of Interfacing”), until they researched IGUANA. After an evaluation and realizing how easy it was to create interfaces, they were convinced that IGUANA was the best solution. They fell in love with IGUANA; the rest as they say, is history.

What’s next for Title21′s use of IGUANA?

Although Title21’s partnership with iNTERFACEWARE is recent, they’re excited to explore new opportunities and we’re excited to see what they’ll come up with next! All innovation stems from meeting the needs of customers so with IGUANA on their side, the possibilities are endless!

About Title21 Software:

Title21 Software develops intuitive, integrated technology that streamline the core clinical and laboratory processes of regulated entities (blood centers, cellular therapy labs, etc.) while closing compliance gaps, increasing efficiency and driving success.

Title21’s platform enables healthcare organizations to capture, manage, trend, track and report on patient and process data while managing broad operational functions spanning from document management through inventory management. Title21 customers include Cleveland Cord Blood Center, Georgetown University, and Stanford Blood Center among many other prestigious healthcare institutions.

For additional information, visit www.Title21Software.com.


What do you get when you cross a customer-centric software vendor with years of experience in a niche industry with IGUANA? New opportunities and the story of DocuTrac’s QuicExchange.

We love talking to our customers and nothing is more fulfilling than hearing that IGUANA is an integral part of a successful project. Read about how DocuTrac developed a new division in their company by fulfilling the needs of their customers in the mental and behavioral health industry.

What does DocuTrac do?

DocuTrac’s main business is developing and selling EMRs for behavioral mental health and substance abuse providers as well as practice management for small providers.

What is QuicExchange?

QuicExchange is an integrated data hub in the cloud. QuicExchange shares data between HIEs and RHIOs, clinical support groups, government agencies as well as health care providers such as hospitals and Medicaid health homes.

QuicExchange helps organizations achieve MU Stage 2 certification while remaining compliant with privacy laws and institutional regulations.

How is IGUANA being used?

With the advent of Meaningful Use Stage 1, DocuTrac saw the opportunity of incorporating lab results into their mix. As they progressed and received MU certification themselves, they noticed that many providers were asking about connecting with RHIOs and HIEs.

They were in a niche market (behavioral healthcare), with the chance to create a product (EMR) that would connect small providers like community or state run mental health facilities to HIEs and RHIOs, so they jumped at the opportunity and used iNTERFACEWARE’s IGUANA to develop QuicExchange.

What integration engine were you using before?

After evaluating IGUANA, DocuTrac’s interface engineer switched from Symphonia (Orion Healthcare) because of how easy it was to create interfaces.

What’s next for DocuTrac’s use of IGUANA?

Growing from a product to a separate division in the company all within a few months, DocuTrac is exploring new opportunities and how to market QuicExchange. Connecting practice management hospitals, physician communities, setting up between customers and patient portals – the possibilities are endless!

About DocuTrac, Inc.:

Founded in 1993 by Arnie Schuster, Ph.D., DocuTrac developed out of the need of providing accurate and comprehensive documentation of clinical records and notes in the mental and behavioral health industries.

DocuTrac’s products include a complete ARRA-Certified Enterprise EHR system for large behavioral health and substance abuse treatment facilities, as well as client-server software and a cloud hosted solution of QuicDoc Office which includes Office Therapy for billing.

For more information about DocuTrac’s products, visit www.docutracinc.com.