Zus Health

Zus Health publishes the Zus Aggregated Profile alongside the Zus App, a Zus API, embeddable components and a Data Mart, with EHR integrations across athenahealth, Canvas, Elation Health and Healthie.

Publishing embeddable components rather than only an API is the design decision that distinguishes this, and it addresses where health data projects usually fail.

An API gives a development team access to data and leaves them to build an interface for it. That is the right shape when the customer has engineers. Most healthcare organisations do not, and even those that do face a harder constraint: clinicians will not use a second application.

A clinician has a patient in front of them and minutes to work with. Anything requiring them to leave the record system, open something else, find the same patient and interpret an unfamiliar screen will not be used, regardless of how good the data is. Health technology is full of well-built products that failed on exactly this.

Embeddable components put the aggregated view inside the record system the clinician already uses, which is the only placement that gets looked at during a consultation.

The named EHR integrations identify the market precisely. athenahealth, Canvas, Elation and Healthie serve ambulatory and independent practices rather than large hospital systems, which is a market underserved by traditional interoperability because it lacks the integration budget hospitals have.

The aggregated profile itself addresses the fragmentation problem: a patient's record exists in pieces across every provider they have seen, and assembling those into one usable view is the work.

A Data Mart alongside the clinical view suggests analytic use as well as point-of-care use, which matters for practices in value-based contracts that must report on populations rather than individuals.

Pricing is not published.