Laboratory connectivity release status (October 2026)

• HTTPS/JSON Solia Lab Contract with signed lifecycle and result events, bounded retries and SSRF-protected destinations.
• Sandbox with the Solia Test Laboratory, including synthetic orders, acknowledgements, accessions and result release.
• Partner API v1 with scoped keys, Program grants, idempotent order creation and signed webhooks.

• Native REST, FHIR R4, HL7 v2 over MLLP and SFTP/file adapters, the standalone gateway and the outbound-only Edge agent. These pass isolated local tests against locally hosted synthetic servers; that is not vendor certification.
• Disabled native REST/FHIR paths record uncertain post-send outcomes as delivery unknown without automatic resend. HTTPS/JSON retains classified retries and a retryable refused sent-state write; that unresolved gap requires separate safety review. Preserve the original transmission for authorized reconciliation.
• HL7 CA is a commit acknowledgement only; application acceptance requires AA. AE, AR, CE and CR are rejections.
• Results enforce reported status (preliminary, final, corrected, amended); corrections create new versions, and release to partners is evaluated separately from receipt.

1. Licensed LIS product and version, plus interface specification and any interface licence.
2. Laboratory IT contact, an approved test endpoint and network path, and test credentials.
3. Test patient identifiers and a mapping for every orderable and result.
4. A signed test plan covering orders, acknowledgements, accessions, final and corrected results, rejection, duplicates and recovery.
5. Laboratory clinical and security sign-off before Production.

The same steps repeat for each additional site; mappings and approvals are per laboratory and environment and are never inherited.