The questions buyers ask us first.

You can build the parser. AI has made that part cheap, and it keeps getting cheaper. What doesn’t get cheaper is owning the pipeline after it ships. Here's what Data Nexus by Dart Health handles for you for less than what you'll pay to maintain it: hosting & server maintenance, SOC II and HIPAA compliance, file validation, error communications, matching the same member across vendors and IDs, data auditability, and keeping history intact when a carrier changes its format. That work never ends, and it grows with every feed you add.

Dart is priced around that math. Up to 50 feeds costs less than half of one FTE, and adding feeds within a tier costs nothing more.

Most of the companies we talk to do too, and they’re good at it. The question isn’t capability, it's opportunity cost.

Dart takes feed negotiation, intake, history & takeover, validation, and exception triage off your team’s plate completely for less than you're spending, so your teams can get back to delivering your product.

A person is. Every record is checked for type, range, duplicates, consistency, and deviation from the prior file before anything moves downstream. A bad record only stops that record, while the rest of the file continues.

When something fails, AI proposes what most likely happened, and a person on Dart’s team makes the call. If that holds up a delivery, your downstream partners are told. AI proposes. A person decides. The file waits.

PHI stays within Data Nexus, and each downstream consumer receives only what is needed under need-to-know access controls. All data is encrypted in transit and at rest, we sign BAAs, and our controls are independently audited for ongoing SOC 2 Type II compliance.

Retention follows your contract: we keep what you need for as long as you need it. Our full security packet is available on request, and current reports and policies live in the Trust Center.

You tell us, and the correction goes into the validation set for that source so it doesn’t happen twice.

Exceptions are visible to you, not just to us. You can see what was flagged, what was decided, and why.

Typically as a file. The employer and its HR system, its TPA or its carrier sends eligibility directly to us over SFTP as an 834, a CSV, or an HRIS export on its own schedule and in its own layout. Each new employer client means a new mapping, new tests and a new way for the file to break.

Dart takes the file however the client sends it: SFTP, webhook or API. Every record is validated as it comes in, and your product reads one documented JSON API that is the same for every client or as custom feeds configured so your existing systems don't need to be overhauled. Send it however you have it. Nothing moves downstream until it’s right.

Dart does. Our specialists set up each new feed, own the exceptions when a file is wrong, and keep the mapping current when a client changes systems. Your engineers build against one API instead of one integration per client.

We built Data Nexus for digital health companies that sell to employers: MSK, mental health, oncology navigation, GLP-1 and cardiometabolic care, fertility, caregiving, leave, and more. Most have 20 to 500 people and an engineering team with better things to build.

They solve different halves of the problem. OneSchema is a configurable importer your team runs. It maps, validates and processes eligibility files from your clients’ HR systems, and it’s a strong choice if you want to run eligibility operations in-house with better tooling.

Data Nexus by Dart Health is software plus the people who run it. Our specialists own intake and exceptions, and one API delivers eligibility alongside claims, leaves, programs and enrollments. Choose Data Nexus by Dart Health if you would rather not continue hiring staff to handle eligibility data operations at all.

Days, not months. New feeds for Data Nexus clients go live in under 7 days, and most take same-day effort. New Fortune 50 implementations for Handpicked Health that would take traditional teams six months take no negotiation and less than 24 hours.

The speed comes from validation and a proven benefits member model that already exists, not from skipping validation. Each feed is checked against the rules for its source before the first record moves.

Each employer authorizes a claims feed from its TPA or carrier, and each feed arrives in its own layout. Most solutions stall here, where the data exists but every source needs its own software integration. Data Nexus by Dart Health removes those blockers.

Data Nexus ingests claims the same way it ingests eligibility: it matches each claim to the right member and delivers both through the same API. Your outcomes team works from one unified member record, instead of a stack of files.

The same way as eligibility: a file or an API feed from the employer’s HR system or its leave administrator. It matters if your program needs to know who is out, who is returning, or who just became eligible.

Data Nexus by Dart Health treats leave as its own feed, with its own validation, and delivers it through the same API, matched to the same member as their eligibility and enrollments.

Dart also performs history & takeover operations as a part of onboarding to make this process painless.

Start in October. Most employer plan years renew January 1, so new clients, open-enrollment files and changed layouts all land in the same few weeks, and member go-live dates don’t move.

Get files in early, test each one against last year’s, and agree in advance who decides when a file is wrong. Dart sets up new feeds in days, which leaves room for the clients who sign late.

Usually for one of three reasons. The layout changed without notice, a field holds the wrong kind of value, or the file contradicts the last one, such as a mass termination nobody intended. Most loaders catch only the first.

A file can parse perfectly and still be wrong. Dart checks every record for type, range, duplicates and consistency, and compares it with the prior file before anything moves. A bad record errors out and the rest of the file continues. A file-wide problem stops the file.

Accept the format they have, and hold the content to one standard. Asking every employer to match your layout slows each implementation and rarely sticks.

Dart takes 834s, CSVs, flat files, HRIS exports and API payloads over SFTP or webhook, and maps each one to the same documented model. We’re flexible on format and strict on content: nothing reaches your API until it passes validation.

With identity resolution, not a shared ID. Employers, TPAs and vendors rarely use the same member identifier, and names, addresses and dependents change between files.

Data Nexus by Dart Health resolves identity across every feed it receives (eligibility, claims, leaves and program enrollments) at over 99%, across about 3 million records a month. A match that can’t be made with confidence goes to a person, not a guess.

For a single file, use an open-source X12 parser, because the 834 is a published standard (005010X220A1). The hard part comes later in production, because each sender implements the 834 standard differently with their own quirks, outdated documentation, human errors, loops that get used differently, and dependents with coverage dates that have to stay consistent from one file to the next.

Yes. Data Nexus by Dart Health is a documented REST API that returns JSON for eligibility, claims, leaves, members, programs and program enrollments. Your clients keep sending data however they do today, and your product reads the API.

Member records can also be updated directly through the API, without waiting for the next file.

Check the content, not just the format. A schema check tells you the file parsed. It doesn’t tell you that 400 employees were terminated by mistake, or that a coverage end date falls before its start date.

Data Nexus by Dart Health runs checks like these in layers: type and range for each field, duplicates, consistency across a member’s records, deviation from the prior file, and a threshold check of what percent of new data differs from the old data to ensure against catastrophic errors. Error catching systems float these errors, so that a person can triage every failure. Each correction is added to that source’s validation set so the same error isn’t repeated.

A few neighboring jobs belong to other tools. For real-time eligibility checks against a payer (270/271), use a clearinghouse such as Stedi or Eligible. For sending enrollment from ben-admin software to carriers, use Noyo or Ideon. For employer claims analytics, use a platform such as Springbuk. For a CSV importer inside your own product, use OneSchema or Flatfile. For HL7 or FHIR integration with hospital EHRs, use Redox.

Data Nexus by Dart Health takes in employer benefits data from many sources, validates it, and delivers it through one API to the companies that serve those employers.