Healthcare AI Privacy — HIPAA and AI Act Intersection
Overview
Artificial intelligence in healthcare introduces privacy challenges that sit at the intersection of established health privacy law (HIPAA, HITECH) and emerging AI regulation (EU AI Act, FDA regulatory framework, proposed state AI laws). Clinical decision support (CDS) systems, diagnostic AI, and predictive analytics operate on protected health information, creating obligations under HIPAA while simultaneously falling within the scope of AI-specific regulation when deployed in high-risk clinical contexts. This skill addresses the complete privacy lifecycle of healthcare AI — from training data acquisition through model deployment and patient interaction — ensuring compliance with both health privacy and AI governance frameworks.
Regulatory Landscape
Overlapping Regulatory Frameworks
| Framework |
Applicability to Healthcare AI |
Key Requirements |
| HIPAA Privacy Rule (45 CFR §164) |
AI systems processing PHI at covered entities or BAs |
Authorization or TPO exception for PHI use; minimum necessary; individual rights |
| HIPAA Security Rule (45 CFR §164.312) |
ePHI used in AI training, inference, and storage |
Access controls, audit trails, encryption, integrity controls |
| EU AI Act (Regulation 2024/1689) |
AI systems deployed in EU healthcare or processing EU patient data |
High-risk classification for medical devices; conformity assessment; transparency |
| FDA Regulatory Framework |
AI/ML-based Software as a Medical Device (SaMD) |
510(k), De Novo, or PMA pathway; GMLP (Good Machine Learning Practice); total product lifecycle approach |
| FTC Act §5 |
AI making health-related decisions affecting consumers |
Unfair or deceptive practices; Health Breach Notification Rule for non-HIPAA entities |
| State AI Laws |
Emerging state legislation (Colorado AI Act SB24-205, Illinois AI Video Interview Act) |
Algorithmic impact assessments; notice and opt-out for automated decisions |
EU AI Act High-Risk Classification for Healthcare AI
Under Annex III of the EU AI Act, the following healthcare AI systems are classified as high-risk:
| Category |
AI Act Reference |
Examples |
| Medical devices (AI-based) |
Annex III, §5(a) |
AI diagnostic imaging (radiology, pathology, dermatology), AI-assisted surgery planning |
| In vitro diagnostic medical devices (AI-based) |
Annex III, §5(a) |
AI-based genetic analysis, AI companion diagnostics |
| Safety components of medical devices |
Annex III, §5(b) |
AI monitoring in ICU, AI-driven infusion pump dosing |
High-risk AI systems must comply with AI Act requirements including risk management (Art. 9), data governance (Art. 10), transparency (Art. 13), human oversight (Art. 14), accuracy/robustness (Art. 15), and conformity assessment (Art. 43).
Training Data PHI Handling
Lawful Basis for Using PHI in AI Training
| Lawful Basis |
HIPAA Provision |
Applicability |
Conditions |
| Treatment |
§164.506(c)(1) |
AI models trained to support individual patient treatment decisions |
Model must directly serve treatment function; minimum necessary applies |
| Healthcare Operations |
§164.506(c)(4) |
Quality assessment, population health analytics, clinical decision support development |
Must qualify as healthcare operations under §164.501 definition |
| Research |
§164.512(i) |
Academic or institutional research developing AI models |
IRB/Privacy Board approval; authorization or waiver of authorization; data use agreement for limited datasets |
| De-identified data |
§164.514(a) |
Training on data that meets safe harbor or expert determination de-identification |
No HIPAA restrictions once properly de-identified; re-identification risk from AI model memorization must be assessed |
| Authorization |
§164.508 |
Individual authorization for specific AI training use |
Valid authorization meeting §164.508(c) requirements; may be impractical at scale |
Asclepius Health Network AI Training Data Governance
Asclepius Health Network has established an AI Data Governance Committee that reviews all AI training data requests:
Training Data Request Workflow:
- Purpose documentation: AI development team submits purpose statement, model description, data elements needed, and lawful basis justification
- Minimum necessary review: Privacy Office reviews requested data elements against stated purpose; removes unnecessary fields
- De-identification assessment: For models that do not require identifiable data, the de-identification team applies safe harbor or coordinates expert determination
- Data use agreement: For limited datasets used in AI development, a DUA is executed specifying permitted uses and prohibiting re-identification attempts
- Security requirements: AI training environment must meet Security Rule requirements — encrypted storage, access-controlled compute environment, audit logging of all data access
- Model memorization testing: Before deployment, models are tested for training data memorization using membership inference and data extraction attacks
- Data retention: Training data copies are deleted within 90 days of model finalization; only the trained model weights are retained
AI-Specific PHI Risks
| Risk |
Description |
Mitigation |
| Training data memorization |
Large models (transformers, LLMs) can memorize and reproduce verbatim training data including PHI |
Differential privacy (DP-SGD), training data deduplication, memorization testing pre-deployment |
| Membership inference |
Adversary determines whether a specific patient's data was in the training set |
Output perturbation, model regularization, membership inference attack testing |
| Model inversion |
Adversary reconstructs patient features from model outputs |
Limit output granularity, add noise to confidence scores, restrict API access |
| Attribute inference |
Model reveals sensitive attributes (HIV status, substance use) not provided as input |
Feature correlation analysis, fairness-aware training, output filtering |
| Training data leakage via model explanation |
SHAP/LIME explanations may reveal individual patient contributions |
Aggregate explanations; use synthetic examples for patient-facing explanations |
Model Transparency and Explainability
HIPAA Transparency Requirements
While HIPAA does not explicitly address AI transparency, several provisions create de facto transparency obligations:
- Notice of Privacy Practices (§164.520): Must describe how PHI is used — if PHI is used in AI systems for treatment or operations, the NPP should disclose this
- Right of Access (§164.524): Patients have the right to access their designated record set, which may include AI-generated assessments, risk scores, and recommendations stored in the medical record
- Minimum Necessary (§164.502(b)): AI systems accessing PHI must be limited to the minimum necessary data elements
EU AI Act Transparency Requirements for Healthcare AI
For high-risk healthcare AI systems under the AI Act:
| Requirement |
AI Act Article |
Implementation |
| Technical documentation |
Art. 11 |
Complete description of AI system including training methodology, data governance, performance metrics, known limitations |
| Record-keeping |
Art. 12 |
Automatic logging of AI system operations enabling traceability |
| Transparency to users |
Art. 13 |
Instructions for use enabling healthcare providers to interpret outputs and exercise oversight; disclosure of performance metrics, known biases, and foreseeable misuse |
| Human oversight |
Art. 14 |
AI systems designed to be effectively overseen by natural persons; override capability; ability to disregard AI output |
| Accuracy and robustness |
Art. 15 |
Declared accuracy levels; resilience against errors, faults, and adversarial attacks |
Asclepius Health Network AI Transparency Framework
For each deployed AI system, Asclepius maintains:
Model Card (following the Mitchell et al. framework, adapted for healthcare):
- Model name, version, deployment date
- Intended clinical use and patient population
- Training data description (source, size, demographics, time period — using aggregate statistics, not individual PHI)
- Performance metrics disaggregated by demographic subgroups (age, sex, race/ethnicity, insurance type)
- Known limitations and failure modes
- Fairness evaluation results
- Human oversight requirements (which clinical decisions require physician review)
- Data privacy measures implemented (de-identification method, differential privacy parameters, access controls)
Patient-Facing Disclosure:
- Asclepius NPP includes disclosure that AI/ML tools may be used in treatment and healthcare operations
- Individual AI-generated recommendations in the patient portal include a notation identifying them as AI-assisted
- Patients may request information about AI systems used in their care through the Privacy Office
Patient Rights in Algorithmic Healthcare Decisions
HIPAA-Based Rights
| Right |
Application to Healthcare AI |
Asclepius Implementation |
| Right of Access (§164.524) |
Patient may access AI-generated risk scores, predictions, and recommendations in their medical record |
AI outputs stored in EHR are accessible through the patient portal; explanations provided in plain language |
| Right to Amend (§164.526) |
Patient may request amendment of AI-generated entries if believed to be inaccurate |
AI-generated entries clearly labeled; amendment requests reviewed by treating physician and AI governance committee |
| Right to Accounting of Disclosures (§164.528) |
AI system disclosures of PHI (e.g., to a cloud-based AI service) must be tracked |
All API calls to AI inference services logged; BA disclosures tracked in disclosure accounting system |
| Right to Restrict (§164.522) |
Patient may request restrictions on AI processing |
Asclepius honors requests to exclude specific data from AI-assisted analytics where clinically feasible |
Automated Decision-Making Considerations
HIPAA does not include a direct analog to GDPR Article 22 (right not to be subject to automated decision-making). However:
- Clinical standard of care: AI-only decisions without physician oversight may constitute substandard care under state medical practice acts
- Informed consent: State informed consent laws may require disclosure that AI was used in diagnosis or treatment recommendations
- Anti-discrimination: AI decisions that disproportionately affect protected groups may violate the ACA §1557 (non-discrimination in healthcare programs), CRA Title VI, or ADA
- FDA regulation: AI/ML SaMD must meet safety and effectiveness standards that inherently require human oversight in the clinical workflow
FDA Regulatory Coordination
AI/ML Software as a Medical Device
The FDA regulates AI/ML-based clinical decision support as Software as a Medical Device (SaMD) when it meets the device definition and is not excluded under the 21st Century Cures Act §3060(a) exemption for certain CDS:
CDS Not Regulated as Device (Cures Act Exemption):
- Not intended to acquire, process, or analyze a medical image, signal, or pattern
- Intended for the purpose of displaying, analyzing, or printing medical information
- Intended for the purpose of supporting or providing recommendations to an HCP
- Intended for the HCP to independently review the basis for the recommendation
All four criteria must be met. AI systems that process imaging (radiology AI, pathology AI) or make autonomous decisions do NOT qualify for the exemption.
Privacy in FDA AI/ML Regulatory Pathway
| FDA Pathway |
Privacy Considerations |
| 510(k) premarket notification |
Training data representativeness documentation; algorithmic bias assessment; cybersecurity controls for ePHI |
| De Novo classification |
Novel AI technology risk-benefit analysis including privacy risks; post-market surveillance plan |
| PMA (Premarket Approval) |
Full clinical evidence including training data provenance; long-term monitoring of AI performance across demographics |
| Predetermined change control plan |
Documentation of how model updates will maintain privacy protections; re-validation requirements after model retraining |
Good Machine Learning Practice (GMLP)
FDA, Health Canada, and MHRA jointly published 10 GMLP principles (October 2021) with privacy-relevant requirements:
- Leverage multi-disciplinary expertise (including privacy professionals) throughout the AI lifecycle
- Implement good software engineering and security practices (aligns with HIPAA Security Rule)
- Ensure training datasets are representative of intended patient population
- Manage training-serving skew through monitoring and version control
- Focus on global model performance and per-subgroup performance metrics
Bias Monitoring and Health Equity
Regulatory Requirements
- ACA §1557: Prohibits discrimination in healthcare programs receiving federal financial assistance — AI systems that produce disparate outcomes may violate §1557
- OCR AI Guidance: OCR has indicated interest in enforcing non-discrimination requirements against AI systems in healthcare
- CMS Conditions of Participation: Hospitals must not discriminate; AI-driven care recommendations must not produce discriminatory outcomes
Asclepius Health Network AI Bias Monitoring Program
Pre-Deployment Assessment:
- Performance metrics disaggregated by: age group, sex, race/ethnicity, primary language, insurance type, geography
- Disparate impact analysis: if any subgroup performance metric falls below 80% of the best-performing group, remediation required before deployment
- Clinical validation with diverse patient populations matching Asclepius's demographics
Post-Deployment Monitoring:
- Monthly automated performance monitoring across demographic subgroups
- Quarterly clinical outcome correlation analysis
- Annual comprehensive bias audit by independent third party
- Real-time alert if model performance on any subgroup degrades below threshold
- Patient feedback mechanism for concerns about AI-assisted care recommendations
Asclepius Health Network AI Privacy Governance Structure
| Role |
Responsibilities |
| Chief Privacy Officer |
Overall accountability for PHI use in AI; approves AI training data requests; reports to Board |
| CISO |
Security controls for AI infrastructure; penetration testing of AI systems; incident response |
| Chief Medical Informatics Officer |
Clinical appropriateness of AI systems; human oversight protocols; clinician training |
| AI Ethics Committee |
Reviews AI use cases for ethical implications including privacy; includes patient advocate representation |
| AI Data Governance Committee |
Reviews training data requests; ensures de-identification adequacy; manages data use agreements |
| Model Risk Management |
Validates AI model performance; tests for memorization and bias; manages model inventory |
Enforcement and Regulatory Activity
- HHS Office of the National Coordinator (ONC): Health Data, Technology, and Interoperability (HTI-1) Final Rule (2023) requires AI-enabled health IT to meet transparency requirements including source attribute disclosure and risk management
- OCR: Ongoing enforcement interest in AI-related privacy violations; no specific AI enforcement action as of early 2025, but OCR has issued guidance emphasizing HIPAA applicability to AI processing of PHI
- FTC: Health Breach Notification Rule updated (2023) to cover health data processed by non-HIPAA entities including AI health apps; enforcement against AI health claims (e.g., FTC v. Cerebral, 2023)
- State Actions: Multiple state AGs investigating healthcare AI for consumer protection and privacy violations
Integration Points
- hipaa-privacy-rule: All PHI use in AI must comply with Privacy Rule requirements; TPO basis for clinical AI
- hipaa-security-rule: AI infrastructure processing ePHI must meet all technical safeguards
- hipaa-deidentification: De-identification enables AI training without PHI constraints; model memorization creates new re-identification vectors
- hipaa-risk-analysis: AI systems with ePHI access must be included in enterprise-wide risk analysis
- telehealth-privacy: AI integrated into telehealth platforms creates compound privacy obligations
1---2name: healthcare-ai-privacy3description: Addresses healthcare AI privacy at the intersection of HIPAA and the EU AI Act for clinical decision support systems. Covers training data PHI handling, model transparency and explainability, patient rights in algorithmic decisions, FDA/OCR regulatory coordination, and bias monitoring. Keywords: healthcare AI, HIPAA, AI Act, clinical decision support, PHI training data, model transparency.4license: Apache-2.05---6# Healthcare AI Privacy — HIPAA and AI Act Intersection
7
8## Overview
9
10Artificial intelligence in healthcare introduces privacy challenges that sit at the intersection of established health privacy law (HIPAA, HITECH) and emerging AI regulation (EU AI Act, FDA regulatory framework, proposed state AI laws). Clinical decision support (CDS) systems, diagnostic AI, and predictive analytics operate on protected health information, creating obligations under HIPAA while simultaneously falling within the scope of AI-specific regulation when deployed in high-risk clinical contexts. This skill addresses the complete privacy lifecycle of healthcare AI — from training data acquisition through model deployment and patient interaction — ensuring compliance with both health privacy and AI governance frameworks.
11
12## Regulatory Landscape
13
14### Overlapping Regulatory Frameworks
15
16| Framework | Applicability to Healthcare AI | Key Requirements |
17|-----------|-------------------------------|-----------------|
18| HIPAA Privacy Rule (45 CFR §164) | AI systems processing PHI at covered entities or BAs | Authorization or TPO exception for PHI use; minimum necessary; individual rights |
19| HIPAA Security Rule (45 CFR §164.312) | ePHI used in AI training, inference, and storage | Access controls, audit trails, encryption, integrity controls |
20| EU AI Act (Regulation 2024/1689) | AI systems deployed in EU healthcare or processing EU patient data | High-risk classification for medical devices; conformity assessment; transparency |
21| FDA Regulatory Framework | AI/ML-based Software as a Medical Device (SaMD) | 510(k), De Novo, or PMA pathway; GMLP (Good Machine Learning Practice); total product lifecycle approach |
22| FTC Act §5 | AI making health-related decisions affecting consumers | Unfair or deceptive practices; Health Breach Notification Rule for non-HIPAA entities |
23| State AI Laws | Emerging state legislation (Colorado AI Act SB24-205, Illinois AI Video Interview Act) | Algorithmic impact assessments; notice and opt-out for automated decisions |
24
25### EU AI Act High-Risk Classification for Healthcare AI
26
27Under Annex III of the EU AI Act, the following healthcare AI systems are classified as high-risk:
28
29| Category | AI Act Reference | Examples |
30|----------|-----------------|---------|
31| Medical devices (AI-based) | Annex III, §5(a) | AI diagnostic imaging (radiology, pathology, dermatology), AI-assisted surgery planning |
32| In vitro diagnostic medical devices (AI-based) | Annex III, §5(a) | AI-based genetic analysis, AI companion diagnostics |
33| Safety components of medical devices | Annex III, §5(b) | AI monitoring in ICU, AI-driven infusion pump dosing |
34
35High-risk AI systems must comply with AI Act requirements including risk management (Art. 9), data governance (Art. 10), transparency (Art. 13), human oversight (Art. 14), accuracy/robustness (Art. 15), and conformity assessment (Art. 43).
36
37## Training Data PHI Handling
38
39### Lawful Basis for Using PHI in AI Training
40
41| Lawful Basis | HIPAA Provision | Applicability | Conditions |
42|-------------|----------------|---------------|-----------|
43| Treatment | §164.506(c)(1) | AI models trained to support individual patient treatment decisions | Model must directly serve treatment function; minimum necessary applies |
44| Healthcare Operations | §164.506(c)(4) | Quality assessment, population health analytics, clinical decision support development | Must qualify as healthcare operations under §164.501 definition |
45| Research | §164.512(i) | Academic or institutional research developing AI models | IRB/Privacy Board approval; authorization or waiver of authorization; data use agreement for limited datasets |
46| De-identified data | §164.514(a) | Training on data that meets safe harbor or expert determination de-identification | No HIPAA restrictions once properly de-identified; re-identification risk from AI model memorization must be assessed |
47| Authorization | §164.508 | Individual authorization for specific AI training use | Valid authorization meeting §164.508(c) requirements; may be impractical at scale |
48
49### Asclepius Health Network AI Training Data Governance
50
51Asclepius Health Network has established an AI Data Governance Committee that reviews all AI training data requests:
52
53**Training Data Request Workflow**:
54
551. **Purpose documentation**: AI development team submits purpose statement, model description, data elements needed, and lawful basis justification
562. **Minimum necessary review**: Privacy Office reviews requested data elements against stated purpose; removes unnecessary fields
573. **De-identification assessment**: For models that do not require identifiable data, the de-identification team applies safe harbor or coordinates expert determination
584. **Data use agreement**: For limited datasets used in AI development, a DUA is executed specifying permitted uses and prohibiting re-identification attempts
595. **Security requirements**: AI training environment must meet Security Rule requirements — encrypted storage, access-controlled compute environment, audit logging of all data access
606. **Model memorization testing**: Before deployment, models are tested for training data memorization using membership inference and data extraction attacks
617. **Data retention**: Training data copies are deleted within 90 days of model finalization; only the trained model weights are retained
62
63### AI-Specific PHI Risks
64
65| Risk | Description | Mitigation |
66|------|-------------|-----------|
67| Training data memorization | Large models (transformers, LLMs) can memorize and reproduce verbatim training data including PHI | Differential privacy (DP-SGD), training data deduplication, memorization testing pre-deployment |
68| Membership inference | Adversary determines whether a specific patient's data was in the training set | Output perturbation, model regularization, membership inference attack testing |
69| Model inversion | Adversary reconstructs patient features from model outputs | Limit output granularity, add noise to confidence scores, restrict API access |
70| Attribute inference | Model reveals sensitive attributes (HIV status, substance use) not provided as input | Feature correlation analysis, fairness-aware training, output filtering |
71| Training data leakage via model explanation | SHAP/LIME explanations may reveal individual patient contributions | Aggregate explanations; use synthetic examples for patient-facing explanations |
72
73## Model Transparency and Explainability
74
75### HIPAA Transparency Requirements
76
77While HIPAA does not explicitly address AI transparency, several provisions create de facto transparency obligations:
78
79- **Notice of Privacy Practices (§164.520)**: Must describe how PHI is used — if PHI is used in AI systems for treatment or operations, the NPP should disclose this
80- **Right of Access (§164.524)**: Patients have the right to access their designated record set, which may include AI-generated assessments, risk scores, and recommendations stored in the medical record
81- **Minimum Necessary (§164.502(b))**: AI systems accessing PHI must be limited to the minimum necessary data elements
82
83### EU AI Act Transparency Requirements for Healthcare AI
84
85For high-risk healthcare AI systems under the AI Act:
86
87| Requirement | AI Act Article | Implementation |
88|-------------|---------------|----------------|
89| Technical documentation | Art. 11 | Complete description of AI system including training methodology, data governance, performance metrics, known limitations |
90| Record-keeping | Art. 12 | Automatic logging of AI system operations enabling traceability |
91| Transparency to users | Art. 13 | Instructions for use enabling healthcare providers to interpret outputs and exercise oversight; disclosure of performance metrics, known biases, and foreseeable misuse |
92| Human oversight | Art. 14 | AI systems designed to be effectively overseen by natural persons; override capability; ability to disregard AI output |
93| Accuracy and robustness | Art. 15 | Declared accuracy levels; resilience against errors, faults, and adversarial attacks |
94
95### Asclepius Health Network AI Transparency Framework
96
97For each deployed AI system, Asclepius maintains:
98
99**Model Card** (following the Mitchell et al. framework, adapted for healthcare):
100- Model name, version, deployment date
101- Intended clinical use and patient population
102- Training data description (source, size, demographics, time period — using aggregate statistics, not individual PHI)
103- Performance metrics disaggregated by demographic subgroups (age, sex, race/ethnicity, insurance type)
104- Known limitations and failure modes
105- Fairness evaluation results
106- Human oversight requirements (which clinical decisions require physician review)
107- Data privacy measures implemented (de-identification method, differential privacy parameters, access controls)
108
109**Patient-Facing Disclosure**:
110- Asclepius NPP includes disclosure that AI/ML tools may be used in treatment and healthcare operations
111- Individual AI-generated recommendations in the patient portal include a notation identifying them as AI-assisted
112- Patients may request information about AI systems used in their care through the Privacy Office
113
114## Patient Rights in Algorithmic Healthcare Decisions
115
116### HIPAA-Based Rights
117
118| Right | Application to Healthcare AI | Asclepius Implementation |
119|-------|----------------------------|------------------------|
120| Right of Access (§164.524) | Patient may access AI-generated risk scores, predictions, and recommendations in their medical record | AI outputs stored in EHR are accessible through the patient portal; explanations provided in plain language |
121| Right to Amend (§164.526) | Patient may request amendment of AI-generated entries if believed to be inaccurate | AI-generated entries clearly labeled; amendment requests reviewed by treating physician and AI governance committee |
122| Right to Accounting of Disclosures (§164.528) | AI system disclosures of PHI (e.g., to a cloud-based AI service) must be tracked | All API calls to AI inference services logged; BA disclosures tracked in disclosure accounting system |
123| Right to Restrict (§164.522) | Patient may request restrictions on AI processing | Asclepius honors requests to exclude specific data from AI-assisted analytics where clinically feasible |
124
125### Automated Decision-Making Considerations
126
127HIPAA does not include a direct analog to GDPR Article 22 (right not to be subject to automated decision-making). However:
128
129- **Clinical standard of care**: AI-only decisions without physician oversight may constitute substandard care under state medical practice acts
130- **Informed consent**: State informed consent laws may require disclosure that AI was used in diagnosis or treatment recommendations
131- **Anti-discrimination**: AI decisions that disproportionately affect protected groups may violate the ACA §1557 (non-discrimination in healthcare programs), CRA Title VI, or ADA
132- **FDA regulation**: AI/ML SaMD must meet safety and effectiveness standards that inherently require human oversight in the clinical workflow
133
134## FDA Regulatory Coordination
135
136### AI/ML Software as a Medical Device
137
138The FDA regulates AI/ML-based clinical decision support as Software as a Medical Device (SaMD) when it meets the device definition and is not excluded under the 21st Century Cures Act §3060(a) exemption for certain CDS:
139
140**CDS Not Regulated as Device (Cures Act Exemption)**:
1411. Not intended to acquire, process, or analyze a medical image, signal, or pattern
1422. Intended for the purpose of displaying, analyzing, or printing medical information
1433. Intended for the purpose of supporting or providing recommendations to an HCP
1444. Intended for the HCP to independently review the basis for the recommendation
145
146All four criteria must be met. AI systems that process imaging (radiology AI, pathology AI) or make autonomous decisions do NOT qualify for the exemption.
147
148### Privacy in FDA AI/ML Regulatory Pathway
149
150| FDA Pathway | Privacy Considerations |
151|------------|----------------------|
152| 510(k) premarket notification | Training data representativeness documentation; algorithmic bias assessment; cybersecurity controls for ePHI |
153| De Novo classification | Novel AI technology risk-benefit analysis including privacy risks; post-market surveillance plan |
154| PMA (Premarket Approval) | Full clinical evidence including training data provenance; long-term monitoring of AI performance across demographics |
155| Predetermined change control plan | Documentation of how model updates will maintain privacy protections; re-validation requirements after model retraining |
156
157### Good Machine Learning Practice (GMLP)
158
159FDA, Health Canada, and MHRA jointly published 10 GMLP principles (October 2021) with privacy-relevant requirements:
160
1611. Leverage multi-disciplinary expertise (including privacy professionals) throughout the AI lifecycle
1622. Implement good software engineering and security practices (aligns with HIPAA Security Rule)
1633. Ensure training datasets are representative of intended patient population
1644. Manage training-serving skew through monitoring and version control
1655. Focus on global model performance and per-subgroup performance metrics
166
167## Bias Monitoring and Health Equity
168
169### Regulatory Requirements
170
171- **ACA §1557**: Prohibits discrimination in healthcare programs receiving federal financial assistance — AI systems that produce disparate outcomes may violate §1557
172- **OCR AI Guidance**: OCR has indicated interest in enforcing non-discrimination requirements against AI systems in healthcare
173- **CMS Conditions of Participation**: Hospitals must not discriminate; AI-driven care recommendations must not produce discriminatory outcomes
174
175### Asclepius Health Network AI Bias Monitoring Program
176
177**Pre-Deployment Assessment**:
178- Performance metrics disaggregated by: age group, sex, race/ethnicity, primary language, insurance type, geography
179- Disparate impact analysis: if any subgroup performance metric falls below 80% of the best-performing group, remediation required before deployment
180- Clinical validation with diverse patient populations matching Asclepius's demographics
181
182**Post-Deployment Monitoring**:
183- Monthly automated performance monitoring across demographic subgroups
184- Quarterly clinical outcome correlation analysis
185- Annual comprehensive bias audit by independent third party
186- Real-time alert if model performance on any subgroup degrades below threshold
187- Patient feedback mechanism for concerns about AI-assisted care recommendations
188
189## Asclepius Health Network AI Privacy Governance Structure
190
191| Role | Responsibilities |
192|------|-----------------|
193| Chief Privacy Officer | Overall accountability for PHI use in AI; approves AI training data requests; reports to Board |
194| CISO | Security controls for AI infrastructure; penetration testing of AI systems; incident response |
195| Chief Medical Informatics Officer | Clinical appropriateness of AI systems; human oversight protocols; clinician training |
196| AI Ethics Committee | Reviews AI use cases for ethical implications including privacy; includes patient advocate representation |
197| AI Data Governance Committee | Reviews training data requests; ensures de-identification adequacy; manages data use agreements |
198| Model Risk Management | Validates AI model performance; tests for memorization and bias; manages model inventory |
199
200## Enforcement and Regulatory Activity
201
202- **HHS Office of the National Coordinator (ONC)**: Health Data, Technology, and Interoperability (HTI-1) Final Rule (2023) requires AI-enabled health IT to meet transparency requirements including source attribute disclosure and risk management
203- **OCR**: Ongoing enforcement interest in AI-related privacy violations; no specific AI enforcement action as of early 2025, but OCR has issued guidance emphasizing HIPAA applicability to AI processing of PHI
204- **FTC**: Health Breach Notification Rule updated (2023) to cover health data processed by non-HIPAA entities including AI health apps; enforcement against AI health claims (e.g., FTC v. Cerebral, 2023)
205- **State Actions**: Multiple state AGs investigating healthcare AI for consumer protection and privacy violations
206
207## Integration Points
208
209- **hipaa-privacy-rule**: All PHI use in AI must comply with Privacy Rule requirements; TPO basis for clinical AI
210- **hipaa-security-rule**: AI infrastructure processing ePHI must meet all technical safeguards
211- **hipaa-deidentification**: De-identification enables AI training without PHI constraints; model memorization creates new re-identification vectors
212- **hipaa-risk-analysis**: AI systems with ePHI access must be included in enterprise-wide risk analysis
213- **telehealth-privacy**: AI integrated into telehealth platforms creates compound privacy obligations
aibot88