Get started
Start with your laboratory in Sandbox.
Laboratory owners can explore Sandbox and configure tests, availability and Programs without hand-building an interface. Your technical team validates the real laboratory connection separately before Production.
Direct connectivity uses a compatible HTTPS/JSON Solia Lab Contract with credentials and mappings. Managed HL7, FHIR and file paths require environment-specific feasibility and validation; bespoke work is scoped separately.
Sandbox workspace
Minutes
Workspace, laboratory profile, testing capabilities, Fulfillment, Programs and Sandbox configuration.
Production connection
Depends on laboratory environment
Existing API or LIS/LIMS connections, mappings and validation requirements determine Production timing.
Custom implementation
Scoped separately
Custom DTC experiences, bespoke interfaces and other non-standard work may require a separate timeline.
Five steps
Explore Sandbox → Configure → Validate → Request Production activation.
01
Minutes
Explore Sandbox
Create a laboratory workspace without hand-building a LIS connector; use synthetic data only.
02
Minutes
Configure
Add tests, panels, collection methods, geography, Fulfillment and other laboratory configuration.
03
Immediately available
Exercise synthetic workflows
Evaluate supported orders and results in Sandbox. Synthetic activity does not prove external LIS compatibility.
04
Environment-specific
Validate
With your technical team, validate real-interface mappings, ACKs, status and released results for the approved Program.
05
Depends on laboratory environment
Request Production activation
Request controlled activation after separate credentials, technical evidence, operational readiness and commercial approval are complete.
Available out of the box
Out of the box by default.
The core Solia Direct operating layer already exists. Laboratories configure their environment rather than waiting for Solia to build a new platform for each account.
Laboratory workspace
Control Plane
Laboratory profile
Testing capability configuration
Catalog and panels
Fulfillment configuration
Diagnostic Programs
Sandbox environment
Partner workflow infrastructure
Order, status and result infrastructure
Sandbox and Production environment separation
Standard Solia configuration
Production and custom work
Implementation only where your environment requires it.
Some laboratories require additional work before Production because their existing systems, mappings or workflows are specific to that laboratory.
LIS/LIMS interface configuration
Laboratory-specific test and result mappings
Managed HL7 v2 interfaces
FHIR where applicable
SFTP and file workflows where applicable
Custom APIs or workflows
Production interface validation
Bespoke consumer and DTC implementations
Custom integrations outside standard Solia configuration
What determines Production timing?
Workspace setup is not a Production launch. Begin configuration in Sandbox while your laboratory’s interface feasibility and dependencies are assessed.
Production timing depends on endpoints, credentials, code mappings, provider or collection dependencies, end-to-end evidence and approval. Implementation schedules are agreed after scope is understood, not guaranteed.
Workspace configuration first. Real-interface validation before Production.
Self-service / configuration
- Laboratory profile
- Tests, panels and availability
- Collection methods and geography
- Fulfillment configuration
- Diagnostic Programs
- Pricing and commercial settings where supported
- Experience configuration where supported
- Users, permissions and Sandbox configuration
Implementation / validation when required
- Custom LIS/LIMS interfaces
- Laboratory-specific mappings
- Managed interface work
- Bespoke workflows and custom APIs
- Production validation
- Custom DTC and consumer implementation
Sandbox uses synthetic data and separate credentials. Production requires its own Program scope, credentials, validated real laboratory interface and technical, operational and commercial readiness; no automatic go-live follows Sandbox completion.
Common questions
How long does implementation take?
Workspace configuration can begin quickly in Sandbox. Production timing varies with interface feasibility, access, mappings, validation and approvals; no 2–4 week launch is guaranteed.
Can we use Solia before our Production connection is complete?
Yes. Sandbox is a separate non-Production environment for configuration and validation. Production remains governed by the existing readiness and validation requirements.
What can require custom implementation?
A compatible HTTPS/JSON Solia Lab Contract can be implemented by the laboratory’s technical team. Managed HL7 v2, FHIR and file paths require environment-specific feasibility, specification and validation; bespoke work is scoped separately.
The platform is ready
Begin your laboratory evaluation.
Explore Sandbox now; request Production activation after the laboratory-specific validation and readiness work.
