Integration GuidesGuide
Managed laboratory interfaces
HL7 v2, FHIR and SFTP/file integrations prepared with Solia, and how they differ from self-service HTTPS/JSON.
On this page
Self-service versus managed
- Self-service — HTTPS/JSON Solia Lab Contract (
solia.lab.v1). The laboratory configures its endpoint and credential, runs the connection test and validates in Sandbox itself. - Managed — HL7 v2, FHIR, SFTP / file exchange, Another interface. The laboratory submits interface details and Solia prepares the connection with its technical team.
Limitation
Managed interfaces are not self-service runtime adapters. Submitting a request records it; it does not create a live interface. Production readiness stays blocked until the adapter and validation evidence genuinely exist.
What the laboratory supplies
- Interface type and existing specifications (message profiles, segments, resources or file layouts).
- Laboratory test codes for every orderable.
- The type of authentication required and how sensitive documentation is exchanged — never passwords, keys or tokens in the request form.
- Test endpoints or drop locations and a technical contact.
What Solia manages
- Review and classification of the request, and the resulting adapter.
- Status of the request in the Control Plane, from requested through ready for testing.
- Normalization of orders and results into the same canonical Solia Core used by every channel.
Validation and ownership
Testing becomes available when the managed connection is ready; validation then follows the same Sandbox-then-Production evidence path as HTTPS/JSON. The laboratory remains the system of record for accessioning, analysis and clinical release.