Healthcare organisations should map each data flow to determine whether it is protected health information or separate personal information subject to CPRA. PHI may remain exempt, but employee data, website data, and other non-PHI records still need CPRA notices, rights handling, and opt-out processes. The practical test is scope, not entity status, so governance must follow the data, not the business label.
How to separate PHI from CPRA-covered personal information in a healthcare organisation
The cleanest approach is to classify by data flow, not by business unit. A patient record may be PHI, while HR files, website analytics, vendor contact details and some patient-adjacent records can still be personal information under CPRA. That means the same organisation can have both HIPAA and CPRA obligations at once, depending on the dataset and purpose.
Start by defining where the data comes from, why it is collected, who receives it and whether any HIPAA exemption actually applies to that specific record set. The practical test is whether the information is part of a HIPAA-covered workflow or whether it sits outside that scope and therefore needs CPRA handling such as notices, access response and opt-out support.
For the data map to be useful, it should separate patient care systems from employee systems, marketing tools, web tracking, recruiting platforms and third-party services. That separation is what lets you apply different notices, retention rules and rights workflows without overextending HIPAA logic to records that are outside PHI scope.
Why scope-based mapping matters more than entity-based assumptions
A healthcare brand does not automatically make every dataset exempt from CPRA. Organisations often over-assume that because they are covered by HIPAA, all personal data they hold is treated the same way. In practice, the legal status changes with context, so the control model has to follow the specific record, process and purpose.
That distinction matters operationally because a single system can hold both PHI and non-PHI data. For example, a patient portal may contain PHI, but the marketing platform that records ad clicks, cookie identifiers or form submissions may be separate personal information with its own notice and rights obligations. A sound map prevents those categories from being merged just because they are stored by the same enterprise.
It also prevents the opposite mistake, which is treating everything as CPRA-covered personal information and applying one generic response workflow everywhere. That usually creates confusion about request handling, retention, disclosure obligations and system ownership, especially when legal, privacy, security and business teams each assume someone else already classified the flow.
What a workable governance split looks like in practice
The right operating model is to assign each system or dataset a primary legal class and then attach the required controls to that class. PHI workflows should stay aligned to HIPAA security, access and disclosure controls, while non-PHI personal information should be routed through CPRA notices, consumer rights intake, opt-out handling and vendor management.
That usually means building a shared inventory that records the data category, source, purpose, storage location, recipients and applicable legal regime. Once that inventory is current, teams can apply different procedures for patient data, employee data and web data without needing separate programs for every department.
Data mapping and records of processing are the practical foundation here, because the privacy split only works when the organisation can show where each flow starts and stops. For healthcare teams, that inventory should also be consistent with the segregation principles discussed in the healthcare identity security guide when access paths span clinical, employee and third-party systems.
Risk and Threat Considerations
Mixing PHI and CPRA-covered personal information in one undifferentiated process creates legal and operational exposure. The usual failure is not a single catastrophic breach, but a slow control drift where notices, rights handling and retention rules are applied inconsistently across systems that should have been separated from the start.
Failure mechanism: Teams assume HIPAA coverage is organisation-wide, so they skip CPRA scoping for employee data, web data or vendor records, then miss requests or notices that should have been handled outside the PHI workflow.
Impact: The organisation can end up with misrouted consumer requests, incomplete disclosures, inconsistent retention, and avoidable regulatory exposure because data governance followed the business label instead of the actual data class.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the technical controls, while GDPR and ISO/IEC 27001:2022 define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| GDPR | Art.5 — Principles Relating to Processing of Personal Data | Data-flow scoping and classification depend on limiting processing to the right legal basis and purpose. |
| Recommendation — Classify each flow by purpose and apply separate handling for data outside the exempt scope. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Separating PHI from other personal data requires distinct access paths and controlled exposure. |
| Recommendation — Separate access rules for PHI and non-PHI datasets by role and purpose. | ||
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | Different legal classes need enforced access boundaries so rights and disclosures do not bleed across systems. |
| AU-6 — Audit Review, Analysis, and Reporting | Mixed PHI and CPRA workflows need logs that show which path handled each request or disclosure. | |
| Recommendation — Enforce dataset-specific access decisions instead of relying on one enterprise-wide rule. Review audit logs to confirm each request was processed under the correct privacy regime. | ||
| NIST CSF 2.0 | ID.IM-01 — Improvements are identified and acted on by stakeholders to reduce cybersecurity risk | Data mapping is an ongoing improvement activity that keeps privacy scope decisions current. |
| Recommendation — Update data maps and rights workflows whenever systems, vendors or data uses change. | ||
Practitioner Guidance
What to verify: Confirm that each major system has one named owner, one documented legal classification and one documented exception path. If a team cannot say whether a flow is PHI, non-PHI personal information or both in different stages, the classification is not ready for operational use.
Decision rule: If the data can identify a person but is not part of treatment, payment, healthcare operations or another HIPAA-covered use, treat it as a separate privacy workflow until proven otherwise. That is especially important for HR, recruiting, marketing, analytics and customer-support tooling where healthcare organisations often inherit non-PHI obligations without noticing.
Practitioner takeaway: The safest model is not “HIPAA first, CPRA second”, but “classify the flow first, then apply the correct regime to each dataset.”
Related resources from NHI Mgmt Group
- Guide: CCPA and CPRA
- Covered Data
- How should organisations assess whether pseudonymized data is still personal data under GDPR?
- How should healthcare organisations classify data to determine what counts as PHI under HIPAA?
- How should organisations apply a risk-based approach when implementing cybersecurity controls for personal data under CPRA?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org