Data Nexus by Dart Health resolves each person across every feed it receives, even when the HR system, the carrier, and the claims vendor each use a different ID. It finds identifiers that stay consistent across sources and keeps each identity stable as files change. Any match it can't make with confidence goes to a person. Resolution runs at over 99% across about 3 million records a month.
The HR system uses an employee number, the carrier uses a subscriber ID, and a claims vendor may send only a name and a date of birth. Claims data is organized around payments and engagement data around providers, so neither is organized around the person.
Names and addresses change between files. Dependents often appear in one feed and not the others. A program that can't link a claim to the right enrolled member can't prove its outcomes to the employer paying for it.
Example: the HR system sends emp_id 4471, carrier eligibility sends sub_id A-9902, and a claims vendor sends only name and date of birth. All 3 resolve to one member, plus a spouse and child the HR system never returned.
Identity resolution runs above 99% across eligibility, claims, provider visits, and benefits, on about 3 million records a month.
Yes. We resolve dependents like any other member, including those who appear in only one feed.
If the match isn't confident, a person on our team reviews it. We don't merge records on a guess.
Yes. Identity doesn't depend on any one system's ID, so a new HR system or carrier ID attaches to the existing member.
Yes. You can update member records through the API without waiting for the next file.
We'll walk through how they resolve to one member, on a 30-minute call.
Our websites may request cookies to be set on your device so our apps can remember your preferences, to share browsing data that we use to improve our services, to understand what brings you here, and to serve more relevant advertising. You may customize your preferences anytime. To learn more, please read our Terms and Conditions and Privacy Policy.
