Overview
HealthArc integrates with Elation using the FHIR R4 APIs and SMART on FHIR OAuth 2.0 authentication. Before production access can be granted, your application must be registered with Elation and approved as an authorized developer.
Prerequisites
Before beginning the integration, ensure you have:
An active Elation Health account
Administrative access to your Elation practice
Permission to request API access
A designated technical or implementation contact
Part 1 – Request Developer Access
Step 1 – Complete the Developer Registration Form
Open the Elation Developer registration page:
Developer Sandbox / Partnership Request
Complete the registration form with:
First Name
Last Name
Organization Name
Email Address
Phone Number
Practice Information
Description of the requested integration
In the description, specify that you are requesting:
FHIR API access for integration with the HealthArc platform.
Submit the form.
An Elation representative will contact you regarding the next steps.
Step 2 – Complete the API Onboarding Process
After receiving your request, Elation will begin the developer onboarding process.
You may be asked to provide:
Application Name
Application Type
Backend
Confidential
Public
Redirect URI(s) (if applicable)
Logo URL (optional)
An Elation representative will review your application before registration.
Part 2 – Sandbox Registration
Step 3 – Receive Sandbox Credentials
Once your application has been approved, Elation will register it in the Sandbox Environment.
You will receive:
Client ID
Client Secret (for confidential applications)
Sandbox API access
These credentials allow HealthArc to begin integration testing without using production patient data.
Step 4 – Sandbox API Endpoints
The Elation Sandbox uses the following endpoints:
SMART Configuration
https://sandbox.fhir.elationemr.com/fhir/.well-known/smart-configuration
FHIR API Endpoint
https://sandbox.fhir.elationemr.com/fhir
FHIR Base URL
https://sandbox.fhir.elationemr.com/fhir/fhir-base-url
These URLs will be used by HealthArc during implementation.
Part 3 – Provide Information to HealthArc
Step 5 – Share Your Integration Credentials
Provide the following information securely to the HealthArc Implementation Team:
Client ID
Client Secret (if applicable)
Sandbox Base URL
Application Name
HealthArc will use these credentials to configure the integration and validate connectivity.
Part 4 – Production Access
Step 6 – Request Production Registration
Once sandbox testing has been successfully completed, request production registration from Elation.
The Elation team will:
Register your application in Production
Issue new production credentials
Enable access after receiving practice authorization
Important: Sandbox credentials cannot be used in Production. Production credentials are issued separately.
Step 7 – Practice Data Sharing Authorization
Before HealthArc can access production patient data:
The Elation practice must provide written authorization for data sharing.
Elation will review the request and enable production access.
Additional API fees may apply depending on the practice's agreement with Elation.
Part 5 – HealthArc Configuration
Step 8 – HealthArc Completes the Integration
After receiving the production credentials, the HealthArc implementation team will:
Configure the Elation connection.
Authenticate using OAuth 2.0.
Validate FHIR API connectivity.
Verify patient data synchronization.
Complete end-to-end testing.
Confirm successful integration.
Your Customer Success Manager will notify you once the integration has been completed.
Information Required by HealthArc
Information | Required |
Application Name | ✓ |
Client ID | ✓ |
Client Secret (if applicable) | ✓ |
Sandbox Base URL | ✓ |
Production Base URL (after go-live) | ✓ |
Environment URLs
Environment | FHIR Base URL |
Sandbox |
|
Production |
|
Important Notes
Registering through the developer form does not immediately grant API access. Elation reviews each application before issuing credentials.
Sandbox and Production use different credentials. Production credentials are issued only after sandbox testing and practice authorization.
Client Secrets are issued only for Confidential applications. Public applications receive only a Client ID.
Production access requires explicit consent from the practice whose data will be accessed.
Refer to Elation support article for more information on Elation FHIR API