Elation Health integration guide
How to connect HealthArc to Elation
Elation integrations run in two stages. Your practice requests developer access and completes Elation’s onboarding, HealthArc tests in Elation’s sandbox, and then your practice authorizes production data sharing so Elation can issue production credentials.
At a glance
The Elation Health integration in six lines
| Connection type | Elation FHIR R4 APIs with SMART on FHIR (OAuth 2.0) |
|---|---|
| Where it runs | Cloud to cloud. Nothing to install on your servers or workstations |
| Who approves it | Elation reviews and registers the application |
| Environments | Sandbox first, then production with separate credentials |
| Practice authorization | Written data-sharing authorization before production access |
| Security | HIPAA compliant, SOC 2 compliant, BAA signed before any data moves |
Data flow
What moves between Elation and HealthArc
From Elation into HealthArc
- Patient demographics and contact details
- Problem list and diagnoses (ICD-10)
- Active medications and allergies
- Appointments and encounters
- Providers and locations
- Vitals and lab results, where available
From HealthArc back to Elation
- Care-management notes and documents, where Elation’s access for your practice allows write-back
- Write-back scope confirmed in writing during scoping
Exact fields depend on your Elation configuration and the programs you run, and are confirmed in writing during scoping. HealthArc only requests the data those programs need.
Before you start
What you need in place
None of this needs an IT team. Most of it is a decision or a name, and the scoping call covers anything you haven’t settled yet.
- An active Elation Health account
- Administrator access to your Elation practice
- Permission to request API access
- A designated technical or implementation contact
- A signed HealthArc agreement and business associate agreement
Your time investment4–8 hours
Total time from your team, across the whole setup. HealthArc does the build.
Where your time goes
- Scoping call
- Authorizing HealthArc in Elation
- Approving the mapping
- Reviewing the pilot
No IT team neededLive in about 30 days
Setup steps
7 steps from first call to go-live
Most practices are monitoring patients within about 30 days of signing.
- 1Practice + HealthArc
Agreements and scoping
We confirm the programs you want to run, the providers and locations involved, and who owns clinical work and billing on your side. The HealthArc agreement and business associate agreement are signed before any data moves.
- 2Practice contact
Submit Elation’s developer request form
Complete Elation’s Developer Sandbox / Partnership form. In the description, say you’re requesting FHIR API access for integration with the HealthArc platform.
- First and last name
- Organization name
- Email address and phone number
- Practice information
- Description of the requested integration
- Acceptance of the Elation Health API and Usage Agreement
Elation’s developer request form. Choose the API access you need and accept the Elation Health API and Usage Agreement. - 3Practice + HealthArc
Complete Elation’s API onboarding
An Elation representative contacts you and reviews the application before registering it. You may be asked for:
- Application name
- Application type: backend, confidential or public
- Redirect URIs, if applicable
- Logo URL (optional)
- 4Practice contact
Receive sandbox credentials and share them
Once approved, Elation registers the application in its sandbox. Share these securely with your HealthArc implementation team:
- Client ID
- Client Secret (confidential applications only)
- Sandbox base URL
- Application name
- 5HealthArc
HealthArc tests in the sandbox
We configure the connection and test it against Elation’s sandbox, with no production patient data involved.
- 6Practice contact
Request production access and authorize data sharing
After sandbox testing, request production registration from Elation and give written authorization for data sharing. Elation reviews it and issues new production credentials; sandbox credentials don’t work in production.
- Additional API fees may apply, depending on your agreement with Elation
- 7HealthArc + practice
HealthArc configures, tests and goes live
Once we have access, our implementation team configures the Elation connection, validates authentication and data access, maps providers and locations, and tests with a small pilot group. Your Customer Success Manager confirms when the integration is complete, and we train your team before enrollment opens.
Who does what
Your team and ours
| Task | Your practice | HealthArc |
|---|---|---|
| Submit the developer request and onboarding details | Yes | Yes |
| Share sandbox and production credentials | Yes | – |
| Sandbox testing | – | Yes |
| Written data-sharing authorization | Yes | – |
| Production configuration and testing | – | Yes |
| Staff training | – | Yes |
| Ongoing monitoring and support | – | Yes |
Security
How patient data is protected
BAA first
A business associate agreement is signed before any patient data moves.
Encrypted
Databases are encrypted at rest, and data in transit uses TLS only.
SOC 2 and HIPAA
HealthArc’s security program follows the SOC 2 framework, and the platform is HIPAA compliant.
U.S. hosting
Data is stored on AWS in the United States.
Full details are on the HealthArc security page.
FAQ
Elation Health integration questions
How do I connect HealthArc to Elation?
Submit Elation’s developer sandbox / partnership form asking for FHIR API access for HealthArc, complete Elation’s onboarding, share the sandbox credentials with HealthArc for testing, then request production registration and give Elation written authorization for data sharing.
What credentials does HealthArc need?
The application name, Client ID, Client Secret (for confidential applications) and the sandbox base URL, then the production base URL and production credentials after go-live approval.
Does submitting the form give us API access?
No. Elation reviews each application before issuing credentials, and production credentials are only issued after sandbox testing and practice authorization.
Does Elation charge API fees?
Additional API fees may apply depending on your practice’s agreement with Elation.
Can sandbox credentials be used in production?
No. Elation issues separate production credentials after testing.
Ready to connect Elation?
Book a scoping call. You’ll leave with a written implementation plan for your practice, your programs and your go-live date.
Elation and Elation Health are trademarks of Elation Health, Inc. HealthArc is an independent company.