A dental practice-management system such as Dentrix, Eaglesoft or Open Dental rarely works alone. It can exchange data with online forms, appointment reminders, two-way texting, payment processing, insurance verification, e-prescribing, review requests, lab ordering, analytics dashboards and Microsoft 365. Each integration is a path for patient data to leave the practice, held open by an account, key or agent that someone set up. This article explains how to keep track of those paths and the vendors behind them.
Where patient data moves
An integration usually works in one of three ways:
- A sync agent installed on the practice server that reads the database and sends data to the vendor’s cloud.
- An API connection authorized with a key, token or vendor login.
- An app connected to Microsoft 365 that was granted permission to read mailboxes, calendars or files.
Each method uses some form of credential, and each can keep running long after anyone remembers turning it on. Cancelling a subscription does not always remove the agent or revoke the permission.
When an integration vendor is a business associate
Under the HIPAA Security Rule, a covered entity may let a business associate create, receive, maintain or transmit electronic protected health information on its behalf only after obtaining satisfactory assurances, documented in a written contract or other arrangement. That is set out in 45 CFR 164.308(b), where the written contract is a required specification.
Section 164.314(a) lists what that contract must provide, including that the business associate will:
- Comply with the applicable requirements of the Security Rule.
- Ensure that its own subcontractors handling the information agree to the same requirements.
- Report security incidents it becomes aware of to the practice, including breaches of unsecured protected health information.
An integration vendor that receives, stores or sends patient data on the practice’s behalf is likely to need a business associate agreement. Whether a particular vendor is a business associate depends on what it does with the data; this is general information, so confirm specific cases with your compliance advisor or counsel.
Build an integration register
A register is a simple table that answers, for every connection:
| Question | Example of what to record |
|---|---|
| What is it and what does it do? | Patient reminder service |
| What data does it read or write? | Names, phone numbers, appointment times |
| How does it connect? | Sync agent on the server, API key, Microsoft 365 app |
| Which account or credential does it use? | The account name and where the credential is stored |
| Who at the practice owns it? | Office manager |
| Is there a business associate agreement? | Yes, with the signed date |
| How is it removed? | Uninstall steps, key revocation, data return |
Start with the practice-management vendor’s list of enabled integrations, then check the server’s installed programs and the apps connected to Microsoft 365.
Check how each connection authenticates
The technical safeguards in section 164.312 include person or entity authentication and transmission security, with encryption of transmitted data as an addressable specification. In practice:
- Confirm the connection is encrypted in transit.
- Give each integration its own credential with only the access it needs, rather than a shared administrator login.
- Store keys and passwords in a password manager, not in a document or email.
- Review apps that have permission in Microsoft 365. Microsoft documents how administrators can review and revoke permissions granted to enterprise applications in Microsoft Entra ID; see our Microsoft 365 page for how we manage tenants.
Retire integrations completely
When you stop using an integration:
- Uninstall any agent from the server and workstations.
- Revoke the API key, token or app permission.
- Disable the account it used.
- Check what your contract says about returning or destroying the data the vendor holds, and ask for confirmation.
- Update the register.
What to do next
Ask your practice-management vendor for a list of every integration enabled on your account and compare it with the business associate agreements on file. Our HIPAA compliance page explains how these requirements fit together. If you want an outside look at what is connected to your systems today, you can request a Blind Spot Scan.