Clinical ordering, review & telehealth
Explore licensed clinical services for Programs that require ordering, review or telehealth. Clinical decisions and care remain with the authorized clinical service.
Integrations
Solia Direct sits around the LIS/LIMS and laboratory systems already in place. One validated laboratory connection can support multiple approved Programs and partners without making Solia the system of record.
Plan the clinical, collection and logistics services each Program requires.
Service Partner planning and Program-fit review are available in the laboratory Control Plane. Laboratories can review prospective or existing service relationships against each approved Diagnostic Program without implying an operational connection.
Explore licensed clinical services for Programs that require ordering, review or telehealth. Clinical decisions and care remain with the authorized clinical service.
Evaluate collection at a patient’s location, subject to geography, staffing, specimen requirements and agreed service scope.
Define laboratory draw-site options and appointment methods separately from mobile collection, with location-specific access and scheduling requirements.
Assess compatible devices and specimen methods against laboratory acceptance criteria, Program design and applicable clinical requirements.
Plan kitting, outbound and return logistics, specimen custody and handoff. Collection methods and specimen transport require separate qualification.
Explore
Review prospective services against your laboratory’s needs.
Establish
Review an intended relationship or record an existing-account path. No request is sent until separate relationship authority is approved.
Configure
Define service scope and eligibility separately for each approved Diagnostic Program.
Validate
Qualify clinical, geography, specimen, technical and contractual requirements before any operational use.
This capability concerns laboratory-side relationship planning and per-Program service fit—not LIS/LIMS connectivity, health-company Partner API access, clinical execution, bilateral reference/send-out testing or Solia On Demand distribution. Solia does not perform clinical services, specimen collection or laboratory testing.
Planned capability · not available for operational use
Planning and Program-fit review are available in the laboratory Control Plane. Partner requests, partner contacts, operational connections and Production execution remain disabled until separate relationship authority, commercial scope, configuration and validation are approved. No nationwide coverage, automatic eligibility or live service availability is implied.
Technical documentation
Solia Direct sits around the LIS/LIMS and laboratory systems already in place. One validated laboratory connection can support multiple approved Programs and partners without making Solia the system of record.
Into the laboratory
Back to Programs
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
Validated laboratory connection
Selected integration
Laboratory systems
LIS / LIMS · APIs · files · validated adapters
Object mapping
Mapping is defined per connected environment. Not every object uses the same method — some arrive through an API, others through HL7, FHIR or an interface adapter.
| Solia object | Typical external source |
|---|---|
| Order | Consumer / ordering workflow |
| Clinical order | Provider / order service |
| Collection | Scheduling / collection network |
| Specimen + accession reference | LIS / laboratory workflow |
| Result set | LIS / laboratory API |
| Biomarker observations | Result interface |
| Corrected / amended result | Laboratory |
| Release state | Laboratory release authority + configured Solia delivery state |
How Solia Direct fits
The self-service path is the supported HTTPS/JSON Solia Lab Contract, requiring a compatible endpoint, credentials, explicit mappings and validation. HL7 v2, FHIR, SFTP/file and laboratory-specific interfaces are managed paths that require environment-specific interface feasibility, specification, mapping and real technical validation. Existing laboratory systems remain authoritative.
Reusable connection
Catalog, serviceability, orders and results can be reused across separately approved Programs.
Explicit mappings
Codes, identifiers, statuses, units, reference intervals and result versions are validated for the connected environment.
Operational control
Acknowledgements, retries, exceptions and reconciliation are observable rather than hidden.
Clear boundaries
Accessioning, analyzers, quality control, specimen processing and official results stay in laboratory systems.
Implementation
A buyer should evaluate the actual interface available in each environment, mapping ownership, failure handling, validation evidence and the operational team responsible for exceptions. Solia does not claim plug-and-play compatibility with every laboratory system.
Data & control
Minimum necessary access
Only exchange the information required for the supported workflow.
Explicit authorization
Credentials, services and staff access should be scoped to defined functions.
Provenance + auditability
Orders, result versions and material integration events should remain traceable.
Appropriate agreements
Where Solia Direct acts as a business associate and handles PHI on behalf of a covered entity, appropriate contractual and technical safeguards must be established before production use.
How we describe integrations
Solia Direct does not display vendor logos for systems it has not connected to. Scope is assessed before implementation; built, validated and live Production status must be evidenced separately for each environment.
Supported standard
The HTTPS/JSON Lab Contract is the supported direct path. Managed HL7, FHIR and file paths require interface feasibility, specification, implementation and validation.
Existing reusable adapter
A connector Solia has already implemented and can reuse in a new deployment, subject to environment-specific configuration and mapping.
Custom / environment-specific integration
Scoped implementation work against the laboratory's own systems, interfaces and identifiers.
Configurable is not built; built is not validated; validated is not vendor-certified or live in Production. Screenshots and referral relationships are not proof of live connectivity.
How integrations are delivered
Configurable integration setup
Configured by the laboratory in the Control Plane — catalog and pricing, the laboratory’s external payment-provider settings, notifications, eligible collection options, branding and consumer experience settings. Configuration alone does not establish a live integration.
Solia-managed implementation
LIS/LIMS, HL7 and FHIR interfaces, proprietary laboratory APIs, result mapping, clinical and provider infrastructure, and complex collection routing. These are scoped, specified and validated with your teams — not one-click connections.
We’ll map the systems, workflows and data exchanges required for your laboratory deployment.
Weighing this connectivity model against an internal build, a diagnostic infrastructure API or your existing interface engine?
Compare Solia Direct