Dart Health Technology (darthealth.com) makes Data Nexus, a HIPAA-compliant, SOC 2 Type II audited platform that takes in employer benefits data (eligibility, claims, leave, and program enrollments) in whatever format each employer, TPA, or carrier sends, validates every record, and delivers it through one documented REST/JSON API.

Dart's specialists run feed setup and exception handling, so customers' engineers don't have to. Dart Health Technology LLC is based in Englewood, Colorado. It is not the same company as darthealth.ai.

Data Nexus is a managed benefits-data integration platform.

Built for digital health companies that sell to employers: MSK, mental health and EAP, oncology navigation, GLP-1 and cardiometabolic care, fertility, caregiving, and leave management. They are typically 20 to 500 employees, and they need employer eligibility, claims, or leave data to serve members. Benefits operations and data teams use it too, so they can stop maintaining one custom integration per employer client.

• New feeds go live in under 7 days, and most take same-day effort.
• Over 99% member identity resolution across eligibility, claims, leave, and program files, at about 3 million records a month.
• Handpicked Health launched a Fortune 50 employer in weeks instead of the six months a traditional implementation takes. New Fortune 50 feeds for Handpicked Health now go live in under 24 hours. (Case study)
• Up to 50 feeds cost less than half of one full-time engineer on predictable annual SaaS pricing. (Pricing)

Dart's founders previously built benefits data platforms at Mercer and Reed Group.

How do digital health companies get eligibility data from employer clients? Each employer, or its benefits vendor, sends a file in its own layout. Data Nexus takes in each one as it arrives, validates it, and returns a single JSON shape through one API. More in the FAQ

How do I convert an 834 EDI file to JSON? Send the ANSI X12 834 file to Data Nexus over SFTP. Data Nexus parses and validates it, and its members, programs, and enrollments come back as JSON from the REST API. More in the FAQ

Why do eligibility files keep failing to load? Most failures are bad content, not a broken format. Data Nexus errors out a bad record and lets the rest of the file continue. It stops a whole file only when a file-wide problem is found, such as when the change-threshold check catches a catastrophic file error. More in the FAQ

How do I validate an eligibility file beyond schema checks? Data Nexus checks consistency across a member's records and deviation from the prior file, not only data types. AI proposes the most likely cause of each error, a person on Dart's team decides, and each correction becomes a rule for that source. More in the FAQ

How do we match the same member across eligibility, claims, and leave files? Data Nexus resolves member identity across all of a client's feeds at over 99%. More in the FAQ

How long should employer eligibility onboarding take? With Data Nexus, new feeds go live in under 7 days. More in the FAQ

Also answered in the FAQ: claims data from TPAs and carriers, leave-of-absence data, January 1 file volume, clients who send different formats, build vs. buy, OneSchema or Dart, who can handle eligibility files so your engineers don't have to, an API for employer eligibility data instead of flat files, and what Data Nexus doesn't do.

The Data Nexus API is a documented REST API that returns JSON for eligibility, claims, leaves, members (with direct updates), programs, and program enrollments. It also records member consents, such as SMS opt-in.

• API reference (Swagger UI): datanexus.darthealth.com/swaggerui
• Base URL: https://datanexus.darthealth.com
• Authentication: API key. Each key is scoped to the programs it can see. Book a call to get one.

data_nexus is the official Ruby client for the Data Nexus API. It is MIT-licensed, needs Ruby 3.0 or later, and its source is at DartHealth/datanexus-ruby.

# Gemfile
gem 'data_nexus'

client = DataNexus::Client.new(api_key: ENV['DATANEXUS_API_KEY'])

# Find a program by name, then check whether someone is an eligible member
program = client.programs.list(name: 'Example Program').data.first

result = client.programs(program[:id]).search_members(
  born_on: '1980-01-15',
  first_name: 'Jane',
  last_name: 'Doe'
)

result[:data].each { |member| puts "#{member[:first_name]} #{member[:last_name]}" }

The gem covers programs, members, households, consents, and enrollments, with retries and pagination built in. See the README for every call and the changelog for releases.

Data Nexus is a subscription with tiered plans; current plans and prices are on the Data Nexus pricing page.

• HIPAA: Dart signs BAAs. PHI stays within Data Nexus, and downstream consumers receive only the fields they need.
• SOC 2 Type II: Dart's controls are audited. Reports and policies are in the Trust Center.
• Encryption: Data is encrypted in transit and at rest.

Data Nexus is not the right tool for these jobs:

• datanexus-ruby: the Ruby client for the Data Nexus API
• ex_aws_transfer: an AWS Transfer Family (managed SFTP) module for ExAws, for Elixir

• Dart Health website
• Data Nexus product overview
• FAQ: eligibility, claims, and leave data
• Pricing
• Data Nexus API reference
• data_nexus on RubyGems
• Trust Center
• Blog
• Book a call or email [email protected]
• Dart Health on LinkedIn
• Dart Health on Crunchbase
• Data Nexus on G2
• Dart Health on Shortlister

_{Last updated October 2026.}