Experience

Experience configures the laboratory's consumer-facing presentation and the delivery of that experience. It is configuration of presentation, not a second catalog or a second source of ordering rules.

It is an optional secondary surface. Every consumer order runs on the same canonical catalog, fulfillment, ordering and result infrastructure used by the Partner API, so nothing here duplicates ordering rules. The included template is a configurable presentation of that infrastructure; a custom implementation is a separate optional commercial service arranged with Solia.

• Tests, prices and biomarkers come from the Catalog; only storefront-eligible tests appear, and featured selections that are no longer eligible drop out automatically.
• Collection methods and serviceability come from Fulfillment.
• Ordering eligibility and provider review come from clinical configuration.
• Released results come from Results. Experience edits presentation only and never becomes a second Catalog, pricing or result source.

Experience has its own canonical consumer deployment state. Saving creates an immutable draft revision; publishing promotes a revision to the published revision served publicly. The deployment records its template and version, state, managed and custom domain intent, and draft and published revisions with their timestamps.

• Configure and privately preview — available in Sandbox before Production activation and regardless of Catalog, brand or collection completeness, which affect only how the preview looks.
• Publish — gated server-side by laboratory Production activation, the commercial plan and publish readiness. Publishing is distinct from laboratory activation: an active laboratory does not publish a storefront automatically.

• Standard DTC template — a governed, configurable storefront and Patient Portal. Only allowlisted fields and destinations are accepted; raw HTML, CSS and scripts are not.
• Existing Laboratory Portal mode — results are delivered through the laboratory's own portal at a validated HTTPS address instead of the Solia Patient Portal.
• Domains — a managed address is derived for the laboratory and a custom domain can be requested; the storefront is public only after its domain is provisioned and verified.

Opening a private preview mints a short-lived, signed, Sandbox-scoped preview grant for one workspace. The consumer runtime sends that grant back to the platform, which is the only verifier; it returns the exact current draft revision and the grant also authorizes read-only Catalog and clinical-requirement reads for that workspace.

• Tenant-scoped and fail-closed: an invalid, expired, mismatched or ineligible grant returns nothing and never falls back to a reference template.
• Read-only: a preview grant never authorizes writes, Production orders, payments or access to patient health information.