---
updatedAt: 2026-10-28T21:27:35.000Z
agentTools:
  projectIndex: https://docs.zushealth.com/llms.txt
---

# Architecture

How your clinical application and backend connect to the Zus services and APIs.

# API Architecture

Let's dive into the basic architecture model of how your solution will integrate with Zus.

![](https://files.readme.io/3b8ae7d06156709cf84f602ed8ca946b3885f5fa7b6855fcb37a381e4c9a8361-image.png)

### Your Tech Stack consists of

* A clinical application where users will view and interact with data about your patients.
* A backend engine that will orchestrate calls to the Zus API layer for doing things like:
  * Creating patients
  * Subscribing/querying patients to pull data from Zus connected networks
  * Writing new data back to Zus on your patients (reciprocity)
  * Pulling data from Zus via FHIR REST or GraphQL APIs for visualizing in your clinical application

### Zus Tech Stack consists of

* A FHIR Data Store where Zus houses patient data
* A Universal Patient Index (UPI) service to manage patient identity and assign each patient a Universal Patient Identifier (UPID)
* A Lens service to summarize and deduplicate data aggregated from external networks
* An Enrichment service to normalize code sets across data aggregated from external networks
* REST/GraphQL APIs for interacting with Zus data
* Zushooks for pushing new patient data to your system
* The Zus App for interacting with patient data at the point of care
* Zus Data Mart for SQL-friendly, relational view of Zus FHIR data for pop health analytics

# Systems Interaction

Below is an interaction diagram highlighting the interplay between your system and Zus

![](https://files.readme.io/ec7a658-image.png)

## Related pages

* [Developer Quickstart](https://docs.zushealth.com/docs/quickstart-guide)
* [Creating App Clients](https://docs.zushealth.com/docs/creating-app-clients)
* [Creating Patients](https://docs.zushealth.com/docs/creating-patients)