Result polling, correlation, clinical release & corrections

Results arrive through the HTTPS/JSON contract as signed inbound events (timestamp tolerance 300 seconds). Native result polling for REST and FHIR is implemented but blocked: it needs a tenant-scoped scheduling authority in Solia Core that is not yet available.

• Every result must correlate to a Solia order and its transmission; caller-supplied correlation is never trusted on its own.
• Results for an order whose specimen was not accepted by the laboratory are not released.

• Preliminary, partial, final, corrected and amended results are distinct versions. A newer version never silently overwrites an earlier released one; corrections are recorded as new versions.
• Duplicate deliveries are deduplicated by the transport's message identity.

The laboratory is the clinical authority. Solia exposes a result through the Partner API and events only after release evaluation in Solia Core; a transport acknowledgement or result receipt is never release.