AdvancedMD integration guide
How to connect HealthArc to AdvancedMD
Your administrator creates an application, asks AdvancedMD Interoperability to approve it, and shares four details with us: Office Key, application name, Client Key and Client Secret. We configure and test the rest. Write-back is optional and needs AdvancedMD’s Partner (Connect) API.
At a glance
The AdvancedMD integration in six lines
| Connection type | AdvancedMD FHIR APIs (FHIR Single Patient API or FHIR Bulk API) |
|---|---|
| Where it runs | Cloud to cloud. Nothing to install on your servers or workstations |
| Who approves it | AdvancedMD Interoperability, after your administrator’s request |
| Direction | Read from AdvancedMD by default. Write-back needs Partner (Connect) API access |
| What we need | Office Key, application name, Client Key, Client Secret |
| Security | HIPAA compliant, SOC 2 compliant, BAA signed before any data moves |
Data flow
What moves between AdvancedMD and HealthArc
From AdvancedMD 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 AdvancedMD
- Nothing by default: standard AdvancedMD FHIR access is read-only
- With Partner (Connect) API access: care-management documents and reports uploaded to the chart
- Write-back scope agreed with you and AdvancedMD during scoping
Exact fields depend on your AdvancedMD 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 AdvancedMD account
- Administrator access to your AdvancedMD environment
- Permission to create applications in the AdvancedMD FHIR Developer Portal
- Your AdvancedMD Office Key
- Access to submit requests to AdvancedMD Interoperability support
- 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 AdvancedMD
- 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 administrator
Create the application
In the AdvancedMD FHIR Developer Portal, create an application for the HealthArc integration. Request one FHIR API product per application: FHIR Single Patient API or FHIR Bulk API.
AdvancedMD FHIR getting started - 3Practice administrator
Request approval from AdvancedMD Interoperability
Open a support request using the FHIR/API Support option and include:
- Your AdvancedMD Office Key
- The application name
- A request to authorize the application for the HealthArc integration
- Anything else AdvancedMD asks for
AdvancedMD’s interoperability support form. Choose the API or FHIR support option. - 4AdvancedMD
AdvancedMD approves the application
The AdvancedMD Interoperability team reviews the request and enables the requested API product for your application.
- 5Practice administrator
Send the credentials to HealthArc
Share these securely with your HealthArc implementation team:
- Client Key
- Client Secret
- Office Key
- Application name
- 6Practice + HealthArc + AdvancedMD
Add document write-back (optional)
If you want HealthArc to upload documents or reports into AdvancedMD, we work with you and AdvancedMD Interoperability on Partner (Connect) API services and credentials.
- 7HealthArc + practice
HealthArc configures, tests and goes live
Once we have access, our implementation team configures the AdvancedMD 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 |
|---|---|---|
| Create the application and request approval | Yes | – |
| Approve the application | – | – |
| Share credentials securely | Yes | – |
| Arrange Partner (Connect) API write-back | Yes | 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
AdvancedMD integration questions
How do I connect HealthArc to AdvancedMD?
Create an application in the AdvancedMD FHIR Developer Portal, submit a FHIR/API Support request to AdvancedMD Interoperability with your Office Key and application name, wait for approval, then send HealthArc the Client Key, Client Secret, Office Key and application name. HealthArc configures and tests the connection.
Should we request the FHIR Single Patient API or the FHIR Bulk API?
Each application requests one product. We recommend which one during scoping, based on how many patients you’ll enroll and how data should sync.
Can HealthArc write back to AdvancedMD?
Only with additional access. AdvancedMD’s standard FHIR APIs are read-only. Writing documents or reports back needs Partner (Connect) API access approved by AdvancedMD Interoperability.
Who approves the application?
AdvancedMD’s Interoperability team. Administrator permissions are needed on your side to create the application and submit the request.
Where can our IT team read more?
AdvancedMD’s FHIR documentation at fhir.advancedmd.com covers the developer portal and API products.
Ready to connect AdvancedMD?
Book a scoping call. You’ll leave with a written implementation plan for your practice, your programs and your go-live date.
AdvancedMD is a trademark of AdvancedMD, Inc. HealthArc is an independent company.