Sohar Health joins Zocdoc to help more patients access care
Read the press release →
/
Platform
/
Network Status

Network Status

Know in-network or out — before the claim is ever filed

Real-time in-network / out-of-network determination on every eligibility request — plan- and payer-specific, including carve-out nuances

Live at intake
Sohar result

Network Status

In network

Plan

PPO

Carve-out

Routed

Response

200ms

8x

ROI within twelve months

Built alongside teams improving access to care
96%
verification accuracy
15M+
eligibility requests a year
95%+
benefits accuracy
8x
ROI within twelve months
Where it fits

Runs on Verification. No second lookup

Network Status runs directly off Verification’s data the moment coverage is confirmed, with no separate lookup. Developers get an API-first integration. RCM and operations teams get a no-code interface to manage the rules themselves

The business problem

Out-of-network claims get denied twice as often

37%

of out-of-network claims are denied, roughly double the 19% rate for in-network claims

In network
19%
Out of network
37%
After the denial

Network status is usually confirmed the hard way: after the claim comes back denied

Claim filed
Claim denied
Network status confirmed
Every request

Manual network lookups cost staff time on every single request

Source: KFF analysis of 2023 ACA marketplace data (CMS), January 2025

The outcome

In network or out, the moment coverage is confirmed

Front desk team member checking a patient in
Answered before the visit
Before

Network status unconfirmed until the claim is filed — and denied

With Sohar
After

In-network or out-of-network status returned the moment coverage is confirmed, automatically, on every request

Core capabilities

Network rules your team controls

01

Real-time determination

In-network/out-of-network status on every eligibility request, automatically

Payer
Aetna
Plan
PPO
Status
In-Network
Response Time
200ms
02

No-code rules engine

RCM teams update plan-, TPA-, and MCO-specific rules themselves — no engineering ticket required

Carelon BH rule
Updated by RCM
Live
Magellan rule
No engineering ticket
Draft
03

Built-in carve-out handling

Native behavioral health TPA and MCO logic (e.g., Carelon BH, Magellan Health)

Health plan
Behavioral health carve-out
TPA rule applied
04

Runs off Verification data

No separate lookup, no manual double-check

Eligibility Status
Payer
Plan Details
Group Details
Customer proof

How Rula automated network requests

Customer result

1,000hrs

Reduction in manual operations work after Rula integrated Discovery, Verification, and Network Status into its intake flow

Security

Built for sensitive data

Security your IT team will ask about, answered before they ask

AICPA SOC 2
SOC 2 Type II
Independently audited security controls
AICPA SOC 2
HIPAA compliant
Built to protect patient health information
BAAs signed
Business associate agreements in place

Network Status

Frequently Asked Questions

How is Network Status different from Verification?

Verification confirms eligibility and pulls benefit details. Network Status takes that data one step further, applying plan- and TPA-specific rules to determine in-network or out-of-network status automatically.

What is the no-code rules engine?

RCM teams can define and update network eligibility rules themselves, by plan, payer, or TPA, without filing an engineering ticket, so nuanced or fast-changing network logic stays current.

Does Network Status handle behavioral health carve-outs?

Yes — Network Status is built with carve-out and MCO logic (e.g., Carelon BH, Magellan Health) native to the rules engine, not added on afterward.

How fast is a Network Status request?

Average response time is 200 milliseconds — fast enough to return a status alongside the eligibility request itself, with no added wait for the patient or front desk.

What's the impact on denials?

Clients see roughly a 9% reduction in network-related denials, plus about 60 seconds saved per request that would otherwise require a manual lookup.

Is Network Status only useful for engineering teams?

No — it's built for both audiences. Developers get an API-first integration; RCM and operations teams get a no-code interface to manage the rules directly.

Ready to stop finding out about network status after the denial?

Show us where coverage questions, manual work, or cost uncertainty slow down intake. We’ll show you how Sohar can help your team get answers earlier and move more patients into care