Operation receipts

Verifying a request, recording a decision, closing a session, attesting a service and correcting scope each leave a receipt. The receipt holds a stable operation key, the action, the revision it expected, when it occurred and its result: Pending, Completed, Failed or needs review. It lists the records the action changed and any external reference.

The operation key means a repeated request is recognized as the same action, so a session is not closed twice and a correction returns its earlier result. The Operations Analyst works through receipts that are pending, failed or need review, compares them with the records they name, and closes each one. An action against an external system is never repeated just to find out what happened.

• One key per action. A repeated request with the same key returns the earlier result.
• Expected revision. The receipt records the revision the action was based on. An action on an out-of-date revision is refused.
• Reconcile the exceptions. Receipts are completed only when their effects are found; otherwise they move to needs review with the discrepancy.

Agree who reconciles receipts and how often. Agree what external references point to, such as encounter IDs in the provider’s system. Decide how long a receipt may stay in needs review and who investigates. Agree that failure reasons stay on record.

A reviewer approves a session close while the network drops, and the request is sent again. Both carry the same operation key, so the close is recorded once and the receipt shows Completed. Later a coordinator tries to correct a request using revision 2 when it is already at revision 3. The correction is refused and its receipt shows Failed with the reason “stale revision”.

The Operations Analyst opens the Receipt Ledger, reads the failure reason and confirms with the coordinator that the newer revision is right. A third receipt for an attestation sits Pending; the analyst finds the verified evidence and attested request it names and marks it Completed.

Rehearse these cases before go-live. Send the same session close twice and check one close and one receipt result. Correct a request against an old revision and check the refusal and its reason. Leave one receipt Pending and confirm the analyst can close it from the records it names.

• Receipt Ledger — Receipts by result with operation key, action, expected revision, external reference and failure reason.

• Receipt reconciliation: Close pending, failed and needs-review receipts.

Plan your integrations before linking external references.