Send each partner its own feed, limited to the data it needs

Last reviewed
October 23, 2026
TL;DR

Data Nexus by Dart Health builds a separate feed for each downstream partner from the same unified member record. Each feed carries only the fields that partner needs and arrives on that partner's schedule. Dart's engineers configure each feed as part of partner setup. Handpicked Health runs partner feeds for several employer clients in production today.

0
manual exports
3M
records a month
HIPAA
SOC 2 Type II

Why one export doesn't fit every partner

If you coordinate care for an employer's population, you work with several vendors, like a navigation partner, a pharmacy partner, and an analytics team. Each one needs a different slice of the same population, in its own layout and on its own schedule.

Without a system for it, each slice becomes a manual export or a one-off script. So partners get more PHI than they need, because trimming it is extra work. And someone has to carry every source change into every export by hand.

How each partner feed gets built

  • Every source flows into one unified, validated member record, with identity resolved.
  • For each partner, our engineers configure the fields it receives, the layout, the delivery method, and the schedule.
  • We build each feed from the unified record and limit it to the configured fields, so a partner never gets PHI outside its scope.
  • When a source changes, every partner feed updates from the same record, and you don't re-export anything by hand.
  • If a validation hold delays a delivery, the affected partners get notified.

For example, a care navigation partner gets eligibility only, daily at 6 AM. A pharmacy partner gets eligibility and plan, weekly. Your analytics team gets claims and visits, nightly.

Running in production at Handpicked Health

Handpicked Health serves several employer clients, each with its own set of partners. Each of those partners gets its own feed configuration, running in production today.

FAQ

Who sets up a new partner feed?

Our engineers set it up when the partner is added. You tell us which fields the partner is allowed to receive, and when.

Can a partner receive a different layout than our API?

Yes. We build each partner's feed to fit the systems that partner already uses.

How is each partner's access kept separate?

Each partner gets only the fields it's configured for, under need-to-know access controls. Data is encrypted in transit and at rest.

What this doesn't do

  • You and the employer set what each partner is entitled to receive. Dart enforces that scope.
  • It doesn't replace the data-sharing agreements or BAAs between you and each partner.
  • It doesn't send enrollment from benefits administration software to carriers. Use Noyo or Ideon for that.

Send us a list of your partners and what each one gets today.

We'll map it with you on a 30-minute call.

Related solutions

Our Customers & Partners

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