Platform comparison
Solia Direct vs. Junction
Two diagnostic APIs designed around opposite sides of the same relationship.
Solia Direct is an operating and connectivity layer for diagnostic laboratories. Connect the laboratory once and reuse that infrastructure across multiple Programs and partners through one Control Plane and Partner API—without replacing the LIS/LIMS.
Junction publicly positions diagnostic infrastructure that healthcare and digital-health companies use to order testing, coordinate collection and retrieve results. The approaches overlap; the distinction is primarily orientation.
What each is designed for.
Junction
Junction's public materials present diagnostic and device infrastructure for healthcare and digital-health companies: a lab testing API covering ordering, collection modalities and results, device connectivity, and enterprise data capabilities such as analytics and warehouse pipelines. Junction publicly describes working with partner laboratories and a physician network in the United States, with documented Sandbox and Production environments.
Solia Direct
Solia Direct is built for the laboratory that already performs testing. The laboratory connects its own infrastructure once, then defines Programs, grants scoped partner access, and exposes catalog, serviceability, ordering, results and webhooks through one Control Plane and Partner API — above the existing LIS/LIMS rather than instead of it.
Where the approaches genuinely overlap.
A comparison is only useful if it starts with the honest overlap. Both products solve real parts of the same workflow.
- Both expose diagnostic capabilities through an HTTPS/JSON API rather than a manual process.
- Both model test ordering, order status and result retrieval as API resources.
- Both use webhooks or event updates to notify a consuming system as an order progresses.
- Both provide Sandbox-style environments with separate credentials so integration work can happen before live testing.
- Both support digital-health and consumer-facing experiences built on top of the API.
- Both address collection logistics in some form, including patient service centers and at-home collection models.
At a glance
Based on each product's publicly described scope as of September 2026.
Architectural orientation
Solia Direct
Starts from the laboratory. The laboratory's own testing capability becomes reusable infrastructure.
Junction
Publicly presents infrastructure for health companies that need access to diagnostics, working with partner laboratories and a physician network.
Primary buyer
Solia Direct
Diagnostic laboratories and laboratory networks commercializing their own capacity.
Junction
Public materials emphasize healthcare, digital-health and consumer-health companies building on health data and diagnostics.
API model
Solia Direct
Partner API scoped by Program grant, with the laboratory controlling which partner reaches which capability.
Junction
A unified API surface spanning users, devices and lab testing, with team-level keys per environment and region.
Who controls the laboratory relationship
Solia Direct
The laboratory owns its catalog, partners, commercial terms and the connection to its own systems.
Junction
Public materials describe a network model in which the platform coordinates laboratory access on behalf of the building company.
Catalog
Solia Direct
The laboratory's own test catalog, mapped to its LIS/LIMS codes and reused across Programs.
Junction
Test definitions and custom panels are configured against the available network.
Serviceability
Solia Direct
Configured by the laboratory — geography, collection model and clinical requirements per Program.
Junction
Determined by network coverage and collection modality; public pricing material notes certain states are handled differently.
Orders and results
Solia Direct
Normalized order lifecycle and result delivery mapped from the laboratory's own systems.
Junction
End-to-end order and result lifecycle across the supported modalities, with webhook updates.
Sandbox and developer workflow
Solia Direct
Sandbox uses synthetic data; Production is separately gated and readiness-driven.
Junction
Documented Sandbox environments with simulated results and the ability to advance an order through its lifecycle.
Program reuse
Solia Direct
One laboratory connection reused across multiple Programs and partners without re-integrating.
Junction
Reuse is at the level of the building company's own product across the network it consumes.
Relationship to the LIS/LIMS
Solia Direct
Connects to the laboratory's LIS/LIMS and does not replace it.
Junction
Public materials do not position the product as a laboratory information system; laboratory operations sit with the partner laboratories.
Where Solia Direct sits in the laboratory's architecture.
The laboratory connects once. Programs and partners consume that connection through the Partner API without each one requiring a new integration into the LIS/LIMS.
Programs and partners
Lab-owned · Partner-led · Optional consumer experience
Control Plane + Partner API
Grants · Catalog · Serviceability · Orders · Results · Webhooks
Solia operating and connectivity layer
Normalization · Mappings · Environments
The laboratory's own LIS/LIMS and infrastructure
Accessioning · Analyzers · Validation
The laboratory remains the source of truth for testing and official clinical results.
What neither approach replaces.
- Solia Direct does not perform laboratory testing and does not replace the laboratory's system of record.
- Solia Direct does not supply a laboratory network — it exposes the capacity a laboratory already operates.
- Junction, per its public materials, is not positioned as a laboratory information system for running a laboratory's internal operations.
- Neither approach removes the need for clinical, regulatory and collection responsibilities to sit with the accountable parties.
When Junction may be the better fit.
Based on publicly available information, Junction may be more attractive when an organization:
- Is a health, digital-health or consumer-health company rather than a laboratory
- Needs access to diagnostic testing without operating a laboratory
- Wants collection modalities and physician coverage coordinated through one vendor
- Also needs wearable and device data alongside diagnostics
- Wants to start on a published self-serve plan and expand into enterprise capabilities
When Solia Direct may be the stronger fit.
Solia Direct is designed for organizations that already perform testing and want that capability to become reusable infrastructure. It may fit when a laboratory wants to:
- Connect its own laboratory infrastructure once and reuse it across Programs
- Grant scoped Partner API access per Program rather than per integration
- Keep ownership of its catalog, partners, pricing and commercial relationships
- Expose serviceability, ordering, status, results and webhooks from its own systems
- Evaluate against synthetic data in Sandbox before gated Production activation
- Keep the existing LIS/LIMS in place as the system of record
Frequently asked questions
Sources and disclosure
Statements about Junction reflect publicly available information reviewed in September 2026, including junction.com, its published pricing page and its public developer documentation. Product scope and pricing may change.
Solia Direct is not affiliated with, endorsed by or sponsored by Junction. All product and company names are the property of their respective owners. This page is intended to help buyers understand architectural differences, not to rank vendors.
Related comparisons
Solia Direct vs Luminate Health
Luminate Health publicly emphasizes patient engagement, provider engagement, direct-to-consumer testing and population-health applications built around laboratory data. Solia Direct is a reusable operating and connectivity layer that exposes laboratory capabilities across multiple Programs and partners.
Read comparisonBuild vs Buy a Laboratory API & Integration Layer
Building means owning partner authentication, catalog normalization, serviceability, order and result lifecycles, webhooks, environments, mappings and ongoing change management. Deploying Solia Direct moves the reusable parts of that surface to a platform.
Read comparisonSolia Direct vs Traditional LIS Middleware
Traditional LIS/LIMS and middleware operate and connect the laboratory's internal systems — accessioning, analyzers, validation, routing and standards interfaces. Solia Direct operates the reusable commercialization and partner-connectivity layer around those systems.
Read comparisonSee every comparison on the Compare Solia Direct hub.
Discuss your laboratory's connectivity model.
Bring your systems, partner requirements and Program plans. We will walk through how the Partner API and Control Plane would map to them.