New York is one of the states where HIPAA compliance alone rarely closes out an organization’s obligations. The SHIELD Act imposes data security and breach notification duties that reach beyond PHI, health insurers and some other entities answer to the Department of Financial Services (DFS), and state health law adds its own confidentiality and access rules.
We help providers, health plans, business associates and digital health companies that serve New York residents build a single program that satisfies HIPAA and accounts for these state-level requirements, working alongside their legal counsel on interpretation.
Key points
- The SHIELD Act covers "private information" of New York residents, which overlaps with but is not identical to PHI.
- HIPAA-compliant entities get some relief under SHIELD, but regulator notice obligations can remain.
- DFS Part 500 applies only to DFS-regulated entities — many providers are not, many insurers are.
- Track pending New York health privacy legislation; its status should be verified before planning around it.
How we serve New York clients
Engagements for New York organizations run remotely, using the same evidence-based methodology we apply nationwide, with on-site visits for facility walkthroughs or leadership workshops arranged when useful. The New York-specific value is in the state-law overlay: identifying where SHIELD, DFS rules or state health law change what your HIPAA program needs to do.
The SHIELD Act: data security and breach notification
New York’s Stop Hacks and Improve Electronic Data Security (SHIELD) Act amended the state’s breach notification law (General Business Law §899-aa) and added a data security requirement (GBL §899-bb). It applies to any person or business that owns or licenses computerized "private information" of New York residents — regardless of where the business is located.
"Private information" under SHIELD includes certain combinations of personal identifiers with Social Security numbers, account numbers, biometric data and online credentials. Medical and health insurance information has also been added to the definition by later amendments; verify the current statutory definition with counsel.
Data security relief for HIPAA-regulated entities
SHIELD’s reasonable-safeguards requirement treats entities that comply with certain federal regimes, including HIPAA, as compliant with the state data security standard. That relief depends on actually complying with HIPAA — which in practice means a current risk analysis, a risk management plan and implemented safeguards under §§164.308–164.312. It is an incentive to keep your HIPAA program real, not a reason to ignore the state law.
Breach notification overlap
Where a HIPAA covered entity notifies affected individuals under HIPAA, SHIELD generally does not require a second individual notice for the same breach. However, notice to New York state regulators — including the Attorney General — can still be required, and SHIELD has provisions requiring HIPAA covered entities to provide the state with a copy of breach notices given to HHS within a short window. New York has also amended its notification timelines in recent years. Confirm current deadlines with counsel and build them into your incident response plan.
DFS Part 500: only if you are DFS-regulated
The DFS cybersecurity regulation (23 NYCRR Part 500) applies to entities licensed or chartered by the Department of Financial Services — for example, many insurers and some health plans operating in New York. It does not apply to a typical physician practice, hospital or health IT vendor simply because they handle New York patient data.
If you are DFS-regulated, Part 500 has prescriptive requirements — such as a cybersecurity program, a designated CISO, multi-factor authentication requirements and annual compliance filings — that go well beyond HIPAA’s technology-neutral Security Rule. Whether your organization is a covered entity under Part 500, and whether any exemption applies, is a question for your counsel. Vendors to DFS-regulated plans may also face Part 500-driven requirements through contract.
| Topic | HIPAA Security Rule | DFS Part 500 (if applicable) |
|---|---|---|
| Who it covers | Covered entities and business associates | DFS-licensed or chartered entities |
| Risk assessment | Required risk analysis, §164.308(a)(1)(ii)(A) | Required periodic risk assessment |
| Multi-factor authentication | Recommended practice under the current rule | Specified requirements |
| Regulator filing | No routine annual filing | Annual compliance certification or acknowledgment |
| Approach | Flexible, scalable, risk-based | More prescriptive control set |
New York health information considerations
New York health law adds confidentiality protections for specific categories of information — for example HIV-related information and certain mental health records — that can be more stringent than HIPAA and therefore not preempted under 45 CFR §160.203. Patient access to records is also addressed in state law. These rules typically affect release-of-information workflows, consent forms and EHR access controls more than they affect your IT security program.
Practically, we look for three things: whether your consent and authorization forms reflect New York-specific requirements, whether your release-of-information team knows which record types need extra handling, and whether your EHR can segment or flag sensitive information. Legal conclusions on specific record types should come from counsel.
Pending New York health privacy legislation
The New York legislature has considered a broad health information privacy bill — often referred to as the New York Health Information Privacy Act — aimed at consumer health data held by entities outside HIPAA, such as apps and wellness companies. Its enactment status, effective date and final scope have been uncertain. Verify its current status before relying on any summary, including this one.
If your organization is a digital health company that handles New Yorkers’ health data outside a HIPAA relationship, this is a priority to watch. Our HIPAA compliance for mobile apps guide explains how to tell whether HIPAA applies in the first place.
Building a New York-ready HIPAA program
- 1
Confirm which regimes apply
Determine whether you are a covered entity, business associate, DFS-regulated entity or none of these, and which data falls under SHIELD.
- 2
Run or refresh the risk analysis
A current HIPAA security risk assessment supports both HIPAA and the SHIELD safe harbor.
- 3
Add a New York section to incident response
Document state regulator notices, timelines and who signs off, alongside HHS and individual notices.
- 4
Review consent and release workflows
Flag record types with heightened New York protections and train release-of-information staff accordingly.
- 5
Align vendor contracts
Update business associate agreements and security addenda, especially where DFS-regulated clients flow down Part 500 expectations.
Frequently asked questions
Does the SHIELD Act apply to us if we are based outside New York?
It can. SHIELD applies to businesses that own or license private information of New York residents, regardless of where the business is located. Confirm applicability with counsel.
If we are HIPAA compliant, do we satisfy SHIELD?
Partly. SHIELD treats HIPAA-compliant entities as meeting its data security requirement, but state regulator notice obligations after a breach can still apply. The relief also depends on genuinely complying with HIPAA, not just having policies on paper.
Is our medical practice subject to DFS Part 500?
Most medical practices are not, because Part 500 applies to entities licensed or chartered by DFS. Health insurers and certain plans often are. Your counsel should confirm your status.
Has the New York Health Information Privacy Act taken effect?
Its status has been uncertain, so verify it directly with the New York legislature’s records or your counsel before planning around it. We track it as a watch item for clients handling consumer health data.
Authoritative sources
- HHS — Preemption of state law (HIPAA FAQs)
- New York State Attorney General
- New York Department of Financial Services
- HHS — Breach Notification Rule
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.