New York Data Privacy Law: A SHIELD Decision Record for Therapy Practices
Outline
The full State Records-Release and Privacy Checklist adds a reusable scope decision, regulated-entity evidence list, vendor-contract prompts, and records-release routing sheet. It contains no patient data.
Document your New York data decision
Use the scope, branch, vendor, and records-release sheets to review one practice workflow this week.
- California CMIA Release-Validation Overlay with format, signer, scope, expiration, copy, and return-for-correction checks
- North Carolina Applicability and Release Overlay with Chapter 122C branch, issuer, signer, records, recipient, and revocation fields
- New York OCA 960 Receive, Review, Respond sheet with Item 9(a) scope and Item 9(b) discussion-authority checks
- New York Data-Flow Decision Record and California Website Data-Flow and Policy Acceptance sheet for vendors, tracking, notices, and counsel questions
Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.
Where should we send the link?
We'll email the PDF link right away. You'll also get the therapist toolkit every two weeks. Unsubscribe any time.
✓ Check your inbox
We've sent you the PDF
The download link is on its way to your inbox, usually within a minute or two. The email will come from Emosapien (hello@team.emosapien.com); check your spam folder if you don't see it.
You're also on the therapist toolkit list, sent every two weeks. Unsubscribe any time from the email footer.
This page is educational guidance, not legal, tax, insurance, licensing, or breach-response advice. Facts and official statuses on this page were checked in November 2026. The New York statute, agency guidance, and legislative status can change. Confirm a live incident, contract, or unresolved interpretation with qualified New York counsel and the relevant authority.
Start with the SHIELD scope question
New York data privacy law is a scope-and-evidence decision for a therapy practice, not a generic privacy badge. The Stop Hacks and Improve Electronic Data Security Act, commonly called the SHIELD Act, was signed on July 25, 2019. General Business Law section 899-bb(2)(a) applies to any person or business that owns or licenses computerized data containing private information of a New York resident. The question is not whether your practice calls itself a therapy practice. The question is what computerized data you own or license and what the current statutory definition captures.
Section 899-aa defines private information as personal information combined with listed data elements, subject to the statute’s encryption language. The current official text includes medical information, meaning information about an individual’s medical history, mental or physical condition, medical treatment, or diagnosis by a health care professional. It also includes health insurance information, such as a policy or subscriber identifier and certain application or claims history. That current text is the source used here, rather than relying only on an older Attorney General summary that lists a narrower set of examples. This is the New York data privacy law scope question your data map must answer before a share.
For a concrete therapy-record flow, inventory the fields, locations, and recipients before you decide that the rule is irrelevant. A release packet, claim attachment, intake export, session note, or support ticket may have a different data path. If a proposed flow contains no New York resident private information as defined by section 899-aa, record why it is out of scope. If it does, continue to the 899-bb branch.
Emosapien’s how Emosapien works page can help you understand a session-documentation workflow, but it does not answer your New York legal analysis. Keep the statutory scope decision with your practice’s own facts.
Choose and document the 899-bb branch
Section 899-bb(2)(b) describes two routes for being deemed in compliance with the reasonable-security requirement: the compliant-regulated-entity route or a data-security program with administrative, technical, and physical safeguards. The first route is not a slogan. Section 899-bb(1)(a) defines a compliant regulated entity as a person or business subject to and in compliance with specified data-security requirements, including HIPAA and HITECH requirements.
A HIPAA covered-entity label does not prove the route. A signed business associate agreement does not prove the route. A vendor’s security badge does not prove the route. Record the applicable regime, the practice’s compliance evidence, the relevant systems, and the person who approved the conclusion. If the evidence does not establish that route, document the safeguards route instead of borrowing the label.
| Decision point | What to record | Stop or route condition |
|---|---|---|
| New York resident data | State whose residents’ information is in the computerized flow | Confirm the resident and data elements before sharing |
| Private-information element | Medical, health insurance, credential, biometric, financial, or other section 899-aa element, with encryption facts | Confirm against the current statutory text |
| Ownership or licensing | Whether the practice owns or licenses the computerized data | Route an unclear custody or licensing fact to counsel |
| Compliant-regulated-entity path | Regime that applies and evidence the practice is subject to and in compliance with it | Do not rely on a title, BAA, or vendor badge alone |
| Safeguards path | Administrative, technical, and physical safeguards selected for the practice | Keep the reason, owner, test, and review date |
The statute defines a small business using alternative thresholds: fewer than 50 employees, less than $3 million in gross annual revenue in each of the last three fiscal years, or less than $5 million in year-end total assets calculated under generally accepted accounting principles. That definition does not erase the security requirement. For a small business using the safeguards route, section 899-bb(2)(c) scales reasonable safeguards to the business’s size and complexity, its activities, and the sensitivity of the personal information. This New York data privacy law branch needs a written owner and review date, even when the practice is small.
| Safeguard area | New York-specific work product | Evidence to retain |
|---|---|---|
| Administrative | Name a security owner, identify foreseeable risks, assess safeguards, train staff, and adjust for change | Owner record, risk decision, training log, review history |
| Service providers | Select capable providers and require appropriate safeguards by contract | Contract clause, provider evidence, renewal review |
| Technical | Assess processing, transmission, storage, network and software risks; test key controls | Data-flow review, control test, correction log |
| Physical and disposal | Protect access during collection, transportation, destruction, and disposal; erase electronic media so data cannot be read or reconstructed | Access review, disposal method, destruction log |
Generic HIPAA risk analysis, access, retention, and vendor checklists belong on the HIPAA compliance checklist page. This New York page adds the state-specific branch and the short decision record that explains why your practice used one route rather than the other.
For the wider privacy and security workflow, use the therapy practice compliance hub to find related federal and state guidance.
Keep the vendor and data-flow evidence together
Map one ordinary flow from collection through disposal. Name the practice account, clinician device, vendor environment, support path, subprocessors, backup, export, and deletion step. For each step, write the information category, who can access it, the purpose, the safeguard, and the evidence location. Do not put real patient content into the worksheet.
The contract record should show the provider’s permitted handling, confidentiality, access controls, incident cooperation, return or deletion process, and required safeguards. Section 899-bb specifically names selecting capable service providers and requiring appropriate safeguards by contract. A sales response can inform the review, but the contract and technical evidence should carry the decision.
Keep the following with the decision record:
- The date and version of the data-flow map
- The section 899-aa scope analysis and encryption facts
- The 899-bb compliant-regulated-entity analysis or scaled safeguards plan
- The service-provider contract and current subprocessor evidence
- Control tests, access reviews, disposal reviews, and corrections
- The decision owner, review trigger, and unresolved questions
- A written route for ordinary record-release authorization questions
Ordinary authorization work is not the same as the SHIELD security analysis. Before releasing records, identify the legal basis, identity, recipient, scope, and disclosure record required by the rules that apply to your practice; HIPAA authorization is required when the Privacy Rule does not otherwise permit or require the disclosure. Do not treat a release authorization as permission to skip the data-security branch, and do not treat this page as a substitute for a records-release policy.
When session notes come up in your data map, see how notes are drafted and reviewed. The clinician remains responsible for reviewing and signing a note. A documentation tool does not decide whether your New York practice may collect, use, disclose, retain, or destroy a specific record.
Separate enacted SHIELD duties from pending bills
This page does not present NYHIPA as current law. The official New York Senate page lists 2025-S929 as vetoed by the Governor on December 19, 2025. It lists 2025-S9269 as Passed Senate & Assembly, with the last listed action shown as June 4, 2026. No signed status was verified for S9269 for this page. Legislative passage and a bill title that says “Act” do not establish enactment.
Do not add pending-bill consent duties, effective dates, authorization deadlines, or a new comprehensive privacy-law checklist to your current SHIELD decision. If your practice may be affected by a bill, record the bill number, current official status, and question for counsel. Recheck the official Senate page before acting.
The New York breach statute has its own definitions, notice provisions, exceptions, and agency reporting framework. This page does not summarize a breach timeline for an incident. Do not infer that HIPAA compliance eliminates every New York breach or reporting duty. Preserve evidence and contact qualified breach-response counsel and the relevant authorities when an incident occurs.
Choosing tools that respect these rules
A tool can support a documented workflow without becoming your legal conclusion. If you evaluate a session-note workflow, start with fictional material, confirm who can access the draft, require clinician review and signature, and retain the result of your practice’s own security and contract review. Emosapien can draft therapy notes from a session for clinician review and signature, but it is not an EHR or practice-management system and does not make a practice compliant with New York law. That boundary is part of a careful New York data privacy law review, not a substitute for it.
See clinician-reviewed session notes
Test a fictional workflow, review the AI-drafted note, and keep the final clinical decision with the clinician.
Try it safely- Free plan
- No credit card
Test record
A fictional client describes a difficult week and asks for a coping plan.
Clinician review
Draft ready for review and signature.
References
- New York Senate. General Business Law section 899-bb, Data security protections (official text accessed and facts checked November 2026).
- New York Senate. General Business Law section 899-aa, breach notification and private-information definitions (official text, revision March 28, 2025, accessed and facts checked November 2026).
- New York Attorney General. SHIELD Act (official guidance, accessed and facts checked November 2026).
- New York Senate. 2025-S929 (official status page, vetoed December 19, 2025, checked November 2026).
- New York Senate. 2025-S9269 (official status page, last listed action June 4, 2026, checked November 2026; signed status not verified).
Related reading
42 CFR Part 2 Therapy Guide: Consent and Mixed Records
42 CFR Part 2 therapy after the 2024 final rule: program status, TPO consent, redisclosure notices, SUD counseling notes, and mixed-record checks.
Read article →ACA Ethical Codes: Principles and Section-by-Section Practice Guide
Use the ACA ethical codes as a practice guide. Match each ACA Code of Ethics section to the counseling decision in front of you.
Read article →Free PDF: State Records-Release and Privacy Checklist
A seven-page worksheet pack for validating California, North Carolina, and New York records releases, plus New York and California website and vendor data flows.
- California CMIA Release-Validation Overlay with format, signer, scope, expiration, copy, and return-for-correction checks
- North Carolina Applicability and Release Overlay with Chapter 122C branch, issuer, signer, records, recipient, and revocation fields
- New York OCA 960 Receive, Review, Respond sheet with Item 9(a) scope and Item 9(b) discussion-authority checks
- New York Data-Flow Decision Record and California Website Data-Flow and Policy Acceptance sheet for vendors, tracking, notices, and counsel questions
Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.
Where should we send the link?
We'll email the PDF link right away. You'll also get the therapist toolkit every two weeks. Unsubscribe any time.
✓ Check your inbox
We've sent you the PDF
The download link is on its way to your inbox, usually within a minute or two. The email will come from Emosapien (hello@team.emosapien.com); check your spam folder if you don't see it.
You're also on the therapist toolkit list, sent every two weeks. Unsubscribe any time from the email footer.