Introduction to Zus

Zus builds a single, current health record for each patient from the networks and sources it connects to, plus the data you send. That record is the Zus Aggregated Profile, or ZAP. Care teams use it to get up to speed on new patients and keep up as new events happen. Analysts and developers use the same data to build reports, workflows and products.

Where the data comes from

• EHR networks: records from thousands of provider sites, through CommonWell, Carequality and TEFCA
• Pharmacy: prescription fill data through Surescripts
• ADT: admission, discharge and transfer notifications through PointClickCare and Bamboo Health
• Labs: lab history and new results through Quest Diagnostics
• Your own data, through the FHIR API, document ingestion and EHR integrations

What Zus does with it

• Patient matching: links records for the same person under one Universal Patient Identifier (UPID)
• FHIR normalization: stores everything as FHIR R4
• Data enrichment: applies consistent terminology so data from different sources lines up
• Zus Lens: deduplicated summaries, so readers don't wade through repeat documents
• Intelligent Refresh: queries the networks again when new data is likely

You always have access to the raw data underneath, with provenance back to its source. See Understanding Zus data.

Ways to work with Zus

• The Zus App: the ZAP for care teams, as a standalone app or embedded in your own application
• EHR integrations: pre-built integrations with EHRs and platforms
• APIs: FHIR REST and GraphQL for reading and writing Zus data
• Zushooks: webhooks that push new data to your systems, for example ADT events
• Data Marts: read-only SQL tables in your data warehouse for analytics and bulk export

How these docs are organized