Understanding In-Network vs. Out-of-Network Testing

Veriport’s Network feature allows Requesters (TPAs) and Providers (CSPs) to coordinate drug and alcohol testing with clear distinctions between In-Network and Out-of-Network testing.

The classification directly affects logistics, cost, lab/MRO usage, and how results are routed.

In-Network Testing

In-network tests are conducted using the Requester’s resources. This includes their own laboratory account, Medical Review Officer (MRO), and testing supplies.

Lab and MRO: Tests are processed through the Requester's designated lab and MRO accounts.
Supplies: The Requester provides the chain-of-custody forms and collection kits.
Pricing: Based on pre-agreed rates. Providers are reimbursed at the in-network rate.
Result Routing: Results are routed directly to the Requester after MRO review.
DOT Compliance: In-network tests support DOT-regulated testing using the Requester’s compliance chain.

Out-of-Network Testing

Out-of-network tests are performed using the Provider’s resources. These are typically used when the Requester cannot supply lab, MRO, or kits, or needs to rely on a CSP’s full-service capability.

Lab and MRO: The Provider uses their own lab and MRO services.
Supplies: The Provider supplies their own testing materials and forms.
Pricing: Additional fees apply. Out-of-network pricing is set by the Provider and may vary.
Result Routing: Results are sent to Veriport and routed to the Requester after MRO review.
DOT Compliance: Providers must ensure DOT-compliant collections if the test is regulated, but MRO/lab ownership determines chain of custody.

Side-by-Side Comparison

Attribute	In-Network Test	Out-of-Network Test
Lab Used	Requester’s lab account	Provider’s lab account
MRO Used	Requester’s MRO	Provider’s MRO
Test Supplies	Provided by Requester	Provided by Provider
Result Delivery	Direct to Requester via Veriport	Via Veriport after Provider's MRO review
Pricing	Fixed, pre-negotiated	Set by Provider; typically higher
DOT Compliance	Requester is responsible	Provider must comply independently

Tip: Requesters should default to in-network tests whenever possible to maintain cost control and compliance consistency. Providers should keep their profile updated to clarify which services they support in- and out-of-network.