Interoperability Fundamentals

#Exchange is only the first layer

Interoperability is the ability of systems and organisations to exchange information and use it appropriately. Technical compatibility concerns whether information can travel between systems in an agreed structure. This includes connection methods, message formats, authentication and reliable handling of transfers that fail, repeat or arrive out of order.

A working connection does not establish that the receiving system interprets the information correctly. Compatibility depends on the specific standards, versions and local configurations used. Statements that two systems support the same standard should therefore be followed by questions about the exact functions and data that have been tested.

#Preserve meaning and clinical context

Semantic compatibility means that information retains its intended meaning. A number may be misleading without its units, timing or relationship to a particular event. Labels and codes may differ between systems, while an empty field might mean unknown, not assessed or not applicable. These distinctions can matter in care.

Check how patients, encounters and professionals are identified across systems. Incorrect matching can attach accurate information to the wrong context. Also examine how corrections, duplicate records and changes to terminology are handled. Mapping one code to another may require judgement, and some concepts cannot be translated without losing detail.

#Fit the exchange into real work

Workflow compatibility concerns what people can do with the information after it arrives. Ask where it appears, who reviews it and whether an acknowledgement or action is required. Data can be technically available yet practically overlooked if they sit outside the screens or tasks that staff normally use.

Test representative scenarios, including missing fields, delayed transfers and system downtime. Define responsibility for monitoring interfaces and resolving faults on both sides. Plan how changes will be checked before release. Successful integration is an ongoing operational responsibility, not simply a connection completed once and assumed to remain correct.

#Common misunderstandings

Interoperability is often mistaken for a connection between two systems. A connection can carry information without making it understandable or useful. A successful transfer does not prove that the receiving system displays the right details, links them to the right person or makes them available when needed.

Another misunderstanding is that using the same technical standard guarantees compatibility. Standards can allow different implementation choices, so systems still need testing together. Local terminology, missing units and differences in how records represent time can all affect interpretation.

Interoperability also does not mean that every organisation should see every piece of information. Appropriate access, privacy safeguards and clear responsibilities remain necessary. Nor does it automatically remove duplicate work: staff may still need to check conflicting entries or reconcile medicines.

Finally, interoperability is not a one-off installation. Software updates, changing clinical processes and new information requirements can introduce problems that require ongoing monitoring and maintenance.

#Questions worth asking a clinician

• How do you verify that information sent by one system arrives complete and is linked to the correct patient in another?
• How do you check that test identifiers and units mean the same thing in both systems?
• How are missing results, collection times and other clinical context flagged so exchanged information is not misinterpreted?
• How do you test whether exchanged information appears where and when clinicians or researchers need it in their workflow?
• Who is responsible for resolving exchange failures, monitoring data quality and checking that future system changes preserve meaning?