Execution history

Each operation run freezes the order revision and input hash at the start of execution. Its status and result reference show whether the operation completed or needs review. Execution attempts record individual tries under an operation key, including provider reference and failure reason. This separation helps the team distinguish a failed attempt from the final state of an order.

Operation steps retain action names, input and output references, external receipt identifiers, receipt dates and attachments. State history records each order transition with its source revision, actor and reason. These records matter most when a release, external acknowledgement or later correction is questioned. They allow a reviewer to follow the path from order revision to external result.

• Follow the run. Start from the source order and revision, then inspect its operation key and result.
• Inspect each step. Read the action, input and output references, status and external receipt evidence.
• Reconcile transitions. Use state history to see the actor, reason and revision behind an order status change.

Agree how an operator identifies a retry by operation key and what external evidence confirms success. Decide who investigates Failed, Unknown and reconciliation required results. Rehearse a correction to an executed order: the successor revision must keep the earlier completed steps and review decision visible. Confirm how the team links a receipt to the step that produced it.

Take a report release whose first provider response is Unknown. The team inspects the attempt and run instead of creating an unrelated release. When a confirmed receipt arrives, it belongs to the appropriate operation step. If reconciliation is required, the run stays in that state with its reason. A later correction refers to a successor revision and preserves the completed earlier steps. Reviewers can compare the order’s status history with the execution result before accepting a final state.

The reviewer traces the Unknown attempt to its source order and checks whether the run needs reconciliation. A later receipt belongs with the relevant step, including its date and external source. The order’s state history should identify the actor and revision behind the final transition. If a correction follows release, the original run and completed steps remain accessible alongside the successor revision.

• Execution exceptions — Review failed and reconciliation-required runs with their source order.
• Released Imaging Orders — Trace released cases back to their accession and study identifiers.

Follow the related process and the data model for the records behind each decision.