Integration receipts

A connected system retries an event after a timeout. The service manager finds the receipt by provider and external event identifier, then compares its payload hash, received time and processing status. A rejected receipt remains visible after a corrected delivery arrives. The manager can reconcile the two outcomes without treating transport receipt as successful application.

A receipt records the provider, external event identifier, received time, payload hash and processing status. Those fields let the service manager compare repeated deliveries from one source. Reconcile the event with the provider identifier and the source owner’s evidence.

• Receive. Retain the source identifier and payload hash when an inbound event is recorded.
• Classify. Distinguish Received, Applied, Rejected and Failed rather than treating arrival as completion.
• Reconcile. Compare a rejected receipt with any corrected delivery by provider and external event identifier.

A different payload hash may explain why a later delivery had a different outcome. Preserve both receipts when reviewing a retry.

Agree which connected system owns each provider name and how its event identifiers are formed. Decide who investigates Rejected and Failed outcomes, and what source evidence is needed before asking for a replay. Keep credentials and transport configuration with the connected system owner.

Test a retry with the same event identifier. The manager should compare received times, hashes and statuses before concluding which delivery was applied. An event merely marked Received still needs an outcome check.

Rehearse a failed inbound event and a corrected resend. Find the original receipt by provider and external event identifier, compare its hash and time with the later receipt, and record which status belongs to each. Ask the source owner to confirm what was resent.

The service manager should be able to explain why the earlier Rejected or Failed result remains in the ledger. Do not convert the first receipt to Applied merely because a later event succeeded; keep both outcomes available for reconciliation.

The rejected receipt screen is the quickest starting point for an exception. Read the original event identifier and hash before requesting a corrected delivery. After the source owner confirms the resend, compare its received time and processing status with the earlier row. Both rows should remain available for the next reconciliation review, with their original times and statuses intact.

• Rejected Clinical Integration Receipts — Review the filtered records and choose the next action.
• Open Clinical Incidents — Open related records before the handoff.

Follow the related process.