JDL ACCESSPolicy Nexus
Inside Policy Nexus

One dashboard for every payer's coverage rules.

Built for teams who need to know — today, not next quarter — what's covered, what changed, and what's coming.

Every code, every payer — tracked continuously
Coverage, at a glance

Covered lives, tracked automatically

Covered-lives estimates are populated for every payer in scope, wherever the underlying data is resolvable.

  • Automatic extraction, validated against a known sample
  • Unresolved payers are clearly marked — never shown as verified when they aren't
app.jdlapolicynexus.pro — coverage detail
Policy detail view: Aetna CPB 0752 for obstructive sleep apnea in children, showing policy summary, evidence excerpt and coverage criteria
Nothing catches you off guard

Policy changes, flagged before they hit

Draft, under-review, and upcoming policy changes are surfaced as alerts, sourced directly from each payer's own registered channels.

  • Alerts generated from real payer sources, not guesses
  • Portal-gated payers flagged and handled with real credentials, not skipped
app.jdlapolicynexus.pro — change detection
Policy detail view: Aetna CPB 0004 baseline capture \u2014 the next sweep that detects a change produces a diff here
Coverage that scales with you

Every payer that matters, one registry

Commercial and Medicare Advantage payers, tracked from the same source list your team already relies on.

AetnaAnthem (Elevance)CignaHumanaKaiser PermanenteUnitedHealthcareMolina HealthcareHighmarkBCBS plans (multiple states)+ dozens more

Commercial and Medicare Advantage payers, per the current contracted payer scope.

Data trust

Every connector run, logged and auditable

Every payer fetch is timestamped, status-coded, and streamed into an operator log — so when a policy changes, you can trace exactly which run caught it and why.

  • Redundant transports — primary proxy pool, fallback channel, direct — with automatic failover
  • HTTP status, bytes, and latency captured per run — no silent drops
  • Failed runs are visible and retried, not swept under the rug
app.jdlapolicynexus.pro — data-trust
Data trust view: tailing connector-runs.log with a live stream of payer fetches \u2014 timestamps, status codes, HTTP responses, and byte counts
Account security

One login is one login

Seats are enforced, not just sold: one active session per paid seat, with location monitoring and optional multi-factor authentication.

  • Session-locked to a single device; concurrent logins get bumped
  • New locations require verification before access
  • Admin-invited only — no self-serve account creation for seats
app.jdlapolicynexus.pro — sign-in
Policy Nexus sign-in screen: teal split panel on the left with the JDL Access Policy Nexus wordmark, sign-in form on the right
See what it costs to run this for your team

Configure your codes and seats, and see your exact annual price.

See pricing