5,000+ subscribers can't be wrong!

We'll share our best insights on how to get the most out of IGUANA.

Sign up today to receive updates twice a month:

MACRA Part 2: Three Reasons Why MACRA Will Have a Big Impact on Hospitals

Welcome to the second part in iNTERFACEWARE’s series of blog posts on MACRA (Medicare Access and CHIP Reauthorization Act of 2015). In the first part of our series, we looked at how an integration engine can increase reimbursements for clinicians under MIPS. In today’s post, we shift our attention to hospitals. Now you might be thinking, “MACRA only applies to medicare physicians, why are we talking about hospitals?“ While MACRA only applies to physicians, it affects hospitals too. And in a big way.

If you are the CEO of a hospital, you probably want to know what MACRA means for your business: how will it affect my hospital’s relationship with physicians? What can I do to prepare for MACRA? And most importantly, what impact will MACRA have on my hospital’s bottom line?

We’ll address these concerns after answering a simple question: why should hospital executives care about MACRA?

MACRA Part 1: How An Integration Engine Can Increase Reimbursements for Clinicians

Welcome to the first part in iNTERFACEWARE’s series of blog posts on MACRA (Medicare Access and CHIP Reauthorization Act of 2015). Over the course of the next few weeks, we will take a look at the implications that MACRA will have for clinicians and healthcare providers when it comes to reporting and collecting reimbursements. We will also look at the role a modern integration plays in all of this, and why using one can potentially lead to substantially higher reimbursements for clinicians and save hospitals valuable time and money when creating reports.

For part one in our series, we will focus on the the impact that MACRA will have on clinicians and how an integration engine can lead to higher reimbursements for their services. First however, we’ll give a brief overview of MACRA: what it is, what the CMS hopes to accomplish with the act, and how clinicians will be scored under the new Merit-based Incentive Payment System (MIPS).

Clinical Document Architecture (CDA): An Overview

Clinical Document Architecture (CDA) is an XML-based standard for encoding clinical documents for easy data exchange. CDA allows healthcare providers to create digital documents containing patient information that they might wish to send to other healthcare providers or regulatory authorities. The documents contain any and all information about a patient’s medical history, such as allergies, medications, insurance information or lab results. Essentially, any piece of information that might be relevant to a healthcare provider or government entity.

Iguana User Conference 2016 Recap

Another year, another successful Iguana User Conference in the books.

From the great presentations and networking activities to the beautiful night at the CN tower, we hope that everyone in attendance enjoyed themselves. More importantly, we hope that attendees walked away from the conference with some actionable insights from each presentation. For those who were not able to make it this year, we’ve got a quick recap for you along with some of the memorable moments from the event.

Disaster Recovery vs. High Availability vs. Fault Tolerance: What are the Differences?

When it comes to thinking about your organization’s backup plan for when your systems and applications go down, there are three terms that you are likely to hear a lot: disaster recovery, high availability, and fault tolerance.

While these terms are related to one another, it is worthwhile to know the differences between them and understand the role that they play in keeping your systems online. Today we’ll define what each term means, demonstrate what it looks like in action, and explain why it is important to the success of your organization.

Workflow Improvements: The Domino Effect of Implementing a Modern Integration Engine

Implementing a modern integration engine can do wonders for improving operational efficiencies in hospitals. Everything from happier and more productive nurses to higher patient satisfaction and huge costs savings can be accomplished by using an integration engine that connects all of your systems. The key to achieving all of these things is to realize the domino effect that one workflow improvement can have on the rest of your hospital.

Let me explain.

How Fast Can Your IT Infrastructure Handle Bundled Payments?

Everyone in the healthcare industry is talking about the Bundled Payments for Care Improvement (BPCI) initiative set up by the CMS. With over 75% of hospitals in America using EHRs, being able to comply with the initiative will require great focus on IT. Specifically, hospitals will need to ensure every department is well connected to one another, to central billing systems, and to the patient’s EHR. Essentially, for hospitals to comply, they will need to focus heavily on interoperability.

First and foremost, hospitals need to understand their capabilities and limitations within their integration landscape. Most hospitals with an EHR system also have an integration engine – many have more than one.

Is High Availability For Your Integration Platform Worth It?

Disasters are inevitable, unpredictable, and they vary in types and seriousness. For example, water leaking into a server room is annoying, but an 8.0 earthquake collapsing the building where the servers are housed is catastrophic.

Most enterprise-level organizations have disaster recovery plans for their different business units to minimize disruption to their operations because not doing so means direct revenue losses and very unhappy customers.

Are you prepared for business continuity when a disaster occurs?

Barriers To Interoperability In Healthcare: The “Lack of Data Standards”

iNTERFACEWARE recently ran a poll asking “What’s the greatest barrier to interoperability in healthcare? The ‘lack of data standards’ lead the poll with 36%.

What do people really mean when they say the ‘lack of data standards’?

Of course, we all know that there are many standards used for data exchange in healthcare. Some would argue there’s far too many.

While it may be simply a matter of semantics, the barrier in question is more accurately the lack of a universal standard; one that is a true standard and not open to various vendor interpretations and implementations.

Healthcare’s current multi-standard environment is challenging to say the least. But, the harsh reality is that it’s not going to change. At least, not any time soon.

Welcome to Iguana Repositories

The release of Iguana 6 was all about giving our users the necessary tools to work smarter and ultimately faster.

In this post, we’re going to explore Iguana’s Repositories and focus on the role that they play in helping you build stable interfaces faster than ever.

At the heart of Iguana 6 is a brand new source control system, powered by the well-known Git version control system.

What this ultimately means for you is:

  • an easier way to share channels between Iguana instances and team members
  • simple access to a library of prebuilt interfaces designed to jumpstart your projects

Before we go into greater detail, let’s first start with the basics.