Sacra Logo

What problem does Zus Health solve, what is its customer profile, and what use cases drive user adoption?

Brendan Keeler

Head of Product at Flexpa

In the past couple of years, we're seeing a shift towards virtual-first care, towards digital health organizations that are providers. They're employing providers and are typically providing that care natively in digital channels. So, it could be as simple as the tele-prescribers, the Hims and Roman and Thirty Madison. There's the primary care and the telehealth providers we think of (Teladoc and things like that), but increasingly, we're seeing more and more nuanced edge cases.

They're going to be disease-specific. You see the Omadas. You see SWORD Health, all those. For the trans or queer communities, you see FOLX Health. You see Spora Health targeting people of color and trying to meet those needs and give and provide better care based on identity.

Off-the-shelf EHRs and customer relationship management tools aren't built with the assumptions in mind that these companies have. They aren't built for virtual-first care. They aren't built for value-based care. Zus Health aims to help these builders. We have a couple of different immediate product offerings that are aimed to help. We're not going to make a full headless EHR out of that. That's just a very high MVP, but we're providing distinct value in the short term.

One is a holistic patient 360, pulling the entirety of the patient's record. That's medical history. That's medication history, lab, social determinants, you name it, pulling that all together, cleansing, enriching it, and then using that to fuel workflows is one aspect. 

Our workflow tooling is another. Rather than have this software that's based around some of the core assumptions of an encounter and a claim and those transactional moments, it's built around the care plan and a care team, and the tooling to really facilitate digital interactions and the handoff of tasks as somebody goes through that ongoing relationship. Those are both user interfaces and also APIs. Like many companies, we're leaning into API first. We see our customers as builders, and ensuring that we're not getting in their way is really important.

Those first two products are the immediate things, but as we build our community of digital health providers, we want to facilitate seamless co-treatment and collaboration. So, if I'm a customer or patient at One Medical and they're on Zus, and then I go and see Oshi Health for a GI problem, it should feel like that care team just extends beyond the walls and the boundaries of my enterprise. And that, we think, is a level up over anything available in healthcare today. So, that's the short-term and medium-term plans for Zus and what we offer.

Find this answer in Brendan Keeler, Senior PM at Zus Health, on building infrastructure for digital health
lightningbolt_icon Unlocked Report