API Architecture

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

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

• An FHIR Data Store where Zus houses patient data
• A Universal Patient Identifier (UPI) service to manage patient identity
• 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