Laboratory API platform
Connect your laboratory once. Support every program through one API.
Solia Direct gives laboratories one standardized way to support catalog, serviceability, orders, specimen status, results and events across DTC and external diagnostic programs—without rebuilding integrations for each new program.
Your existing systems stay in place. Your laboratory remains authoritative for testing operations and official results.
A reusable foundation
One connection. More programs.
A laboratory should not need another custom integration every time a new health company, employer, wellness platform or consumer program needs testing fulfillment.
Each program is configured and approved independently, then runs on the same connected laboratory foundation.
Lab-owned DTC
Your own branded consumer program.
Health-company programs
Approved programs from consumer-health partners.
Employer / wellness programs
Configured testing programs for supported populations.
Provider-led programs
Programs that include an approved provider-order workflow.
The standardized workflow
One API covers the workflow your programs need.
Catalog
Expose approved tests and panels consistently.
Serviceability
Show where each approved program and collection path is available.
Orders
Receive standardized orders without rebuilding partner-specific workflows.
Provider workflows
Coordinate provider-order steps where the program requires them.
Collection
Carry the collection context needed for the configured workflow.
Specimen and order status
Give programs a consistent view of progress through the laboratory workflow.
Results
Return released laboratory results through the same contract.
Webhooks and events
Keep programs updated as orders move through the laboratory workflow.
How it fits
One operating layer between programs and your laboratory.
DTC / health-company programs
Lab-owned DTC · health companies · employers · provider-led programs
Solia Direct
Catalog · Orders · Collection · Status · Results · Webhooks
Your laboratory
LIS/LIMS · existing APIs · interfaces
Every new program should not become another technology project.
Without Solia
- Health Company A → custom build
- Health Company B → another integration
- DTC → another workflow
- Employer program → another implementation
With Solia
One laboratory connection
Solia standardized API
Multiple approved programs
Real product, shared operations
Operate every program from one Control Plane.
Configure approved programs, manage their catalog context and move connections from isolated testing toward controlled Production use.
Your systems remain authoritative
Keep the laboratory infrastructure you already operate.
Solia Direct sits above existing laboratory systems. It does not require replacement of your LIS/LIMS, testing workflows, result-authoring systems or authoritative laboratory records.
Solia connects through the interfaces available in each laboratory environment. Protocol, mapping and validation details are defined for that environment.
Laboratory governance
Your laboratory stays in control.
Solia standardizes how approved programs connect while the laboratory controls the operating decisions behind them.
- Catalog
- Pricing
- Serviceability
- Supported geographies
- Collection options
- Program activation
- Partner access
- Results
- Production activation
From evaluation to Production
A controlled path to a live program.
- 01
Sandbox
Explore the standard workflow with synthetic, non-Production data.
- 02
Configure
Set the program, catalog, access and laboratory connection details.
- 03
Validate
Test mappings and the end-to-end workflow against the laboratory source.
- 04
Production
Activate once credentials, validation and readiness requirements are complete.
Implementation options
Choose the support your environment requires.
Standard deployment
Configuration-led deployment using Solia’s standard connection and Control Plane workflow.
Optional white-glove implementation
Available for laboratories that want Solia to manage agreed-scope onboarding, setup, supported integrations, validation and Production deployment.
Typical target: 2–4 weeks once required access, credentials and dependencies are available.
This service is optional—not required for a Production subscription or DTC capability. Genuinely custom integration work may be scoped separately.
Technical trust
Built for controlled Production use.
Controlled access
Each program receives only approved access.
Sandbox / Production separation
Validate with synthetic data before Production.
Duplicate protection
Repeated requests do not create duplicate orders.
Auditable lifecycle
Orders, results and key connection events remain traceable.
Validated mappings
Production connectivity is tested against the laboratory source.
Clear integration scope
Standard, reusable and environment-specific work are identified before activation.
Implementation clarity
Clear about what is standard and what requires implementation.
Supported standard
A protocol or interface Solia supports, including REST APIs, webhooks, HL7, FHIR and file-based exchange.
Existing reusable adapter
A connector Solia has already implemented and can reuse, subject to environment-specific configuration and mapping.
Custom / environment-specific integration
Scoped work against the laboratory’s own systems, interfaces and identifiers.
Technical documentation
Ready for the technical details?
Does Solia replace our LIS or LIMS?
No. Your LIS or LIMS, testing workflows, result-authoring systems and authoritative laboratory records stay in place. Solia sits above them as the standardized program and connectivity layer.
Can Solia work with our existing laboratory API?
Yes, when the available interface supports the required workflow. An existing laboratory API can sit underneath Solia as an adapter or input, with environment-specific mapping and validation where needed.
Can one laboratory connection support multiple programs?
Yes. One validated connection can support DTC and multiple separately approved external diagnostic programs. Each program still requires its own configuration, authorization and Production readiness.
How is partner and program access controlled?
Credentials and permissions are scoped to the approved client, program and environment, so each program receives access only to the catalog, workflows and data it needs.
What is required before Production activation?
Production activation requires approved program scope, real credentials, completed mappings, end-to-end validation and readiness sign-off for the connected laboratory environment.
Connect your laboratory once. Launch the next program faster.
Use the same connected infrastructure to support the next approved diagnostic program without starting another custom technology project.