SecurePatientData — Patient privacy and protection

Protect your information

Passwords and verification

Secure the keys to your health accounts

Sources checked November 19, 2026 · 5 questions · 5 min read

An older adult and family caregiver reviewing a healthcare portal on a laptop
AI-generated illustrative care scene; no real patient or provider is depicted.

Why should each health account use a different password?

A password reused after another company’s breach can expose a patient portal. Generate a different long password for every account and protect your password manager. Reused credentials can connect otherwise unrelated accounts: a password exposed at one service can be tried against email, insurance or portal accounts. Unique credentials reduce that cross-account risk.

Use a reputable password manager or another secure method you can maintain, and protect the manager’s own recovery and sign-in. If an account is compromised, update any reused credential elsewhere and review sessions and recovery methods. These are recommended practices for your accounts, not a waiver of the provider’s safeguard duties. Ask the service how it handles recovery rather than giving a helper your password as a substitute for authorized proxy access.

Which additional verification method should I use?

Enable the strongest option your service offers. Phishing-resistant methods such as supported passkeys or security keys can reduce phishing risk. Keep recovery codes in a protected location. Choose a supported method you can use consistently and recover safely. Stronger phishing resistance is useful, but availability and accessibility differ across providers and patient circumstances.

Ask whether passkeys or security keys are available and learn the approved fallback process. Verification does not prevent every attack: a person can be tricked into approving a malicious request or disclosing a code. Do not treat any method as a guarantee of privacy or evidence that every other safeguard is adequate. Under the current Security Rule, organizations must implement appropriate authentication and security measures in their context; patient-facing methods can vary.

Should I ever share a verification code with someone claiming to be support?

Support staff should not need your password or a one-time sign-in code. If someone asks you to approve a prompt during an unsolicited call, end the call and contact the organization independently. A code or approval prompt can authorize access, not merely confirm that you answered a call. Treat unexpected requests for it as a reason to stop and verify independently.

Use the service’s known recovery route and follow its actual instructions rather than an unsolicited caller’s script. If you already shared a code, promptly tell the legitimate support team, secure the affected email or account and ask about revoking sessions. Keep the facts and timing. The organization should apply its incident procedures where relevant, but your immediate protective action should not depend on having a final determination that a HIPAA-reportable breach occurred.

How do I secure the email and phone used to recover my portal?

Review recovery email addresses, phone numbers and backup codes. Remove obsolete options where the service permits it. A strong portal password helps little if an attacker can reset it through an unprotected email account. If someone else helps you, use the portal’s authorized caregiver features instead of giving them your credentials. The recovery chain can be as important as the portal password. A forgotten shared mailbox or obsolete phone number may still receive a reset even after a new password is chosen.

Remove outdated recovery options where the service allows it and keep backup access information protected. Ask portal support how it verifies recovery requests and how to report a suspicious contact change. If another person assists you, ask about the provider’s authorized proxy features rather than sharing credentials. A password list in ordinary email creates a different risk from a properly scoped caregiver account and can be difficult to unwind after a relationship changes.

What should I do if verification prompts arrive repeatedly without my action?

Do not approve a notification simply to make it stop. Open the service independently and check your sign-in settings. If you already gave a caller a code, tell the service’s real support team and secure the account promptly. Verification adds protection, but a scammer can still trick someone into authorizing a sign-in. Repeated prompts may indicate attempted access or a scam, but the prompt alone does not identify the actor or prove which account information was acquired. Do not approve one just to stop the interruptions.

Open the real service independently and review account settings or contact support. Change compromised or reused credentials and ask how to end suspicious sessions and secure recovery methods. If the account contains health information, report the event through the provider’s appropriate support or privacy channel and keep a case reference. Security incident handling and breach notification are related but separate processes; describe what actually occurred without assuming either that nothing happened or that every record was disclosed.

Sources & further reading

Primary guidance supporting this guide. Follow the linked resources for full requirements, exceptions and current procedures.

Source check: November 19, 2026. Suggested action prompts and examples are educational, not official forms or findings about your situation.

Not sure where to begin?

Request help with a general concern. You do not need to send us your medical history.

Find your next step