Any health data program has to be built on a regulatory foundation, and for us, that’s the HIPAA Security Rule. It isn’t just a suggestion. Complying with its provisions is the absolute floor for protecting electronic protected health information (ePHI).
HIPAA Security Rule Requirements
The rule breaks down into three main buckets of safeguards that every covered entity and their business associates have to put in place. The whole point is to guarantee the integrity, confidentiality, and availability of ePHI, meaning the data is accurate, only seen by authorized people, and accessible when it’s needed. You achieve this through a continuous cycle of risk analysis and management, which isn’t a one-and-done task but the core engine of your security program.
- Administrative Safeguards: This is the paperwork and process layer, things like having formal security management processes (including a documented risk analysis), assigning a specific person to be in charge of security, implementing workforce security policies, managing who can access what information, running security awareness training, and having a ready-to-go plan for security incidents.
- Physical Safeguards: These are the locks and keys. They cover controlling physical access to facilities where ePHI is stored, setting rules for how workstations are used and secured, and managing controls for devices and media like laptops or backup drives.
- Technical Safeguards: This is the digital layer, covering access controls like unique user IDs, audit controls to log and review activity on systems, integrity controls to prevent data tampering, and transmission security like encryption when data is moving across a network.
Historically, the rule has been flexible, letting organizations scale their security measures to their size, what works for a huge hospital system isn’t what a small clinic can manage. But that ‘scalability’ doesn’t mean you can ignore the core requirements. They apply to everyone. Now, that flexibility is on its way out. A big change is coming down the pipe with a Notice of Proposed Rulemaking from December 2024. HHS is looking to kill the difference between “required” and “addressable” specs by a target date of July 2027, which effectively makes almost everything mandatory for everyone. For the nitty-gritty details on the current rules, the HHS HIPAA Security Rule guidance from HHS is still the best source.
Device Context and FDA CDRH Record
When you’re dealing with medical devices, the FDA’s Center for Devices and Radiological Health (CDRH) has its own set of expectations that line up pretty well with the HIPAA Security Rule. For a device, and especially for Software as a Medical Device (SaMD), security has to be baked into the product itself with things like encryption and secure boot processes. The security is part of the device’s formal record, which is a world away from a typical consumer app where security is often just a marketing promise in the terms of service.
The FDA’s guidance makes it clear that cybersecurity isn’t a one-time check. It’s a continuous job across the device’s entire lifecycle, from design to decommissioning. You have to document your cyber controls in your premarket submission, and then you’re on the hook for postmarket surveillance to watch for new vulnerabilities. If a device can be hacked, it can harm a patient, so the FDA treats security as a direct component of patient safety. Their updated guidance from 2025 and again in February 2026 gets into the weeds on this, pushing for formal threat modeling (thinking through how an attacker might break your device) and having a real plan for vulnerability management. Most of this work gets done inside a Quality Management System (QMS) built on ISO 13485:2016, which is even more important now that the FDA’s Quality Management System Regulation (QMSR) formally points to ISO 13485 as the standard as of February 2, 2026. You can find the specifics in the FDA medical device cybersecurity guidance.
Genetics Program Context: 23andMe and Ambry Genetics
Consumer genetics is a tricky area. Companies like 23andMe aren’t typically HIPAA covered entities, but they often make public commitments to protect data with HIPAA-like standards. The problem is, the real test of those promises often comes after a disaster. Look at 23andMe: after a huge data breach in 2023, the company ended up in Chapter 11 bankruptcy by March 2025, with its assets sold to TTAM Research Institute in July 2025 (thankfully, with commitments to uphold the original privacy policies). When a company isn’t under HIPAA, the Federal Trade Commission (FTC) is often the one to step in and enforce the privacy promises they made to their customers, as their FTC consumer privacy enforcement actions show.
On the other side you have a company like Ambry Genetics, which is a clinical lab and absolutely a HIPAA covered entity. For them, there’s no ambiguity, they have to follow the HIPAA Security Rule to the letter. Genomic data is about as sensitive as it gets, so the need for stringent controls like end-to-end data encryption, strict access controls to see who can view what, and detailed audit trails isn’t just best practice. It’s a hard requirement to stop unauthorized access and make sure the data hasn’t been tampered with. The consequences for failure are real: in September 2026, Ambry Genetics got hit with a $700,000 settlement from the HHS Office for Civil Rights (OCR) for Security Rule violations from a 2020 phishing incident that exposed data on over 225,000 people. The different stories of 23andMe and Ambry show how health data programs face very different, but related, regulatory pressures depending on whether they’re consumer-facing or clinical.
Baseline for Privacy Reviews
When you’re reviewing a health data program, you start with the black-and-white text of the governing rule, not some feel-good policy written for the company’s website. The HIPAA Security Rule is that baseline. A program is only as strong as its actual, documented adherence to that rule’s specific requirements. There’s nothing glamorous about it. Effective health data privacy is a discipline built on a consistent pattern of checking your work, monitoring for new threats, and adapting your controls. So the privacy officer’s job isn’t to ask abstract questions. It’s to answer one very concrete one: does this program actually meet the mandated security standards or not?
Frequently Asked Questions
What is the foundational regulatory framework for health data programs?
The HIPAA Security Rule establishes the foundational regulatory framework for health data programs. It defines the minimum acceptable standard for protecting electronic protected health information (ePHI).
What are the three main categories of safeguards mandated by the HIPAA Security Rule?
The HIPAA Security Rule mandates administrative, physical, and technical safeguards for ePHI. These include security management processes, facility access controls, and access control for electronic systems, respectively.
How does the FDA’s approach to medical device cybersecurity align with the HIPAA Security Rule?
The FDA Center for Devices and Radiological Health (CDRH) record aligns with HIPAA Security Rule expectations by requiring robust security measures for medical devices, especially Software as a Medical Device (SaMD). The FDA views device security as integral to patient safety and mandates cybersecurity controls throughout the total product lifecycle.
Are consumer genetics companies like 23andMe directly subject to HIPAA?
Consumer genetics companies like 23andMe are generally not directly subject to HIPAA as covered entities. However, they frequently commit to HIPAA-like protections, and the Federal Trade Commission (FTC) enforces privacy promises made to consumers, particularly concerning health-related data shared by non-HIPAA entities.
What is the core question for any privacy review regarding health data programs?
The core question for any privacy review remains: does the program meet the mandated security standards of the HIPAA Security Rule? Compliance requires continuous monitoring and adaptation to evolving threats to ensure adherence to these specific requirements.