ShieldForce Colored Variance Logo
ChatGPT and HIPAA in Nursing Homes: A Guide to Shadow AI for SNF and LTC Leaders
Nursing Home Security

ChatGPT and HIPAA in Nursing Homes: A Guide to Shadow AI for SNF and LTC Leaders

6 min read
SF
Obi Ibeto

Not with a personal account. Free and paid personal ChatGPT accounts are not covered by a HIPAA business associate agreement. When a nurse, MDS coordinator or social worker pastes resident...

Not with a personal account. Free and paid personal ChatGPT accounts are not covered by a HIPAA business associate agreement. When a nurse, MDS coordinator or social worker pastes resident information into one, that is an impermissible disclosure the facility must investigate as a possible breach. A one-page AI policy, an approved tool, training and device controls prevent it.

The clearest warning so far came from a long-term care setting. In November 2026, HIPAA Journal reported that a staff member at Lake Burien Transitional Care Facility, a Washington State facility, used a personal ChatGPT account to draft summaries of client case notes. The notes included names, diagnoses and medications. The state found one instance, then discovered several earlier ones, and wrote to 12 families. A similar incident affected four patients at Western State Hospital.

No one hacked anything. A staff member with a heavy documentation load found a faster way to write. That pressure is familiar in nursing homes and skilled nursing facilities: care plan updates, progress notes, incident write-ups, discharge summaries and family emails, often written at the end of a long shift by staff who rotate across units and facilities.

This guide covers where the HIPAA line is, what to do if staff have already crossed it, and how to let your team benefit from AI without putting resident information at risk.

Can nursing home staff use ChatGPT with resident information?

Only through a tool your facility has a signed business associate agreement for. Without that agreement, resident information should never go into an AI tool, whatever brand it is.

A business associate agreement (BAA) is the contract in which a vendor commits to protect health information the way HIPAA requires. The U.S. Department of Health and Human Services (HHS) Guidance on HIPAA and Cloud Computing says a cloud service that stores or processes electronic health information is a business associate. It also says using one without a BAA violates the HIPAA Rules. Online AI tools work the same way: what staff type in is processed on the vendor's servers.

OpenAI's help center lists only specific business offerings, such as ChatGPT for Healthcare and ChatGPT Enterprise with a Regulated Workspace, as available with a BAA. Personal free and paid accounts are not on that list. The same test applies to Gemini, Copilot, Claude and any other assistant: no signed BAA, no resident information.

What happens after a slip

Under the HIPAA Breach Notification Rule, an impermissible disclosure is presumed to be a breach. The exception is when a documented risk assessment shows a low probability that the information was compromised. That assessment weighs what was disclosed, who received it, whether it was actually acquired or viewed, and how far the risk was reduced.

If the facility can't show a low probability, it must notify affected residents or their representatives within 60 days of discovery. It must also report to HHS, and notify the media if more than 500 residents of one state are affected. Many states add their own rules.

In the first 48 hours:

  • Stop it without blame, so the staff member tells you everything.

  • Find out what went in: which residents, which details, how many times. At Lake Burien, the first find led to earlier ones.

  • Reduce the exposure: have the conversations, and if appropriate the account, deleted, and record when.

  • Document every decision. This is what HHS and state surveyors may ask to see.

  • Run the risk assessment with your privacy officer, and get legal advice before deciding not to notify.

For what follows, see our nursing home ransomware and recovery playbook. Its response steps apply to any security incident.

How can nursing homes stop shadow AI without banning it?

Give staff an approved way to get documentation help, then close the unapproved ways. A ban alone moves the behavior onto personal phones at the nurses' station, where you can't see it.

Shadow AI means AI tools staff use for work without the organization's approval. A Wolters Kluwer Health survey, cited by HIPAA Journal, found 40% of hospital workers knew colleagues using unauthorized AI tools, and 20% admitted using them. Nursing homes have their own risk factors: shared workstations, staff who rotate across units, agency nurses who bring their own habits, and heavy documentation loads.

1. Find out what's already in use

Ask without blame which AI tools staff use and for what: care plan wording, progress notes, incident reports, family updates, policy drafts. Include agency and per diem staff. Check browser extensions on shared workstations. Then add AI tools to your annual risk analysis.

HIPAA tie-in: risk analysis, 45 CFR 164.308(a)(1)(ii)(A).

2. Offer an approved tool, with one simple rule

The rule: no resident information goes into any tool unless the facility has a signed BAA for it. Then offer an approved option, such as an AI feature inside your EHR or a business AI service with a BAA. Until one exists, tell staff which tasks are fine without resident details.

Need Audit-Ready HIPAA Compliance for Your Field Team?

Protect remote clinical staff, field laptops, mobile EVV apps, and EHR systems starting at $35/user/month.

HIPAA tie-in: business associate contracts, 164.308(b)(1) and 164.502(e).

3. Train at onboarding, not just annually

With high turnover and agency staffing, annual training alone misses people. Cover AI in new-hire and agency orientation. Use real examples, like a nurse pasting a discharge summary into a chatbot to shorten it. Back it with a written sanctions policy, applied consistently.

HIPAA tie-in: security awareness and training, 164.308(a)(5); sanctions policy, 164.308(a)(1)(ii)(C).

4. Lock down shared workstations and devices

On facility-managed computers and tablets, block or restrict consumer AI sites and apps. Use data loss prevention (DLP) tools, which spot sensitive information leaving a device. Give every staff member a unique login so activity can be traced, and review logs for traffic to AI services.

HIPAA tie-in: unique user identification and access control, 164.312(a); audit controls, 164.312(b); information system activity review, 164.308(a)(1)(ii)(D).

5. Treat an AI slip as a security incident

Add the AI scenario to your incident response plan: who staff tell, who checks what was shared, and who decides on notification. Make reporting safe, so staff come forward early.

HIPAA tie-in: security incident procedures, 164.308(a)(6).

What should a nursing home AI policy include?

One or two pages that a CNA or agency nurse can follow on their first shift. Cover these points:

Policy element

What to write down

Approved tools

The exact tools allowed with resident information, each with a signed BAA on file.

The bright line

No resident information in any other tool, including on personal phones and accounts.

Allowed without PHI

Tasks fine with any tool when no resident details are included, such as a general activity calendar.

Accounts

Work AI use only through facility-managed accounts.

Human review

A licensed nurse or the responsible clinician reviews and owns anything AI drafts for the medical record or a family.

Agency and contract staff

The policy applies to them, and is covered in their orientation.

Requesting a new tool

Who to ask, and how the facility checks security and gets a BAA first.

Reporting mistakes

Who to tell, how fast, and an assurance that early reporting is encouraged.

Sanctions, training, review

Consistent sanctions, sign-off at onboarding and annually, and a set review date.

You can fold this into your acceptable use policy; our acceptable use policy guide shows the structure. Documented policies and training also help when surveyors or partners ask how you protect resident information. See what CMS surveyors look for.

The bottom line

Your staff turn to AI because documentation never stops, and AI can help. The risk is resident information going into tools your facility has no agreement with and no view into. Set one rule, offer an approved option, train every new hire and agency nurse, and make reporting safe.

ShieldForce works alongside the EHR you already run, adding monitoring, data loss prevention, training and incident response at a flat $35 per user per month. Start with the Nursing Home Compliance Audit or our Nursing Home Cybersecurity Guide.

Sources

This article is general information, not legal advice. Consult qualified HIPAA counsel for guidance specific to your facility.

Share this post

Need Audit-Ready HIPAA Compliance for Your Field Team?

Protect remote clinical staff, field laptops, mobile EVV apps, and EHR systems starting at $35/user/month.

Topics

#Nursing Home Security#AI Security#HIPAA compliance#Shadow AI
Free Security Assessment

Ready to Secure Your Business?

Don't let cyber threats put your business at risk. Discover how ShieldForce protects organizations like yours - 24/7.