...
- If the specification is about a communication protocol (e.g. a transfer protocol, an interface like the eHealth Hub webservices) and about the behavior of processors of this protocol, then interoperability is understood as the ability of two implementations of this specification – i.e. processors of this protocol - to communicate properly. In the case of an interface, ability of a user entity to communicate with an implementation (or processor) of the interface.
- If the specification is of an artifact (e.g. a business document, a process definition, a policy contract, a medication scheme), then interoperability is understood as the ability to process this artifact with consistent results, using different platforms or processors. In such a case, interoperability is often described as portability from the artifact perspective (the artifact is portable across platforms), while the platforms or processors are qualified as interoperable.
Taking responsibility
Be aware that it is not always clear which aspects of interoperability fall under the specification writers responsibility, and which fall under the implementation developers responsibility. Too often interoperability problems arise when each party is over-reliant on the other party to ensure interoperability.
Guidelines
Clear understanding of specification
When you are developing an implementation, make sure that you have a clear understanding of the specification of the protocol and the artefact. The specification should is meant to be precise enough to ensure that your implementation is interoperable with others or is at least very close to be. In case of questions, do not consciously make assumptions but contact the writer of the specification. Interoperability is primarily a matter of correct and consensual interpretation of this specification.
Taking responsibility
Be aware that it is not always clear which aspects of interoperability fall under the specification writers responsibility, and which fall under the implementation developers responsibility. Too often interoperability problems arise when each party is over-reliant on the other party to ensure interoperability.
Guidelines
Take into account the the intended audience of the specification is wide. Knowing that product managers, end-users, test developers or product developers not always fully share the author’s background and expertise, be aware that interpretation mistakes or liberties will abound.
Defined behavior after errors
...
- the errors from "Errors" section of the specification, . This mainly concerning concerns the protocol specification.
- errors after reception of faulty artefacts from another implementation.
- errors when processing correct artefacts by your implementation
- errors during generation of faulty artefacts by your implementation
...