Standards
Health Gorilla returns clinical data as structured FHIR R4 resources that follow nationally recognized medical vocabularies. Incoming records are normalized during processing so applications can store, display, and reuse data without custom transformations or mapping logic.
Clinical Code Systems
Each FHIR resource contains structured code elements—code, coding, or codeableConcept—that identify clinical concepts in a computable format, and values conform to the US Core Implementation Guide or HL7 FHIR specification. They use established code systems, including:
- LOINC®: Laboratory tests, vital signs, and document types
- SNOMED CT®: Conditions, procedures, allergies, and clinical findings
- RxNorm: Medications, ingredient names, and dosage forms
- ICD-10-CM and CPT: Diagnosis and procedure codes, where required by source systems
USCDI Alignment
All data returned through Health Gorilla’s FHIR APIs conforms to the United States Core Data for Interoperability (USCDI) and HL7 FHIR R4 standards. Data classes include allergies and intolerances, medications and immunizations, conditions and procedures, laboratory results, vital signs, clinical notes, and care plans.
Records are automatically returned based on what connected networks supply; no additional configuration or specialized queries are required.
Resource Metadata
FHIR resources include metadata that supports provenance, versioning, and workflow context.
Key elements include:
meta.profile: Identifies the applied FHIR or US Core conformance profilemeta.tagandmeta.security: Control routing, visibility, and contextual filteringstatus,category, andcode: Define workflow state and clinical meaning
These fields enable traceability, security enforcement, and accurate presentation in downstream systems.
Interoperability Frameworks
Health Gorilla operates in full compliance with national interoperability frameworks—including Carequality, CommonWell, eHealth Exchange, and TEFCA.
The platform manages record-locator logic, patient matching, query formatting, and audit logging across these networks, eliminating the need for clients to maintain separate trust agreements or implement framework-specific standards.