Before we dive into why interoperability matters, let's start with what it means. According to the Healthcare Information and Management Systems Society (HIMSS), interoperability is “the ability of different information technology systems and software applications to communicate, exchange data, and use the information that has been exchanged.” The key phrase here is: "Use the information that has been exchanged."
What are the four levels of interoperability in healthcare?
So, is our healthcare system interoperable? The answer isn’t simple. Interoperability is complex, which is why HIMSS breaks it down into four levels. Let’s take a quick look at each, and then we’ll explore the challenges of semantic interoperability in more depth.
1. Foundational interoperability
Foundational interoperability is the most basic level. It allows one health IT system to send data to another. You can think of it as “opening the pipes” so data can flow. FHIR APIs are a good example of this in action.
2. Structural interoperability
In structural interoperability, the focus is on how data is formatted and exchanged. Also called syntactic interoperability, this level ensures that data is organized in a consistent way, like turning words into sentences. Standards like direct messaging, FHIR implementation guides, and C-CDA are examples of how systems structure the data so it can be interpreted correctly by receiving systems.
3. Semantic interoperability
Semantic interoperability ensures that the receiving system is not only able to receive the data, but can understand and use it. This is where things get more complex—and more meaningful. That requires standardized, codified data using common vocabularies.
Scattered, isolated HIT systems that have evolved over the years and employ a range of medical terminologies and nonstandard ways of documenting important clinical details have led to significant barriers in this layer of interoperability. Regulations like the HTI-1 rule that enforce the use of FHIR-enabled APIs and require that the most critical data elements used in patient care be shared using common vocabulary standards have helped to codify those important data elements. Refer to the USCDI for a list of those data and the requisite vocabulary standards.
What about the data not identified in the USCDI, or that is not easily codified to a single standard? To create actionable, usable data, it needs to be optimized through a process of mapping to an applicable standard or normalizing the data. This cannot be left up to untrained IT systems, AI, or non-clinical personnel. A data normalization solution allows for apples-to-apples comparisons and aggregation of information from different systems by 1) standardizing local content to common terminology standards and 2) semantically translating data between standards (concept mapping) to eliminate any ambiguity of meaning.
4. Organizational Interoperability
This final level brings everything together. Organization interoperability includes the governance, policies, and trust frameworks that make interoperability work across organizations. This is where initiatives like the Trusted Exchange Framework and Common Agreement (TEFCA) come into play, emphasizing the importance of trust, privacy, and data governance in enabling seamless, secure data exchange. Data governance is key to achieving organizational interoperability and the path to accelerating outcomes.