Veradigm integration guide
How to connect HealthArc to Veradigm
Your practice submits Veradigm’s Partner Request form naming HealthArc, Veradigm provisions the application and issues credentials, and you share them with our team. HealthArc configures and tests the connection from there.
At a glance
The Veradigm integration in six lines
| Connection type | Veradigm FHIR R4 APIs with OAuth 2.0 |
|---|---|
| Where it runs | Cloud to cloud. Nothing to install on your servers or workstations |
| Application name | HealthArc |
| Who approves it | Veradigm reviews and provisions each request |
| What we need | Practice ID, Client ID, Client Secret, practice name and any endpoints Veradigm supplies |
| Security | HIPAA compliant, SOC 2 compliant, BAA signed before any data moves |
Data flow
What moves between Veradigm and HealthArc
From Veradigm 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 Veradigm
- Care-management notes and documents, where Veradigm’s access for your practice allows write-back
- Write-back scope confirmed in writing during scoping
Exact fields depend on your Veradigm 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 Veradigm Practice Fusion or Veradigm EHR account
- Administrator access to your Veradigm environment
- Permission to request API access
- Your practice information for onboarding
- 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 Veradigm
- Approving the mapping
- Reviewing the pilot
No IT team neededLive in about 30 days
Setup steps
6 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 administrator
Submit Veradigm’s Partner Request form
Complete the Partner Request form in the Veradigm Developer Portal with your organization and contact details. When asked for integration details, enter:
- Application Name: HealthArc
- API Type: FHIR R4
- Integration Purpose: HealthArc EHR Integration
- 3Veradigm
Veradigm reviews and provisions the application
Veradigm’s onboarding team reviews the request, registers HealthArc for your practice, provisions API access and sends OAuth credentials with onboarding instructions. The review may include verifying the practice and the intended use.
- 4Practice administrator
Send the credentials to HealthArc
Share these securely with your HealthArc implementation team:
- Practice ID
- Client ID
- Client Secret
- Practice name
- Any environment-specific API endpoints Veradigm supplied
- 5Practice administrator
Authorize HealthArc
If your Veradigm environment asks for it, approve HealthArc’s access to your practice data. This lets HealthArc retrieve the approved clinical information over OAuth 2.0.
- 6HealthArc + practice
HealthArc configures, tests and goes live
Once we have access, our implementation team configures the Veradigm 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 Partner Request | Yes | – |
| Provision the application | – | – |
| Share credentials securely | Yes | – |
| Authorize access (if required) | Yes | – |
| Technical build, mapping 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
Veradigm integration questions
How do I connect HealthArc to Veradigm?
Submit Veradigm’s Partner Request form naming HealthArc as the application and FHIR R4 as the API type, wait for Veradigm to provision access, send HealthArc the practice ID, Client ID and Client Secret, and authorize access if Veradigm asks.
Can we email Veradigm instead of using the form?
Yes. Email Veradigm Connect at veradigmconnect@veradigm.com with the subject “Request for Veradigm FHIR Integration with HealthArc”, and include your practice and organization names, contact name and email, practice location, the requested integration, HealthArc as the application name and FHIR R4 as the API.
Is API access enabled as soon as we submit the request?
No. Veradigm reviews and provisions each request before issuing credentials, and HealthArc can’t configure the integration until those credentials exist.
What does HealthArc need from us?
Your practice ID, Client ID, Client Secret and practice name, plus any FHIR base URL or OAuth endpoints Veradigm provides.
Does this cover Practice Fusion?
Yes. The process applies to Veradigm EHR and Veradigm Practice Fusion accounts.
Ready to connect Veradigm?
Book a scoping call. You’ll leave with a written implementation plan for your practice, your programs and your go-live date.
Veradigm and Practice Fusion are trademarks of Veradigm. HealthArc is an independent company.