Laboratory environments
Solia Direct + LigoLab
Solia Direct can be deployed around a LigoLab environment using the interfaces that laboratory has configured, while LigoLab remains the laboratory system.
LigoLab publicly describes an end-to-end informatics platform with an interface engine intended to connect the LIS to instruments, EHRs and third-party services. Its public material lists the formats that engine supports, which gives implementation planning an unusually concrete starting point — though what a specific laboratory has configured and licensed is still environment-specific.
How Solia Direct fits around LigoLab
LigoLab laboratories often already operate a configured interface layer, which shortens the distance between an approved Program and a working order path. Solia Direct connects to that layer rather than into laboratory processing: Programs and partners reach the Partner API, Solia validates and normalizes, and orders and results move over whichever interface the laboratory exposes.
The division of responsibility does not change. LigoLab holds the laboratory workflow and the authoritative result. Solia holds Programs, grants, catalog, serviceability, the normalized order and result envelope and the event stream partners consume.
Programs + partners
Consumer, provider-led and partner-led Programs
Control Plane + Partner API
Grants, catalog, serviceability, orders, results, webhooks
Solia operating / connectivity layer
Validation, normalization, mapping, status lifecycle
LigoLab LIS / interface engine
Configured interface in the laboratory's environment
Laboratory workflow + analyzers
Specimen handling, processing, review, release
Solia Direct operates above the laboratory environment. It is not inserted into laboratory processing.
What remains in LigoLab
Solia Direct is not the laboratory system of record and does not become one. The following stay where they are.
Specimen handling and tracking
Receipt, labelling, tracking and case workflow stay in LigoLab.
Instrument and analyzer connectivity
Instrument integration remains a LigoLab-side responsibility.
Result authoring and release
The laboratory produces, reviews and releases the authoritative result.
Rules, automation and billing workflow
Rule and automation engines and revenue cycle workflow remain in the LIS.
What Solia Direct adds around it
Diagnostic Programs
Separately approved Programs that reuse the same underlying laboratory capability.
Partner API + Control Plane
One partner-facing API and one operator surface over the connected environment.
Program access and grants
Scoped credentials and explicit grants that decide which partner can order what.
Reusable catalog and serviceability
A normalized testing catalog with geography, collection and eligibility rules.
Normalized orders and statuses
Order validation, idempotency and a consistent status lifecycle across Programs.
Results delivery and events
Normalized results, corrections and signed webhooks with retries and replay.
Sandbox and Production environments
Separate credentials, synthetic testing and governed Production activation.
Optional Consumer Experience
A consumer-facing ordering and results journey where a Program calls for one.
More detail: Diagnostic Programs and catalog, Laboratory Partner API and laboratory commercialization infrastructure.
Connection paths: self-service and managed
Solia Direct can be deployed around LigoLab using the interfaces available in the laboratory’s environment. There is no native, certified or vendor-approved connector, and no single path fits every deployment.
Self-service
HTTPS/JSON Solia Lab Contract
- The laboratory exposes the HTTPS/JSON Solia Lab Contract, either directly or through its existing integration layer.
- Where a LigoLab environment already exposes REST endpoints externally, mapping those to the Solia contract is often the shortest path.
- The contract is documented, versioned and testable in Sandbox before Production is discussed.
Managed implementation
Environment-specific interfaces
- HL7 v2 order and result messaging through the configured interface.
- FHIR where the laboratory has it enabled for external exchange.
- File-based exchange over SFTP, including CSV and flat-file formats.
- Other site-specific interfaces supported by the environment, scoped with mapping and validation.
What public material supports
- LigoLab's public material describes an interface engine intended to connect the LIS to instruments, EHRs and third-party services such as billing, registries and state reporting agencies.
- That public material lists supported formats including FHIR, HL7, XML, X12, CSV, PDF, flat file, ASTM and RESTful API.
- A documented platform capability is not the same as a configured, externally reachable interface in a given laboratory. Licensing, configuration, network posture and validation requirements still apply.
- There is no prebuilt Solia–LigoLab connector. Each deployment is scoped against the laboratory's actual environment.
Managed implementation scope depends on the LIS product and version, enabled modules and licences, interface capability, deployment model, message profiles, network and security configuration, site-specific mappings and validation requirements. See HL7, FHIR & SFTP.
What moves, and how it is mapped
Solia → laboratory
- Validated order with Program context
- Patient and order identifiers
- Laboratory test / order code for the ordered panel
- Collection and specimen context
- Clinical or ask-at-order-entry data where the test requires it
Laboratory → Solia and partners
- Order and specimen status transitions
- Accession identifiers where the environment exposes them
- Released results with units and reference intervals
- Corrected or amended result versions
- Operational events (rejections, cancellations, exceptions)
- LigoLab test and order definitions are mapped to the Solia catalog entries a Program can order.
- Result fields, units and reference intervals are mapped to the normalized result structure partners consume.
- Case and order statuses are mapped into the Solia status lifecycle.
- Amended and corrected reports are mapped to result versions rather than replacing prior values.
Sandbox first, then governed Production activation
Sandbox
- Synthetic, isolated test activity with its own credentials
- Mapping validation against representative cases
- Order, status and result workflow testing end to end
- Partner-side integration testing before any Program launch
- No Production data and no Production secrets
- Remains available after go-live for regression testing
Production
- The real LigoLab interface, not a simulation
- Validated mappings reviewed against laboratory source data
- Real credentials issued separately from Sandbox
- A Production Program with explicit scope
- Evidence-based readiness review
- Governed activation rather than a self-serve switch
Completing Sandbox testing does not by itself establish Production readiness. See Sandbox and Production.
What becomes reusable after the connection is validated
Once the LigoLab connection is configured and validated, the underlying laboratory capability can be reused across multiple separately approved Programs and partners without rebuilding the LIS integration for each one. Reuse is not automatic approval: every Program and every partner grant is still reviewed and activated on its own terms.
Validated interface
The order and result path does not have to be rebuilt per Program.
Mapping set
Codes, units, intervals and statuses are reused across Programs.
Catalog and serviceability
Test availability and geography rules are defined once.
Partner surface
New partners consume the same Partner API and event contract.
Frequently asked questions
Sources and disclosure
Product and interface references are based on publicly available vendor information as of September 2026. Interface availability and implementation requirements vary by product, version and laboratory environment. Solia Direct is not affiliated with LigoLab.
Interface formats listed above reflect LigoLab's public platform description. Availability in a specific laboratory depends on licensing, configuration and deployment.
Other laboratory environments
Solia Direct + Orchard
A widely installed LIS family, now part of Clinisys. Connection depends on the interfaces enabled in the specific Orchard environment.
Read moreSolia Direct + Epic Beaker
Epic publicly documents HL7 v2 and FHIR laboratory interfaces; activation and configuration are decided in each Epic customer environment.
Read moreSolia Direct + Clinisys / 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 — LIS/LIMS integration overview.
Technical documentation
Continue with implementation detail.
Related: Laboratory connectivity · Laboratory Partner API · HL7, FHIR & SFTP · Diagnostic Programs · Sandbox & Production · Architecture
Review what your LigoLab environment can expose today.
We scope the available interface, the mappings required and the validation path before any Production commitment is made.