Documentation
Solia Direct documentation
Operate diagnostic programs, connect a LIS or LIMS, integrate the Partner API, and manage optional DTC and Solia On Demand channels. The API reference is generated from the contract the server enforces.
One connection, multiple programs
One canonical laboratory connection supports governed Programs, partner ordering, laboratory-branded DTC, and published Solia On Demand discovery. The laboratory remains the seller and clinical authority.
Laboratory Partner ServicesLaboratory business relationships, four workspace surfaces and non-executable evidence boundaries.QuickstartLaboratory setup, then a complete Sandbox developer workflow from authentication to a released result and reconciled events.Laboratory IntegrationTechnical hub for connecting a LIS or LIMS: architecture, transports, contracts, operations and troubleshooting.Compendium & clinical reviewImport, review and reimport a laboratory menu without inventing native codes, clinical equivalence or publication.Laboratory engineering runbookAn ordered founder, IT, clinical and security handoff with explicit stop conditions.Partner APIOne versioned API for programs and catalog, serviceability, orders, results and events.Webhooks & EventsRegistration, signature verification, delivery and retry semantics.Standard DTCHow the optional consumer storefront is served from canonical platform truth.Solia On DemandThe B2B laboratory discovery network consumer health companies use to find laboratory supply and move into a governed Diagnostic Program.Security / Production ReadinessWhat must be true before a laboratory goes live, and how activation finalizes.API ReferenceThe versioned Partner API surface, its envelopes and its machine-readable description.
Developer hub
Laboratory Partner Services
- Laboratory Partner Services architecture
- Partner connections, introductions and existing accounts
- Diagnostic Program service assignment and compatibility
- Clinical authorization, mobile collection and devices
- Kitting, inventory, shipments and specimen receipt
- Partner Services security, errors and reconciliation
- Partner Services isolated conformance and Sandbox runbook
- Partner Services activation prerequisites and operations
Laboratory Engineering
- Laboratory integration architecture & authority
- Universal compendium & native catalog workflow
- Reviewed terminology & panel equivalence
- Versioned connector profile engineering
- Nexus-shaped synthetic conformance walkthrough
- Independent Programs on one laboratory installation
- Network testing discovery, packages & price visibility
- Results, receipts & uncertain-send incident playbook
- Integration testing & acceptance evidence
- Operator onboarding & go-live inputs
- Integration troubleshooting & practical FAQ
Reference Testing
- Reference testing architecture & dual-role laboratories
- Reference mappings, private pricing and referral orders
- Reference results, exceptions & pilot runbook
- Laboratory invitations, claims and bilateral relationships
- Reference Programs and fail-closed eligibility
- Reference native catalog, clinical mapping and specimen review
- Reference order lifecycle, correlation and idempotency
- Reference specimen custody and accession evidence
- Reference results, correction lineage and scoped webhooks
- Reference troubleshooting, refusal codes and safe reconciliation
- Two-laboratory reference Sandbox conformance and evidence tiers
- Reference activation and operating runbook
Health Companies
Platform
Partner API
Laboratory Integration
Integration Guides
Standard DTC
Security & Production
Reference
Support
External resources
The Partner API is also published as a machine-readable OpenAPI 3.1 description at /api/public/partner-openapi.