Skip to main content
Solia Direct

Integrations

Provider ordering where required.

Provider ordering, clinical review and telehealth require an actual authorized clinical service where applicable. Laboratories can discuss prospective or existing service relationships; operational routing requires separate technical integration and validation for the approved Program. Not every laboratory, test or jurisdiction requires provider authorization.

Technical documentation

Continue with implementation detail.

What the connection carries.

Provider ordering, clinical review and telehealth require an actual authorized clinical service where applicable. Laboratories can discuss prospective or existing service relationships; operational routing requires separate technical integration and validation for the approved Program. Not every laboratory, test or jurisdiction requires provider authorization.

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. An actual authorized clinical service and its coverage must be confirmed for each deployment. An introduction, referral or nominated relationship is not evidence of a live API integration, signed agreement or automatic Program eligibility. Service Partner planning and Program-fit review are available in the laboratory Control Plane. Partner requests, operational connections and Production execution remain disabled pending separate relationship authority, configuration and validation. Clinical and legal responsibility for provider review remains with the clinical 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. 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

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, 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.

  1. 01RequirementsSystems, interfaces, data and workflows in scope.
  2. 02ConfigurationStandardized settings applied in the Control Plane.
  3. 03Credentials & specificationAccess, endpoints and message specifications agreed.
  4. 04ValidationMapping and result fidelity reviewed against laboratory sources.
  5. 05TestingEnd-to-end runs in a non-production environment.
  6. 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.

Pricing·How deployment works·Partner API documentation

Weighing this connectivity model against an internal build, a diagnostic infrastructure API or your existing interface engine?

Compare Solia Direct