On this page
5 sections
- Privacy obligations and permitted uses
- Security as an operational obligation
- Breach response and notification
- Oversight, enforcement, and accountability
- Articles in this section
General information, not medical advice.
Health information policy governs how protected health information is collected, used, disclosed, stored, accessed, and destroyed. It also determines what organizations must do when information is exposed, lost, stolen, or made unavailable by a cyberattack. The central framework is the Health Insurance Portability and Accountability Act, or HIPAA, including its Privacy Rule, Security Rule, and Breach Notification Rule. The HITECH Act expanded and strengthened that framework, including oversight of electronic health information, breach reporting, and the responsibilities of business associates.
These rules apply most directly to covered entities such as health plans, health care clearinghouses, and health care providers that conduct certain electronic transactions. They also apply to business associates that perform services involving protected health information on behalf of covered entities. The result is a system in which privacy and security obligations follow information through a complex health care ecosystem. A medical practice, hospital, insurer, cloud service provider, billing company, software vendor, or health technology partner may each have distinct responsibilities for the same data.
Privacy obligations and permitted uses
The HIPAA Privacy Rule establishes boundaries around the use and disclosure of protected health information. It permits many activities essential to health care, including treatment, payment, and health care operations, while limiting disclosures that are unnecessary or unrelated to those purposes. It also gives individuals rights to receive notices of privacy practices, inspect and obtain copies of their records, request certain restrictions, and seek corrections to inaccurate information.
Those principles become practical questions in everyday operations. A provider must determine who may access a record, whether a disclosure is permitted, how much information is necessary, and whether an individual request has been handled correctly. A rewards program, digital health product, patient portal, research project, or marketing arrangement may raise different questions about authorization, notice, data sharing, and the boundary between health care and commercial activity.
The rules also matter when an organization changes structure or closes. Records cannot simply be abandoned when a practice ends, a vendor relationship is terminated, or a business is sold. Retention, access, disposal, and patient notification responsibilities may continue after operations change.
Security as an operational obligation
The Security Rule focuses on electronic protected health information and requires covered entities and business associates to implement administrative, physical, and technical safeguards. It is flexible by design, allowing organizations of different sizes and capabilities to assess their own risks and select reasonable and appropriate protections. Flexibility does not mean optional compliance. Organizations must be able to show that they identified risks, adopted policies, trained personnel, controlled access, and responded to known weaknesses.
Security therefore reaches beyond software settings. Risk analysis, workforce training, contingency planning, vendor oversight, facility controls, device management, authentication, encryption, audit controls, and incident response all influence whether an organization can protect information. A portable device may create exposure because it was not encrypted. A phishing message may succeed because staff were not prepared to recognize it. A cloud service may be configured in a way that leaves information accessible to the wrong users. A system may technically record access while the organization fails to review those records.
The Security Rule also treats security as a continuing obligation. Threats change, systems change, and health care operations change. Ransomware, remote work, connected medical devices, application programming interfaces, and strategic partnerships can alter the risk environment without changing the underlying duty to protect information.
Breach response and notification
A breach generally involves an impermissible acquisition, access, use, or disclosure of protected health information that compromises its security or privacy. Determining what happened is only the beginning. Organizations must assess the nature and extent of the information, who received or used it, whether it was actually viewed or acquired, and what steps reduce the likelihood of harm.
Those findings can determine whether notification is required and who must receive it. Depending on the circumstances, notices may be sent to affected individuals, the Office for Civil Rights, and sometimes the media. State breach notification laws may impose additional requirements, and those laws differ in their definitions, deadlines, covered data, and notice procedures. A single incident can therefore trigger overlapping federal and state obligations.
Cyber incidents also test operational judgment. An organization may need to contain an attack, preserve evidence, restore systems, communicate with patients, coordinate with vendors, and continue providing care at the same time. Disaster conditions can affect how ordinary procedures are carried out, but they do not eliminate the need to protect information or document decisions.
Oversight, enforcement, and accountability
The Office for Civil Rights administers and enforces the HIPAA Privacy, Security, and Breach Notification Rules. Its work includes investigations, complaint reviews, audits, guidance, technical assistance, and corrective actions. Enforcement outcomes commonly focus on failures such as inadequate risk analysis, weak access controls, missing policies, insufficient training, delayed response, poor business associate oversight, or failure to investigate and report a breach.
Settlements and corrective action plans show how broad requirements become concrete commitments. An organization may need to revise policies, conduct a formal risk analysis, improve monitoring, train its workforce, test its incident response, or provide periodic reports demonstrating progress. These outcomes make clear that compliance is not limited to having a privacy notice or a written security policy. It depends on whether safeguards operate in practice and whether an organization can identify, address, and learn from failures.
Articles in this section
- A New Year’s Resolution (and Corrective Action Plan) from OCR: Physician Practice Cited for HIPAA Violations
- A phishing email dressed up as an audit notice
- A stolen portable device and an avoidable uncertainty
- Advice to Healthcare Providers on Ransomware from the Head of the FBI
- Audit controls and knowing who looked
- Back to School – HIPAA 101
- Cliff Notes from the Joint OCR/NIST HIPAA Security Conference
- Closing the business does not end the obligation
- Colorado tightens its breach law
- Commercializing a digital health product with strategic partners
- Connected health security is a continuing obligation
- Connecticut and the pharmacy rewards disclosure rule
- Data breaches and audits arriving at once
- Fifty states, fifty breach notification laws
- HIPAA during a disaster, and what bends
- HIPAA guidance for hospitals and health plans using cloud services
- Health law developments worth tracking
- Hollywood Presbyterian Concedes to Hacker’s Demands in Ransomware Attack
- How Medicaid demonstrations can change coverage
- Inside the OIG semiannual report to Congress
- Legal groundwork before building a health app
- Lessons covered entities take from OCR settlements
- OCR Publishes Model Notice of Privacy Practices
- OCR Releases Guidance on Reporting and Monitoring Cyber Threats
- Patching and why healthcare is slow at it
- Proposed lab rules on patient access to results
- Ransomware in healthcare and the importance of availability
- Responding to a bad review without breaking privacy law
- Responding to a cyber attack under HIPAA
- Smaller HIPAA breaches drew more scrutiny
- The audit protocol as a compliance checklist
- The criminal side of HIPAA
- The first round of HIPAA audits
- The long wait for the HIPAA omnibus rule
- The press release that cost $2.4 million
- The privacy problems that keep returning
- The risk assessment nobody had done
- The year health insurers got breached
- Unencrypted laptops remain a costly risk
- What OCR’s breach reports kept showing
- What a global ransomware wave means for health data
- What an unread email reveals about oversight
- When an organization fought a HIPAA penalty and lost
- When attackers impersonated the regulator
- When health privacy rules meet background check reporting
- Who counts as family under HIPAA
- Why HIPAA compliance keeps getting harder
- Why reporting a breach can lead to a broader investigation
- Your right to your own medical records
- After a health data breach, what actually happens
- Arkansas work requirements faced a court challenge
- Breach reporting deadlines and why they tighten
- Building a health app: Where privacy obligations begin
- Business associate agreements deserve more attention
- CMS Finalizes HIPAA and CLIA Amendments Intended to Increase Patient Access to Test Results
- Congress examines responses to the opioid crisis
- Data Breach Nightmare Scenario: News Affiliate Reports Improper Disposal of Patient Information
- Data Breach Wall of Shame: 2013’s Highlights and Lessons
- Federal guidance on sharing patient information
- First OCR Breach Resolution for Less than 500 Patients Shows No Breach is Too Small
- Gun control and HIPAA: What the final rule means for firearm background checks
- HHS OCR Announces First Settlement of a Self-Reported HIPAA Violation
- HIPAA Omnibus Rule Expected Within 90 Days, Pending Review at OMB
- HITECH Data Breach Reporting Deadline Approaches
- Health data privacy at the end of 2015
- How OCR audit notification letters work
- Keeping up with health privacy and security rules
- Law proposal to revive Medicare ID card changes
- Massachusetts proposes changes to medical marijuana rules
- Medicare opens the door to physician payment data
- Mobile devices and health privacy safeguards
- Modernizing Medicare and the patient access problem
- OCR Confirms that Medical Records Should Not be Left in the Driveway
- OCR Shares Preliminary HITECH Audit Results – What Regulated Entities Can Expect Next
- Phase 2 HIPAA audits and who is covered
- Phishing and why it still works
- Practical HIPAA and why compliance fails in ordinary ways
- Removing Social Security numbers from Medicare cards
- Rewriting the rules for research consent
- Security guidance for organizations without security staff
- The FTC covers what HIPAA does not
- The unglamorous half of health data security
- Trends in 1115 Medicaid waivers
- Using the HIPAA breach reporting portal
- What recurring health data breaches reveal
- When health apps asked whether HIPAA applied to them
- When sales representatives saw patient records