Key takeaways
- Technical interoperability and business understanding are different.
- All four aspects may be needed together.
- Sharing requirements should be considered early and followed through implementation.
Four complementary aspects
Interoperability concerns the ability to share information and services usefully. Presentation interoperability addresses user access and presentation. Information interoperability concerns information meaning, structure, and exchange. Application interoperability concerns exchanges between application functions. Technical interoperability concerns the technical mechanisms enabling those exchanges.
A common protocol therefore does not guarantee that two organizations understand data in the same way. An “end date” field needs shared meaning, a suitable representation, and usage rules. Interoperability requires coordinated decisions across several architecture domains.
A concern throughout the cycle
The vision identifies sharing needs and actors. Business, Data, Application, and Technology Architectures refine requirements and mechanisms. Realization and migration phases translate these into solutions and planned work. Phase F organizes migration; it is not itself the activity that installs software. Implementation is monitored through Phase G governance.
- Define the meaning of shared information.
- Identify contracts, interfaces, and technical constraints.
- Verify actual usage and the operational conditions of exchanges.
TERMS TO KNOW
The terms, in context.
- Information interoperability
- Ability to share information with usable meaning and structure.
- Technical interoperability
- Compatibility of technical exchange mechanisms.