Exceptions

Specimen, sample and result problems are represented as canonical exceptions on the order, readable in the Control Plane and through the order exceptions endpoint. An exception is an operational fact to resolve, not a free-text note.

Preserve the original correlation, environment, transmission state and safe request ID. Do not put clinical payloads, passwords or keys in support requests. A sending record after a crash is not permission to retry; result receipt and canonical release are separate outcomes.

• Native REST/FHIR source paths mark uncertain post-send outcomes delivery unknown. The executable HTTPS/JSON worker still retries classified failures and can mark a failed sent-state write retryable; do not assume its behavior is identical.
• Native delivery-unknown transmissions are non-retryable. The HTTPS/JSON retry-safety gap remains unresolved; preserve original correlation and have an authorized operator confirm the laboratory outcome rather than create a replacement order.
• Reprocessing is limited to roles with operator authority and is scoped to the selected environment; Sandbox and Production exceptions are never mixed.