National Network Retrieval
National network retrieval enables organizations to access clinical records from external care settings through Carequality, CommonWell, eHealth Exchange, and TEFCA-based networks. Records are retrieved through Health Gorilla’s Patient360 framework, which performs identity resolution, request routing, and normalization before returning a complete longitudinal dataset. This approach supports broad interoperability across disparate health systems, EHR vendors, and exchange networks.
Key Characteristics
| Attribute | Behavior |
|---|---|
| Response model | Assembled longitudinal record |
| Data storage | Stored and normalized in Health Gorilla |
| Record formats | Returned as FHIR R4 bundles and C-CDA documents |
| Identity handling | Identity verified and linked via MPI |
| Routing ownership | Health Gorilla orchestrates record requests across networks |
| Document fulfillment | Multiple external data sources |
| Audit visibility | Full end-to-end retrieval history in TEC > EHR Audit |
| Viewer visibility | Viewable in Patient Viewer |
Use Cases
National network retrieval is commonly used when:
- Comprehensive longitudinal history is required across multiple care sites and EHRs
- Population-level or cross-facility record coverage is necessary
- Data must be normalized before ingestion into downstream systems
- Integration requires consistency and standardization rather than original-format documents
General Workflow
National network retrieval produces a unified aggregated record.
- A retrieval request is submitted to Health Gorilla
- MPI verifies and links patient identity across network sources
- Queries are executed across participating exchange networks
- Records are retrieved from external responding systems
- Documents are normalized and aggregated into a longitudinal patient record
- The resulting bundle is delivered to the requester
Common Outcomes
| Result Behavior | Explanation |
|---|---|
| Large consolidated dataset | Multiple responding sources |
| Documents from unanticipated facilities | Broader network discovery |
| Duplicate or similar records | Caused by varying source formats or events |
| Partial records returned | Limited local participation or incomplete data availability |
| No records returned | No matching patient or minimal query coverage |
Outcome Expectations
Effective use of national network retrieval ensures that:
- Patient identity is resolved consistently across multiple networks
- Aggregated records are normalized and structured for ingestion
- Data availability reflects what external care sites contribute to exchange networks
- Requesters understand expected response variability based on network participation
Best Practices
- Provide complete demographics to improve match success
- Narrow or broaden date filtering based on expected availability
- Review Patient Viewer to understand record composition and provenance
- Use asynchronous retrieval for large datasets
- Monitor audit history to confirm participation and response outcomes