Laboratory IntegrationGuide
Order interface
How orders are delivered to the laboratory.
Expectations
- Orders are POSTed to
/orderswith the correlation headers above; retain the canonical order identifier and transmission identifier. - Delivery is idempotent by
Idempotency-Key: a repeat of the same transmission must not create a second order. - Orderables are identified by your mapped laboratory codes, so an unmapped orderable is blocked upstream rather than delivered ambiguously.
Retry semantics
- Up to 5 attempts, with exponential backoff from 30 seconds up to a 60-minute ceiling.
- Network errors, timeouts, 408, 425, 429 and 5xx responses are retried; a contract violation is not retried, because repeating an invalid payload cannot succeed.
- The scheduled transport process claims queued transmissions with a bounded lease, records attempts and acknowledgements, and safely returns when no work is due.
- A transmission that cannot be delivered is raised as a canonical transmission exception on the order rather than silently dropped.