Staff texting patient information from personal phones: how to fix it

To fix staff texting, move internal staff conversations to a messaging app whose vendor signs a business associate agreement (BAA) covering the exact product and plan you use. Then retire WhatsApp and SMS for work with a written policy, a cutover date and records that show the old channel is closed. Banning WhatsApp alone does not close a risk assessment finding. Staff need an approved tool that is as fast as the one they lose, plus the paperwork that shows the change happened.

Short answer: what to switch to

Switch internal staff conversations to a staff messaging app covered by a signed BAA on the plan you buy. Retire WhatsApp groups and SMS for work on a fixed date, and back the change with a one-page policy.

There are two separate jobs, and they usually need two separate tools:

  • Staff-to-staff coordination includes front desk questions, schedule changes, supply requests, billing questions and "can someone cover room 3." This needs a staff chat.
  • Patient-facing messages include appointment reminders, intake links and replies to patients. These need a patient messaging tool built for that purpose.

One tool rarely does both well. Decide first which job you are fixing. If staff are discussing patients among themselves in WhatsApp groups, you are fixing the first one.

Consumer messaging apps tend to show up as findings in a risk assessment for three reasons:

  • No BAA with the practice. The vendor has not signed a BAA with you, and no official WhatsApp or Meta page offers one. WhatsApp's Business Messaging Policy tells businesses not to use WhatsApp to send or request health information where regulations prohibit sharing it with systems that do not meet heightened requirements (whatsappbusiness.com).
  • Data on personal devices. Messages sit on personal phones, in personal accounts the practice does not control.
  • No admin control. The practice cannot manage accounts, cannot see who belongs to a group, and cannot remove a former employee's access to past messages.

For the full rules on texting PHI, including patient texting and consent, see HIPAA texting rules and options. This page covers the fix.

What a HIPAA risk assessment expects for staff messaging

The Security Rule requires a covered entity to run a risk analysis of where electronic PHI (ePHI) is created, received, stored and transmitted. It must then manage the risks it finds (45 CFR 164.308(a)(1)(ii)(A) risk analysis and (B) risk management, both required) (ecfr.gov). Staff messaging falls in scope whenever patient information passes through it.

Assessors typically check these safeguards for a messaging channel:

Safeguard What the assessor looks for Citation
Access control and unique user IDs Each staff member has their own account; shared logins are not used; access can be removed 45 CFR 164.312(a)(1), (a)(2)(i); 164.308(a)(3)(ii)(C) (ecfr.gov)
Audit controls The system records activity that can be reviewed 45 CFR 164.312(b) (ecfr.gov)
Transmission security ePHI is protected in transit 45 CFR 164.312(e)(1) (ecfr.gov)
Business associate agreements A signed BAA with any vendor that creates, receives, maintains or transmits PHI for you 45 CFR 164.308(b)(1) and 164.502(e); contract content in 164.314(a) and 164.504(e) (ecfr.gov)

Some specifications are "addressable" rather than "required." Addressable does not mean optional. Under 45 CFR 164.306(d)(3), you either implement the specification or document why it is not reasonable and appropriate, and implement an equivalent alternative measure only if one is reasonable and appropriate (ecfr.gov).

A messaging finding is usually closed with documented remediation. That record typically includes:

  • the approved tool
  • the signed BAA
  • a written policy
  • training records
  • device rules
  • evidence that the old channel was retired

HHS's Guidance on Risk Analysis says an organization must identify where ePHI is stored, received, maintained or transmitted, regardless of the electronic medium, including portable media (hhs.gov).

Messaging is one line in a wider program. Use the HIPAA compliance checklist for clinics to place it alongside email, phones, devices and vendors.

What to check in a staff messaging app

Check the BAA first. Confirm the vendor signs one, that it covers the specific product and plan you will pay for, and what data it covers. Then check the controls below.

Check Why it matters What to ask the vendor
BAA on the plan you will buy No BAA means no basis for sharing PHI with the vendor "Which plans include a signed BAA? Is it included or an add-on?"
What the BAA covers Some agreements cover messages but not files or voice notes "Does the BAA cover messages, files, voice notes, tasks and any other content in the workspace?"
Access controls and roles Front desk, billing and managers should not all see everything "Can we create roles and restrict channels by role?"
2FA and SSO A stolen password should not open the workspace "Is two-factor authentication available on this plan? SSO?"
Retention settings Your policy decides how long messages are kept, not the app's defaults "Can admins set workspace-wide and per-conversation retention?"
Remote sign-out / session revocation Lost phones and same-day leavers "Can an admin end a user's sessions on all devices? On which plan?"
Audit logs Assessors ask how activity is reviewed "What user and admin actions are logged, and on which plan?"
Encryption in transit and at rest Transmission security and stored data "What protocol is used in transit? Is stored data and file storage encrypted?"
Guest separation Outside billers, IT contractors and vendors "Can guests be limited to specific conversations?"
Mobile apps staff will use If the app is slower than WhatsApp, staff drift back "Are there iOS and Android apps? How long does setup take for a new user?"

The BAA is plan-specific. Free tiers often come with no BAA. A BAA on one plan does not extend to a cheaper plan of the same product. If half your locations sit on a free workspace, those locations are not covered. For how this applies across software categories, see what qualifies as a HIPAA-compliant app.

Integrations and AI features need their own check. For every connector, automation platform or AI feature, ask whether it falls inside the vendor's BAA. Third-party connectors usually move data to another company, and that company needs its own BAA with you.

The tool supports compliance; it does not deliver it. The practice still has to:

  • sign the BAA before any PHI is shared
  • configure roles and retention
  • manage offboarding
  • secure devices
  • train staff

Tool categories and where each fits

There are four categories. Most practices fixing staff texting need the first or second.

Category Who it is for Typical fit Main thing to confirm
General team chat with a BAA (e.g. Slack, Microsoft Teams, Google Chat on qualifying plans) Organizations that already run the vendor's suite Practices of any size already standardized on that suite Which plans and services the BAA covers. Slack requires an Enterprise plan and a signed BAA (slack.com). Microsoft includes its BAA by default for in-scope commercial services, including Teams (learn.microsoft.com). Google covers Chat only after an admin accepts its BAA.
Healthcare staff chat for clinic operations Front desk, practice managers, billing, HR and IT coordinating daily work Small practices and multi-location groups BAA on the plan; ease of use for frontline staff. Example: Chanty offers team chat, calls, announcements, files and assigned tasks for clinic staff, with HIPAA support and a signed BAA from the Business plan (not on Free). It is for operational coordination alongside the EHR, not clinical handoffs, alerts or patient messaging.
Clinical communication platforms Care teams exchanging clinical messages, on-call and escalation Hospital-adjacent groups and larger clinical organizations Validation for clinical workflows; integration with clinical systems
Patient messaging tools Texting patients: reminders, replies, intake Any practice that messages patients BAA, patient consent handling, two-way texting rules

Read more about the third category in clinical communication platforms, and about the fourth in patient communication and messaging software. Video visits are a separate category again; see HIPAA-compliant telehealth platforms. For what a staff chat built for clinic operations looks like, see HIPAA-compliant chat for clinic staff.

If you already use Microsoft 365 or Google Workspace, check your current agreement before buying anything. Microsoft includes its BAA by default for in-scope commercial services, including Teams. Google covers Chat only after an admin accepts its BAA in the Admin console (Account settings > Legal and compliance) (learn.microsoft.com). If your agreement covers the tool, the remaining question is whether frontline staff will actually use it on their phones.

A two-week plan to move a clinic team off WhatsApp and SMS

Days 1–3: Set up and write the rules

  • Choose the tool.
  • Sign the BAA on the plan that includes it.
  • Name an admin.
  • Turn on 2FA, set roles (front desk, clinical staff, billing, managers) and set retention to match your records policy.
  • Write a one-page messaging policy covering what goes where, what never goes in chat, and the rules for personal devices.

Days 4–6: Mirror the old groups and pilot

  • Create channels that match the WhatsApp groups staff already use, for example:
    • "Front desk – Main St"
    • one channel per location
    • "Managers"
    • "Billing questions"
  • Invite a pilot group of one front desk lead, one clinic manager and one biller.
  • Pin the policy and a short how-to in each channel.

Days 7–10: Full rollout

  • Run a 15-minute walkthrough per shift, including the early shift that opens the front desk.
  • From day 7, leads post schedule changes, coverage requests and updates only in the new tool. Staff follow where the information is.
  • Collect questions in one channel and answer them there.

Days 11–14: Cutover and evidence

  • On the cutover date, admins post a final notice in each old WhatsApp group pointing to the new channel.
  • Ask staff to leave the old work groups and follow the instruction your privacy officer or counsel gives on messages already on their phones.
  • Record completion for the risk assessment file.
Step Owner Date Evidence kept
BAA signed on the correct plan Practice owner / COO Day 2 Signed BAA, plan confirmation
Roles, 2FA, retention configured Admin / IT or MSP Day 3 Screenshots of settings
Messaging policy approved Privacy officer Day 3 Signed policy, version date
Channels created, pilot live Practice administrator Day 6 Channel list, pilot roster
Training per shift Clinic managers Day 10 Attendance and attestations
Old groups closed Admin + location leads Day 14 Final notice, staff confirmations

Following this plan does not guarantee a passed assessment. It produces the record of remediation an assessor will ask for.

Policy and device rules that close the gap

A messaging policy should fit on one page and cover at least:

  • Approved channels: the staff chat for internal coordination, the EHR for clinical documentation, and the patient messaging tool for patients.
  • Minimum necessary: share only the patient details the task needs. Use initials plus appointment time instead of the full name and diagnosis where that is enough.
  • No PHI in personal apps or SMS, including personal email and personal cloud notes.
  • Photos and screenshots: no photos of schedules, charts or insurance cards in personal camera rolls.
  • Lost devices: report a lost or stolen phone to the admin within a set time, so access can be removed.

Personal phones (BYOD) are workable with rules:

  • Require a device lock or app passcode.
  • Require 2FA on the work app.
  • Make sure the admin can end the user's access.

Write these rules into your risk management plan so the decision is documented.

Offboarding: remove access the same day someone leaves, including part-time and per-diem staff. Keep evidence of the date and the person who removed it.

Training and sign-off: run a short session on the new policy, have each staff member sign an attestation, and store the attestations with the assessment. For a wider program, see HIPAA training for staff.

Common mistakes when replacing WhatsApp

  • Choosing the free tier and assuming it is covered. The BAA is tied to a plan. Check that the plan you pay for includes it.
  • Running old and new channels in parallel with no end date. Staff keep using whichever channel the manager posts in. Set the cutover date on day 1.
  • Using staff chat for clinical handoffs or urgent clinical alerts. A team chat is for operational coordination. Clinical handoffs and alerts belong in systems built and validated for them.
  • Connecting integrations or AI tools that move PHI outside the BAA. An automation that copies messages into another service creates a new vendor relationship, which needs its own BAA.
  • Banning WhatsApp without an equally fast mobile option. If the front desk cannot reach a manager in seconds from their phone, the WhatsApp group comes back within a week.

Next steps

The path is:

  1. Assessment finding
  2. Approved tool with a signed BAA on the right plan
  3. Policy and training
  4. Dated cutover
  5. Evidence in the file

Before you choose a tool:

To set up a staff workspace, start on the Business plan, the first plan that includes a signed BAA. Sign the BAA before anyone shares patient information.

Where Chanty fits. chanty.health is published by Chanty, a team chat for clinic staff with a signed BAA from the Business plan. If your team still coordinates in personal group chats, see how HIPAA-compliant staff chat works or start free.

FAQ

Our clinic staff use WhatsApp groups to discuss patients. What should we switch to?

Switch to a staff messaging app whose vendor signs a BAA covering the plan you buy. Then close the WhatsApp groups on a fixed cutover date with a written policy. If staff also text patients, handle that with a separate patient messaging tool.

Is WhatsApp HIPAA compliant if messages are encrypted?

Encryption alone does not settle it. Encryption addresses transmission security, but HIPAA also expects:

  • a BAA with the vendor
  • unique user access the practice controls
  • audit controls
  • the ability to remove access

Check WhatsApp's current position on BAAs before relying on it. Its Business Messaging Policy tells businesses not to send or request health information where regulations require systems meeting heightened requirements (whatsappbusiness.com).

We failed a HIPAA risk assessment because of staff texting. What do we need to fix it?

You need documented remediation:

  • an approved messaging tool with a signed BAA on your plan
  • a written messaging policy
  • staff training with attestations
  • device rules for personal phones
  • evidence that the old WhatsApp or SMS channels were retired on a specific date

HHS's Guidance on Risk Analysis calls risk analysis the first step and foundational, and says an organization must identify where ePHI is stored, received, maintained or transmitted (hhs.gov).

What are good alternatives to WhatsApp for healthcare staff communication?

There are three options for staff-to-staff messaging:

  • general team chat with a BAA, such as Slack, Microsoft Teams or Google Chat on qualifying plans
  • healthcare staff chat built for clinic operations
  • clinical communication platforms, for care-team clinical workflows

For general team chat, qualifying means Slack on an Enterprise plan with a signed BAA, Teams under Microsoft's default BAA for commercial services, and Google Chat once an admin accepts Google's BAA (slack.com). Choose based on whether you need operational coordination or clinical messaging.

Is SMS texting between staff allowed under HIPAA?

HIPAA does not name specific apps. It sets safeguards that any channel carrying ePHI must meet. Standard SMS between personal phones gives the practice no BAA with a vendor and little control over access or retention, which is why it is a common finding. See HIPAA texting rules and options for the detail.

Does a free messaging plan cover patient information?

Usually not. Free tiers often come without a BAA, and a BAA on a paid plan does not extend to the free plan of the same product. Chanty's Free plan, for example, has no BAA and should not be used for patient information.

We already use Microsoft 365. Can we use Teams instead of buying a new tool?

Possibly. Microsoft's BAA applies by default through its Data Protection Addendum to in-scope commercial services, including Teams. Confirm that your subscription is a commercial Microsoft 365 or Office 365 plan (learn.microsoft.com). If it is, the question becomes whether front desk and frontline staff will use Teams on their phones.

Can staff keep using their personal phones with an approved app?

Yes, with documented rules:

  • device lock or app passcode
  • 2FA on the work app
  • lost-device reporting
  • admin ability to remove the user's access

Record these rules in your risk management plan.

What should we do with patient information already in old WhatsApp groups?

Decide this with your privacy officer or counsel. Whatever you decide, document the instruction you gave staff and their confirmation.

Is a staff chat app the same as a patient messaging or clinical communication platform?

No. A staff chat handles internal operational coordination: schedules, coverage, supplies, billing questions and follow-up tasks. Patient messaging tools handle communication with patients. Clinical communication platforms handle care-team clinical workflows such as handoffs and escalation.