Phone Operations

What Makes a Phone System HIPAA Compliant?

Where patient information lives in a phone system, which HIPAA safeguards and agreements apply, and what to do if a call recording or voicemail leaks.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why “HIPAA compliant phone system” is a misleading phrase
  2. Map where patient information lives
  3. The agreements that apply
  4. Safeguards to configure
  5. Verify identity before discussing anything
  6. A quarterly phone privacy review
  7. When something goes wrong
  8. AI phone tools and patient trust
  9. Worked Example: a misdirected voicemail
  10. Frequently asked questions
  11. References
Phone Operations: What Makes a Phone System HIPAA Compliant?Article coverPHONE OPERATIONSWhat Makes a PhoneSystem HIPAA Compliant?Ava Medical IntakeInsightsPhone Operations: What Makes a Phone System HIPAA Compliant?Article coverPHONE OPERATIONSWhat Makes a PhoneSystem HIPAACompliant?Ava Medical Intake

Key takeaways

  • No phone system is HIPAA compliant out of the box; compliance comes from the agreement, the settings and how staff use it.
  • Patient information sits in more places than most practices expect: voicemail, recordings, transcripts, call logs, text messages and fax.
  • Vendors that create, store or transmit that information for you need a signed business associate agreement.
  • Know the breach clock: individual notices no later than 60 days after discovery, and an annual log for small breaches.

Why “HIPAA compliant phone system” is a misleading phrase

Vendors often describe their phones as HIPAA compliant. There is no government certification that makes a product compliant. HIPAA applies to covered entities, such as medical practices, and their business associates. A phone product can support compliance by offering the right safeguards and signing the right agreement, but the practice still has to configure it, train staff and keep records. Two practices using the same system can be in very different positions.

A useful test: if the vendor says its product is compliant but will not sign a business associate agreement, the claim means very little for your practice.

Map where patient information lives

Start with an inventory. Walk through every part of the phone setup and ask whether patient information could end up there. Most practices find more locations than they expected.

Where protected health information can sit in a medical office phone system
ComponentPatient information it may holdKey safeguard
Voicemail boxesNames, dates of birth, symptoms, medicationsIndividual logins, short retention, no forwarding to personal email
Call recordingsEntire conversations including clinical detailRestricted access, audit logs, set retention period
Transcripts and summariesText versions of calls and voicemailsSame controls as recordings; check where text is stored
Call detail recordsPatient phone numbers, times, durationsRole-based access to reports
Text messagingAppointment details, sometimes clinical contentBusiness texting platform under agreement, consent on file
Online faxReferrals, results, recordsEncrypted storage, routed into the EHR, not email
Desk phone displays and speakerphonesCaller names, overheard conversationsScreen placement, headsets, low voices at the window

Oral information counts too. The Privacy Rule covers health information in any form, so a front desk conversation overheard in the waiting room is a privacy issue even though no system stored it. Physical layout and staff habits belong in the same review as the technology.

The agreements that apply

Any vendor that creates, receives, maintains or transmits protected health information on the practice's behalf is a business associate. HIPAA permits a covered entity to let a business associate handle that information only if it obtains satisfactory assurance, in a business associate agreement, that the vendor will appropriately safeguard it[1]. For a phone setup, that usually means the cloud phone provider, any transcription or call recording service, a texting platform, an online fax service and any answering service or call center.

  • Keep a list of every phone-related vendor and whether an agreement is signed, with the date.
  • Read what the agreement covers. Some vendors cover voice but exclude texting or transcription add-ons.
  • Ask how the vendor handles its own subcontractors, such as data centers or transcription engines.
  • Store signed agreements with your HIPAA records; required documentation must be kept for six years from creation or last effective date[2].

Safeguards to configure

The Security Rule expects technical safeguards for electronic protected health information, including access controls, audit controls, person or entity authentication and transmission security; encryption is an addressable specification, which means you assess it and document your decision[3]. In a phone system, that turns into a short list of settings.

  1. Unique logins for every staff member on the phone portal, voicemail and recordings. No shared passwords.
  2. Role-based access: front desk staff can reach their queues, managers can reach recordings, nobody else.
  3. Multi-factor sign-in on the admin console.
  4. Audit logs switched on, showing who listened to or downloaded a recording and when.
  5. A retention period for recordings and voicemails that matches your policy, with automatic deletion.
  6. Encryption for stored recordings and voicemails, and for calls carried over the internet where the vendor supports it.
  7. Same-day removal of access when someone leaves, on the same checklist as EHR access.

Administrative safeguards matter as much as settings: a written policy on what can be said on voicemail, training on verifying identity before discussing anything by phone, and a named person responsible for the phone vendor relationship.

Verify identity before discussing anything

The most common phone privacy failure is not technical. It is a staff member confirming an appointment, a result or a balance to someone who is not the patient. A short, consistent verification routine prevents most of these incidents and protects staff from awkward judgment calls.

  • Ask for two identifiers, such as full name and date of birth, before discussing anything patient-specific. Do not read the date of birth to the caller and ask them to confirm it.
  • Check the chart for authorized contacts before speaking with a spouse, adult child or caregiver, and note who called.
  • For calls where identity is doubtful, offer to call back at the number on file instead of continuing.
  • Keep minor and adolescent confidentiality rules handy, since state law varies on what parents may be told.
  • When an interpreter or relay operator joins the call, verification still happens with the patient, through the interpreter.

Script the routine so it sounds natural: “Before I look anything up, can I have the patient's full name and date of birth?” Staff who say the same words every time are less likely to skip them on a busy day.

A quarterly phone privacy review

Set a recurring 30-minute review with the practice manager and privacy officer. Pull the list of users with access to recordings and voicemail and remove anyone who has left or changed roles. Check that retention settings have not been changed. Review any incidents and near misses from the quarter. Listen to a small sample of recorded calls for verification and voicemail habits. Confirm that every phone-related vendor still has a current agreement on file, especially after any add-on purchase such as transcription or texting.

When something goes wrong

Phone-related breaches are usually small and ordinary: a detailed voicemail left at the wrong number, a recording emailed to the wrong person, a text sent to an old number. They still trigger obligations.

  1. Report internally the same day

    Staff tell the privacy officer as soon as they notice. Speed matters because the notification clock runs from discovery.

  2. Assess the incident

    Work out what information was exposed, to whom, and whether it was actually viewed or heard. Document the assessment.

  3. Notify affected patients if required

    Breach notifications to affected individuals must be made without unreasonable delay and no later than 60 calendar days after discovery[4].

  4. Log small breaches for HHS

    Breaches affecting fewer than 500 individuals are logged and reported to HHS no later than 60 days after the end of the calendar year[5].

  5. Fix the cause

    Change the setting, script or habit that allowed it, and record the change.

60 days

latest point after discovery to notify individuals affected by a breach[4]

Penalties scale with culpability. The inflation-adjusted HIPAA civil money penalty starts at 145 dollars per violation in the lowest tier and can reach a calendar-year cap of 2,190,294 dollars for identical violations[6]. Most phone incidents never come near those figures, but repeated, unaddressed problems are exactly what moves an organization up the tiers.

AI phone tools and patient trust

Practices adding AI tools to the phones should take patient attitudes seriously. In a Pew survey, 37% of US adults thought using AI in health and medicine would make the security of patients' records worse, compared with 22% who thought it would make it better[7]. Be clear with patients about what any automated system does, keep it away from clinical detail unless an agreement and safeguards are in place, and route patient-specific requests to staff.

US adults' view of how AI in health and medicine would affect the security of patient records
US adults' view of how AI in health and medicine would affect the security of patient recordsComparison. Would make security worse: 37%; Would make security better: 22%.37%Would make security worseWould make security worse: 37%22%Would make security betterWould make security better: 22%US adults' view of how AI in health and medicine would affect the security of patient recordsComparison. Would make security worse: 37%; Would make security better: 22%.37%Would make security worseWould make security worse: 37%22%Would make security betterWould make security better: 22%

Source: Pew Research Center, 2022[7]

Show the data
ItemValue
Would make security worse37%
Would make security better22%

Worked Example: a misdirected voicemail

Example: a medical assistant at a fictional cardiology practice leaves a detailed message about a medication change on a number that turns out to belong to the patient's former employer. She tells the privacy officer within the hour. The officer confirms what was said, calls the number to ask that the message be deleted, documents the conversation and decides with counsel that notification is required.

Example follow-up: the patient is notified in writing well within the 60-day limit, the incident goes on the practice's annual small-breach log, and the practice changes its policy so detailed messages are left only at numbers verified in the last 12 months with documented permission. The medical assistant's quick report is praised at the staff meeting, which makes the next report more likely.

Related reading: what to check when switching to VoIP and serving Spanish-speaking callers, where interpreter calls add another party to the line.

Frequently asked questions

Is there such a thing as a HIPAA certified phone system?

No. There is no official HIPAA certification for products. A vendor can offer safeguards and sign a business associate agreement, and the practice is responsible for configuring and using the system in line with its policies.

Do call recordings count as protected health information?

Recordings of patient calls usually contain protected health information, so they need access controls, audit logs, a retention policy and, where a vendor stores them, a business associate agreement.

Can staff text patients from a practice phone system?

Yes, with care. Use a business texting platform covered by an agreement, keep consent on file, and avoid clinical detail in texts unless your policy and the patient's preferences allow it.

What should we do if a voicemail goes to the wrong person?

Report it to the privacy officer the same day, assess what was disclosed, notify the patient if required within the federal limit, log it, and fix the cause.

References

  1. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑

  2. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑

  3. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR 164.312 - Technical safeguards (opens in a new tab) ↑

  4. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR § 164.404 - Notification to individuals (opens in a new tab) ↑

  5. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR § 164.408 - Notification to the Secretary (opens in a new tab) ↑

  6. Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑

  7. Pew Research Center (2022). 60% of Americans Would Be Uncomfortable With Provider Relying on AI in Their Own Health Care (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo