Electronic medical records bring privacy and security responsibilities, but there is no single step that can “get rid of” every risk. Healthcare organizations need an ongoing process to understand where electronic protected health information (ePHI) is created, accessed, stored, and shared; assess potential threats; and implement safeguards appropriate to their environment.
Common privacy and security concerns
- Access beyond a person’s role: excessive permissions, shared accounts, or delayed offboarding can expose information unnecessarily.
- Human error: sending information to the wrong recipient, misplacing a device, or entering data into the wrong record.
- Cybersecurity incidents: phishing, malware, ransomware, or compromised credentials may affect confidentiality and system availability.
- Vendor and exchange risks: outside services and interfaces can create additional data flows and responsibilities.
- Insufficient recovery planning: a security incident or outage can interrupt access to records needed for care.
Build an ongoing risk-management process
- Inventory information and systems. Identify where ePHI is created, received, maintained, and transmitted, including devices, interfaces, and vendors.
- Assess threats and vulnerabilities. Consider likelihood and potential impact in your organization’s actual environment.
- Implement appropriate safeguards. Use administrative, physical, and technical measures based on documented risks and applicable requirements.
- Manage access. Assign appropriate roles, review access periodically, and remove access when job responsibilities change.
- Train and prepare staff. Explain approved workflows, remote access, incident reporting, device handling, and how to get help.
- Plan and rehearse response. Define how to report, investigate, contain, and recover from incidents or outages.
- Reassess as conditions change. Review risks when technology, vendors, operations, or threats change; update safeguards where needed.
Questions to ask an EMR vendor
- What data does the service handle, and where does it flow?
- Which access controls, audit capabilities, and incident processes are available?
- What security responsibilities belong to the practice and what belongs to the vendor?
- What contractual terms, including business-associate terms where applicable, govern the relationship?
- How are backups, recovery, downtime, data export, and termination handled?
- How will the practice receive notice and coordinate in the event of an incident?
