Zus Health

All Zus products are built on top of a HIPAA-compliant FHIR-native data store, which includes detailed provenance and a terminology service.

The company is building customizable features that users can select to meet technology-stack-specific needs.

Details like demographics, coverage, care team, and medications matter. Leveraging the Zus Patient History API, Zus patient profiles include all the key information – and are flexibly available through either an API or embedded UI element.

These are pretty commonplace decisions where most developers have a preference based on their previous experiences. Things get interesting when the line between buy and build becomes blurred, particularly for cross cutting functionality like authentication.

The page describes an emerging healthcare data landscape and conflicting business motives.

The first installment of the Zus Q&A series features Dave Boerner discussing the current landscape of interoperability.

The company says its work is guided by compassion for patients and its people, and that diverse backgrounds strengthen collaboration on new solutions.

In a conversation with Zus Health CEO Jonathan Bush, Larry from Tennessee Oncology discusses a familiar challenge in oncology care: patient data exists, but turning it into something clinicians can actually use takes too long.

The page says digital health is more usable for many patients and care providers, while outdated tools and limited systems put digitally enabled care at risk.

Zus Health 1 Lincoln St., Suite 2900 Boston, MA 02111

Zus provides patient data at the point of care through an API, embedded components, and direct EHR integrations to support healthcare data interoperability. Its mission is to maximize patient insights for value-based care.

The definition covers activities of a Covered Entity related to covered functions, including quality assessment and improvement, clinical guideline development, patient safety, and population-based activities.

GitHubRepository owner