Can Solia Direct work with Orchard?

Solia Direct can be deployed around an Orchard environment using the interfaces available in that laboratory. There is no native or certified Orchard connector; feasibility is confirmed against the specific environment during implementation planning.

Does Solia replace Orchard?

No. Orchard remains the laboratory system of record for accessioning, processing and authoritative results. Solia operates the Program, partner and connectivity layer around it.

Do we need to change our LIS or upgrade it?

Not as a rule. The question is which interface the environment can expose today. Where the available interface is limited, the scope of the managed implementation changes rather than the LIS itself.

What is the self-service path?

The laboratory or its integration layer exposes the HTTPS/JSON Solia Lab Contract. That path is documented and can be implemented and tested without Solia-side interface development.

When is managed implementation required?

When orders and results move over HL7 v2, SFTP/file or another site-specific interface. Those paths require message profiles, mappings and validation scoped to the environment.

How are test codes and results mapped?

Order codes, result identifiers, units, reference intervals and statuses are mapped explicitly and reviewed against laboratory source data before Production.

Can we test in Sandbox first?

Yes. Sandbox uses synthetic activity with its own credentials, and mapping and workflow validation happen there before any Production discussion.

Can multiple Programs reuse one Orchard connection?

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

Laboratory environments

Solia Direct + Orchard LIS

Solia Direct can be deployed around an Orchard environment using the interfaces available in that laboratory, without replacing the LIS.

Clinisys announced the acquisition of Orchard Software in July 2025, and Orchard's laboratory information system — including the Harvest product line, now presented under the Clinisys brand — remains a widely installed product family in physician office, reference and specialty laboratories. Because those installations span versions, deployment models and interface configurations, the connection path is determined by the specific environment rather than by the product name.

How Solia Direct fits around Orchard

Solia Direct does not sit inside the Orchard environment and does not participate in laboratory processing. It sits around it: partners and Programs talk to the Partner API, Solia normalizes and validates what they send, and the laboratory's own interface layer exchanges orders and results with the LIS the way that environment already supports.

That boundary matters operationally. The laboratory keeps the workflow, the validation rules and the authoritative result. Solia holds the Program model, the partner credentials, the catalog and serviceability logic, and the normalized order and result envelope that every Program sees.

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

Orchard LIS / interface environment

Host, reference lab and instrument interfaces as configured

Laboratory workflow + analyzers

Accessioning, processing, review, release

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

What remains in Orchard

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

Accessioning and specimen workflow

Receipt, labelling, routing and specimen handling stay in the LIS.

Instrument connectivity

Analyzer interfaces and instrument data flow remain an Orchard-side concern.

Result authoring and release

The laboratory generates, reviews and releases the authoritative clinical result.

Site-specific rules

Reflex logic, autoverification and local workflow configuration 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 Orchard 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 already operates in front of Orchard, exposes the HTTPS/JSON Solia Lab Contract.
Order intake, status callbacks and result posting follow the documented Solia contract rather than a vendor-specific message profile.
The laboratory controls its own release cycle for that endpoint and can test end to end in Sandbox before anything is scheduled for Production.

Managed implementation

Environment-specific interfaces

HL7 v2 order and result messaging through the interface path the environment already uses.
SFTP or file-based exchange where that is how the laboratory currently moves orders and results.
FHIR or another site-specific interface where the environment exposes one.
Message profile, mapping and validation work scoped with the laboratory and its interface team.

What public material supports

Orchard publicly documents HL7 v2 result specifications for Harvest, including unsolicited observation (ORU) result messages with standard MSH, PID, ORC, OBR and OBX segments.
Public Orchard material describes host (EMR/HIS), reference laboratory, billing and instrument interfaces as routine, quoted and implemented per site.
Clinisys publicly describes Harvest as supporting robust interfaces built by its integration team across analyzers, EHRs and billing systems.
What any individual laboratory can expose still depends on its product version, licensed interfaces, deployment model and network configuration.

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)

Orchard order codes and test definitions are mapped to the Solia catalog entries a Program can order.
Result OBX identifiers, units and reference intervals are mapped to the normalized result fields partners consume.
Order and specimen statuses are mapped into the Solia status lifecycle so every Program sees the same progression.
Corrected and amended results are mapped to result versions rather than overwriting prior values.

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 Orchard 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 Orchard 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 or Orchard Software.

Orchard Software was acquired by Clinisys in 2025 and Orchard products are now presented under the Clinisys brand. Interface availability differs by Orchard product, version and installation.

Other laboratory environments

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.

Solia Direct + Clinisys / Sunquest

A broad portfolio: Sunquest is now part of Clinisys. Integration options vary by the Clinisys product and version in use.

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 Orchard environment can expose today.

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