Integrations
Collection and specimen logistics are two different problems.
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.
Collection is how a specimen is obtained. Logistics is how it reaches the laboratory intact and traceable. Solia Direct coordinates both as configured categories around the laboratory's own operating model and the collection and logistics infrastructure it uses.
Collection
- Laboratory draw sites
- Laboratory-owned mobile collection
- Configured third-party mobile collection
- Other supported collection methods where appropriate
- Coverage, availability and collection fees
- Preparation requirements
Specimen logistics
- Chain of custody
- Packaging
- Specimen stability and temperature requirements as defined by the laboratory
- Pickup / courier handoff
- Shipment and transport visibility where supported
- Delivery to the laboratory
- Accessioning handoff
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
Collection & logistics infrastructure
Selected integration
Laboratory systems
LIS / LIMS · APIs · files · validated adapters
How Solia Direct fits
Solia Direct coordinates the workflow — it does not own collection or logistics infrastructure.
Where another organization performs collection, courier, transport, laboratory or testing functions, Solia Direct does not represent itself as that party.
Responsibilities stay where they belong
Collection responsibilities remain with the laboratory or the configured collection provider; transport responsibilities remain with the configured logistics infrastructure; testing remains with the laboratory.
Traceable handoff
Specimen identity, custody and handoff remain traceable from collection through delivery and accessioning.
At-home and self-collection are conditional
Self-collection paths are supported only where methodology, program design, laboratory validation and applicable requirements support them.
Implementation
What to consider before production.
Applicable certifications and licensure depend on the functions each party performs in the deployment. Solia Direct does not display collection or logistics providers it has not established.
- 01Configured collection methods per program and geography
- 02Participating provider responsibilities and agreements
- 03Specimen identity, labeling and chain of custody
- 04Packaging, stability and temperature requirements defined by the laboratory
- 05Courier pickup, transport visibility and delivery confirmation where supported
- 06Accessioning handoff and reconciliation
- 07Exception, recollection and rejection workflows
- 08State and local requirements, which may vary
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