PlatformGuide
Architecture
How requests, tenancy, and the partner surface fit together.
Layers
Solia Direct is the operating and connectivity layer for diagnostic laboratories: one canonical Control Plane supports Partner API integrations, optional laboratory-branded DTC, and optional distribution through Solia On Demand—without replacing the LIS/LIMS.
- Application layer: a React/TanStack Start application serving the Control Plane and this documentation site.
- Server layer: typed server functions for app-internal logic and HTTP routes for external callers, including the Partner API surface and its machine-readable description.
- Data layer: a Postgres database with row-level security; every operational read and write is evaluated against the caller's authorized workspace.
- Consumer runtime: the optional Standard DTC Storefront and Patient Portal are a separately deployed application. It holds no catalog, pricing, clinical or result data of its own; it reads governed projections from the platform and submits transactions only through supported interfaces.
- Solia On Demand is the optional business-to-business laboratory discovery and distribution surface for Health Companies. It exposes explicitly published inventory and governed introductions, not consumer checkout or patient commerce.
Important
Configuration and deployment authority for the consumer experience stays in the Control Plane. The consumer runtime renders what the platform authorizes and fails closed when authority is missing.
Tenancy
Authorization is workspace-scoped and fail-closed: when a caller's authorization for a workspace cannot be proven, access is denied rather than assumed. Partner API keys are additionally bound to one environment and one scope set.
Important
Availability of any given capability depends on the laboratory's configuration and activation state. The documentation describes what the platform enforces, not what a specific workspace has enabled.