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/FQS API for visualizing in your clinical application

Zus Tech Stack consists of

  • An API layer for managing requests from our customers
  • A FHIR data store for housing information about your patients and FHIRPlace for interacting with data
  • A web based Zus Application for interacting with patient data at the point of care
  • A Data Mart for real time export of rectangularized data from Zus for pop health analytics purposes
  • A set of connected networks which we leverage to pull data about your patients across healthcare systems. We do the hard work of converting documents to FHIR resources
  • An authentication and authorization layer for securing requests and data in transit and at rest
  • A Universal Patient Identifier (UPI) service to aggregate all the data we find on your patients around a single Master Patient Identifier (MPI)
  • A Data Lens service to clean up the data we find across the networks, de-duplication for example
  • An Enrichment service to normalize code sets across our connected networks

Systems Interaction

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

What’s Next