
healthcare-privacy-skills
11 healthcare privacy skills: HIPAA Privacy/Security Rules, risk analysis, BAA management, de-identification, telehealth
- version
- 1.0.0
- GitHub stars
- 340
Install
/plugin install healthcare-privacy-skills@privacy-data-protection-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.
Contents
Discovered from sourceSkills 11
42 CFR Part 2 — Substance Use Disorder Records
Overview
42 CFR Part 2 establishes federal confidentiality protections for patient records created by federally assisted programs treating substance use disorders (SUDs). Originally enacted under the Comprehensive Alcohol Abuse and Alcoholism Prevention, Treatment, and Rehabilitation Act of 1970 and the Drug Abuse Prevention, Treatment, and Rehabilitation Act of 1972, Part 2 was designed to remove barriers to treatment by ensuring that SUD records could not be used to criminally prosecute or otherwise discriminate against patients. Part 2 is intentionally stricter than HIPAA — it requires specific written consent for most disclosures and prohibits re-disclosure by recipients. The CARES Act §3221 (enacted March 2020) and the subsequent 2024 Final Rule (89 FR 12472, effective February 16, 2024) significantly amended Part 2 to align certain provisions with HIPAA while preserving core patient protections.
Applicability — Who Must Comply
Part 2 Programs
Part 2 applies to any "program" that is federally assisted and holds itself out as providing, and provides, substance use disorder diagnosis, treatment, or referral for treatment. A program is federally assisted if it:
- Is conducted by any department or agency of the United States (VA, IHS, military)
- Is carried out under a license, certification, registration, or authorization from the federal government (DEA registration for opioid treatment programs)
- Is supported by funds from any federal department or agency (Medicare/Medicaid participation qualifies)
- Is assisted by the IRS through tax-exempt status under 26 USC §501(c)(3)
- Is conducted by a state or local government receiving federal funds that could be used for SUD programs (even if not directly used for SUD)
Asclepius Health Network Applicability: Asclepius operates 3 dedicated SUD treatment facilities and provides SUD treatment services in all 12 hospitals. Because Asclepius participates in Medicare and Medicaid, all SUD treatment records are Part 2 records. Asclepius maintains a separate consent workflow for Part 2 records in its EHR.
General Medical Facilities
A general medical facility (like a hospital ED) is a Part 2 program only with respect to an identified unit that holds itself out as providing SUD diagnosis, treatment, or referral. However, the 2024 amendments clarify that incidental SUD information in a general medical record (e.g., a note that a patient has a history of alcohol use disorder documented during a cardiac admission) is subject to Part 2 only if the information was obtained from a Part 2 program.
What Records Are Protected — §2.12
Part 2 protects records that:
- Would identify a patient as having or having had a substance use disorder
- Are created by a Part 2 program (or received from a Part 2 program)
- Contain SUD diagnosis, treatment, or referral information
The protections apply to any information that would identify an individual as a SUD patient, including the fact that the person is or was a patient in a Part 2 program.
Consent Requirements — §2.31
Written Consent Required
Unlike HIPAA, which permits disclosures for TPO without consent, Part 2 historically required specific written consent for virtually all disclosures. The 2024 amendments introduced a HIPAA-aligned consent-once model for TPO, but with important safeguards.
Pre-2024 Consent Requirements (Still Applicable for Non-TPO Disclosures)
A valid Part 2 consent must include all of the following:
| Element | Requirement |
|---|---|
| Name of patient | Full legal name of the patient |
| Name of Part 2 program | Specific program making the disclosure |
| Recipient name | Name or general designation of the person(s) or entity to whom disclosure is made |
| Purpose | The purpose of the disclosure must be specified |
| Information to be disclosed | How much and what kind of information is to be disclosed |
| Patient signature | Patient (or authorized representative) signature |
| Date signed | Date the consent was signed |
| Revocability statement | Statement that consent is subject to revocation at any time, except to the extent the program has already acted in reliance on it |
| Expiration | Date, event, or condition upon which consent will expire (if none, the consent must state it expires when the purpose is fulfilled) |
| Re-disclosure prohibition notice | Statement that information disclosed pursuant to consent may not be further disclosed unless permitted by Part 2 |
2024 Amendments — HIPAA-Aligned Consent for TPO
The 2024 Final Rule (89 FR 12472) introduced §2.33, allowing a single prior written consent for all future uses and disclosures for treatment, payment, and healthcare operations:
Key Features of §2.33 Consent:
- Patient may provide a single written consent covering all future TPO disclosures
- Consent covers disclosures to treating providers, payers, and entities performing healthcare operations
- Consent need not name each specific recipient — a general designation of recipient categories is sufficient (e.g., "my treating providers" or "my health plan")
- Consent does not expire unless the patient revokes it
- Patient retains the right to revoke at any time (revocation effective prospectively)
- Recipients remain bound by Part 2's anti-discrimination and limited use/disclosure restrictions
Asclepius Health Network Implementation: Asclepius offers patients a §2.33 TPO consent form at SUD program intake. Patients who sign the TPO consent have their Part 2 records flagged in the EHR for permitted sharing with treating providers and the patient's health plan. Patients who decline the TPO consent retain the traditional per-disclosure consent process. All consent decisions are documented in the EHR.
Re-Disclosure Prohibition — §2.32
The Core Part 2 Protection
Each disclosure of Part 2 records must be accompanied by the following notice:
"This record which has been disclosed to you is protected by federal confidentiality rules (42 CFR Part 2). The federal rules prohibit you from making any further disclosure of information in this record that identifies a patient as having or having had a substance use disorder either directly, by reference to publicly available information, or through verification of such identification by another person unless further disclosure is expressly permitted by the written consent of the individual whose information is being disclosed or as otherwise permitted by 42 CFR Part 2. A general authorization for the release of medical or other information is NOT sufficient for this purpose (see §2.31). The federal rules restrict any use of the information to investigate or prosecute with regard to a crime any patient with a substance use disorder, except as provided at §§2.12(c)(5) and 2.65."
2024 Amendment Impact on Re-Disclosure
Under the 2024 amendments, when Part 2 records are disclosed pursuant to a §2.33 TPO consent:
- Recipients who are HIPAA covered entities or business associates may further use and disclose the records under HIPAA rules (effectively treating them as HIPAA-protected PHI for TPO purposes)
- The re-disclosure prohibition is relaxed for HIPAA-covered recipients to permit standard HIPAA-authorized TPO activities
- However, Part 2's prohibition on use in civil, criminal, administrative, or legislative proceedings against the patient is preserved (§2.12(d))
- Non-HIPAA-covered recipients remain bound by the traditional re-disclosure prohibition
Court Order Requirements — §2.64, §2.65
Authorizing Disclosures by Court Order
When consent is unavailable or not applicable, a court may issue an order authorizing disclosure only after the court finds "good cause" — meaning that:
- Other ways of obtaining the information are not available or would not be effective
- The public interest and need for disclosure outweigh the potential injury to the patient, the physician-patient relationship, and the treatment services
Application Process
An application for a court order must use a fictitious name for the patient and may not disclose patient-identifying information to the court unless the patient is the applicant. The application must be filed under seal.
Criminal Investigations — §2.65
Part 2 records may not be used to investigate or prosecute a patient with respect to a substance use disorder-related crime, with very limited exceptions:
- A court order under §2.65 requires an additional finding that the crime is extremely serious (causing or threatening to cause death or serious bodily injury)
- The order must limit disclosure to the information essential to fulfill the purpose and limit access to those who need the information
Qualified Service Organization Agreements — §2.11(a)
Part 2 uses QSOAs (analogous to HIPAA BAAs) for entities that provide services to Part 2 programs:
| QSOA Requirement | Description |
|---|---|
| Written agreement | Must be in writing, signed by both parties |
| Acknowledge Part 2 obligations | QSO acknowledges it is bound by Part 2 |
| Permitted activities | Data processing, laboratory analyses, legal/medical/accounting/other professional services |
| No re-disclosure | QSO agrees not to re-disclose except as permitted by Part 2 |
| Resistibility to compulsory process | QSO agrees to resist judicial process seeking patient records unless permitted by Part 2 |
2024 Amendment: Existing QSOAs may be maintained, but programs may now transition to using HIPAA-style BAAs for Part 2 records, provided the BAA includes Part 2's specific protections (anti-discrimination, use restriction for investigations/prosecutions).
Comparison: Part 2 vs HIPAA (Post-2024 Amendments)
| Aspect | HIPAA | 42 CFR Part 2 (Post-2024) |
|---|---|---|
| Consent for TPO | Not required | Written consent required (§2.33 single consent available) |
| Consent specificity | N/A (no consent needed for TPO) | Must include specified elements; may use general recipient designation for TPO |
| Re-disclosure | HIPAA allows under permitted uses/disclosures | Restricted — recipients who are HIPAA CEs may use under HIPAA for TPO; anti-discrimination protections preserved |
| Use in legal proceedings against patient | No prohibition | Prohibited except under specific court order (§2.12(d)) |
| Breach notification | Required under §164.400-414 | Now aligned with HIPAA breach notification requirements (2024 amendment) |
| Penalties | HIPAA civil and criminal penalties | Part 2 criminal penalties (§2.4) PLUS HIPAA penalties for covered entities (2024 amendment) |
| Enforcement | OCR | SAMHSA (Part 2-specific) AND OCR (aligned enforcement, 2024 amendment) |
| Patient right of access | Yes, §164.524 | Now aligned with HIPAA (2024 amendment) |
Special Populations and Situations
Minors — §2.14
- State law governs whether a minor may consent to SUD treatment
- If the minor can lawfully consent to SUD treatment, the minor controls the Part 2 consent for disclosure
- A parent/guardian may consent for a minor who cannot lawfully consent to treatment, but the Part 2 program may deny parental access to protect the minor
Medical Emergencies — §2.51
Disclosure without consent is permitted in a bona fide medical emergency to medical personnel to the extent necessary to meet the emergency. The program must document: the name and affiliation of the recipient, the name of the individual authorizing disclosure, the date and time of disclosure, the nature of the emergency, and the information disclosed.
Audit and Evaluation — §2.53
Federal, state, and local government agencies and third-party payers may access Part 2 records for audit and evaluation purposes without consent, subject to restrictions on re-disclosure and a prohibition on use in criminal investigation or prosecution.
Asclepius Health Network Part 2 Compliance Program
- EHR Segmentation: Part 2 records are flagged with a sensitivity code; access controls prevent viewing by users without Part 2 authorization
- Consent Management: Dedicated consent forms tracked in the EHR with consent status (granted/revoked/never requested) visible to clinical staff
- Staff Training: Annual Part 2-specific training for all clinical, billing, and HIM staff; quarterly refresher for SUD program staff
- HIE Participation: Part 2 records are excluded from automated HIE feeds unless patient has signed §2.33 TPO consent
- Breach Response: Part 2 breach response follows HIPAA breach notification procedures (aligned under 2024 amendments) with additional SAMHSA reporting
Enforcement
Criminal Penalties — §2.4
Any person who violates Part 2 is subject to:
- First offense: Fine of not more than $500
- Subsequent offenses: Fine of not more than $5,000
2024 Amendment Penalty Alignment
The 2024 Final Rule aligned Part 2 enforcement with HIPAA's penalty tiers for covered entities and business associates, enabling OCR to impose HIPAA-level civil monetary penalties for Part 2 violations.
Integration Points
- hipaa-privacy-rule: Part 2 records held by HIPAA CEs are subject to both Part 2 and HIPAA; Part 2 is the more restrictive standard
- hipaa-breach-notify: Part 2 breach notification now aligned with HIPAA breach notification requirements
- hipaa-minimum-necessary: Part 2 consent specifies the scope of disclosure; minimum necessary applies separately under HIPAA
- hipaa-baa-management: QSOAs serve Part 2's function analogous to BAAs; 2024 amendments permit BAA use with Part 2 additions
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
HIPAA Business Associate Agreement Management — §164.502(e), §164.504(e)
Overview
The HIPAA Privacy and Security Rules require covered entities to obtain satisfactory assurances from business associates that they will appropriately safeguard PHI. These assurances are documented through Business Associate Agreements (BAAs). The HITECH Act of 2009 and the 2013 Omnibus Rule fundamentally changed the BA landscape by making business associates directly liable for HIPAA Security Rule compliance and certain Privacy Rule provisions, and by extending the BAA chain to subcontractors. A BAA is not merely a contractual formality — it is a regulatory requirement, and failure to execute a BAA when required is itself a HIPAA violation subject to enforcement.
Who Is a Business Associate — §160.103
Definition
A business associate is a person or entity that:
- On behalf of a covered entity or another business associate, creates, receives, maintains, or transmits PHI for a function or activity regulated by the HIPAA Administrative Simplification rules, including claims processing, data analysis, utilization review, quality assurance, billing, benefit management, practice management, and repricing; OR
- Provides legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation, or financial services to or for a covered entity where the provision of the service involves the disclosure of PHI
Who Is NOT a Business Associate
| Entity | Why Not a BA | Reference |
|---|---|---|
| Member of the covered entity's workforce | Employees, volunteers, trainees under direct control are workforce, not BAs | §160.103 definition of workforce |
| Another covered entity exchanging PHI for treatment | Treatment disclosures between covered entities do not create BA relationship | §164.502(e)(1)(i) |
| Health plan sponsor receiving only summary health information or enrollment/disenrollment information | Exemption for plan sponsor limited functions | §164.504(f) |
| Conduit (entity that merely transports PHI without accessing it beyond what is necessary for transport) | Postal service, Internet service providers, couriers with transient access | OCR guidance on conduit exception |
| Banking institutions processing financial transactions containing only the minimum necessary demographic information | Payment processing exception | OCR FAQ on financial institutions |
| Person or entity whose functions do not involve the use or disclosure of PHI | Janitorial services, plumbing, electrical contractors | §160.103 |
Common Business Associate Categories at Asclepius Health Network
| BA Category | Examples | PHI Access Level |
|---|---|---|
| EHR/IT Vendors | Epic hosting, cloud infrastructure (Azure) | Full ePHI access — storage, maintenance, support |
| Revenue Cycle Management | Third-party billing company, collections agency | Demographics, insurance, diagnosis/procedure codes, dates of service |
| Transcription Services | Medical transcription vendor | Dictated clinical notes, patient identifiers |
| Legal/Accounting | Healthcare law firm, external auditors | PHI involved in litigation, audit samples |
| Data Analytics | Population health analytics vendor | De-identified or limited datasets; full PHI if performing analytics on behalf of CE |
| Health Information Exchange | Regional HIE operator | ADT, CCD documents, lab results |
| Shredding/Destruction | Document destruction vendor | Paper records containing PHI during destruction |
| Accreditation | Joint Commission surveyors | PHI in medical records reviewed during survey |
| Consulting | Privacy/security consultants, compliance firms | PHI accessed during assessments |
| Cloud Services | Email hosting, cloud storage, SaaS platforms | ePHI stored or processed in cloud environment |
Required BAA Provisions — §164.504(e)(2)
Mandatory Contract Terms
A BAA must include the following provisions:
1. Permitted and Required Uses and Disclosures
The BAA must establish the permitted and required uses and disclosures of PHI by the business associate. The BA may not use or disclose PHI other than as permitted or required by the BAA or as required by law.
Asclepius Health Network BAA language: "Business Associate shall not use or disclose Protected Health Information other than as permitted or required by this Agreement, as Required by Law, or as otherwise permitted by 45 CFR §164.504(e)."
2. Prohibition on Unauthorized Use or Disclosure
The BAA must not authorize the BA to use or disclose PHI in a manner that would violate the Privacy Rule if done by the covered entity.
Exception: The BAA may permit the BA to use PHI for:
- Proper management and administration of the BA
- Carrying out its legal responsibilities
- Data aggregation services (if specifically authorized)
3. Appropriate Safeguards
The BA must use appropriate safeguards and comply with the Security Rule to prevent unauthorized use or disclosure.
Asclepius Health Network BAA language: "Business Associate shall implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of ePHI that it creates, receives, maintains, or transmits on behalf of Covered Entity, in accordance with 45 CFR Part 164, Subpart C."
4. Breach Reporting
The BA must report to the covered entity any use or disclosure of PHI not provided for by the BAA, including breaches of unsecured PHI as required by §164.410.
Asclepius Health Network BAA language: "Business Associate shall report to Covered Entity any use or disclosure of Protected Health Information not provided for by this Agreement of which Business Associate becomes aware, including any Breach of Unsecured Protected Health Information as required by 45 CFR §164.410, without unreasonable delay and in no case later than five (5) business days after discovery of the Breach."
5. Subcontractor Requirements
The BA must ensure that any subcontractors that create, receive, maintain, or transmit PHI on behalf of the BA agree to the same restrictions and conditions that apply to the BA, including entering into a BAA with the subcontractor.
6. Access Rights
The BA must make PHI available to the covered entity (or directly to the individual if designated in the BAA) to satisfy the individual's right of access under §164.524.
Asclepius Health Network BAA language: "Business Associate shall make available Protected Health Information in a Designated Record Set to Covered Entity, or at Covered Entity's direction, directly to the Individual, within fifteen (15) business days of a request, to satisfy Covered Entity's obligations under 45 CFR §164.524."
7. Amendment Rights
The BA must make PHI available for amendment and incorporate amendments as directed by the covered entity under §164.526.
8. Accounting of Disclosures
The BA must make available the information required to provide an accounting of disclosures under §164.528.
9. HHS Access
The BA must make its internal practices, books, and records relating to the use and disclosure of PHI available to HHS for determining compliance.
10. Return or Destruction of PHI
At termination of the BAA, the BA must return or destroy all PHI received from or created on behalf of the covered entity. If return or destruction is not feasible, the BA must extend the protections of the BAA for as long as it maintains the PHI.
Asclepius Health Network BAA Lifecycle Management
| Phase | Activities | Responsible Party | Timeline |
|---|---|---|---|
| Identification | Determine if vendor relationship requires BAA through PHI access assessment questionnaire | Privacy Office + Procurement | Before contract execution |
| Risk Assessment | Evaluate vendor security posture through questionnaire, SOC 2 review, security assessment | Information Security | 15-30 business days |
| Negotiation | Execute BAA using Asclepius standard template; negotiate deviations with legal review | Legal + Privacy Office | Concurrent with master services agreement |
| Execution | Final BAA signed by authorized signatories; logged in BAA tracking system | Legal + Compliance | Before PHI access begins |
| Monitoring | Annual security assessment questionnaire; SOC 2 report review; incident tracking | Information Security + Privacy | Annually and upon trigger events |
| Renewal/Amendment | Review BAA at master agreement renewal; update for regulatory changes | Legal + Privacy Office | At MSA renewal or regulatory change |
| Termination | PHI return/destruction verification; certificate of destruction obtained; BAA tracking system updated | Privacy Office + IT | Within 60 days of termination |
Business Associate vs Subcontractor Obligations
Direct Liability Under HITECH/Omnibus Rule
Since the 2013 Omnibus Rule, business associates are directly liable for:
| Obligation | BA Directly Liable | Subcontractor Directly Liable |
|---|---|---|
| Security Rule compliance (all standards) | Yes — §164.306, 308, 310, 312, 314, 316 | Yes — through BA-subcontractor BAA |
| Impermissible uses/disclosures under Privacy Rule | Yes — §164.502(a)(3) | Yes — through BA-subcontractor BAA |
| Breach notification to covered entity | Yes — §164.410 | Yes — notify BA, who notifies CE |
| Minimum necessary standard | Yes — §164.502(b) | Yes — through BAA chain |
| Individual rights (access, amendment, accounting) | Yes — as delegated | Yes — as delegated in BAA chain |
| Civil and criminal penalties | Yes — directly enforceable by OCR | Yes — directly enforceable by OCR |
Subcontractor BAA Chain
Covered Entity
└── BAA → Business Associate
└── BAA → Subcontractor (Level 1)
└── BAA → Subcontractor (Level 2)
└── ...continues downstream
Each link in the chain must have a BAA in place. Asclepius Health Network requires primary BAs to:
- Maintain a registry of subcontractors with PHI access
- Provide the registry to Asclepius upon request
- Ensure subcontractor BAAs contain provisions no less restrictive than the primary BAA
- Report subcontractor breaches through the primary BA
Breach Chain Notification Flow
When a breach occurs at a subcontractor:
- Subcontractor discovers breach → notifies BA within timeframe specified in sub-BA (Asclepius standard: 24 hours)
- Business Associate validates and documents → notifies Covered Entity within BAA timeframe (Asclepius standard: 5 business days of BA's discovery)
- Covered Entity conducts four-factor risk assessment → determines if breach notification to individuals/HHS/media/AG is required
- Covered Entity fulfills notification obligations (or delegates to BA per BAA)
Termination Remedies — §164.504(e)(2)(iii)
Material Breach
If the covered entity knows of a pattern of activity or practice of the BA that constitutes a material breach or violation of the BAA:
- Cure: Provide the BA an opportunity to cure the breach or end the violation
- Terminate: If cure is not successful, terminate the contract if feasible
- Report to HHS: If termination is not feasible, report the problem to HHS OCR
Asclepius Health Network Termination Process:
- Written notice of material breach with 30-day cure period
- If not cured within 30 days, termination notice with 60-day wind-down period
- During wind-down: PHI access restricted to minimum necessary for transition
- At termination: BA must return or certify destruction of all PHI within 30 days post-termination
- If return/destruction infeasible, BA must provide written certification of ongoing protection
PHI Return/Destruction Verification
Asclepius Health Network requires:
- Written certification of PHI destruction from BA within 30 days of termination
- Destruction must comply with NIST SP 800-88 Rev. 1 for electronic media
- Paper records destroyed via cross-cut shredding or incineration
- Asclepius reserves the right to audit destruction compliance
Common BAA Deficiencies
| Deficiency | Risk | Mitigation |
|---|---|---|
| No BAA in place for qualifying vendor relationship | Direct HIPAA violation; CE liable for BA's actions without contractual protections | Pre-procurement PHI assessment; no PHI access before BAA execution |
| BAA does not include breach notification provisions | CE may not learn of breach timely; notification deadlines missed | Use standard template with mandatory breach reporting within 5 days |
| BAA permits BA to use PHI for BA's own purposes (marketing, analytics) | Impermissible use of PHI; potential sale of PHI violation | Restrict BA use to services performed for CE; prohibit independent use |
| No subcontractor flow-down requirements | Downstream entities handle PHI without HIPAA obligations | Require BA to bind subcontractors to equivalent BAA terms |
| No termination provisions for PHI return/destruction | PHI retained indefinitely by former BA without safeguards | Mandatory return/destruction clause with certification requirement |
| Outdated BAA not updated for Omnibus Rule | Missing required provisions (subcontractor, breach notification, direct liability acknowledgment) | Periodic BAA review aligned with MSA renewal |
Enforcement Actions
- North Memorial Health Care (2016): $1.55 million — failed to execute a BAA with a major contractor that had access to ePHI of 289,904 individuals; failed to conduct organization-wide risk analysis
- Care New England Health System (2019): $400,000 — failed to execute BAA with BA that experienced a breach; BAA was under negotiation but not signed when PHI was disclosed
- UMMC (University of Mississippi Medical Center) (2016): $2.75 million — multiple Security Rule violations including failure to manage BA relationships properly
Integration Points
- hipaa-privacy-rule: BAA requirement stems from Privacy Rule §164.502(e); BA permitted uses mirror Privacy Rule provisions
- hipaa-security-rule: BA must independently comply with Security Rule; BAA must require appropriate safeguards
- hipaa-breach-notify: BAA breach notification chain is critical path for timely CE notification and individual notice
- hipaa-minimum-necessary: BA disclosures must comply with minimum necessary standard
HIPAA Breach Notification Rule — 45 CFR §164.400-414
Overview
The HIPAA Breach Notification Rule, added by the HITECH Act of 2009 and finalized in the Omnibus Rule of 2013 (78 FR 5566), requires covered entities and business associates to provide notification following a breach of unsecured protected health information (PHI). The rule establishes specific timeframes, content requirements, and reporting obligations that vary based on the number of individuals affected. Post-2013, the rule applies a presumption that any impermissible acquisition, access, use, or disclosure of PHI is a breach unless the covered entity demonstrates through a risk assessment that there is a low probability the PHI was compromised.
Definition of Breach — §164.402
What Constitutes a Breach
A breach is the acquisition, access, use, or disclosure of PHI in a manner not permitted under the Privacy Rule that compromises the security or privacy of the PHI.
Presumption of Breach
Under the 2013 Omnibus Rule, an impermissible use or disclosure of PHI is presumed to be a breach unless the covered entity or business associate demonstrates through a four-factor risk assessment that there is a low probability that the PHI has been compromised.
Four-Factor Risk Assessment — §164.402(2)
| Factor | Assessment Questions |
|---|---|
| 1. Nature and extent of PHI involved | What types of identifiers and clinical information were involved? Does the PHI include sensitive data (SSN, financial, substance abuse, mental health, HIV)? How many data elements were exposed? |
| 2. Unauthorized person who used or received the PHI | Who impermissibly accessed the PHI? Was it an unauthorized employee, an external attacker, an unintended recipient? Does the person have obligations to protect PHI (e.g., another covered entity)? |
| 3. Whether the PHI was actually acquired or viewed | Was the PHI actually accessed or viewed, or was there only an opportunity for access? Are there forensic logs demonstrating whether data was exfiltrated? Was an encrypted laptop stolen but the encryption verified as NIST-compliant? |
| 4. Extent to which the risk has been mitigated | Were satisfactory assurances obtained from the recipient that the PHI will not be further used or disclosed? Was the PHI recovered? Was the recipient a covered entity that has agreed to destroy the information? |
If the risk assessment demonstrates low probability of compromise across all four factors, the incident is not a breach and notification is not required. The assessment must be documented regardless of the conclusion.
Exceptions to the Breach Definition — §164.402(1)
Three circumstances are excluded from the definition of breach:
- Unintentional good-faith acquisition: PHI acquired unintentionally by a workforce member or person acting under the authority of the covered entity or BA, made in good faith and within the scope of authority, and the PHI is not further used or disclosed impermissibly
- Inadvertent disclosure between authorized persons: PHI inadvertently disclosed by a person authorized to access PHI to another person authorized to access PHI at the same covered entity, BA, or organized healthcare arrangement, and the information is not further used or disclosed impermissibly
- Good-faith belief of non-retention: The covered entity or BA has a good-faith belief that the unauthorized person to whom the disclosure was made would not reasonably have been able to retain the information
Unsecured PHI — §164.402
Breach notification obligations apply only to "unsecured PHI" — PHI that has not been rendered unusable, unreadable, or indecipherable to unauthorized individuals through one of the technologies specified by HHS:
Safe Harbor Technologies (HHS Guidance, 74 FR 19006)
| Technology | Specification |
|---|---|
| Encryption | NIST-validated encryption processes consistent with NIST Special Publication 800-111 (data at rest) and FIPS 140-2/140-3 validated modules. AES-128 or AES-256 for data at rest; TLS 1.2+ for data in transit |
| Destruction | Paper: shredding or destruction such that PHI cannot be read or reconstructed. Electronic media: clearing, purging, or destroying consistent with NIST SP 800-88 Rev. 1 |
If PHI was properly encrypted and the encryption key was not compromised, or if PHI was properly destroyed, then it is "secured" and the breach notification provisions do not apply.
Notification Requirements
Individual Notification — §164.404
Who must notify: The covered entity (not the business associate directly, unless delegated by the BA agreement).
Timeframe: Without unreasonable delay, and no later than 60 calendar days from the date of discovery of the breach. Discovery occurs on the first day the breach is known or, by exercising reasonable diligence, would have been known. Knowledge of a workforce member or agent is imputed to the covered entity.
Method: Written notice by first-class mail to the individual's last known address (or next of kin if deceased). Email is permitted if the individual has agreed to electronic notice. If contact information is insufficient or out of date for 10 or more individuals, a conspicuous posting on the covered entity's website for 90 days or a notice in major print or broadcast media is required.
Content requirements (§164.404(c)):
- A brief description of what happened, including the date of the breach and the date of discovery
- A description of the types of unsecured PHI involved (e.g., name, SSN, date of birth, diagnosis, treatment information — do not include the actual PHI)
- Steps individuals should take to protect themselves from potential harm
- A brief description of what the covered entity is doing to investigate, mitigate harm, and prevent future breaches
- Contact procedures including a toll-free telephone number, email address, postal address, or website
Asclepius Health Network Individual Notice Template:
Asclepius Health Network maintains pre-approved breach notification letter templates reviewed by legal counsel, with variable fields for breach-specific details. The template includes:
- Description of the incident
- Types of information involved
- Steps Asclepius has taken (investigation, remediation, enhanced safeguards)
- Offer of complimentary credit monitoring and identity theft protection services (24 months for breaches involving SSN or financial data)
- Toll-free call center number staffed by trained representatives
- Instructions for placing fraud alerts and security freezes
- Contact information for the Asclepius Privacy Office, HHS OCR, and relevant state attorney general
HHS Secretary Notification — §164.408
| Breach Size | Reporting Requirement | Timeframe | Method |
|---|---|---|---|
| 500+ individuals | Individual report to HHS | Without unreasonable delay, no later than 60 days from discovery (concurrent with individual notification) | HHS breach reporting portal (ocrportal.hhs.gov) |
| Fewer than 500 individuals | Log and report annually | Within 60 days of end of calendar year in which breach was discovered | HHS breach reporting portal — annual breach log submission |
Breaches affecting 500 or more individuals are posted on the HHS "Wall of Shame" — the public breach reporting portal at ocrportal.hhs.gov/ocr/breach/breach_report.jsf.
HHS Portal Required Fields:
- Covered entity name, address, contact information
- Covered entity type (health plan, healthcare provider, healthcare clearinghouse, BA acting as agent)
- Number of individuals affected
- Date of breach, date of discovery
- Type of breach (hacking/IT incident, unauthorized access/disclosure, theft, loss, improper disposal, other)
- Location of breached information (email, electronic medical record, network server, paper/films, laptop, desktop, portable device, other)
- Type of PHI involved
- Description of breach
- Safeguards in place at time of breach
- Actions taken in response
State Attorney General Notification — §13402(e)(3) HITECH
For breaches affecting 500 or more residents of a state or jurisdiction, the covered entity must notify the state attorney general concurrent with individual notification.
Asclepius Health Network operates across 4 states. If a breach affects 500+ residents of any single state, the AG of that state must be notified. Many states have their own breach notification laws with additional requirements; Asclepius tracks requirements across all 50 states and files notifications as required.
Media Notification — §164.406
For breaches affecting 500 or more residents of a state or jurisdiction, the covered entity must provide notice to prominent media outlets serving the state or jurisdiction without unreasonable delay and no later than 60 days from discovery. This is typically accomplished through a press release distributed to major media outlets in the affected area.
Business Associate Breach Obligations — §164.410
Business associates must:
- Notify the covered entity of a breach without unreasonable delay and no later than 60 days from discovery (or shorter if specified in the BAA)
- Identify affected individuals to the extent possible
- Provide information the covered entity needs to fulfill its notification obligations
The covered entity retains responsibility for individual, HHS, state AG, and media notification unless the BAA delegates notification to the BA. Asclepius Health Network BAAs require BA breach notification within 5 business days of discovery and require the BA to bear notification costs when the breach results from the BA's acts or omissions.
Breach Response Timeline — Asclepius Health Network
| Day | Action | Responsible Party |
|---|---|---|
| Day 0 | Incident detected or reported | Workforce member, IT security, BA |
| Day 0-1 | Incident response team activated; containment initiated | CISO, Incident Response Team |
| Day 1-7 | Forensic investigation; scope and nature of PHI determined | Forensic investigators (internal or third-party) |
| Day 7-14 | Four-factor risk assessment completed; breach determination made | Privacy Officer, Legal Counsel |
| Day 14-21 | If breach confirmed: notification letters drafted, reviewed by legal, call center prepared | Privacy Office, Legal, Communications |
| Day 21-30 | Notification letters mailed; HHS portal submission prepared | Privacy Office, Compliance |
| Day 30-45 | HHS notified; state AG notified (if 500+ in a state); media notified (if 500+ in a state) | Compliance, Legal |
| Day 45-60 | Substitute notice posted if needed; call center operational; credit monitoring enrollment tracked | Privacy Office, Vendor Management |
| Within 60 days | All individual notifications completed (hard deadline) | Privacy Office |
| Ongoing | Remediation measures implemented; risk analysis updated; workforce re-trained | CISO, Privacy Office, Training |
Documentation Requirements — §164.414(b)
Covered entities must maintain documentation of breach risk assessments, notifications, and related actions for a minimum of 6 years from the date of creation or the date when the document was last in effect, whichever is later. This includes:
- Breach risk assessment and determination
- Individual notification copies and mailing records
- HHS notification records
- State AG notification records
- Media notification records
- Remediation documentation
- Workforce sanctions applied
Enforcement Actions for Breach Notification Failures
- Presence Health (2017): $475,000 — delayed breach notification by over 100 days beyond the 60-day deadline for breach affecting 836 individuals
- Cottage Health (2019): $3 million — failure to conduct thorough risk assessment prior to breach; inadequate security measures contributing to breach of 62,500 records
- Lafourche Medical Group (2023): $480,000 — phishing breach affecting approximately 34,862 individuals; failure to conduct risk analysis and implement security measures; late breach notification
Integration Points
- hipaa-privacy-rule: Breach is defined as impermissible use/disclosure under the Privacy Rule
- hipaa-security-rule: Security safeguards determine whether PHI is "unsecured" for notification purposes
- hipaa-risk-analysis: Post-breach risk analysis update required; breach risk assessment is related but distinct from Security Rule risk analysis
- hipaa-baa-management: BAA breach notification provisions define BA obligations
- hitech-act-privacy: HITECH established the breach notification requirement and penalty tiers
HIPAA De-Identification Methods — 45 CFR §164.514(a)-(b)
Overview
De-identification is the process by which protected health information (PHI) is stripped of identifying elements such that it no longer identifies an individual and there is no reasonable basis to believe it can be used to identify an individual. Under 45 CFR §164.514(a), health information that has been de-identified is no longer PHI and is not subject to the HIPAA Privacy Rule. HIPAA provides two permissible methods for de-identification: expert determination (§164.514(b)(1)) and safe harbor (§164.514(b)(2)). The choice of method depends on the nature of the data, the intended use, and the organization's risk tolerance and resources. OCR published detailed guidance on de-identification methods in November 2012 (updated September 2023), providing extensive clarification on both methods.
Legal Framework
Definition of De-Identified Information — §164.514(a)
Health information is de-identified if it does not identify an individual and if the covered entity has no reasonable basis to believe it can be used to identify an individual. The standard is met by applying either the expert determination or safe harbor method.
Key Distinction: De-Identification vs Anonymization
HIPAA uses the term "de-identification" rather than "anonymization." De-identified data under HIPAA may still carry some theoretical re-identification risk — the standard is "no reasonable basis" to believe identification is possible, not absolute impossibility. This contrasts with GDPR's concept of anonymization, which requires irreversibility.
Method 1: Expert Determination — §164.514(b)(1)
Requirements
A person with appropriate knowledge of and experience with generally accepted statistical and scientific principles and methods for rendering information not individually identifiable must:
- Apply such principles and methods to determine that the risk is very small that the information could be used, alone or in combination with other reasonably available information, to identify an individual who is a subject of the information
- Document the methods and results of the analysis that justify the determination
Qualified Expert
OCR guidance does not specify required credentials but indicates the expert should have knowledge in:
- Statistical methods for assessing disclosure risk (k-anonymity, l-diversity, t-closeness)
- Re-identification attack methodologies (linkage attacks, inference attacks)
- Publicly available data sources and their linkage potential
- Health data characteristics and population uniqueness
Typical qualifications include PhD-level training in statistics, biostatistics, data science, or computer science with specialization in privacy or disclosure limitation.
Expert Determination Process
Step 1: Threat Modeling
The expert identifies plausible re-identification scenarios:
| Attack Type | Description | Example |
|---|---|---|
| Prosecutor attack | Adversary knows the target is in the dataset and attempts to match records | Researcher knows a specific person visited the hospital and tries to find their record in a published dataset |
| Journalist attack | Adversary attempts to re-identify any individual in the dataset | Reporter uses voter registration data to link de-identified hospital discharge records to named individuals |
| Marketer attack | Adversary attempts to re-identify as many individuals as possible | Data broker combines de-identified health data with consumer databases |
Step 2: Risk Quantification
The expert applies statistical methods to quantify re-identification risk:
Population Uniqueness Analysis: Assess how unique combinations of quasi-identifiers are in the relevant population.
Commonly used metrics:
| Metric | Definition | Threshold |
|---|---|---|
| k-anonymity | Every record in the dataset is identical to at least k-1 other records with respect to quasi-identifiers | k ≥ 5 is commonly accepted; k ≥ 10 for higher sensitivity |
| l-diversity | Within each equivalence class (k-anonymous group), there are at least l distinct values for sensitive attributes | l ≥ 3 to protect against homogeneity attacks |
| t-closeness | Distribution of sensitive attributes within each equivalence class is within distance t of the overall distribution | t ≤ 0.15 (application-dependent) |
| Maximum re-identification probability | Probability that any single record can be matched to a specific individual | ≤ 0.04 (4%) — commonly cited by experts; some use 0.05 or 0.09 |
Step 3: Transformation Application
The expert specifies transformations to reduce risk to an acceptable level:
| Transformation | Application |
|---|---|
| Generalization | Replace specific values with ranges (age 47 → age 45-49; ZIP 02139 → 021**) |
| Suppression | Remove records or values that are too unique (suppress records with rare diseases in small populations) |
| Perturbation | Add controlled noise to numerical values (date of birth shifted by random offset within ±7 days) |
| Aggregation | Replace individual-level data with group-level statistics |
| Top/bottom coding | Cap extreme values (age >89 → 90+; weight >300 → 300+) |
Step 4: Documentation
The expert must document:
- Qualifications and experience
- Methodology applied
- Data analyzed (original and transformed)
- Risk metrics computed
- Justification for risk thresholds selected
- Residual risk assessment
- Any conditions on data use that affect the risk determination
Asclepius Health Network engages an external expert (PhD biostatistician with healthcare disclosure risk expertise) for expert determination on research datasets. The expert's report is retained as required documentation.
Method 2: Safe Harbor — §164.514(b)(2)
Requirements
Remove the following 18 categories of identifiers of the individual or of relatives, employers, or household members:
| # | Identifier | Removal Specification |
|---|---|---|
| 1 | Names | All names |
| 2 | Geographic data | All geographic subdivisions smaller than a state. Exception: first 3 digits of ZIP code may be retained if the geographic unit formed by combining all ZIP codes with the same first 3 digits contains more than 20,000 persons (per Census Bureau data). ZIP codes where the 3-digit prefix has ≤20,000 persons must be replaced with 000 |
| 3 | Dates | All elements of dates (except year) directly related to an individual, including birth date, admission date, discharge date, death date. All ages over 89 and all elements of dates (including year) indicative of such age must be aggregated into a single category of 90+ |
| 4 | Telephone numbers | All telephone numbers |
| 5 | Fax numbers | All fax numbers |
| 6 | Email addresses | All email addresses |
| 7 | Social Security numbers | All SSNs |
| 8 | Medical record numbers | All MRNs |
| 9 | Health plan beneficiary numbers | All plan IDs |
| 10 | Account numbers | All account numbers |
| 11 | Certificate/license numbers | All certificate and license numbers |
| 12 | Vehicle identifiers | All vehicle identifiers and serial numbers including license plate numbers |
| 13 | Device identifiers | All device identifiers and serial numbers |
| 14 | Web URLs | All web Universal Resource Locators |
| 15 | IP addresses | All Internet Protocol address numbers |
| 16 | Biometric identifiers | Including finger and voice prints |
| 17 | Full-face photographs | And any comparable images |
| 18 | Any other unique identifying number, characteristic, or code | Except as permitted by re-identification under §164.514(c) |
Additional Safe Harbor Requirement
The covered entity must have no actual knowledge that the remaining information could be used alone or in combination with other information to identify an individual.
Asclepius Health Network Safe Harbor Implementation
Asclepius Health Network uses an automated de-identification pipeline for data released under the safe harbor method:
-
Structured data: EHR extraction scripts strip all 18 identifier categories from structured fields. Date fields are transformed to retain year only (or year and quarter if research protocol requires and dates are not directly related to the individual). Ages over 89 are mapped to 90+. ZIP codes are truncated to 3 digits and validated against the Census Bureau threshold table.
-
Unstructured data (clinical notes): NLP-based named entity recognition (NER) system identifies and redacts names, locations, dates, phone numbers, SSNs, MRNs, email addresses, URLs, and other identifiers in free-text clinical notes. Redacted text is replaced with category-specific tags (e.g.,
[DATE],[NAME],[LOCATION]). Human review sample (10% of documents) validates NER accuracy. -
Imaging data: DICOM header scrubbing removes patient name, ID, dates, institution name, and all private tags. Burned-in annotations on images are reviewed and redacted for identifiers (facial photographs require defacing algorithms).
-
Quality assurance: Post-de-identification audit scans output datasets for residual identifiers using regular expressions, dictionaries of patient names, and cross-reference against the source dataset. Any residual identifiers trigger re-processing and root cause analysis.
Re-Identification — §164.514(c)
Code-Based Re-Identification
A covered entity may assign a code or other record identification mechanism to de-identified information, enabling re-identification under the following conditions:
- The code is not derived from or related to information about the individual (cannot be a hash of SSN or MRN)
- The code is not otherwise capable of being translated to identify the individual
- The covered entity does not use or disclose the code for any other purpose
- The covered entity does not disclose the mechanism for re-identification
The re-identification key must be maintained securely and separately from the de-identified dataset.
Asclepius Health Network: Research datasets are assigned a study-specific random identifier. The crosswalk (random ID ↔ MRN) is encrypted and stored separately from the de-identified dataset in a restricted-access key management system accessible only to the IRB-approved honest broker.
Limited Data Set — §164.514(e)
Definition
A limited data set is PHI that excludes the following direct identifiers of the individual or of relatives, employers, or household members:
- Names
- Street addresses (city, state, ZIP code may be retained)
- Telephone numbers, fax numbers, email addresses
- Social Security numbers
- Medical record numbers, health plan beneficiary numbers, account numbers
- Certificate/license numbers
- Vehicle identifiers, device identifiers
- Web URLs, IP addresses
- Biometric identifiers
- Full-face photographs
A limited data set retains dates (birth, admission, discharge, death), city, state, ZIP code, and ages (including over 89).
Data Use Agreement (DUA) — §164.514(e)(4)
A limited data set may be used or disclosed only if the covered entity enters into a data use agreement with the recipient. The DUA must:
- Establish the permitted uses and purposes of the limited data set (limited to research, public health, or healthcare operations)
- Establish who is permitted to use or receive the limited data set
- Provide that the recipient will not use or further disclose the information other than as permitted by the DUA or as required by law
- Provide that the recipient will use appropriate safeguards to prevent unauthorized use or disclosure
- Provide that the recipient will report any unauthorized use or disclosure to the covered entity
- Provide that the recipient will ensure that any agents to whom it provides the limited data set agree to the same restrictions and conditions
- Provide that the recipient will not attempt to identify the individuals or contact the individuals
Limited Data Set vs De-Identified Data
| Feature | De-Identified (Safe Harbor) | Limited Data Set |
|---|---|---|
| HIPAA status | Not PHI; not subject to Privacy Rule | Still PHI; subject to Privacy Rule |
| Dates permitted | Year only | Full dates |
| Geographic data | First 3 digits of ZIP (if population threshold met) | City, state, full ZIP code |
| Ages over 89 | Must be aggregated to 90+ | Retained |
| Agreement required | None | Data Use Agreement |
| Permitted uses | Any (not PHI) | Research, public health, healthcare operations only |
| Breach notification | Not applicable (not PHI) | Required if unsecured |
Re-Identification Risk Considerations
Publicly Available Data Sources
The expert determination method requires assessment of "reasonably available" data that could be combined with de-identified health data:
| Data Source | Re-Identification Risk | Availability |
|---|---|---|
| Voter registration records | Name, address, DOB, gender | Publicly available in most states |
| Property records | Name, address, purchase date | County recorder offices; commercial aggregators |
| News/media reports | Specific incident details (accident, shooting, notable illness) | Internet search |
| Social media | Self-disclosed health information, location, activities | Publicly posted profiles |
| Death records | Name, DOB, date of death, cause | State vital statistics; SSDI |
| Court records | Name, address, case details | PACER; state court systems |
| Commercial data brokers | Demographics, purchasing behavior, inferred attributes | Commercially available |
OCR Guidance on Re-Identification Risk
OCR has noted that:
- Small geographic areas (census tracts, block groups) combined with birth dates and gender can uniquely identify a high percentage of the US population
- Rare diseases and unusual procedures increase uniqueness even after safe harbor de-identification
- Temporal specificity (exact dates of admission/discharge) combined with institution identity can enable re-identification via news reports
- The "no actual knowledge" requirement under safe harbor is a substantive obligation, not merely a formality
Enforcement
- Aetna (2017): Settled with multiple state AGs and OCR for $1.15 million (state AG settlement) plus separate OCR resolution — mailing envelopes with visible window revealed HIV medication status of approximately 12,000 members. While not a de-identification case per se, it demonstrated the risk of identifiable health information exposure through seemingly innocuous channels.
OCR has not imposed penalties specifically for de-identification methodology failures, but has included de-identification review in corrective action plans and emphasized the importance of proper de-identification in guidance documents.
Integration Points
- hipaa-privacy-rule: De-identification removes data from Privacy Rule scope; failure to properly de-identify means all Privacy Rule requirements apply
- hipaa-minimum-necessary: De-identification and limited datasets serve minimum necessary purposes for research and analytics
- healthcare-ai-privacy: AI training data often requires de-identification; model memorization risk can undermine de-identification
- hipaa-risk-analysis: Re-identification risk assessment parallels security risk analysis methodology
HIPAA Minimum Necessary Standard — 45 CFR §164.502(b)
Overview
The minimum necessary standard is a core principle of the HIPAA Privacy Rule requiring covered entities to make reasonable efforts to limit protected health information to the minimum necessary to accomplish the intended purpose of the use, disclosure, or request. Codified at 45 CFR §164.502(b) and elaborated in §164.514(d), this standard affects every PHI handling decision within a covered entity's operations. The HITECH Act §13405(b) directed HHS to issue guidance on defining "minimum necessary" with greater specificity, and while HHS has not issued a final rule on this provision, OCR has consistently enforced the standard through settlements and corrective action plans.
Regulatory Framework
Statutory and Regulatory Basis
- 45 CFR §164.502(b)(1): "When using or disclosing protected health information or when requesting protected health information from another covered entity or business associate, a covered entity or business associate must make reasonable efforts to limit protected health information to the minimum necessary to accomplish the intended purpose of the use, disclosure, or request."
- 45 CFR §164.514(d): Implementation specifications for the minimum necessary standard
- HITECH Act §13405(b): Required HHS to issue guidance defining minimum necessary; pending final rule, the standard is applied as a reasonableness standard
Exceptions to Minimum Necessary — §164.502(b)(2)
The minimum necessary standard does NOT apply to:
| Exception | Rationale |
|---|---|
| Disclosures to or requests by a healthcare provider for treatment | Treatment requires full clinical picture; limiting information could compromise patient safety |
| Uses or disclosures to the individual who is the subject of the PHI | Individuals have a right to their complete information |
| Uses or disclosures pursuant to a valid authorization under §164.508 | The individual has specifically authorized the scope of disclosure |
| Disclosures to HHS for compliance investigation/enforcement | HHS needs access to determine compliance |
| Uses or disclosures required by law | Legal mandate supersedes minimum necessary limitation |
| Uses or disclosures required for HIPAA Administrative Simplification compliance | Standard transactions require specified data elements |
Implementation Requirements — §164.514(d)
Uses of PHI by Workforce — §164.514(d)(2)
For internal uses of PHI, the covered entity must:
- Identify the workforce members or classes of workforce members who need access to PHI to carry out their duties
- Identify the categories of PHI each class of workforce members needs access to
- Make reasonable efforts to limit access to only the PHI identified as needed
Asclepius Health Network Role-Based Access Matrix:
| Workforce Role | PHI Access Categories | Access Scope | EHR Access Level |
|---|---|---|---|
| Attending Physician | Full clinical record of assigned patients | Current and historical encounters | Full read/write on assigned patients; read-only on others via break-the-glass |
| Consulting Specialist | Clinical record relevant to consultation | Current encounter, relevant history | Read-only on referred patients for relevant clinical domains |
| Registered Nurse (Inpatient) | Nursing assessments, vital signs, medication administration, care plans, physician orders | Current admission on assigned unit | Read/write for assigned patients on unit; read-only for transferred patients for continuity |
| Emergency Department Nurse | Full clinical record of ED patients | Current ED encounter | Full read/write for ED patients; access terminates at discharge/transfer |
| Pharmacist | Medication orders, allergies, diagnoses relevant to drug therapy, renal/hepatic function | Current and recent encounters | Read medication-related clinical data; write medication verification/dispensing |
| Medical Coder | Diagnoses, procedures, operative notes, discharge summaries | Post-discharge records | Read-only for coding-relevant documentation |
| Billing Specialist | Demographics, insurance information, diagnosis codes, procedure codes, dates of service | Billed encounters | No access to clinical notes; demographics and billing codes only |
| Registration Clerk | Demographics, insurance information, emergency contacts | Registration screen only | Read/write limited to demographic and insurance fields |
| Quality Improvement Analyst | Aggregate clinical data, de-identified data, limited datasets per DUA | Population-level reports | Limited dataset access with data use agreement; no individual record access without specific justification |
| IT Support Staff | System administration — may access ePHI incidentally during troubleshooting | As needed for technical support | Logged access during active support ticket; no browsing; all access audited |
| Executive Leadership | Summary reports, aggregate statistics | De-identified or aggregate | Dashboard access only; no individual patient record access |
| Legal Counsel | PHI related to active litigation or compliance investigation | Specific records per legal hold | Access granted per matter with Privacy Office authorization |
Routine and Recurring Disclosures — §164.514(d)(3)(i)
For routine, recurring disclosures, the covered entity must implement policies and procedures that limit the PHI disclosed to the amount reasonably necessary to achieve the purpose:
Asclepius Health Network Routine Disclosure Protocols:
| Routine Disclosure Type | Standard PHI Set | Excluded PHI |
|---|---|---|
| Insurance eligibility verification | Patient name, DOB, insurance ID, service date | Clinical information, diagnoses, SSN |
| Referral to external provider | Relevant clinical summary, current medications, allergies, reason for referral | Unrelated historical diagnoses, substance abuse records (42 CFR Part 2), psychotherapy notes |
| Workers' compensation claim | Work-related injury/illness records, treatment for that condition | Unrelated medical history |
| Pre-authorization request | Proposed procedure, clinical justification, relevant diagnostic results | Complete medical record |
| Public health reporting | Required data elements per reporting jurisdiction statute | Additional clinical detail beyond reportable elements |
| Subpoena response (with qualified protective order) | Records specified in the subpoena/court order | Records beyond the scope of the order |
Non-Routine Disclosures — §164.514(d)(3)(ii)
For non-routine disclosures, the covered entity must:
- Develop criteria to limit PHI to the minimum necessary for the particular disclosure
- Review each request on a case-by-case basis against the criteria
Asclepius Health Network Non-Routine Disclosure Process:
- All non-routine PHI requests are routed to the Health Information Management (HIM) department
- HIM specialist reviews the request against the purpose stated
- If the purpose is unclear or the request scope appears broader than necessary, HIM contacts the requestor for clarification
- Privacy Officer review is required for requests involving: psychotherapy notes, substance abuse records, HIV/STI records, records of minors, requests from law enforcement without a warrant, and any request affecting more than 50 individuals
- Only the PHI elements necessary for the stated purpose are disclosed
- The disclosure is logged with the scope justification for accounting of disclosures
Disclosures to Other Covered Entities — Reasonable Reliance §164.514(d)(3)(iii)
A covered entity may rely on a request from another covered entity or business associate as meeting minimum necessary if:
| Requestor Type | Reasonable Reliance Permitted When |
|---|---|
| Public official | Request states PHI is the minimum necessary for the stated purpose (§164.514(d)(3)(iii)(A)) |
| Another covered entity | Request is for PHI the requestor needs (§164.514(d)(3)(iii)(B)) |
| Professional member of the workforce of the CE or BA | Represents that PHI requested is the minimum necessary for the stated purpose (§164.514(d)(3)(iii)(C)) |
| Research with IRB/Privacy Board waiver | Waiver documentation represents PHI is the minimum necessary for the research (§164.514(d)(3)(iii)(D)) |
Reasonable reliance does not eliminate the disclosing entity's obligation; it shifts the burden of determining minimum necessary to the requestor in specified circumstances.
HITECH Act §13405(b) — Enhanced Minimum Necessary
HITECH §13405(b) added two provisions:
- Limited dataset standard: Until HHS issues final guidance, if a covered entity is required to comply with the minimum necessary standard and determines that a limited dataset (§164.514(e)) would accomplish the purpose, the minimum necessary standard is met by providing the limited dataset
- Future guidance: HHS was directed to issue regulations that further restrict minimum necessary to limit information to the minimum necessary for the stated purpose — this final rule remains pending
Documentation Requirements
Covered entities must document and maintain:
- Policies and procedures implementing the minimum necessary standard (§164.530(i))
- Role-based access definitions identifying PHI categories by workforce class (§164.514(d)(2))
- Routine disclosure protocols specifying standard PHI sets (§164.514(d)(3)(i))
- Non-routine review criteria and case-by-case determination records (§164.514(d)(3)(ii))
- Training materials covering minimum necessary for all workforce members
- Sanction records for workforce members who violate minimum necessary policies
All documentation must be retained for 6 years from creation or last effective date under §164.530(j).
Common Minimum Necessary Violations
| Violation Pattern | Example | Remediation |
|---|---|---|
| Granting full record access by default | All nurses have access to all patient records across all departments | Implement unit-based access restrictions; require break-the-glass for cross-department access |
| Sending entire medical record in response to limited request | Attorney requests records related to knee surgery; HIM sends complete chart | Train HIM on request scope analysis; implement disclosure review checklist |
| Overly broad role definitions | "Clinician" role grants same access to physicians, nurses, medical assistants, and technicians | Granular role definitions aligned with job function; separate access profiles per clinical role |
| No logging of access for minimum necessary auditing | Unable to determine if workforce members are accessing only patients in their care | Implement access audit reports comparing records accessed to assigned patients |
| Faxing full face sheets with all demographics for limited purpose | Registration faxes complete demographic page to pharmacy for prescription verification | Create limited forms with only necessary fields per transaction type |
Enforcement Actions
- Memorial Hermann Health System (2017): $2.4 million — disclosed a patient's PHI (name linked to involvement in a vehicular incident) in a press release, exceeding minimum necessary
- Cignet Health (2011): $4.3 million (CMP) — although primarily for denial of access rights, OCR noted systemic failure to implement minimum necessary policies
- CVS Pharmacy (2009): $2.25 million — improper disposal of PHI in dumpsters reflected failure to implement minimum necessary in disposal processes
Integration Points
- hipaa-privacy-rule: Minimum necessary is a core Privacy Rule requirement affecting all uses and disclosures
- hipaa-security-rule: Technical access controls (§164.312(a)) implement minimum necessary through role-based ePHI access
- hipaa-baa-management: BAAs must limit BA access to minimum necessary PHI for contracted services
- hipaa-deidentification: De-identification and limited datasets serve as minimum necessary tools for research and analytics
- 42-cfr-part-2: Substance abuse records have their own consent-based minimum necessary requirements that are stricter than HIPAA
HIPAA Privacy Rule — 45 CFR §164.500-534
Overview
The HIPAA Privacy Rule establishes national standards for the protection of individually identifiable health information — Protected Health Information (PHI) — held by covered entities and their business associates. Enacted under the Health Insurance Portability and Accountability Act of 1996 and finalized in the Privacy Rule of 2000 (with major modifications in 2002 and 2013 under HITECH/Omnibus), the rule balances patient privacy rights with the practical needs of healthcare delivery. The Privacy Rule applies to health plans, healthcare clearinghouses, and healthcare providers who transmit any health information electronically in connection with a HIPAA-covered transaction.
Covered Entities and Business Associates
Who Is a Covered Entity
Under 45 CFR §160.103, covered entities include:
| Entity Type | Definition | Examples |
|---|---|---|
| Healthcare Provider | Any provider who transmits health information electronically in connection with a covered transaction | Hospitals, physician practices, pharmacies, laboratories, dentists, chiropractors |
| Health Plan | Individual or group plan that provides or pays for medical care | Health insurers, HMOs, employer-sponsored health plans, government programs (Medicare, Medicaid, TRICARE) |
| Healthcare Clearinghouse | Entity that processes nonstandard health information into standard format | Billing services, repricing companies, community health management information systems |
Asclepius Health Network Example
Asclepius Health Network operates as a covered entity comprising 12 hospitals, 85 outpatient clinics, and an affiliated health plan. Every workforce member — from attending physicians to front desk staff — must comply with the Privacy Rule. Asclepius designates its Chief Privacy Officer to manage rule implementation across all facilities.
Protected Health Information (PHI)
Definition
PHI is individually identifiable health information that is transmitted or maintained in any form or medium by a covered entity or business associate. Under 45 CFR §160.103, individually identifiable health information is information that:
- Is created or received by a healthcare provider, health plan, employer, or healthcare clearinghouse
- Relates to the past, present, or future physical or mental health or condition of an individual, the provision of healthcare to an individual, or payment for healthcare
- Identifies the individual or provides a reasonable basis to believe the individual can be identified
What PHI Includes
PHI encompasses information in any form — electronic (ePHI), paper, or oral. The 18 identifiers defined in §164.514(b)(2) include:
- Names
- Geographic data smaller than state (street address, city, county, ZIP code — first 3 digits allowed if population > 20,000)
- Dates related to the individual (birth, admission, discharge, death — year alone is permitted)
- Telephone numbers
- Fax numbers
- Email addresses
- Social Security numbers
- Medical record numbers
- Health plan beneficiary numbers
- Account numbers
- Certificate/license numbers
- Vehicle identifiers and serial numbers including license plates
- Device identifiers and serial numbers
- Web URLs
- IP addresses
- Biometric identifiers (fingerprints, voiceprints)
- Full-face photographs and comparable images
- Any other unique identifying number, characteristic, or code
Exclusions
PHI does not include:
- Education records covered by FERPA
- Employment records held by a covered entity in its role as employer
- De-identified data meeting §164.514(a)-(b) standards
Uses and Disclosures of PHI
Permitted Uses Without Authorization
The Privacy Rule permits uses and disclosures of PHI without individual authorization in the following circumstances:
Treatment, Payment, and Healthcare Operations (TPO) — §164.506
TPO is the primary exception enabling routine healthcare delivery:
Treatment (§164.501): The provision, coordination, or management of healthcare and related services by one or more healthcare providers. Includes consultation between providers, referrals, and provider-to-provider communication about a patient.
At Asclepius Health Network, a cardiologist may share a patient's echocardiogram results with the referring primary care physician without patient authorization because this constitutes treatment.
Payment (§164.501): Activities by a covered entity or its business associate to obtain or provide reimbursement for healthcare. Includes eligibility determinations, billing, claims management, utilization review, and collection activities.
Asclepius Health Network's billing department may submit a patient's diagnosis codes and procedure codes to the patient's health insurer for claim adjudication without patient authorization.
Healthcare Operations (§164.501): Activities including quality assessment, competency assurance, conducting or arranging medical review, legal services, auditing, business planning, customer service, resolution of internal grievances, compliance activities, and limited de-identified data analysis.
Public Interest and Benefit Activities — §164.512
| Activity | CFR Section | Requirements |
|---|---|---|
| Required by law | §164.512(a) | Disclosure compelled by statute, regulation, or court order |
| Public health | §164.512(b) | To public health authorities for disease prevention, FDA reporting, workplace safety |
| Victims of abuse/neglect | §164.512(c) | To government authority authorized to receive reports |
| Health oversight | §164.512(d) | To health oversight agencies for audits, investigations, inspections |
| Judicial proceedings | §164.512(e) | In response to court order or qualified protective order with subpoena |
| Law enforcement | §164.512(f) | Pursuant to process, limited circumstances (identification, crime on premises, emergency) |
| Decedents | §164.512(g) | To coroners, medical examiners, funeral directors |
| Organ donation | §164.512(h) | To organ procurement organizations |
| Research | §164.512(i) | With IRB/Privacy Board waiver of authorization, preparatory to research, or decedent research |
| Serious threat | §164.512(j) | To prevent or lessen serious and imminent threat to health or safety |
| Essential government functions | §164.512(k) | Military, veterans, national security, intelligence, protective services |
| Workers' compensation | §164.512(l) | As authorized by workers' compensation laws |
Uses and Disclosures Requiring Authorization — §164.508
An authorization is required for:
- Uses and disclosures of psychotherapy notes (§164.508(a)(2))
- Uses and disclosures for marketing purposes (§164.508(a)(3))
- Sale of PHI (§164.508(a)(4))
- Any use or disclosure not otherwise permitted or required by the Privacy Rule
Valid Authorization Requirements
A valid authorization under §164.508(c) must contain:
- A specific and meaningful description of the information to be used or disclosed
- The name or specific identification of the person(s) authorized to make the use or disclosure
- The name or specific identification of the person(s) to whom the disclosure may be made
- A description of each purpose of the use or disclosure ("at the request of the individual" is sufficient)
- An expiration date or event
- The individual's signature and date
- If signed by a personal representative, a description of the representative's authority
Required statements on the authorization form:
- Right to revoke the authorization in writing
- Ability or inability to condition treatment, payment, enrollment, or eligibility on the authorization
- Potential for re-disclosure by the recipient (no longer protected by HIPAA)
Minimum Necessary Standard — §164.502(b)
General Requirement
Covered entities must make reasonable efforts to limit PHI to the minimum necessary to accomplish the intended purpose of the use, disclosure, or request. This is one of the most frequently cited and enforced provisions.
Exceptions to Minimum Necessary
The minimum necessary standard does NOT apply to:
- Disclosures to or requests by a healthcare provider for treatment purposes
- Disclosures to the individual who is the subject of the PHI
- Uses or disclosures made pursuant to a valid authorization
- Disclosures to HHS for compliance investigation or enforcement
- Uses or disclosures required by law
- Uses or disclosures required for HIPAA Administrative Simplification compliance
Implementation at Asclepius Health Network
Asclepius Health Network implements the minimum necessary standard through:
Workforce Access: Role-based access controls defining the categories of PHI each workforce member role needs. Emergency department nurses access current visit records, vital signs, allergies, and medication lists. Billing staff access demographic information, insurance details, diagnosis codes, and procedure codes — not clinical notes.
Routine Disclosures: For routine, recurring disclosures, Asclepius maintains standard protocols limiting information provided. For insurance eligibility verification, only the patient name, date of birth, insurance ID, and requested service dates are transmitted.
Non-Routine Disclosures: For non-routine disclosures, each request is reviewed on a case-by-case basis by the Privacy Office. The reviewer applies the minimum necessary principle and documents the rationale for the scope of disclosure.
Individual Rights
Right of Access — §164.524
Individuals have the right to inspect and obtain a copy of PHI maintained in a designated record set, with limited exceptions:
- Timeframe: Covered entity must act on a request within 30 days (one 30-day extension permitted with written explanation)
- Format: If requested, PHI must be provided in electronic form if readily producible
- Fees: Limited to reasonable, cost-based fees for labor for copying, supplies, and postage (not retrieval or search)
- Denial grounds: Psychotherapy notes, information compiled for legal proceedings, lab results subject to CLIA, inmates if access would jeopardize health/safety, research participant during study if agreed upon enrollment
Asclepius Health Network provides patient portal access to electronic health records. Patients who request additional records receive them within 15 business days. Asclepius charges $6.50 per electronic copy (flat fee covering labor and transmission).
Right to Amend — §164.526
Individuals may request amendment of PHI in a designated record set. The covered entity may deny if the information:
- Was not created by the covered entity (unless the originator is no longer available)
- Is not part of the designated record set
- Would not be available for access under §164.524
- Is accurate and complete
If denied, the individual may submit a statement of disagreement appended to the record.
Right to an Accounting of Disclosures — §164.528
Individuals have the right to receive an accounting of disclosures made by the covered entity in the six years prior to the request. Exceptions include disclosures:
- For treatment, payment, or healthcare operations
- To the individual
- Pursuant to an authorization
- For the facility's directory or to persons involved in care
- For national security or intelligence purposes
- To correctional institutions or law enforcement in custody situations
- Part of a limited data set
- That occurred before the Privacy Rule compliance date
Right to Request Restrictions — §164.522(a)
Individuals may request restrictions on uses and disclosures for TPO. The covered entity is NOT required to agree to the restriction, except:
- Mandatory restriction: If the individual pays out of pocket in full for a healthcare item or service, the covered entity MUST agree to restrict disclosure to a health plan for payment or healthcare operations purposes (added by HITECH §13405(a))
Right to Request Confidential Communications — §164.522(b)
Individuals may request that communications be sent by alternative means or to alternative locations. Healthcare providers must accommodate reasonable requests. Health plans must accommodate when the individual states that disclosure could endanger them.
Right to Receive Notice of Privacy Practices — §164.520
Covered entities must provide a Notice of Privacy Practices (NPP) that describes:
- How PHI may be used and disclosed
- The individual's rights regarding PHI
- The covered entity's legal duties
- Whom to contact for further information
- How to file complaints
Distribution: Healthcare providers with a direct treatment relationship must provide the NPP at first service delivery and make a good faith effort to obtain written acknowledgment. Health plans must provide at enrollment and within 60 days of material revision.
Directory Opt-Out — §164.510(a)
Covered entities that maintain a facility directory may include limited PHI (patient name, location in facility, general condition, religious affiliation) for directory purposes. The individual must be:
- Informed in advance of the PHI to be included
- Given the opportunity to restrict or prohibit some or all uses
- Allowed to opt out entirely
If the individual is incapacitated or unavailable, the covered entity may include directory information if consistent with any prior expressed preference and if disclosure is in the individual's best interest as determined by professional judgment.
At Asclepius Health Network, patients are asked at registration whether they wish to be listed in the facility directory. Those who opt out are flagged in the admissions system, and all staff are instructed that no information may be provided to callers or visitors.
Personal Representatives — §164.502(g)
A personal representative must be treated as the individual for purposes of the Privacy Rule if the representative has authority under applicable law to act on behalf of the individual in making healthcare decisions:
| Individual | Personal Representative | Authority Basis |
|---|---|---|
| Adult | Person with healthcare power of attorney | State healthcare POA statute |
| Minor (general) | Parent, guardian, or person acting in loco parentis | State law on parental authority |
| Minor (exceptions) | Minor acts as own representative | State law permitting minor consent (STI treatment, substance abuse, reproductive health) |
| Deceased individual | Executor, administrator, or person with legal authority over estate | State probate law |
| Adult lacking capacity | Court-appointed guardian or person authorized under state law | State guardianship statute |
Abuse/neglect exception: A covered entity may decline to treat a person as a personal representative if the covered entity reasonably believes the individual has been or may be subject to domestic violence, abuse, or neglect by the representative, and treating them as representative is not in the individual's best interest.
Enforcement and Penalties
OCR Enforcement
The HHS Office for Civil Rights (OCR) enforces the Privacy Rule through:
- Complaint investigations
- Compliance reviews
- Technical assistance and guidance
Civil Monetary Penalties (as amended by HITECH)
| Tier | Culpability Level | Per Violation | Annual Maximum |
|---|---|---|---|
| 1 | Did not know (and would not have known with reasonable diligence) | $137–$68,928 | $2,067,813 |
| 2 | Reasonable cause, not willful neglect | $1,379–$68,928 | $2,067,813 |
| 3 | Willful neglect, corrected within 30 days | $13,785–$68,928 | $2,067,813 |
| 4 | Willful neglect, not corrected | $68,928–$2,067,813 | $2,067,813 |
Penalty amounts are adjusted annually for inflation per 45 CFR §160.404.
Notable Enforcement Actions
- Anthem Inc. (2018): $16 million settlement — largest HIPAA settlement — for breach affecting 78.8 million individuals. Findings included insufficient access controls and failure to conduct enterprise-wide risk analysis.
- Premera Blue Cross (2020): $6.85 million settlement for breach of 10.4 million records due to failure to conduct risk analysis and implement adequate security controls.
- Banner Health (2023): $1.25 million settlement for breach affecting over 2.81 million individuals. OCR found failure to conduct accurate risk analysis and implement audit controls.
Integration Points
- hipaa-security-rule: Technical safeguards implementing the Privacy Rule's ePHI protections
- hipaa-minimum-necessary: Detailed implementation of the minimum necessary standard
- hipaa-breach-notify: Breach notification obligations when Privacy Rule violations result in unauthorized disclosure
- hipaa-baa-management: Business associate obligations under the Privacy Rule
- hipaa-deidentification: Methods for de-identifying PHI to remove it from Privacy Rule scope
HIPAA Risk Analysis — 45 CFR §164.308(a)(1)
Overview
The HIPAA Security Rule requires covered entities and business associates to conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI held by the organization. Risk analysis under §164.308(a)(1)(ii)(A) is the foundational requirement of the Security Rule — it drives all subsequent safeguard decisions. OCR has identified failure to conduct a comprehensive, enterprise-wide risk analysis as the most common finding in breach investigations and compliance reviews. The risk analysis must be ongoing, not a one-time event, and must be updated whenever significant changes occur in the environment or in response to security incidents.
Legal Foundation
Regulatory Text
45 CFR §164.308(a)(1)(ii)(A) — Risk Analysis (Required):
"Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate."
45 CFR §164.308(a)(1)(ii)(B) — Risk Management (Required):
"Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level to comply with §164.306(a)."
OCR Guidance Documents
OCR published "Guidance on Risk Analysis Requirements under the HIPAA Security Rule" (July 14, 2010) establishing nine essential elements that an adequate risk analysis must address. This guidance, while not binding regulation, represents OCR's enforcement expectations and has been consistently applied in settlement agreements and corrective action plans.
OCR Nine Essential Elements
Element 1: Scope of the Analysis
The risk analysis must encompass all ePHI that the organization creates, receives, maintains, or transmits, in every form and location:
Asclepius Health Network Scope Inventory:
| ePHI Location | System/Medium | Data Categories | Volume |
|---|---|---|---|
| Electronic Health Record (Epic) | Production servers, disaster recovery site | Complete clinical records, demographics, insurance | 4.2 million patient records |
| Practice Management System | Cloud-hosted (Azure US East) | Scheduling, billing, referrals | 4.2 million patients |
| Laboratory Information System | On-premises servers | Lab orders, results, specimen tracking | 12 million results annually |
| Radiology PACS | On-premises SAN storage | Diagnostic images, reports | 850 TB imaging data |
| Email System (Exchange Online) | Microsoft 365 tenant | Incidental ePHI in clinical communications | Estimated 15,000 messages/day containing ePHI |
| Mobile Devices | 3,200 organization-owned tablets, 800 BYOD smartphones | Clinical reference, secure messaging, patient photos | Variable |
| Medical Devices | 1,400 networked devices (infusion pumps, monitors, ventilators) | Real-time patient data, device logs | Continuous streaming |
| Paper-to-digital Conversion | Scanning workstations, OCR servers | Scanned historical records, faxed referrals | 2,000 pages/day |
| Business Associate Systems | 47 BA relationships with ePHI access | Varies by BA (billing, transcription, cloud hosting, analytics) | Varies |
| Backup and Archive | Tape library, offsite vault, cloud archive | Complete system backups | 6-year retention |
| Health Information Exchange | Regional HIE platform | ADT feeds, CCD documents, lab results | 150,000 transactions/month |
Element 2: Data Collection
Identify and document where ePHI is stored, received, maintained, or transmitted. Methods include:
- Automated discovery: Network scanning tools identifying systems communicating health data (HL7, FHIR, DICOM traffic analysis)
- Data flow mapping: Documenting how ePHI moves between systems, departments, and external parties
- Workforce interviews: Structured interviews with department managers, clinical informaticists, and IT staff
- System inventory review: Cross-referencing CMDB (Configuration Management Database) with ePHI classification tags
- Vendor assessment questionnaire responses: BA-reported ePHI handling practices
- Physical walkthroughs: Identifying workstations, printers, fax machines, and storage locations processing ePHI
Element 3: Identify and Document Potential Threats and Vulnerabilities
Threat Categories
| Threat Category | Specific Threats | Source |
|---|---|---|
| Natural | Flood, earthquake, tornado, hurricane, wildfire, pandemic | Geographic and climate risk assessment |
| Human — Intentional | Hacking/IT incident, ransomware, phishing, insider theft, social engineering, nation-state APT | FBI IC3 reports, HHS cybersecurity alerts, threat intelligence feeds |
| Human — Unintentional | Misdirected email/fax, lost device, improper disposal, misconfiguration, training failure | Incident history, OCR breach portal patterns |
| Environmental | Power failure, HVAC failure, water damage, fire, electromagnetic interference | Facility assessments, utility reliability data |
| Technical | Software vulnerability, hardware failure, network outage, cryptographic weakness | CVE databases, vendor advisories, penetration test results |
Vulnerability Assessment Methods
- Penetration testing: Annual external and internal penetration test by independent third party
- Vulnerability scanning: Weekly automated scans of all network-connected assets (Qualys, Nessus, or equivalent)
- Configuration auditing: Quarterly review of system configurations against CIS benchmarks
- Social engineering testing: Semi-annual phishing simulations; annual physical penetration attempts
- Application security testing: SAST/DAST scanning of internally developed applications; third-party code review for critical systems
- Wireless security assessment: Quarterly rogue access point scanning; annual wireless penetration test
Element 4: Assess Current Security Measures
Document existing safeguards and their effectiveness:
Asclepius Health Network Current Controls Assessment (Sample):
| Control Area | Implemented Measure | Effectiveness Rating | Gap Identified |
|---|---|---|---|
| Access Control | Role-based access in EHR with unique user IDs | Effective | Quarterly access reviews not consistently completed for all departments |
| Encryption at Rest | AES-256 FDE on servers and endpoints | Effective | 12 legacy medical devices running unencrypted embedded systems |
| Encryption in Transit | TLS 1.2+ enforced on all external connections | Effective | 3 internal legacy interfaces still using TLS 1.0 |
| Audit Logging | Centralized SIEM with 6-year retention | Effective | Log review staffing insufficient for alert volume |
| Backup | Daily incremental, weekly full, offsite replication | Effective | Restore testing frequency needs improvement |
| Physical Security | Badge access, CCTV, visitor management | Partially Effective | Server room access badge list includes 15 individuals who no longer require access |
| Anti-Malware | EDR deployed on all managed endpoints | Effective | Coverage gap on BYOD devices with MDM enrollment below 100% |
| Patch Management | Monthly patch cycle, 14-day critical patch SLA | Partially Effective | Medical device patching delayed by manufacturer certification requirements |
Element 5: Determine the Likelihood of Threat Occurrence
Assign likelihood ratings based on threat capability, motivation, and existing controls:
| Likelihood Level | Definition | Scoring |
|---|---|---|
| Very High | Almost certain to occur within the next year; active exploitation observed | 5 |
| High | Likely to occur; threat source is capable and motivated; controls have known weaknesses | 4 |
| Medium | Possible occurrence; threat source exists and has some capability; controls are partially effective | 3 |
| Low | Unlikely but possible; limited threat capability or motivation; controls are generally effective | 2 |
| Very Low | Remote possibility; no known threat source targeting this vulnerability; strong controls in place | 1 |
Element 6: Determine the Potential Impact of Threat Occurrence
Assess the magnitude of harm if a threat exploits a vulnerability:
| Impact Level | Definition | Examples | Scoring |
|---|---|---|---|
| Critical | Catastrophic harm to individuals or organization | Breach of >500K records, permanent patient harm from data integrity failure, organizational insolvency | 5 |
| High | Significant harm to many individuals or severe organizational impact | Breach of 10K-500K records, extended system outage affecting patient care, OCR investigation | 4 |
| Medium | Moderate harm to limited individuals or substantial operational disruption | Breach of 500-10K records, multi-day system unavailability, significant remediation costs | 3 |
| Low | Limited harm to few individuals or manageable operational impact | Breach of <500 records, brief system disruption, contained incident | 2 |
| Negligible | Minimal or no harm | No ePHI exposure confirmed, minor operational inconvenience | 1 |
Element 7: Determine the Level of Risk
Risk is calculated as the product of likelihood and impact:
Risk Score = Likelihood × Impact
| Risk Score | Risk Level | Action Required |
|---|---|---|
| 20-25 | Critical | Immediate mitigation required; senior leadership notification; consider system suspension |
| 12-19 | High | Mitigation plan required within 30 days; management approval to accept risk |
| 6-11 | Medium | Mitigation plan required within 90 days; documented risk acceptance alternative |
| 2-5 | Low | Monitor and address in normal operations; annual review |
| 1 | Minimal | Accept and document; review at next scheduled risk analysis |
Asclepius Health Network Risk Register (Sample Entries):
| Risk ID | Threat/Vulnerability | Likelihood | Impact | Risk Score | Risk Level |
|---|---|---|---|---|---|
| R-001 | Ransomware attack on clinical systems | 4 (High) | 5 (Critical) | 20 | Critical |
| R-002 | Insider unauthorized access to celebrity patient records | 4 (High) | 3 (Medium) | 12 | High |
| R-003 | Unencrypted legacy medical device data exposure | 3 (Medium) | 4 (High) | 12 | High |
| R-004 | Phishing leading to credential compromise | 4 (High) | 4 (High) | 16 | High |
| R-005 | Lost/stolen unencrypted mobile device | 2 (Low) | 3 (Medium) | 6 | Medium |
| R-006 | Misdirected fax containing ePHI | 3 (Medium) | 2 (Low) | 6 | Medium |
| R-007 | Natural disaster affecting primary data center | 2 (Low) | 5 (Critical) | 10 | Medium |
Element 8: Finalize Documentation
The risk analysis must be documented in sufficient detail to demonstrate:
- The scope covered all ePHI
- Threats and vulnerabilities were comprehensively identified
- Current security measures were evaluated
- Likelihood and impact were assessed using a consistent methodology
- Risk levels were determined
- The analysis was conducted by qualified personnel
Required Documentation Components:
- Date of analysis and date range covered
- Personnel conducting the analysis (names, qualifications)
- Methodology description
- Complete asset inventory with ePHI classification
- Threat and vulnerability catalog
- Current controls inventory
- Risk scoring matrix and ratings
- Risk register with all identified risks
- Executive summary for leadership
Element 9: Periodic Review and Updates
The risk analysis is not a one-time activity. It must be updated:
- At least annually as a scheduled comprehensive review
- When new systems, applications, or technologies are implemented
- When significant changes to the operating environment occur (mergers, relocations, new facilities)
- After a security incident or breach
- When new threats are identified (new malware families, regulatory changes, threat intelligence alerts)
- When OCR or industry guidance identifies new risk areas
Risk Management and Mitigation Planning — §164.308(a)(1)(ii)(B)
For each risk above the organization's acceptable risk threshold, develop and implement a mitigation plan:
Mitigation Plan Template (Risk R-001: Ransomware):
| Element | Detail |
|---|---|
| Risk ID | R-001 |
| Risk Description | Ransomware attack encrypting clinical systems, rendering ePHI unavailable |
| Current Risk Score | 20 (Critical) |
| Mitigation Measures | (1) Deploy advanced EDR with behavioral ransomware detection; (2) Implement network segmentation isolating clinical systems; (3) Maintain immutable backup copies with air-gapped storage; (4) Conduct quarterly tabletop ransomware exercises; (5) Implement application whitelisting on clinical workstations |
| Implementation Timeline | EDR: Complete; Segmentation: 60 days; Immutable backups: 90 days; Tabletop: Quarterly; Whitelisting: 120 days |
| Responsible Party | CISO (overall); Network Engineering (segmentation); Backup Administrator (immutable backups) |
| Target Risk Score | 8 (Medium) — likelihood reduced from 4 to 2 through layered controls |
| Residual Risk Acceptance | Approved by CIO and CPO on documented risk acceptance form |
| Review Date | Next comprehensive review or 90 days post-implementation |
Common OCR Findings
OCR consistently identifies the following deficiencies in risk analyses:
- Not enterprise-wide: Analysis limited to EHR system only, excluding email, mobile devices, medical devices, and BA systems
- Not updated: One-time analysis without periodic review or updates after significant changes
- Not thorough: Failure to identify all ePHI assets, particularly shadow IT, personal devices, and cloud services
- No documentation: Analysis conducted informally without written documentation
- No risk management follow-through: Risks identified but no mitigation plans developed or implemented
- Inadequate methodology: No structured approach to likelihood/impact determination; subjective risk ratings without defined criteria
Enforcement Actions for Risk Analysis Failures
Risk analysis deficiency is cited in the majority of OCR enforcement actions:
- Anthem Inc. (2018): $16 million — failed to conduct enterprise-wide risk analysis prior to breach affecting 78.8 million
- Premera Blue Cross (2020): $6.85 million — risk analysis failed to identify risks across the enterprise; did not assess all systems with ePHI
- Banner Health (2023): $1.25 million — risk analysis was not accurate and thorough; did not identify all risks to ePHI
- CHSPSC LLC (2020): $2.3 million — failed to conduct accurate risk analysis and implement risk management measures
- University of Massachusetts Amherst (2020): $650,000 — failure to conduct risk analysis of ePHI maintained by research programs
- Metro Community Provider Network (2017): $400,000 — risk analysis not conducted to sufficient depth
Integration Points
- hipaa-security-rule: Risk analysis drives implementation decisions for all technical, administrative, and physical safeguards
- hipaa-breach-notify: Post-breach risk analysis updates feed into breach risk assessment under §164.402
- hipaa-baa-management: Risk analysis must include ePHI held by or accessible to business associates
- hipaa-privacy-rule: Privacy risk assessments complement security risk analysis for comprehensive PHI protection
HIPAA Security Rule — Technical Safeguards 45 CFR §164.312
Overview
The HIPAA Security Rule establishes national standards for protecting electronic protected health information (ePHI) that is created, received, used, or maintained by a covered entity or business associate. Published as a final rule on February 20, 2003 (68 FR 8334), with compliance required by April 20, 2005 (April 20, 2006 for small health plans), the Security Rule operationalizes the Privacy Rule's confidentiality protections through administrative, physical, and technical safeguards. The rule adopts a risk-based, technology-neutral approach — it specifies what must be achieved but allows flexibility in how covered entities implement protections based on their size, complexity, and capabilities.
The Security Rule applies only to ePHI, unlike the Privacy Rule which covers PHI in all forms. The rule organizes its requirements into three safeguard categories (administrative §164.308, physical §164.310, technical §164.312) plus organizational requirements (§164.314) and policies/procedures/documentation (§164.316).
Technical Safeguards — §164.312
Technical safeguards are the technology and related policies and procedures that protect ePHI and control access to it. Each standard has required implementation specifications (mandatory) and addressable implementation specifications (must be implemented if reasonable and appropriate, with documented rationale if an alternative measure is adopted or the specification is not implemented).
Access Control — §164.312(a)(1)
Standard: Implement technical policies and procedures for electronic information systems that maintain ePHI to allow access only to those persons or software programs that have been granted access rights.
| Implementation Specification | Type | Requirement |
|---|---|---|
| Unique User Identification — §164.312(a)(2)(i) | Required | Assign a unique name and/or number for identifying and tracking user identity |
| Emergency Access Procedure — §164.312(a)(2)(ii) | Required | Establish and implement procedures for obtaining necessary ePHI during an emergency |
| Automatic Logoff — §164.312(a)(2)(iii) | Addressable | Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity |
| Encryption and Decryption — §164.312(a)(2)(iv) | Addressable | Implement a mechanism to encrypt and decrypt ePHI |
Unique User Identification
Every workforce member, administrator, and system account accessing ePHI must have a unique identifier. Shared accounts and generic logins are prohibited.
Asclepius Health Network Implementation:
- Active Directory assigns unique user IDs in the format
[first initial][last name][employee number](e.g.,jsmith4821) - Service accounts for application-to-application communication use the format
svc-[application]-[function](e.g.,svc-epic-hl7) - Privileged administrative accounts are separate from standard user accounts (
adm-jsmith4821) - All user accounts are tied to the HR system — terminated employees are automatically disabled within 1 hour of separation processing
- Biometric authentication (fingerprint) is deployed at clinical workstations for single sign-on
- Multi-factor authentication is required for remote access and administrative functions
Emergency Access Procedure
Covered entities must have documented procedures for accessing ePHI during emergencies when normal access controls cannot function.
Asclepius Health Network Implementation:
- Break-the-glass procedures allow any clinician to access any patient record during declared emergencies
- Break-the-glass events generate immediate alerts to the Privacy Office and require post-event justification within 24 hours
- Disaster recovery accounts with elevated privileges are maintained in sealed envelopes in the IT Operations Center safe
- Emergency access accounts are tested quarterly and passwords rotated after each test or use
- The EHR system maintains a separate emergency mode with simplified authentication (badge + PIN) activated during IT system failures
Automatic Logoff
Asclepius Health Network Implementation:
- Clinical workstations: 5-minute inactivity timeout with screen lock, 15-minute session termination
- Administrative workstations: 10-minute inactivity timeout with screen lock, 30-minute session termination
- Patient portal sessions: 15-minute inactivity timeout with session termination
- Mobile devices (tablets on clinical carts): 2-minute inactivity lock, requiring biometric re-authentication
- Proximity-based logoff using RFID badges — session locks when clinician's badge moves more than 10 feet from the workstation
Encryption and Decryption
Although addressable, OCR has consistently found that failing to encrypt ePHI without documented equivalent alternative measures constitutes a Security Rule violation.
Asclepius Health Network Implementation:
- Data at rest: AES-256 encryption on all storage volumes containing ePHI (database tablespace encryption, full disk encryption on endpoints)
- Data in transit: TLS 1.2 minimum (TLS 1.3 preferred) for all network communications containing ePHI
- Database field-level encryption for highly sensitive fields (SSN, substance abuse diagnoses, HIV status, mental health notes)
- Encryption key management through a FIPS 140-2 Level 3 validated hardware security module (HSM)
- Key rotation: Annual for data-at-rest keys, per-session for TLS, quarterly for application-level encryption keys
Audit Controls — §164.312(b)
Standard: Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use ePHI.
No implementation specifications are designated — the standard itself is required.
Asclepius Health Network Implementation:
What is logged:
- All authentication events (successful and failed logins, logoffs, account lockouts)
- All access to ePHI (reads, writes, modifications, deletions) including the specific records accessed
- All administrative actions (user creation, privilege changes, configuration modifications)
- All system events (startup, shutdown, errors, backup operations)
- All network events involving ePHI systems (connections, disconnections, firewall events)
- Break-the-glass access events with enhanced detail
Log management:
- Centralized log aggregation using SIEM (Security Information and Event Management) platform
- Real-time correlation and alerting for suspicious patterns (multiple failed logins, unusual access volumes, after-hours access to records outside care team)
- Immutable log storage — logs are write-once to prevent tampering
- Log retention: minimum 6 years (aligned with HIPAA documentation retention requirement under §164.530(j))
- Daily automated log review reports provided to the Security Operations Center
- Monthly audit sample: random selection of 50 patient records reviewed for access appropriateness
Audit triggers and alerts:
| Trigger | Response SLA | Action |
|---|---|---|
| 5+ failed login attempts in 10 minutes | Immediate | Account lockout, alert to SOC |
| Access to VIP/employee patient records | Immediate | Alert to Privacy Office for review |
| Bulk record access (>50 records in 1 hour by single user) | 15 minutes | SOC review, possible account suspension |
| After-hours access from unusual location | 1 hour | Review by SOC next business day or immediate if high risk |
| Break-the-glass event | 24 hours | Privacy Office justification review |
| Administrative privilege escalation | Immediate | SOC verification of change ticket |
Integrity — §164.312(c)(1)
Standard: Implement policies and procedures to protect ePHI from improper alteration or destruction.
| Implementation Specification | Type | Requirement |
|---|---|---|
| Mechanism to Authenticate ePHI — §164.312(c)(2) | Addressable | Implement electronic mechanisms to corroborate that ePHI has not been altered or destroyed in an unauthorized manner |
Asclepius Health Network Implementation:
- Database integrity: SHA-256 checksums on clinical document records; tamper-evident logging of all modifications
- Append-only clinical documentation model — original entries are never deleted or overwritten; amendments are linked to original records with author, timestamp, and reason
- Digital signatures on laboratory results, radiology reports, and medication orders using PKI certificates
- Daily integrity verification scans comparing file checksums against known-good baselines
- Backup integrity verification: automated restore testing of randomly selected backup sets weekly
Person or Entity Authentication — §164.312(d)
Standard: Implement procedures to verify that a person or entity seeking access to ePHI is the one claimed. This standard is required with no implementation specifications.
Asclepius Health Network Implementation:
- Internal workforce: Multi-factor authentication (badge + PIN for workstations; authenticator app + password for remote)
- External providers (Health Information Exchange): Digital certificate-based mutual TLS authentication
- Patient portal: Knowledge-based authentication for enrollment; username + password + SMS/email verification code for ongoing access
- Business associates accessing Asclepius systems: VPN with certificate + password + hardware token
- Application-to-application: OAuth 2.0 with client credentials and mutual TLS
Transmission Security — §164.312(e)(1)
Standard: Implement technical security measures to guard against unauthorized access to ePHI that is being transmitted over an electronic communications network.
| Implementation Specification | Type | Requirement |
|---|---|---|
| Integrity Controls — §164.312(e)(2)(i) | Addressable | Implement security measures to ensure electronically transmitted ePHI is not improperly modified without detection |
| Encryption — §164.312(e)(2)(ii) | Addressable | Implement a mechanism to encrypt ePHI whenever deemed appropriate |
Asclepius Health Network Implementation:
- All internal network traffic containing ePHI is encrypted using TLS 1.2+ (network segmentation with ePHI VLAN)
- External transmissions: mandatory TLS 1.2+ or VPN tunnels; unencrypted email containing ePHI is blocked by DLP gateway
- HL7 FHIR API endpoints: mutual TLS with SMART on FHIR authorization
- Direct secure messaging for provider-to-provider ePHI exchange (Direct Protocol with S/MIME encryption)
- Integrity controls: TLS provides built-in integrity via HMAC; additional checksums on batch file transfers (HL7 batch, X12 EDI)
- Wireless networks: WPA3 Enterprise with 802.1X RADIUS authentication on all clinical wireless networks; separate guest network with no ePHI system access
Administrative Safeguards — §164.308 (Selected Key Requirements)
Security Management Process — §164.308(a)(1)
| Implementation Specification | Type |
|---|---|
| Risk Analysis | Required |
| Risk Management | Required |
| Sanction Policy | Required |
| Information System Activity Review | Required |
Workforce Security — §164.308(a)(3)
| Implementation Specification | Type |
|---|---|
| Authorization and/or Supervision | Addressable |
| Workforce Clearance Procedure | Addressable |
| Termination Procedures | Addressable |
Information Access Management — §164.308(a)(4)
| Implementation Specification | Type |
|---|---|
| Isolating Healthcare Clearinghouse Functions | Required |
| Access Authorization | Addressable |
| Access Establishment and Modification | Addressable |
Security Awareness and Training — §164.308(a)(5)
| Implementation Specification | Type |
|---|---|
| Security Reminders | Addressable |
| Protection from Malicious Software | Addressable |
| Log-in Monitoring | Addressable |
| Password Management | Addressable |
Security Incident Procedures — §164.308(a)(6)
| Implementation Specification | Type |
|---|---|
| Response and Reporting | Required |
Contingency Plan — §164.308(a)(7)
| Implementation Specification | Type |
|---|---|
| Data Backup Plan | Required |
| Disaster Recovery Plan | Required |
| Emergency Mode Operation Plan | Required |
| Testing and Revision Procedures | Addressable |
| Applications and Data Criticality Analysis | Addressable |
Physical Safeguards — §164.310 (Summary)
Facility Access Controls — §164.310(a)(1)
Addressable specifications: Contingency operations, facility security plan, access control and validation procedures, maintenance records.
Workstation Use — §164.310(b)
Required standard specifying appropriate physical environment and manner of use for workstations accessing ePHI.
Workstation Security — §164.310(c)
Required standard implementing physical safeguards restricting access to workstations that access ePHI.
Device and Media Controls — §164.310(d)(1)
Required specifications for disposal and media re-use; addressable specifications for accountability and data backup/storage.
Required vs Addressable: OCR Expectations
OCR has clarified that "addressable" does not mean "optional." For each addressable specification, covered entities must:
- Assess whether the implementation specification is a reasonable and appropriate safeguard in their environment
- If yes, implement it
- If not, document why it is not reasonable and appropriate AND implement an equivalent alternative measure that is reasonable and appropriate OR document why the standard can still be met without the specification or alternative
OCR enforcement actions have found violations where entities failed to encrypt ePHI (addressable) without documenting any alternative measure. In practice, encryption of ePHI at rest and in transit is expected by OCR absent extraordinary documented justification.
Enforcement Precedents
- Anthem Inc. (2018): $16 million — failure to implement technical safeguards including access controls sufficient to prevent unauthorized access to ePHI of 78.8 million individuals
- Premera Blue Cross (2020): $6.85 million — failure to implement security measures sufficient to reduce risks and vulnerabilities to ePHI; inadequate audit controls
- CHSPSC LLC (2020): $2.3 million — failure to implement information system activity review, inadequate response to known security incident (APT attack affecting 6.1 million individuals)
- Excellus Health Plan (2021): $5.1 million — inadequate access controls, failure to conduct enterprise-wide risk analysis, insufficient technical policies
- Banner Health (2023): $1.25 million — failure to implement audit controls and conduct accurate technical risk analysis after breach of 2.81 million records
Integration Points
- hipaa-privacy-rule: Privacy Rule establishes what must be protected; Security Rule establishes how
- hipaa-risk-analysis: Detailed risk analysis methodology mandated by §164.308(a)(1)(ii)(A)
- hipaa-breach-notify: Security incidents that result in unauthorized access trigger breach notification
- hipaa-baa-management: Business associates must independently comply with all Security Rule standards
HITECH Act Privacy and Security Requirements
Overview
The Health Information Technology for Economic and Clinical Health (HITECH) Act was enacted as Title XIII of the American Recovery and Reinvestment Act of 2009 (Pub. L. 111-5). HITECH fundamentally transformed HIPAA enforcement by establishing breach notification requirements, creating a four-tier penalty structure with significantly increased penalties, granting enforcement authority to state attorneys general, extending HIPAA Security Rule requirements directly to business associates, and tying privacy and security compliance to the Electronic Health Record (EHR) meaningful use incentive program. The 2013 Omnibus Rule (78 FR 5566) implemented most HITECH provisions into the HIPAA regulatory framework.
Breach Notification — HITECH §13402
Establishment of Federal Healthcare Breach Notification
Prior to HITECH, HIPAA had no breach notification requirement. HITECH §13402 created the obligation for covered entities and business associates to notify individuals, HHS, and in some cases the media, following a breach of unsecured PHI.
Key provisions enacted by HITECH:
| Provision | HITECH Section | Implementation |
|---|---|---|
| Individual notification within 60 days | §13402(a) | Codified at 45 CFR §164.404 |
| HHS notification for breaches of 500+ immediately; under 500 annually | §13402(e)(1)-(3) | Codified at 45 CFR §164.408 |
| Media notification for 500+ in a state/jurisdiction | §13402(e)(2) | Codified at 45 CFR §164.406 |
| State AG notification for 500+ in a state | §13402(e)(3) | 45 CFR §164.408(c) |
| BA obligation to notify CE | §13402(b) | Codified at 45 CFR §164.410 |
| Unsecured PHI definition and safe harbor for encryption/destruction | §13402(h) | HHS guidance at 74 FR 19006 |
Evolution of the Breach Standard
HITECH originally used a "harm standard" — notification was required only if there was a significant risk of financial, reputational, or other harm. The 2013 Omnibus Rule replaced this with the "low probability of compromise" standard under the four-factor risk assessment (§164.402(2)), which is more protective of individuals. Under this standard, an impermissible use or disclosure is presumed to be a breach unless the entity demonstrates low probability of compromise.
Penalty Structure — HITECH §13410
Four-Tier Civil Monetary Penalty Framework
HITECH §13410(d) replaced the single-tier HIPAA penalty structure with a graduated system based on culpability:
| Tier | Culpability Level | Per Violation (2024 adjusted) | Annual Cap (2024 adjusted) | Correction Possible |
|---|---|---|---|---|
| A | Did not know and would not have known by exercising reasonable diligence | $137 – $68,928 | $2,067,813 | Must correct within 30 days |
| B | Reasonable cause (not willful neglect) | $1,379 – $68,928 | $2,067,813 | Must correct within 30 days |
| C | Willful neglect — timely corrected | $13,785 – $68,928 | $2,067,813 | Corrected within 30 days of knowledge |
| D | Willful neglect — not timely corrected | $68,928 – $2,067,813 | $2,067,813 | Investigation/penalty mandatory |
Penalty amounts are adjusted annually for inflation under the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015.
Criminal Penalties
HITECH preserved and enhanced criminal penalties under 42 USC §1320d-6:
| Tier | Conduct | Maximum Penalty |
|---|---|---|
| 1 | Knowingly obtaining or disclosing PHI | Up to $50,000 fine and 1 year imprisonment |
| 2 | Offenses committed under false pretenses | Up to $100,000 fine and 5 years imprisonment |
| 3 | Offenses with intent to sell, transfer, or use for commercial advantage, personal gain, or malicious harm | Up to $250,000 fine and 10 years imprisonment |
Percentage of CMPs and Settlements to Affected Individuals — §13410(c)(2)
HITECH §13410(c)(2) directed HHS to establish methods for distributing a percentage of CMPs and settlement amounts to individuals harmed by HIPAA violations. HHS has not yet issued final regulations implementing this provision, but OCR has included equitable relief provisions in certain settlement agreements.
State Attorney General Enforcement — HITECH §13410(e)
Authority Granted
HITECH §13410(e) authorized state attorneys general to bring civil actions in federal district court on behalf of state residents who may have been affected by HIPAA violations. This was a significant expansion — previously only HHS/OCR could enforce HIPAA.
Requirements for State AG Actions
| Requirement | Detail |
|---|---|
| Prior notice to HHS | State AG must provide notice to the Secretary of HHS before filing suit |
| HHS intervention right | HHS may intervene and assume primary responsibility for the action |
| No action during pending HHS action | State AG may not bring action during a pending HHS action against the same entity for the same violation |
| Remedies available | Injunctive relief, damages (up to $100 per violation, $25,000 per calendar year per identical violation), attorneys' fees |
State AG Enforcement Precedents
| State | Year | Entity | Outcome |
|---|---|---|---|
| Connecticut | 2010 | Health Net of Connecticut | $250,000 settlement — first state AG action under HITECH; loss of unencrypted hard drive with PHI of 1.5 million individuals |
| Minnesota | 2011 | Accretive Health | $2.5 million settlement — unauthorized access to PHI; failure to have BAA |
| Indiana | 2014 | WellPoint (Anthem) | $1.9 million penalty — application vulnerability exposing ePHI of 612,402 individuals; state AG used HITECH authority alongside state law |
| New York | 2021 | EyeMed Vision Care | $600,000 settlement — email phishing breach exposing PHI of 2.1 million; state AG cited HITECH and state consumer protection |
| New Jersey | 2019 | Virtua Medical Group | $418,000 settlement — disclosure of PHI to vendor without BAA |
Business Associate Direct Liability — HITECH §13401
Pre-HITECH vs Post-HITECH
| Aspect | Pre-HITECH | Post-HITECH (§13401) |
|---|---|---|
| Security Rule compliance | Contractual obligation through BAA only; no direct regulatory liability | BAs directly subject to Security Rule; enforceable by OCR and state AGs |
| Privacy Rule | BAs bound only by BAA terms | BAs directly liable for impermissible uses/disclosures; subject to minimum necessary |
| Penalties | Only covered entities subject to HIPAA penalties; BAs subject only to breach of contract | BAs subject to same civil and criminal penalties as covered entities |
| Subcontractors | No regulatory requirements | Subcontractors treated as BAs; must have BAAs in place |
Impact on Asclepius Health Network
Asclepius Health Network manages 47 business associate relationships. Post-HITECH, each BA must:
- Independently comply with all Security Rule administrative, physical, and technical safeguards
- Report breaches to Asclepius within 5 business days per the BAA
- Demonstrate compliance through annual security assessments
- Flow down BAA requirements to their subcontractors
EHR Meaningful Use Privacy Conditions — HITECH §13401(b)
Privacy and Security as Prerequisites for Incentive Payments
HITECH created the Medicare and Medicaid EHR Incentive Programs (now known as Promoting Interoperability) with total payments exceeding $38 billion. Privacy and security compliance is a prerequisite for receiving incentive payments:
| Meaningful Use Stage | Privacy/Security Requirements |
|---|---|
| Stage 1 (2011-2013) | Conduct or review a security risk analysis; implement security updates; correct identified security deficiencies |
| Stage 2 (2014-2016) | All Stage 1 requirements plus: address encryption/security of data at rest; enable patient electronic access to health information |
| Stage 3 / Promoting Interoperability (2017+) | Security risk analysis; patient electronic access; secure messaging; API access; ONC Health IT Certification privacy and security criteria |
Privacy Requirements in Health IT Certification
ONC Health IT Certification Criteria (45 CFR Part 170) require certified EHR technology to support:
- Authentication, access control, and authorization
- Auditable events and tamper-resistance
- Automatic access time-out
- Emergency access
- End-user device encryption
- Integrity verification
- Accounting of disclosures
- Amendments to health information
- Consent management (including segmentation for Part 2 and state-specific restrictions)
Asclepius Health Network uses ONC-certified Epic EHR and verifies that each software version maintains certification for privacy and security criteria. The Promoting Interoperability dashboard tracks privacy measure compliance for CMS attestation.
Accounting of Disclosures Expansion — HITECH §13405(c)
HITECH Expansion
HITECH §13405(c) expanded the right to an accounting of disclosures to include disclosures through an electronic health record for treatment, payment, and healthcare operations (previously excluded under HIPAA §164.528). The accounting period was set at 3 years (rather than HIPAA's 6 years) for EHR disclosures.
Status: HHS published a Notice of Proposed Rulemaking in 2011 (76 FR 31426) proposing an "access report" approach but withdrew the NPRM and has not issued a final rule. The HITECH provision is self-executing in the statute but implementation guidance remains pending.
Restrictions on Sale of PHI — HITECH §13405(d)
HITECH §13405(d) prohibits a covered entity or business associate from receiving direct or indirect remuneration in exchange for PHI without a valid authorization from the individual that states whether the PHI can be further exchanged for remuneration.
Exceptions
| Exception | Description |
|---|---|
| Public health | Disclosures for public health activities under §164.512(b) |
| Research | Reasonable cost-based fee for preparing and transmitting PHI for research |
| Treatment and payment | Normal treatment and payment activities |
| Transfer of business | Sale, transfer, merger of covered entity |
| BA services | Remuneration is for services BA provides on behalf of CE |
| Individual request | Individual requests own PHI |
| HHS-determined exceptions | Other purposes determined by HHS through regulation |
Minimum Necessary Enhancement — HITECH §13405(b)
HITECH directed HHS to issue guidance making the minimum necessary standard more specific:
- Until HHS issues guidance, the limited dataset standard (§164.514(e)) is the floor for minimum necessary when PHI is in electronic form and a limited dataset would accomplish the purpose
- HHS has not issued the final rule, but the provision is self-executing to the extent described
Enforcement Milestones Under HITECH
| Year | Action | Significance |
|---|---|---|
| 2009 | HITECH enacted | Four-tier penalties, breach notification, BA liability, state AG enforcement |
| 2010 | Interim Final Breach Notification Rule | Initial implementation of breach notification with harm standard |
| 2011 | First resolution agreement post-HITECH (Cignet Health, $4.3M) | Demonstrated willingness to impose significant penalties |
| 2013 | Omnibus Rule | Comprehensive implementation of HITECH provisions into HIPAA regulations |
| 2016 | Advocate Medical Group ($5.55M) | Largest fine at the time; multiple breaches involving unencrypted devices |
| 2018 | Anthem ($16M) | Largest HIPAA settlement; demonstrated HITECH penalty levels for major breaches |
| 2020-2024 | Annual penalty adjustments | Inflation-adjusted penalties increasing annually |
Integration Points
- hipaa-breach-notify: HITECH created the breach notification framework implemented in the Breach Notification Rule
- hipaa-privacy-rule: HITECH strengthened Privacy Rule provisions including restrictions on sale of PHI and minimum necessary
- hipaa-security-rule: HITECH extended Security Rule directly to business associates
- hipaa-baa-management: HITECH created BA direct liability and subcontractor requirements
- hipaa-risk-analysis: Risk analysis is a prerequisite for EHR meaningful use/Promoting Interoperability attestation
Telehealth Privacy Compliance
Overview
Telehealth (also termed telemedicine, virtual care, or remote patient monitoring) involves the delivery of healthcare services through electronic communications technologies when the patient and provider are in different locations. The rapid expansion of telehealth — accelerated during the COVID-19 public health emergency — created a complex regulatory environment where HIPAA, state privacy laws, telecommunications regulations, and professional licensing requirements converge. Privacy compliance for telehealth requires addressing the security of the communication platform, the privacy of the encounter, state-specific consent and recording requirements, cross-state practice considerations, and the obligations of technology vendors as business associates.
HIPAA Compliance for Telehealth
Core HIPAA Requirements
Telehealth encounters involve the creation, transmission, and storage of ePHI and are fully subject to HIPAA:
| HIPAA Requirement | Telehealth Application |
|---|---|
| Privacy Rule (§164.500-534) | Telehealth encounters create PHI (notes, prescriptions, diagnoses); all Privacy Rule provisions apply including individual rights, minimum necessary, and authorization requirements |
| Security Rule (§164.312) | Telehealth platform must meet technical safeguards: access controls, audit logs, encryption in transit and at rest, integrity controls |
| Breach Notification Rule (§164.400-414) | Unauthorized access to telehealth session data (recording, transcript, chat) triggers breach notification analysis |
| BAA Requirement (§164.502(e)) | Telehealth technology vendor that creates, receives, maintains, or transmits ePHI must have a BAA with the covered entity |
Platform Security Requirements
Asclepius Health Network evaluates telehealth platforms against these Security Rule requirements:
Access Controls (§164.312(a)):
- Unique user identification for all providers and patients
- Multi-factor authentication for provider access
- Patient authentication through verified identity (DOB verification, registered email/phone, patient portal credentials)
- Session-level access controls — each encounter creates a separate, access-controlled session
- Automatic session termination after provider disconnect or 5-minute inactivity
Audit Controls (§164.312(b)):
- Logging of all session events: initiation, connection, disconnection, duration, participants
- Recording access logs (who accessed any stored recordings)
- Chat/messaging logs maintained as part of the medical record
- Logs retained for minimum 6 years
Transmission Security (§164.312(e)):
- End-to-end encryption for video, audio, and data channels (minimum AES-128; Asclepius requires AES-256)
- TLS 1.2 or higher for signaling and data transport
- No unencrypted fallback — session fails rather than downgrades
- SRTP (Secure Real-time Transport Protocol) for media streams
Integrity Controls (§164.312(c)):
- Tamper-evident session metadata
- Digital signatures on stored encounter records
- Integrity verification on transmitted prescriptions and orders
Platforms Requiring BAA
| Platform Type | BAA Required | Rationale |
|---|---|---|
| Dedicated telehealth platform (Teladoc, Amwell, Doxy.me) | Yes | Creates, receives, maintains, or transmits ePHI |
| Video conferencing adapted for telehealth (Zoom for Healthcare, Microsoft Teams with BAA) | Yes | ePHI transmitted and potentially stored (recordings, chat) |
| Consumer video platforms without BAA (standard Zoom, FaceTime, Skype, Google Hangouts) | No BAA available — generally not compliant | No BAA offered; ePHI not adequately protected |
| EHR-integrated telehealth (Epic MyChart Video Visit) | Covered by existing EHR BAA | ePHI managed within existing BAA relationship |
| Remote patient monitoring devices | Yes (for cloud-connected devices) | Device data transmitted to vendor cloud containing ePHI |
| Asynchronous telehealth (store-and-forward) | Yes | Images, data transmitted and stored by vendor |
| Patient messaging/portal | Covered by existing EHR/portal BAA | Secure messaging within covered platform |
OCR Enforcement Discretion During Public Health Emergency
On March 17, 2020, OCR issued a Notification of Enforcement Discretion for Telehealth Remote Communications (85 FR 22024), stating that during the COVID-19 public health emergency, OCR would exercise enforcement discretion and would not impose penalties for noncompliance with HIPAA related to the good-faith provision of telehealth using non-public-facing remote communication technologies:
What was permitted during enforcement discretion:
- Use of non-public-facing video platforms (Apple FaceTime, Facebook Messenger video, Google Hangouts video, Zoom, Skype) without a BAA
- Covered entities were expected to use encryption and privacy settings available on these platforms
- OCR encouraged providers to notify patients of potential privacy risks
What was NOT permitted even during enforcement discretion:
- Use of public-facing platforms (Facebook Live, Twitch, TikTok) where communications are open to the public
- Abandonment of all privacy protections (providers still had to use reasonable precautions)
Post-PHE Status: The COVID-19 PHE ended on May 11, 2023. OCR enforcement discretion for telehealth formally expired on August 9, 2023. All telehealth must now be conducted on HIPAA-compliant platforms with BAAs in place.
Asclepius Health Network: Asclepius transitioned all telehealth to BAA-covered platforms (Epic MyChart Video Visit as primary; Zoom for Healthcare as backup) prior to the enforcement discretion expiration. All consumer-grade platform use for clinical telehealth was discontinued.
State Licensing Requirements
Cross-State Telehealth Practice
Healthcare providers are generally licensed by individual states. Providing telehealth services to a patient in a state where the provider is not licensed may violate that state's medical practice act.
Key Licensing Models:
| Model | Description | Participating States |
|---|---|---|
| Interstate Medical Licensure Compact (IMLC) | Expedited licensure pathway for physicians seeking multi-state licenses | 42 states, DC, and Guam as of 2024 |
| Nurse Licensure Compact (NLC) | Multistate license allowing RNs and LPN/VNs to practice across member states | 41 states as of 2024 |
| Psychology Interjurisdictional Compact (PSYPACT) | Allows psychologists to practice telepsychology across member states | 42 states as of 2024 |
| Individual state telehealth licenses | Some states offer special telehealth-only or limited-scope licenses | Varies by state (e.g., Florida, Texas telehealth registrations) |
| Full state licensure | Traditional full license in each state where patients are located | All states |
Privacy Implication: The state where the patient is physically located at the time of the telehealth encounter generally controls which state's privacy laws apply. This means the provider must comply with that state's specific privacy, consent, and recording requirements even if the provider is located in a different state.
Asclepius Health Network: Asclepius providers are licensed in the 4 states where Asclepius operates. For telehealth, the EHR prompts the provider to confirm the patient's physical location at the start of each encounter. The system applies location-specific consent requirements and recording notices based on the patient's state.
Recording Consent Requirements
HIPAA and Recording
HIPAA does not specifically address recording of telehealth encounters, but recordings containing ePHI are subject to all HIPAA protections. Recordings become part of or associated with the medical record and must be:
- Stored securely with encryption
- Subject to access controls
- Retained per the entity's record retention policy
- Made available to patients under the right of access (§164.524) if part of the designated record set
State Recording Consent Laws
State wiretapping and eavesdropping laws impose consent requirements on the recording of communications:
| Consent Model | Requirement | States |
|---|---|---|
| One-party consent | Only one participant needs to consent to recording (the provider can record without patient consent, but best practice is to inform) | 38 states + DC including New York, Texas, Ohio, Georgia, Virginia |
| Two-party (all-party) consent | All participants must consent to recording | 12 states: California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, New Hampshire, Pennsylvania, Washington |
Two-party consent states require particular attention: A provider in a one-party state conducting telehealth with a patient in a two-party state must obtain the patient's consent before recording. The more restrictive state law controls.
Asclepius Health Network Recording Policy:
- All telehealth encounters may be recorded for quality assurance and medical record purposes
- Prior to recording, the platform displays a notice and requires patient acknowledgment: "This telehealth visit may be recorded for quality assurance and medical record purposes. Your provider will also be taking notes during the visit. Do you consent to the recording of this visit?"
- For patients in two-party consent states, recording does not proceed without affirmative consent
- For patients who decline recording, the encounter proceeds without recording; the provider documents clinical notes manually
- Recordings are encrypted and stored in the EHR document management system; access is restricted to the care team and authorized quality reviewers
Cross-State Prescribing
Federal Requirements
- DEA: Practitioners must be registered with the DEA to prescribe controlled substances. For telehealth prescribing of controlled substances, the Ryan Haight Act (21 USC §829(e)) generally requires at least one in-person medical evaluation before prescribing controlled substances via telehealth, with exceptions:
- During DEA-declared telemedicine exceptions
- When the patient is at a DEA-registered location (hospital, clinic)
- Under specific state exemptions authorized by DEA
- 2024 DEA proposed rule would establish a pathway for initial telehealth prescribing of Schedule III-V controlled substances with conditions
State Prescribing Rules
| State Requirement | Privacy Implication |
|---|---|
| Prescriber must be licensed in patient's state | Provider credential verification creates PHI (license lookup, verification) |
| State prescription drug monitoring program (PDMP) check required | Provider must access the patient's state PDMP — cross-state PDMP data sharing involves PHI |
| State formulary restrictions | May require disclosure of diagnosis to justify off-formulary prescriptions |
| E-prescribing mandates (most states for controlled substances) | Electronic prescription transmission must be HIPAA-compliant; DEA EPCS standards apply |
Asclepius Health Network: The telehealth platform integrates with the state PDMP for the patient's location. Providers must complete PDMP checks before prescribing controlled substances. The integration uses a HIPAA-compliant API with the state PDMP system. For cross-state encounters, the system automatically routes prescriptions to the correct state PDMP.
Remote Patient Monitoring (RPM) Privacy
RPM-Specific Considerations
Remote patient monitoring involves continuous or periodic collection of health data from devices in the patient's home or on their person:
| RPM Component | Privacy Consideration | HIPAA Requirement |
|---|---|---|
| Monitoring devices (blood pressure cuffs, glucometers, pulse oximeters) | Device data is ePHI; device may store data locally | Encryption on device storage; secure transmission |
| Wearable devices (smartwatches, continuous glucose monitors) | Continuous data collection; potential for excessive data collection beyond medical necessity | Minimum necessary — collect only clinically relevant data; patient consent for monitoring scope |
| Cloud platform for data aggregation | Vendor receives and stores ePHI | BAA required with RPM platform vendor |
| Alerts and notifications | Transmitted health data may reach patient's personal device | Patient education on securing personal devices; notification content should minimize PHI |
| Data integration with EHR | RPM data flows into clinical record | Secure integration (FHIR API with OAuth 2.0); data quality validation |
Patient Consent for RPM
While HIPAA does not require consent for treatment, RPM programs should obtain informed consent addressing:
- What data will be collected and how frequently
- Who will access the data (care team, monitoring center, BA)
- How data will be used (clinical decision-making, AI analytics, quality improvement)
- Patient's ability to pause or stop monitoring
- Security measures protecting transmitted data
- Limitations of RPM (not a substitute for emergency services)
Asclepius Health Network Telehealth Privacy Program
Governance
| Component | Implementation |
|---|---|
| Telehealth Privacy Policy | Comprehensive policy covering platform selection, consent, recording, cross-state compliance, RPM; reviewed annually |
| Platform Approval Process | All telehealth platforms must be approved by IT Security and Privacy Office; BAA executed; security assessment completed |
| Provider Training | Annual telehealth-specific privacy training covering: location verification, consent procedures, recording requirements, secure environment setup |
| Patient Education | Telehealth privacy information provided at scheduling; pre-visit checklist includes privacy tips (private location, headphones, secure WiFi) |
| Incident Response | Telehealth-specific incident playbook covering: unauthorized access to session, recording breach, platform compromise |
| Compliance Monitoring | Monthly audit of telehealth session compliance: location verification completion, consent documentation, platform adherence |
Environmental Security for Providers
Asclepius requires providers conducting telehealth to:
- Use a private room with closed door (no shared/open workspaces)
- Ensure no patient information visible on whiteboards, screens, or papers behind the provider
- Use headphones or earbuds to prevent audio leakage
- Lock workstation screen when stepping away during a session
- Not conduct telehealth visits from public locations (coffee shops, airports)
- Use only Asclepius-managed or approved devices for telehealth
Enforcement
- OCR Enforcement Discretion (2020-2023): During the COVID-19 PHE, OCR exercised enforcement discretion for good-faith telehealth. Post-PHE, full HIPAA enforcement applies.
- No OCR enforcement actions specific to telehealth privacy violations as of early 2025, but OCR has emphasized that the return to normal enforcement means platforms must be HIPAA-compliant with BAAs.
- State AG actions: Multiple state AGs have investigated telehealth companies for privacy practices, particularly regarding consumer-facing telehealth apps that may not be HIPAA-covered entities (Cerebral, Done Health — FTC and state AG investigations in 2023-2024 for unauthorized PHI disclosure to third-party advertisers).
Integration Points
- hipaa-privacy-rule: All telehealth encounters are subject to full Privacy Rule compliance
- hipaa-security-rule: Telehealth platforms must meet all technical safeguards; transmission security is paramount
- hipaa-baa-management: Telehealth vendors require BAAs; evaluation of vendor security posture is critical
- hipaa-breach-notify: Platform compromises or unauthorized recording access trigger breach analysis
- healthcare-ai-privacy: AI integrated into telehealth (AI scribes, clinical decision support during visits) creates compound obligations
- 42-cfr-part-2: Telehealth SUD treatment encounters are subject to Part 2 protections in addition to HIPAA
Sponsors
Details
- Marketplace
- mukul975/Privacy-Data-Protection-Skills
- Source
- plugins/healthcare-privacy-skills
- Author
- Mahipal
- Category
- Compliance
- License
- Apache-2.0
- Keywords
- hipaa, healthcare, phi, security-rule, privacy-rule
More from mukul975/Privacy-Data-Protection-Skills
All 21- privacy-audit-skillsv1.0.0
- privacy-by-design-skillsv1.0.0
- privacy-engineering-skillsv1.0.0
- privacy-impact-assessment-skillsv1.0.0
- privacy-skills-completev1.0.0
- records-of-processing-skillsv1.0.0
- us-state-privacy-skillsv1.0.0
- vendor-privacy-management-skillsv1.0.0
- ai-privacy-governance-skillsv1.0.0
- children-privacy-skillsv1.0.0
- consent-management-skillsv1.0.0
- cookie-consent-skillsv1.0.0
- cross-border-transfers-skillsv1.0.0
- data-breach-response-skillsv1.0.0
- data-classification-skillsv1.0.0
- data-retention-skillsv1.0.0
- data-subject-rights-skillsv1.0.0
- employee-privacy-skillsv1.0.0
- gdpr-compliance-skillsv1.0.0
- global-privacy-regulations-skillsv1.0.0