athenahealth integration services for apps, portals, RPM and CRM
We connect patient apps, portals, remote monitoring tools and CRMs to athenahealth, and we have shipped athenahealth integrations. We start from the standards a certified EHR must support, FHIR R4 with US Core and SMART on FHIR, and add vendor-specific APIs only where your workflow needs them. The practice that uses athenahealth decides what your app may read and write, so its approval is part of the plan from the start.

What does integrating with athenahealth involve?
Integrating with athenahealth means your product reads or writes data in a practice's athenahealth environment through the APIs athenahealth exposes, with the practice's permission. For a patient app, that might mean showing medications and lab results. For a CRM, it might mean keeping patient and referral records in sync. For an RPM tool, it usually means filing readings where clinicians will see them.
Where the athenahealth product your customer runs is certified to ONC's §170.315(g)(10) criterion, it must offer a FHIR R4 API with US Core, SMART App Launch for authorization, and Bulk Data for groups of patients, with complete documentation available at a public link. That gives you a standards-based floor. We confirm which product and version your customer runs before we rely on it.
athenahealth sets its own developer terms, onboarding steps and any fees, and they change over time, so we read the current documentation with you during the audit.
Which workflows fit an athenahealth integration?
The ones we see most often are patient-facing apps and portals that read the record, scheduling and intake flows, remote monitoring products that file readings, and CRMs or care coordination tools that need patient, provider and referral data.
Each has a different read and write profile. A read-only patient app is the simplest to approve. Anything that books, files or updates data needs a specific API for each action and a decision by the practice about where the data goes and who reviews it.
We write this profile down per feature during the audit. It is the document the practice's reviewers will ask for anyway.
What can you read, and what needs the practice's approval?
Reads through FHIR R4 and US Core are the predictable part: problems, medications, allergies, labs, vitals and other USCDI data, within the scopes your app is granted. SMART App Launch defines those permissions as scopes, such as a scope that lets an app read and search a user's encounters, so a reviewer can see exactly what you ask for.
Writes depend on what the vendor exposes for that action and on what the practice enables. Plan them one by one, and design for the case where a write fails or is delayed.
Patients keep control, too. Under §170.315(g)(10), a certified authorization server must be able to revoke an app's access at a patient's direction within one hour, and for confidential apps it must issue refresh tokens valid for at least three months. Your app has to handle both.
What do we need from you to start?
A sponsoring practice or health system that runs athenahealth, with an administrator who can approve access and a clinical or operations sponsor who wants the workflow. You can build against a test environment first, but you cannot go live without one.
Access to your athenahealth developer account, or agreement that we set one up in your company's name, so credentials and keys stay with you after the project.
A signed BAA before we touch PHI, the list of features in the first release, and one person on your side who answers the practice's questions.
What drives the timeline and cost of an athenahealth integration?
We do not publish a price, because the drivers differ by project. The main ones are the number of distinct reads and writes, whether the standard FHIR APIs cover your data or you need vendor-specific ones, how many practices you are rolling out to, and how each practice's setup differs.
The practice's schedule sets much of the pace. Its administrators approve access alongside their regular work, and a security questionnaire can add questions about hosting, logging and every other service that touches the data.
The audit report turns these into a dated plan for your project, with the waiting points marked.
What are the risks, and how do we reduce them?
Building on vendor-specific APIs where a standard one would do. It ties your product more tightly to one vendor. We start from FHIR R4 and US Core and use anything else only for the gaps.
Testing only with sample data. Each practice configures its environment differently, so we plan time to test with the customer before launch.
Writes that fail silently. We design queues, retries and clear messages so a reading or update that has not reached the care team never looks as if it has.
Security gaps found late. We sign a BAA before PHI, scope access so each clinician sees only their own patients, and run a penetration test before launch.
How we run a athenahealth integration
- 1
5-day free technical audit
We read your product, your data flows and the vendor's current documentation, then list every read and write your features need and the API or interface that serves each one. You get a written report, whether or not you hire us.
- 2
Scope and dated plan
From the report we agree the scope, the order of work and a plan with dates, including the points where we wait on the vendor or your customer. We sign a BAA before any PHI is in reach.
- 3
Build in the vendor sandbox
We build against a test environment with test data, starting with the reads and then each write. For any part of athenahealth's platform we work from its documentation and sandbox.
- 4
Testing
We test sign-in, token refresh, revocation and each read and write, then repeat the main flows with the sponsoring practice before launch.
- 5
Go-live with a penetration test
Before launch we run a penetration test and fix what it finds, then go live with the customer and watch the first days of real traffic. Access is scoped so each clinician sees only their own patients.
athenahealth integration questions
1Have you shipped athenahealth integrations?
Yes, we have shipped athenahealth integrations. We do not publish client names or project details. For any part of athenahealth's platform, including APIs we have not used before, we work from its documentation and sandbox, and the audit report tells you what we found for your use case before you commit.
2Do we need an agreement with athenahealth?
That depends on athenahealth's current developer terms and on the APIs and distribution your product needs, and those terms are athenahealth's to set. We read them with you during the audit and list in the report which agreements you would need, with athenahealth and with each practice.
3Should we use FHIR or athenahealth-specific APIs?
Start with FHIR R4 and US Core wherever they cover your data. They are the same standards other certified EHRs support, which makes your next integration cheaper. Use vendor-specific APIs only for the actions the standard ones do not cover, and keep that code behind one clear interface in your product.
4Can our RPM app write readings into athenahealth?
It depends on the API available for that data and on what the practice enables. We find the specific API for each write, agree with the practice where the readings land and who reviews them, and design the app so patients and staff can see when a reading has not been filed yet.
5Can we start before a practice signs up?
Yes. We can build and test against a test environment first, so your team can demo a working connection. Going live needs a practice that approves your app and grants access in its production environment.
6How much does an athenahealth integration cost?
We do not quote a number without seeing your scope. Cost follows the number of reads and writes, the APIs involved, and how many practices you roll out to. The 5-day free technical audit ends with a written report and an estimate you can plan from.