Platform overview

• 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.

• Control Plane — the authenticated operating workspace for catalog, fulfillment, orders, customers, results, integrations, access and launch readiness.
• Partner API — the versioned server-to-server interface for Program discovery, serviceability, ordering, status, released results and reconciliation events.
• Experience — an optional consumer presentation on the same governed catalog, fulfillment, ordering and result infrastructure; it is not a separate operating system.

Partner system
  → 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.