What is a covered provider legally responsible for protecting?
A covered provider must apply HIPAA’s privacy requirements to PHI in its custody or within its regulated activities, including appropriate safeguards for spoken, paper and electronic information. Section 164.530(c) requires reasonable safeguards against impermissible uses or disclosures and limits incidental disclosure around otherwise permitted activity. Electronic PHI is also subject to the Security Rule, whose general obligations cover confidentiality, integrity and availability under § 164.306.
This means protection concerns unauthorized viewing and sharing, improper changes, and loss of authorized access. It is not a promise that no error or cyberattack can occur, and a patient cannot determine compliance from one advertised feature alone. Ask which privacy and security contacts handle concerns and what process applies to your situation. If the organization claims HIPAA does not apply, ask it to explain its role and the information involved.
Must the provider assess and reduce security risks?
Yes. Section 164.308(a)(1)(ii)(A) requires an accurate and thorough analysis of risks and vulnerabilities to electronic PHI, and paragraph (B) requires measures to reduce those risks to a reasonable and appropriate level. Other administrative requirements address security responsibility, workforce access, training, incident response and contingency planning. These are organizational duties, not tasks transferred to patients by asking them to choose a strong portal password.
A patient can ask whether an identified weakness has been assessed, what protective action is being taken and how the organization will communicate with affected people. HIPAA does not ordinarily entitle each patient to a full internal risk assessment or sensitive technical diagram. Request an understandable explanation relevant to your information, preserve the response, and use the privacy complaint process if the concern remains unresolved.
Must providers limit who can access patient information?
The Security Rule requires technical access controls and procedures to verify identities, and administrative rules require management of workforce access to electronic PHI. The Privacy Rule’s minimum necessary standard also applies to many uses, disclosures and requests. However, it has express exceptions, including disclosures to or requests by a provider for treatment and disclosures to the individual. These exceptions do not authorize curiosity-driven employee access.
If you suspect someone accessed a record without a legitimate purpose, tell the privacy office the relevant facts and date range and request investigation. Ask how proxy permissions and connected applications are managed as well. Do not assume that knowing a staff member’s name proves wrongdoing, or that a treatment exception removes all safeguards. The organization must assess the actual role, purpose and circumstances under the applicable rules.
Must providers train staff and respond to violations?
Section 164.530(b) requires workforce training appropriate to privacy functions, including training for new workforce members and relevant policy changes within the specified reasonable periods. Paragraph (e) requires appropriate sanctions for workforce noncompliance, subject to the rule’s exceptions. Section 164.308 separately requires a security awareness and training program and a security sanction policy for regulated entities handling electronic PHI.
Patients can reasonably ask that a complaint be documented and routed to the responsible office. They are not automatically entitled to another employee’s personnel file or a particular disciplinary result. Ask what can be shared about the investigation, whether your information was affected and what steps address further risk. A generic statement that staff receive training does not answer a specific, documented concern about unauthorized access or disclosure.
What must the provider do when a privacy or security incident is reported?
The Privacy Rule requires mitigation, to the extent practicable, of known harmful effects of certain impermissible uses or disclosures by the covered entity or its business associate. Security Rule incident procedures require response to suspected or known security incidents, mitigation where practicable, and documentation of incidents and outcomes. Whether an incident also triggers breach notification requires the separate analysis under § 164.402 and related provisions.
Report a concern through a verified privacy or security channel and preserve the case reference. Ask whether the issue is being treated as an access problem, a security incident or a potential breach, and what protective actions are appropriate now. Do not assume an investigation can be ignored merely because the organization has not established that a reportable breach occurred; equally, an incident report is not itself proof of a violation or obligation to notify everyone.
What do providers owe patients after a reportable breach?
Following a breach of unsecured PHI, § 164.404 generally requires notice to affected individuals without unreasonable delay, with 60 calendar days after discovery as the outer limit, subject to § 164.412. The notice must contain the required information in plain language to the extent possible. Separate provisions govern notice to HHS, certain media notifications and reports from business associates to covered entities.
The 60-day limit is not permission to wait automatically until day 60, and the discovery date is not necessarily the date the attack began or appeared in the news. Ask what information about you was involved, what steps to take, how the organization is responding and how to obtain follow-up. Keep your contact information current and verify a notice independently before enrolling in any offered service.
Can providers avoid responsibility by blaming a vendor?
Outsourcing does not erase the covered entity’s applicable HIPAA duties. Business associate rules require appropriate written assurances and contractual provisions for covered functions involving PHI, and business associates have direct responsibilities under specified HIPAA provisions. A vendor may handle records or notifications on a provider’s behalf, but that does not turn a patient’s underlying rights request into something the provider can simply disregard.
Ask the provider who is coordinating the issue, what organization held the affected information and where your access or amendment request should be directed. Keep notices from both organizations and compare the events and dates. Contract terms and agency relationships can affect responsibility in a particular case, so avoid assuming every vendor incident automatically proves provider liability or that a vendor name automatically excuses the provider.
Does a patient’s mistake remove the provider’s legal duties?
No. A patient’s protective choices and an organization’s HIPAA obligations are different parts of the picture. Sharing a password or using an insecure device may contribute to risk, but a provider still must comply with duties applicable to its own handling of PHI, access processes and incident response. Conversely, HIPAA does not generally regulate every copy that a patient independently stores or shares outside a covered relationship.
Explain honestly what happened so the organization can evaluate the facts: for example, whether you approved an unexpected login or sent records to the wrong address. Ask what assistance and investigation are appropriate without accepting a blanket assertion that patients are solely responsible for all subsequent activity. Take account-protection steps promptly and keep a written record of the provider’s explanation and the specific duties or exceptions it relies on.
Sources & further reading
Primary guidance supporting this guide. Follow the linked resources for full requirements, exceptions and current procedures.
- 45 CFR § 164.530
- 45 CFR § 164.306
- HHS — covered entities and business associates
- 45 CFR § 164.308
- HHS — guidance on risk analysis
- 45 CFR § 164.312
- 45 CFR § 164.502
- HHS — minimum necessary requirement
- 45 CFR § 164.402
- 45 CFR § 164.404
- 45 CFR § 164.408
- 45 CFR § 164.410
- 45 CFR § 164.412
- 45 CFR § 164.504
- HHS — business associate requirements
- HHS — health information on personal phones and apps
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