A director of nursing opens a resident's care plan and notices that a fall-risk entry has changed. No one remembers editing it. The question is not only who changed it but whether the system could have told you. That question sits at the center of the integrity standard.
Most people think of HIPAA security as keeping outsiders away from records. Integrity is a different idea. It asks whether the records you rely on are accurate, complete and unchanged except by people who are supposed to change them.
Under the Security Rule, you are expected to protect electronic health information from improper alteration or destruction. "Improper" is the key word. Nurses correct charting, physicians sign orders and the business office updates insurance details every day. Those are proper changes. Integrity problems are the others: an entry edited by someone without authority, a note deleted to hide an error, a file corrupted by a failing drive, a record overwritten by a bad software update, or data lost because a sync tool misbehaved.
Integrity is about both people and machines. A well-meaning aide and a failing server can damage a record equally.
You do not need exotic tools. Most of what keeps records trustworthy is ordinary and consistent.
Individual logins. If three people share one account, you can never say who changed what. Every user needs their own sign-in.
Role-based permissions. A dietary aide has no reason to edit a medication order. Limit editing rights to the roles that need them, and limit who can delete.
Audit trails. Your EHR should record who viewed, created, changed or removed an entry, and when. Confirm that logging is turned on, and that someone is allowed to read it.
Locked and signed entries. Many systems let you lock a note after signing, so later changes appear as addenda rather than overwriting the original. Use that behavior.
Backups with tested restores. A backup you have never restored is a guess. Backups also protect against ransomware, which attacks integrity as well as availability.
Protected devices. Updated software and endpoint protection reduce the chance that malware alters or encrypts files.
Integrity failures often happen where the formal system ends. Spreadsheets of census and diet orders, shared folders of incident reports, scanned faxes, and photos of wound care all hold information that people rely on. Ask where each one is stored, who can edit it, and whether older versions can be recovered. Cloud storage such as OneDrive or SharePoint offers version history, which can be a quick way to see what a file looked like last week, provided it is turned on and retained.
Can we tell who changed a given chart entry last month?
Who is allowed to delete records, and is that logged?
Do we have any shared logins on the floor or at the front desk?
When did we last restore from a backup to prove it works?
What do staff do when they spot an error in a record? Is there a correction process that keeps the original visible?
Who reviews the audit logs, and how often?
If any answer is "I'm not sure," that is useful information. Write it down and assign an owner.
Staff sometimes fear that fixing a mistake looks like tampering. Teach the opposite. A good correction process is a late entry or addendum that is dated, signed and linked to the original, with the original still readable. Your policies should say that deleting or backdating an entry to cover a mistake is a serious violation, and that honest corrections are expected. Check your state's requirements and your EHR vendor's guidance for how corrections should be recorded, and have counsel review your policy.
Preserve the evidence first. Do not let people continue editing the record, and ask IT to export the audit trail before anything rotates out. Then involve your privacy officer, who will follow your incident process and decide whether further steps are needed.
UnityCare IT helps care providers check that audit logging is on and readable, that permissions match job roles, and that backups can really be restored. We can also review how files are shared in Microsoft 365 and sort out where version history can protect you, so your records stay accurate and your team can show it.
Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support