Question 1

What is Solia Direct?

Accepted Answer

Solia Direct is an API-first commercialization, connectivity, and operating layer for diagnostic laboratories. It connects laboratory infrastructure to reusable catalog, program, ordering, status, results, and consumer-facing workflows without becoming the laboratory system of record.

Question 2

Who is Solia Direct built for?

Accepted Answer

Solia Direct is built primarily for diagnostic laboratories that want to launch and support multiple diagnostic programs from shared infrastructure. Health companies are a secondary audience when they need connected laboratory infrastructure and fulfillment for a testing program.

Question 3

Does Solia Direct replace our LIS or LIMS?

Accepted Answer

No. Solia Direct connects to a laboratory’s existing LIS/LIMS and provides a standardized commercialization and program layer above it. The laboratory’s existing systems and clinical workflows remain authoritative.

Question 4

What does “connect your laboratory once” mean?

Accepted Answer

It means establishing a reusable connection between Solia and the laboratory’s systems, catalog, mappings, and operating workflows. Compatible laboratory-owned and health-company programs can then use that shared foundation instead of requiring a separate point-to-point build for every program.

Question 5

How is Solia Direct different from a traditional DTC storefront?

Accepted Answer

A traditional DTC storefront is usually one consumer channel. Solia Direct is the underlying API and operating layer that can support a laboratory-owned DTC experience, health-company programs, and other compatible diagnostic workflows from the same laboratory foundation.

Question 6

Can Solia Direct support more than one diagnostic program?

Accepted Answer

Yes. A connected laboratory can configure and operate multiple compatible diagnostic programs while reusing its core catalog, connectivity, and operational infrastructure. Each program can have its own supported testing, collection, geography, and workflow configuration.

Question 7

Can a laboratory launch its own direct-to-consumer testing program?

Accepted Answer

Yes. A laboratory can use Solia Direct to configure a laboratory-owned DTC program, connect consumer ordering and collection workflows, and return laboratory results through the configured experience. Clinical, testing, and regulatory responsibilities remain with the applicable laboratory and providers.

Question 8

Can laboratories support testing programs for health companies?

Accepted Answer

Yes. Laboratories can use the same connected infrastructure to support programs operated with consumer health, digital health, telehealth, wellness, provider, or employer-health companies when the program and laboratory relationship are established and validated.

Question 9

How does Solia Direct work for health companies?

Accepted Answer

A health company defines its diagnostic program, works with a connected laboratory, and integrates with the program-backed Partner API in Sandbox before Production validation. Solia supports the operating connection; it does not remove the need for an established laboratory relationship and program scope.

Question 10

How does Solia Direct connect to laboratory systems?

Accepted Answer

Solia Direct connects through the interfaces available in each laboratory environment. The supported path may use standardized HTTPS/JSON APIs or managed HL7 v2, FHIR, SFTP, and file workflows where applicable to the laboratory’s systems and requirements.

Question 11

Does Solia Direct support LIS/LIMS integration?

Accepted Answer

Yes. Solia Direct is designed to connect with existing LIS/LIMS environments through the interfaces and mappings that environment exposes. The exact integration scope depends on the laboratory system, workflow, and Production validation requirements.

Question 12

What does the Solia API handle?

Accepted Answer

The Solia API provides a standardized contract for configured diagnostic program workflows. Depending on program scope, it can support catalog access, ordering, provider-order requirements where applicable, status exchange, collection and logistics coordination, results connectivity, and related events.

Question 13

How are orders, statuses, results, and webhooks exchanged?

Accepted Answer

Orders, statuses, and results move through configured API or managed interface workflows, with the laboratory remaining the authoritative clinical source. Webhooks notify authorized systems about relevant events so they can respond without repeatedly polling for changes.

Question 14

How does Sandbox → Production deployment work?

Accepted Answer

Sandbox is a separate non-Production environment for configuration and validation using non-Production data. Production activation follows the laboratory-specific connection, mappings, readiness, security, and validation work required for the live environment; Sandbox completion alone does not establish Production readiness.

Question 15

Do we need to rebuild our existing laboratory infrastructure?

Accepted Answer

No. Solia Direct is intended to connect to and extend the laboratory infrastructure already in place. Laboratory-specific interfaces, mappings, or bespoke workflows may still require separately scoped implementation and validation work.

Question 16

How does Solia Direct approach security and data protection?

Accepted Answer

Solia Direct applies encryption in transit and at rest, role-scoped access, laboratory data boundaries, controlled integrations, and result-provenance controls. Production controls are configured and reviewed for the applicable laboratory environment and program scope.

Question 17

How does Solia support laboratory compliance requirements?

Accepted Answer

Solia Direct is designed to support HIPAA-regulated laboratory workflows through deployment-specific safeguards, vendor and subprocessor review, data-flow review, and applicable contractual requirements completed before PHI use. Where a Business Associate Agreement is required, an executed agreement and validated Production configuration are prerequisites. CLIA certification and CAP accreditation belong to qualifying laboratory organizations and facilities—not to Solia Direct—and SOC 2 is not currently attested.

Question 18

How are laboratory and program environments separated?

Accepted Answer

Laboratory records are scoped to laboratory-specific data boundaries and access rules, while integrations and program access are explicitly configured for the relevant environment. Sandbox and Production are separate, and demonstration environments use synthetic data.

Question 19

How is Solia Direct priced?

Accepted Answer

Solia Direct offers a free, synthetic Sandbox and paid Production plans beginning at $2,500 per month. Eligible Production plans include the Standard DTC Storefront and Solia Patient Portal, active partner-program capacity, and a monthly billable Production-order allowance; orders above the allowance continue processing at the applicable published overage rate. Optional custom services and Enterprise arrangements are separately scoped. Current plan details are maintained on the Pricing page.

Question 20

What is involved in implementing Solia Direct?

Accepted Answer

Standard deployments are configuration-led. Laboratories can configure Standard DTC and privately preview the actual application in Sandbox before Production connectivity is complete. Public launch remains gated by Production and readiness. Custom websites, custom consumer experiences, materially bespoke integrations and expanded deployment services are optional and separately scoped.

Question 21

Where can developers find the documentation?

Accepted Answer

Developers can use the canonical Solia Direct documentation site for API references, integration guidance, and deployment information. The public marketing site links to that documentation rather than maintaining a separate copy.

Question 22

How can our laboratory evaluate Solia and get started?

Accepted Answer

Start in Sandbox to configure the laboratory, testing capabilities, fulfillment, and diagnostic programs with non-Production data. When the intended workflow is defined, Solia and the laboratory can scope the Production connection, validation, and any separately required custom work.

Frequently Asked Questions

Platform & Fit

Programs & Use Cases

Integration & Deployment

Security & Operations

Commercial & Getting Started

Review the technical details or talk with our team.