AdvancedMD's Interoperability Solutions: Overview
AdvancedMD supports a variety of interoperability solutions to help both third-party developer partners and our own clients—collectively referred to here as "developers"—build custom applications and connect mission-critical systems to the AdvancedMD platform. This page provides an overview of the integration technologies we offer, how to get started, and how to request support.
Connect APIs (Partner APIs)
AdvancedMD offers a comprehensive set of proprietary APIs, known as the Connect APIs, that allow developers to build applications that replicate nearly all functionality available within the AdvancedMD user interface.
These APIs are available in both XML-RPC and REST formats.
Common Use Cases:
Patient engagement applications
Appointment scheduling
Custom clinical forms
Patient payment and responsibility tools
Revenue cycle management (RCM)
Clinical decision support
Many other real-time workflow integrations
Recommended For:
Developers seeking real-time, transactional access to AdvancedMD data, where data exchange needs to happen as users interact with the platform—rather than in large, infrequent batches.
Our API Development Philosophy:
AdvancedMD is an API-first company. As we develop new features and enhancements within our core platform, we simultaneously publish and maintain corresponding APIs. This ensures that our developer community always has access to the latest capabilities and can extend the platform in real-time.
Access Requirements:
Developers must sign a Certified API Developer Agreement, which includes associated licensing and support fees.
Upon execution of the agreement, developers are granted access to full API documentation and a sandbox environment to begin building and testing their integrations.
After a successful demonstration of the integration with our Interoperability (InterOps) team, the developer will receive production credentials, including a unique appname, for use in the live environment.
Contact AdvancedMD Sales to learn more about becoming a Certified API Developer.
ODBC Access for Bulk Data
For developers and organizations that need to pull down large volumes of data—such as for building data warehouses, running advanced analytics, or meeting unique regulatory reporting requirements—AdvancedMD provides access via a custom ODBC driver.
How It Works:
Developers can use SQL queries via ODBC to extract client data directly from AdvancedMD systems.
The driver includes a library of prebuilt SQL scripts to perform initial full-data extractions and subsequent delta loads to maintain up-to-date backups.
Recommended For:
Organizations familiar with SQL databases and DBA best practices
Use cases requiring offline access to client data or custom reporting environments
Developers with infrastructure capable of securely storing and maintaining large data sets
Contact AdvancedMD Sales for access to our ODBC offering and licensing details.
FHIR APIs (Regulatory APIs)
In alignment with U.S. federal healthcare IT regulations, AdvancedMD supports FHIR R4-based APIs as part of its Certified EHR Technology (CEHRT) status.
Regulatory Background:
In 2020, the ONC Cures Act Final Rule introduced requirements for standardized APIs under 45 CFR § 170.315(g)(10).
These APIs must follow HL7® FHIR® Specification Release 4 and expose data defined in the US Core Data for Interoperability (USCDI) standard.
The purpose is to enable secure and standardized access to clinical information by patients and third-party applications.
Notes on FHIR:
Our FHIR APIs are read-only, supporting only GET requests, in accordance with (g)(10) regulations.
Access is granted via SMART on FHIR OAuth 2.0 authorization flows, enabling patient-facing and provider-facing apps.
These APIs are ideal for apps that allow patients or providers to view and interact with clinical data, including medication lists, allergies, vitals, and more.
Note: If your application requires full create, read, update, and delete (CRUD) functionality, you will need to use the Connect APIs rather than FHIR.
Currently, the FHIR APIs are provided at no cost, and documentation is available on our FHIR Developer Portal.
HIE Integrations
AdvancedMD offers connectivity with a number of state and regional Health Information Exchanges (HIEs) to facilitate clinical document exchange and real-time patient information sharing.
Our HIE integrations include outbound CCDA and optional outbound ADT support.
How to Request an HIE Integration:
Visit the Interoperability Support Request form
Use the subject line: “HIE Discovery Call”
In the request, include the following:
Client office key (if applicable)
Client point-of-contact information
HIE vendor name
Contact information for a representative at the HIE
Our InterOps team will review the request, coordinate an initial discovery call with the HIE, and advise on next steps.
Clients should also contact AdvancedMD Sales for HIE connectivity pricing.
Orders & Results Interfaces (Labs, Imaging, etc.)
AdvancedMD supports electronic orders and results delivery for most major laboratories and radiology providers in the U.S.
Integration Model:
Rather than building one-off integrations with individual labs or imaging centers, AdvancedMD works through trusted integration partners who maintain and support hundreds of interfaces on our behalf.
If your organization is a lab, radiology center, or diagnostic service looking to integrate with AdvancedMD, we recommend reaching out to one of the following partners:
HL7 2.x Messaging
AdvancedMD does not directly support custom HL7 2.x messaging interfaces for external developers. However, integration partners can assist in translating HL7 messages to and from our supported APIs, allowing for seamless bidirectional communication.
For HL7 2.x integrations, we recommend contacting one of our preferred partners:
Developer Support
Need help? We're here to assist.
Visit our FAQ page for answers to the most common developer questions.
For additional support, submit a request through our Support Form, and a member of our team will respond as soon as possible.