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.
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.
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.
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.
Our engineers set it up when the partner is added. You tell us which fields the partner is allowed to receive, and when.
Yes. We build each partner's feed to fit the systems that partner already uses.
Each partner gets only the fields it's configured for, under need-to-know access controls. Data is encrypted in transit and at rest.
We'll map it with you on a 30-minute call.

