Laboratory connection

Solia owns the ordering channel, catalog, program governance, partner authorization, order lifecycle state, released-result exposure and audit records. The laboratory system remains the system of record for accessioning, analysis and clinical release. The connection is the contract between the two.

Solia order queue → HTTPS/JSON order POST → laboratory acknowledgement
Laboratory → accession/specimen/result/report event → Solia lifecycle
Solia released result → Partner API + signed event notification

• HTTPS/JSON Solia Lab Contract — the self-service executable transport available today for outbound orders and authenticated inbound lifecycle events.
• HL7 v2, FHIR and SFTP/file — managed integration request paths. Solia records discovery and delivery status; these modes are not presented as self-service runtime adapters.

Selecting a managed mode records an integration request; it does not claim that a live interface exists. Production readiness remains blocked until the resulting adapter and validation evidence genuinely exist.

• A public HTTPS endpoint for connection tests and order receipt, or existing interface specifications for a managed integration.
• The required authentication method and credentials through the protected configuration flow.
• Laboratory test codes and mappings for every orderable item.
• Acknowledgement, accession, specimen-state, result and report behavior for conformance testing.
• Separate Sandbox and Production endpoints and credentials; Production configuration is never copied from Sandbox.

• Contract version solia.lab.v1, sent on every request as X-Solia-Contract-Version.
• Adapter keys: solia-lab-https-sandbox for sandbox connectivity and solia-lab-https for production connectivity — a sandbox adapter can never carry production traffic.
• Correlation headers: X-Solia-Tenant-Id, X-Solia-Adapter-Key, X-Solia-Transmission-Id and Idempotency-Key.
• Endpoints on your side: /connection-test for connection testing and /orders for order delivery.
• Outbound authentication is either Authorization: Bearer <secret> or an API-key header (default X-API-Key).
• Request timeout 15 seconds; response bodies are read up to 512 KB and inbound bodies up to 1000 KB.

A connection test performs a bounded authenticated request to the contract test path and records whether reachability, authentication and contract-version agreement succeeded. Success is evidence for that exact adapter and environment; it does not activate Production by itself.

Sandbox proves the contract with synthetic data; Production carries live operations. They use separate configurations, credentials and adapters, and outbound DNS is re-evaluated before delivery so a configured hostname cannot resolve to a private destination at send time.