FHIR: Can It Reduce Interface Costs?

The industry has been abuzz with talk of FHIR (Fast Healthcare Interoperability Resources) recently. It’s a subject that’s near and dear to me since it’s a real attempt at advancing the quality of patient care while reducing the cost associated with integration.

What is FHIR? If this is your first time hearing about FHIR, I suggest you peruse the first entry in my recent blog series – entitled: What is ‘FHIR’ and Why Should You Care? – to learn about the origins of the standard.

FHIR is simple. Watch how blogger Jayant Singh converts HL7 v2.x to FHIR using IGUANA in my second post called Burning v2 with FHIR in Mumbai.

FHIR vs CDA. Need more proof on its simplicity? When compared to CDA/CCD, FHIR is very modular and it’s extremely easy to build small adapters to cover just what you need. That’s exactly why I think FHIR will burn the CDA.

FHIR is RESTful. I’m excited that FHIR is helping make the paradigm of RESTful API-based integration a mainstream concept. RESTful APIs are simpler to implement and this translates into faster development time and lower overall integration costs. Coincidentally, these are also core benefits of IGUANA. Learn how IGUANA + FHIR = Profit.

On another note, I’m going to be at Apps for Health and Education 2013 on May 16 in Hamilton, Ontario. If you’re going to the event, it would be great to schedule a meeting with you.

Until next time: Happy Integrations!

EMuirSignature.png

Eliot Muir,

President and CEO, iNTERFACEWARE™

IGUANA User Conference:

Toronto, Ontario – September 19-20, 2013

We’re excited to announce our first ever IGUANA User Conference! Save the date and be sure to join us for two action-packed days of education, insights and fun!

Be Our Guest:

Connect with your peers, witness a showcase of amazing real-world projects, gain insights into best practices and above all have a great time! This is a celebration of you – an exclusive group of talented integration heroes.

Newsletter - Button - RSVP-L

Calling IGUANA Innovators – 2 Speaking Spots Left for the IGUANA User Conference:

We’ve filled most of our speaking spots and are looking for two out-of-this-world speakers who are interested in highlighting their specific uses of IGUANA and leading the discussion on hot topics and industry trends.

Contact us for the opportunity to speak to a cross-section of integrators and innovators.

IGUANA 5 Training:

Jun: Chicago, IL
Sept: Toronto, ON

Become an IGUANA expert by learning all facets of the translator for quicker implementation times and more effective interface administration.

Courses are interactive and customer-centric so that your training directly contributes to your integration success.

The sessions are filling up quickly, so reserve your spot today!

 

When are you going to replace your integration engine?

Below is a repost of my recent newsletter.  Please read and comment below.

=======

My team is off enjoying their summer vacations this week; leaving me responsible for our newsletter. Since I don’t have their knack for design or clever wordplay, I thought I’d just share an interesting trend I’ve been seeing over the past several months.

Recently, I’ve seen upwards of 50 new inquiries from people looking to replace their eGate, Cloverleaf or homegrown integration engines.  A significant portion of our business has always come from helping enterprises ease their migration headaches, but never have I seen so many large deployments looking to change… and all at the same time!

So, why are they turning to IGUANA? Maybe it’s:

Maybe my marketing team is really that good and actually deserves their time off.

To be honest I don’t know the answer. But what I do know is that iNTERFACEWARE has been there for our customers by creating the solutions they need, when they need them. From our early HL7 toolkits for developers to our IGUANA integration engine and the IGUANA Translator, we continue to develop the most reliable and innovative integration solutions.

Could the answer be that simple?:  Great Product + Great Service = Amazing Results.

What do you think?  Is this surge in replacement engine inquiries the result of my marketing team’s prowess or are integration requirements growing beyond those a traditional engine can handle?  Maybe there is just a collective distrust of the outdated engines (who are often being sunset or sold off to the highest bidder) and their ability to keep up with the push for truly connected healthcare.

I’ll be reposting this e-mail at blog.interfaceware.com, so head on over and share your thoughts. I’d love to read to them.

In the meantime, if you’re looking to future-proof your integration strategy or just getting started with your first interface, do yourself a favor: take a look at IGUANA, read what people are saying about it and reach out to us. You won’t regret it.

Thanks for reading and enjoy your summer!

Kind Regards,

Art Harrison
Vice President, Marketing and Communications

iNTERFACEWARE Inc.

Is re-implementing 4 eGate interfaces within one day fast or slow?

I just got news that one of our integration partners managed to convert 4 eGate interfaces within 1 day.

She did this:

  1. Without a product demonstration.
  2. Without any formal training other than our online documentation.
  3. Without calling our helpdesk once.

Two of the interfaces were relatively simple, the other two were more complicated.

While she is very experienced with integration, she is new to Iguana.

Is this typical for the time it takes to migrate off eGate?  I am impressed.  What do other people think?

HIMSS 11 Perspective: Eliot Muir

Our very own CEO of iNTERFACEWARE, Eliot Muir sat down to talk with HIT Exchange Media at HIMSS 11 to discuss the importance and role of interfacing data systems in HIE with a particular emphasis on CDA.

 

Video Transcript

One of the things we are really kind of excited to look at is seeing the emergence of the CDA as a new business challenge that businesses are facing. I think the first stage of the meaningful use provision has got people generating CDA documents. Now generating a document, there is a fair bit of work in doing it but the real work is going to be when people start having to try to consume CDA documents from other vendors. I think we will get back into the same classic problem that interfaces usually reflect the structure of the databases that they feed from and so there’s going to be the same issues with CDA. So you might have a system that has heavy smoker, light smoker, non-smoker and another system says 5 packs a day, non-smoker, 10 packs and over 50. Invariably data is not stored in compatible formats in databases and that’s always reflected in interfaces. So, it’s going to be interesting in looking to see how as the meaningful use provisions go forward, vendors start having to try to interchange the CDA standard. We are ready to help with that if people are facing that challenge.

— — —

Remember to subscribe to our blog or follow us on twitter (twitter.com/interfaceware) for product updates, future resources and discussions.