Zus Health Raises $33M Series B for Connected Patient Data

Keeping a medical history useful is a recurring engineering job. Zus Health is asking healthcare software builders to buy that work together: the connections that retrieve outside information, the patient record that organizes it and the workflows that put it in front of a care team.

The Boston company announced a $33M Series B on November 10, 2026, led by Drive Capital, taking reported total funding above $100M. Sanofi Ventures, HealthX Ventures and Alumni Ventures participated alongside existing investors Andreessen Horowitz, F-Prime, Maverick Ventures and JAZZ Venture Partners. Founder and CEO Jonathan Bush is financing a business built around a fairly demanding promise: a patient's information should remain useful after it leaves the organization that created it.

For digital health companies and providers, the financing directs more resources toward shared data infrastructure beneath clinical AI. Zus plans to expand its clinical intelligence, national network and supported workflows, giving application developers a common foundation rather than another separate integration project to maintain.

A financing for the work between applications

Goodwin, which advised Zus on the financing, confirms the transaction's amount, round and investor roster. Neither that account nor the company's announcement discloses a valuation or individual investor allocations. The reported cumulative figure remains more than $100M; it should not be confused with the size of this round.

There is an economic choice inside the product architecture. A software builder can spend engineering time assembling outside records and keeping the connections current, or purchase a maintained foundation and concentrate more of its effort on the application. Zus is positioning itself to receive that infrastructure spending across multiple customers and use cases.

That makes continuity part of the commercial proposition. Retrieving information once can support a demonstration; maintaining its usefulness as the patient receives more care creates a continuing service obligation. Buyers evaluating Zus have reason to look closely at how the product handles new records, duplicates, missing context and delivery into their existing systems.

Bush brings experience as an athenahealth co-founder to that problem. Zus's current leadership page identifies Philip Wickline as CTO, Ada Glover as CPO and Jason Bent as CFO and COO. The company is bringing product, technical and operating work to a service whose value depends on connections continuing to function after the initial deployment.

A patient record with a maintenance budget

Zus describes its business through a network, a platform and workflows. The Zus Aggregated Profile, or ZAP, organizes information into a longitudinal patient record, while connectivity draws from sources including electronic health records, pharmacies, labs and care events. Its Generated Patient Summaries are intended to make that accumulated information easier for care teams to use.

The company's product site describes APIs, embedded views and integration into existing clinical software. It also emphasizes refreshing patient information and supporting exchange between connected systems. That delivery choice matters commercially because a provider has to fit the information into an actual working day, with existing tools and established responsibilities.

Consider a care transition as an operating example. A team needs to establish that an encounter happened, obtain useful documentation and put it where the person responsible for follow-up can act on it. Each step gives the next one something to work with; an elegant summary cannot compensate for an encounter that never reached the record.

For an application developer, this changes the boundary of what is being bought. The contract concerns the continuing availability of information as well as the presentation of that information. Clinical AI increases the number of things a developer can attempt with a record, while also making the quality and currency of that record harder to ignore. DevCuration’s coverage of Alterra Labs’ medical AI evaluations follows another part of that work: deciding how a clinical system’s answers should be assessed.

Reading scale without inventing outcomes

Zus reports more than 110M networked transactions during August 2026 and 39M evidence citations year-to-date across its solutions. The company supplies both figures, and they describe different kinds of activity over different periods. They offer a view of platform usage without establishing the savings or clinical benefits of an individual customer deployment.

An operator can use that distinction constructively. A useful evaluation would ask how much relevant outside information reaches the care team, how recently it was updated and how readily a user can inspect the underlying evidence. The commercial value becomes clearer when those answers connect to work a customer already has to perform.

Network participation also brings governance into the product discussion. Zus announced QHIN candidacy in August 2026 under the Trusted Exchange Framework and Common Agreement, or TEFCA. The official TEFCA framework describes a nationwide exchange structure with common requirements and a formal application, onboarding and designation process.

Candidacy is a specific stage in that process. The Recognized Coordinating Entity's directory distinguishes organizations that completed designation from candidates still onboarding. For a buyer, questions about permitted exchange, network status and responsibilities belong alongside questions about the interface and summary quality.

Where the shared foundation earns its place

Zus's financing puts the connection work and the application work in the same investment plan. That is a consequential combination for a company selling to organizations that need useful patient context inside software they already operate. Broader connectivity creates more potential information; effective workflow delivery gives a customer a reason to keep paying for it.

The competitive decision can begin inside the customer's own engineering budget. Buying a maintained data layer means depending on someone else's coverage, refresh and service quality. Building it internally means retaining responsibility for that work as the product expands, with each new workflow creating another use for the same underlying record.

Zus is trying to make the common foundation attractive enough to support both decisions: the developer's decision to build on it and the provider's decision to use what arrives through it. Its new investors are financing more of the network and clinical intelligence behind those handoffs. The next encounter will bring another piece of history, and someone still has to make sure it reaches the people taking care of the patient.