Key takeaways
- There is no HIPAA certification for vendors; check the business associate agreement, the safeguards and the delivery method yourself.
- A service that stores your messages is a business associate even if it never reads them[2], so the agreement is not optional[3].
- Read the breach, subcontractor and termination clauses line by line; the regulation sets the minimum[4][5].
- Most leaks happen in delivery: messages texted to personal phones, faxes on an open tray, shared logins.
- The safest message is the one never taken: design scripts so office-only calls collect no health information[3].
No certificate exists, so check four things
Every answering service sales page says HIPAA compliant, and the phrase tells you very little. There is no government certificate a vendor can hold, and compliance is something a service does every night with your patients' messages, not a badge on its website. What a practice can check is narrower and more useful: the business associate agreement, the safeguards behind it, the way messages reach your staff, and every other company that touches the data on the way.
The agreement is where it starts. A phone carrier that only transmits the call is a conduit. A service that writes down the patient's name and reason for calling and keeps that message is not. HHS has said the conduit exception covers transmission only, including temporary storage incidental to it, and that an entity that maintains protected health information for a covered entity is a business associate even if it never actually views the information[2]. A practice may let a business associate handle that information only after getting satisfactory assurances, in a written agreement, that it will be safeguarded[3].
The stakes have risen. Large breaches reported to HHS, those affecting 500 or more people, more than doubled between 2018 and 2023, and hacking incidents rose 260% over the same period[1]. Vendors are part of that picture: HHS audits of 2016 and 2017 found only 17% of business associates substantially fulfilling their risk analysis duties[1].
Source: U.S. Department of Health and Human Services, Office for Civil Rights (Federal Register), 2023[1]
Show the data
| Year | Large breaches |
|---|---|
| 2018 | 302 |
| 2019 | 408 |
| 2020 | 656 |
| 2021 | 609 |
| 2022 | 626 |
| 2023 | 725 |
The BAA clauses to read line by line
Most services send a template agreement. It will contain the clauses the regulation requires, because those are easy to copy. The value is in the detail around them: timelines, lists, formats. Read it against this table before anyone signs, and see business associate agreements: when you need one for the general rules.
| Clause | What the rule requires | What to ask the service |
|---|---|---|
| Permitted uses | No use or disclosure beyond what the contract allows | Is message content used for training, quality scoring, analytics or marketing? |
| Safeguards | Comply with the Security Rule | When was your last risk analysis, and who performed it? |
| Incident and breach reports | Report security incidents; breaches within 60 days of discovery at the latest | Will you commit to a shorter window and name the contact who calls us? |
| Subcontractors | The same restrictions flow down to anyone handling the data | List every subcontractor: telephony, messaging app, cloud host, overflow centers, offshore staff. |
| Patient rights | Make information available for access, amendment and accounting | How fast can you produce every message about one patient? |
| Termination | Return or destroy the information at the end, if feasible | In what format do we get our history, and when is it deleted? |
The regulation sets the floor. The contract must require the vendor to report uses or disclosures the agreement does not allow, bind its subcontractors to the same restrictions, open its books to HHS, and return or destroy the information when the contract ends; it must also let you terminate if the vendor breaks a material term[4]. Security incidents, not only confirmed breaches, must be reported[6], and a breach must reach you no later than 60 calendar days after the vendor discovers it, with the affected patients identified where possible[5]. Sixty days is a ceiling, not a target. Your own notices to patients and HHS cannot start until you know, so negotiate a window measured in days and name the person who will call you; the steps that follow are in breach notification for small practices.
Safeguards to verify, not just read about
The Security Rule's technical safeguards are short enough to check one by one. Unique user identification and an emergency access procedure are required; automatic logoff and encryption are addressable[7]. Addressable does not mean optional. The vendor must assess each one and either implement it, or document why it is not reasonable and put an equivalent measure in place[8]. Ask to see that decision for encryption.
- Every operator has a personal login. Shared logins make audit logs useless.
- Audit logs record who opened which message and when, and the service can pull them for one patient on request.
- Multi-factor sign-in on the message app your physicians use, and on operator workstations.
- Encryption for messages in transit and at rest, including backups and call recordings.
- Screens lock automatically; home-based operators work under written physical safeguards.
- A written retention schedule for messages and recordings, and deletion you can confirm.
HHS has proposed going further. Its January 2025 proposal would require practices to get written verification from each business associate, at least every 12 months, that the required technical safeguards are in place, and would add a clause requiring vendors to report activation of their contingency plan within 24 hours[1]. It is a proposal, not a final rule, but nothing stops you asking for both now.
Delivery is where most messages leak
A service can run a careful call center and still undo it at the last step. The night message has to reach a physician, and the easiest routes are the riskiest: a plain text to a personal phone with the patient's name and symptoms, an email to a home account, a fax that sits on an open tray until 8 a.m.
- Caller
- Your team
- System
01Caller
Patient calls the office
Forwarding carries the call; the carrier acts as a conduit.
02Your team
Operator writes the message
Name, date of birth, reason: now stored by the service, a business associate.
03System
Message app or paging tool
Often a subcontractor; it must be bound by the same terms.
04Your team
On-call physician reads it
On a personal phone; needs a login, not a plain text.
05System
Morning copy to the office
Portal, secure email or e-fax; who can open it, and for how long?
Example. Every box after the first holds a copy of the message; each copy needs a safeguard and an owner.
Ask for a secure app with a login and read receipts for physicians, and a notification text that says only that a message is waiting. For the office copy, a portal or secure inbox beats fax; if fax stays, it lands in a locked room. Check what happens when a physician leaves the group: the app account must close the same day. Texting patients and HIPAA and faxing PHI cover the related rules, and secure message delivery from your answering service compares the options.
Collect less, so there is less to protect
The minimum necessary standard asks covered entities and business associates to make reasonable efforts to limit protected health information to what the task needs[3]. On the phone, that means writing scripts so that office-only calls never produce a health record. A caller asking about Saturday hours, parking or whether you accept a plan does not need to give a date of birth, and the operator should not ask for one.
Some practices put a no-PHI front line ahead of the clinical one. An SI Employee answers office and new-patient questions from the information you approve, gives your 911 instruction when a caller describes an emergency, and transfers anything about a specific patient to the number you choose, such as your nurse line or your BAA-covered answering service. It does not take health details, and AssistCall does not sign business associate agreements today, so it is not a substitute for a covered service on clinical calls. Callers can still volunteer details, so limit who on your team has a login to recordings and transcripts. The family medicine example shows refill and appointment callers routed without details being taken (how it works).
| Input | Example |
|---|---|
| Overnight messages per weekday | 18 |
| Minutes to read, call back and close each one | 5 |
| Share that were office-only questions | 30% |
| Staff cost per hour, wages plus benefits | $36.73 |
| Calls a month | 391 |
| Staff hours on these calls | 33 |
| Hours handed off | 9.8 |
| Monthly value of that staff time | $359 |
How it is worked out: Calls a day × 21.7 working days × minutes per call ÷ 60 × share handled = hours; hours × hourly cost.
Assumptions
- Hourly cost of $36.73, the average total compensation per hour worked for private-industry office and administrative support workers in June 2026.[9]
- Message count, minutes per message and the office-only share are invented for this example; count a week of your own morning messages.
Example only. The calculator counts staff time on morning callbacks for questions that could have been answered on the call without any patient details.
Questions to put to every service
- Will you sign our business associate agreement, or only yours? Send yours now so our counsel can compare.
- Who are your subcontractors for telephony, messaging, hosting and overflow, and where do they work?
- How do physicians receive messages, and what appears on the lock screen?
- Show us the audit log for one test patient after our trial calls.
- What is your breach notification window in practice, and who calls us?
- Do operators work from home, and under what written safeguards?
- Is any part of the call handled by automated speech or software, and is message content used to train it?
- What happens to our messages and recordings 30 days after we cancel?
Score the answers the way you would any vendor, using the vendor BAA checklist. Vague answers to the subcontractor and delivery questions are the clearest warning. A good service answers both in writing within a day.
Example script for the sales call: “Before pricing, we need three things in writing: your subcontractor list, a screenshot of what our physicians see when a message arrives, and your last risk analysis date. If those are fine, we will send our BAA.”
Test the answers during a trial
Paperwork tells you what a service promises. A two-week trial with a fictional patient tells you what it does. Agree the test with the vendor in advance so nobody mistakes it for a real emergency, and use a made-up name and date of birth that exist nowhere in your records.
Place five test calls
A routine message, an urgent post-op story, an office question, a call from a family member, and a call that asks the operator for medical advice.
Check what the physician sees
Photograph the on-call phone's lock screen when each message arrives. Nothing beyond a prompt to open the app should show.
Ask for the audit trail
Request the log of everyone who opened the test patient's messages. It should arrive within days and list named users, not a shared account.
Check the office copy
Note where the morning copy landed, who could open it and whether it carried more detail than the call needed.
Request deletion
Ask the service to delete the test patient's messages and recordings, then confirm in writing that it did, including backups.
A service that passes all five is rare, and a near miss is not a reason to walk away. A service that cannot produce an audit log or a deletion confirmation is telling you how a real incident would go.
Why patients and regulators both care
Penalties scale with culpability, from $145 per violation at the lowest tier to a calendar-year cap of $2,190,294 per identical provision[10]. Patients care for their own reasons: 77% of the public say they are concerned about the privacy of medical information given to AI tools[11], and more services now put software somewhere in the call. Ask where, and get the answer into the agreement. For phone-side safeguards inside the practice, see what makes a phone system HIPAA compliant.
Frequently asked questions
Is there such a thing as a HIPAA certified answering service?
No. HIPAA has no vendor certification. A service can sign a business associate agreement, run the required safeguards and pass outside security audits, and you can check each of those, but no badge replaces that review.
Does an answering service need to sign a BAA?
If it takes and stores patient messages for your practice, yes. HHS treats an entity that maintains protected health information for a covered entity as a business associate even if it never views the information[2].
Is our phone carrier a business associate too?
A carrier that only transmits calls usually falls under the conduit exception, which covers transmission and temporary storage incidental to it[2]. Voicemail transcription, call recording and messaging features can change that, so ask what the carrier stores.
Can the answering service text messages to our doctors?
Only through a channel your risk analysis supports. A plain text with patient details on a personal phone is the riskiest option; a secure app with a login and a content-free notification is the usual answer.
How fast must a service tell us about a breach?
Without unreasonable delay and no later than 60 calendar days after discovery[5]. Negotiate a shorter window, because your own notices to patients cannot start until the vendor tells you.
References
U.S. Department of Health and Human Services, Office for Civil Rights (Federal Register) (2023). HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information; Proposed Rule (90 FR 898, January 6, 2025) (opens in a new tab) ↑
U.S. Department of Health and Human Services (Federal Register) (2013). Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules (Omnibus Final Rule, 78 FR 5566, January 25, 2013) (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 164.504 - Uses and disclosures: Organizational requirements (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 164.410 - Notification by a business associate (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 164.314 - Organizational requirements (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 164.312 - Technical safeguards (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 164.306 - Security standards: General rules (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: private industry workers by occupational and industry group, June 2026 (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (2026). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑
KFF (2026). KFF Tracking Poll on Health Information and Trust: Use of AI For Health Information and Advice (fielded Feb 24 - Mar 2, 2026) (opens in a new tab) ↑