AMIA: Why interoperability is 'taking so darn long'

Hospitals can have hundreds of IT systems. Vendors have built proprietary databases. Not everyone follows the same standards. Health systems fear sharing data with competitors. Policymakers have not focused on health information exchange or EHR usability.

These are just a few of the reasons why true interoperability of health information remains so elusive, according to a panel of informatics luminaries.

 

"Technology is only one obstacle to interoperability," said Gilad Kuperman, MD, director of interoperability informatics at New York-Presbyterian Hospital, who moderated the panel at the just-concluded American Medical Informatics Association (AMIA) Annual Symposium about why interoperability is "taking so darn long.

"

Charles Jaffe, MD, CEO of standards development organization Health Level Seven International (HL7) described a "circle of blame" involving government agencies and regulators, hospitals and healthcare systems, technology vendors, clinicians, academicians like those at AMIA and, yes, standards development organizations (SDOs), such as HL7. "The policy always preempts the technology," said Jaffe.

"And just like [in the 1983 Cold War movie] WarGames, in this finger-pointing, no one wins." He noted that not-for-profit HL7 in September made most of its standards and other intellectual property available free as a means of building trust for HL7 communications messaging. "Without trust, none of this is possible," Jaffe said.

Harry Solomon, interoperability architect at GE Healthcare, and a lecturer at Oregon Health and Science University, explained the road to interoperability with four numbers: 2, 4, 3 and 5.

There are two overarching concepts that need to be defined, namely interoperability and standards, and Solomon said "good enough" definitions exist from Institute of Electrical and Electronics Engineers (IEEE) and the International Organization for Standardization, known as ISO. Therefore, healthcare should not have to do any more in this arena. "We can't afford to have custom integrations for every data transfer that we have," Solomon advised.

The number 4 stands for the levels of interoperability specification: workflow, messaging, format, vocabulary.

The other two numbers represent three phases – standards development (generally handled by an SDO), product development (vendors), and system deployment (users) – and five process steps for each phase.

These steps include: the decision to proceed on each phase; allocation of resources; development; validation; and deployment.

Previous
1