Skip to main content
Nexo Access

The platform

The whole trip, in one system.

Dedicated views for members, care teams, transport providers, and operations connect each ride request to dispatch, assignment, claims, compliance, and oversight in one system.

A four-step walkthrough of the Nexo Access operations software. Step one, schedule: composing a wheelchair trip for the sample member J. Sample. Step two, assign: assigning it only to a driver whose credentials are current, since drivers with expired credentials are blocked from assignment. Step three, complete: advancing the trip through validated status changes to a final, tamper-evident completed record. Step four, bill: running the resulting claim through four automated scrubbing checks and seven adjudication checks before it is billed to the plan that covered the member.

Nexo Access · DispatchSample data

System chapters

Four connected operating areas, shown in the same order a ride request and claim move through the system.

01
Dispatch

One validated path for every trip.

From booking to a locked, completed record, the system holds the trip to a single path.

  • Every trip follows a validated state machine. Completed, cancelled, and no-show are final.
  • Drivers and vehicles with lapsed credentials are blocked from assignment, checked live at dispatch.
  • Two dispatchers can’t overwrite each other: the losing write is rejected, and every turnback or restore carries a logged reason.
  • Outbound and return trips scheduled around the appointment, including will-call returns.
Assign driverSample data
M. RiveraReady · credentials current
D. OkaforBlocked · license expired
Assigned to M. Rivera
02
Claims & billing

Clean claims, by construction.

The checks run before submission, and the record can’t be quietly changed after.

  • Four automated scrubbing checks before a claim can be submitted.
  • Seven adjudication checks route every claim to approve, review, or deny.
  • Thirteen fields frozen at submission into a tamper-evident record.
  • A database constraint makes double-paying a claim impossible.
  • A two-level appeal ladder: appeals provable from the platform’s own records overturn automatically.
  • Every claim bills the plan that covered the member on the trip date.
  • Timely-filing deadlines warn before they lapse.
Claim reviewSample data
CLM-3390Trip NX-1042
Signature on file
Driver match
Vehicle match
Mileage source
7/7 adjudication checks passed
13 fields frozen · tamper-evident
Denied? A two-level appeal, provable from the records, overturns automatically.
03
Compliance

Isolation and audit, enforced in the database.

These controls are constraints the platform can’t skip, not entries in a policy binder.

  • Credentials tracked for drivers, vehicles, and providers. Expiry blocks assignment automatically.
  • Providers only receive the service levels they’re formally approved for, enforced at the database level.
  • An immutable audit trail on the records that matter.
  • Row-Level Security on every table, for per-organization isolation.
  • Built for HIPAA compliance
CredentialsSample data
M. RiveraCurrent
A. BelloExpiring · 12 days
D. OkaforExpired · blocked
Row-Level Security · per-organization isolation
04
Oversight & reporting

Exceptions get a person, not a rubber stamp.

The claims that need judgment wait for it; the rest keep moving.

  • Flagged claims are held out of automatic payment until a person reviews them.
  • Exception review with a full decision trail.
  • Pattern reports by rule, driver, and provider.
  • CSV / Excel exports for program reporting.
Exception queueSample data
CLM-5120Held for review
Held out of automatic payment
In review · assigned to a reviewer
Pattern report · by rule, driver, provider

Walkthrough

See it with your own trips in mind.

A walkthrough with your program, provider, and claim questions in view.

Talk to usProvider interest