Data Availability and Behavior

The Patient Chart displays only the data that is currently available for the selected patient in the processed dataset within the tenant. What appears in the chart depends on prior workflows, source-system responses, patient matching outcomes, and applicable configuration.

Availability Prerequisites

Data appears in the Patient Chart only after an upstream Health Gorilla workflow has made patient data available in the tenant. These workflows include Patient360 retrieval from exchange networks and direct integrations, Lab Network order results, admission, discharge, and transfer (ADT) and event data delivered to the tenant, and documents stored by Clinical Alerts.

If no prior workflow has completed, or if no data is returned or contributed for the patient, the chart may contain limited or no records.

Upstream Dependencies

Data availability and completeness depend on factors outside the Patient Chart, including:

• Whether external organizations or connected systems have records for the patient
• Whether those records are returned through enabled exchange pathways
• Whether records are successfully matched to the correct patient through the Master Patient Index (MPI)
• Whether client-contributed data has been submitted to the tenant
• Whether lab or imaging results have been delivered through the Lab Network
• Whether ADT or event data has been delivered to the tenant
• Whether Clinical Alerts have stored documents for the patient
• Tenant configuration, feature enablement, and applicable consent settings
• The structure, quality, and timeliness of source data

Point-in-Time Behavior

The Patient Chart reflects the current state of the processed dataset at the time it is opened or refreshed.

• Opening the chart or navigating between sections does not trigger new upstream retrieval from external networks or a new ingestion workflow
• Search, filtering, and sorting query the patient's already-processed data in the tenant; they do not pull new data from external sources
• Chart content changes only after an upstream workflow completes

As a result, the chart should be understood as a point-in-time view of the patient record, not a continuously refreshed connection to external systems.

Data Completeness and Variability

The amount and type of data available in the Patient Chart may vary by patient, source, and workflow.

Variability may appear in several ways:

• Some patients may have extensive structured data, while others may have primarily document-based records
• Some chart sections may contain records while others remain empty
• Structured records may provide less detail than the source document from which they were derived
• Metadata, timestamps, classifications, and available fields may differ across sources

An empty section indicates that no corresponding records are currently available in the processed dataset for that patient. It does not necessarily mean that no such records exist in external systems.