Laboratory environments
Connect Solia Direct with Epic Beaker
Solia Direct can be deployed around an Epic Beaker environment using the interfaces that Epic customer environment exposes, while Beaker remains the laboratory system.
Epic publicly documents laboratory order and result interfaces for Beaker, including HL7 v2 results and order messaging and a broad FHIR resource surface. Epic also states plainly that interfaces are configured per customer: which interfaces exist, in which format, and with which authorization model is a decision made in the health system's own environment, not a property of Beaker as a product.
How Solia Direct fits around Epic Beaker
In an Epic environment the health system already owns a mature interface practice. Solia Direct does not attempt to displace it. Orders that originate from a Program are validated and normalized by Solia and then handed to whichever interface the Epic customer environment supports; results return along the same path and are normalized before partners see them.
Beaker stays the laboratory system. Solia holds the outward-facing layer: which partner may order which test, where that test is serviceable, what the normalized order and result look like, and how events are delivered and replayed.
Programs + partners
Partner-led, provider-led and consumer Programs
Control Plane + Partner API
Grants, catalog, serviceability, orders, results, webhooks
Solia operating / connectivity layer
Validation, normalization, mapping, status lifecycle
Epic interface environment (Beaker)
HL7 v2 and/or FHIR interfaces as activated by the customer
Laboratory workflow + analyzers
Accessioning, processing, review, release
Solia Direct operates above the laboratory environment. It is not inserted into laboratory processing.
What remains in Epic Beaker
Solia Direct is not the laboratory system of record and does not become one. The following stay where they are.
Beaker laboratory workflow
Accessioning, specimen handling and in-laboratory processing remain in Epic.
Clinical record and ordering governance
The Epic record, the clinical context and the health system's ordering rules stay in Epic.
Result verification and release
The laboratory authors, verifies and releases the authoritative result.
Interface activation and security posture
Which interfaces exist and how access is authorized is the Epic customer's decision.
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 Epic Beaker 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 health system's own integration layer in front of Epic exposes the HTTPS/JSON Solia Lab Contract.
- This is common where an interface engine or internal API platform already fronts Epic for external partners.
- Solia consumes the documented contract; no Epic-specific adapter is built or implied.
Managed implementation
Environment-specific interfaces
- HL7 v2 laboratory order and result messaging over the interface path the environment already runs.
- FHIR resources such as ServiceRequest, Observation and DiagnosticReport where the environment exposes and authorizes them.
- Authorization and client setup handled according to the health system's own process.
- Message profile, mapping and validation scoped with the Epic interface team.
What public material supports
- Epic publicly documents outgoing results and orders interfaces for Beaker, including HL7 v2.5.1 LRI-format result messages and order status messages sent to external systems.
- Epic publicly documents HL7 v2 clinical interfaces and a FHIR resource surface spanning DSTU2, STU3 and R4 read, search and write resources, with OAuth2 authorization for API access.
- Epic publicly states that interfaces may be real-time or batch, one-way or bidirectional, and point-to-point or mediated by an interface engine.
- Not every Epic Beaker environment exposes every documented interface. Availability, message profile and authorization depend on the customer's activation and 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)
- Epic order codes and the laboratory's test compendium are mapped to the Solia catalog entries a Program can order.
- Result identifiers, units and reference intervals are mapped to normalized result fields; LOINC is used where the environment supplies it.
- Order status messages are mapped into the Solia status lifecycle so partner-facing progression is consistent.
- Corrections and amendments are mapped to result versions with the prior version 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 Epic Beaker 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 Epic Beaker 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 Epic Systems Corporation.
Epic interface availability, message profiles and authorization requirements are determined by each Epic customer environment. Documented capability does not mean a given deployment has it enabled.
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.
Read moreSolia Direct + LigoLab
An end-to-end LIS with a documented interface engine. Connection depends on which of those interfaces the laboratory has configured.
Read moreSolia Direct + Clinisys / Sunquest
A broad portfolio: Sunquest is now part of Clinisys. Integration options vary by the Clinisys product and version in use.
Read moreDon’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.
Related: Laboratory connectivity · Laboratory Partner API · HL7, FHIR & SFTP · Diagnostic Programs · Sandbox & Production · Architecture
Review what your Epic Beaker environment can expose today.
We scope the available interface, the mappings required and the validation path before any Production commitment is made.