Developer Guide - Idempotency

Summary

• In MP9v3, the MP‑..O transactions do not support duplicate detection at the application level because HL7v3 messages do not contain an Act Id.

• MP9v3 building‑block instances do have a unique GUID, but these are treated as patient documents and must always be processed, even if received multiple times.

• Duplicate detection at the application level is therefore not required or expected.

Platform requirements

Platform‑level requirements for reliable transport can be found under Betrouwbaar transport.

Application requirements

• Duplicate detection at the transport level: Required.

• Duplicate detection at the application level: Not expected.

Additional clarifications:

• Because MP9v3 HL7v3 messages lack an Act Id, application‑level duplicate detection is not technically possible on that basis.

• Although building blocks contain a GUID, a repeated instance must still be processed upon each receipt.

• A prescription may only be sent once (functionally and legally).

  • Therefore, an MP‑VOS receiver may implement optional duplicate detection if the same VV instance is received twice.

  • This is not defined as a formal requirement.

Avoid duplicate on notifications

Known issue
In the GBx response to the infrastructure transaction 'v3 - Afleveren ... signaal' the GBx should not apply duplicate detection on transport level.
AORTA-LSP is currently not yet tolerant for Soap-client faults or AE Application Acknowledgement Error Key205 responses by the GBx.