Integrations
Collection and specimen logistics are two different problems.
Collection is how a specimen is obtained: a laboratory draw site, mobile visit or qualified self-collection method. Kitting and logistics cover supplies, outbound and return transport, custody and laboratory handoff. Prospective or existing service relationships require separate Program qualification and operational integration; listing a method does not establish availability.
Technical documentation
Continue with implementation detail.
What the connection carries.
Collection is how a specimen is obtained: a laboratory draw site, mobile visit or qualified self-collection method. Kitting and logistics cover supplies, outbound and return transport, custody and laboratory handoff. Prospective or existing service relationships require separate Program qualification and operational integration; listing a method does not establish availability.
Collection
- Laboratory draw sites and appointment methods
- Laboratory-owned or third-party mobile specimen collection, subject to qualification
- Compatible at-home devices and self-collection specimen methods, subject to laboratory validation
- Program-specific coverage, availability and collection fees
- Preparation requirements
Specimen logistics
- Kitting and outbound / return 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.
Mobile collection, draw sites, compatible at-home devices, self-collection methods and logistics depend on the laboratory, geography, specimen, approved Program, technical validation and contractual scope; no blanket live coverage is implied. Applicable certifications and licensure depend on the functions each party performs. 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. An introduction or nominated relationship does not establish a signed agreement, operational integration, automatic eligibility or Production availability.
- 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. 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.
- 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