Standard Retrieval
Standard retrieval returns normalized clinical records through Patient360. Retrieved documents are aggregated from national networks and connected sources, normalized to FHIR R4, and stored within the Health Gorilla platform for viewing and downstream processing. This model supports longitudinal record creation, document reuse, and consistent data representation across workflows.
Key Characteristics
| Attribute | Behavior |
|---|---|
| Response model | Records aggregated and normalized into Patient360 |
| Data storage | Stored within the Health Gorilla platform |
| Record format | Returned as a unified FHIR R4 Bundle and C-CDA documents |
| Identity handling | Identity verified and linked through the MPI |
| Routing ownership | Health Gorilla |
| Audit visibility | Full end-to-end audit available |
| Viewer visibility | Records appear in Patient Viewer |
| Retrieval timing | Synchronous or asynchronous |
Use Cases
Standard retrieval is effective when:
- A unified longitudinal record is required for care coordination or analytics
- Documents must be normalized to a consistent structure
- Multiple sources must be reconciled and deduplicated
- Records need to be retained and available for audited review
General Workflow
Standard retrieval follows an aggregation and normalization model.
- Identity is matched or enrolled in the MPI
- Record retrieval is initiated via Patient360
- Health Gorilla collects documents from connected networks and sources
- Records are normalized and deduplicated into FHIR R4
- A complete record bundle is assembled and delivered
- Data is stored and visible in the Patient Viewer
Common Outcomes
| Result Behavior | Explanation |
|---|---|
| Longitudinal record assembled | Records successfully retrieved, normalized, and linked |
| Partial result set | Some sources may not return additional documents |
| Missing records | Typically caused by incomplete identity resolution or limited source availability |
| Asynchronous completion | Large record sets may continue processing after initial response |
Outcome Expectations
Effective use of standard retrieval ensures that:
- Identity resolution determines the accuracy and completeness of the record
- Retrieval succeeds across all connected sources under a single workflow
- Records are normalized to FHIR R4 to support interoperability, analytics, and reuse
- Full audit visibility is available for troubleshooting and compliance
Best Practices
- Confirm patient identity and demographic completeness before initiating retrieval
- Use asynchronous processing for large queries or broad date ranges
- Leverage the Patient Viewer for result validation and audit review
- Avoid repeated retrieval attempts while a job is still processing