Architecture
Laboratory commercialization infrastructure for reusable growth.
Solia Direct is an operating and connectivity layer for diagnostic laboratories. Connect the laboratory once and reuse that infrastructure across multiple Programs and partners through one Control Plane and Partner API—without replacing the LIS/LIMS.
Programs + partners · Control Plane + Partner API · Solia layer · Laboratory systems
Commercialization infrastructure
Turn existing testing capacity into reusable Program and partner infrastructure.
Instead of rebuilding a catalog, order workflow, result exchange and partner integration for each opportunity, Solia places a shared operating model between Programs and the laboratory environment. Programs and partners connect through the Control Plane and Partner API; Solia coordinates catalog, serviceability, orders and results; existing laboratory systems continue to run accessioning, testing, quality control and official results.
Operating model
Four layers, one direction of dependency.
Different laboratory environments use the same Core with governed configuration and deployment-specific adapters. The laboratory keeps its systems; Solia supplies everything above them.
Solia Core
What is shared across every deployment.
Identity
One consumer identity across ordering, collection, accounts and results, with role-scoped laboratory access separated from consumer access.
Diagnostic data model
Shared objects — order, collection, specimen reference, result set, observation, release state — that every deployment maps into rather than redefines.
Workflow orchestration
Order, collection and result states progress through defined transitions. Eligible failures are retried, and operational exceptions are surfaced instead of hidden.
Structured results
Results are presented from the laboratory's released data with provenance retained — corrections and amendments carry through as distinct versions.
Longitudinal health
Result history and biomarker trends are retained against the consumer identity to support repeat testing.
Tenant isolation
Each laboratory deployment runs isolated from every other deployment, with configuration, data and access scoped to that deployment.
Control + integration
Configuration is an interface, not a rebuild.
Catalog, pricing, experience, collection options, workflow settings and integration configuration are operated from the Control Plane.
See the platform
Boundaries
What is standard, and what is scoped per laboratory.
Configured, not rewritten
Brand, catalog, pricing, geography, collection options and business rules are governed configuration applied to Solia Foundation — the versioned consumer deployment baseline — not a separate codebase per laboratory.
Laboratory stays the source of truth
Clinical data originates in the laboratory's systems. Solia presents and operates around it and does not replace the LIS/LIMS.
Adapters scoped per deployment
Deployment-specific adapters connect Solia Core to each laboratory's systems. Interfaces are specified, mapped and validated with the laboratory — support is stated per system, not assumed.
Environment separation
Sandbox, Staging / UAT and Production are distinct environments. Staging / UAT is non-production, and access is scoped to defined roles.
Deployment Validation
Readiness is verified through Deployment Validation — configuration, interface and launch checks — before a production launch is approved.
Operational exceptions
Eligible failures are retried; operational exceptions are surfaced for review rather than hidden.
Solia does not claim universal LIS compatibility or universal result normalization. Supported standards, existing adapters and custom integration work are stated per deployment on the integrations pages.
Review the architecture against your laboratory environment.
Weighing this architecture against an internal build, a diagnostic infrastructure API or your existing LIS middleware?
Compare Solia Direct