⌘K

Integration GuidesGuide

Result ingestion & release

How results return from the laboratory, how release works and what is authoritative.

On this page

Lifecycle

text
Laboratory result event → validated & correlated → append-only version
  → release → Partner API / Patient Portal / events
  • Partial, final and corrected results are separate append-only versions; superseded versions are retained.
  • Only released versions are exposed externally; unreleased versions read as pending or not found.
  • Critical results emit result.critical as an escalation signal; details are read from the API.

Ingestion path

With HTTPS/JSON, the laboratory sends signed inbound events (ack, accession, specimen_status, result, report_metadata) correlated to the exact adapter, transmission and order. Managed interfaces normalize into the same lifecycle.

Authority and auditability

  • The laboratory's release decision and its governed report are the official result.
  • The report is retrieved per request through GET /v1/orders/{orderId}/results/{resultId}/report; no permanent or signed URL is issued.
  • Every version keeps provenance, and release, correction and delivery outcomes are recorded.

Related resources