Environments
Health Gorilla provides two environments for API usage: Sandbox and Production. Each environment has a distinct purpose, URL structure, and data model. You must use the correct base URL and configuration based on your development stage and FHIR version.
Sandbox Environment
Use the Sandbox for development, testing, and validation. It simulates real-world workflows using synthetic patient data. The Sandbox supports the full FHIR API, web interface, and simulated diagnostic exchanges. Patient records created in the Sandbox are pre-populated with mock clinical data and test scenarios.
- Diagnostic orders trigger simulated lab results
- Webhook notifications use test endpoints
- No real messages, emails, or external data are sent
To request access, contact Health Gorilla Support. The Sandbox environment must be manually enabled for your organization.
Production Environment
The Production environment connects to live networks, providers, and data sources. It supports real-time patient record retrieval, diagnostics, and clinical alerting.
- Access is gated by tenant approval and IP allowlisting
- Webhooks deliver to live endpoints
- Production data is subject to rate limits and licensing
Contact Health Gorilla Support to configure Production access, request allowlist changes, or manage credentials.
Base URLs by Environment and Version
Use the correct base URL for your environment and FHIR version. Do not mix FHIR versions within a single implementation.
| Environment | FHIR R4 Base URL | FHIR STU3 Base URL |
|---|---|---|
| Sandbox | https://sandbox.healthgorilla.com/fhir/R4 | https://sandbox.healthgorilla.com/fhir/3.0.1 |
| Production | https://api.healthgorilla.com/fhir/R4 | https://api.healthgorilla.com/fhir/3.0.1 |
Environment Differences
| Feature | Sandbox | Production |
|---|---|---|
| Data type | Synthetic test data | Live clinical data |
| API rate limits | Relaxed | Enforced by contract |
| Webhooks | Test endpoints only | Live delivery |
| Licensing | Enabled by Support | Requires active license |
| Network access | Simulated responses | Real-time HIE and lab data |
FHIR Version Support
FHIR R4 is used for all new implementations. FHIR STU3 is supported for legacy use cases such as $p360-retrieve. Each version supports a distinct resource set and processing logic.
Note: All API requests must include a valid OAuth 2.0 bearer token in the Authorization header. Tokens are environment-specific, so ensure you authenticate against the correct base URL using the corresponding credentials.