• E-mail
• Print
• RSS

Interface v. integrate: Do you know the difference?

HIM Connection, August 2, 2005

Want to receive articles like this one in your inbox? Subscribe to HIM Connection!

As you research EHRs and investigate software and how to convert to paperless systems, you're bound to hear the words "integrate" and "interface." But don't confuse the terms as meaning the same thing.

The difference is significant, explains Michael Glickman, president of Computer Network Architects, Inc., in Maryland. "Interfacing is a process and integration is a result."

An interface is the point of communication between computer programs and other devices. A simple example of an interface is the message your word processor sends to your printer once you click "print."

Typically interfaces occur at the back end of the system where data are shared. Interfaced systems require messaging standards, for example, HL-7, and a controlled vocabulary such as SNOMED CT, the Systemized Nomenclature of Medicine-Clinical Terms, as well as a series of coordinated trigger events and error-processing rules.

Interfaced systems are practical because there is no need to change or even understand the architecture of the underlying systems, says Glickman.

Integration is more complicated than interfaces, says Glickman. It involves combining software and hardware components into an overall system that works seamlessly to share information. Integration is achieved when a single source, or closely aligned sources, develop the systems so the data, logic, rules, and presentation are all consistent, says Glickman.

Integrated systems allow for the collection and correlation of data. It allows information to move in any direction among the underlying component systems. The look and feel-what users see-are also consistent. Integration requires significant understanding and control of the underlying systems and can be difficult to achieve.

Electronic systems should have coordinated trigger events-keystrokes or commands-in place so that when one system sends data as the result of an event, the other system is prepared and able to receive the data.

Editor's note: This article was adapted from the newsletter Electronic Health Records Briefing. Go to www.hcmarketplace.com/Prod.cfm?id=3224 for more information or to order.

Want to receive articles like this one in your inbox? Subscribe to HIM Connection!

• E-mail to a Colleague
• Print
• RSS
• Archive