Integrations
HL7, FHIR and SFTP workflows for the environment you operate.
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 supports managed HL7 v2, FHIR and SFTP/file exchange when those paths fit the connected laboratory environment. The HTTPS/JSON Solia Lab Contract remains the self-service connection path. Format and security are separate concerns, and every managed interface still requires environment-specific specification, mapping and validation.
HL7 v2 patterns
- Orders
- Results
- Status messaging
FHIR and file patterns
- Patient and identity context
- Orders / service requests where appropriate
- Diagnostic reports
- Observations
- Provenance
- Supported API workflows
- SFTP batch and file exchange
- Delimited or structured files where specified
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
Managed standards or file exchange
Selected integration
Laboratory systems
LIS / LIMS · APIs · files · validated adapters
How Solia Direct fits
Version and profile follow the connected environment.
No single HL7 version, FHIR release, profile or file layout is universally required. Solia Direct implements these as managed paths against the version, profile, transport and mapping agreed for the connected environment.
Format is not compliance
Authentication, authorization, transport security and audit controls are configured independently of the exchange standard.
Provenance is preserved
Result versions, corrections and originating system remain attributable to the laboratory.
Implementation
What to consider before production.
Where applicable to the parties and use case, implementation accounts for HIPAA requirements and relevant federal interoperability and information-access requirements. Solia Direct does not claim ONC certification.
- 01Authenticated clients
- 02Authorized and scoped access
- 03Encrypted transport
- 04Audit events
- 05Provenance
- 06Resource validation
- 07Version and profile compatibility
- 08File layout, delivery cadence and reconciliation
- 09Consent and access requirements where applicable
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