Can Solia Direct work with Clinisys or Sunquest?

Solia Direct can be deployed around these environments using the interfaces available in the specific product and version. There is no out-of-the-box or vendor-approved Clinisys connector.

Is Sunquest still a separate system?

Sunquest is now part of Clinisys, and specific integration options vary by the Clinisys product and version in use. Legacy Sunquest environments are still common and are scoped on their own terms.

Why does Orchard have its own page if it is also Clinisys?

Orchard was acquired by Clinisys in 2025 but remains a distinct, widely installed product family with its own interface characteristics, so it is documented separately.

Does Solia replace the LIS?

No. The Clinisys environment remains the laboratory's operational system of record and the source of the authoritative result.

What is the self-service path?

The laboratory or its integration layer exposes the HTTPS/JSON Solia Lab Contract, often by mapping an existing orders and results API to it.

When is managed implementation required?

When exchange runs over HL7 v2, FHIR, file transfer or a product-specific interface requiring message profiles, mappings and validation.

Can we test in Sandbox?

Yes. Sandbox uses synthetic activity with separate credentials, and mapping and workflow validation happen there first.

Can multiple Programs reuse one connection?

Yes, once the connection and mappings are validated. Each Program is still separately approved and activated.

Laboratory environments

Solia Direct + Clinisys / Sunquest

Solia Direct can be deployed around Clinisys and legacy Sunquest environments using the interfaces available in that specific product and version.

Sunquest is now part of Clinisys, and Clinisys presents a broad portfolio spanning healthcare, public health, toxicology and life sciences laboratories — including Clinisys Laboratory Solution and the clinical and anatomic pathology product lines that carry forward Sunquest capabilities. Because that portfolio covers several product lines, versions and deployment models, there is no single "Clinisys interface". Specific integration options vary by the Clinisys product and version in use.

How Solia Direct fits around Clinisys / Sunquest

Clinisys positions its platform as the laboratory's operational system of record. That is the right place for it to sit, and Solia Direct does not compete with it. Solia operates the layer outside the laboratory: Programs, partner credentials, catalog and serviceability, and the normalized order and result envelope partners work against.

Because the portfolio is broad, discovery matters more here than elsewhere. The first implementation question is which product and version the laboratory runs, what its interface layer already does for external counterparties, and whether that path can carry Program-originated orders without disturbing existing traffic.

Programs + partners

Consumer, provider-led and partner-led Programs

Control Plane + Partner API

Grants, catalog, serviceability, orders, results, webhooks

Solia operating / connectivity layer

Validation, normalization, mapping, status lifecycle

Clinisys / Sunquest interface environment

Product- and version-specific interfaces and APIs

Laboratory workflow + analyzers

Accessioning, processing, review, release

Solia Direct operates above the laboratory environment. It is not inserted into laboratory processing.

What remains in Clinisys / Sunquest

Solia Direct is not the laboratory system of record and does not become one. The following stay where they are.

Operational system of record

Specimen collection, laboratory operations and core data remain in the Clinisys environment.

Instrument integration

Bi-directional instrument connectivity stays with the laboratory platform.

Result generation and release

The laboratory authors, verifies and releases the authoritative result.

Site-specific workflow and reporting

Configured workflows, quality processes and statutory reporting remain in the LIS.

What Solia Direct adds around it

Diagnostic Programs

Separately approved Programs that reuse the same underlying laboratory capability.

Partner API + Control Plane

One partner-facing API and one operator surface over the connected environment.

Program access and grants

Scoped credentials and explicit grants that decide which partner can order what.

Reusable catalog and serviceability

A normalized testing catalog with geography, collection and eligibility rules.

Normalized orders and statuses

Order validation, idempotency and a consistent status lifecycle across Programs.

Results delivery and events

Normalized results, corrections and signed webhooks with retries and replay.

Sandbox and Production environments

Separate credentials, synthetic testing and governed Production activation.

Optional Consumer Experience

A consumer-facing ordering and results journey where a Program calls for one.

More detail: Diagnostic Programs and catalog, Laboratory Partner API and laboratory commercialization infrastructure.

Connection paths: self-service and managed

Solia Direct can be deployed around Clinisys / Sunquest using the interfaces available in the laboratory’s environment. There is no native, certified or vendor-approved connector, and no single path fits every deployment.

Self-service

HTTPS/JSON Solia Lab Contract

The laboratory, or the integration layer it operates in front of Clinisys, exposes the HTTPS/JSON Solia Lab Contract.
Where the environment already exposes an orders and results API externally, mapping it to the Solia contract is usually the shortest path.
The contract can be implemented and validated in Sandbox independently of any Solia-side interface work.

Managed implementation

Environment-specific interfaces

HL7 v2 order and result messaging over the interface path the environment already uses.
FHIR where the specific product and version exposes it for external exchange.
SFTP or file-based exchange where that is the current operational pattern.
Other site-specific interfaces, scoped with message profiles, mappings and validation.

What public material supports

Clinisys publicly positions Clinisys Laboratory Solution as the laboratory's operational system of record, spanning specimen collection, laboratory operations, research, genomics and biorepository management.
Clinisys public material describes bi-directional instrument integrations, third-party database and registry integration and a documented orders and results API.
Clinisys states that Sunquest products' capabilities continue as core components of Clinisys Laboratory Solution, under the Clinisys brand.
Specific interface options vary by Clinisys product, version, licensed modules and deployment. Nothing here implies one universal Clinisys interface.

Managed implementation scope depends on the LIS product and version, enabled modules and licences, interface capability, deployment model, message profiles, network and security configuration, site-specific mappings and validation requirements. See HL7, FHIR & SFTP.

What moves, and how it is mapped

Solia → laboratory

Validated order with Program context
Patient and order identifiers
Laboratory test / order code for the ordered panel
Collection and specimen context
Clinical or ask-at-order-entry data where the test requires it

Laboratory → Solia and partners

Order and specimen status transitions
Accession identifiers where the environment exposes them
Released results with units and reference intervals
Corrected or amended result versions
Operational events (rejections, cancellations, exceptions)

Product-specific order codes and the laboratory compendium are mapped to the Solia catalog entries a Program can order.
Result identifiers, units and reference intervals are mapped to normalized result fields.
Order and specimen statuses from the environment are mapped into the Solia status lifecycle.
Corrected and amended results are mapped to result versions with prior versions retained.

Sandbox first, then governed Production activation

Sandbox

Synthetic, isolated test activity with its own credentials
Mapping validation against representative cases
Order, status and result workflow testing end to end
Partner-side integration testing before any Program launch
No Production data and no Production secrets
Remains available after go-live for regression testing

Production

The real Clinisys / Sunquest interface, not a simulation
Validated mappings reviewed against laboratory source data
Real credentials issued separately from Sandbox
A Production Program with explicit scope
Evidence-based readiness review
Governed activation rather than a self-serve switch

Completing Sandbox testing does not by itself establish Production readiness. See Sandbox and Production.

What becomes reusable after the connection is validated

Once the Clinisys / Sunquest connection is configured and validated, the underlying laboratory capability can be reused across multiple separately approved Programs and partners without rebuilding the LIS integration for each one. Reuse is not automatic approval: every Program and every partner grant is still reviewed and activated on its own terms.

Validated interface

The order and result path does not have to be rebuilt per Program.

Mapping set

Codes, units, intervals and statuses are reused across Programs.

Catalog and serviceability

Test availability and geography rules are defined once.

Partner surface

New partners consume the same Partner API and event contract.

Frequently asked questions

Sources and disclosure

Product and interface references are based on publicly available vendor information as of September 2026. Interface availability and implementation requirements vary by product, version and laboratory environment. Solia Direct is not affiliated with Clinisys.

Clinisys spans multiple product lines and versions, including environments that originated as Sunquest, Orchard, HORIZON and ApolloLIMS. Interface availability is product-, version- and deployment-specific.

Other laboratory environments

Solia Direct + Orchard

A widely installed LIS family, now part of Clinisys. Connection depends on the interfaces enabled in the specific Orchard environment.

Solia Direct + Epic Beaker

Epic publicly documents HL7 v2 and FHIR laboratory interfaces; activation and configuration are decided in each Epic customer environment.

Solia Direct + LigoLab

An end-to-end LIS with a documented interface engine. Connection depends on which of those interfaces the laboratory has configured.

Don’t see your LIS? Solia is not limited to the systems listed here. Connection feasibility depends on the interfaces available in your laboratory environment — LIS/LIMS integration overview.

Technical documentation

Continue with implementation detail.

Laboratory connection Order interface Result interface Mappings Validation Production readiness

Review what your Clinisys / Sunquest environment can expose today.

We scope the available interface, the mappings required and the validation path before any Production commitment is made.