Integrations
Connect consumer payments without rebuilding laboratory billing infrastructure.
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 consumer checkout and payment workflows while keeping payment processing within appropriately configured payment infrastructure.
Consumer transactions
- Panel and test payment
- Collection fees
- Discounts and promotions
- Membership pricing where enabled
Post-transaction
- Refunds
- Payment status
- Transaction references
Flow
Partner / Program
Partner API · webhooks · consumer experience
Solia Core
Programs · orchestration · state · results
Payment provider
Selected integration
Laboratory systems
LIS / LIMS · APIs · files · validated adapters
How Solia Direct fits
Keep cardholder data out of Solia Direct wherever the payment architecture allows.
Provider-hosted and tokenized payment flows are preferred over unnecessarily handling raw payment credentials inside the platform.
Processing stays with the provider
Solia Direct orchestrates checkout state and references; the configured provider handles the transaction.
Minimal payment metadata
Diagnostic or health information is not placed into payment metadata unnecessarily.
Implementation
What to consider before production.
Merchant-of-record and payment-processor roles depend on the deployment and the payment architecture selected; Solia Direct is not automatically the merchant of record or the processor. PCI DSS responsibilities depend on the final payment architecture and providers used, and apply only where relevant to the deployment. Solia Direct makes no claim of independent PCI certification.
- 01Selected payment architecture and provider
- 02Tokenization and hosted payment flows
- 03Scope of data stored versus referenced
- 04Refund, dispute and reconciliation workflows
- 05Currency, tax and fee handling where applicable
- 06Separation of payment records from clinical records
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