Search
K
< Back

Data Flows

Health Gorilla delivers clinical data through structured, standards-based workflows that connect to national networks, match patient identities, normalize and deduplicate results, and return data as FHIR resources or original documents. These workflows support both retrieving external clinical records and sharing data back into the ecosystem when required.

Your organization can retrieve records synchronously for immediate use, subscribe to real-time updates through FHIR Subscription, contribute structured data through FHIR-based shareback workflows, or use asynchronous export for legacy or bulk use cases.

These examples illustrate how data moves through the Health Gorilla FHIR core—from initial request to retrieval, notification, export, or shareback delivery.

Retrieve a Patient Record with Patient360

You can use Patient360 to retrieve a comprehensive clinical record for a specific patient. This flow runs federated queries across national networks and connected data sources.

  1. Your system submits patient demographics or identifiers to Health Gorilla.
  2. Health Gorilla matches the patient across national networks using entity-resolution logic and referential data.
  3. The platform issues FHIR R4 queries to Carequality, CommonWell, eHealth Exchange, TEFCA QHINs, and connected laboratories.
  4. Retrieved documents are normalized, deduplicated, and converted into FHIR resources.
  5. Health Gorilla returns a FHIR R4 Bundle synchronously to your application.

Outcome: Provides a unified longitudinal record that supports care coordination, pre-visit review, analytics, and other clinical workflows.

Note: The $p360-retrieve operation supports bulk aggregation in FHIR R4. FHIR STU3 remains available only for legacy integrations.

Receive Notifications with FHIR Subscription

Using FHIR Subscriptions, you can arrange the automatic delivery of notifications when new or updated clinical events occur.

  1. Your system registers a FHIR Subscription resource that specifies your HTTPS endpoint and query criteria.
  2. Health Gorilla monitors incoming data for matches to your subscription parameters.
  3. When a matching resource is processed, the system sends a POST request with the full FHIR payload to your endpoint.
  4. Your application consumes the notification and updates its internal data or triggers event-based workflows.

Outcome: Enables clinical follow-up, automated outreach, and proactive decision support.

Monitor Admissions and Discharges with HL7 v2 ADT Messages

You can use HL7 v2 ADT messaging to support workflows that require prompt admission, discharge, or transfer notifications from hospitals and connected care facilities.

  1. Hospitals or partners send HL7 v2 ADT messages to Health Gorilla’s secure HL7 interface.
  2. Health Gorilla validates the message and optionally converts it into a FHIR resource.
  3. Notifications can be delivered as native HL7 v2 messages or through FHIR Subscription for downstream use.
  4. Your organization logs, displays, or routes the event for care-management and reporting workflows.

Outcome: Provides continuous visibility into hospital activity, enabling coordinated care, timely follow-up, and accurate reporting.

Export Documents for Downstream Processing

Document export workflows allow you to provide access to original-format clinical files such as C-CDA documents or PDFs for regulatory, analytical, or archival use.

  1. Your application searches for available documents using the DocumentReference resource.
  2. Health Gorilla returns metadata and download URLs for each document.
  3. Your system retrieves the file using the Binary resource or the $export-ccda operation.
  4. The original document can then be stored, parsed, or transferred to another system.

Outcome: Supports compliance reporting, manual review, and ingestion into applications that require native document formats.

Contribute Data Back to Networks

Your organization can contribute structured data to connected networks through Health Gorilla’s FHIR core, supporting shareback and reciprocity requirements.

  1. Your system submits validated FHIR R4 resources such as Observation, Condition, MedicationStatement, or DocumentReference.
  2. Health Gorilla validates and normalizes each resource against USCDI vocabularies and FHIR terminology mappings.
  3. Contributed data is routed to connected networks (for example, Carequality, CommonWell, eHealth Exchange, and TEFCA QHINs) through established trust channels.
  4. Provenance and audit metadata are recorded so downstream systems can trace data origin, authoring organization, and version history.

Outcome: Enables TEFCA-aligned shareback, supports national interoperability requirements, and ensures contributed data remains discoverable and usable by authorized participants.

For more informantion on reciprocity and shareback, go to Data Sharing.