Password Management Policy Checklist for Otology and Neurotology Practices
A written password policy helps your practice control access to electronic protected health information (ePHI) across the EHR, email, imaging systems, audiology and diagnostic equipment, and other clinical applications. Use this checklist alongside your broader security risk analysis and access-control procedures; a password policy alone does not establish HIPAA compliance. The HIPAA Security Rule requires appropriate safeguards, and its addressable specifications require assessment and documentation—not automatic omission. See HHS guidance on risk analysis and addressable specifications.
What should a written password policy cover?
Assign a practice security lead to maintain the policy, approve exceptions, and coordinate with your EHR, IT, and medical-device vendors. State which systems and accounts are covered, who is responsible for each safeguard, and how staff can report suspected credential exposure or unauthorized access.
Your policy should describe how to create, change, and safeguard passwords; request, approve, modify, and disable accounts; handle emergency access; respond to failed login activity; and configure automatic logoff. HIPAA specifically addresses password management and login monitoring in its administrative safeguards. The details should reflect your practice’s risk analysis and actual systems. See 45 CFR § 164.308.
Explain that “addressable” does not mean optional. For each addressable implementation specification, assess whether it is reasonable and appropriate for your environment; document the decision and, when appropriate, implement an equivalent alternative measure. See HHS guidance on required and addressable specifications.
How should practices manage individual user accounts?
Give each workforce member a unique user identification wherever a system supports individual user identification. A shared login can make it difficult to determine who viewed or changed a patient record, so routine clinical work should be traceable to the person who performed it. HIPAA requires unique user identification for systems containing ePHI. See 45 CFR § 164.312.
Grant access according to each person’s role and responsibilities. For example, a clinician, audiologist, scheduler, billing employee, and IT administrator may need different levels of access. Review accounts and permissions when duties change, and promptly disable access when a workforce member leaves or no longer needs it. Keep any necessary emergency access controlled, documented, and reviewed.
If a device or application cannot support separate user accounts, document the limitation and assess compensating controls with your security lead and vendor. A shared workstation is not a reason to share personal passwords.
How can staff create strong passwords and prevent reuse?
Require staff to use a long, unique password or passphrase for each work account. Do not reuse a work password on personal websites or across the EHR, email, remote access, and other services. A breach at one service should not provide a working credential for another.
Consider a managed password manager approved by the practice so staff can create and store distinct credentials without having to memorize each one. Block commonly used or known-compromised passwords when the system supports it, and encourage passphrases that are difficult to guess but practical to remember. NIST’s current digital identity guidance recommends at least 15 characters for a password used as a single authentication factor, allows a lower minimum when the password is used as part of multifactor authentication, and advises against arbitrary periodic password changes. Treat this as technical guidance for policy design—not as a password length or rotation rule specifically imposed by HIPAA. See NIST SP 800-63B-4.
Require an immediate password change when there is evidence or a reasonable suspicion that a credential has been exposed, phished, shared, or used without authorization. Staff should report suspected compromise promptly rather than wait for a scheduled password change.
How should passwords and stored authentication information be protected?
Tell staff never to disclose passwords to coworkers, supervisors, callers, or anyone claiming to be IT support. Support staff should use approved identity-verification and account-recovery procedures rather than asking users to reveal their current password. Do not write passwords on notes attached to workstations or store them in unapproved documents, browsers, or messaging tools.
Use an approved password manager for credential storage, and limit access to the vault by role. The practice should confirm with its vendors how authentication information is protected, including how password verifiers are stored and how account recovery is controlled. Do not retain passwords in plain-text files or logs.
If staff receive a password or reset link unexpectedly, they should not follow the link or reply with credentials. They should use the known, approved sign-in page or contact the practice’s support contact through a verified channel. HHS warns that social-engineering messages may attempt to obtain usernames and passwords; see HHS guidance on phishing and credential theft.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhich default passwords and device protections need attention?
Inventory devices and applications that can access or store ePHI, including workstations, routers, wireless access points, servers, diagnostic systems, and vendor-managed equipment. Before connecting a new system to the practice network or using it with patient information, change any factory-set or installer-provided default password. Use a unique credential for each device or service where supported, and disable unused accounts and services.
Ask vendors how to change default credentials, enable individual accounts, apply security updates, and manage remote support access. Track systems that cannot be updated or do not support stronger authentication, and include them in the practice’s risk analysis and mitigation plan. HHS notes that known operating-system vulnerabilities and unsupported systems should be considered in a risk analysis. See HHS guidance on operating systems and the Security Rule.
Restrict physical access to devices and avoid leaving a logged-in workstation visible or accessible to patients and visitors. HIPAA requires workstation security safeguards for workstations that access ePHI; the specific protections should fit the practice’s environment.
When should multifactor authentication and login monitoring be used?
Use multifactor authentication (MFA) where a risk assessment indicates that a password alone does not adequately protect an account. Prioritize remote access, email, administrator accounts, cloud services, and systems that provide broad access to ePHI. When available, prefer phishing-resistant MFA. HIPAA requires procedures to verify that a person seeking access is who they claim to be, but does not prescribe one specific authentication technology for every system. See HHS guidance on authentication and risk-based MFA.
HHS’s healthcare Cybersecurity Performance Goals are voluntary recommendations, not a replacement for the Security Rule. They identify MFA as a high-impact safeguard for assets and accounts directly accessible from the internet. See HHS Healthcare and Public Health Cybersecurity Performance Goals.
Define how your practice will monitor failed login attempts and report discrepancies. Configure available systems to flag repeated failures, unusual access, or other suspicious activity; identify who reviews alerts and what steps to take, such as verifying the user, temporarily locking an account, resetting a compromised password, and documenting the response. HIPAA’s administrative safeguards include procedures for monitoring login attempts and reporting discrepancies. See 45 CFR § 164.308.
How should shared clinical workstations be configured?
Configure shared workstations so each staff member signs in with an individual account, even when several people use the same computer during a clinic session. Staff should lock the screen whenever they step away, and the workstation should end or protect an inactive session after a time limit selected through the practice’s risk assessment and workflow review.
HIPAA lists automatic logoff as an addressable implementation specification and does not set a universal timeout in minutes. Assess whether automatic logoff is reasonable and appropriate for the practice; document the decision and any equivalent alternative safeguard if needed. See HHS guidance on automatic logoff.
Set the timeout short enough to reduce exposure when a workstation is unattended, but test it in actual clinical workflows so it does not disrupt patient care. Where feasible, configure both the operating-system screen lock and the clinical application’s session timeout. Make sure staff know that a locked screen is not the same as signing out when a session must be fully ended.
Conclusion
A practical password policy combines unique user identification, strong and non-reused credentials, secure account recovery, attention to default passwords, risk-based MFA, failed login monitoring, and safeguards for shared workstations. Review the policy when systems, workflows, vendors, or identified risks change, and make sure staff understand how to follow it.
FAQs
Should each staff member have a unique account?
Yes. Use unique accounts for staff wherever the system supports them so access and activity can be attributed to an individual. HIPAA requires unique user identification for systems containing ePHI. If a system cannot support individual accounts, document the limitation and assess appropriate alternative safeguards. See 45 CFR § 164.312.
Should multifactor authentication be required for access to electronic protected health information?
Use your risk analysis to decide where MFA is needed, and prioritize remote access, email, privileged accounts, and systems that expose ePHI. HIPAA requires authentication procedures but does not prescribe MFA for every access scenario. HHS recommends MFA for internet-accessible assets and accounts as part of its voluntary healthcare Cybersecurity Performance Goals. See HHS Cybersecurity Performance Goals.
How should a practice handle passwords sent through email or messaging?
Do not send reusable passwords through ordinary email, chat, or text, and never send a password in the same message as the account identifier or protected file it unlocks. Use an approved password-reset process or secure credential-sharing tool instead. If a temporary credential must be communicated, use an approved method, limit its validity, and require the user to replace it at first sign-in. This is a prudent practice policy, not a blanket HIPAA rule about every message containing a password.
How should automatic logoff be configured on shared clinical workstations?
Choose an inactivity period based on your risk assessment, room layout, patient-care workflow, and the workstation’s use. Test the setting to make sure it protects unattended sessions without unnecessarily interrupting care. Require staff to lock the screen when stepping away, and configure automatic logoff when it is a reasonable and appropriate safeguard for your environment. HIPAA does not prescribe a single timeout length. See HHS guidance on automatic logoff.
Table of Contents
- What should a written password policy cover?
- How should practices manage individual user accounts?
- How can staff create strong passwords and prevent reuse?
- How should passwords and stored authentication information be protected?
- Which default passwords and device protections need attention?
- When should multifactor authentication and login monitoring be used?
- How should shared clinical workstations be configured?
- Conclusion
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today