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

Known Issues

Suggest Edits

:white-check-mark: [Resolved] Inaccurate Patient History API status reporting

Posted on April 10, 2023

A high proportion of patient history API jobs are currently permanently reporting a status of in_progress, even if they have successfully completed processing and should be done. We do not believe this issue is impacting data ingestion and are working to provide accurate status information.

Updated 1 day ago


  • Table of Contents
    • :white-check-mark: Resolved Inaccurate Patient History API status reporting