Integrations
Connect Diagnostic Programs to the laboratory system of record.
Connect the selected interface to Solia’s shared operating layer while the laboratory’s existing systems remain authoritative.
Technical documentation
Continue with implementation detail.
What the connection carries.
Solia Direct connects partner-led and lab-owned program workflows to the laboratory systems responsible for testing operations and official results.
Inbound to laboratory
- Orders
- Laboratory test codes
- Patient and order identifiers
- Collection context
- Supported order metadata
Returned from laboratory
- Order status
- Specimen and laboratory status
- Official results
- Corrected results
- Amended results
- Result versions
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
LIS / LIMS interface
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
Solia Direct does not replace the LIS or LIMS.
Solia Direct handles order translation, transmission, acknowledgement, specimen and laboratory state updates, result ingestion, mapping and release to the consumer, including corrected and amended result versions, provenance, retries and operational exceptions. Accessioning, analyzer management, quality control, instrumentation, core specimen processing and other laboratory operations remain in the laboratory's existing systems, and the laboratory remains authoritative for accessioning and testing. Compatibility is established per environment; there is no universal LIS connector.
Laboratory remains authoritative
Official results, reference ranges and clinical interpretation stay with the laboratory system of record.
Solia Direct manages the program layer
Partner access, program configuration, order state, workflow coordination and delivery of returned results.
Common laboratory environments
How the connection looks in the systems laboratories actually run.
Solia Direct can connect around each of these using the interfaces available in the laboratory’s environment. None of them requires a native or vendor-approved connector, and none of them is replaced by Solia.
Orchard
A widely installed LIS family, now part of Clinisys. Connection depends on the interfaces enabled in the specific Orchard environment.
Read moreEpic Beaker
Epic publicly documents HL7 v2 and FHIR laboratory interfaces; activation and configuration are decided in each Epic customer environment.
Read moreLigoLab
An end-to-end LIS with a documented interface engine. Connection depends on which of those interfaces the laboratory has configured.
Read moreClinisys / Sunquest
A broad portfolio: Sunquest is now part of Clinisys. Integration options vary by the Clinisys product and version in use.
Read moreDon’t see your LIS? Solia is not limited to the systems listed here. Connection feasibility depends on the interfaces available in your laboratory environment.
Implementation
What to consider before production.
Where PHI is exchanged, implementation must use the contractual and technical safeguards applicable to the parties and data flow.
- 01Interface method selected for the connected environment
- 02Authentication between systems
- 03Laboratory identifiers and record mapping
- 04Test-code mapping and catalog alignment
- 05Order and status mapping
- 06Result provenance, versions and corrections
- 07Exception states and reconciliation
- 08Auditability of material interface events
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