Retrieval Models

Retrieval models define how clinical records and documents are located, returned, and delivered within the Health Gorilla platform. Each model supports different interoperability requirements and determines how records are retrieved, stored, normalized, and presented across Patient360 and connected exchange networks.

Model Comparison

Attribute	Standard Retrieval	National Network Retrieval	Federated Retrieval	Event-Driven Retrieval
Response origin	Patient360	National networks	Responding system	Event callback
Data format	Normalized FHIR R4 and C-CDA	C-CDA, normalized	Original source format	Event payload with optional follow-up retrieval
Stored in Health Gorilla	Yes	Yes	No	Yes (optional)
Viewer visibility	Yes	Yes	No	Yes
Response timing	Asynchronous	Asynchronous	Relay	Asynchronous notification
Primary purpose	Unified longitudinal record	Network-based record discovery	Direct controlled exchange	Continuous monitoring and update delivery

Standard Retrieval

Describes how normalized patient records are retrieved through Patient360 after aggregation, deduplication, and FHIR transformation.

National Network Retrieval

Explains how records are retrieved from national networks such as Carequality, CommonWell, eHEX, and TEFCA/QHIN before normalization and assembly.

Federated Retrieval

Details direct system-to-system delivery, where responding organizations return documents to the requester without storage or normalization in Health Gorilla.

Event-Driven Retrieval

Outlines subscription-based delivery models that notify requesting systems when new or updated records become available.