Jump to Content
Zus Health
Product GuideAPI ReferenceChangelog
Log InZus Health
Log In
Product GuideAPI ReferenceChangelog

πŸ“– Introduction

  • Introduction to Zus Health
  • Zus Aggregated Profile

πŸ—ƒοΈ Populating the ZAP

  • Quickstart Guide
    • Architecture
    • M2M Application Setup
    • Creating and Seeding Patients
    • Reciprocity
    • Retrieving FHIR Data
  • Core Concepts
    • ZAP Structure
    • Universal Patient Index
    • How Zus Uses FHIR
    • Data Validation
    • Access Requirements
  • Data Services
    • Patient History API
    • Patient Events Notification APIs
    • Data Enrichment
    • Data Lenses
    • Data Marts
    • ZusHooks
    • GraphQL API
  • Access Controls
    • Setting up Users
    • User Authentication
    • Roles and Permissions
    • Cross-Builder Grants

πŸ“± ZAP Front-End

  • Zus App
    • Getting Started with the ZAP
  • Zus for EHRs
    • Healthie
    • Canvas Medical
  • Embeddable UI Components
    • Implementation Guide
    • Conditions
    • Medications
    • Allergies
    • Documents
    • Timeline
    • Patient History Request
  • Data-Enriched Forms
    • Forms Admin
    • Embedding a Zus Form
    • Getting Data From a Zus Form

❓ Support

  • Contact Support
  • FAQs
  • Operational Status
  • Compliance Support
  • Known Issues

πŸ“š Resources

  • Links to Zus UIs
  • FHIR Specification
  • Postman Collection
  • Privacy Policy
  • Terms of Service

Retrieving FHIR Data

Suggest Edits

The last step on your interoperability journey is to pull the data from Zus to surface in your own solution.

The simplest way to do this is use our FHIR APIs to pull resources you're interested in consuming as outlined here.

πŸ‘

The best way to pull patient data is by UPID - this allows users to take advantage of Zus aggregating data for a patient from all sources and connecting them via the UPID.

Follow along!

Updated 6 months ago