Platform overview

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.

• A laboratory workspace is the tenant. It owns the catalog, programs, fulfillment configuration, orders, customers, results and integrations.
• Programs group what can be ordered, under what conditions, and by whom.
• The Catalog defines orderable tests and panels, and maps them to laboratory codes.
• Fulfillment defines collection models and where a subject can be served.
• Orders and Results are the canonical operational records; the Partner API reads and writes the same records the Control Plane shows.

• Core / Control Plane — canonical laboratory state and the authenticated operating workspace for Catalog, Fulfillment, Programs, orders, customers, results, integrations and readiness.
• Partner API — the versioned server-to-server distribution and integration surface for Program discovery, serviceability, ordering, status, released results and reconciliation events.
• Standard DTC — optional laboratory-branded consumer commerce presentation over canonical Core truth.
• 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.
• Laboratory — seller, merchant, performing-laboratory operator and result authority.

Programs remain laboratory-owned configuration and policy, not a separate product surface. All channels consume governed projections of the same canonical Catalog, Fulfillment, order and Results records.

API integration (internal system or external partner)
  → Partner API authentication, scope and Program grant
  → serviceability + governed order requirements
  → canonical Solia order
  → validated laboratory transport
  → LIS/LIMS accession, specimen and result events
  → released result
  → authorized API retrieval + signed webhook notification

One canonical order and result lifecycle serves every authorized channel. Program policy, mappings and environment boundaries are evaluated before data advances; missing authority fails closed rather than being inferred.