Data Contribution

Organizations connected to Health Gorilla both retrieve and contribute clinical data as part of nationwide interoperability. Data contribution supports reciprocal exchange, enables continuity of care, and helps organizations meet applicable federal and framework-specific participation requirements.

All contributed data is processed through the same platform-level validation, normalization, and routing workflows used for record retrieval, ensuring consistent handling regardless of direction.

Why Contribution Matters

Nationwide exchange frameworks are built on reciprocity. Organizations that retrieve external records are generally expected to share clinically meaningful data in return, subject to their participation model and technical capabilities.

By contributing data through Health Gorilla, your organization:

• Strengthens continuity of care for shared patients
• Enriches longitudinal patient records across participating networks
• Supports compliance with the Trusted Exchange Framework and Common Agreement (TEFCA), the Health Insurance Portability and Accountability Act (HIPAA), Centers for Medicare & Medicaid Services (CMS) interoperability rules, and applicable participation agreements
• Reduces fragmentation by sharing data through standardized exchange pathways

Where reciprocity policies apply, the ability to retrieve records may depend on meeting contribution obligations defined by the governing framework.

Shareback Expectations

Contribution requirements vary based on organizational role and participation model.

Health Gorilla enforces applicable contribution requirements based on tenant configuration, framework rules, and contractual obligations.

Contribution Methods

Health Gorilla supports multiple methods for contributing clinical data, allowing organizations to align exchange with existing systems and workflows.

Supported approaches include:

• FHIR write operations: Post supported FHIR resources directly to the API, including Patient, Encounter, DocumentReference, Observation, Immunization, and MedicationRequest, when enabled for your tenant.

• Structured document submission: Upload documents such as C-CDAs. Where supported, Health Gorilla parses submitted documents and converts structured content into FHIR resources for downstream exchange.

Contribution capabilities depend on tenant provisioning, assigned OAuth 2.0 scopes, and applicable exchange framework rules.

Responder-Only Participation

Some organizations contribute data without initiating outbound record retrievals. Health Gorilla supports responder-only participation models where permitted by governing frameworks and participation agreements.

Responder-only participation may be implemented using:

• Health Gorilla data repository: Contributed data is stored in the Health Gorilla FHIR core and made available to authorized external queries through participating networks.

• Federated access: Data remains in your system, and Health Gorilla queries it in place when supported inbound requests are received.

Responder-only configurations restrict outbound retrieval capabilities while preserving full auditability and compliance with network requirements. Participation is evaluated independently for each network, so an organization can be responder-only in one network while retrieving and contributing normally in another.

Data Processing and Handling

All contributed data is subject to platform-level processing to ensure quality, consistency, and trust.

Health Gorilla applies the following controls:

• Validation against applicable FHIR profiles and supported vocabularies where relevant
• Normalization into consistent resource structures
• Provenance tagging to identify original data sources
• Routing to participating networks according to the rules of each framework

These steps help ensure that contributed data is usable, traceable, and exchanged in accordance with national interoperability standards.