Onboard a new employer's eligibility file in under 7 days

Last reviewed
October 23, 2026
TL;DR

Data Nexus by Dart Health onboards a new employer client's eligibility file in under 7 days, and most feeds take same-day effort. The employer, its HR system, its TPA, or its carrier sends the file the way it already does. Our specialists map it to one documented member model and validate every record. Your product reads the same JSON API for every client.

Under 7 days
to take a new feed live
3M
records processed a month
HIPAA
SOC 2 Type II

Why onboarding stalls

If you sell to employers, you sign the contract before you have the data. Members can't enroll until the employer's eligibility file loads, so your implementation queue becomes your revenue queue.

Each employer sends eligibility in its own layout: an 834, a CSV, an HRIS export, or an API payload. Every new layout means another mapping to write and test, and one more way for the file to break.

That work lands on the same engineers who are supposed to be building your product.

How it works

  • Intake. The sender delivers over SFTP, webhook, or API, in the format it has: CSV, flat file, HRIS export, or API payload. 834 EDI intake is available on Enterprise plans.
  • Mapping. AI drafts the map from the sender's fields to our benefits member model. One of our specialists checks every map before any data flows.
  • Validation. We check the first file against the rules for its source before any record moves. See what happens when a file is wrong.
  • History and takeover. If a client is moving from another vendor or an in-house process, we load the prior history during onboarding so each member's record starts complete.
  • Delivery. Your product reads one documented REST API that returns JSON for members, eligibility, claims, programs, and program enrollments. Leave data is available on Enterprise plans. If your systems need a different layout, we build a custom feed instead.

Flat file or API?

You don't have to choose. Many employers, TPAs, and carriers can only send files on a schedule, and asking each one to build an API for you slows every implementation.

So Data Nexus takes the file the employer has and gives your engineers an API. Nothing reaches that API until it passes validation.

How Handpicked Health takes feeds live

Handpicked Health had to onboard a Fortune 50 employer's data at launch, an implementation projected at 6 months. Its latest Fortune 50 feed went from first test file to production-ready in 1 day. Across clients, new feeds go live in under 7 days, and most take same-day effort. Data Nexus processes about 3 million records a month.

Read the Handpicked Health case study

FAQ

Do our engineers rebuild anything for each new client?

No. Your product reads the same API for every client. A new client is a new feed on our side, and our specialists set it up and test it.

What happens when an employer switches HR systems mid-year?

We update the mapping for the new layout. Members keep their history because identity doesn't depend on any one system's ID. See matching members without a shared ID.

Can we test one real client before committing?

Yes. The Validation plan is $2,990 a month for the trial and includes 3 feeds and 500,000 monthly record updates.

What this doesn't do

  • It doesn't take 834 EDI files on Starter or Pro plans. You'll need Enterprise for that.
  • It doesn't move a feed to production before its first file passes validation, even when go-live is close.
  • It doesn't send enrollment from benefits administration software to carriers. Use Noyo or Ideon for that.
  • It doesn't check eligibility against a payer in real time (270/271). Use a clearinghouse such as Stedi or Eligible.

Bring a file layout to a 30-minute call.

We'll show you how it maps and how our validation checks work before records move.

Related solutions

Our Customers & Partners

Handpicked Health LogoDa Primus LogoSage Digital LogoMicrosoft Azure logoAmazon Web Services Logo