Integrations
Provider ordering where required.
Connect the selected interface to Solia’s shared operating layer while the laboratory’s existing systems remain authoritative.
Technical documentation
Continue with implementation detail.
What the connection carries.
Solia Direct can orchestrate provider-order workflows between the consumer experience, supported clinical-provider services, and the laboratory testing workflow where licensed-provider authorization is required. Not every laboratory, test, or jurisdiction requires this.
Solia Direct orchestrates
- Consumer intake
- Workflow routing
- Order state
- Provider-service integration
- Return of authorized order / requisition state
- Continuation into collection and testing workflow
The provider service performs
- Licensed clinician review
- Clinical review of the request
- Authorization and order issuance
- Jurisdictional provider coverage
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
Provider-order service
Selected integration
Laboratory systems
LIS / LIMS · APIs · files · validated adapters
How Solia Direct fits
Solia Direct is not the provider network.
Where licensed-provider authorization is required, the applicable clinical review and order issuance are performed by the configured provider service. The laboratory continues to control testing, laboratory operations, supported test availability, and downstream specimen and result processing.
Routing can be automated; review is not
Operational routing can be highly automated. Licensed-provider review and authorization itself is not represented as automatic where provider review is required. Provider review may occur asynchronously depending on the configured provider service and workflow.
Provider-order cost is separate
Provider-order / telehealth usage is a separate third-party cost where used. Exact pricing depends on the selected provider service, geography, testing model, and volume.
Existing provider infrastructure
Laboratories may be able to use existing qualified provider-order infrastructure or supported third-party services depending on deployment requirements and integration feasibility.
Laboratory scope is unchanged
Testing, laboratory operations and official results remain with the laboratory and its systems of record.
Implementation
What to consider before production.
Solia Direct does not act as a clinical provider and does not publish named provider partners it has not established. Supported provider-order partners are identified during implementation planning. Clinical and legal responsibility for provider review remains with the provider service and the parties to the applicable agreements.
- 01Whether provider authorization is required for the catalog and jurisdictions in scope
- 02Selected provider service and its coverage
- 03Intake questions and clinical information required by the provider service
- 04Order, authorization and decline states returned to the workflow
- 05Asynchronous review handling and consumer communication
- 06Requisition and identifier mapping into the laboratory workflow
- 07Auditability of order authorization events
- 08Third-party provider-service cost and volume assumptions
Data & control
Integration starts with clear system boundaries.
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
Three integration states — stated precisely, per connected environment.
Solia Direct does not display vendor logos for systems it has not connected to. Each integration is classified for the connected environment before implementation begins.
Supported standard
A protocol or interface the platform supports — HL7, FHIR, REST APIs, webhooks and file-based exchange.
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.
Third-party relationships are identified during Production connectivity planning. They are not published as an integration maturity state.
How integrations are delivered
Standardized configuration where possible. Managed implementation where healthcare infrastructure requires it.
Configurable integration setup
Configured by the laboratory in the Control Plane — catalog and pricing, payments, notifications, collection options, branding and consumer experience settings.
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.
- 01RequirementsSystems, interfaces, data and workflows in scope.
- 02ConfigurationStandardized settings applied in the Control Plane.
- 03Credentials & specificationAccess, endpoints and message specifications agreed.
- 04ValidationMapping and result fidelity reviewed against laboratory sources.
- 05TestingEnd-to-end runs in a non-production environment.
- 06Production activationControlled enablement once sign-off is complete.
Connect Solia Direct to the infrastructure you already run.
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