Integrations
Laboratory connectivity for the systems you already run.
Solia Direct sits around the LIS/LIMS and laboratory systems already in place. One validated laboratory connection can support multiple approved Programs and partners without making Solia the system of record.
Technical documentation
Continue with implementation detail.
What the connection carries.
Solia Direct sits around the LIS/LIMS and laboratory systems already in place. One validated laboratory connection can support multiple approved Programs and partners without making Solia the system of record.
Into the laboratory
- Program-aligned orders
- Identifiers and requirements
- Catalog and serviceability context
- Acknowledgements and status
Back to Programs
- Laboratory status
- Released results
- Corrections and amendments
- Operational events
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
Validated laboratory connection
Selected integration
Laboratory systems
LIS / LIMS · APIs · files · validated adapters
Object mapping
How Solia objects relate to laboratory systems.
Mapping is defined per connected environment. Not every object uses the same method — some arrive through an API, others through HL7, FHIR or an interface adapter.
| Solia object | Typical external source |
|---|---|
| Order | Consumer / ordering workflow |
| Clinical order | Provider / order service |
| Collection | Scheduling / collection network |
| Specimen + accession reference | LIS / laboratory workflow |
| Result set | LIS / laboratory API |
| Biomarker observations | Result interface |
| Corrected / amended result | Laboratory |
| Release state | Solia workflow |
How Solia Direct fits
A connectivity layer, not a universal connector.
The self-service path is the HTTPS/JSON Solia Lab Contract. HL7 v2, FHIR, SFTP/file and laboratory-specific interfaces are managed paths that require environment-specific specification, mapping and validation. Existing laboratory systems remain authoritative.
Reusable connection
Catalog, serviceability, orders and results can be reused across separately approved Programs.
Explicit mappings
Codes, identifiers, statuses, units, reference intervals and result versions are validated for the connected environment.
Operational control
Acknowledgements, retries, exceptions and reconciliation are observable rather than hidden.
Clear boundaries
Accessioning, analyzers, quality control, specimen processing and official results stay in laboratory systems.
Implementation
What to consider before production.
A buyer should evaluate the actual interface available in each environment, mapping ownership, failure handling, validation evidence and the operational team responsible for exceptions. Solia does not claim plug-and-play compatibility with every laboratory system.
- 01Current interface and transport
- 02Catalog and serviceability ownership
- 03Order, identifier and status mappings
- 04Result provenance and correction handling
- 05Acknowledgements, retries and exceptions
- 06Sandbox test evidence
- 07Production credentials and network controls
- 08Operating ownership after launch
Data & control
Integration starts with clear system boundaries.
Minimum necessary access
Only exchange the information required for the supported workflow.
Explicit authorization
Credentials, services and staff access should be scoped to defined functions.
Provenance + auditability
Orders, result versions and material integration events should remain traceable.
Appropriate agreements
Where Solia Direct acts as a business associate and handles PHI on behalf of a covered entity, appropriate contractual and technical safeguards must be established before production use.
How we describe integrations
Three integration states — stated precisely, per connected environment.
Solia Direct does not display vendor logos for systems it has not connected to. Each integration is classified for the connected environment before implementation begins.
Supported standard
A protocol or interface the platform supports — HL7, FHIR, REST APIs, webhooks and file-based exchange.
Existing reusable adapter
A connector Solia has already implemented and can reuse in a new deployment, subject to environment-specific configuration and mapping.
Custom / environment-specific integration
Scoped implementation work against the laboratory's own systems, interfaces and identifiers.
Third-party relationships are identified during Production connectivity planning. They are not published as an integration maturity state.
How integrations are delivered
Standardized configuration where possible. Managed implementation where healthcare infrastructure requires it.
Configurable integration setup
Configured by the laboratory in the Control Plane — catalog and pricing, payments, notifications, collection options, branding and consumer experience settings.
Solia-managed implementation
LIS/LIMS, HL7 and FHIR interfaces, proprietary laboratory APIs, result mapping, clinical and provider infrastructure, and complex collection routing. These are scoped, specified and validated with your teams — not one-click connections.
- 01RequirementsSystems, interfaces, data and workflows in scope.
- 02ConfigurationStandardized settings applied in the Control Plane.
- 03Credentials & specificationAccess, endpoints and message specifications agreed.
- 04ValidationMapping and result fidelity reviewed against laboratory sources.
- 05TestingEnd-to-end runs in a non-production environment.
- 06Production activationControlled enablement once sign-off is complete.
Connect Solia Direct to the infrastructure you already run.
We’ll map the systems, workflows and data exchanges required for your laboratory deployment.
Weighing this connectivity model against an internal build, a diagnostic infrastructure API or your existing interface engine?
Compare Solia Direct