Compatibility and interoperability: the two design aspects

The correct answer: D. Compatibility and interoperability

✅ Why this answer

The basic pair in systems design: the system’s components must coexist in the same environment (compatibility: they connect and work alongside each other), and they must understand each other (interoperability: they exchange usable data). They are two successive layers: compatibility is the ground, and interoperability is built on top of it (a related question in the full bank).

❌ Why the other options are wrong

The trick is that all the options are pairs of resounding positive qualities:

• Innovation and standardization (A): two real values, but ones that are in tension to begin with (innovation breaks standardization), and not the pair meant here.
• Efficiency and cost (B): financial evaluation considerations.
• Agility and availability (C): quality attributes (and availability is indeed an important nonfunctional requirement), but they do not describe “working alongside systems and exchanging data each one understands”.

💡 Key concept

The basic pair in design: compatibility means the system works alongside the other systems in the same environment. Interoperability means it exchanges data with them that they can use. In terms of the levels of interoperability (a related question in the full bank): compatibility is close to what the foundational level asks for (a connection over which data can be sent and received), and the exchange of usable data starts at the structural and semantic levels.

In the exam: “runs alongside existing systems” points to compatibility, and “exchanges data the other side understands and uses” points to interoperability. When both phrases are in the stem, the answer is the pair together. The other options are good qualities, but they do not describe these two things.

🔗 Related facts and questions

• The levels of interoperability: foundational: one system sends and the other receives. Structural: the format of the message and its fields are agreed. Semantic: the meaning is the same on both sides, thanks to standard vocabularies. Organizational: the policies, governance and consents that allow the exchange.
  Practice question: two systems exchange lab results in correctly formatted messages, but one uses local test codes the other does not understand. Which level is missing? → Semantic.
• Compatibility without interoperability:
  Practice question: a device connected to the network and got an IP address, but the receiving system cannot understand its messages. Which half of the pair has been achieved? → Compatibility only. The remedy for the second half is messaging standards, such as HL7 in device integration (a related question in the full bank), or an interface engine (a related question in the full bank).
• The interface engine: middleware that receives messages from each system, converts their format and routes them to the systems concerned. Each system connects to the engine once, in place of a separate interface between every two systems.
  Practice question: the hospital has 12 systems, each connected directly to the others, and adding a new system needs many interfaces. Which component reduces that number? → An interface engine.
• Standards in the design decision: choosing products that support standards achieves interoperability at lower cost: HL7 for clinical and administrative messages, FHIR (Fast Healthcare Interoperability Resources) for exchange through application programming interfaces, and DICOM (Digital Imaging and Communications in Medicine) for medical images.
  Practice question: a new imaging device must send its images to the picture archiving and communication system (PACS). Which standard is required in its specification? → DICOM.
• The difference between compatibility and interoperability in a practical situation: a related question in the full bank.