Laboratory IntegrationGuide
Connectivity availability & certification status
Which laboratory transports are executable today, which are implemented but gated, and what certification means.
Three tiers
- Available — the HTTPS/JSON Solia Lab Contract (
solia.lab.v1) and the Solia Test Laboratory in Sandbox. A laboratory can configure, test and validate these itself. - Implemented, not enabled — native REST, FHIR R4, HL7 v2/MLLP, SFTP/file and the private-network Edge agent. The code exists and passes isolated local tests, but runtime gates are off and no installation is approved.
- Installed — a specific laboratory installation that has completed validation and approval. No installation of any native transport exists today.
Important
Solia does not offer zero-code, plug-and-play connectivity to any LIS today. Every native connection requires an installation-specific endpoint, a laboratory or vendor interface license where applicable, approved code mappings, security review and clinical sign-off.
Status matrix
text
Transport Status Certification
HTTPS/JSON Solia Lab Contract (solia.lab.v1) Available Self-service Sandbox connection test and Production validation
Native REST (laboratory-defined JSON API) Implemented, not enabled No laboratory installation validated
FHIR R4 (ServiceRequest / DiagnosticReport) Implemented, not enabled No FHIR server or vendor product certified
HL7 v2 over MLLP (via gateway) Implemented, not enabled No LIS vendor or version certified
SFTP / delimited file Implemented, not enabled No hosted SFTP installation validated
Private-network Edge agent Implemented, not enabled Not deployed; no signed release distributedWhat certification means here
- Local wire test — the protocol code exchanges real bytes with a local test peer. It proves framing and parsing, not interoperability with a vendor product.
- Installation validation — orders, acknowledgements and results exchanged with one laboratory's own test system using approved mappings.
- Clinical sign-off — the laboratory's clinical and IT owners confirm results reach release correctly. Only the laboratory can give this.
Solia publishes no vendor- or version-specific conformance claim until an installation has passed validation with that product.
Choosing a path today
- Can expose or build an HTTPS endpoint → use the HTTPS/JSON contract (Laboratory connection).
- Requires HL7 v2, FHIR or file exchange → submit a managed integration request; it is tracked in the Control Plane and does not by itself create a live interface.
- Evaluating only → use the Solia Test Laboratory in Sandbox. Sandbox proof is never Production validation.