Health Gorilla: TEFCA QHIN Architecture, Patient360 API, and C-CDA to FHIR R4 Normalization

Health Gorilla is a healthcare interoperability platform and designated Qualified Health Information Network (QHIN) that provides RESTful APIs for nationwide clinical data aggregation, diagnostic laboratory ordering and resulting, and health information exchange. In clinical informatics, digital health engineering, and real-world data (RWD) research, Health Gorilla acts as an abstraction and normalization layer between heterogeneous hospital document exchange networks and modern HL7 FHIR Release 4 (R4) applications.

What Role Does Health Gorilla Play as a Designated TEFCA QHIN?

Under the 21st Century Cures Act, the Office of the National Coordinator for Health Information Technology (ASTP/ONC) and its Recognized Coordinating Entity (The Sequoia Project) established the Trusted Exchange Framework and Common Agreement (TEFCA) to connect disparate health information networks across the United States. Health Gorilla is designated as an operational TEFCA QHIN, serving as a direct gateway node on the national interoperability backbone.

By connecting to Health Gorilla as a Participant or Subparticipant, healthcare delivery organizations, life sciences platforms, and patient-facing applications gain unified connectivity across:

• TEFCA QHIN-to-QHIN Exchange: Nationwide queries across all other designated QHINs under standard TEFCA Exchange Purposes (including Treatment, Individual Access Services [IAS], Payment, Health Care Operations, Public Health, and Government Benefits Determination);
• Legacy & Partner Frameworks: Interconnected document query routing across Carequality, CommonWell Health Alliance, eHealth Exchange, and state/regional Health Information Exchanges (HIEs); and
• National Diagnostic Laboratory & Imaging Vendors: Bi-directional electronic laboratory ordering (`ServiceRequest`) and structured result ingestion (`DiagnosticReport` and `Observation`) with major reference and specialty laboratories.

How Does the Health Gorilla API Aggregate Patient Clinical Records?

Querying nationwide health networks directly requires managing complex SOAP-based Integrating the Healthcare Enterprise (IHE) profiles—specifically IHE XCPD (Cross-Community Patient Discovery), IHE XCA (Cross-Community Access), and SAML XUA security assertions. The Health Gorilla API encapsulates these underlying IHE transactions behind a single OAuth 2.0–secured RESTful FHIR R4 interface:

1. Tenant Patient Registration & MPI Matching: The consuming system registers or looks up the patient using verified demographics (legal name, date of birth, sex, residential address, phone number, and optional identifiers) to generate a unique Health Gorilla Patient ID.
2. Asynchronous Network Query ($p360-retrieve): Invoking the FHIR Patient/$p360-retrieve operation initiates federated patient discovery and document retrieval across connected TEFCA, Carequality, and CommonWell endpoints based on geographic proximity and prior care locations.
3. Webhook Event Notification: Because external hospital EHR gateways respond asynchronously over seconds or minutes, Health Gorilla emits FHIR `Subscription` webhook notifications as external clinical documents are retrieved, parsed, and indexed into the patient’s longitudinal record.

How Does Health Gorilla Normalize C-CDA Documents Into FHIR R4 Resources?

Although modern APIs rely on JSON-formatted FHIR resources, the majority of cross-enterprise hospital exchanges over TEFCA and Carequality transmit clinical records as HL7 Consolidated Clinical Document Architecture (C-CDA R2.1) Continuity of Care Documents (CCDs) encoded in XML. A single chronically ill patient may have dozens of overlapping C-CDA XML files returned from different health systems, each containing redundant problem lists, historical medications, and inconsistently coded lab results.

Health Gorilla’s Patient360 data pipeline transforms these raw C-CDA XML payloads into clean, queryable US Core HL7 FHIR R4 resources through four processing stages:

Pipeline Stage	Technical Transformation Performed by Patient360	Output FHIR R4 Resource / Element
1. C-CDA XML Section Parsing	Extracts discrete entries from C-CDA structured body templates (Problems, Medications, Allergies, Results, Vital Signs, Immunizations, Procedures, Encounters, and Social History).	Preserves raw XML and PDF artifacts via DocumentReference and Binary while generating discrete resource instances.
2. Terminology Uplift & Coding Normalization	Maps local, deprecated, or non-standard codes inside C-CDA `translation` elements to canonical standard vocabularies (SNOMED CT, ICD-10-CM, LOINC, RxNorm, NDC, and CVX).	Populates standardized CodeableConcept.coding arrays across Condition, Observation, and MedicationStatement.
3. Cross-Source Deduplication	Identifies identical diagnoses, immunizations, allergies, or laboratory results reported across multiple hospital CCDs and merges duplicate records into a single longitudinal resource.	Maintains consolidated active clinical lists while linking back to each contributing source document via Provenance.
4. USCDI & US Core FHIR Exposure	Exposes the harmonized longitudinal record through standard RESTful FHIR R4 search parameters (`GET /fhir/Condition?patient=…`, `GET /fhir/Observation?patient=…&category=laboratory`) and FHIR Bundles.	Patient, Condition, Observation, MedicationRequest, AllergyIntolerance, Immunization, Procedure, DiagnosticReport, Encounter.

Clinical Research and Decentralized Trial Workflows

In observational registries, real-world evidence (RWE) cohorts, and decentralized clinical trials (DCTs), Health Gorilla’s Individual Access Services (IAS) and patient-authorized record retrieval pathways allow study participants to consent electronically and pull their longitudinal medical records from any participating U.S. hospital or clinic. Rather than waiting weeks for manual medical record release requests or faxed chart abstractions, clinical data management pipelines ingest normalized FHIR R4 bundles directly into electronic data capture (EDC) or OMOP Common Data Model repositories with full document-level provenance.

Sources

• Health Gorilla, Inc. Developer Portal: Patient360 API, C-CDA to FHIR R4 Normalization, and Diagnostic Network Documentation. https://developer.healthgorilla.com/
• The Sequoia Project (ONC TEFCA Recognized Coordinating Entity). Qualified Health Information Network (QHIN) Directory & Common Agreement Specifications. https://rce.sequoiaproject.org/qhin-directory/
• Health Gorilla, Inc. TEFCA QHIN Interoperability & Clinical Data Exchange Overview. https://www.healthgorilla.com/