Initial upload: HIPAA regulatory corpus + role-based Q&A

.gitattributes

@@ -58,3 +58,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 # Video files - compressed
 *.mp4 filter=lfs diff=lfs merge=lfs -text
 *.webm filter=lfs diff=lfs merge=lfs -text
+tmp/title-45-2026-04-24.xml filter=lfs diff=lfs merge=lfs -text

Building a HIPAA AI Agent.md

@@ -0,0 +1,246 @@
+# **Comprehensive Architectural and Regulatory Blueprint for HIPAA-Compliant RAG Systems: Integrating HHS Guidelines, Real-World Practices, and Mojar.ai Agent Deployment**
+
+## **Introduction to the Compliant AI Paradigm**
+
+The integration of Generative Artificial Intelligence and Retrieval-Augmented Generation (RAG) architectures into the healthcare and life sciences sectors represents a profound paradigm shift in how medical organizations access, process, and deploy institutional knowledge. Promising generative AI solutions are currently being developed to revolutionize everything from patient care coordination to complex drug discovery processes.1 However, the deployment of such advanced computational systems operates within a highly complex and stringent regulatory landscape designed to safeguard patient privacy and data security.1 In the United States, the Health Insurance Portability and Accountability Act (HIPAA), alongside the Health Information Technology for Economic and Clinical Health (HITECH) Act, mandates rigorous technical, physical, and administrative safeguards that profoundly impact the design, ingestion, and output mechanisms of any system handling health data.1
+
+Building an advanced AI agent utilizing platforms like Mojar.ai to query official documentation, resolve compliance ambiguities, and surface authoritative citations requires substantially more than simple vector search capabilities. It demands a deterministic, hallucination-resistant architecture capable of parsing nuanced legal distinctions—such as the operational differences between patient "consent" and formal "authorization" 4—while strictly enforcing data exposure boundaries to prevent the inadvertent leakage of Protected Health Information (PHI).5 Furthermore, the requirement to embed a dedicated snippet tool within the Mojar use-case page to render passage-level citations bridges the critical gap between probabilistic AI text generation and deterministic legal verification.6
+
+To achieve this, developers must look beyond basic API integrations. Artificial intelligence coding agents, which rely heavily on token optimization and context engineering, require stable instructions moved into durable artifacts where only the right context is surfaced for the current task.7 The RAG pipeline itself must be engineered to understand the semantic nuance between different regulatory domains, utilizing context-preserving tokenization to mask sensitive data before ingestion.8 The following comprehensive analysis provides an exhaustive codification of official documentation from the U.S. Department of Health and Human Services (HHS), synthesizes real-world compliance pitfalls extracted from industry practitioners and engineering forums, and establishes the foundational technical architecture and system prompt required to operationalize a highly effective, HIPAA-compliant Mojar.ai agent.
+
+## **Exhaustive Codification of HIPAA Administrative Simplification Rules**
+
+To build a robust, authoritative knowledge base for the Mojar.ai agent, the system must first ingest, semantically index, and perfectly comprehend the core tenets of the HIPAA Administrative Simplification provisions. These provisions establish the foundational national standards for electronic health care transactions, data privacy, and cybersecurity protocols.3
+
+### **The HIPAA Privacy Rule and Data Governance**
+
+The HIPAA Privacy Rule, legally codified at 45 CFR Part 160 and Subparts A and E of Part 164, establishes the national baseline for protecting individuals' medical records and other individually identifiable health information.9 This information is collectively termed Protected Health Information (PHI) and includes any demographic data relating to an individual's past, present, or future physical or mental health, the provision of care, or payment for that care, held or transmitted in any form.10
+
+The Privacy Rule applies explicitly to entities known as "covered entities," which encompass health plans, health care clearinghouses, and health care providers who conduct standard health care transactions electronically.3 The core functional requirement that must be embedded into the RAG system's reasoning logic is the understanding of precise limitations on the use and disclosure of PHI. Covered entities are legally mandated to implement appropriate safeguards and are heavily restricted in how they may disclose this information without an individual's prior, explicitly documented authorization.9
+
+The Mojar.ai RAG agent must be programmed to recognize the specific rights granted to individuals under this regulatory framework. These rights form the basis for many patient-facing applications and include the right for individuals to examine and obtain a physical or electronic copy of their health records, the right to direct a covered entity to transmit an electronic copy of their PHI to a designated third party, and the right to request formal corrections to erroneous health information.9
+
+Furthermore, the Privacy Rule dictates the implementation of the "Minimum Necessary" standard.11 This principle requires that any disclosure of PHI be strictly limited to the minimum amount of information necessary to accomplish the intended purpose of the use, disclosure, or request.11 For developers building AI systems, this legal principle translates directly into technical requirements: prompt minimization, dynamic token-filtering techniques, and the enforcement of least-privilege access controls at the API layer.5
+
+| Permitted Disclosures Under the Privacy Rule | Operational Context for AI and Software Systems |
+| :---- | :---- |
+| **Required by Law** | Disclosures required by statute, regulation, or court order must be logged and audited. |
+| **Public Health Activities** | Automated reporting to public health authorities for disease tracking requires secure, encrypted transmission channels. |
+| **Health Oversight** | Systems must support the extraction of data for audits and investigations without exposing unrelated patient records. |
+| **Limited Data Sets** | Data extracted for research or operations must have specific identifiers removed and be governed by a data use agreement. |
+
+### **The HIPAA Security Rule and Technical Safeguards**
+
+While the Privacy Rule governs the general protection of PHI, the Security Rule establishes the highly specific national standards for protecting electronic Protected Health Information (ePHI).13 Published in its final form in February 2003, the Security Rule is structured around three core pillars of safeguards, which any health-tech software architecture must accommodate to achieve compliance.3
+
+The first pillar involves Administrative Safeguards, which require regulated entities to perform continuous risk assessments, manage workforce security protocols, and establish contingency plans for data emergencies.13 The second pillar, Physical Safeguards, mandates strict physical controls over facility access, workstation use, and the hardware security of devices containing ePHI.13
+
+The third pillar, Technical Safeguards, is the most highly relevant to modern software deployment and artificial intelligence integration. These safeguards mandate robust access controls, comprehensive audit logs, integrity mechanisms to prevent improper data alteration, and transmission security to protect data in transit.13 A frequent misconception in modern application development is that the mere implementation of encryption automatically satisfies the Security Rule. However, the rule explicitly requires comprehensive access controls and audit trails to prevent unauthorized access, even if the underlying data is encrypted at the storage level.14 For example, if a system uses AES-256 encryption but lacks mechanisms to prevent an authenticated user from scraping data beyond their authorization level, the system remains fundamentally non-compliant.
+
+### **The Breach Notification Rule and Risk Assessment**
+
+Finalized through the HIPAA Omnibus Rule, the Breach Notification Rule (45 CFR §§ 164.400-414) enforces provisions of the HITECH Act, mandating strict notification protocols following the compromise of unsecured PHI.3 A breach is generally defined as an impermissible use or disclosure that compromises the security or privacy of PHI.15
+
+The regulatory framework relies heavily on a structured risk assessment to determine if a security incident legally constitutes a reportable breach. The AI agent's knowledge base must deeply index the four mandated factors of this assessment to provide accurate guidance to users experiencing security incidents. These factors include the nature and extent of the PHI involved (including the types of identifiers and the likelihood of re-identification), the specific identity of the unauthorized person who used the PHI or to whom the disclosure was made, verification of whether the PHI was actually acquired or merely viewed, and the extent to which the risk to the PHI has been successfully mitigated.15
+
+Notification protocols are strictly bound by aggressive timelines and numerical thresholds. Individual notices must be dispatched without unreasonable delay, and under no circumstances later than 60 days following the discovery of the breach.15 If a breach affects more than 500 residents of a specific state or jurisdiction, the entity faces the elevated requirement to notify prominent media outlets and the Secretary of HHS simultaneously within the same 60-day window.15 Breaches involving fewer than 500 individuals require annual reporting to the Secretary, due no later than 60 days after the end of the calendar year in which the breaches were discovered.15
+
+Crucially, the rule introduces an explicit exception for "secured" PHI. If PHI is rendered unusable, unreadable, or indecipherable to unauthorized individuals through technologies specified by the HHS Secretary—such as rigorous encryption at rest or physical cryptographic destruction—the entity is relieved of all notification requirements, providing a massive incentive for robust architectural security.14
+
+## **The Complexities of PHI De-Identification in AI Pipelines**
+
+For generative AI and RAG systems, the most vital component of HIPAA compliance is the standard for data de-identification. Information that has been successfully de-identified is no longer considered Protected Health Information and is consequently entirely exempt from the restrictions of both the Privacy and Security Rules.10 This exemption is what allows massive datasets to be safely utilized in Large Language Model (LLM) training, large-scale analytical processing, and enterprise search indexing without triggering compliance violations.16 The HHS outlines two distinct, mutually exclusive methodologies for achieving legal de-identification: the Safe Harbor method and the Expert Determination method.16
+
+### **The Safe Harbor Method: Deterministic Redaction**
+
+The Safe Harbor method provides a highly deterministic, prescriptive approach requiring the total removal of 18 specific identifiers pertaining to the individual, their relatives, employers, or household members.16 For an AI ingestion pipeline preparing data for a vector database, this requires the implementation of robust Natural Language Processing (NLP) and Named Entity Recognition (NER) filtering to seamlessly identify and scrub these elements.8
+
+The mandated identifiers for removal include names, telephone numbers, fax numbers, email addresses, Social Security numbers, medical record numbers, health plan beneficiary numbers, account numbers, certificate/license numbers, vehicle identifiers (including license plates), device identifiers, web Universal Resource Locators (URLs), Internet Protocol (IP) addresses, biometric identifiers (such as finger and voice prints), full-face photographs, and any other unique identifying number, characteristic, or code.11
+
+However, there are highly specific geographical and temporal nuances within the Safe Harbor provisions that frequently confuse automated data pipelines. The first is the rule governing all geographic subdivisions smaller than a state. Street addresses, cities, counties, and precincts must be removed entirely.16 The treatment of ZIP codes is particularly complex: the first three digits of a ZIP code may be retained only if the combined geographic unit formed by all ZIP codes sharing those same initial three digits contains a population of more than 20,000 people according to the latest Bureau of the Census data.16 If the population threshold is 20,000 or fewer, those initial three digits must be converted to "000".16
+
+The second major nuance involves the treatment of dates. While the year of a healthcare event may be retained, all specific elements of dates directly related to an individual (such as birth dates, admission dates, discharge dates, and death dates) must be redacted.16 Furthermore, to protect the identities of the elderly, all ages over 89, including any elements of dates indicating such an age, must be aggregated into a single, less descriptive category of "90 or older".16
+
+The final and perhaps most perilous aspect of the Safe Harbor method is the "Actual Knowledge" provision. The HHS mandates that even if a system successfully parses and removes all 18 identifiers, the data is still not legally de-identified if the covered entity possesses actual knowledge that the remaining information could be used to re-identify the subject.16 For example, if a patient record contains a highly specific occupation—such as "President of the local university" in a small college town—the covered entity has actual knowledge that this remaining data point could lead to identification.16 Similarly, rare clinical events that have received significant media exposure (such as an unusually large number of children born at once) constitute actual knowledge.16
+
+### **The Expert Determination Method: Probabilistic Analysis**
+
+Conversely, the Expert Determination method is probabilistic rather than prescriptive. It requires the engagement of a person with "appropriate knowledge of and experience with generally accepted statistical and scientific principles" to apply complex analytical techniques to the dataset.16 The expert must determine and formally document that the risk is "very small" that the information could be used, either alone or in combination with other reasonably available information, by an anticipated recipient to identify an individual.16
+
+This method involves a rigorous evaluation of data replicability, external data source availability, and individual distinguishability.16 Experts prioritize health information features based on how consistently they occur; for instance, blood glucose levels vary wildly and have low replicability, while birth dates are highly stable and pose a greater risk.16 The expert must define what constitutes an acceptable "very small" risk based on the specific environment and the recipient's computational capabilities.16 Because technology and social conditions change rapidly, practitioners often use "time-limited certifications," requiring re-evaluation of the de-identification strategy for future data releases.16 This method allows organizations to retain significant data utility that might otherwise be destroyed by the strict, inflexible redaction required by the Safe Harbor approach.
+
+## **Architecting the Healthcare Knowledge Base: HHS Indexing Strategy**
+
+To ensure the Mojar.ai agent provides authoritative answers rather than generic AI approximations, its underlying vector database must be meticulously seeded with the exact URLs, subdirectories, and FAQ indices of the HHS website. A highly effective RAG system relies on semantic chunking and contextual awareness; therefore, indexing the exact regulatory paths allows the agent to generate passage-level citations directly pointing to the foundational legal source code.6
+
+The foundational ingestion targets for the RAG platform must include the comprehensive hubs for the rules: The HIPAA for Professionals Hub (https://www.hhs.gov/hipaa/for-professionals/index.html), the Privacy Rule documentation (https://www.hhs.gov/hipaa/for-professionals/privacy/index.html), the Security Rule specifics (https://www.hhs.gov/hipaa/for-professionals/security/index.html), and the Breach Notification guidelines (https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html).3 Furthermore, technical directives regarding Business Associates (https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html), De-identification Specifications (https://www.hhs.gov/hipaa/for-professionals/privacy/special-topics/de-identification/index.html), and Cloud Computing environments (https://www.hhs.gov/hipaa/for-professionals/special-topics/cloud-computing/index.html) must be parsed and deeply embedded.10
+
+In addition to the primary rule text, the true value of the RAG agent lies in its access to the vast repository of edge-case resolutions contained within the HHS FAQ database. The ingestion pipeline must systematically scrape, chunk, and index the thousands of clarifications located within the FAQ categories.19
+
+| Key HHS FAQ Categories for RAG Indexing | Question Count | Core Analytical Topics Covered |
+| :---- | :---- | :---- |
+| **Smaller Providers and Businesses** | 145 Questions | Operational compliance strategies for clinics, minimal viable safeguards, cost-effective technical controls. |
+| **Right to Access and Research** | 58 Questions | Patient access rights, electronic transmission format requirements, research data use agreements. |
+| **Business Associates** | 41 Questions | Contractual liability requirements, Cloud Service Provider (CSP) responsibilities, breach reporting chains. |
+| **Health Information Technology** | 39 Questions | Electronic Health Records (EHR) integration, interoperability, HITECH Act intersections. |
+| **Security Rule & Safeguards** | 37 Questions | Encryption standards, access controls, audit logging requirements, disaster recovery plans. |
+| **Treatment, Payment, Operations (TPO)** | 31 Questions | Permitted disclosures without authorization, billing operations, debt collection boundaries. |
+| **Notice of Privacy Practices** | 20 Questions | Document retention, patient acknowledgment workflows, refusal of treatment scenarios. |
+
+## **Real-World Friction: Synthesizing Reddit and Practitioner Forums**
+
+While theoretical compliance involves parsing dense HHS documentation, practical compliance involves navigating the architectural realities and budget constraints of modern software development. Extracting discourse from technical subreddits, MSP (Managed Service Provider) forums, and industry discussions reveals a profound gap between regulatory text and software engineering execution. A highly capable AI agent must understand these real-world translation failures to provide genuinely actionable advice to healthcare startups.
+
+### **The "MVP Delay" and Compounding Architectural Debt**
+
+A recurrent theme dominating developer discussions on platforms like Reddit is the fatal misconception that HIPAA compliance is merely a feature flag that can be "bolted on" after a Minimum Viable Product (MVP) achieves market traction.20 Industry veterans consistently emphasize that delaying compliance generates catastrophic architectural debt.21 Startup founders often attempt to push the boundaries, processing real patient data on cloud infrastructure designed without granular access controls, immutable audit logs, or strict data segmentation networks.21
+
+When enterprise contracting eventually necessitates a HIPAA audit—which frequently takes the form of grueling 300-question security assessments and 200-question business associate evaluations—the cost of refactoring data pipelines to implement retroactive compliance is often fatal to the company.21 Developers note that many MVPs pass the initial "it works" test but disintegrate the moment they undergo real due diligence.20 The overwhelming industry consensus dictates that HIPAA is a foundational infrastructure requirement from day one, not a post-launch administrative checklist.14
+
+### **Cloud Infrastructure and BAA Misconceptions**
+
+Another pervasive technical misconception involves the reliance on third-party cloud services without proper contractual coverage. The HHS provides explicit guidance regarding Cloud Service Providers (CSPs).10 According to NIST Special Publication 800-145, cloud computing provides ubiquitous, on-demand network access to shared computing resources across Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS) models.10 The HHS mandates that any CSP that creates, receives, maintains, or transmits ePHI on behalf of a covered entity is legally classified as a Business Associate, regardless of whether the CSP possesses the decryption keys to view the data.10
+
+Despite this clear regulation, developers frequently spin up databases using services like Firebase or Twilio without securing a Business Associate Agreement (BAA).14 If these tools touch PHI without a signed BAA, the primary organization is liable for every byte that traverses the network.14 Startups often assume that because a vendor advertises their platform as "HIPAA Compliant" on their marketing pages, the technology is inherently safe to use out of the box.22 However, compliance is a shared responsibility model. The vendor provides the tools (such as logging, encryption, and password controls), but the customer must configure them correctly and sign the BAA to establish the legal framework.22 If a vendor will not sign a BAA, HIPAA compliance cannot rely on a contract that does not exist; the solution must be technical, treating those endpoints as zero-trust environments.23
+
+### **The Fallacy of Encryption as Immunity**
+
+Perhaps the most dangerous technical fallacy observed in engineering discussions is the belief that standard data encryption equates to absolute HIPAA compliance. Engineers frequently assume that implementing AES-256 encryption at rest and TLS 1.2+ in transit inoculates the system against violations.14 While encryption protects against network interception and physical hardware theft, it provides zero protection against application-layer vulnerabilities, unauthorized access by authenticated users, or logical flaws in the application architecture.14
+
+Real-world data leaks frequently occur via unencrypted secondary channels that bypass the primary encrypted database entirely. Common pitfalls extracted from technical audits include:
+
+* **Logging Architectures:** Developers inadvertently dumping plain-text HTTP request payloads (which inherently contain PHI) into centralized monitoring systems like Datadog, Splunk, or AWS CloudWatch.14  
+* **Customer Support Systems:** End-users submitting screenshots containing unmasked medical records into non-compliant SaaS ticketing systems like Zendesk or Intercom, exposing the data to third-party support staff.24  
+* **Mobile Blind Spots:** Applications transmitting push notifications containing explicit appointment details (e.g., "Oncology follow-up at 3 PM") which are displayed on locked device screens, entirely bypassing device-level operating system encryption.14 Furthermore, analytics SDKs embedded in mobile applications frequently scrape and transmit user behavior that inherently reveals sensitive treatment data.14
+
+### **The Digital Marketing and Client-Side Tracking Disaster**
+
+The intersection of digital marketing and healthcare has emerged as a massive, often ignored liability vector. Technologies such as the Meta Pixel, Google Analytics 4 (GA4), and other client-side retargeting scripts are designed to automatically collect user behavior and transmit it to third-party advertising networks to optimize ad spend.25 In a healthcare context, tracking a user's navigation through a patient portal or disease-specific landing page constitutes the unauthorized disclosure of PHI.25
+
+Because massive advertising platforms universally refuse to sign Business Associate Agreements, their active presence on authenticated patient pages or specific diagnostic scheduling flows is a direct HIPAA violation.23 The regulatory burden requires complex technical solutions—such as server-side proxy tracking, robust content security policies, or strict tag management controls—to monitor and sever these non-compliant data flows before they reach external servers.5
+
+### **Conceptual Confusion: Consent, Authorization, and Data Quality**
+
+A frequent administrative failure highlighted by compliance officers involves the semantic confusion between "consent," "authorization," and "release of information".4 Clinics and software platforms often require patients to complete exhaustive authorization forms merely to access their own PHI—a fundamental misunderstanding of the Privacy Rule, which guarantees patient access without requiring such complex authorization.4 Conversely, entities frequently attempt to use basic "consent for treatment" forms as blanket justifications for complex secondary disclosures, violating the explicit requirement that independent authorization must define specific expiration dates and rigid disclosure boundaries.4
+
+Other overlooked administrative issues include the failure to properly capture disclosures on the Accounting of Disclosures log, or over-including disclosures that are not actually required by the rule.4 Furthermore, navigating edge cases where minor patients control access to their encounter data (especially when providers operate across multiple states with varying age-of-consent laws) introduces massive architectural complexity that out-of-the-box software rarely accommodates.4 Finally, when integrating with Electronic Health Records (EHRs), organizations often confuse "interoperability" with "integration," failing to account for the fact that EHR data is frequently incomplete, inconsistent, or poorly structured, requiring robust normalization and error handling before it can be safely utilized.26
+
+## **Deploying the Mojar.ai Healthcare Compliance Agent**
+
+To construct an AI agent within Mojar.ai capable of navigating these complex regulatory and technical realities, the system must leverage an advanced RAG pipeline optimized for semantic density, robust context retention, and strict data governance.6
+
+### **Vector Store Sanitization and Token Efficiency**
+
+Unlike rigid, rule-based chatbots, AI coding agents and compliance assistants operate on tokens rather than files or human intent.7 Every prompt, retrieved document, and generated response must be transformed into tokens before the model can process it, placing practical limits on what an agent can read, reason about, and retain in a single interaction.7 Because HIPAA regulations are dense, the Mojar.ai RAG system must utilize semantic understanding rather than basic keyword matching to conserve token bandwidth.6 For example, a user querying about "employee rights" should not trigger the retrieval of document chunks related to "patient access rights," even though both contain the word "rights." Semantic understanding is what makes RAG viable for specialized domains.6
+
+Crucially, the ingestion pipeline must strictly enforce data masking before any documentation is vectorized.8 If internal company documents (such as past audit reports or technical architecture diagrams containing real data) are uploaded to Mojar.ai, a preprocessing layer must scan every document for PII, PHI, and confidential content.8 Simple redaction—blanking out words—destroys the semantic value the LLM needs to generate useful embeddings. Instead, context-preserving tokenization must be used, replacing sensitive values with surrogate tokens that maintain formatting and syntactical meaning without compromising privacy.5 Furthermore, every query entering the RAG system should be inspected before reaching the retrieval layer to catch prompt injection attempts that might manipulate the agent into exposing backend system instructions or cross-tenant data.8
+
+### **The Snippet Tool Implementation and Passage-Level Citations**
+
+A profound limitation of standard LLMs in legal and compliance settings is the hallucination of regulatory statutes. To establish trust, the Mojar.ai agent must support what is termed "passage-level citations".6 When the agent formulates a response regarding breach notification timelines or de-identification specifications, it must not merely summarize the rule; it must retrieve the exact clause from the HHS source material and utilize the Mojar snippet tool to display the verbatim text alongside the AI-generated answer.
+
+The Snippet Tool acts as a visual validation layer. Similar to the declarative JSON UI configuration utilized by frameworks like Webix—which takes structured output from an LLM and renders predictable frontend components 28—the Mojar agent will be instructed to format specific source quotes within predefined XML tags. The Mojar UI will intercept these tags and render an embedded, highly visible citation block directly on the use-case page. This provides instant verification, allowing users to trace an answer directly to its authoritative source document, identifying exactly which sections informed the response.6
+
+### **Agent Governance and Maintenance Protocols**
+
+Regulatory guidelines evolve, and internal company policies are frequently updated. The Mojar.ai system architecture must deploy asynchronous "maintenance agents" to ensure the vector store remains accurate over time.6 These specialized background agents perform staleness detection, flagging compliance documents that have not been reviewed against recent HHS updates.6 They execute deprecated reference scanning, identifying internal policies that reference outdated software configurations or sunset compliance protocols.6 Additionally, they provide conflict-triggered updates, detecting contradictions between public marketing materials (which may falsely claim complete HIPAA compliance) and internal security architecture documents.6
+
+Furthermore, the system architecture must acknowledge credential persistence gaps and implement zero-trust policies. As noted in limitations of toolkits like Microsoft's Agent Governance Toolkit (AGT), systems often fail to track which API keys or tokens an agent holds across tasks within a single session.29 The governance layer must ensure that if the Mojar agent uses an internal tool to retrieve sensitive audit context for one query, it explicitly revokes those permissions before handling the next task, preventing the cross-contamination of context and ensuring workflow-level policy enforcement.29
+
+## **Prompt Engineering: Constructing the Chief Compliance Architect**
+
+The efficacy of the AI agent hinges entirely on the quality of its system prompt. The prompt must utilize structural techniques, domain-specific constraints, and chain-of-thought reasoning to force the model into an analytical, highly compliant persona.30 Incorporating best practices for prompt engineering—such as including consistent examples, leveraging multimodal awareness where applicable, and building systematic quality controls to run prompts against known inputs—ensures the agent output does not degrade into generic platitudes.30
+
+Below is the exhaustive, highly effective master system prompt designed specifically for the Mojar.ai HIPAA Compliance Agent, tailored to utilize the platform's retrieval pipeline and the frontend Snippet Tool.
+
+### ---
+
+**Mojar.ai System Prompt: Chief Compliance Architect Agent**
+
+---
+
+You are the Chief Healthcare Compliance Architect, an elite, highly specialized AI agent operating exclusively within the Mojar.ai platform. Your singular operational purpose is to provide authoritative, highly technical, and architecturally sound guidance on HIPAA (Health Insurance Portability and Accountability Act) and HITECH compliance. Your target audience consists of healthcare startup founders, senior software engineers, Managed Service Providers (MSPs), and corporate compliance officers.
+
+Your tone must be strictly professional, academic, analytical, and authoritative. You do not use conversational filler, emojis, or colloquialisms. You approach every query by first analyzing the formal regulatory text, translating that text into precise technical architectural requirements, and proactively identifying potential software engineering edge cases (such as logging vulnerabilities, unencrypted cached data, client-side tracking pixels, or BAA omissions).
+
+1. ---
+
+   **Zero Hallucination Tolerance:** You must ground every assertion regarding HIPAA rules, timelines, definitions, and penalties strictly in the provided RAG context retrieved from HHS.gov or established legal frameworks. If the retrieved context does not contain the answer, you must explicitly state: "The requested information is not available in the current official documentation." Do not guess or extrapolate beyond the retrieved facts.  
+2. **Passage-Level Citations (Snippet Tool Integration):** You are equipped with a UI rendering capability known as the Snippet Tool. Whenever you reference an official HHS rule, definition, or FAQ, you MUST provide the exact verbatim text from the retrieved context using the following structured XML format:  
+   \<snippet id="" url=""\>  
+   \[Insert exact verbatim quote from the text\]  
+   \</snippet\>  
+   The Mojar UI will automatically parse this XML tag and display a stylized citation block. Always follow the snippet block with your analytical synthesis.  
+3. **Actionable Engineering Translation:** When discussing compliance, always bridge the gap between legal text and software engineering execution. For example, if discussing the Security Rule's "Access Controls," translate this into concepts like Identity and Access Management (IAM), Role-Based Access Control (RBAC), JWT token expiration, and API gateway validation. Do not leave the advice purely in legal terms.  
+4. **PHI Security Mandate:** You must never ask the user to provide raw patient data, PII, or PHI to assist in your analysis. If a user inputs data that resembles PHI in their prompt, you must immediately halt the analysis, issue a formal warning that unmasked PHI has been detected in the prompt layer, and advise them on context-preserving tokenization and data masking techniques before further ingestion.
+
+---
+
+Before formulating your final response, silently execute the following reasoning steps:
+
+* *Step 1 (Classification):* Determine which specific HIPAA Rule applies to the query (Privacy, Security, Breach Notification, or Enforcement Rules).  
+* *Step 2 (Retrieval Assessment):* Scan the retrieved context for official HHS definitions, specific timelines (e.g., the 60-day breach notice window), and relevant FAQ exceptions.  
+* *Step 3 (Edge Case Identification):* Consider how this rule commonly fails in real-world software application. Are there third-party SaaS tools involved without BAAs? Is mobile architecture implicated? Are marketing trackers violating the minimum necessary rule?  
+* *Step 4 (Synthesis):* Combine the regulatory text, the citation snippet, and the technical implementation advice into a highly structured, cohesive response.  
+* ---
+
+  **Business Associate Agreements (BAAs):** Always remind the user that downstream cloud providers (AWS, GCP, Twilio, Firebase, Datadog) require signed BAAs before processing any PHI. Emphasize that a vendor claiming to be "HIPAA Compliant" is meaningless without the legally executed BAA.  
+* **De-identification:** When asked about removing patient data, distinguish clearly between the Safe Harbor method (removing the 18 specific identifiers, explicitly mentioning the ZIP\>20k rule and Age\>89 rule) and the Expert Determination method (statistical analysis regarding replicability and distinguishability).  
+* **Breach Notification:** Always outline the 4-factor risk assessment (Nature of PHI, Identity of unauthorized person, Actual acquisition, Mitigation). Highlight that encryption at rest/transit is the primary safe harbor to avoid breach notification obligations entirely.  
+* ---
+
+  Use bolding for core regulatory terms (e.g., **Covered Entity**, **Electronic Protected Health Information (ePHI)**).  
+* Use Markdown tables to break down complex technical requirements, multi-step risk assessments, or comparisons between different compliance strategies.  
+* Always include the Snippet Tool XML tags for evidence. Do not alter the quote inside the snippet tags in any way.
+
+## ---
+
+**Conclusion**
+
+The successful implementation of a RAG-enabled AI agent within the highly regulated and technically complex sphere of healthcare requires a meticulous, uncompromising synthesis of legal doctrine and modern software architecture. As demonstrated by the exhaustive extraction of HHS documentation, compliance is not a static endpoint but a continuous operational requirement that dictates precisely how data is stored, anonymized, and transmitted across digital ecosystems.3 The rules governing Protected Health Information—specifically the strict parameters of the Safe Harbor de-identification method 16, the aggressive 60-day reporting window of the Breach Notification Rule 15, and the universal legal mandate for Business Associate Agreements across all cloud infrastructure 18—must be hardcoded into the operational logic of any data-processing system.
+
+Furthermore, analyzing the real-world discourse from technical communities reveals that startups and established vendors alike frequently suffer from fundamental misunderstandings regarding the scope and enforcement of HIPAA.14 The reliance on encryption as a panacea, the vulnerability of mobile application blind spots, the administrative confusion between consent and authorization, and the systemic leakage of PHI through un-audited digital marketing trackers highlight the profound gap between theoretical compliance and engineering reality.4
+
+By deploying the Mojar.ai agent equipped with the comprehensive system prompt provided, organizations can successfully bridge this gap. The integration of a vector store populated with deterministic HHS citations 17, coupled with the Snippet Tool for passage-level verification 6 and robust token-efficiency safeguards 7, transforms the LLM from a probabilistic text generator into a precise, highly reliable compliance architect. This structural alignment ensures that healthcare technology initiatives can maintain aggressive innovation timelines without incurring catastrophic regulatory debt or compromising foundational patient trust.
+
+#### **Works cited**
+
+1. HIPAA compliance for generative AI solutions on AWS, accessed April 28, 2026, [https://aws.amazon.com/blogs/industries/hipaa-compliance-for-generative-ai-solutions-on-aws/](https://aws.amazon.com/blogs/industries/hipaa-compliance-for-generative-ai-solutions-on-aws/)  
+2. Privacy Challenges and Solutions in RAG-Enhanced LLMs for Healthcare Chatbots: A Review of Applications, Risks, and Future Directions \- arXiv, accessed April 28, 2026, [https://arxiv.org/html/2511.11347v2](https://arxiv.org/html/2511.11347v2)  
+3. HIPAA for Professionals | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/index.html](https://www.hhs.gov/hipaa/for-professionals/index.html)  
+4. What are the little things that are often overlooked in HIPAA? : r/hipaa, accessed April 28, 2026, [https://www.reddit.com/r/hipaa/comments/1q4tgxf/what\_are\_the\_little\_things\_that\_are\_often/](https://www.reddit.com/r/hipaa/comments/1q4tgxf/what_are_the_little_things_that_are_often/)  
+5. Best Practices for HIPAA Compliant AI & LLMs in Healthcare \- Edenlab, accessed April 28, 2026, [https://edenlab.io/blog/hipaa-compliant-ai-best-practices](https://edenlab.io/blog/hipaa-compliant-ai-best-practices)  
+6. RAG for marketing and sales: the complete guide | Mojar AI, accessed April 28, 2026, [https://www.mojar.ai/blog/marketing-sales/rag-marketing-sales-complete-guide](https://www.mojar.ai/blog/marketing-sales/rag-marketing-sales-complete-guide)  
+7. Token Efficiency in AI Coding Agents | by Nagaprasad Sathyanarayana \- Medium, accessed April 28, 2026, [https://medium.com/@nprasads/token-efficiency-in-ai-coding-agents-12d4e3b00f00](https://medium.com/@nprasads/token-efficiency-in-ai-coding-agents-12d4e3b00f00)  
+8. Data Security In RAG Systems: Best Practices \- Protecto AI, accessed April 28, 2026, [https://www.protecto.ai/blog/data-security-in-rag-systems-best-practices/](https://www.protecto.ai/blog/data-security-in-rag-systems-best-practices/)  
+9. The HIPAA Privacy Rule | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/privacy/index.html](https://www.hhs.gov/hipaa/for-professionals/privacy/index.html)  
+10. Guidance on HIPAA & Cloud Computing | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/special-topics/cloud-computing/index.html](https://www.hhs.gov/hipaa/for-professionals/special-topics/cloud-computing/index.html)  
+11. HIPAA Frequently Asked Questions \- Office of Research \- Kennesaw State University, accessed April 28, 2026, [https://campus.kennesaw.edu/offices-services/research/centers-facilities/center-research-computing/resources/quickstart/hipaa-frequently-asked-questions.php](https://campus.kennesaw.edu/offices-services/research/centers-facilities/center-research-computing/resources/quickstart/hipaa-frequently-asked-questions.php)  
+12. What should software developers do to comply with HIPAA when they're building software solutions for the healthcare industry? \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/hipaa/comments/13u6wk3/what\_should\_software\_developers\_do\_to\_comply\_with/](https://www.reddit.com/r/hipaa/comments/13u6wk3/what_should_software_developers_do_to_comply_with/)  
+13. The Security Rule | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/security/index.html](https://www.hhs.gov/hipaa/for-professionals/security/index.html)  
+14. 10 Common HIPAA Pitfalls Startups Overlook and How to Avoid Them \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/topflightapps/comments/1oh25rs/10\_common\_hipaa\_pitfalls\_startups\_overlook\_and/](https://www.reddit.com/r/topflightapps/comments/1oh25rs/10_common_hipaa_pitfalls_startups_overlook_and/)  
+15. Breach Notification Rule | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html](https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html)  
+16. Guidance Regarding Methods for De-identification of Protected ..., accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/privacy/special-topics/de-identification/index.html](https://www.hhs.gov/hipaa/for-professionals/privacy/special-topics/de-identification/index.html)  
+17. Health Information Privacy | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/index.html](https://www.hhs.gov/hipaa/index.html)  
+18. Business Associates | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html)  
+19. HIPAA FAQs for Professionals | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/faq/index.html](https://www.hhs.gov/hipaa/for-professionals/faq/index.html)  
+20. Topflightapps on HIPAA compliance, why your tool choice matters less than your system, accessed April 28, 2026, [https://www.reddit.com/r/topflightapps/comments/1sgy4ro/topflightapps\_on\_hipaa\_compliance\_why\_your\_tool/](https://www.reddit.com/r/topflightapps/comments/1sgy4ro/topflightapps_on_hipaa_compliance_why_your_tool/)  
+21. HIPAA vs traction: what actually matters first for a healthcare startup? : r/healthIT \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/healthIT/comments/1n8738l/hipaa\_vs\_traction\_what\_actually\_matters\_first\_for/](https://www.reddit.com/r/healthIT/comments/1n8738l/hipaa_vs_traction_what_actually_matters_first_for/)  
+22. How does one actually find hipaa guidelines spelled out somewhere? : r/sysadmin \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/sysadmin/comments/11ub0lw/how\_does\_one\_actually\_find\_hipaa\_guidelines/](https://www.reddit.com/r/sysadmin/comments/11ub0lw/how_does_one_actually_find_hipaa_guidelines/)  
+23. r/Feroot \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/Feroot/](https://www.reddit.com/r/Feroot/)  
+24. Launched: Mojar.ai \- Turn your PDFs, docs & knowledge base into an AI support assistant, accessed April 28, 2026, [https://www.reddit.com/r/SaaS/comments/1oubrjo/launched\_mojarai\_turn\_your\_pdfs\_docs\_knowledge/](https://www.reddit.com/r/SaaS/comments/1oubrjo/launched_mojarai_turn_your_pdfs_docs_knowledge/)  
+25. What Are the Biggest HIPAA Compliance Risks in Retargeting and Digital Marketing for Healthcare Organizations? : r/Feroot \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/Feroot/comments/1lrf0q6/what\_are\_the\_biggest\_hipaa\_compliance\_risks\_in/](https://www.reddit.com/r/Feroot/comments/1lrf0q6/what_are_the_biggest_hipaa_compliance_risks_in/)  
+26. r/ReferralMD \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/ReferralMD/](https://www.reddit.com/r/ReferralMD/)  
+27. Lead Workday Integration Engineer @ Salesforce | Simplify Jobs, accessed April 28, 2026, [https://simplify.jobs/p/e4184fdd-05ef-4f36-8201-bbb383497deb/Lead-Workday-Integration-Engineer](https://simplify.jobs/p/e4184fdd-05ef-4f36-8201-bbb383497deb/Lead-Workday-Integration-Engineer)  
+28. Start AI-Assisted Coding with Webix, accessed April 28, 2026, [https://webix.com/ai-coding-with-webix/](https://webix.com/ai-coding-with-webix/)  
+29. agent-governance-toolkit/docs/LIMITATIONS.md at main \- GitHub, accessed April 28, 2026, [https://github.com/microsoft/agent-governance-toolkit/blob/main/docs/LIMITATIONS.md](https://github.com/microsoft/agent-governance-toolkit/blob/main/docs/LIMITATIONS.md)  
+30. Prompt Engineering Best Practices: Tutorial & Examples | LaunchDarkly, accessed April 28, 2026, [https://launchdarkly.com/blog/prompt-engineering-best-practices/](https://launchdarkly.com/blog/prompt-engineering-best-practices/)  
+31. Healthcare startup looking for guidance on HIPAA compliance path : r/cybersecurity \- Reddit, accessed April 28, 2026, [https://www.reddit.com/r/cybersecurity/comments/1mf9h2y/healthcare\_startup\_looking\_for\_guidance\_on\_hipaa/](https://www.reddit.com/r/cybersecurity/comments/1mf9h2y/healthcare_startup_looking_for_guidance_on_hipaa/)
+
+
+
+
+
+
+
+Build with gemini deep research: https://gemini.google.com/share/b36b09653590

README.md

@@ -0,0 +1,67 @@
+---
+license: mit
+language:
+- en
+tags:
+- hipaa
+- healthcare
+- compliance
+- legal
+- rag
+- regulations
+pretty_name: HIPAA Knowledge Base
+size_categories:
+- n<1K
+---
+
+# HIPAA Knowledge Base
+
+A curated knowledge base of HIPAA (Health Insurance Portability and Accountability Act) regulations, guidance, and real-world Q&A, intended for building HIPAA-aware AI agents and RAG systems.
+
+Maintained by [Mojar AI](https://mojar.ai).
+
+## Contents
+
+### `datasets/` — Reference & regulatory material
+Long-form markdown documents covering the HIPAA regulatory landscape:
+
+- Privacy, Security, and Breach Notification Rules
+- PHI definitions, identifiers, and de-identification
+- Business associates, covered entities, minimum necessary standard
+- Patient rights, consent vs. authorization
+- Technical safeguards (engineering perspective)
+- Cloud computing, digital marketing/tracking risks
+- HITECH Act, enforcement & penalties
+- Verbatim 45 CFR Parts 160, 162, 164
+- HHS official guidance and FAQ pages (verbatim)
+- OCR resolution agreements index
+- Real-world compliance pitfalls
+- RAG system architecture notes
+- Q&A compilation
+
+### `datasets-real-life/` — Role-based Q&A
+Practitioner-oriented HIPAA Q&A grouped by role:
+
+- Doctors
+- Nurses
+- Admin / front-desk
+- Billing & insurance
+- Compliance / privacy officers
+
+Plus a 200-question role-based summary and authoring guide.
+
+### `tmp/`
+Raw source material (e.g. CFR Title 45 XML) used to build the curated documents.
+
+### `Building a HIPAA AI Agent.md`
+Design notes on assembling a HIPAA-aware AI agent on top of this corpus.
+
+## Format
+
+All documents are plain Markdown (`.md`), suitable for direct ingestion into RAG pipelines. The verbatim CFR / HHS files preserve original wording for citation fidelity; curated explainers are written in plain English.
+
+## License & disclaimer
+
+Released under the MIT license. U.S. federal regulations and HHS guidance are public-domain works of the U.S. Government; the curated commentary and Q&A are licensed under MIT.
+
+This dataset is provided **for informational and research purposes only** and does **not** constitute legal advice. Consult qualified counsel and your organization's privacy/security officer for compliance decisions.

datasets-real-life/01-doctors-qa.md

@@ -0,0 +1,123 @@
+# HIPAA Q&A Dataset - Doctors
+
+This file contains 40 practical HIPAA questions and answers for Doctors.
+
+1. Q: As a doctor, can I email a patient their lab result if they ask for email delivery?
+   A: Yes, if policy permits and identity is verified. Use approved secure transmission, limit content to minimum necessary, and follow communication preferences. Refs: 45 CFR 164.502(a), 164.312(e)(1), 164.514(d), 164.522(b).
+
+2. Q: As a doctor, can I text appointment reminders that include diagnosis details?
+   A: Appointment reminders are usually permitted, but avoid unnecessary diagnosis details. Keep message content minimal and use approved secure tools. Refs: 45 CFR 164.506, 164.514(d), 164.530(c).
+
+3. Q: As a doctor, if a patient sends PHI by personal SMS, can I reply with clinical advice on the same app?
+   A: Move the conversation to an approved secure channel quickly. Do not continue sharing detailed PHI on consumer messaging apps. Refs: 45 CFR 164.502(a), 164.530(c), 164.312(e)(1).
+
+4. Q: As a doctor, can I leave a detailed voicemail with test results?
+   A: Use limited information, verify contact details, and honor patient communication requests. Avoid unnecessary PHI in voicemail. Refs: 45 CFR 164.514(d), 164.522(b), 164.530(c).
+
+5. Q: As a doctor, can I discuss a patient's status with a caller who says they are the spouse?
+   A: Verify identity and apply professional judgment based on patient involvement, preferences, and restrictions before disclosure. Refs: 45 CFR 164.510(b), 164.502(g), 164.522(a).
+
+6. Q: As a doctor, can I give an employer a patient's diagnosis for a return-to-work request?
+   A: Usually no without valid authorization unless disclosure is required by law. Refs: 45 CFR 164.508, 164.512(a).
+
+7. Q: As a doctor, can I release records to police without a warrant or subpoena?
+   A: Only under specific HIPAA law-enforcement exceptions. Route uncertain requests to privacy or legal review. Refs: 45 CFR 164.512(f), 164.502(a).
+
+8. Q: As a doctor, can I share a teenager's visit details with a parent in every case?
+   A: Not always. Minor consent rules and state law may limit parent access in specific services. Refs: 45 CFR 164.502(g)(3).
+
+9. Q: As a doctor, can we repost a patient's public testimonial on social media?
+   A: Not without valid HIPAA authorization covering that use. Refs: 45 CFR 164.508(a), 164.508(c).
+
+10. Q: As a doctor, can we use patient photos in marketing materials?
+    A: Only with a valid authorization that specifically permits marketing use of PHI. Refs: 45 CFR 164.508(a)(3), 164.501 marketing.
+
+11. Q: As a doctor, can a messaging vendor access PHI before a business associate agreement is signed?
+    A: No. Execute a compliant BAA before vendor PHI access. Refs: 45 CFR 164.502(e), 164.504(e), 164.308(b).
+
+12. Q: As a doctor, can an AI transcription vendor process visit audio containing PHI?
+    A: Only when vendor terms are HIPAA-compliant, safeguards are in place, and use is limited to permitted purposes. Refs: 45 CFR 164.502(e), 164.314(a), 164.306.
+
+13. Q: As a doctor, can I open a chart of a friend or celebrity out of curiosity?
+    A: No. Access must be job-related for treatment, payment, or operations. Refs: 45 CFR 164.502(a), 164.308(a)(4), 164.312(b).
+
+14. Q: As a doctor, can I send a full chart to a consulting specialist for treatment?
+    A: Treatment disclosures are generally permitted, but send only relevant information through secure channels. Refs: 45 CFR 164.506(c), 164.312(e)(1).
+
+15. Q: As a doctor, can I discuss PHI in hallways or elevators if I do not say the patient's name?
+    A: No. Incidental disclosure risk remains. Move discussions to private settings and use safeguards. Refs: 45 CFR 164.530(c), 164.502(a)(1)(iii).
+
+16. Q: As a doctor, does a patient have a right to an electronic copy of records?
+    A: Yes, in requested form and format when readily producible. Refs: 45 CFR 164.524(c).
+
+17. Q: As a doctor, what do we do when a patient requests an amendment to their record?
+    A: Follow HIPAA amendment workflow, evaluate request, and document acceptance or denial. Refs: 45 CFR 164.526.
+
+18. Q: As a doctor, what do we do when a patient requests an accounting of disclosures?
+    A: Provide accounting as required, considering HIPAA scope and exceptions. Refs: 45 CFR 164.528.
+
+19. Q: As a doctor, can a patient restrict disclosure to their health plan after paying out of pocket?
+    A: Yes, for qualifying payment/operations disclosures when the item is paid in full out of pocket. Refs: 45 CFR 164.522(a)(1)(vi).
+
+20. Q: As a doctor, can a patient require us to use a different mailing address or phone number?
+    A: Yes, accommodate reasonable confidential communication requests. Refs: 45 CFR 164.522(b).
+
+21. Q: As a doctor, what should we do after sending PHI to the wrong email recipient?
+    A: Contain, document, risk-assess, and notify as required. Refs: 45 CFR 164.402, 164.404, 164.410, 164.414.
+
+22. Q: As a doctor, what are obligations when a breach affects more than 500 people?
+    A: Notify affected individuals without unreasonable delay and no later than 60 days, plus HHS and media notice when required. Refs: 45 CFR 164.404, 164.406, 164.408(b).
+
+23. Q: As a doctor, what are obligations when a breach affects fewer than 500 people?
+    A: Notify individuals when required, maintain breach documentation, and report to HHS per annual process. Refs: 45 CFR 164.404, 164.408(c), 164.414.
+
+24. Q: As a doctor, what must a business associate do after discovering a breach?
+    A: Notify the covered entity without unreasonable delay and provide known details. Refs: 45 CFR 164.410.
+
+25. Q: As a doctor, what do we do if an unencrypted laptop with PHI is lost or stolen?
+    A: Treat as security incident, investigate compromise risk, and apply breach notification duties if triggered. Refs: 45 CFR 164.308(a)(6), 164.310(d), 164.312(a)(2)(iv), 164.402.
+
+26. Q: As a doctor, can staff share usernames or passwords to speed up work?
+    A: No. Credentials must remain unique and protected for access control and auditability. Refs: 45 CFR 164.312(a)(2)(i), 164.308(a)(3), 164.312(b).
+
+27. Q: As a doctor, what access steps are required when an employee leaves?
+    A: Promptly terminate or modify access rights and document offboarding actions. Refs: 45 CFR 164.308(a)(3)(ii)(C), 164.308(a)(4).
+
+28. Q: As a doctor, can I use personal email to send claim or care documents containing PHI?
+    A: Use only approved systems with required safeguards unless policy explicitly allows a controlled exception. Refs: 45 CFR 164.312(e)(1), 164.530(c), 164.514(d).
+
+29. Q: As a doctor, can we fax PHI and what safeguards are required?
+    A: Yes with safeguards: verify recipient, limit content, and use cover sheets and workflow checks. Refs: 45 CFR 164.530(c), 164.514(d).
+
+30. Q: As a doctor, can we disclose PHI to a payer for prior authorization or claims payment?
+    A: Yes, payment disclosures are generally permitted with appropriate limits and safeguards. Refs: 45 CFR 164.506(c), 164.501 payment, 164.514(d).
+
+31. Q: As a doctor, can we disclose PHI for research without patient authorization?
+    A: Only when HIPAA pathways are satisfied, such as authorization, waiver, or limited data set requirements. Refs: 45 CFR 164.508, 164.512(i), 164.514(e).
+
+32. Q: As a doctor, can we use de-identified data for analytics and model training?
+    A: Yes, if de-identification meets HIPAA standards and re-identification controls are maintained. Refs: 45 CFR 164.502(d), 164.514(a), 164.514(b).
+
+33. Q: As a doctor, can we sell patient data to a marketing company?
+    A: Not without specific HIPAA-compliant authorization for sale of PHI. Refs: 45 CFR 164.502(a)(5)(ii), 164.508(a)(4).
+
+34. Q: As a doctor, can we share PHI with an interpreter during care coordination?
+    A: Yes, when needed for treatment communication and with reasonable safeguards. Refs: 45 CFR 164.506, 164.530(c).
+
+35. Q: As a doctor, can we send referral information to another treating provider without authorization?
+    A: Yes, treatment disclosures are generally permitted. Refs: 45 CFR 164.506(c).
+
+36. Q: As a doctor, when a patient is unconscious, can we share information with family involved in care?
+    A: Use professional judgment to share relevant information in the patient's best interest. Refs: 45 CFR 164.510(b)(3).
+
+37. Q: As a doctor, how should we respond to subpoenas and court orders for PHI?
+    A: Disclose only as HIPAA and the legal process allow, with documentation and minimum necessary controls. Refs: 45 CFR 164.512(e), 164.514(d).
+
+38. Q: As a doctor, what are compliant disposal requirements for paper and electronic PHI?
+    A: Dispose securely so PHI cannot be reconstructed, and enforce media disposal controls. Refs: 45 CFR 164.530(c), 164.310(d)(2)(i).
+
+39. Q: As a doctor, what are first-response steps after a ransomware incident?
+    A: Activate incident response, contain impact, preserve evidence, assess compromise risk, and handle notification obligations. Refs: 45 CFR 164.308(a)(6), 164.402, 164.404, 164.410.
+
+40. Q: As a doctor, how long must HIPAA policies and compliance documentation be retained?
+    A: Retain required documentation for at least six years from creation or last effective date, whichever is later. Refs: 45 CFR 164.316(b)(2)(i), 164.530(j).

datasets-real-life/02-nurses-qa.md

@@ -0,0 +1,123 @@
+# HIPAA Q&A Dataset - Nurses
+
+This file contains 40 practical HIPAA questions and answers for Nurses.
+
+1. Q: As a nurse, can I email a patient their lab result if they ask for email delivery?
+   A: Yes, if policy permits and identity is verified. Use approved secure transmission, limit content to minimum necessary, and follow communication preferences. Refs: 45 CFR 164.502(a), 164.312(e)(1), 164.514(d), 164.522(b).
+
+2. Q: As a nurse, can I text appointment reminders that include diagnosis details?
+   A: Appointment reminders are usually permitted, but avoid unnecessary diagnosis details. Keep message content minimal and use approved secure tools. Refs: 45 CFR 164.506, 164.514(d), 164.530(c).
+
+3. Q: As a nurse, if a patient sends PHI by personal SMS, can I reply with clinical advice on the same app?
+   A: Move the conversation to an approved secure channel quickly. Do not continue sharing detailed PHI on consumer messaging apps. Refs: 45 CFR 164.502(a), 164.530(c), 164.312(e)(1).
+
+4. Q: As a nurse, can I leave a detailed voicemail with test results?
+   A: Use limited information, verify contact details, and honor patient communication requests. Avoid unnecessary PHI in voicemail. Refs: 45 CFR 164.514(d), 164.522(b), 164.530(c).
+
+5. Q: As a nurse, can I discuss a patient's status with a caller who says they are the spouse?
+   A: Verify identity and apply professional judgment based on patient involvement, preferences, and restrictions before disclosure. Refs: 45 CFR 164.510(b), 164.502(g), 164.522(a).
+
+6. Q: As a nurse, can I give an employer a patient's diagnosis for a return-to-work request?
+   A: Usually no without valid authorization unless disclosure is required by law. Refs: 45 CFR 164.508, 164.512(a).
+
+7. Q: As a nurse, can I release records to police without a warrant or subpoena?
+   A: Only under specific HIPAA law-enforcement exceptions. Route uncertain requests to privacy or legal review. Refs: 45 CFR 164.512(f), 164.502(a).
+
+8. Q: As a nurse, can I share a teenager's visit details with a parent in every case?
+   A: Not always. Minor consent rules and state law may limit parent access in specific services. Refs: 45 CFR 164.502(g)(3).
+
+9. Q: As a nurse, can we repost a patient's public testimonial on social media?
+   A: Not without valid HIPAA authorization covering that use. Refs: 45 CFR 164.508(a), 164.508(c).
+
+10. Q: As a nurse, can we use patient photos in marketing materials?
+    A: Only with a valid authorization that specifically permits marketing use of PHI. Refs: 45 CFR 164.508(a)(3), 164.501 marketing.
+
+11. Q: As a nurse, can a messaging vendor access PHI before a business associate agreement is signed?
+    A: No. Execute a compliant BAA before vendor PHI access. Refs: 45 CFR 164.502(e), 164.504(e), 164.308(b).
+
+12. Q: As a nurse, can an AI transcription vendor process visit audio containing PHI?
+    A: Only when vendor terms are HIPAA-compliant, safeguards are in place, and use is limited to permitted purposes. Refs: 45 CFR 164.502(e), 164.314(a), 164.306.
+
+13. Q: As a nurse, can I open a chart of a friend or celebrity out of curiosity?
+    A: No. Access must be job-related for treatment, payment, or operations. Refs: 45 CFR 164.502(a), 164.308(a)(4), 164.312(b).
+
+14. Q: As a nurse, can I send a full chart to a consulting specialist for treatment?
+    A: Treatment disclosures are generally permitted, but send only relevant information through secure channels. Refs: 45 CFR 164.506(c), 164.312(e)(1).
+
+15. Q: As a nurse, can I discuss PHI in hallways or elevators if I do not say the patient's name?
+    A: No. Incidental disclosure risk remains. Move discussions to private settings and use safeguards. Refs: 45 CFR 164.530(c), 164.502(a)(1)(iii).
+
+16. Q: As a nurse, does a patient have a right to an electronic copy of records?
+    A: Yes, in requested form and format when readily producible. Refs: 45 CFR 164.524(c).
+
+17. Q: As a nurse, what do we do when a patient requests an amendment to their record?
+    A: Follow HIPAA amendment workflow, evaluate request, and document acceptance or denial. Refs: 45 CFR 164.526.
+
+18. Q: As a nurse, what do we do when a patient requests an accounting of disclosures?
+    A: Provide accounting as required, considering HIPAA scope and exceptions. Refs: 45 CFR 164.528.
+
+19. Q: As a nurse, can a patient restrict disclosure to their health plan after paying out of pocket?
+    A: Yes, for qualifying payment/operations disclosures when the item is paid in full out of pocket. Refs: 45 CFR 164.522(a)(1)(vi).
+
+20. Q: As a nurse, can a patient require us to use a different mailing address or phone number?
+    A: Yes, accommodate reasonable confidential communication requests. Refs: 45 CFR 164.522(b).
+
+21. Q: As a nurse, what should we do after sending PHI to the wrong email recipient?
+    A: Contain, document, risk-assess, and notify as required. Refs: 45 CFR 164.402, 164.404, 164.410, 164.414.
+
+22. Q: As a nurse, what are obligations when a breach affects more than 500 people?
+    A: Notify affected individuals without unreasonable delay and no later than 60 days, plus HHS and media notice when required. Refs: 45 CFR 164.404, 164.406, 164.408(b).
+
+23. Q: As a nurse, what are obligations when a breach affects fewer than 500 people?
+    A: Notify individuals when required, maintain breach documentation, and report to HHS per annual process. Refs: 45 CFR 164.404, 164.408(c), 164.414.
+
+24. Q: As a nurse, what must a business associate do after discovering a breach?
+    A: Notify the covered entity without unreasonable delay and provide known details. Refs: 45 CFR 164.410.
+
+25. Q: As a nurse, what do we do if an unencrypted laptop with PHI is lost or stolen?
+    A: Treat as security incident, investigate compromise risk, and apply breach notification duties if triggered. Refs: 45 CFR 164.308(a)(6), 164.310(d), 164.312(a)(2)(iv), 164.402.
+
+26. Q: As a nurse, can staff share usernames or passwords to speed up work?
+    A: No. Credentials must remain unique and protected for access control and auditability. Refs: 45 CFR 164.312(a)(2)(i), 164.308(a)(3), 164.312(b).
+
+27. Q: As a nurse, what access steps are required when an employee leaves?
+    A: Promptly terminate or modify access rights and document offboarding actions. Refs: 45 CFR 164.308(a)(3)(ii)(C), 164.308(a)(4).
+
+28. Q: As a nurse, can I use personal email to send claim or care documents containing PHI?
+    A: Use only approved systems with required safeguards unless policy explicitly allows a controlled exception. Refs: 45 CFR 164.312(e)(1), 164.530(c), 164.514(d).
+
+29. Q: As a nurse, can we fax PHI and what safeguards are required?
+    A: Yes with safeguards: verify recipient, limit content, and use cover sheets and workflow checks. Refs: 45 CFR 164.530(c), 164.514(d).
+
+30. Q: As a nurse, can we disclose PHI to a payer for prior authorization or claims payment?
+    A: Yes, payment disclosures are generally permitted with appropriate limits and safeguards. Refs: 45 CFR 164.506(c), 164.501 payment, 164.514(d).
+
+31. Q: As a nurse, can we disclose PHI for research without patient authorization?
+    A: Only when HIPAA pathways are satisfied, such as authorization, waiver, or limited data set requirements. Refs: 45 CFR 164.508, 164.512(i), 164.514(e).
+
+32. Q: As a nurse, can we use de-identified data for analytics and model training?
+    A: Yes, if de-identification meets HIPAA standards and re-identification controls are maintained. Refs: 45 CFR 164.502(d), 164.514(a), 164.514(b).
+
+33. Q: As a nurse, can we sell patient data to a marketing company?
+    A: Not without specific HIPAA-compliant authorization for sale of PHI. Refs: 45 CFR 164.502(a)(5)(ii), 164.508(a)(4).
+
+34. Q: As a nurse, can we share PHI with an interpreter during care coordination?
+    A: Yes, when needed for treatment communication and with reasonable safeguards. Refs: 45 CFR 164.506, 164.530(c).
+
+35. Q: As a nurse, can we send referral information to another treating provider without authorization?
+    A: Yes, treatment disclosures are generally permitted. Refs: 45 CFR 164.506(c).
+
+36. Q: As a nurse, when a patient is unconscious, can we share information with family involved in care?
+    A: Use professional judgment to share relevant information in the patient's best interest. Refs: 45 CFR 164.510(b)(3).
+
+37. Q: As a nurse, how should we respond to subpoenas and court orders for PHI?
+    A: Disclose only as HIPAA and the legal process allow, with documentation and minimum necessary controls. Refs: 45 CFR 164.512(e), 164.514(d).
+
+38. Q: As a nurse, what are compliant disposal requirements for paper and electronic PHI?
+    A: Dispose securely so PHI cannot be reconstructed, and enforce media disposal controls. Refs: 45 CFR 164.530(c), 164.310(d)(2)(i).
+
+39. Q: As a nurse, what are first-response steps after a ransomware incident?
+    A: Activate incident response, contain impact, preserve evidence, assess compromise risk, and handle notification obligations. Refs: 45 CFR 164.308(a)(6), 164.402, 164.404, 164.410.
+
+40. Q: As a nurse, how long must HIPAA policies and compliance documentation be retained?
+    A: Retain required documentation for at least six years from creation or last effective date, whichever is later. Refs: 45 CFR 164.316(b)(2)(i), 164.530(j).

datasets-real-life/03-admin-frontdesk-qa.md

@@ -0,0 +1,123 @@
+# HIPAA Q&A Dataset - Admin and Front Desk
+
+This file contains 40 practical HIPAA questions and answers for Admin and Front Desk.
+
+1. Q: As front-desk staff, can I email a patient their lab result if they ask for email delivery?
+   A: Yes, if policy permits and identity is verified. Use approved secure transmission, limit content to minimum necessary, and follow communication preferences. Refs: 45 CFR 164.502(a), 164.312(e)(1), 164.514(d), 164.522(b).
+
+2. Q: As front-desk staff, can I text appointment reminders that include diagnosis details?
+   A: Appointment reminders are usually permitted, but avoid unnecessary diagnosis details. Keep message content minimal and use approved secure tools. Refs: 45 CFR 164.506, 164.514(d), 164.530(c).
+
+3. Q: As front-desk staff, if a patient sends PHI by personal SMS, can I reply with clinical advice on the same app?
+   A: Move the conversation to an approved secure channel quickly. Do not continue sharing detailed PHI on consumer messaging apps. Refs: 45 CFR 164.502(a), 164.530(c), 164.312(e)(1).
+
+4. Q: As front-desk staff, can I leave a detailed voicemail with test results?
+   A: Use limited information, verify contact details, and honor patient communication requests. Avoid unnecessary PHI in voicemail. Refs: 45 CFR 164.514(d), 164.522(b), 164.530(c).
+
+5. Q: As front-desk staff, can I discuss a patient's status with a caller who says they are the spouse?
+   A: Verify identity and apply professional judgment based on patient involvement, preferences, and restrictions before disclosure. Refs: 45 CFR 164.510(b), 164.502(g), 164.522(a).
+
+6. Q: As front-desk staff, can I give an employer a patient's diagnosis for a return-to-work request?
+   A: Usually no without valid authorization unless disclosure is required by law. Refs: 45 CFR 164.508, 164.512(a).
+
+7. Q: As front-desk staff, can I release records to police without a warrant or subpoena?
+   A: Only under specific HIPAA law-enforcement exceptions. Route uncertain requests to privacy or legal review. Refs: 45 CFR 164.512(f), 164.502(a).
+
+8. Q: As front-desk staff, can I share a teenager's visit details with a parent in every case?
+   A: Not always. Minor consent rules and state law may limit parent access in specific services. Refs: 45 CFR 164.502(g)(3).
+
+9. Q: As front-desk staff, can we repost a patient's public testimonial on social media?
+   A: Not without valid HIPAA authorization covering that use. Refs: 45 CFR 164.508(a), 164.508(c).
+
+10. Q: As front-desk staff, can we use patient photos in marketing materials?
+    A: Only with a valid authorization that specifically permits marketing use of PHI. Refs: 45 CFR 164.508(a)(3), 164.501 marketing.
+
+11. Q: As front-desk staff, can a messaging vendor access PHI before a business associate agreement is signed?
+    A: No. Execute a compliant BAA before vendor PHI access. Refs: 45 CFR 164.502(e), 164.504(e), 164.308(b).
+
+12. Q: As front-desk staff, can an AI transcription vendor process visit audio containing PHI?
+    A: Only when vendor terms are HIPAA-compliant, safeguards are in place, and use is limited to permitted purposes. Refs: 45 CFR 164.502(e), 164.314(a), 164.306.
+
+13. Q: As front-desk staff, can I open a chart of a friend or celebrity out of curiosity?
+    A: No. Access must be job-related for treatment, payment, or operations. Refs: 45 CFR 164.502(a), 164.308(a)(4), 164.312(b).
+
+14. Q: As front-desk staff, can I send a full chart to a consulting specialist for treatment?
+    A: Treatment disclosures are generally permitted, but send only relevant information through secure channels. Refs: 45 CFR 164.506(c), 164.312(e)(1).
+
+15. Q: As front-desk staff, can I discuss PHI in hallways or elevators if I do not say the patient's name?
+    A: No. Incidental disclosure risk remains. Move discussions to private settings and use safeguards. Refs: 45 CFR 164.530(c), 164.502(a)(1)(iii).
+
+16. Q: As front-desk staff, does a patient have a right to an electronic copy of records?
+    A: Yes, in requested form and format when readily producible. Refs: 45 CFR 164.524(c).
+
+17. Q: As front-desk staff, what do we do when a patient requests an amendment to their record?
+    A: Follow HIPAA amendment workflow, evaluate request, and document acceptance or denial. Refs: 45 CFR 164.526.
+
+18. Q: As front-desk staff, what do we do when a patient requests an accounting of disclosures?
+    A: Provide accounting as required, considering HIPAA scope and exceptions. Refs: 45 CFR 164.528.
+
+19. Q: As front-desk staff, can a patient restrict disclosure to their health plan after paying out of pocket?
+    A: Yes, for qualifying payment/operations disclosures when the item is paid in full out of pocket. Refs: 45 CFR 164.522(a)(1)(vi).
+
+20. Q: As front-desk staff, can a patient require us to use a different mailing address or phone number?
+    A: Yes, accommodate reasonable confidential communication requests. Refs: 45 CFR 164.522(b).
+
+21. Q: As front-desk staff, what should we do after sending PHI to the wrong email recipient?
+    A: Contain, document, risk-assess, and notify as required. Refs: 45 CFR 164.402, 164.404, 164.410, 164.414.
+
+22. Q: As front-desk staff, what are obligations when a breach affects more than 500 people?
+    A: Notify affected individuals without unreasonable delay and no later than 60 days, plus HHS and media notice when required. Refs: 45 CFR 164.404, 164.406, 164.408(b).
+
+23. Q: As front-desk staff, what are obligations when a breach affects fewer than 500 people?
+    A: Notify individuals when required, maintain breach documentation, and report to HHS per annual process. Refs: 45 CFR 164.404, 164.408(c), 164.414.
+
+24. Q: As front-desk staff, what must a business associate do after discovering a breach?
+    A: Notify the covered entity without unreasonable delay and provide known details. Refs: 45 CFR 164.410.
+
+25. Q: As front-desk staff, what do we do if an unencrypted laptop with PHI is lost or stolen?
+    A: Treat as security incident, investigate compromise risk, and apply breach notification duties if triggered. Refs: 45 CFR 164.308(a)(6), 164.310(d), 164.312(a)(2)(iv), 164.402.
+
+26. Q: As front-desk staff, can staff share usernames or passwords to speed up work?
+    A: No. Credentials must remain unique and protected for access control and auditability. Refs: 45 CFR 164.312(a)(2)(i), 164.308(a)(3), 164.312(b).
+
+27. Q: As front-desk staff, what access steps are required when an employee leaves?
+    A: Promptly terminate or modify access rights and document offboarding actions. Refs: 45 CFR 164.308(a)(3)(ii)(C), 164.308(a)(4).
+
+28. Q: As front-desk staff, can I use personal email to send claim or care documents containing PHI?
+    A: Use only approved systems with required safeguards unless policy explicitly allows a controlled exception. Refs: 45 CFR 164.312(e)(1), 164.530(c), 164.514(d).
+
+29. Q: As front-desk staff, can we fax PHI and what safeguards are required?
+    A: Yes with safeguards: verify recipient, limit content, and use cover sheets and workflow checks. Refs: 45 CFR 164.530(c), 164.514(d).
+
+30. Q: As front-desk staff, can we disclose PHI to a payer for prior authorization or claims payment?
+    A: Yes, payment disclosures are generally permitted with appropriate limits and safeguards. Refs: 45 CFR 164.506(c), 164.501 payment, 164.514(d).
+
+31. Q: As front-desk staff, can we disclose PHI for research without patient authorization?
+    A: Only when HIPAA pathways are satisfied, such as authorization, waiver, or limited data set requirements. Refs: 45 CFR 164.508, 164.512(i), 164.514(e).
+
+32. Q: As front-desk staff, can we use de-identified data for analytics and model training?
+    A: Yes, if de-identification meets HIPAA standards and re-identification controls are maintained. Refs: 45 CFR 164.502(d), 164.514(a), 164.514(b).
+
+33. Q: As front-desk staff, can we sell patient data to a marketing company?
+    A: Not without specific HIPAA-compliant authorization for sale of PHI. Refs: 45 CFR 164.502(a)(5)(ii), 164.508(a)(4).
+
+34. Q: As front-desk staff, can we share PHI with an interpreter during care coordination?
+    A: Yes, when needed for treatment communication and with reasonable safeguards. Refs: 45 CFR 164.506, 164.530(c).
+
+35. Q: As front-desk staff, can we send referral information to another treating provider without authorization?
+    A: Yes, treatment disclosures are generally permitted. Refs: 45 CFR 164.506(c).
+
+36. Q: As front-desk staff, when a patient is unconscious, can we share information with family involved in care?
+    A: Use professional judgment to share relevant information in the patient's best interest. Refs: 45 CFR 164.510(b)(3).
+
+37. Q: As front-desk staff, how should we respond to subpoenas and court orders for PHI?
+    A: Disclose only as HIPAA and the legal process allow, with documentation and minimum necessary controls. Refs: 45 CFR 164.512(e), 164.514(d).
+
+38. Q: As front-desk staff, what are compliant disposal requirements for paper and electronic PHI?
+    A: Dispose securely so PHI cannot be reconstructed, and enforce media disposal controls. Refs: 45 CFR 164.530(c), 164.310(d)(2)(i).
+
+39. Q: As front-desk staff, what are first-response steps after a ransomware incident?
+    A: Activate incident response, contain impact, preserve evidence, assess compromise risk, and handle notification obligations. Refs: 45 CFR 164.308(a)(6), 164.402, 164.404, 164.410.
+
+40. Q: As front-desk staff, how long must HIPAA policies and compliance documentation be retained?
+    A: Retain required documentation for at least six years from creation or last effective date, whichever is later. Refs: 45 CFR 164.316(b)(2)(i), 164.530(j).

datasets-real-life/04-billing-insurance-qa.md

@@ -0,0 +1,123 @@
+# HIPAA Q&A Dataset - Billing and Insurance
+
+This file contains 40 practical HIPAA questions and answers for Billing and Insurance.
+
+1. Q: As billing or insurance staff, can I email a patient their lab result if they ask for email delivery?
+   A: Yes, if policy permits and identity is verified. Use approved secure transmission, limit content to minimum necessary, and follow communication preferences. Refs: 45 CFR 164.502(a), 164.312(e)(1), 164.514(d), 164.522(b).
+
+2. Q: As billing or insurance staff, can I text appointment reminders that include diagnosis details?
+   A: Appointment reminders are usually permitted, but avoid unnecessary diagnosis details. Keep message content minimal and use approved secure tools. Refs: 45 CFR 164.506, 164.514(d), 164.530(c).
+
+3. Q: As billing or insurance staff, if a patient sends PHI by personal SMS, can I reply with clinical advice on the same app?
+   A: Move the conversation to an approved secure channel quickly. Do not continue sharing detailed PHI on consumer messaging apps. Refs: 45 CFR 164.502(a), 164.530(c), 164.312(e)(1).
+
+4. Q: As billing or insurance staff, can I leave a detailed voicemail with test results?
+   A: Use limited information, verify contact details, and honor patient communication requests. Avoid unnecessary PHI in voicemail. Refs: 45 CFR 164.514(d), 164.522(b), 164.530(c).
+
+5. Q: As billing or insurance staff, can I discuss a patient's status with a caller who says they are the spouse?
+   A: Verify identity and apply professional judgment based on patient involvement, preferences, and restrictions before disclosure. Refs: 45 CFR 164.510(b), 164.502(g), 164.522(a).
+
+6. Q: As billing or insurance staff, can I give an employer a patient's diagnosis for a return-to-work request?
+   A: Usually no without valid authorization unless disclosure is required by law. Refs: 45 CFR 164.508, 164.512(a).
+
+7. Q: As billing or insurance staff, can I release records to police without a warrant or subpoena?
+   A: Only under specific HIPAA law-enforcement exceptions. Route uncertain requests to privacy or legal review. Refs: 45 CFR 164.512(f), 164.502(a).
+
+8. Q: As billing or insurance staff, can I share a teenager's visit details with a parent in every case?
+   A: Not always. Minor consent rules and state law may limit parent access in specific services. Refs: 45 CFR 164.502(g)(3).
+
+9. Q: As billing or insurance staff, can we repost a patient's public testimonial on social media?
+   A: Not without valid HIPAA authorization covering that use. Refs: 45 CFR 164.508(a), 164.508(c).
+
+10. Q: As billing or insurance staff, can we use patient photos in marketing materials?
+    A: Only with a valid authorization that specifically permits marketing use of PHI. Refs: 45 CFR 164.508(a)(3), 164.501 marketing.
+
+11. Q: As billing or insurance staff, can a messaging vendor access PHI before a business associate agreement is signed?
+    A: No. Execute a compliant BAA before vendor PHI access. Refs: 45 CFR 164.502(e), 164.504(e), 164.308(b).
+
+12. Q: As billing or insurance staff, can an AI transcription vendor process visit audio containing PHI?
+    A: Only when vendor terms are HIPAA-compliant, safeguards are in place, and use is limited to permitted purposes. Refs: 45 CFR 164.502(e), 164.314(a), 164.306.
+
+13. Q: As billing or insurance staff, can I open a chart of a friend or celebrity out of curiosity?
+    A: No. Access must be job-related for treatment, payment, or operations. Refs: 45 CFR 164.502(a), 164.308(a)(4), 164.312(b).
+
+14. Q: As billing or insurance staff, can I send a full chart to a consulting specialist for treatment?
+    A: Treatment disclosures are generally permitted, but send only relevant information through secure channels. Refs: 45 CFR 164.506(c), 164.312(e)(1).
+
+15. Q: As billing or insurance staff, can I discuss PHI in hallways or elevators if I do not say the patient's name?
+    A: No. Incidental disclosure risk remains. Move discussions to private settings and use safeguards. Refs: 45 CFR 164.530(c), 164.502(a)(1)(iii).
+
+16. Q: As billing or insurance staff, does a patient have a right to an electronic copy of records?
+    A: Yes, in requested form and format when readily producible. Refs: 45 CFR 164.524(c).
+
+17. Q: As billing or insurance staff, what do we do when a patient requests an amendment to their record?
+    A: Follow HIPAA amendment workflow, evaluate request, and document acceptance or denial. Refs: 45 CFR 164.526.
+
+18. Q: As billing or insurance staff, what do we do when a patient requests an accounting of disclosures?
+    A: Provide accounting as required, considering HIPAA scope and exceptions. Refs: 45 CFR 164.528.
+
+19. Q: As billing or insurance staff, can a patient restrict disclosure to their health plan after paying out of pocket?
+    A: Yes, for qualifying payment/operations disclosures when the item is paid in full out of pocket. Refs: 45 CFR 164.522(a)(1)(vi).
+
+20. Q: As billing or insurance staff, can a patient require us to use a different mailing address or phone number?
+    A: Yes, accommodate reasonable confidential communication requests. Refs: 45 CFR 164.522(b).
+
+21. Q: As billing or insurance staff, what should we do after sending PHI to the wrong email recipient?
+    A: Contain, document, risk-assess, and notify as required. Refs: 45 CFR 164.402, 164.404, 164.410, 164.414.
+
+22. Q: As billing or insurance staff, what are obligations when a breach affects more than 500 people?
+    A: Notify affected individuals without unreasonable delay and no later than 60 days, plus HHS and media notice when required. Refs: 45 CFR 164.404, 164.406, 164.408(b).
+
+23. Q: As billing or insurance staff, what are obligations when a breach affects fewer than 500 people?
+    A: Notify individuals when required, maintain breach documentation, and report to HHS per annual process. Refs: 45 CFR 164.404, 164.408(c), 164.414.
+
+24. Q: As billing or insurance staff, what must a business associate do after discovering a breach?
+    A: Notify the covered entity without unreasonable delay and provide known details. Refs: 45 CFR 164.410.
+
+25. Q: As billing or insurance staff, what do we do if an unencrypted laptop with PHI is lost or stolen?
+    A: Treat as security incident, investigate compromise risk, and apply breach notification duties if triggered. Refs: 45 CFR 164.308(a)(6), 164.310(d), 164.312(a)(2)(iv), 164.402.
+
+26. Q: As billing or insurance staff, can staff share usernames or passwords to speed up work?
+    A: No. Credentials must remain unique and protected for access control and auditability. Refs: 45 CFR 164.312(a)(2)(i), 164.308(a)(3), 164.312(b).
+
+27. Q: As billing or insurance staff, what access steps are required when an employee leaves?
+    A: Promptly terminate or modify access rights and document offboarding actions. Refs: 45 CFR 164.308(a)(3)(ii)(C), 164.308(a)(4).
+
+28. Q: As billing or insurance staff, can I use personal email to send claim or care documents containing PHI?
+    A: Use only approved systems with required safeguards unless policy explicitly allows a controlled exception. Refs: 45 CFR 164.312(e)(1), 164.530(c), 164.514(d).
+
+29. Q: As billing or insurance staff, can we fax PHI and what safeguards are required?
+    A: Yes with safeguards: verify recipient, limit content, and use cover sheets and workflow checks. Refs: 45 CFR 164.530(c), 164.514(d).
+
+30. Q: As billing or insurance staff, can we disclose PHI to a payer for prior authorization or claims payment?
+    A: Yes, payment disclosures are generally permitted with appropriate limits and safeguards. Refs: 45 CFR 164.506(c), 164.501 payment, 164.514(d).
+
+31. Q: As billing or insurance staff, can we disclose PHI for research without patient authorization?
+    A: Only when HIPAA pathways are satisfied, such as authorization, waiver, or limited data set requirements. Refs: 45 CFR 164.508, 164.512(i), 164.514(e).
+
+32. Q: As billing or insurance staff, can we use de-identified data for analytics and model training?
+    A: Yes, if de-identification meets HIPAA standards and re-identification controls are maintained. Refs: 45 CFR 164.502(d), 164.514(a), 164.514(b).
+
+33. Q: As billing or insurance staff, can we sell patient data to a marketing company?
+    A: Not without specific HIPAA-compliant authorization for sale of PHI. Refs: 45 CFR 164.502(a)(5)(ii), 164.508(a)(4).
+
+34. Q: As billing or insurance staff, can we share PHI with an interpreter during care coordination?
+    A: Yes, when needed for treatment communication and with reasonable safeguards. Refs: 45 CFR 164.506, 164.530(c).
+
+35. Q: As billing or insurance staff, can we send referral information to another treating provider without authorization?
+    A: Yes, treatment disclosures are generally permitted. Refs: 45 CFR 164.506(c).
+
+36. Q: As billing or insurance staff, when a patient is unconscious, can we share information with family involved in care?
+    A: Use professional judgment to share relevant information in the patient's best interest. Refs: 45 CFR 164.510(b)(3).
+
+37. Q: As billing or insurance staff, how should we respond to subpoenas and court orders for PHI?
+    A: Disclose only as HIPAA and the legal process allow, with documentation and minimum necessary controls. Refs: 45 CFR 164.512(e), 164.514(d).
+
+38. Q: As billing or insurance staff, what are compliant disposal requirements for paper and electronic PHI?
+    A: Dispose securely so PHI cannot be reconstructed, and enforce media disposal controls. Refs: 45 CFR 164.530(c), 164.310(d)(2)(i).
+
+39. Q: As billing or insurance staff, what are first-response steps after a ransomware incident?
+    A: Activate incident response, contain impact, preserve evidence, assess compromise risk, and handle notification obligations. Refs: 45 CFR 164.308(a)(6), 164.402, 164.404, 164.410.
+
+40. Q: As billing or insurance staff, how long must HIPAA policies and compliance documentation be retained?
+    A: Retain required documentation for at least six years from creation or last effective date, whichever is later. Refs: 45 CFR 164.316(b)(2)(i), 164.530(j).

datasets-real-life/05-compliance-privacy-qa.md

@@ -0,0 +1,123 @@
+# HIPAA Q&A Dataset - Compliance and Privacy
+
+This file contains 40 practical HIPAA questions and answers for Compliance and Privacy.
+
+1. Q: As a compliance officer, can I email a patient their lab result if they ask for email delivery?
+   A: Yes, if policy permits and identity is verified. Use approved secure transmission, limit content to minimum necessary, and follow communication preferences. Refs: 45 CFR 164.502(a), 164.312(e)(1), 164.514(d), 164.522(b).
+
+2. Q: As a compliance officer, can I text appointment reminders that include diagnosis details?
+   A: Appointment reminders are usually permitted, but avoid unnecessary diagnosis details. Keep message content minimal and use approved secure tools. Refs: 45 CFR 164.506, 164.514(d), 164.530(c).
+
+3. Q: As a compliance officer, if a patient sends PHI by personal SMS, can I reply with clinical advice on the same app?
+   A: Move the conversation to an approved secure channel quickly. Do not continue sharing detailed PHI on consumer messaging apps. Refs: 45 CFR 164.502(a), 164.530(c), 164.312(e)(1).
+
+4. Q: As a compliance officer, can I leave a detailed voicemail with test results?
+   A: Use limited information, verify contact details, and honor patient communication requests. Avoid unnecessary PHI in voicemail. Refs: 45 CFR 164.514(d), 164.522(b), 164.530(c).
+
+5. Q: As a compliance officer, can I discuss a patient's status with a caller who says they are the spouse?
+   A: Verify identity and apply professional judgment based on patient involvement, preferences, and restrictions before disclosure. Refs: 45 CFR 164.510(b), 164.502(g), 164.522(a).
+
+6. Q: As a compliance officer, can I give an employer a patient's diagnosis for a return-to-work request?
+   A: Usually no without valid authorization unless disclosure is required by law. Refs: 45 CFR 164.508, 164.512(a).
+
+7. Q: As a compliance officer, can I release records to police without a warrant or subpoena?
+   A: Only under specific HIPAA law-enforcement exceptions. Route uncertain requests to privacy or legal review. Refs: 45 CFR 164.512(f), 164.502(a).
+
+8. Q: As a compliance officer, can I share a teenager's visit details with a parent in every case?
+   A: Not always. Minor consent rules and state law may limit parent access in specific services. Refs: 45 CFR 164.502(g)(3).
+
+9. Q: As a compliance officer, can we repost a patient's public testimonial on social media?
+   A: Not without valid HIPAA authorization covering that use. Refs: 45 CFR 164.508(a), 164.508(c).
+
+10. Q: As a compliance officer, can we use patient photos in marketing materials?
+    A: Only with a valid authorization that specifically permits marketing use of PHI. Refs: 45 CFR 164.508(a)(3), 164.501 marketing.
+
+11. Q: As a compliance officer, can a messaging vendor access PHI before a business associate agreement is signed?
+    A: No. Execute a compliant BAA before vendor PHI access. Refs: 45 CFR 164.502(e), 164.504(e), 164.308(b).
+
+12. Q: As a compliance officer, can an AI transcription vendor process visit audio containing PHI?
+    A: Only when vendor terms are HIPAA-compliant, safeguards are in place, and use is limited to permitted purposes. Refs: 45 CFR 164.502(e), 164.314(a), 164.306.
+
+13. Q: As a compliance officer, can I open a chart of a friend or celebrity out of curiosity?
+    A: No. Access must be job-related for treatment, payment, or operations. Refs: 45 CFR 164.502(a), 164.308(a)(4), 164.312(b).
+
+14. Q: As a compliance officer, can I send a full chart to a consulting specialist for treatment?
+    A: Treatment disclosures are generally permitted, but send only relevant information through secure channels. Refs: 45 CFR 164.506(c), 164.312(e)(1).
+
+15. Q: As a compliance officer, can I discuss PHI in hallways or elevators if I do not say the patient's name?
+    A: No. Incidental disclosure risk remains. Move discussions to private settings and use safeguards. Refs: 45 CFR 164.530(c), 164.502(a)(1)(iii).
+
+16. Q: As a compliance officer, does a patient have a right to an electronic copy of records?
+    A: Yes, in requested form and format when readily producible. Refs: 45 CFR 164.524(c).
+
+17. Q: As a compliance officer, what do we do when a patient requests an amendment to their record?
+    A: Follow HIPAA amendment workflow, evaluate request, and document acceptance or denial. Refs: 45 CFR 164.526.
+
+18. Q: As a compliance officer, what do we do when a patient requests an accounting of disclosures?
+    A: Provide accounting as required, considering HIPAA scope and exceptions. Refs: 45 CFR 164.528.
+
+19. Q: As a compliance officer, can a patient restrict disclosure to their health plan after paying out of pocket?
+    A: Yes, for qualifying payment/operations disclosures when the item is paid in full out of pocket. Refs: 45 CFR 164.522(a)(1)(vi).
+
+20. Q: As a compliance officer, can a patient require us to use a different mailing address or phone number?
+    A: Yes, accommodate reasonable confidential communication requests. Refs: 45 CFR 164.522(b).
+
+21. Q: As a compliance officer, what should we do after sending PHI to the wrong email recipient?
+    A: Contain, document, risk-assess, and notify as required. Refs: 45 CFR 164.402, 164.404, 164.410, 164.414.
+
+22. Q: As a compliance officer, what are obligations when a breach affects more than 500 people?
+    A: Notify affected individuals without unreasonable delay and no later than 60 days, plus HHS and media notice when required. Refs: 45 CFR 164.404, 164.406, 164.408(b).
+
+23. Q: As a compliance officer, what are obligations when a breach affects fewer than 500 people?
+    A: Notify individuals when required, maintain breach documentation, and report to HHS per annual process. Refs: 45 CFR 164.404, 164.408(c), 164.414.
+
+24. Q: As a compliance officer, what must a business associate do after discovering a breach?
+    A: Notify the covered entity without unreasonable delay and provide known details. Refs: 45 CFR 164.410.
+
+25. Q: As a compliance officer, what do we do if an unencrypted laptop with PHI is lost or stolen?
+    A: Treat as security incident, investigate compromise risk, and apply breach notification duties if triggered. Refs: 45 CFR 164.308(a)(6), 164.310(d), 164.312(a)(2)(iv), 164.402.
+
+26. Q: As a compliance officer, can staff share usernames or passwords to speed up work?
+    A: No. Credentials must remain unique and protected for access control and auditability. Refs: 45 CFR 164.312(a)(2)(i), 164.308(a)(3), 164.312(b).
+
+27. Q: As a compliance officer, what access steps are required when an employee leaves?
+    A: Promptly terminate or modify access rights and document offboarding actions. Refs: 45 CFR 164.308(a)(3)(ii)(C), 164.308(a)(4).
+
+28. Q: As a compliance officer, can I use personal email to send claim or care documents containing PHI?
+    A: Use only approved systems with required safeguards unless policy explicitly allows a controlled exception. Refs: 45 CFR 164.312(e)(1), 164.530(c), 164.514(d).
+
+29. Q: As a compliance officer, can we fax PHI and what safeguards are required?
+    A: Yes with safeguards: verify recipient, limit content, and use cover sheets and workflow checks. Refs: 45 CFR 164.530(c), 164.514(d).
+
+30. Q: As a compliance officer, can we disclose PHI to a payer for prior authorization or claims payment?
+    A: Yes, payment disclosures are generally permitted with appropriate limits and safeguards. Refs: 45 CFR 164.506(c), 164.501 payment, 164.514(d).
+
+31. Q: As a compliance officer, can we disclose PHI for research without patient authorization?
+    A: Only when HIPAA pathways are satisfied, such as authorization, waiver, or limited data set requirements. Refs: 45 CFR 164.508, 164.512(i), 164.514(e).
+
+32. Q: As a compliance officer, can we use de-identified data for analytics and model training?
+    A: Yes, if de-identification meets HIPAA standards and re-identification controls are maintained. Refs: 45 CFR 164.502(d), 164.514(a), 164.514(b).
+
+33. Q: As a compliance officer, can we sell patient data to a marketing company?
+    A: Not without specific HIPAA-compliant authorization for sale of PHI. Refs: 45 CFR 164.502(a)(5)(ii), 164.508(a)(4).
+
+34. Q: As a compliance officer, can we share PHI with an interpreter during care coordination?
+    A: Yes, when needed for treatment communication and with reasonable safeguards. Refs: 45 CFR 164.506, 164.530(c).
+
+35. Q: As a compliance officer, can we send referral information to another treating provider without authorization?
+    A: Yes, treatment disclosures are generally permitted. Refs: 45 CFR 164.506(c).
+
+36. Q: As a compliance officer, when a patient is unconscious, can we share information with family involved in care?
+    A: Use professional judgment to share relevant information in the patient's best interest. Refs: 45 CFR 164.510(b)(3).
+
+37. Q: As a compliance officer, how should we respond to subpoenas and court orders for PHI?
+    A: Disclose only as HIPAA and the legal process allow, with documentation and minimum necessary controls. Refs: 45 CFR 164.512(e), 164.514(d).
+
+38. Q: As a compliance officer, what are compliant disposal requirements for paper and electronic PHI?
+    A: Dispose securely so PHI cannot be reconstructed, and enforce media disposal controls. Refs: 45 CFR 164.530(c), 164.310(d)(2)(i).
+
+39. Q: As a compliance officer, what are first-response steps after a ransomware incident?
+    A: Activate incident response, contain impact, preserve evidence, assess compromise risk, and handle notification obligations. Refs: 45 CFR 164.308(a)(6), 164.402, 164.404, 164.410.
+
+40. Q: As a compliance officer, how long must HIPAA policies and compliance documentation be retained?
+    A: Retain required documentation for at least six years from creation or last effective date, whichever is later. Refs: 45 CFR 164.316(b)(2)(i), 164.530(j).

datasets-real-life/200-role-based-hipaa-qa-summary.md

@@ -0,0 +1,10 @@
+# HIPAA 200 Q&A Dataset Summary
+
+Generated files:
+- 01-doctors-qa.md: 40 entries
+- 02-nurses-qa.md: 40 entries
+- 03-admin-frontdesk-qa.md: 40 entries
+- 04-billing-insurance-qa.md: 40 entries
+- 05-compliance-privacy-qa.md: 40 entries
+
+Total entries: 200

datasets-real-life/Building HIPAA Question Datasets.md

@@ -0,0 +1,356 @@
+# **Structuring and Securing Clinical Question-Answering Datasets: An Exhaustive Analysis of Patient Inquiries and HIPAA Compliance Frameworks**
+
+## **The Paradigm Shift in Digital Patient-Provider Communications**
+
+The digitalization of the healthcare sector has catalyzed a fundamental restructuring of the communication paradigms that govern patient-provider interactions. Historically, the exchange of medical information, clinical triage, and therapeutic management was strictly confined to synchronous, in-person consultations or structured telephonic encounters. However, propelled by rapid technological advancements, evolving consumer expectations, and systemic pressures to enhance healthcare efficiency, the nexus of patient interaction has decisively migrated toward digital platforms. This digital ecosystem predominantly comprises asynchronous secure messaging through patient portals, synchronous telehealth video conferencing, and remote patient monitoring interfaces.1
+
+The velocity of this transition has been heavily accelerated by global public health crises, notably the COVID-19 pandemic, which forced a temporary cessation of routine in-person care and normalized virtual modalities.4 Furthermore, this migration has been legally and financially incentivized by robust legislative frameworks in the United States, including the American Recovery and Reinvestment Act (ARRA), the Health Information Technology for Economic and Clinical Health (HITECH) Act, and the Medicare Electronic Health Record (EHR) Incentive Program.7 These initiatives collectively established the "Meaningful Use" criteria, compelling healthcare providers to transition from paper records to interoperable electronic medical records and to provide patients with direct electronic access to their health data.7
+
+Because these digital inquiries and electronic exchanges inherently involve the transmission, processing, and storage of highly sensitive personal health information, they are strictly governed by the Health Insurance Portability and Accountability Act (HIPAA) of 1996\.9 HIPAA regulations impose rigorous administrative, physical, and technical safeguards to ensure patient confidentiality and data integrity, thereby creating an extraordinarily complex regulatory environment for entities seeking to leverage this communication data.9 This regulatory density severely complicates the extraction, utilization, and dissemination of clinical conversational data for secondary research purposes, quality improvement initiatives, or the training of advanced artificial intelligence (AI) and Large Language Models (LLMs).11
+
+Determining the "most asked question" online that is actively regulated by HIPAA requires a bifurcated, empirical analysis of the two primary modalities of digital patient-provider interaction: asynchronous secure messaging and synchronous telehealth encounters. Understanding the empirical distribution, semantic intent, and clinical acuity of these queries is the foundational prerequisite for designing, engineering, and validating robust clinical Question-Answering (QA) datasets. This comprehensive report provides an exhaustive analysis of patient query behaviors, evaluates the regulatory and technical frameworks governing Protected Health Information (PHI), analyzes the limitations of existing dataset architectures, and delineates a meticulously structured, multi-phase strategic plan for constructing a high-fidelity, HIPAA-compliant medical QA dataset.
+
+## **Legislative Catalysts and the Empirical Landscape of Digital Access**
+
+To properly contextualize the volume and nature of HIPAA-regulated questions, it is necessary to examine the underlying legislative catalysts that have democratized digital health access and the resulting empirical usage trends among diverse patient populations.
+
+### **Information Blocking and the 21st Century Cures Act**
+
+The accessibility of patient health information has been profoundly reshaped by the 21st Century Cures Act of 2016 and the subsequent Information Blocking Rule finalized by the Office of the National Coordinator for Health Information Technology (ONC) in 2020\.14 Prior to these regulations, the HIPAA Privacy Rule envisioned a relatively analog process wherein patients would submit formal requests for their medical records, granting providers up to thirty days to locate, assemble, and mail paper copies or physical digital media.8
+
+The Information Blocking Rule radically altered this temporal dynamic by effectively prohibiting practices likely to interfere with the access, exchange, or use of electronic health information.15 To comply with the Cures Act, certified health IT developers are required to adopt secure, standards-based application programming interfaces (APIs) that empower patients to seamlessly access their health records via third-party smartphone applications and provider-hosted portals.14 Consequently, health systems have vastly expanded the depth and immediacy of the data available to patients in their portals, transitioning from limited, delayed release schedules to near-instantaneous access to clinical notes, laboratory results, and diagnostic imaging reports.6
+
+### **Demographic Utilization and Portal Adoption Rates**
+
+Despite the pervasive availability of patient portals, adoption and utilization rates reveal a complex landscape characterized by behavioral barriers and demographic disparities. Data published by the U.S. Government Accountability Office (GAO) indicates that while nearly 90 percent of patients interacting with participating Medicare EHR providers have access to patient portals, historically fewer than a third of these patients utilized the portals to view their health information.7
+
+However, longitudinal survey data demonstrates a steady upward trajectory in adoption. The Health Information National Trends Survey (HINTS) fielded by the National Cancer Institute indicates that by early 2020, approximately 60 percent of individuals nationwide were offered access to a patient portal, representing a 17 percentage point increase from 2014\.14 Among those offered access, nearly 40 percent logged into their records at least once in 2020, with nearly four in ten users accessing their portals via mobile smartphone applications.14
+
+The COVID-19 pandemic served as a massive catalyst for digital health literacy. Data derived from the 2022 HINTS 6 survey demonstrates that overall portal access surged to 61.3 percent of all respondents over a 12-month period, with 43.7 percent of users managing multiple portals simultaneously.6 The utilization frequency also highlights the integration of these platforms into routine health management.
+
+| Patient Portal Use Frequency (Past 12 Months) | Percentage of Active Users |
+| :---- | :---- |
+| **1 to 9 times annually** | 52.7% 16 |
+| **About monthly** | 18.6% 16 |
+| **More than monthly** | 28.7% 16 |
+
+The most common impetus for logging into a portal is the retrieval of clinical data, with 89.9 percent of respondents reporting usage to access test results, 69.8 percent viewing clinical notes, and 31.9 percent downloading their personal health information.6 Furthermore, likelihood of portal utilization significantly increased (by 24.9 percentage points) when access was explicitly encouraged by healthcare providers or insurers, indicating that provider engagement is a critical variable in driving digital patient interaction.6 User demographics consistently indicate that portal utilization rates generally increase with advancing age and among female cohorts, reflecting broader patterns in healthcare consumption and chronic disease management.3
+
+## **The Taxonomy and Frequency of HIPAA-Regulated Online Queries**
+
+While accessing test results is the primary driver of portal login events, the asynchronous secure messaging feature represents the core interface where patients actively generate novel, HIPAA-regulated questions. To ascertain the "most asked question" in this domain, one must classify the semantic intent of millions of unstructured narrative messages generated within these secure digital environments.
+
+### **Asynchronous Secure Messaging: The Dominance of Alerts and Triage Requests**
+
+When patients initiate communication with their healthcare providers via secure messaging, their inquiries are fundamentally transactional or deeply clinical. A comprehensive empirical classification of secure patient messages reveals that the most frequently generated online questions and statements actively regulated by HIPAA fall under the category of "Alerts and Requests," which comprise exactly 40 percent of all patient-initiated messages.17
+
+This dominant category encompasses messages wherein a patient identifies a new clinical condition, reports a novel symptom, details the exacerbation of an existing problem, or requests a specific medical service or therapeutic device.17 These messages operate effectively as asynchronous clinical triage requests. For example, statements such as "I have been having more frequent headaches" or "My surgical incision is increasingly red and swollen" are classic manifestations of this category.17
+
+The second most prevalent category, accounting for 28 percent of patient messages, is purely interrogative "Questions".17 These queries seek specific medical, pharmacological, or logistical information without necessarily alerting the provider to a new symptom.17 Examples include questions regarding diagnostic scheduling ("Will I be having an MRI today?") or inquiries about medication side effects.17
+
+A detailed taxonomy of the semantic intent driving asynchronous patient messages reveals the following distribution:
+
+| Message Intent Category | Definition and Scope | Example Query | Patient-Initiated Frequency |
+| :---- | :---- | :---- | :---- |
+| **Alerts / Requests** | Identifying new symptoms, acute conditions, or requesting clinical services or devices. | "I have been having more frequent headaches." | 40% 17 |
+| **Questions** | Seeking specific information regarding a clinical or administrative topic. | "Will I be having an MRI today?" | 28% 17 |
+| **Thanks / Gratitude** | Offering thanks or expressing gratitude for care received. | "Thank you for taking such great care of me." | 25% 17 |
+
+Secondary structural analyses of these communications indicate that a substantial volume of messaging is utilized for non-urgent administrative and custodial issues.18 Patients frequently use portals to navigate the bureaucratic complexities of the healthcare system, submitting queries regarding insurance pre-authorization forms, workplace injury documentation, or assistance activating prescription savings programs.18 Custodial queries also extend to the inpatient environment, where tablet-based applications allow patients to report technical issues or request physical environment adjustments (e.g., "I would like an extra pillow").17
+
+However, from a dataset engineering perspective, the asynchronous reporting of new symptoms for triage purposes represents the intersection of the highest clinical value and the highest regulatory risk. These messages are densely saturated with PHI, including specific dates of symptom onset, concurrent medication lists, and detailed anatomical descriptions.17 Furthermore, analyses of health outcomes connected to secure messaging indicate that potentially reversible, serious illnesses—such as severe infections requiring intravenous antibiotics or acute asthma exacerbations requiring hospitalization—are frequently initially communicated via these digital alerts.20
+
+### **Specialty-Specific Variances in Question Generation**
+
+The volume, frequency, and specific medical nature of HIPAA-regulated questions vary dramatically depending on the medical specialty of the receiving provider. Large-scale analyses of outpatient encounters and secure message threads demonstrate that Internal Medicine and Primary Care disciplines drive the vast majority of digital queries.21 Primary care physicians initiate and respond to the largest absolute number of messages year over year, heavily focused on chronic disease management, blood pressure monitoring, and routine triage.21
+
+However, adoption is not exclusive to primary care. Data indicates that surgical specialists emerged as the second most frequent users of secure messaging, contributing to over 11 percent of all message threads in some large academic medical centers.22 Surgical queries frequently revolve around post-operative wound care, pain management, and recovery timelines.22
+
+| Clinical Specialty | Outpatient Encounters (N=2,189,521) | Total Message Threads (N=948,428) | Percentage of Total Threads |
+| :---- | :---- | :---- | :---- |
+| **Internal Medicine / Primary Care** | High Volume | \~379,352 (2010 data) | \~78.3% 22 |
+| **Surgery** | 661,337 (30.2%) | 84,001 | 8.9% 22 |
+| **Obstetrics / Gynecology** | 54,872 (2.5%) | 53,424 | 5.6% 22 |
+| **Pediatrics** | 318,386 (14.5%) | 33,543 | 3.5% 22 |
+| **Dermatology** | 34,785 (1.6%) | 13,591 | 1.4% 22 |
+
+### **The Telehealth Modality: Logistical, Efficacy, and Comparative Inquiries**
+
+While asynchronous portals capture acute symptom reporting and chronic disease tracking, synchronous telehealth encounters generate a highly distinct set of commonly asked questions. As patients navigate the virtual care ecosystem, their inquiries heavily index toward logistical preparedness, platform security, and the comparative efficacy of virtual medicine versus traditional in-person care.
+
+Empirical data underscores the deep entrenchment of this modality. A 2024 national survey conducted by Public Opinion Strategies on behalf of Hims & Hers revealed that fully 54 percent of the American populace has now engaged in a telehealth visit.23 Furthermore, an overwhelming 89 percent of those users reported high satisfaction levels with their most recent virtual encounter, a metric that has remained remarkably stable, never dipping below 86 percent in four years of longitudinal tracking.23 Similarly, two-thirds (67 percent) of Americans actively support legislation designed to expand patient access to asynchronous telehealth services.23
+
+Despite this high satisfaction, the primary question patients ask regarding telehealth remains foundational: "How does a virtual doctor's appointment work?".1 Because telehealth relies on interactive video technology—or asynchronous store-and-forward communication—to bridge the geographic divide between provider and patient, users frequently seek assurance regarding the procedural mechanics of the encounter.1
+
+Secondary interrogatories in the telehealth domain encompass:
+
+* **Security and Privacy:** "Is my virtual visit safe and secure?" Patients are acutely aware of cyber risks and explicitly question whether their clinical conversations are protected from interception, underscoring the absolute necessity for platforms to utilize end-to-end encryption and comply fully with HIPAA security standards.24  
+* **Clinical Appropriateness:** "Do virtual visits meet my needs?" or "What conditions can be treated virtually?" Patients seek validation that their specific ailments—whether chronic obstructive pulmonary disease (COPD), congestive heart failure, or acute issues like a urinary tract infection or a severe laceration—can be safely managed without physical palpation or immediate laboratory testing.1  
+* **Continuity of Care:** "How do I get prescription medications if I see my provider by telemedicine? What if I need lab tests?" Logistical concerns regarding the integration of virtual prescribing and remote diagnostic orders represent a major subset of continuity inquiries.1  
+* **Equivalence to Traditional Care:** "Is remote care as good as in-person care?" and "How much will virtual medicine change my normal care?" Queries addressing the qualitative equivalence of virtual medicine compared to physical office visits remain pervasive, indicating a lingering skepticism regarding diagnostic accuracy over video feeds.24
+
+Medicare claims data corroborates the systemic reliance on telehealth, particularly within behavioral health. Research indicates that psychiatrists had the highest share of eligible spending billed as telehealth services at 31.2 percent, whereas procedural specialties like ophthalmology utilized it for only 1.8 percent of visits.28 Consequently, mental health inquiries heavily dominate telehealth transcripts.1
+
+### **The Shift Toward Secure Text Messaging**
+
+While patient portals remain the standard enterprise solution, there is a pronounced consumer preference shifting toward secure, mobile text messaging. Surveys indicate that only 10 percent of patients prefer to receive physician communications via traditional patient portals.30 Conversely, nearly twice that amount (19.6 percent) explicitly favor receiving information via secure text messages when physical or telephonic communication is not feasible.30 Furthermore, over 90 percent of respondents desire the ability to communicate via secure text messaging with a family member's care team during acute illnesses.30
+
+Patients overwhelmingly welcome text messages that encourage health adherence; 83 percent of respondents welcome reminders regarding medication adherence, blood pressure checks, rehabilitation exercises, and follow-up scheduling.30 Texting reduces no-show rates by up to 50 percent and eliminates the friction of navigating portal login screens and remembering passwords.31 Consequently, healthcare organizations are increasingly investing in purpose-built, HIPAA-compliant secure messaging applications that offer end-to-end encryption, role-based access controls, and automatic message deletion schedules to mitigate unauthorized access while fulfilling patient preferences.26 Inpatient data reveals that these secure messaging platforms are heavily utilized for intra-professional communication, with the highest proportion of messages flowing from nurses to physicians, followed by physicians to nurses, enhancing care coordination while avoiding the friction of "telephone tag".33
+
+In synthesis, the singular "most asked question" online that is actively regulated by HIPAA is an asynchronous triage request detailing the onset or exacerbation of a symptom (e.g., "I am experiencing; what should I do?"), closely followed by logistical inquiries regarding the operational mechanics and diagnostic efficacy of virtual care platforms. Any dataset architecture constructed to accurately model clinical question-answering must heavily index these precise semantic and structural intents.
+
+## **The Regulatory Architecture: HIPAA, PHI, and Intersecting Frameworks**
+
+Constructing a dataset from authentic patient-provider interactions requires a flawless, institutional understanding of the federal regulatory guardrails established by the Health Insurance Portability and Accountability Act. Enacted in 1996, HIPAA was designed to safeguard patient privacy, secure health information, facilitate the detection and enforcement of healthcare fraud, and ensure the portability of health insurance coverage for American workers.9
+
+### **The Privacy and Security Rules**
+
+The HIPAA mandate is operationally bifurcated into several distinct rules, the most critical for health informaticians being the Privacy Rule and the Security Rule.9
+
+The Standards for Privacy of Individually Identifiable Health Information, commonly known as the Privacy Rule, establishes a comprehensive set of national standards governing the protection of specific health data.10 Issued by the U.S. Department of Health and Human Services (HHS) and enforced by the Office for Civil Rights (OCR), the Privacy Rule meticulously defines and regulates the use and disclosure of "Protected Health Information" (PHI) by organizations legally defined as "covered entities".10 Covered entities exclusively include health plans, healthcare clearinghouses, and any healthcare provider who electronically transmits health information in connection with certain transactions, such as claims processing or benefit eligibility inquiries.36 Crucially, the Privacy Rule sets rigid standards for individual privacy rights, granting patients the legal authority to access, be informed of, and control how their health information is utilized or restricted.10
+
+Concurrently, the Security Rule establishes specific national standards for protecting the confidentiality, integrity, and availability of *electronic* Protected Health Information (ePHI).11 The Security Rule mandates that covered entities implement highly specific administrative, physical, and technical safeguards.11 These encompass stringent requirements for data encryption, emergency mode operations planning, disaster recovery architecture, and continuous testing of data backup plans to ensure data availability during catastrophic events.38
+
+### **Defining Protected Health Information (PHI)**
+
+Under the administrative simplification regulations of HIPAA, PHI is defined comprehensively as any individually identifiable health information—whether communicated orally, recorded on paper, or transmitted via electronic medium—that relates to the past, present, or future physical or mental health or condition of an individual; the provision of healthcare to an individual; or the past, present, or future payment for the provision of healthcare.11 This definition encompasses all related information maintained in a designated record set that could identify the individual or be combined with other available information to deduce identity.39
+
+It is vital to recognize that health information only achieves the legal status of PHI when it is created, received, maintained, or transmitted by a covered entity or its business associate.36 For instance, if a patient posts a highly specific medical question detailing their symptoms and genetic history on an open internet forum or commercial social media platform, that data is generally outside the purview of HIPAA. However, if that identical question is typed into a hospital's secure messaging portal, it immediately transforms into PHI, subjecting the data to the full weight of federal protection.15
+
+### **Business Associates and the Adversarial Data Security Landscape**
+
+Organizations that provide external services to covered entities and require access to PHI to perform their functions—such as cloud storage providers, AI analytics vendors, clinical transcription services, and software testing firms—are legally classified as "Business Associates".40 Under HIPAA, covered entities must execute rigorous, legally binding Business Associate Agreements (BAAs) with these vendors.13 A BAA contractually obligates the business associate to adhere to identical HIPAA Privacy and Security regulations, extending the liability envelope to the third party.13
+
+The urgency of maintaining flawless compliance is dramatically underscored by epidemiological data regarding healthcare cybersecurity. A study published in JAMA Network Open in May 2025 revealed that healthcare data breaches more than doubled between 2010 and 2024, rising from 216 reported incidents to 566\.43 More concerning is the fundamental shift in the vector of these breaches. In 2010, malicious hacking and information technology vulnerabilities accounted for a mere 4 percent of reported incidents.43 By 2024, sophisticated cyberattacks and hacking operations represented an overwhelming 81 percent of all HIPAA-reported healthcare breaches.43 Ransomware attacks, which were historically rare in the medical sector, have become an existential threat, affecting nearly 7 in 10 breached records and compromising 69 percent of all patient data involved in breaches.43 Consequently, any infrastructure designed to aggregate patient questions for dataset construction must be built under the assumption of a highly hostile, adversarial cybersecurity environment.
+
+### **Intersecting Ethical and Regulatory Frameworks**
+
+Beyond HIPAA, the aggregation of healthcare data intersects with other complex legal and ethical frameworks. While HIPAA protects patient charts, the ethical sourcing of provider contact data for research or commercial outreach is governed by alternative statutes.44 If a research entity attempts to source communication transcripts or survey data directly from providers via SMS or email, they must navigate the Telephone Consumer Protection Act (TCPA) and the CAN-SPAM Act.44 The TCPA imposes strict restrictions on automated communications and robocalls to mobile devices, and while there are narrow "health care messaging" exemptions, these primarily apply to clinic-to-patient operational reminders, not vendor-to-physician recruitment or advertising.44 Furthermore, industry codes such as those published by the Pharmaceutical Research and Manufacturers of America (PhRMA) dictate the ethical boundaries of interacting with healthcare professionals.44
+
+In the realm of research datasets, there is also a critical legal distinction between HIPAA definitions of de-identification and the definitions utilized by the Federal Policy for the Protection of Human Subjects, known as the Common Rule.45 Under the Common Rule, a dataset is only considered "de-identified" when absolutely no one can re-identify the data; if the data utilizes a code mapping to an identity, the key to that code must be permanently destroyed.45 The Common Rule classifies data retaining a re-identification code as "indirectly identifiable".45 Conversely, HIPAA permits the retention of a re-identification key by the covered entity under certain conditions.45 Therefore, a dataset can technically meet HIPAA "de-identified" criteria while still being classified as "identifiable" and subject to stringent IRB oversight under the Common Rule.45
+
+## **Methodological Paradigms in Protected Health Information De-Identification**
+
+Before any raw patient inquiry or provider response can be safely ingested into an AI training dataset, it must undergo a rigorous de-identification process. HIPAA provides two explicit, statutory methodologies for achieving legal de-identification: The Safe Harbor Method and the Expert Determination (Statistical) Method.13
+
+### **The Safe Harbor Method**
+
+The Safe Harbor method is a highly prescriptive, conservative, and deterministic approach to privacy. It mandates the absolute removal of 18 specific categories of identifiers pertaining to the patient, the patient's relatives, employers, or household members.13 Once these 18 identifiers are successfully excised from the designated record set, and provided the covered entity possesses no actual knowledge that the remaining residual information could be utilized—either alone or in combination with external datasets—to re-identify the patient, the data is legally considered de-identified.45 At this juncture, the information is stripped of its PHI status and is no longer subject to HIPAA regulations, negating the requirement to report subsequent data leaks or breaches.46
+
+The 18 HIPAA Safe Harbor identifiers encompass a broad spectrum of demographic and digital data:
+
+| Identifier Category | Specific Elements Mandated for Removal |
+| :---- | :---- |
+| **Nomenclature** | All names associated with patients, providers, relatives, and household members. |
+| **Geographic Data** | All geographic subdivisions smaller than a state (e.g., street address, city, county, precinct, ZIP code). Exception: The initial 3 digits of a ZIP code may be retained if the combined population of all ZIP codes beginning with those digits exceeds 20,000.45 |
+| **Chronological Data** | All elements of dates (except the year) directly related to an individual, including birth date, admission date, discharge date, and specific dates of medical procedures. Additionally, all exact ages over 89 must be aggregated into a single category of "age 90 or older".51 |
+| **Contact Interfaces** | Telephone numbers, fax numbers, and personal email addresses.51 |
+| **Identification Metrics** | Social Security Numbers (SSNs), Medical Record Numbers (MRNs), Health plan beneficiary numbers, Account numbers, and Certificate/license numbers.50 |
+| **Hardware Data** | Vehicle identifiers and serial numbers (including license plate numbers), and Device identifiers/serial numbers.50 |
+| **Digital Footprints** | Web Universal Resource Locators (URLs) and Internet Protocol (IP) address numbers.50 |
+| **Biometric & Image Data** | Biometric identifiers (including finger and voice prints), Full-face photographic images, and any comparable visual images.50 |
+| **Catch-All Provision** | Any other unique identifying number, characteristic, or code not explicitly listed above.50 |
+
+While the Safe Harbor method provides a straightforward, highly predictable operational checklist that simplifies compliance audits, it fundamentally degrades the analytic utility of the resulting dataset.47 Safe Harbor was not conceived with complex longitudinal research or geospatial epidemiology in mind.52 The total removal of specific dates and geographic locations destroys the ability to track disease progression timelines, seasonal symptom fluctuations, and localized environmental health trends.52 Furthermore, Safe Harbor fails to account for unique quasi-identifiers; a patient listed with the occupation of "Mayor" or "Governor" combined with a state-level geographic marker remains easily re-identifiable, highlighting a critical vulnerability in the prescriptive approach.52
+
+### **The Expert Determination (Statistical) Method**
+
+To circumvent the data utility destruction inherent in Safe Harbor, the HIPAA Privacy Rule established a secondary standard known as the Expert Determination Method, or Statistical Method.47 This approach utilizes sophisticated risk-management protocols designed to preserve richer data detail while maintaining strict legal compliance.47
+
+Under this provision, an organization must employ a qualified expert possessing appropriate knowledge of, and experience with, generally accepted statistical and scientific principles for rendering information not individually identifiable.46 This expert conducts a rigorous statistical analysis to determine that the risk is "very small" that the information could be used by an anticipated recipient to identify an individual.46 The expert documents the specific methods, risk analyses, data transformations applied, limitations, and re-evaluation triggers in a formal written report.53
+
+Expert Determination achieves privacy protection through mathematical binning strategies, such as ![][image1]\-anonymity, which stipulates that each disclosed record within a dataset must be indistinguishable from at least ![][image2] other records with respect to a set of potentially identifying attributes.54 Advanced frameworks utilize lattice structures to automatically discover alternative de-identification policies, tuning the fidelity of potentially identifying attributes to locate solutions that offer equal or lesser risk compared to Safe Harbor, while preserving critical clinical variances.54 Because Expert Determination quantifies residual risk and tailors protections to the specific characteristics of the dataset, it is highly preferred for advanced AI training, research-grade datasets involving small or rare disease populations, and complex modalities like free-text narrative logs where Safe Harbor would indiscriminately over-suppress contextual data.47
+
+### **Algorithmic De-Identification Pipelines for Narrative Text**
+
+Executing these de-identification methodologies on the unstructured, highly variable narrative text found in patient portal messages requires sophisticated computational NLP pipelines.51 Early attempts utilizing basic rule-based systems, pattern matching, and regular expressions (RegEx) to target 10-digit phone numbers or SSNs proved wholly inadequate for electronic health records.51 Narrative clinical notes and patient messages are rife with typographical errors, non-standard abbreviations, and idiosyncratic syntax that cause dictionary lookups to fail.55 These failures lead to catastrophic PHI leakage or aggressive over-redaction, such as a rule-based algorithm deleting the word "Jackson" when a physician describes placing a Jackson-Pratt surgical drain, falsely identifying it as a patient's surname.55
+
+State-of-the-art de-identification architectures rely on an ensemble approach that fuses rule-based heuristics with advanced deep learning models.51 These systems utilize Named Entity Recognition (NER) models powered by transformer architectures like ClinicalBERT, which are specifically pre-trained on vast corpuses of clinical text to detect and classify entities based on semantic context rather than mere string matching.51 Once PHI is detected, the pipeline executes advanced transformations. Rather than simply deleting dates, the system employs "Date Shifting," moving dates backward or forward by a random, uniformly distributed integer that remains consistent for a specific patient's longitudinal record, thereby preserving the timeline while obfuscating the actual dates.51 Finally, "PHI Seeding" techniques are utilized to replace detected real names with synthetically generated, demographically accurate fake names, maintaining the linguistic structure and readability of the text for downstream NLP tasks.51
+
+## **Critical Analysis of Existing Medical Question-Answering Corpora**
+
+To engineer a superior QA dataset, it is essential to critically evaluate the architectural successes and methodological shortcomings of existing clinical datasets within the open-source and academic domains.58 The landscape is notoriously sparse due to the inherent legal and ethical risks of publicly releasing data derived from real EHRs.58
+
+### **The emrQA Corpus: Scale via Automated Generation**
+
+The emrQA dataset stands as a foundational benchmark in clinical Question Answering.60 Recognizing the critical absence of publicly available EMR QA corpora, researchers from academic institutions developed a novel, semi-automated generation framework.62 Instead of manually annotating hundreds of thousands of notes—a prohibitively expensive and slow process—they repurposed existing expert annotations from the community-shared i2b2 challenge datasets, which included pre-existing tags for medications, relations, smoking status, and obesity.62
+
+The generation pipeline was highly structured: researchers collected authentic clinical questions from medical experts and converted these into abstract templates by replacing specific clinical entities with semantic placeholders (e.g., converting "How was the patient's extensive liver metastases diagnosed?" to "How was the diagnosis of |problem| made?").60 These templates were then annotated with logical forms representing the search criteria.60 Finally, automated algorithms utilized the existing i2b2 annotations to fill the placeholders and generate answer evidence.63
+
+This slot-filling methodology allowed emrQA to achieve massive scale, resulting in a corpus of over 1 million question-logical form pairs and 400,000 question-answer evidence pairs mapped directly against 2,425 clinical notes.60 However, subsequent evaluations of models trained on emrQA exposed a critical vulnerability: a severe lack of generalizability.64 When state-of-the-art readers like DocReader and ClinicalBERT were trained on emrQA and then tested on entirely unseen, human-generated questions from a different clinical dataset (MIMIC-III), their performance dropped precipitously by approximately 40 percent.64 The models struggled significantly with questions that were syntactically different or paraphrased from the rigid templates, demonstrating that slot-filled synthetic generation fails to capture the chaotic, colloquial nuance of true human inquiry.64
+
+### **ASQ-PHI: Adversarial Prompts and Safe Handoffs**
+
+A newer paradigm is represented by the ASQ-PHI (Adversarial Synthetic Queries for Protected Health Information de-identification) benchmark.65 This dataset was engineered to address a specific, modern problem: the interaction between clinicians and HIPAA-compliant LLMs. While hospitals increasingly deploy LLMs under secure Business Associate Agreements, these models are trained on fixed knowledge cutoffs.65 When clinicians require updated medical evidence, the LLM must execute a live web search—an external tool often not covered by the BAA.65 This creates a high-risk "safe handoff" point where the clinician's prompt must be perfectly scrubbed of PHI before leaving the secure environment.65
+
+Because existing de-identification tools were built for long-form narrative discharge summaries rather than short, conversational LLM prompts, ASQ-PHI provides a fully synthetic, publicly shareable dataset mimicking these clinical search queries.65 The dataset contains 1,051 single-turn queries incorporating 2,973 annotated PHI elements across 13 HIPAA Safe Harbor identifier types, with a heavy emphasis on geographic locations (27.8%), names (27.4%), and dates (27.1%).66 Crucially, ASQ-PHI introduces 219 "hard negatives"—adversarial queries designed to perfectly mimic PHI-like syntax without actually containing identifiable data.66 This forces NLP models to distinguish between true PHI and clinically relevant contextual data (e.g., patient age under 90, eponymous disease names), establishing a vital metric for measuring over-redaction.65
+
+### **Taxonomic Refinement: MedQuAD and RealMedQA**
+
+Other notable advancements include MedQuAD and RealMedQA, which focus heavily on intent classification and realistic syntax.69 MedQuAD utilizes an extensive XML annotation schema that tags not just the question and answer, but the specific medical entity it focuses on (disease, drug, test), the unique identifier (CUI), and the semantic type.69 RealMedQA attempts to solve the template-rigidity problem of emrQA by utilizing a hybrid approach where questions are generated by both human experts and LLMs, resulting in lower lexical similarity between queries and a more realistic reflection of how health professionals actually seek information.70
+
+A definitive, next-generation dataset must amalgamate the massive scale and clinical grounding of emrQA, the adversarial prompt-based structure of ASQ-PHI, and the rich, granular semantic taxonomy of MedQuAD.
+
+## **Strategic Blueprint for Constructing a Next-Generation Clinical QA Dataset**
+
+Based on the preceding exhaustive analysis of patient inquiry behavior, regulatory constraints, and existing dataset architecture, the following is a comprehensive, multi-phase strategic plan for building an impenetrable, highly structured, and intent-classified dataset focused on the most frequently asked online medical inquiries.
+
+### **Phase 1: Institutional Sourcing and Zero-Trust Infrastructure**
+
+The genesis of the dataset relies on sourcing authentic, diverse conversational data while establishing an impregnable, compliant technical architecture capable of withstanding modern cyber threats.
+
+**1\. Data Sourcing and Legal Frameworks:** Given the strict ethical and legal constraints regarding patient data, scraping unverified public forums is inadequate; it fails to capture true clinical intent and is inherently biased toward low-acuity, non-urgent inquiries. The dataset must rely on structured, formalized partnerships with large-scale academic health systems.11
+
+* **EHR and Portal Extraction:** The primary data source will be historical, de-identified patient portal message logs and secure text messaging application transcripts.11 Accessing this data requires the execution of comprehensive Business Associate Agreements (BAAs) and formal Institutional Review Board (IRB) approvals to ensure compliance with both HIPAA and the Common Rule.41  
+* **Adversarial Synthetic Augmentation:** Mirroring the highly successful ASQ-PHI methodology, the authentic data will be supplemented with LLM-generated synthetic queries.65 These synthetic queries will be mathematically engineered to reflect the known empirical distribution of real queries (e.g., strictly maintaining a ratio of 40% Alerts/Requests, 28% General Questions, etc.).17 The synthetic generation will deliberately introduce edge cases, typographical errors, colloquialisms, and adversarial "hard negative" structures designed to aggressively challenge downstream NLP models.17
+
+**2\. Secure Data Lake and Blockchain Architecture:**
+
+The ingestion and processing infrastructure must be HIPAA-compliant from inception, utilizing zero-trust network principles and decentralized auditing mechanisms.
+
+* **Storage and Compute:** Implement a centralized data lake utilizing a Ceph storage cluster with mixed NVMe and HDD nodes to provide a robust, unified block, object, and file storage foundation.72 Compute workloads will execute on isolated OpenStack virtual machines with dedicated private networking.41  
+* **Network Isolation:** Implement stringent VLAN segmentation, utilizing Neutron security groups to strictly isolate any traffic containing potential PHI from public-facing internet nodes.41  
+* **Cryptographic Security and Blockchain Auditing:** Utilize advanced identity management (OpenStack Keystone) and key management systems (Barbican) to enforce encryption at rest and in transit.41 To solve the complex challenge of consent management and multi-organizational auditing, the architecture will incorporate a permissioned blockchain framework utilizing Hyperledger Fabric and the InterPlanetary File System (IPFS).73 Smart contracts will be deployed to enforce privacy policies, manage patient consent dynamically, and provide a decentralized, immutable audit trail of every data access event, fully satisfying HIPAA's strict auditing requirements.41
+
+### **Phase 2: Intent Taxonomy and Semantic Structuring**
+
+A high-utility QA dataset must do substantially more than pair a question with an answer; it must accurately classify the underlying semantic intent of the query to enable downstream AI models to route, prioritize, and process information accurately.69
+
+**1\. Development of an E-Health Question Taxonomy (EQT):** Drawing inspiration from e-commerce intent modeling, the dataset will annotate every query utilizing a granular, bespoke taxonomy derived directly from empirical portal usage data.17
+
+* **Clinical Alerts (Acute Triage):** Inquiries signaling acute physiological changes, pain onset, trauma, or adverse medication reactions requiring immediate triage.17  
+* **Therapeutic Management:** Questions regarding specific medication dosages, drug-drug interactions, and contraindications.58  
+* **Diagnostic Interpretation:** Questions seeking lay-term translation and interpretation of laboratory assay results, imaging reports, or specialist referrals.3  
+* **Logistical / Custodial Telehealth:** Inquiries regarding telehealth platform mechanics, video conferencing troubleshooting, appointment scheduling, and insurance pre-authorization mechanics.1
+
+**2\. Multi-Modal Annotation Schema:** Following the precedents set by MedQuAD and emrQA, each discrete query entry in the dataset will be structurally enriched with multiple annotation layers 60:
+
+* **Raw Query (Scrubbed):** The exact, colloquial wording utilized by the patient or provider.  
+* **Semantic Intent Tag:** The classified category from the EQT hierarchy.  
+* **Extracted Clinical Entities (NER):** Tagged clinical entities utilizing BIO (Begin, Inside, Outside) format (e.g., B-Disease, I-Symptom, B-Drug).76  
+* **Logical Form Template:** A structured, machine-readable representation of the question's core logic (e.g., Does \[Patient\] show evidence of following administration of \[Medication\]?).60  
+* **Ground Truth Answer:** High-quality answers curated by domain experts or extracted directly from the corresponding physician responses within the secure message thread.17
+
+### **Phase 3: The Deep-Learning De-Identification Pipeline**
+
+This operational phase is the most critical for ensuring the dataset is legally viable for semi-public research distribution. The pipeline will transition the data from raw PHI to full compliance while retaining maximum longitudinal and clinical utility.
+
+**1\. Ensemble De-Identification:** Because relying on a single modality for PHI removal routinely results in catastrophic failure, the dataset pipeline will utilize a highly redundant ensemble approach.55
+
+* **Heuristic Pre-Processing:** Initial application of exhaustive, highly tuned regular expressions to target standard 10-digit phone numbers, SSNs, IP addresses, and structured calendar dates.51  
+* **Transformer-Based NER Extraction:** Deployment of fine-tuned ClinicalBERT models specifically trained to detect the 18 HIPAA identifier classes within unstructured, colloquial conversational text.51  
+* **Contextual Shifting and Masking:** Instead of destructively deleting dates, the pipeline will employ date shifting, moving all chronological events for a single patient by a uniform random integer to preserve the relative timeline.51 Geographical data will be programmatically binned to the 3-digit ZIP code level, ensuring minimum population thresholds are met without losing regional epidemiological data.46
+
+**2\. Statistical Certification via Expert Determination:** Once the automated pipeline completes the scrubbing process, rigorous statistical analysis will be performed to measure the dataset's ![][image1]\-anonymity and ![][image3]\-diversity metrics.54 A qualified statistical privacy expert will formally assess the data to certify that the mathematical risk of re-identification is negligible, satisfying the Expert Determination criteria of HIPAA.46 This critical certification step allows the dataset to retain the vital quasi-identifiers necessary for complex medical AI research that Safe Harbor would otherwise destroy.53
+
+**3\. Physician-in-the-Loop Clinical Validation:** A statistically significant subset of the de-identified QA pairs will be manually reviewed by board-certified physicians.64 This human-in-the-loop validation ensures that the clinical integrity of the original question and the medical accuracy of the ground truth answer have not been inadvertently altered, corrupted, or inverted during the algorithmic de-identification process.64
+
+### **Phase 4: Implementation of Dataset Evaluation Metrics**
+
+To guarantee the dataset actively drives progress in clinical AI rather than merely providing rote memorization tasks, it must be subject to rigorous internal benchmarking and software testing.77
+
+* **Explainability Constraints:** The dataset will incorporate multiple detailed explanations for each QA pair, forcing models to generate nuanced medical rationales rather than relying on shallow classification accuracy.78  
+* **Adversarial Robustness Testing:** The deliberate inclusion of ASQ-PHI inspired "hard negatives" will allow researchers to test their models against over-redaction and false-positive triage alerts, ensuring models can distinguish between true emergencies and benign conversational context.65  
+* **Generalizability Metrics:** The dataset will establish specific benchmarks to evaluate how models trained on templated queries perform against completely unseen, differently phrased synthetic human queries, measuring the F1 score and Exact Match (EM) degradation to ensure robust real-world applicability.64
+
+### **Phase 5: Distribution and Access Governance**
+
+While the finalized data will be rigorously de-identified, responsible governance of medical datasets remains an absolute ethical imperative.
+
+* **Tiered Access Model:** Distribution will utilize a credentialed, tiered access model similar to MIMIC-III or the i2b2 challenge datasets.60 Researchers requesting access must sign strict Data Use Agreements (DUAs) explicitly prohibiting any attempts at mathematical re-identification or linking the dataset with external public registries.71  
+* **Continuous Threat Monitoring:** The dataset administrators will actively monitor computational advancements in re-identification attacks and periodically update the masking algorithms, encryption keys, and data binning thresholds to ensure perpetual, long-term compliance with evolving data privacy standards.41
+
+## **Conclusion**
+
+The rapid, systemic evolution of healthcare communication into asynchronous patient portals and synchronous telehealth environments has generated a vast, unstructured repository of digital clinical interactions. Comprehensive analysis of these digital interactions demonstrates definitively that the most frequently asked online questions regulated by HIPAA involve direct, asynchronous patient alerts regarding new physiological symptoms and requests for clinical triage, operating alongside pervasive logistical inquiries regarding the efficacy and security of virtual care platforms.
+
+Constructing a robust, high-utility Question-Answering dataset from this sensitive data requires navigating an incredibly complex nexus of federal regulatory constraints, cybersecurity threats, and advanced NLP engineering challenges. Existing datasets provide critical foundational methodologies regarding synthetic generation and slot-filling, yet future datasets must aggressively bridge the remaining gaps between massive scale, true colloquial generalizability, and deep semantic intent classification.
+
+By executing a highly structured, multi-phase plan that relies on secure, zero-trust cloud architectures, empirical intent taxonomy, and redundant ensemble-based de-identification pipelines certified by Expert Determination, it is entirely possible to build a dataset that significantly accelerates clinical AI research. Such a dataset will not only train the next generation of clinical LLMs to safely and accurately navigate PHI handoffs, but it will also drastically enhance the efficiency and quality of automated patient triage, ultimately optimizing the digital delivery of healthcare while maintaining absolute, uncompromising fidelity to patient privacy.
+
+#### **Works cited**
+
+1. Common Questions about Telemedicine \- University of Kansas Medical Center, accessed April 28, 2026, [https://www.kumc.edu/research/center-for-telemedicine-and-telehealth/common-questions.html](https://www.kumc.edu/research/center-for-telemedicine-and-telehealth/common-questions.html)  
+2. Patient-To-Physician Messaging: Volume Nearly Tripled As More Patients Joined System, But Per Capita Rate Plateaued \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC4418542/](https://pmc.ncbi.nlm.nih.gov/articles/PMC4418542/)  
+3. The Impact of Digital Patient Portals on Health Outcomes, System Efficiency, and Patient Attitudes: Updated Systematic Literature Review \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC8459217/](https://pmc.ncbi.nlm.nih.gov/articles/PMC8459217/)  
+4. Health Information Privacy Laws in the Digital Age: HIPAA Doesn't Apply \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC7883355/](https://pmc.ncbi.nlm.nih.gov/articles/PMC7883355/)  
+5. 6 Common Telemedicine Questions Answered \- RWJBarnabas Health, accessed April 28, 2026, [https://www.rwjbh.org/blog/2020/june/6-questions-about-telemedicine-answered/](https://www.rwjbh.org/blog/2020/june/6-questions-about-telemedicine-answered/)  
+6. Patient Factors Associated With the Use of Online Portal Health Information in the Postpandemic Era: Cross-Sectional Analysis of a National Survey \- Journal of Medical Internet Research, accessed April 28, 2026, [https://www.jmir.org/2025/1/e60472](https://www.jmir.org/2025/1/e60472)  
+7. Only One Third of Patients Use Patient Portals to View Health Data \- The HIPAA Journal, accessed April 28, 2026, [https://www.hipaajournal.com/only-one-third-of-patients-use-patient-portals-to-view-their-health-data-8902/](https://www.hipaajournal.com/only-one-third-of-patients-use-patient-portals-to-view-their-health-data-8902/)  
+8. Patient Access to Personal Health Information: Regulation vs. Reality \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC4700868/](https://pmc.ncbi.nlm.nih.gov/articles/PMC4700868/)  
+9. Health Insurance Portability and Accountability Act (HIPAA) Compliance \- StatPearls \- NCBI, accessed April 28, 2026, [https://www.ncbi.nlm.nih.gov/books/NBK500019/](https://www.ncbi.nlm.nih.gov/books/NBK500019/)  
+10. Summary of the HIPAA Privacy Rule \- HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/privacy/laws-regulations/index.html](https://www.hhs.gov/hipaa/for-professionals/privacy/laws-regulations/index.html)  
+11. Patient Confidentiality \- StatPearls \- NCBI Bookshelf \- NIH, accessed April 28, 2026, [https://www.ncbi.nlm.nih.gov/books/NBK519540/](https://www.ncbi.nlm.nih.gov/books/NBK519540/)  
+12. HIPAA, Healthcare Data, and Artificial Intelligence, accessed April 28, 2026, [https://www.hipaajournal.com/hipaa-healthcare-data-and-artificial-intelligence/](https://www.hipaajournal.com/hipaa-healthcare-data-and-artificial-intelligence/)  
+13. Synthesizing healthcare data for AI model training, with HIPAA Expert Determination, accessed April 28, 2026, [https://www.tonic.ai/guides/hipaa-ai-compliance](https://www.tonic.ai/guides/hipaa-ai-compliance)  
+14. Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2020, accessed April 28, 2026, [https://healthit.gov/data/data-briefs/individuals-access-and-use-patient-portals-and-smartphone-health-apps-2020/](https://healthit.gov/data/data-briefs/individuals-access-and-use-patient-portals-and-smartphone-health-apps-2020/)  
+15. Provider Obligations for Patient Portals Under the 21st Century Cures Act, accessed April 28, 2026, [https://www.manatt.com/Insights/Newsletters/Health-Highlights/Provider-Obligations-for-Patient-Portals-Under-the](https://www.manatt.com/Insights/Newsletters/Health-Highlights/Provider-Obligations-for-Patient-Portals-Under-the)  
+16. Adult Patients' Experiences of Using a Patient Portal With a Focus on Perceived Benefits and Difficulties, and Perceptions on Privacy and Security: Qualitative Descriptive Study \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC10411420/](https://pmc.ncbi.nlm.nih.gov/articles/PMC10411420/)  
+17. Understanding Secure Messaging in the Inpatient Environment: A New Avenue for Communication and Patient Engagement \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC6281442/](https://pmc.ncbi.nlm.nih.gov/articles/PMC6281442/)  
+18. Patient-Centered Communication in Digital Medical Encounters \- PMC \- NIH, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC5573682/](https://pmc.ncbi.nlm.nih.gov/articles/PMC5573682/)  
+19. The Rules of Engagement: Perspectives on Secure Messaging From Experienced Ambulatory Patient Portal Users \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC5516097/](https://pmc.ncbi.nlm.nih.gov/articles/PMC5516097/)  
+20. Patient-generated secure messages and eVisits on a patient portal: are patients at risk? | Journal of the American Medical Informatics Association | Oxford Academic, accessed April 28, 2026, [https://academic.oup.com/jamia/article/20/6/1143/704281](https://academic.oup.com/jamia/article/20/6/1143/704281)  
+21. Characterizing Patient-Clinician Communication in Secure Medical Messages: Retrospective Study, accessed April 28, 2026, [https://www.jmir.org/2022/1/e17273/](https://www.jmir.org/2022/1/e17273/)  
+22. Growth of Secure Messaging Through a Patient Portal as a Form of Outpatient Interaction across Clinical Specialties \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC4493331/](https://pmc.ncbi.nlm.nih.gov/articles/PMC4493331/)  
+23. 2024 National Telehealth Survey \- Public Opinion Strategies, accessed April 28, 2026, [https://pos.org/2024-national-telehealth-survey/](https://pos.org/2024-national-telehealth-survey/)  
+24. Patients are Commonly Asking These 8 Virtual Care Questions \- TigerConnect, accessed April 28, 2026, [https://tigerconnect.com/resources/blog-articles/8-common-virtual-care-questions-posed-by-patients/](https://tigerconnect.com/resources/blog-articles/8-common-virtual-care-questions-posed-by-patients/)  
+25. The Top 10 Questions Physicians Ask About Telehealth \- Amwell Resource Center, accessed April 28, 2026, [https://resources.amwell.com/blog/the-top-10-questions-physicians-ask-about-telehealth](https://resources.amwell.com/blog/the-top-10-questions-physicians-ask-about-telehealth)  
+26. Secure Messaging in Healthcare: Why It Matters & Best Practices | TeleVox, accessed April 28, 2026, [https://televox.com/blog/healthcare/secure-messaging-healthcare/](https://televox.com/blog/healthcare/secure-messaging-healthcare/)  
+27. Get answers to your most common telehealth questions \- CHOC Health, accessed April 28, 2026, [https://health.choc.org/answers-to-your-most-common-telehealth-questions/](https://health.choc.org/answers-to-your-most-common-telehealth-questions/)  
+28. New data details how telehealth use varies by physician specialty, accessed April 28, 2026, [https://www.ama-assn.org/practice-management/digital-health/new-data-details-how-telehealth-use-varies-physician-specialty](https://www.ama-assn.org/practice-management/digital-health/new-data-details-how-telehealth-use-varies-physician-specialty)  
+29. Research Articles and Papers | Telehealth.HHS.gov, accessed April 28, 2026, [https://telehealth.hhs.gov/research-articles](https://telehealth.hhs.gov/research-articles)  
+30. Survey: Patients Prefer Secure Texting Over Patient Portal Communication From Their Physicians | DrFirst, accessed April 28, 2026, [https://drfirst.com/press-releases/survey-patients-prefer-secure-texting-over-patient-portal-communication-from-their-physicians](https://drfirst.com/press-releases/survey-patients-prefer-secure-texting-over-patient-portal-communication-from-their-physicians)  
+31. Healthcare Texting Statistics That Prove Its Value in 2025 \- Falkon SMS, accessed April 28, 2026, [https://www.falkonsms.com/post/healthcare-texting-statistics](https://www.falkonsms.com/post/healthcare-texting-statistics)  
+32. Should Your Hospital Invest in a Secure Messaging App? \- Amtelco, accessed April 28, 2026, [https://www.amtelco.com/resources/should-your-hospital-invest-in-a-secure-messaging-app/](https://www.amtelco.com/resources/should-your-hospital-invest-in-a-secure-messaging-app/)  
+33. Secure Messaging in Modern Healthcare Communication \- Updox, accessed April 28, 2026, [https://www.updox.com/blog/secure-messaging-in-modern-healthcare-communication/](https://www.updox.com/blog/secure-messaging-in-modern-healthcare-communication/)  
+34. 5 Common Misconceptions About Secure Messaging in Healthcare \- QliqSOFT, accessed April 28, 2026, [https://www.qliqsoft.com/blog/5-common-misconceptions-about-secure-messaging-in-healthcare](https://www.qliqsoft.com/blog/5-common-misconceptions-about-secure-messaging-in-healthcare)  
+35. FACT SHEET \- HealthIT.gov, accessed April 28, 2026, [https://healthit.gov/wp-content/uploads/2026/01/nlc-secure-messaging-fact-sheet.pdf](https://healthit.gov/wp-content/uploads/2026/01/nlc-secure-messaging-fact-sheet.pdf)  
+36. HIPAA Frequently Asked Questions \- American Psychological Association, accessed April 28, 2026, [https://www.apa.org/science/programs/research/hipaa-faq](https://www.apa.org/science/programs/research/hipaa-faq)  
+37. HIPAA FAQs for Individuals \- HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-individuals/faq/index.html](https://www.hhs.gov/hipaa/for-individuals/faq/index.html)  
+38. Healthcare Data Breach Statistics – Updated for 2026 \- The HIPAA Journal, accessed April 28, 2026, [https://www.hipaajournal.com/healthcare-data-breach-statistics/](https://www.hipaajournal.com/healthcare-data-breach-statistics/)  
+39. What is Considered PHI under HIPAA? Updated for 2026, accessed April 28, 2026, [https://www.hipaajournal.com/considered-phi-hipaa/](https://www.hipaajournal.com/considered-phi-hipaa/)  
+40. HIPAA 20 Questions | American Dental Association, accessed April 28, 2026, [https://www.ada.org/resources/practice/legal-and-regulatory/hipaa/hipaa-20-questions](https://www.ada.org/resources/practice/legal-and-regulatory/hipaa/hipaa-20-questions)  
+41. HIPAA Compliance for Healthcare Data Warehouse Projects: A Practical Guide, accessed April 28, 2026, [https://www.accountablehq.com/post/hipaa-compliance-for-healthcare-data-warehouse-projects-a-practical-guide](https://www.accountablehq.com/post/hipaa-compliance-for-healthcare-data-warehouse-projects-a-practical-guide)  
+42. HIPAA Compliance for Transcriptions, What You Need to Know \- TranscribeMe, accessed April 28, 2026, [https://www.transcribeme.com/blog/hipaa-compliance-for-transcriptions-what-you-need-to-know/](https://www.transcribeme.com/blog/hipaa-compliance-for-transcriptions-what-you-need-to-know/)  
+43. HIPAA Statistics Every Healthcare Entity Needs to Know in 2025, accessed April 28, 2026, [https://hipaauniversity.com/blog/hipaa-statistics/](https://hipaauniversity.com/blog/hipaa-statistics/)  
+44. HCP Contact Data: A Guide to Ethical Sourcing & Laws \- IntuitionLabs, accessed April 28, 2026, [https://intuitionlabs.ai/articles/ethical-hcp-contact-data-sourcing](https://intuitionlabs.ai/articles/ethical-hcp-contact-data-sourcing)  
+45. De-identified Data Sets – Medical School Office of Research, accessed April 28, 2026, [https://az.research.umich.edu/medschool/guidance/de-identified-data-sets/](https://az.research.umich.edu/medschool/guidance/de-identified-data-sets/)  
+46. Guidance Regarding Methods for De-identification of Protected Health Information in Accordance with the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule | HHS.gov, accessed April 28, 2026, [https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html](https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html)  
+47. HIPAA Safe Harbor vs. Expert Determination | Censinet, Inc., accessed April 28, 2026, [https://censinet.com/perspectives/hipaa-safe-harbor-vs-expert-determination](https://censinet.com/perspectives/hipaa-safe-harbor-vs-expert-determination)  
+48. The Safe Harbor Method of De-Identification \- Satori Cyber, accessed April 28, 2026, [https://satoricyber.com/data-classification/the-safe-harbor-method-of-de-identification-2/](https://satoricyber.com/data-classification/the-safe-harbor-method-of-de-identification-2/)  
+49. De-identification of Protected Health Information: How to Anonymize PHI \- The HIPAA Journal, accessed April 28, 2026, [https://www.hipaajournal.com/de-identification-protected-health-information/](https://www.hipaajournal.com/de-identification-protected-health-information/)  
+50. HIPAA PHI: Definition of PHI and List of 18 Identifiers \- Human Research Protection Program | UC Berkeley, accessed April 28, 2026, [https://cphs.berkeley.edu/hipaa/hipaa18.html](https://cphs.berkeley.edu/hipaa/hipaa18.html)  
+51. Natural Language Processing for Enterprise-scale De-identification of Protected Health Information in Clinical Notes \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC9285160/](https://pmc.ncbi.nlm.nih.gov/articles/PMC9285160/)  
+52. Safe Harbor Vs the Statistical Method \- Privacy Analytics, accessed April 28, 2026, [https://privacy-analytics.com/hubfs/Safe-Harbor-vs-the-Statistical-Method.pdf](https://privacy-analytics.com/hubfs/Safe-Harbor-vs-the-Statistical-Method.pdf)  
+53. HIPAA's Two Methods of De-Identification Explained: Safe Harbor vs. Expert Determination, accessed April 28, 2026, [https://www.accountablehq.com/post/hipaa-s-two-methods-of-de-identification-explained-safe-harbor-vs-expert-determination](https://www.accountablehq.com/post/hipaa-s-two-methods-of-de-identification-explained-safe-harbor-vs-expert-determination)  
+54. Beyond Safe Harbor: Automatic Discovery of Health Information De-identification Policy Alternatives \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC4267471/](https://pmc.ncbi.nlm.nih.gov/articles/PMC4267471/)  
+55. Identifying the Best De-Identification Protocols \- Mayo Clinic Platform, accessed April 28, 2026, [https://www.mayoclinicplatform.org/2021/07/12/identifying-the-best-de-identification-protocols/](https://www.mayoclinicplatform.org/2021/07/12/identifying-the-best-de-identification-protocols/)  
+56. De-Identification \- Clinical NLP Demos & Notebooks, accessed April 28, 2026, [https://nlp.johnsnowlabs.com/deidentification](https://nlp.johnsnowlabs.com/deidentification)  
+57. DeIDClinic: A Multi-Layered Framework for De-identification of Clinical Free-text Data \- arXiv, accessed April 28, 2026, [https://arxiv.org/html/2410.01648v1](https://arxiv.org/html/2410.01648v1)  
+58. Question Answering for Electronic Health Records: Scoping Review of Datasets and Models, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC11561445/](https://pmc.ncbi.nlm.nih.gov/articles/PMC11561445/)  
+59. Question Answering for Electronic Health Records: Scoping Review of Datasets and Models, accessed April 28, 2026, [https://pubmed.ncbi.nlm.nih.gov/39475821/](https://pubmed.ncbi.nlm.nih.gov/39475821/)  
+60. emrQA Homepage, accessed April 28, 2026, [https://emrqa.github.io/](https://emrqa.github.io/)  
+61. \[1809.00732\] emrQA: A Large Corpus for Question Answering on Electronic Medical Records \- arXiv, accessed April 28, 2026, [https://arxiv.org/abs/1809.00732](https://arxiv.org/abs/1809.00732)  
+62. emrQA: A Large Corpus for Question Answering on Electronic Medical Records \- MIT-IBM Watson AI Lab, accessed April 28, 2026, [https://mitibmwatsonailab.mit.edu/research/blog/emrqa-a-large-corpus-for-question-answering-on-electronic-medical-records/](https://mitibmwatsonailab.mit.edu/research/blog/emrqa-a-large-corpus-for-question-answering-on-electronic-medical-records/)  
+63. Code for the emrQA question answering dataset \- GitHub, accessed April 28, 2026, [https://github.com/panushri25/emrQA](https://github.com/panushri25/emrQA)  
+64. Clinical Reading Comprehension: A Thorough Analysis of the emrQA Dataset \- ACL Anthology, accessed April 28, 2026, [https://aclanthology.org/2020.acl-main.410.pdf](https://aclanthology.org/2020.acl-main.410.pdf)  
+65. ASQ-PHI: An adversarial synthetic data benchmark for clinical de-identification and search utility \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC12926592/](https://pmc.ncbi.nlm.nih.gov/articles/PMC12926592/)  
+66. ASQ-PHI Introduced: A Novel Benchmark Balancing Clinical Data Privacy and Search Utility, accessed April 28, 2026, [https://www.medtigo.com/news/asq-phi-introduced-a-novel-benchmark-balancing-clinical-data-privacy-and-search-utility/](https://www.medtigo.com/news/asq-phi-introduced-a-novel-benchmark-balancing-clinical-data-privacy-and-search-utility/)  
+67. ASQ-PHI: An adversarial synthetic data benchmark for clinical de-identification and search utility \- UTMB Research Expert Profiles, accessed April 28, 2026, [https://researchexperts.utmb.edu/en/publications/asq-phi-an-adversarial-synthetic-data-benchmark-for-clinical-de-i/](https://researchexperts.utmb.edu/en/publications/asq-phi-an-adversarial-synthetic-data-benchmark-for-clinical-de-i/)  
+68. ASQ-PHI: Adversarial Synthetic Queries for PHI \- GitHub, accessed April 28, 2026, [https://github.com/JamesWeatherhead/asq-phi](https://github.com/JamesWeatherhead/asq-phi)  
+69. MedQuAD: Medical Question-Answer Dataset \- Kaggle, accessed April 28, 2026, [https://www.kaggle.com/datasets/pythonafroz/medquad-medical-question-answer-for-ai-research](https://www.kaggle.com/datasets/pythonafroz/medquad-medical-question-answer-for-ai-research)  
+70. RealMedQA: A pilot biomedical question answering dataset containing realistic clinical questions \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC12099375/](https://pmc.ncbi.nlm.nih.gov/articles/PMC12099375/)  
+71. HIPAA Questions and Answers Relating to Research | Johns Hopkins Medicine, accessed April 28, 2026, [https://www.hopkinsmedicine.org/institutional-review-board/hipaa-research/faq-research](https://www.hopkinsmedicine.org/institutional-review-board/hipaa-research/faq-research)  
+72. Building a HIPAA-Compliant Healthcare Data Lake With Ceph Storage \- OpenMetal, accessed April 28, 2026, [https://openmetal.io/resources/blog/building-a-hipaa-compliant-healthcare-data-lake-with-ceph-storage/](https://openmetal.io/resources/blog/building-a-hipaa-compliant-healthcare-data-lake-with-ceph-storage/)  
+73. Advancing Compliance with HIPAA and GDPR in Healthcare: A Blockchain-Based Strategy for Secure Data Exchange in Clinical Research Involving Private Health Information \- PMC, accessed April 28, 2026, [https://pmc.ncbi.nlm.nih.gov/articles/PMC12563691/](https://pmc.ncbi.nlm.nih.gov/articles/PMC12563691/)  
+74. MSA K-BERT: A Method for Medical Text Intent Classification \- MDPI, accessed April 28, 2026, [https://www.mdpi.com/2076-3417/15/12/6834](https://www.mdpi.com/2076-3417/15/12/6834)  
+75. A Bespoke Question Intent Taxonomy for E-commerce \- Amazon Science, accessed April 28, 2026, [https://assets.amazon.science/4e/45/6130c9ea4752a48f4a78e13ceda4/a-bespoke-question-intent-taxonomy-for-e-commerce.pdf](https://assets.amazon.science/4e/45/6130c9ea4752a48f4a78e13ceda4/a-bespoke-question-intent-taxonomy-for-e-commerce.pdf)  
+76. Medical QA Oriented Multi-Task Learning Model for Question Intent Classification and Named Entity Recognition \- MDPI, accessed April 28, 2026, [https://www.mdpi.com/2078-2489/13/12/581](https://www.mdpi.com/2078-2489/13/12/581)  
+77. HIPAA Compliance Testing Services: 5 Best Strategies in 2026 \- QASource, accessed April 28, 2026, [https://www.qasource.com/blog/5-best-strategies-to-comply-with-hipaa-compliance-testing](https://www.qasource.com/blog/5-best-strategies-to-comply-with-hipaa-compliance-testing)  
+78. MedExQA: Medical Question Answering Benchmark with Multiple Explanations \- arXiv, accessed April 28, 2026, [https://arxiv.org/html/2406.06331v1](https://arxiv.org/html/2406.06331v1)
+
+[image1]: <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAAXCAYAAADduLXGAAAAoElEQVR4XmNgGJSAEYhV0QWxgadA/B+KiQJXGEhQDFJ4DV0QFwApjkAXxAaiGDCd0ATE/mhiYHCTAaGYC4jvAzEfEH+Dq0ACIIW3gVgQiDdCxX5CxTEASHAnEM9El0AHMxgQJsyGslUQ0qgAPTJA7INQdj6SOBiAJKeh8VuQ2HDACRUQRRL7CMQbgLgHiA2RxMHAE10ACDyAmANdcBTAAACQdCSKrBERiwAAAABJRU5ErkJggg==>
+
+[image2]: <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACwAAAAYCAYAAACBbx+6AAAA9ElEQVR4XmNgGAWjAC9gBGJVdMHBCp4C8X8oHgxAgIEIt1xhIEIRDYEoED9iQAQcQbeAFFxDFxwgQLSDI9AFBwgQdHAUA6aCJiD2RxOjFyDo4JsMCAVcQHwfiPmA+BtcBX0BQQeDJG8DsSAQb4SK/YSKDwQgysE7gXgmugQBoAvEJkRiHqgeYgBeB4MyGkjyKpTegyqNF7gBsR+RGFRsEQvwOvg6A6okiD0FiT8QAK+DQRLI5S+IvxLK/ogkTk9A0MFhaPxsBkjb4hiSOD0BTgeLMWBKgNIbSOwDmjg9AMjOZ0D8GIpB7IFwxygYBaNgFNADAACZw0t8+sbSQgAAAABJRU5ErkJggg==>
+
+[image3]: <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAYAAAAZCAYAAAASTF8GAAAAaElEQVR4XmNgoB9QB+LXQPwfiL+gyTEwQiWa0CUUoRLc6BILoRIYACT4C10QBEASbeiC8lAJLnSJ+VAJDHCfAYcESPAwuiAIgCRc0AVjoRIgkM4ACR4wKESS+AsThIGvDBBJc3SJIQIAAjoY/HXc2YoAAAAASUVORK5CYII=>

datasets-real-life/HIPAA_200_QA_Guide.md

@@ -0,0 +1,1590 @@
+# 🏥 HIPAA 200: The Definitive Q&A Guide for Healthcare Professionals (2026)
+
+This document contains 200 of the most frequent and critical HIPAA questions and answers encountered by healthcare staff, nurses, and administrators.
+
+## General
+
+**Q1: What does HIPAA stand for?**
+
+**A:** Health Insurance Portability and Accountability Act of 1996.
+
+---
+
+**Q2: What is the primary goal of the Privacy Rule?**
+
+**A:** To protect individuals' medical records and other personal health information.
+
+---
+
+**Q3: What is the primary goal of the Security Rule?**
+
+**A:** To protect electronic protected health information (ePHI) from unauthorized access or breaches.
+
+---
+
+**Q4: What is Protected Health Information (PHI)?**
+
+**A:** Any identifiable health information relating to past, present, or future physical/mental health, or payment.
+
+---
+
+**Q5: What are the 18 identifiers under HIPAA?**
+
+**A:** Names, geography (smaller than state), dates (except year), phone, fax, email, SSN, MRN, insurance IDs, account numbers, license numbers, vehicle IDs, device IDs, URLs, IP addresses, biometric identifiers, photos, and any other unique code.
+
+---
+
+**Q6: Who is a Covered Entity (CE)?**
+
+**A:** Healthcare providers, health plans, and healthcare clearinghouses that transmit health information electronically.
+
+---
+
+**Q7: Who is a Business Associate (BA)?**
+
+**A:** A person or entity that performs functions on behalf of a CE involving the use/disclosure of PHI (e.g., billing, IT, legal).
+
+---
+
+**Q8: What is a Business Associate Agreement (BAA)?**
+
+**A:** A contract that ensures BAs will appropriately safeguard PHI.
+
+---
+
+**Q9: What is the 'Minimum Necessary' Standard?**
+
+**A:** Entities must make reasonable efforts to limit PHI to the minimum amount necessary to accomplish the intended purpose.
+
+---
+
+**Q10: When does 'Minimum Necessary' NOT apply?**
+
+**A:** For treatment, disclosures to the patient, disclosures with valid authorization, or disclosures required by law.
+
+---
+
+**Q11: What is the Notice of Privacy Practices (NPP)?**
+
+**A:** A document describing how a CE uses and discloses PHI and explaining patient rights.
+
+---
+
+**Q12: What is Treatment, Payment, and Healthcare Operations (TPO)?**
+
+**A:** The three main reasons PHI can be used or shared without a patient’s specific written authorization.
+
+---
+
+**Q13: Does HIPAA apply to de-identified data?**
+
+**A:** No, once data is properly de-identified, it is no longer PHI.
+
+---
+
+**Q14: What are the two methods of de-identification?**
+
+**A:** The Expert Determination method and the Safe Harbor method.
+
+---
+
+**Q15: Can PHI be used for research without authorization?**
+
+**A:** Only if a waiver of authorization is granted by an IRB or Privacy Board, or if the data is a Limited Data Set.
+
+---
+
+**Q16: What is a Limited Data Set?**
+
+**A:** PHI that excludes direct identifiers but may include dates and geographic data larger than a street address.
+
+---
+
+**Q17: What is an 'Incident' under the Security Rule?**
+
+**A:** An attempted or successful unauthorized access, use, disclosure, modification, or destruction of information.
+
+---
+
+**Q18: What is the Breach Notification Rule?**
+
+**A:** A rule requiring CEs to notify individuals, the HHS, and sometimes the media when PHI is breached.
+
+---
+
+**Q19: What constitutes a 'breach'?**
+
+**A:** The acquisition, access, use, or disclosure of PHI in a manner not permitted by the Privacy Rule which compromises the security/privacy of the PHI.
+
+---
+
+**Q20: How long does a CE have to report a breach to individuals?**
+
+**A:** No later than 60 days after discovery.
+
+---
+
+## Workplace
+
+**Q21: Can I check my child's lab results in the EHR if I have access?**
+
+**A:** No. You must follow the same procedure as any other parent, usually via the patient portal.
+
+---
+
+**Q22: Can I tell a coworker about a patient's diagnosis just to 'vent'?**
+
+**A:** No. This is a violation as it is not for TPO purposes.
+
+---
+
+**Q23: Is it okay to leave a physical chart on a desk unattended?**
+
+**A:** No. PHI should be stored in a way that prevents unauthorized viewing (e.g., face down or in a folder).
+
+---
+
+**Q24: Can I discuss a patient in the hospital elevator?**
+
+**A:** No. Public spaces are prone to overhearing and are high-risk for violations.
+
+---
+
+**Q25: What should I do with printed PHI I no longer need?**
+
+**A:** It must be shredded or placed in a secure bin for destruction.
+
+---
+
+**Q26: Can patient names be on a whiteboard in the hallway?**
+
+**A:** Yes, but only if kept to a minimum (e.g., last name and room number) and necessary for care coordination.
+
+---
+
+**Q27: Can a nurse call out a patient's name in a waiting room?**
+
+**A:** Yes, this is an 'incidental disclosure' and is generally permitted.
+
+---
+
+**Q28: Are sign-in sheets allowed?**
+
+**A:** Yes, as long as they don't ask for sensitive info like 'reason for visit.'
+
+---
+
+**Q29: Can I look up my own medical records?**
+
+**A:** Generally no, most facility policies require you to use the patient portal or medical records office.
+
+---
+
+**Q30: What is 'Snooping'?**
+
+**A:** Accessing PHI without a clinical or administrative reason to do so.
+
+---
+
+**Q31: Is a 'password on a sticky note' a violation?**
+
+**A:** Yes. It is a failure of administrative and technical safeguards.
+
+---
+
+**Q32: Can I share my EHR login with a resident?**
+
+**A:** No. Every user must have their own unique identifier and credentials.
+
+---
+
+**Q33: If I find a lost thumb drive in the parking lot, should I plug it in to find the owner?**
+
+**A:** No. This is a security risk (malware/unauthorized PHI access). Give it to IT.
+
+---
+
+**Q34: Can I take a photo of a cool surgery for my personal portfolio?**
+
+**A:** No, unless you have explicit written patient consent and facility approval.
+
+---
+
+**Q35: Is it a violation if a patient sees a screen while I'm charting?**
+
+**A:** It is an incidental disclosure, but you should use privacy screens or angle the monitor away.
+
+---
+
+**Q36: Can I look up a celebrity's record if they are in the hospital?**
+
+**A:** No. This is one of the most common causes of high-profile HIPAA terminations.
+
+---
+
+**Q37: What happens if I accidentally look at the wrong patient's chart?**
+
+**A:** Close it immediately and report the error to your supervisor or privacy officer.
+
+---
+
+**Q38: Can I fax PHI?**
+
+**A:** Yes, but verify the recipient's fax number first and use a cover sheet.
+
+---
+
+**Q39: Can I leave PHI in my car?**
+
+**A:** Generally no. If unavoidable, it must be in a locked trunk or hidden and the car must be locked.
+
+---
+
+**Q40: Can I work on PHI while at a coffee shop?**
+
+**A:** No. Public Wi-Fi is insecure, and 'shoulder surfing' is a major risk.
+
+---
+
+## Rights
+
+**Q41: Do patients have the right to see their records?**
+
+**A:** Yes, under the Right of Access.
+
+---
+
+**Q42: Can a patient request a correction to their chart?**
+
+**A:** Yes, they have the right to request an amendment.
+
+---
+
+**Q43: If a doctor disagrees with a requested amendment, do they have to change it?**
+
+**A:** No, but they must document the request and provide a reason for the denial.
+
+---
+
+**Q44: How much can a facility charge for record copies?**
+
+**A:** Only a reasonable, cost-based fee for labor, supplies, and postage.
+
+---
+
+**Q45: Can a patient request to be contacted only on their cell phone?**
+
+**A:** Yes, patients have the right to request 'confidential communications.'
+
+---
+
+**Q46: Can a patient restrict their info from being shared with their insurer?**
+
+**A:** Yes, if they pay for the service in full out-of-pocket.
+
+---
+
+**Q47: Can a patient revoke an authorization?**
+
+**A:** Yes, at any time, though it doesn't apply to disclosures already made.
+
+---
+
+**Q48: What is an Accounting of Disclosures?**
+
+**A:** A report provided to a patient listing certain disclosures of their PHI made by the CE.
+
+---
+
+**Q49: Does the 'Accounting of Disclosures' include TPO?**
+
+**A:** Currently, the law does not require TPO disclosures to be in the accounting, though this has been debated.
+
+---
+
+**Q50: Can a parent always see their child's records?**
+
+**A:** Usually yes, but exceptions exist for minors who can consent to their own care (e.g., sexual health).
+
+---
+
+**Q51: Can a patient request their records in a digital format?**
+
+**A:** Yes, if the CE maintains them electronically and it is readily producible.
+
+---
+
+**Q52: Can a CE withhold records because the patient hasn't paid their bill?**
+
+**A:** No. This is a common violation of the Right of Access.
+
+---
+
+**Q53: What is the 'Cures Act' in relation to HIPAA?**
+
+**A:** It mandates 'Information Blocking' rules that facilitate easier patient access to their data.
+
+---
+
+**Q54: How many days does a CE have to respond to an amendment request?**
+
+**A:** 60 days.
+
+---
+
+**Q55: If a patient asks for records via unencrypted email, can you send them?**
+
+**A:** Yes, but only after warning them of the risks and documenting their preference.
+
+---
+
+**Q56: Can a patient's representative (Power of Attorney) access their records?**
+
+**A:** Yes, they stand in the shoes of the patient for HIPAA purposes.
+
+---
+
+**Q57: Do deceased individuals have HIPAA rights?**
+
+**A:** Yes, for 50 years after their death.
+
+---
+
+**Q58: Can a patient sue a provider directly for a HIPAA violation?**
+
+**A:** No, HIPAA does not have a 'private right of action.' They must file a complaint with the OCR.
+
+---
+
+**Q59: Can a patient opt-out of a facility directory?**
+
+**A:** Yes, they must be given the opportunity to object to being listed.
+
+---
+
+**Q60: What info is in a facility directory?**
+
+**A:** Name, location in facility, general condition, and religious affiliation (for clergy only).
+
+---
+
+## Tech
+
+**Q61: Is email secure for PHI?**
+
+**A:** Standard email is not. It must be encrypted to be HIPAA-compliant.
+
+---
+
+**Q62: What is Encryption?**
+
+**A:** The process of converting PHI into an unreadable format that requires a key to decipher.
+
+---
+
+**Q63: What is MFA?**
+
+**A:** Multi-Factor Authentication (e.g., password + text code).
+
+---
+
+**Q64: Is MFA required for remote access?**
+
+**A:** Yes, it is a standard safeguard for accessing ePHI from outside the network.
+
+---
+
+**Q65: Can I use Dropbox to store patient files?**
+
+**A:** Only if it is the Enterprise version and they have signed a BAA.
+
+---
+
+**Q66: Can I use Skype or FaceTime for telehealth?**
+
+**A:** Under current rules, you should use platforms that are HIPAA-compliant (e.g., Zoom for Healthcare).
+
+---
+
+**Q67: What is a Risk Analysis?**
+
+**A:** An ongoing process of identifying threats and vulnerabilities to ePHI.
+
+---
+
+**Q68: How often should passwords be changed?**
+
+**A:** HIPAA doesn't set a specific time, but policies should define a regular interval (e.g., 90 days).
+
+---
+
+**Q69: What is Malware?**
+
+**A:** Malicious software (viruses, ransomware) designed to damage or gain unauthorized access to a system.
+
+---
+
+**Q70: What is Ransomware?**
+
+**A:** A type of malware that locks files until a ransom is paid; it is usually considered a reportable breach.
+
+---
+
+**Q71: Is 'Auto-fill' for passwords allowed?**
+
+**A:** Generally discouraged in healthcare settings due to security risks.
+
+---
+
+**Q72: What are Audit Trails?**
+
+**A:** Logs that record who accessed what PHI and when.
+
+---
+
+**Q73: Can I use my personal phone for work emails?**
+
+**A:** Only if the device is managed (MDM) and encrypted by the organization.
+
+---
+
+**Q74: What is an 'Addressable' safeguard?**
+
+**A:** A safeguard that must be implemented if reasonable/appropriate, or an equivalent must be used.
+
+---
+
+**Q75: What is a 'Required' safeguard?**
+
+**A:** A safeguard that MUST be implemented exactly as stated (e.g., unique user IDs).
+
+---
+
+**Q76: Is cloud storage allowed under HIPAA?**
+
+**A:** Yes, provided there is a BAA and appropriate security controls.
+
+---
+
+**Q77: What happens to ePHI on a copier when it's sold?**
+
+**A:** The hard drive must be wiped or destroyed.
+
+---
+
+**Q78: What is Phishing?**
+
+**A:** Fraudulent emails used to trick staff into revealing passwords or installing malware.
+
+---
+
+**Q79: Are biometrics (fingerprints) considered PHI?**
+
+**A:** Yes, if they are used to identify a patient.
+
+---
+
+**Q80: Does HIPAA require data backups?**
+
+**A:** Yes, the Security Rule requires a data backup plan and disaster recovery plan.
+
+---
+
+## Disclosures
+
+**Q81: Can I give info to a patient's spouse?**
+
+**A:** Only if the patient agrees or doesn't object when given the chance.
+
+---
+
+**Q82: Can I give info to a patient's friend who is in the room?**
+
+**A:** Yes, it is implied consent if the patient doesn't object while the friend is present.
+
+---
+
+**Q83: What if the patient is unconscious and a family member asks for an update?**
+
+**A:** You may share info if, in your professional judgment, it is in the patient's best interest.
+
+---
+
+**Q84: Can I disclose PHI to a school?**
+
+**A:** Generally, you need written authorization from a parent/guardian.
+
+---
+
+**Q85: Can I report child abuse without consent?**
+
+**A:** Yes, HIPAA permits disclosures required by law for public health/safety.
+
+---
+
+**Q86: Can I report a gunshot wound to the police?**
+
+**A:** Yes, this is typically a disclosure required by state law.
+
+---
+
+**Q87: Can I share PHI with an employer?**
+
+**A:** Only with a specific written authorization from the employee (except for Workers' Comp).
+
+---
+
+**Q88: What is the 'Face-to-Face' exception for marketing?**
+
+**A:** A provider can recommend a product to a patient during a visit without it being 'marketing' under HIPAA.
+
+---
+
+**Q89: Can I share PHI with the media?**
+
+**A:** No, never without a specific written authorization from the patient.
+
+---
+
+**Q90: Can I share PHI for organ donation?**
+
+**A:** Yes, PHI can be shared with organ procurement organizations.
+
+---
+
+**Q91: Can I give info to a funeral director?**
+
+**A:** Yes, as necessary for them to carry out their duties.
+
+---
+
+**Q92: What is a 'Public Health Authority'?**
+
+**A:** An agency like the CDC or FDA to which you can report PHI for disease tracking or safety.
+
+---
+
+**Q93: Can I share PHI with law enforcement without a warrant?**
+
+**A:** Only in limited circumstances (e.g., identifying a suspect/victim, or emergencies).
+
+---
+
+**Q94: Can I share PHI with a jail/prison?**
+
+**A:** Yes, if necessary for the health/safety of the inmate or others.
+
+---
+
+**Q95: Do I need authorization to share info for a Workers' Comp claim?**
+
+**A:** No, PHI can be shared as authorized by state workers' comp laws.
+
+---
+
+**Q96: Can I tell a patient's family about their death?**
+
+**A:** Yes, unless it is known to be against the patient's prior expressed wishes.
+
+---
+
+**Q97: Can I tell a pastor about a parishioner's surgery?**
+
+**A:** Only if the patient is in the facility directory and listed their religion.
+
+---
+
+**Q98: Can I send a 'get well' card from the staff?**
+
+**A:** Yes, provided the PHI used is limited to the name and location for a friendly gesture.
+
+---
+
+**Q99: Can I call a patient to remind them of an appointment?**
+
+**A:** Yes, this is part of healthcare operations.
+
+---
+
+**Q100: Can I leave an appointment reminder on a voicemail?**
+
+**A:** Yes, but keep the information minimal (name, date, time, clinic).
+
+---
+
+## Penalties
+
+**Q101: Who enforces HIPAA?**
+
+**A:** The Office for Civil Rights (OCR) within the Department of Health and Human Services (HHS).
+
+---
+
+**Q102: What are the four 'Tiers' of HIPAA violations?**
+
+**A:** 1. Unknowing, 2. Reasonable Cause, 3. Willful Neglect (Corrected), 4. Willful Neglect (Uncorrected).
+
+---
+
+**Q103: What is the maximum fine for a HIPAA violation in a year?**
+
+**A:** Approximately $2 million (inflation-adjusted).
+
+---
+
+**Q104: Can you go to jail for a HIPAA violation?**
+
+**A:** Yes, for criminal violations like selling PHI or intentional theft.
+
+---
+
+**Q105: What is the 'Wall of Shame'?**
+
+**A:** The OCR's public website listing all breaches affecting 500+ individuals.
+
+---
+
+**Q106: Are state attorneys general allowed to enforce HIPAA?**
+
+**A:** Yes, they can bring civil actions on behalf of state residents.
+
+---
+
+**Q107: Is a 'good faith' mistake still a violation?**
+
+**A:** Technically yes, but it usually results in Tier 1 (low/no fine) and corrective action.
+
+---
+
+**Q108: What is a Compliance Review?**
+
+**A:** An investigation by OCR to determine if a CE is following HIPAA rules.
+
+---
+
+**Q109: Can a nurse lose their license over HIPAA?**
+
+**A:** Yes, state licensing boards can take action based on privacy violations.
+
+---
+
+**Q110: Does firing the employee fix the HIPAA violation?**
+
+**A:** It is part of the mitigation, but the entity may still be liable for failing to train/supervise.
+
+---
+
+**Q111: Is it a violation if a hacker steals data despite good security?**
+
+**A:** It depends on whether the CE was compliant with the Security Rule prior to the attack.
+
+---
+
+**Q112: What is 'Safe Harbor' for breaches?**
+
+**A:** If the stolen data was encrypted (according to HHS standards), it is generally NOT considered a breach.
+
+---
+
+**Q113: Who must be notified if 500+ people are affected by a breach?**
+
+**A:** The affected individuals, the HHS, and prominent media outlets.
+
+---
+
+**Q114: Who must be notified if <500 people are affected?**
+
+**A:** The individuals and the HHS (via an annual log).
+
+---
+
+**Q115: What is the 'harm threshold'?**
+
+**A:** A risk assessment used to determine if an incident is a reportable breach based on the probability PHI was compromised.
+
+---
+
+**Q116: How long should HIPAA training records be kept?**
+
+**A:** 6 years is the standard retention period for HIPAA documentation.
+
+---
+
+**Q117: What is the 'Statute of Limitations' for HIPAA complaints?**
+
+**A:** 180 days from when the person knew (or should have known) of the violation.
+
+---
+
+**Q118: Can employees be whistleblowers?**
+
+**A:** Yes, employees can report violations to OCR without fear of legal retaliation from a HIPAA perspective.
+
+---
+
+**Q119: Is sharing PHI on social media a criminal offense?**
+
+**A:** It can be if there is 'malicious intent' or 'personal gain.'
+
+---
+
+**Q120: Do penalties apply to Business Associates?**
+
+**A:** Yes, BAs are directly liable for many HIPAA requirements since 2013.
+
+---
+
+## Specialized
+
+**Q121: Are Psychotherapy Notes handled differently?**
+
+**A:** Yes, they require a separate authorization for almost all uses and disclosures.
+
+---
+
+**Q122: What are 'Psychotherapy Notes'?**
+
+**A:** Notes by a mental health professional documenting a conversation during a session, kept separate from the rest of the medical record.
+
+---
+
+**Q123: What is 42 CFR Part 2?**
+
+**A:** Federal regulations protecting the confidentiality of substance use disorder (SUD) patient records.
+
+---
+
+**Q124: Has Part 2 been aligned with HIPAA?**
+
+**A:** Yes, the 2024/2026 updates align Part 2 more closely with HIPAA for TPO purposes.
+
+---
+
+**Q125: Can you share SUD info for an overdose emergency?**
+
+**A:** Yes, to medical personnel who have a need for the information to treat a condition.
+
+---
+
+**Q126: Can a 16-year-old consent to mental health treatment without parents?**
+
+**A:** This depends on state law; HIPAA defers to state law for minor consent.
+
+---
+
+**Q127: If a minor consents to their own care, can the parent see the record?**
+
+**A:** No, under HIPAA, the minor is the 'individual' and the parent is generally not the personal representative for that care.
+
+---
+
+**Q128: Can PHI be shared with a school nurse?**
+
+**A:** Only with written parent/guardian authorization (HIPAA) or under FERPA rules.
+
+---
+
+**Q129: Is DNA/Genetic info PHI?**
+
+**A:** Yes, and it is also protected by GINA (Genetic Information Nondiscrimination Act).
+
+---
+
+**Q130: Can insurers use genetic info to deny coverage?**
+
+**A:** No, GINA prohibits this for health insurance.
+
+---
+
+**Q131: What is 'Marketing' under HIPAA?**
+
+**A:** A communication about a product or service that encourages the recipient to purchase or use it.
+
+---
+
+**Q132: Does marketing require authorization?**
+
+**A:** Yes, if the CE receives payment (remuneration) from a third party for the communication.
+
+---
+
+**Q133: Can I send a newsletter to all patients about new services?**
+
+**A:** Yes, this is generally considered 'Healthcare Operations' rather than marketing.
+
+---
+
+**Q134: Can a CE sell PHI?**
+
+**A:** Generally no, unless it is for a permitted purpose (like a merger) or with explicit patient authorization.
+
+---
+
+**Q135: Can I use PHI for fundraising?**
+
+**A:** Yes, but you must include a clear way for patients to opt-out of future fundraising.
+
+---
+
+**Q136: What PHI can be used for fundraising?**
+
+**A:** Demographic info and dates of service only.
+
+---
+
+**Q137: Does HIPAA protect info in an employment file?**
+
+**A:** No, info in employment records held by a CE in its role as an employer is not PHI.
+
+---
+
+**Q138: Can a provider talk to a patient's employer about their sick leave?**
+
+**A:** No, not without authorization.
+
+---
+
+**Q139: Is the 'Notice of Privacy Practices' required in the lobby?**
+
+**A:** Yes, it must be prominently posted and available for patients to take.
+
+---
+
+**Q140: Must the NPP be on the website?**
+
+**A:** Yes, if the CE has a website.
+
+---
+
+## Security
+
+**Q141: What is a Physical Safeguard?**
+
+**A:** Measures to protect physical buildings and equipment (e.g., locks, badges).
+
+---
+
+**Q142: What is an Administrative Safeguard?**
+
+**A:** Policies and procedures to manage security (e.g., training, risk analysis).
+
+---
+
+**Q143: What is a Technical Safeguard?**
+
+**A:** Technology and policy protecting ePHI access (e.g., encryption, audit logs).
+
+---
+
+**Q144: Are 'Workstation Security' rules required?**
+
+**A:** Yes, CEs must implement physical safeguards for all workstations that access ePHI.
+
+---
+
+**Q145: Is 'Automatic Log-off' required?**
+
+**A:** It is an addressable safeguard, but highly recommended in clinical settings.
+
+---
+
+**Q146: What is 'Integrity' in the Security Rule?**
+
+**A:** Ensuring that ePHI is not altered or destroyed in an unauthorized manner.
+
+---
+
+**Q147: What is 'Availability' in the Security Rule?**
+
+**A:** Ensuring that ePHI is accessible and usable on demand by an authorized person.
+
+---
+
+**Q148: What is 'Access Control'?**
+
+**A:** Technical policies that allow only authorized persons to access ePHI.
+
+---
+
+**Q149: What are 'Transmission Security' rules?**
+
+**A:** Measures to guard against unauthorized access to ePHI being transmitted over a network.
+
+---
+
+**Q150: Do I need to encrypt my office's internal Wi-Fi?**
+
+**A:** Yes, the Security Rule requires protecting data in transit.
+
+---
+
+**Q151: Can I use a personal USB drive for work?**
+
+**A:** Most healthcare IT policies forbid this to prevent data leakage and malware.
+
+---
+
+**Q152: What is a 'Security Officer'?**
+
+**A:** A designated person responsible for the development and implementation of security policies.
+
+---
+
+**Q153: What is a 'Privacy Officer'?**
+
+**A:** A designated person responsible for ensuring compliance with the Privacy Rule.
+
+---
+
+**Q154: Can one person be both Privacy and Security Officer?**
+
+**A:** Yes, especially in smaller practices.
+
+---
+
+**Q155: How often should staff receive HIPAA training?**
+
+**A:** HIPAA requires training for all new staff and 'periodically' thereafter (usually annually).
+
+---
+
+**Q156: What is a 'Sanction Policy'?**
+
+**A:** A policy that outlines the consequences for staff who violate HIPAA (e.g., warning, firing).
+
+---
+
+**Q157: What is 'Data Disposal'?**
+
+**A:** The process of permanently removing PHI from electronic media.
+
+---
+
+**Q158: Can I reuse a computer hard drive?**
+
+**A:** Only if it has been wiped using software that meets NIST standards.
+
+---
+
+**Q159: What is an 'Emergency Access' procedure?**
+
+**A:** A way for staff to get into a system during a disaster (often called 'break-glass' access).
+
+---
+
+**Q160: Are smartwatches/wearables HIPAA compliant?**
+
+**A:** The devices themselves are just tools; the app and data handling must be HIPAA compliant if used for PHI.
+
+---
+
+## BA
+
+**Q161: If a shredding company loses my files, who is responsible?**
+
+**A:** Both the CE (for not vetting the BA) and the BA (directly under HIPAA).
+
+---
+
+**Q162: Does a janitorial service need a BAA?**
+
+**A:** Generally no, unless their work involves routine access to PHI.
+
+---
+
+**Q163: Does the Post Office need a BAA?**
+
+**A:** No, they are considered 'conduits' and are exempt.
+
+---
+
+**Q164: Does an ISP (Internet Service Provider) need a BAA?**
+
+**A:** No, they are also considered conduits.
+
+---
+
+**Q165: Does a cloud service provider (like AWS) need a BAA?**
+
+**A:** Yes, because they store PHI even if they don't look at it.
+
+---
+
+**Q166: Is a BAA required for a lawyer representing the clinic?**
+
+**A:** Yes, if they will have access to PHI.
+
+---
+
+**Q167: Can a BA be fined by the OCR?**
+
+**A:** Yes, they have been directly liable since the Omnibus Rule of 2013.
+
+---
+
+**Q168: What if a BA refuses to sign a BAA?**
+
+**A:** The CE should not work with them or share any PHI with them.
+
+---
+
+**Q169: Does a consultant who sees PHI need a BAA?**
+
+**A:** Yes.
+
+---
+
+**Q170: Is a BA responsible for their subcontractors?**
+
+**A:** Yes, the BA must ensure their subcontractors also follow HIPAA via a contract.
+
+---
+
+## Communication
+
+**Q171: Can I use a pager for PHI?**
+
+**A:** Standard pagers are unencrypted; only 'Secure Paging' apps are truly compliant.
+
+---
+
+**Q172: Can I text a patient?**
+
+**A:** Only if they have consented to text and you use a secure platform.
+
+---
+
+**Q173: Can I use a whiteboard in the OR?**
+
+**A:** Yes, it is necessary for surgical safety and TPO.
+
+---
+
+**Q174: Can I announce a patient's name over the PA system?**
+
+**A:** Yes, but keep it to the minimum (e.g., 'John Doe, please come to the front').
+
+---
+
+**Q175: Is it okay to use a translation app on my phone for PHI?**
+
+**A:** Only if the app has a BAA and doesn't store data on its servers.
+
+---
+
+**Q176: Can I email a referral to another doctor?**
+
+**A:** Only via a secure, encrypted email system.
+
+---
+
+**Q177: Can I use a shared office computer?**
+
+**A:** Yes, provided you log out after every session and use a unique login.
+
+---
+
+**Q178: What is 'Shoulder Surfing'?**
+
+**A:** Looking over someone's shoulder to see PHI on a screen.
+
+---
+
+**Q179: Are privacy screens required?**
+
+**A:** They are an addressable safeguard used to mitigate risk in high-traffic areas.
+
+---
+
+**Q180: Can I talk to a patient about their HIV status in a semi-private room?**
+
+**A:** You must take reasonable precautions (pull curtains, speak softly) to maintain privacy.
+
+---
+
+## Misc
+
+**Q181: Does HIPAA protect me from my boss seeing my medical leave?**
+
+**A:** No, the boss sees the leave request; but they shouldn't see the underlying chart without authorization.
+
+---
+
+**Q182: Is 'Death' a reason PHI is no longer protected?**
+
+**A:** No, it stays protected for 50 years.
+
+---
+
+**Q183: Does HIPAA apply to life insurance companies?**
+
+**A:** No, they are not Covered Entities.
+
+---
+
+**Q184: Does HIPAA apply to the DMV?**
+
+**A:** No.
+
+---
+
+**Q185: Does HIPAA apply to schools?**
+
+**A:** Generally no, records are usually covered by FERPA.
+
+---
+
+**Q186: Is it a HIPAA violation if a patient sees another patient's name on a label?**
+
+**A:** It depends on the context; usually an 'incidental disclosure' if reasonable steps were taken.
+
+---
+
+**Q187: Can I disclose PHI to prevent a serious threat to health/safety?**
+
+**A:** Yes, this is the 'Duty to Warn' exception.
+
+---
+
+**Q188: Can I use PHI for training medical students?**
+
+**A:** Yes, this is part of 'Healthcare Operations.'
+
+---
+
+**Q189: Does HIPAA apply to gym memberships?**
+
+**A:** No.
+
+---
+
+**Q190: Does HIPAA apply to DNA testing sites (like 23andMe)?**
+
+**A:** Generally no, unless they are acting as a provider/health plan.
+
+---
+
+## Specific
+
+**Q191: Can I give PHI to a researcher after a patient has died?**
+
+**A:** Yes, if the researcher represents that the PHI is for research on decedents.
+
+---
+
+**Q192: What is the '6-year rule'?**
+
+**A:** Most HIPAA-related documentation (authorizations, NPP, training logs) must be kept for 6 years.
+
+---
+
+**Q193: Can a provider refuse to give a patient their records if they think it will harm them?**
+
+**A:** Only in very narrow cases regarding 'Psychotherapy Notes' or if a professional believes it would cause life-threatening harm.
+
+---
+
+**Q194: What is 'Red Flag' Rule?**
+
+**A:** An FTC rule requiring identity theft prevention programs (often grouped with HIPAA).
+
+---
+
+**Q195: Is a patient's room number PHI?**
+
+**A:** Yes.
+
+---
+
+**Q196: Is a patient's date of birth PHI?**
+
+**A:** Yes.
+
+---
+
+**Q197: Is 'Male' or 'Female' PHI?**
+
+**A:** By itself, no; but when combined with other data, it can be part of PHI.
+
+---
+
+**Q198: Can I mention a patient's initials?**
+
+**A:** Initials can sometimes be used to identify someone, so they should be treated carefully.
+
+---
+
+**Q199: What is the 'Safe Harbor' de-identification list?**
+
+**A:** The list of 18 identifiers that must be removed.
+
+---
+
+**Q200: Can I use PHI in a lawsuit for unpaid bills?**
+
+**A:** Yes, but only the minimum necessary to collect payment.
+
+---
+
+**Q201: Who does a patient complain to about a HIPAA violation?**
+
+**A:** The HHS Office for Civil Rights (OCR).
+
+---
+
+**Q202: Can I charge for 'search and retrieval' of records?**
+
+**A:** Under federal law, generally no for the patient; you can only charge for the copies/labor.
+
+---
+
+**Q203: Is 'Identity Theft' a HIPAA violation?**
+
+**A:** If it involves PHI, yes.
+
+---
+
+**Q204: What is a 'Privacy Board'?**
+
+**A:** A group that reviews research requests involving PHI, similar to an IRB.
+
+---
+
+**Q205: Can a CE provide PHI to a 'Health Information Exchange' (HIE)?**
+
+**A:** Yes, for TPO purposes, often subject to state 'opt-out' rules.
+
+---
+
+**Q206: Is a 'Limited Data Set' the same as 'De-identified'?**
+
+**A:** No, a Limited Data Set still has some dates/geography and requires a 'Data Use Agreement.'
+
+---
+
+**Q207: What is a 'Data Use Agreement'?**
+
+**A:** A contract for using a Limited Data Set.
+
+---
+
+**Q208: Can I tell a patient's employer about their positive drug test?**
+
+**A:** Only if the drug test was part of a workplace program and the patient authorized it.
+
+---
+
+**Q209: Can a provider use an unencrypted laptop?**
+
+**A:** Only if there is no PHI on it; if it has PHI, it must be encrypted.
+
+---
+
+**Q210: Can I send PHI via a web portal?**
+
+**A:** Yes, if the portal is secure and encrypted.
+
+---
+
+## Final
+
+**Q211: Is it a violation to discuss a patient case during 'Grand Rounds'?**
+
+**A:** No, this is healthcare operations/training.
+
+---
+
+**Q212: Can I post a picture of a patient's wound (no face) on a medical forum?**
+
+**A:** Only if it is fully de-identified OR you have authorization.
+
+---
+
+**Q213: What is 'Minimum Necessary' in a medical emergency?**
+
+**A:** It does not apply; provide all info needed to save the life.
+
+---
+
+**Q214: Does HIPAA require an 'opt-out' for the hospital gift shop?**
+
+**A:** No, but the shop should not have access to PHI.
+
+---
+
+**Q215: Is a patient's voice recording PHI?**
+
+**A:** Yes.
+
+---
+
+**Q216: Can I give PHI to a patient's lawyer?**
+
+**A:** Only with a signed patient authorization.
+
+---
+
+**Q217: Can I give PHI to a court in response to a subpoena?**
+
+**A:** Yes, but there are specific steps to follow (e.g., notice to patient or protective order).
+
+---
+
+**Q218: Is a court order the same as a subpoena?**
+
+**A:** No; a court order signed by a judge must be followed immediately.
+
+---
+
+**Q219: What is a 'Subpoena duces tecum'?**
+
+**A:** A request for the production of documents (medical records).
+
+---
+
+**Q220: Can I tell a mother her 20-year-old daughter is in the ER?**
+
+**A:** Yes, if the daughter doesn't object, or if it is an emergency and in her best interest.
+
+---
+
+**Q221: Does HIPAA apply to military records?**
+
+**A:** Yes, but with specific 'Military Command' exceptions.
+
+---
+
+**Q222: Can I look up my neighbor's address in the EHR to send them a party invite?**
+
+**A:** No. This is snooping.
+
+---
+
+**Q223: What is 'Disaster Recovery'?**
+
+**A:** Restoring ePHI and systems after a flood, fire, or cyberattack.
+
+---
+
+**Q224: Is 'Offsite Storage' of backups required?**
+
+**A:** It is an addressable safeguard, but highly recommended.
+
+---
+
+**Q225: Can I use my personal iPad for charting?**
+
+**A:** Only if authorized and secured by your facility.
+
+---
+
+**Q226: What is 'Social Engineering'?**
+
+**A:** Psychological manipulation of staff to reveal PHI or passwords.
+
+---
+
+**Q227: Are medical records on microfilm protected?**
+
+**A:** Yes, HIPAA applies to all formats: paper, electronic, and oral.
+
+---
+
+**Q228: Can I leave PHI on a printer?**
+
+**A:** No. Pick it up immediately.
+
+---
+
+**Q229: Can I share PHI with the Social Security Administration?**
+
+**A:** Yes, with authorization for disability claims.
+
+---
+
+**Q230: Is 'Curiosity' a valid reason to access PHI?**
+
+**A:** Never.
+
+---
+
+**Q231: Can a doctor take their patients' charts when they leave a practice?**
+
+**A:** It depends on their contract, but the CE's privacy policies still apply.
+
+---
+
+**Q232: Can I email a patient's lab results to their personal Gmail?**
+
+**A:** Only if you follow the warning/consent process.
+
+---
+
+**Q233: Does HIPAA apply to COVID-19 vaccination status?**
+
+**A:** Yes, if the record is held by a healthcare provider.
+
+---
+
+**Q234: Can an employer ask for a doctor's note?**
+
+**A:** Yes, but the doctor should only provide the minimum necessary info (e.g., duration of leave).
+
+---
+
+**Q235: Is a 'Privacy Shield' the same as HIPAA?**
+
+**A:** No, that relates to EU-US data transfers.
+
+---
+
+**Q236: Does HIPAA cover dental records?**
+
+**A:** Yes.
+
+---
+
+**Q237: Does HIPAA cover vision records?**
+
+**A:** Yes.
+
+---
+
+**Q238: Does HIPAA cover pharmacy records?**
+
+**A:** Yes.
+
+---
+
+**Q239: Does HIPAA cover health insurance premiums info?**
+
+**A:** Yes.
+
+---
+
+**Q240: What is the 'Privacy Rule' of 2000?**
+
+**A:** The original rule that established PHI protections.
+
+---
+
+**Q241: What is the 'Omnibus Rule' of 2013?**
+
+**A:** The update that significantly expanded HIPAA to Business Associates and increased penalties.
+
+---
+
+**Q242: Can I discuss a patient with my spouse?**
+
+**A:** No.
+
+---
+
+**Q243: Is a patient's ZIP code PHI?**
+
+**A:** Yes, if it's the full ZIP or for a small population area.
+
+---
+
+**Q244: Is 'Patient 123' a de-identified name?**
+
+**A:** Only if '123' is a random code and not derived from PHI (like last 3 of SSN).
+
+---
+
+**Q245: Can I help a patient's daughter understand her mother's medications?**
+
+**A:** Yes, if the mother agrees or it is helpful for the mother's care.
+
+---
+
+**Q246: Is 'Oral PHI' protected?**
+
+**A:** Yes.
+
+---
+
+**Q247: Can I look up my ex-partner's records?**
+
+**A:** No. This is a severe violation.
+
+---
+
+**Q248: What is 'Self-Reporting'?**
+
+**A:** When an entity discovers their own violation and reports it to the OCR to show good faith.
+
+---
+
+**Q249: Can a doctor share PHI with another doctor for a second opinion?**
+
+**A:** Yes, this is 'Treatment.'
+
+---
+
+**Q250: What is the 'Health Breach Notification Rule' from the FTC?**
+
+**A:** It applies to vendors of personal health records (like apps) not covered by HIPAA.
+
+---
+
+**Q251: Can I use 'Slack' for PHI?**
+
+**A:** Only if it is the Enterprise Grid version with a BAA.
+
+---
+
+**Q252: Can I use 'WhatsApp' for PHI?**
+
+**A:** No, it is generally not considered HIPAA compliant for professional healthcare use.
+
+---
+
+**Q253: What is 'Audit Log Management'?**
+
+**A:** Regularly reviewing logs to check for unauthorized access.
+
+---
+
+**Q254: Can I share PHI with the Red Cross during a disaster?**
+
+**A:** Yes, for coordinating relief efforts.
+
+---
+
+**Q255: Can I share PHI with a threat intelligence agency?**
+
+**A:** Yes, for cybersecurity purposes under certain conditions.
+
+---
+
+**Q256: Does HIPAA cover workers' compensation insurers?**
+
+**A:** No, they are generally not CEs, but they can receive PHI to process claims.
+
+---
+
+**Q257: Is a 'Notice of Privacy Practices' a contract?**
+
+**A:** No, it is a notice of the patient's rights and the CE's duties.
+
+---
+
+**Q258: Can I look up why my friend was admitted?**
+
+**A:** No.
+
+---
+
+**Q259: Can I take a patient's picture to track wound healing?**
+
+**A:** Yes, for treatment, but keep it in the secure clinical system.
+
+---
+
+**Q260: Can I print a list of my patients for the day?**
+
+**A:** Yes, but keep it secure and shred it at the end of the shift.
+
+---
+

datasets/01-hipaa-privacy-rule.md

@@ -0,0 +1,203 @@
+# HIPAA Privacy Rule — Comprehensive Dataset
+
+**Source:** 45 CFR Part 160 and Subparts A and E of Part 164  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/privacy/index.html
+
+---
+
+## 1. Overview
+
+The HIPAA Privacy Rule establishes the national baseline for protecting individuals' medical records and other individually identifiable health information. This information is collectively termed **Protected Health Information (PHI)**.
+
+PHI includes any demographic data relating to an individual's:
+
+- Past, present, or future physical or mental health condition
+- Provision of health care to the individual
+- Past, present, or future payment for the provision of health care
+
+PHI applies to information held or transmitted in **any form** — electronic, paper, or oral.
+
+---
+
+## 2. Covered Entities Subject to the Privacy Rule
+
+The Privacy Rule applies explicitly to the following **covered entities**:
+
+| Entity Type                    | Description                                                                                                        |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
+| **Health Plans**               | Insurance companies, HMOs, Medicare, Medicaid, employer-sponsored health plans                                     |
+| **Health Care Clearinghouses** | Entities that process health information between standard and non-standard formats                                 |
+| **Health Care Providers**      | Providers who conduct covered health care transactions electronically (hospitals, clinics, physicians, pharmacies) |
+
+---
+
+## 3. Core Restrictions on Use and Disclosure of PHI
+
+Covered entities are legally mandated to implement appropriate safeguards and are heavily restricted in how they may disclose PHI without an individual's prior, explicitly documented authorization.
+
+### 3.1 Permitted Disclosures (No Authorization Required)
+
+| Permitted Use / Disclosure                  | Operational Context                                                                                   |
+| ------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| **To the Individual**                       | The patient themselves always has a right to their own PHI                                            |
+| **Treatment, Payment, Operations (TPO)**    | Health care providers may share PHI for treatment purposes without separate authorization             |
+| **Required by Law**                         | Disclosures required by statute, regulation, or court order — must be logged and audited              |
+| **Public Health Activities**                | Reporting to public health authorities for disease surveillance, injury reporting, FDA product safety |
+| **Health Oversight Activities**             | Government audits, investigations, inspections of covered entities                                    |
+| **Judicial and Administrative Proceedings** | Court orders, subpoenas (with individual notification or protective order)                            |
+| **Law Enforcement**                         | Limited purposes with proper legal process                                                            |
+| **Decedents**                               | Coroners, medical examiners, funeral directors                                                        |
+| **Research**                                | With proper IRB/Privacy Board waiver and data use agreements                                          |
+| **Serious Threat to Health or Safety**      | To avert a serious and imminent threat                                                                |
+| **Limited Data Sets**                       | With direct identifiers removed and a data use agreement in place                                     |
+
+### 3.2 Disclosures Requiring Individual Authorization
+
+The following types of disclosures always require a valid, written individual authorization:
+
+- Most uses and disclosures of **psychotherapy notes**
+- Uses and disclosures of PHI for **marketing purposes** (with limited exceptions)
+- **Sale of PHI**
+- Uses and disclosures not otherwise permitted by the Privacy Rule
+
+---
+
+## 4. Minimum Necessary Standard
+
+The Privacy Rule dictates the implementation of the **"Minimum Necessary"** standard. This principle requires that any disclosure of PHI be strictly limited to the minimum amount of information necessary to accomplish the intended purpose.
+
+**Technical engineering implications:**
+
+- Prompt minimization in AI/LLM pipelines
+- Dynamic token-filtering before LLM context windows
+- Least-privilege access controls at the API layer
+- Role-Based Access Control (RBAC) per job function
+- Scoped database queries — never `SELECT *` on PHI tables
+
+### Exceptions to Minimum Necessary Standard:
+
+1. Disclosures to or requests by a health care provider for treatment
+2. Disclosures to the individual who is the subject of the information
+3. Uses or disclosures made pursuant to an individual's authorization
+4. Disclosures to HHS for compliance investigations
+5. Uses or disclosures required by law
+
+---
+
+## 5. Individual Rights Under the Privacy Rule
+
+| Right                                    | Description                                                                      | Technical Implementation Required                  |
+| ---------------------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------- |
+| **Right to Access**                      | Examine and obtain a copy of health records (electronic or paper) within 30 days | Patient portal with secure download, audit logging |
+| **Right to Direct Transmission**         | Request covered entity to transmit ePHI to a designated third party              | API integration with secure token-based auth       |
+| **Right to Amend**                       | Request corrections to inaccurate or incomplete PHI                              | Edit request workflow with audit trail             |
+| **Right to Accounting of Disclosures**   | Receive a list of disclosures made in the past 6 years                           | Disclosure logging system                          |
+| **Right to Request Restrictions**        | Request limitations on how PHI is used or disclosed                              | Override flags in patient record                   |
+| **Right to Confidential Communications** | Request communication via alternative means (e.g., different address or phone)   | Preference system in patient profile               |
+| **Right to Receive Notice**              | Receive a Notice of Privacy Practices (NPP)                                      | NPP document, acknowledgment workflow              |
+| **Right to Opt Out of Fundraising**      | Opt out of fundraising communications                                            | Opt-out flag in CRM systems                        |
+
+---
+
+## 6. Notice of Privacy Practices (NPP)
+
+Every covered entity must provide individuals with a written Notice of Privacy Practices that explains:
+
+- How their PHI may be used and disclosed
+- Their rights under the Privacy Rule
+- The covered entity's legal duties
+
+**When NPP must be provided:**
+
+- At time of first service delivery
+- Upon request at any time
+- Posted prominently on websites if the entity has one
+- Sent by email if the individual agrees to electronic notice
+
+---
+
+## 7. Authorization Requirements
+
+A valid HIPAA authorization must contain all of the following elements:
+
+1. A description of the PHI to be used or disclosed, identifying the information in a specific and meaningful manner
+2. The name(s) of the person(s) or class of persons authorized to make the requested use or disclosure
+3. The name(s) of the person(s) or class of persons to whom the covered entity may make the requested use or disclosure
+4. A description of each purpose of the requested use or disclosure
+5. An expiration date or expiration event
+6. The individual's signature and date
+7. If signed by a personal representative, a description of their authority to act
+
+**An authorization is not valid if:**
+
+- The expiration date has passed
+- It was not filled out completely
+- The covered entity knows it has been revoked
+- Defective (e.g., contains prohibited conditions on treatment)
+
+---
+
+## 8. Business Associate Relationship Under Privacy Rule
+
+A **Business Associate** is any person or entity that performs functions or activities on behalf of a covered entity that involve the use or disclosure of PHI. The Privacy Rule requires covered entities to have a **Business Associate Agreement (BAA)** with each business associate.
+
+The BAA must:
+
+- Establish permitted uses and disclosures of PHI
+- Require appropriate safeguards
+- Require reporting of breaches
+- Ensure the business associate will return or destroy PHI at contract termination
+
+---
+
+## 9. Key Privacy Rule Definitions
+
+| Term                                             | Definition                                                                                                                                                                     |
+| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Protected Health Information (PHI)**           | Individually identifiable health information held or transmitted by a covered entity or business associate in any form                                                         |
+| **Individually Identifiable Health Information** | Information that identifies or could be used to identify the individual                                                                                                        |
+| **De-identified Information**                    | Health information that does not identify an individual and there is no reasonable basis to believe it can be used to identify an individual — not subject to the Privacy Rule |
+| **Limited Data Set**                             | PHI with specified direct identifiers removed, used under a data use agreement                                                                                                 |
+| **Covered Entity**                               | Health plan, health care clearinghouse, or health care provider conducting electronic transactions                                                                             |
+| **Business Associate**                           | Person or entity performing functions involving PHI on behalf of a covered entity                                                                                              |
+| **Treatment**                                    | Provision, coordination, or management of health care                                                                                                                          |
+| **Payment**                                      | Activities to obtain reimbursement for health care                                                                                                                             |
+| **Health Care Operations**                       | Administrative, financial, legal, and quality improvement activities                                                                                                           |
+
+---
+
+## 10. Enforcement
+
+- HHS Office for Civil Rights (OCR) enforces the Privacy Rule
+- Individuals cannot directly sue under HIPAA; enforcement is administrative
+- Civil penalties range from $100 to $50,000 per violation, capped at $1.9 million per violation category per year
+- Criminal penalties apply to willful violations (up to $250,000 and 10 years imprisonment)
+- State attorneys general may bring civil actions on behalf of state residents
+
+---
+
+## 11. Frequently Cited Privacy Rule Violations
+
+1. Impermissible uses and disclosures of PHI
+2. Lack of safeguards for PHI
+3. Failure to provide patients access to their PHI within the required timeframe
+4. Using or disclosing more than the minimum necessary PHI
+5. Lack of administrative safeguards for electronic PHI
+6. Failure to enter into Business Associate Agreements
+7. No procedures to address patient complaints
+8. Failure to provide employees training on Privacy Rule policies
+
+---
+
+## Supplementary Ingestion Sources
+
+For a production RAG agent, supplement this dataset with direct ingestion of:
+
+- **[ecfr.gov](https://www.ecfr.gov/current/title-45/parts-160-164)** — 45 CFR Parts 160, 162, 164 (full verbatim regulatory text)
+- **[hhs.gov/hipaa/for-professionals](https://www.hhs.gov/hipaa/for-professionals/index.html)** — Official HHS guidance and FAQ pages
+- **[OCR Resolution Agreements](https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/index.html)** — Case precedent from enforcement settlements
+
+---
+
+**Related Datasets:** `02-hipaa-security-rule.md`, `06-phi-definitions-identifiers.md`, `07-patient-rights.md`, `05-business-associates.md`, `18-minimum-necessary-standard.md`

datasets/02-hipaa-security-rule.md

@@ -0,0 +1,247 @@
+# HIPAA Security Rule — Comprehensive Dataset
+
+**Source:** 45 CFR Part 164, Subparts A and C  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**Published:** Final Rule February 2003  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/security/index.html
+
+---
+
+## 1. Overview
+
+The HIPAA Security Rule establishes national standards for protecting **electronic Protected Health Information (ePHI)**. It applies to covered entities and business associates that create, receive, maintain, or transmit ePHI.
+
+The Security Rule does **not** apply to PHI transmitted orally or on paper — that is governed solely by the Privacy Rule.
+
+**Core Principle:** Covered entities and business associates must ensure the confidentiality, integrity, and availability of all ePHI they create, receive, maintain, or transmit.
+
+---
+
+## 2. Three Pillars of Security Safeguards
+
+### 2.1 Administrative Safeguards (§ 164.308)
+
+Administrative safeguards are the policies, procedures, and actions to manage the selection, development, implementation, and maintenance of security measures.
+
+| Standard                             | Implementation Specifications                                                                                            | Required (R) or Addressable (A) |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------- |
+| **Security Management Process**      | Risk analysis, risk management, sanction policy, information system activity review                                      | R                               |
+| **Assigned Security Responsibility** | Designate a Security Officer                                                                                             | R                               |
+| **Workforce Security**               | Authorization and supervision, workforce clearance, termination procedures                                               | A                               |
+| **Information Access Management**    | Isolating health care clearinghouse functions, access authorization, access establishment                                | A                               |
+| **Security Awareness and Training**  | Security reminders, malicious software protection, log-in monitoring, password management                                | A                               |
+| **Security Incident Procedures**     | Response and reporting                                                                                                   | R                               |
+| **Contingency Plan**                 | Data backup plan, disaster recovery plan, emergency mode operations, testing, applications and data criticality analysis | R/A                             |
+| **Evaluation**                       | Periodic technical and non-technical evaluation                                                                          | R                               |
+| **Business Associate Contracts**     | Written contracts with business associates                                                                               | R                               |
+
+### 2.2 Physical Safeguards (§ 164.310)
+
+Physical safeguards govern physical access to electronic information systems and the buildings and equipment that house them.
+
+| Standard                      | Implementation Specifications                                                                      | Required (R) or Addressable (A) |
+| ----------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------- |
+| **Facility Access Controls**  | Contingency operations, facility security plan, access control and validation, maintenance records | A                               |
+| **Workstation Use**           | Specify proper use of workstations accessing ePHI                                                  | R                               |
+| **Workstation Security**      | Physical safeguards for workstations                                                               | R                               |
+| **Device and Media Controls** | Disposal, media re-use, accountability, data backup and storage                                    | R/A                             |
+
+### 2.3 Technical Safeguards (§ 164.312)
+
+Technical safeguards are the technology and policy to protect ePHI and control access to it. This is the most relevant pillar for software architecture.
+
+| Standard                            | Implementation Specifications                                                                   | Required (R) or Addressable (A) |
+| ----------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------- |
+| **Access Control**                  | Unique user identification, emergency access procedure, automatic logoff, encryption/decryption | R/A                             |
+| **Audit Controls**                  | Hardware, software, and procedural mechanisms to record and examine ePHI access                 | R                               |
+| **Integrity**                       | Mechanisms to authenticate ePHI — verify data has not been altered or destroyed                 | A                               |
+| **Person or Entity Authentication** | Procedures to verify that persons seeking access are who they claim to be                       | R                               |
+| **Transmission Security**           | Encryption of ePHI in transit, integrity controls                                               | A                               |
+
+---
+
+## 3. Required vs. Addressable Implementation Specifications
+
+A critical distinction in the Security Rule:
+
+- **Required (R):** Must be implemented — no flexibility
+- **Addressable (A):** Must assess whether the specification is reasonable and appropriate. If so, implement it. If not, document why and implement an equivalent alternative
+
+> **Common Misconception:** "Addressable" does NOT mean "optional." Organizations must document their assessment and reasoning for every addressable specification they choose not to implement in its stated form.
+
+---
+
+## 4. Risk Analysis — The Foundation of Security Rule Compliance
+
+Risk analysis is the **single most cited deficiency** in HIPAA enforcement actions. It is a Required standard under § 164.308(a)(1).
+
+### Required Risk Analysis Components:
+
+1. **Scope:** Define the scope of the analysis — all ePHI created, received, maintained, or transmitted
+2. **Data Collection:** Identify where ePHI is stored, received, maintained, or transmitted
+3. **Identify Threats and Vulnerabilities:** Reasonably anticipated threats to confidentiality, integrity, and availability of ePHI
+4. **Assess Current Controls:** Evaluate existing security measures
+5. **Determine Likelihood:** Assess the probability that each threat will exploit a vulnerability
+6. **Determine Impact:** Evaluate the potential impact of a threat exploiting a vulnerability
+7. **Determine Level of Risk:** Combine likelihood and impact to assign risk levels
+8. **Document Results:** Formal written risk analysis document
+9. **Periodic Review:** Re-assess risk when environment or operations change
+
+---
+
+## 5. Technical Safeguards in Software Architecture
+
+### 5.1 Access Control Requirements
+
+| Technical Control          | HIPAA Requirement                  | Engineering Implementation                                   |
+| -------------------------- | ---------------------------------- | ------------------------------------------------------------ |
+| Unique User Identification | § 164.312(a)(2)(i) — Required      | UUID-based user accounts, no shared credentials              |
+| Emergency Access           | § 164.312(a)(2)(ii) — Required     | Break-glass procedure with audit logging                     |
+| Automatic Logoff           | § 164.312(a)(2)(iii) — Addressable | Session timeout after inactivity (15–30 minutes recommended) |
+| Encryption/Decryption      | § 164.312(a)(2)(iv) — Addressable  | AES-256 at rest; critical for breach safe harbor             |
+
+### 5.2 Audit Controls
+
+The Security Rule requires mechanisms to record and examine activity in information systems that contain or use ePHI.
+
+**Minimum audit log contents:**
+
+- User identity (who)
+- Date and time of event (when)
+- Originating source (where — IP, device)
+- Type of event (what action)
+- Success or failure of the event
+
+**Critical Engineering Note:** Audit logs must be:
+
+- Immutable (write-once, cannot be modified by end users)
+- Retained for a minimum of 6 years (HIPAA document retention period)
+- Protected from unauthorized access or deletion
+- Regularly reviewed — not just stored
+
+### 5.3 Transmission Security
+
+| Requirement            | Standard                              | Notes                                            |
+| ---------------------- | ------------------------------------- | ------------------------------------------------ |
+| TLS Version            | TLS 1.2 minimum, TLS 1.3 preferred    | TLS 1.0 and 1.1 are deprecated and non-compliant |
+| Certificate Management | Valid certificates from trusted CA    | Self-signed certificates are high-risk           |
+| API Security           | HTTPS only, no HTTP fallback          | Enforce HSTS headers                             |
+| Email Encryption       | S/MIME or equivalent for PHI in email | Do not send unencrypted PHI via email            |
+
+### 5.4 Encryption Standards
+
+| Data State              | Recommended Standard       | Notes                                            |
+| ----------------------- | -------------------------- | ------------------------------------------------ |
+| At Rest (database)      | AES-256                    | Column-level encryption for PHI fields preferred |
+| At Rest (files/backups) | AES-256                    | Encrypted before upload to cloud storage         |
+| In Transit              | TLS 1.2+                   | End-to-end, no protocol downgrade allowed        |
+| In Use (memory)         | Application-level controls | Minimize ePHI in memory; clear buffers after use |
+| Backups                 | AES-256                    | Backup keys must be stored separately            |
+
+> **Safe Harbor for Breach Notification:** If ePHI is encrypted at rest AND in transit using HHS-specified methods, a breach of that data does not trigger mandatory breach notification requirements.
+
+---
+
+## 6. Common Security Rule Violations
+
+| Violation                        | Root Cause                                      | Frequency                    |
+| -------------------------------- | ----------------------------------------------- | ---------------------------- |
+| No documented risk analysis      | Never performed or not updated                  | Most common OCR finding      |
+| No risk management plan          | Risk analysis performed but no remediation plan | Very common                  |
+| No security officer designated   | Small organizations lack formal roles           | Common in small providers    |
+| No workforce security training   | Staff not trained on security policies          | Very common                  |
+| No audit controls                | Systems lack logging capabilities               | Common in legacy systems     |
+| No transmission security         | PHI sent via unencrypted email                  | Frequent violation           |
+| No device/media controls         | Lost/stolen unencrypted laptops                 | Major breach cause           |
+| Insufficient access controls     | Shared passwords, no MFA                        | Very common                  |
+| No Business Associate Agreements | Cloud services used without BAA                 | Extremely common in startups |
+| No incident response procedures  | No documented process for breaches              | Common                       |
+
+---
+
+## 7. Encryption: The Safe Harbor Misconception
+
+> **Critical Note for Software Engineers:** The mere implementation of encryption does NOT automatically satisfy the Security Rule.
+
+Encryption protects against:
+
+- Network interception
+- Physical hardware theft
+
+Encryption does **NOT** protect against:
+
+- Application-layer vulnerabilities
+- SQL injection attacks on the database
+- Unauthorized access by authenticated users
+- Insecure direct object references (IDOR)
+- Business logic flaws
+- Improper API authorization (accessing another user's data)
+
+**Example failure pattern:** A system uses AES-256 encryption but lacks granular access controls. An authenticated user can query a database endpoint and retrieve other patients' records. The system is non-compliant despite strong encryption.
+
+---
+
+## 8. Multi-Factor Authentication (MFA)
+
+While not explicitly required by name in the HIPAA Security Rule, MFA is strongly implied by:
+
+- § 164.312(d) — Person or Entity Authentication (Required)
+- OCR guidance and enforcement actions strongly recommend MFA
+
+**MFA requirements for HIPAA environments:**
+
+- All administrative access to systems containing ePHI
+- Remote access (VPN, SSH, RDP)
+- Cloud management consoles
+- EHR system login
+
+---
+
+## 9. Mobile Device Management (MDM)
+
+Mobile devices that access ePHI require:
+
+| Control               | Requirement                                    |
+| --------------------- | ---------------------------------------------- |
+| Device encryption     | Encryption of device storage                   |
+| Remote wipe           | Ability to remotely wipe device if lost/stolen |
+| Screen lock           | Automatic lock after inactivity                |
+| Device authentication | PIN, biometric, or password                    |
+| App containerization  | Separate work apps from personal use           |
+| MDM enrollment        | Device registered in mobile management system  |
+| Jailbreak detection   | Block access from compromised devices          |
+
+---
+
+## 10. Workforce Training Requirements
+
+All workforce members who have access to ePHI must receive regular security training including:
+
+- Security awareness basics
+- How to recognize and avoid phishing attacks
+- Password management policies
+- Proper use of mobile devices with ePHI
+- How to report security incidents
+- Consequences of violations (sanctions policy)
+
+**Recommended training frequency:** At minimum annually; quarterly for high-risk roles
+
+---
+
+## 11. Incident Response Planning
+
+Required under § 164.308(a)(6) — Security Incident Procedures.
+
+An incident response plan must address:
+
+1. **Detection:** Monitoring systems to identify potential incidents
+2. **Reporting:** Procedures for workforce to report incidents
+3. **Response:** Steps to contain and mitigate the incident
+4. **Investigation:** Determine scope, cause, and impact
+5. **Documentation:** Document the incident and response actions
+6. **Notification:** Determine if breach notification is required
+7. **Post-incident Review:** Lessons learned and control improvements
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `03-breach-notification-rule.md`, `08-technical-safeguards-engineering.md`, `10-cloud-computing-hipaa.md`

datasets/03-breach-notification-rule.md

@@ -0,0 +1,199 @@
+# HIPAA Breach Notification Rule — Comprehensive Dataset
+
+**Source:** 45 CFR §§ 164.400–414  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**Enacted:** HITECH Act (2009), finalized via HIPAA Omnibus Rule (2013)  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html
+
+---
+
+## 1. Overview
+
+The Breach Notification Rule requires **covered entities** and their **business associates** to provide notification following a breach of unsecured Protected Health Information (PHI).
+
+A **breach** is generally defined as an impermissible use or disclosure under the Privacy Rule that compromises the **security or privacy** of the PHI.
+
+**Key Presumption:** An impermissible use or disclosure of PHI is presumed to be a breach unless the covered entity or business associate demonstrates that there is a **low probability** that the PHI has been compromised.
+
+---
+
+## 2. What Constitutes "Unsecured PHI"
+
+PHI is considered **unsecured** (and thus subject to breach notification) unless it has been rendered unusable, unreadable, or indecipherable through one of the following HHS-approved methods:
+
+| Securing Method | Description                                                                                                                                  |
+| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Encryption**  | PHI encrypted using NIST-approved algorithms (AES-256 at rest, TLS 1.2+ in transit) with keys stored separately                              |
+| **Destruction** | Paper/film: shredded or destroyed so PHI cannot be read or reconstructed; Electronic media: cleared, purged, or destroyed per NIST SP 800-88 |
+
+> **Safe Harbor:** If PHI is secured through one of these methods, a breach of that data **does NOT trigger** mandatory breach notification requirements. This is the strongest incentive for full encryption implementation.
+
+---
+
+## 3. Exceptions — When a Security Incident is NOT a Breach
+
+Three explicit exceptions exist where an impermissible disclosure is not considered a breach:
+
+1. **Unintentional Access by Workforce Member**  
+   An unintentional acquisition, access, or use of PHI by a workforce member acting in good faith within the scope of authority — and the PHI is not further used or disclosed.
+
+2. **Inadvertent Disclosure Between Authorized Personnel**  
+   An inadvertent disclosure of PHI by a person authorized to access it at a covered entity to another person authorized to access PHI at the same covered entity — and the PHI is not further used or disclosed.
+
+3. **Inability to Retain**  
+   Where a covered entity or business associate has a good faith belief that the unauthorized person to whom the impermissible disclosure was made would not have been able to retain the information.
+
+---
+
+## 4. The Four-Factor Risk Assessment
+
+Before determining if notification is required, the entity must perform a formal risk assessment evaluating these four factors:
+
+| Factor                                             | Description                                                                              | Key Considerations                                                           |
+| -------------------------------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+| **1. Nature and Extent of PHI Involved**           | What types of identifiers were exposed, and what is the likelihood of re-identification? | Financial information, SSN, and clinical details significantly increase risk |
+| **2. Who Accessed or Could Have Accessed the PHI** | Was the unauthorized person someone who would use the PHI to harm individuals?           | Internal IT error vs. malicious external actor — very different risk profile |
+| **3. Whether PHI Was Actually Acquired or Viewed** | Did the unauthorized person actually take or view the information?                       | Server logs, access logs, forensic evidence can demonstrate this             |
+| **4. Extent to Which Risk Has Been Mitigated**     | Were steps taken to reduce the risk after the breach?                                    | Recovery of devices, return of information, assurances from recipient        |
+
+If after assessment the probability of compromise is **low**, no breach notification is required. The entity must **document** the analysis regardless.
+
+---
+
+## 5. Notification Requirements
+
+### 5.1 Notification to Affected Individuals
+
+| Requirement           | Details                                                                                                                                      |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Deadline**          | Without unreasonable delay, and no later than **60 calendar days** after discovery of the breach                                             |
+| **Form**              | Written notice by first-class mail to last known address; email if individual has agreed to electronic notice                                |
+| **Content Required**  | Description of breach, types of PHI involved, steps individuals should take, steps entity is taking, contact information for questions       |
+| **Substitute Notice** | If contact information is insufficient for 10+ individuals, post notice on website homepage or provide notice in major print/broadcast media |
+| **Urgent Notice**     | If there is risk of imminent misuse, must also provide notice via phone or other means in addition to written notice                         |
+
+### 5.2 Notification to Media (Large Breaches)
+
+| Threshold                                     | Requirement                                                   | Deadline             |
+| --------------------------------------------- | ------------------------------------------------------------- | -------------------- |
+| **500+ residents of a state or jurisdiction** | Notify prominent media outlets serving the state/jurisdiction | Same 60-day deadline |
+
+### 5.3 Notification to HHS Secretary
+
+| Breach Size                    | How to Notify                                                         | Deadline                                                                                    |
+| ------------------------------ | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| **500+ individuals**           | Submit via HHS web portal; entity is placed on public "Wall of Shame" | Within 60 days of discovery                                                                 |
+| **Fewer than 500 individuals** | Maintain log; submit annually to HHS                                  | No later than **60 days after the end of the calendar year** in which the breaches occurred |
+
+### 5.4 Business Associate Notification to Covered Entity
+
+When a business associate discovers a breach:
+
+- Must notify the covered entity **without unreasonable delay** and within **60 days** of discovery
+- BA must provide information to the covered entity to allow the covered entity to fulfill its notification obligations
+- BAA may specify a shorter notification period
+
+---
+
+## 6. Date of Discovery vs. Date of Breach
+
+| Term                  | Definition                                                                                                                        |
+| --------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| **Date of Discovery** | The first day on which the breach is **known** to the covered entity, or by exercising reasonable diligence would have been known |
+| **Date of Breach**    | The date the actual incident occurred (may be earlier than discovery)                                                             |
+
+> The 60-day notification clock starts from the **date of discovery**, not the date of the breach itself.
+
+---
+
+## 7. Breach Notification Content Requirements (Individual Notice)
+
+A written notification to individuals must include, to the extent possible:
+
+1. A brief description of what happened, including the date of the breach and the date of discovery
+2. A description of the types of unsecured PHI involved (e.g., name, SSN, date of birth, financial information, clinical information)
+3. Any steps individuals should take to protect themselves from potential harm
+4. A brief description of what the covered entity is doing to investigate the breach, mitigate harm, and protect against future breaches
+5. Contact procedures for individuals to ask questions or learn additional information (toll-free phone number, email address, website, or postal address)
+
+---
+
+## 8. HHS Wall of Shame (Public Breach List)
+
+The HHS maintains a publicly accessible database of all breaches affecting 500 or more individuals. This is commonly referred to as the "Wall of Shame."
+
+**Information publicly disclosed:**
+
+- Name of covered entity
+- State
+- Type of covered entity
+- Individuals affected
+- Date of breach
+- Type of breach (Hacking/IT incident, Theft, Unauthorized Access, etc.)
+- Location of breached information (Desktop computer, Laptop, Network Server, Paper, etc.)
+
+---
+
+## 9. Business Associate Breach Reporting Chain
+
+```
+Breach Occurs at Business Associate
+         ↓
+BA notifies Covered Entity (within 60 days of BA's discovery)
+         ↓
+Covered Entity notifies affected Individuals (within 60 days of CE discovery)
+         ↓
+Covered Entity notifies HHS Secretary (within 60 days for 500+, annually for <500)
+         ↓
+If 500+ in a state: Covered Entity also notifies Media
+```
+
+---
+
+## 10. Penalties for Failure to Provide Timely Notification
+
+Failure to provide required breach notifications is a separate HIPAA violation subject to civil monetary penalties:
+
+| Violation Category                         | Penalty Range Per Violation | Annual Cap |
+| ------------------------------------------ | --------------------------- | ---------- |
+| **Did not know (reasonable diligence)**    | $100 – $50,000              | $1,919,173 |
+| **Reasonable cause (not willful neglect)** | $1,000 – $50,000            | $1,919,173 |
+| **Willful neglect, corrected**             | $10,000 – $50,000           | $1,919,173 |
+| **Willful neglect, not corrected**         | $50,000                     | $1,919,173 |
+
+---
+
+## 11. Breach Response Engineering Checklist
+
+- [ ] Security incident detected and logged
+- [ ] Incident response team assembled
+- [ ] Forensic analysis to determine scope and date of breach
+- [ ] Risk assessment performed against 4-factor test
+- [ ] Legal counsel consulted
+- [ ] Determine if incident meets definition of breach
+- [ ] If breach: prepare individual notifications
+- [ ] If breach: notify HHS (immediately for 500+, log for <500)
+- [ ] If 500+ in a state: notify major media
+- [ ] If business associate caused breach: ensure BA has notified you
+- [ ] Document entire process with timestamps
+- [ ] Implement remediation controls
+- [ ] Post-incident review and updated risk analysis
+
+---
+
+## 12. Common Causes of Reportable Breaches
+
+Based on HHS breach database patterns:
+
+| Cause                            | Percentage of Breaches | Notes                                             |
+| -------------------------------- | ---------------------- | ------------------------------------------------- |
+| Hacking / IT Incident            | ~75%                   | Ransomware, phishing, external server attacks     |
+| Unauthorized Access / Disclosure | ~10%                   | Employees accessing records without authorization |
+| Theft                            | ~8%                    | Physical theft of devices                         |
+| Loss                             | ~3%                    | Lost laptops, USB drives, paper records           |
+| Improper Disposal                | ~2%                    | PHI in garbage, unsanitized devices sold          |
+| Unknown                          | ~2%                    | —                                                 |
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `02-hipaa-security-rule.md`, `05-business-associates.md`, `14-enforcement-penalties.md`

datasets/04-phi-de-identification.md

@@ -0,0 +1,247 @@
+# PHI De-Identification — Comprehensive Dataset
+
+**Source:** 45 CFR § 164.514(b)  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/privacy/special-topics/de-identification/index.html
+
+---
+
+## 1. Overview
+
+De-identified health information is **not subject to the Privacy Rule** because it does not identify an individual, and there is no reasonable basis to believe it can be used to identify an individual.
+
+De-identification is the process of removing or transforming identifiers such that the resulting data cannot reasonably be used to identify an individual — making it legally safe for AI training, research, analytics, and publication.
+
+**Why this matters for AI/RAG systems:** De-identified data can be freely used for LLM training, vector database ingestion, and analytics without triggering HIPAA restrictions. Improperly de-identified data that is ingested into AI systems creates massive legal liability.
+
+---
+
+## 2. Two Methods of De-Identification
+
+HHS specifies **two mutually exclusive methods**. An organization must fully comply with one of these methods for the data to qualify as de-identified.
+
+| Method                   | Approach                                                       | Flexibility                 | Best For                               |
+| ------------------------ | -------------------------------------------------------------- | --------------------------- | -------------------------------------- |
+| **Safe Harbor**          | Remove all 18 specified identifiers                            | Prescriptive, deterministic | Operational teams, automated pipelines |
+| **Expert Determination** | Statistical analysis proving very small re-identification risk | Flexible, requires expert   | Research requiring data utility        |
+
+---
+
+## 3. Safe Harbor Method — The 18 Required Removals
+
+Under the Safe Harbor method, **all 18 of the following identifiers** must be removed from the data. The removal must apply to the individual **and** their relatives, employers, and household members.
+
+| #   | Identifier                                                       | Examples                                               | Pipeline Notes                            |
+| --- | ---------------------------------------------------------------- | ------------------------------------------------------ | ----------------------------------------- |
+| 1   | **Names**                                                        | First, last, middle, initials                          | NER model required                        |
+| 2   | **Geographic data**                                              | Street address, city, county, precinct                 | See ZIP code nuance below                 |
+| 3   | **Dates**                                                        | Birth date, admission date, discharge date, death date | Year may be retained (with age exception) |
+| 4   | **Phone numbers**                                                | All telephone numbers                                  |                                           |
+| 5   | **Fax numbers**                                                  | All fax numbers                                        |                                           |
+| 6   | **Email addresses**                                              | All email addresses                                    |                                           |
+| 7   | **Social Security numbers**                                      | Full or partial SSN                                    |                                           |
+| 8   | **Medical record numbers**                                       | MRN, patient IDs                                       |                                           |
+| 9   | **Health plan beneficiary numbers**                              | Insurance member IDs                                   |                                           |
+| 10  | **Account numbers**                                              | Bank accounts, billing account numbers                 |                                           |
+| 11  | **Certificate/license numbers**                                  | Medical license, DEA number                            |                                           |
+| 12  | **Vehicle identifiers**                                          | VIN, license plate numbers                             |                                           |
+| 13  | **Device identifiers**                                           | Serial numbers, unique device identifiers              |                                           |
+| 14  | **Web URLs**                                                     | Personal website addresses                             |                                           |
+| 15  | **IP addresses**                                                 | Full IPv4/IPv6 addresses                               |                                           |
+| 16  | **Biometric identifiers**                                        | Fingerprints, voice prints, retina scans               |                                           |
+| 17  | **Full-face photographs**                                        | Any comparable images (scars, tattoos)                 |                                           |
+| 18  | **Any other unique identifying number, characteristic, or code** | Catch-all for novel identifiers                        |                                           |
+
+---
+
+## 4. Safe Harbor: Geographic Data Nuances
+
+### 4.1 General Geographic Rule
+
+All geographic subdivisions **smaller than a state** must be removed:
+
+- Street addresses
+- City names
+- County names
+- Precinct names
+
+### 4.2 ZIP Code Exception (Critical for Data Pipelines)
+
+ZIP codes — or their geographic equivalents — may be **retained** only under specific conditions:
+
+| Condition                                                                                                                                           | Action                                     |
+| --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
+| The first three digits of a ZIP code represent a geographic unit with a combined population **greater than 20,000 people** (per latest Census data) | **First 3 digits may be retained**         |
+| The first three digits of a ZIP code represent a geographic unit with a combined population of **20,000 or fewer people**                           | **Must replace first 3 digits with "000"** |
+
+**Example:** ZIP code `02139` (Cambridge, MA area) — if the 3-digit `021` covers >20,000 people, it may be kept. Otherwise, it becomes `000xx`.
+
+### 4.3 State-Level Data
+
+State names may always be retained. Only sub-state geographies must be evaluated.
+
+---
+
+## 5. Safe Harbor: Temporal Data Nuances
+
+### 5.1 Dates — What Can Be Retained vs. Removed
+
+| Date Element                           | Rule                                                             |
+| -------------------------------------- | ---------------------------------------------------------------- |
+| **Year**                               | May be retained                                                  |
+| **Month and Day**                      | Must be removed from all dates directly related to an individual |
+| **Specific admission/discharge dates** | Must be removed                                                  |
+| **Birth date**                         | Must be removed (month and day — year may be retained)           |
+| **Death date**                         | Must be removed (month and day — year may be retained)           |
+
+### 5.2 The Age Over 89 Rule
+
+Any ages over 89 **and** any elements of dates (including year) that would allow identification of an individual's age as over 89 must be:
+
+- **Aggregated into a single category: "90 or older"**
+
+**Rationale:** The elderly population is smaller and more identifiable; precise ages or dates that reveal an age above 89 must be suppressed.
+
+**Automated pipeline failure mode:** A system that retains birth year and the current year can inadvertently reveal an age over 89 through arithmetic. Both values must be checked.
+
+---
+
+## 6. Safe Harbor: The "Actual Knowledge" Provision
+
+> **The most critical and most overlooked provision in the Safe Harbor method.**
+
+Even if all 18 identifiers are successfully removed, the data is **still not legally de-identified** if the covered entity has **actual knowledge** that the remaining information could be used to re-identify the subject.
+
+### Actual Knowledge Examples:
+
+| Scenario                                                                   | Why it Violates the Provision                                               |
+| -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
+| Record contains "President of Smalltown University"                        | In a small town, this occupation uniquely identifies one person             |
+| Record describes "the patient who had the rare sextuplet birth"            | A nationally reported event tied to a single identifiable individual        |
+| Record includes an extremely rare disease diagnosis in a very small county | Population so small the diagnosis is effectively identifying                |
+| Internal records reference a celebrity patient                             | The entity has actual knowledge that remaining data maps to a public figure |
+
+### Engineering Implication:
+
+Automated de-identification pipelines **cannot fully solve** the Actual Knowledge problem. A human review step or subject matter expert validation is required for any data that might contain quasi-identifiers with small population denominators.
+
+---
+
+## 7. Expert Determination Method
+
+The Expert Determination method takes a **probabilistic, statistical approach** instead of a fixed 18-identifier checklist.
+
+### Requirements:
+
+1. **Qualified Expert:** Must be a person with "appropriate knowledge of and experience with generally accepted statistical and scientific principles and methods for rendering information not individually identifiable"
+2. **Risk Analysis:** Apply analytical techniques 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
+3. **Documentation:** The expert must formally document their methods and results
+
+### Expert Analysis Framework:
+
+| Factor                                 | Description                                                                                |
+| -------------------------------------- | ------------------------------------------------------------------------------------------ |
+| **Replicability**                      | How consistently does a feature occur across individuals? (Low replicability = lower risk) |
+| **Distinguishability**                 | How much does the feature uniquely distinguish one individual from others?                 |
+| **External Data Availability**         | What publicly available data could be combined with this dataset to re-identify?           |
+| **Recipient Computational Capability** | What is the anticipated computational power of the data recipient?                         |
+| **Population Denominator**             | How large is the underlying population the record is drawn from?                           |
+
+### Priority Features by Re-identification Risk:
+
+| Feature Type                            | Risk Level | Rationale                         |
+| --------------------------------------- | ---------- | --------------------------------- |
+| Date of birth                           | Very High  | Stable, unique across time        |
+| Rare disease diagnosis                  | Very High  | Small patient population          |
+| Occupation + location combination       | High       | May be unique in small areas      |
+| Common lab values (e.g., blood glucose) | Low        | High variation, low replicability |
+| Generic age ranges (decade)             | Low        | Large population denominator      |
+
+---
+
+## 8. Time-Limited Certifications
+
+Because technology and public data availability change rapidly:
+
+- Expert Determination certifications are often issued as **time-limited** (e.g., valid for 2 years)
+- Data must be **re-evaluated** against current external data sources before future releases
+- A dataset that was safely de-identified in 2020 may no longer be de-identified in 2026 due to new public data becoming available
+
+---
+
+## 9. Re-Identification Risk Management
+
+### Re-identification Attack Vectors:
+
+| Attack Type               | Description                                                                      | Mitigation                                         |
+| ------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------- |
+| **Linkage Attack**        | Combining released dataset with external public data (voter rolls, social media) | Expert Determination review; limit released fields |
+| **Inference Attack**      | Deriving sensitive attributes from non-sensitive features                        | Suppress or generalize quasi-identifiers           |
+| **Reconstruction Attack** | Using aggregate statistics to reconstruct individual records                     | Differential privacy, k-anonymity                  |
+| **Temporal Attack**       | Cross-referencing multiple time-separated releases                               | Consistent suppression across releases             |
+
+### K-Anonymity and Beyond:
+
+While not explicitly required by HIPAA, privacy-preserving techniques include:
+
+- **k-Anonymity:** Each record is indistinguishable from at least k-1 other records
+- **l-Diversity:** Each equivalence class has at least l well-represented sensitive values
+- **t-Closeness:** Distribution of sensitive attributes approximates overall distribution
+- **Differential Privacy:** Mathematical privacy guarantee used by Apple, Google, and US Census
+
+---
+
+## 10. De-Identification in AI/RAG Pipelines
+
+### Pipeline Requirements for HIPAA-Compliant Ingestion:
+
+```
+Raw PHI Document
+     ↓
+[NER + Pattern Matching] — Identify all 18 identifier types
+     ↓
+[Context-Preserving Tokenization] — Replace with surrogate tokens
+     ↓
+[ZIP Code Population Check] — Retain or replace first 3 digits
+     ↓
+[Date Stripping] — Remove month/day, aggregate ages >89
+     ↓
+[Actual Knowledge Review] — Human or expert validation
+     ↓
+[Residual Risk Assessment] — Quasi-identifier analysis
+     ↓
+De-identified Document → Safe for RAG Vector Ingestion
+```
+
+### Context-Preserving Tokenization (Critical Technique):
+
+Simple redaction (blanking out text) destroys semantic value needed for LLM embeddings.
+
+**Better approach — surrogate tokenization:**
+
+- Replace `John Smith` → `[PATIENT_001]`
+- Replace `123-45-6789` → `[SSN_REDACTED]`
+- Replace `12/15/1978` → `[DOB_YEAR:1978]`
+
+This preserves document structure and semantic context while removing identifiable data.
+
+---
+
+## 11. Limited Data Set — Alternative to Full De-identification
+
+A **Limited Data Set** is an intermediate option: PHI with specific direct identifiers removed, but not fully de-identified. It can be used for research, public health, and health care operations under a **Data Use Agreement (DUA)**.
+
+### Direct Identifiers Removed in a Limited Data Set:
+
+Names, postal address (other than town/city, state, ZIP), phone/fax numbers, emails, SSN, medical record numbers, health plan numbers, account numbers, certificate numbers, vehicle identifiers, device identifiers, URLs, IP addresses, biometrics, full-face photographs
+
+### Identifiers Retained in a Limited Data Set:
+
+- Dates (full dates — including birth date, admission, discharge, death)
+- Town/city, state, ZIP code
+- Ages
+- Geographic subdivisions other than street address
+
+---
+
+**Related Datasets:** `06-phi-definitions-identifiers.md`, `01-hipaa-privacy-rule.md`, `16-rag-system-architecture.md`

datasets/05-business-associates.md

@@ -0,0 +1,191 @@
+# HIPAA Business Associates — Comprehensive Dataset
+
+**Source:** 45 CFR §§ 164.502(e), 164.504(e), 164.308(b), 164.314  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html
+
+---
+
+## 1. Overview
+
+A **Business Associate (BA)** is any person or entity that performs functions or activities on behalf of a covered entity that involve the use or disclosure of Protected Health Information (PHI). Business associates are **directly liable** for HIPAA compliance — they are not exempt simply because they are not a covered entity.
+
+Under the HIPAA Omnibus Rule (2013), business associates and their **subcontractors** are bound by the same HIPAA obligations as covered entities.
+
+---
+
+## 2. Definition of a Business Associate
+
+A business associate is a person or organization (other than a member of a covered entity's workforce) that:
+
+- Creates, receives, maintains, or transmits PHI on behalf of a covered entity
+- Provides services to a covered entity that require access to PHI
+
+### Functions That Create BA Status:
+
+| Function                            | Examples                                         |
+| ----------------------------------- | ------------------------------------------------ |
+| Claims processing or administration | Insurance billing companies, clearinghouses      |
+| Data analysis and processing        | Analytics firms, EHR vendors                     |
+| Utilization review                  | Insurance review companies                       |
+| Quality assurance                   | Third-party quality auditors                     |
+| Patient safety activities           | Patient safety organizations                     |
+| Billing                             | Medical billing companies                        |
+| Benefit management                  | PBM (pharmacy benefit managers)                  |
+| Practice management                 | Practice management software vendors             |
+| Re-pricing                          | Insurance re-pricing services                    |
+| Legal services                      | Attorneys requiring PHI for representation       |
+| Accounting services                 | Accountants reviewing financial records with PHI |
+| Data aggregation                    | HIT companies aggregating ePHI                   |
+| Administrative activities           | Document management companies                    |
+
+---
+
+## 3. Cloud Service Providers as Business Associates
+
+This is the **most commonly misunderstood BA rule** in modern software development.
+
+Under HHS Guidance on Cloud Computing, **any Cloud Service Provider (CSP) that creates, receives, maintains, or transmits ePHI on behalf of a covered entity is a Business Associate — regardless of whether the CSP has the decryption keys to view the data.**
+
+| Cloud Model                                               | BA Status | BAA Required? |
+| --------------------------------------------------------- | --------- | ------------- |
+| **IaaS** (AWS, GCP, Azure) — stores encrypted ePHI        | YES — BA  | YES           |
+| **PaaS** (Heroku, Railway, Render) — runs app with ePHI   | YES — BA  | YES           |
+| **SaaS** (Salesforce, Zendesk, Intercom) — receives ePHI  | YES — BA  | YES           |
+| **SaaS (no ePHI contact)** — completely isolated from PHI | NO        | NO            |
+
+> **Critical Rule:** Even if a CSP only stores encrypted data and cannot see the underlying PHI, the CSP is still a BA because it "maintains" ePHI. A BAA must be executed.
+
+---
+
+## 4. Business Associate Agreement (BAA) Requirements
+
+A covered entity must have a written Business Associate Agreement (BAA) with every BA before any PHI exchange occurs.
+
+### Required BAA Provisions:
+
+| Provision                             | Description                                                                       |
+| ------------------------------------- | --------------------------------------------------------------------------------- |
+| **Permitted Uses and Disclosures**    | Establishes the purposes for which the BA may use or disclose PHI                 |
+| **Prohibited Uses**                   | BA may not use or disclose PHI other than as permitted by the BAA                 |
+| **Appropriate Safeguards**            | BA must implement safeguards to prevent unauthorized use or disclosure            |
+| **Subcontractor Requirements**        | BA must obtain BAAs from its own subcontractors that handle PHI                   |
+| **Reporting Obligations**             | BA must report any use or disclosure not permitted by the BAA, including breaches |
+| **Individual Rights**                 | BA must assist covered entity in fulfilling individual rights (access, amendment) |
+| **Availability of Books and Records** | BA must make internal practices available to HHS for compliance investigations    |
+| **Return or Destruction of PHI**      | At contract termination, BA must return or destroy all PHI                        |
+| **Compliance with Security Rule**     | BA must comply with the Security Rule for ePHI                                    |
+
+---
+
+## 5. Common Vendors Offering BAAs
+
+| Vendor                           | Service Type       | BAA Available                                       |
+| -------------------------------- | ------------------ | --------------------------------------------------- |
+| Amazon Web Services (AWS)        | IaaS               | YES — AWS BAA available for HIPAA-eligible services |
+| Google Cloud Platform (GCP)      | IaaS               | YES — Google Cloud BAA available                    |
+| Microsoft Azure                  | IaaS               | YES — Azure BAA available                           |
+| Microsoft 365 (Healthcare plans) | SaaS               | YES — with specific licensing                       |
+| Twilio                           | Communications API | YES — Twilio BAA available                          |
+| Salesforce Health Cloud          | CRM                | YES — Salesforce BAA available                      |
+| Zoom                             | Video conferencing | YES — Zoom BAA for Healthcare                       |
+| Slack                            | Messaging          | YES — Enterprise Grid with BAA                      |
+| Datadog                          | Monitoring         | YES — Datadog BAA available                         |
+
+---
+
+## 6. Vendors That Do NOT Offer BAAs (High-Risk)
+
+These vendors commonly refuse to sign BAAs, making them **prohibited from touching PHI**:
+
+| Vendor                                 | Notes                                                                        |
+| -------------------------------------- | ---------------------------------------------------------------------------- |
+| **Meta (Facebook Pixel / Meta Ads)**   | Universally refuses BAA; cannot be used on authenticated patient pages       |
+| **Google Analytics (client-side GA4)** | Standard GA4 does not support BAA; requires server-side proxy for healthcare |
+| **Firebase (default setup)**           | Standard Firebase does not have a BAA path for many services                 |
+| **Intercom (standard plans)**          | Does not offer BAA on standard plans                                         |
+| **Zendesk (standard plans)**           | Does not offer BAA on standard plans                                         |
+| **HubSpot (standard plans)**           | Does not sign BAAs for standard marketing/CRM usage                          |
+| **Most social media platforms**        | Twitter/X, LinkedIn, TikTok — do not offer BAAs                              |
+
+> **Compliance Action:** If a vendor will not sign a BAA, PHI must never reach their systems. This requires technical enforcement — not just policy — such as server-side API calls, data masking, and strict CSP headers.
+
+---
+
+## 7. Subcontractor Business Associates
+
+A BA that uses a subcontractor to perform services involving PHI must:
+
+- Obtain a BAA from the subcontractor (treating them as their own business associate)
+- Ensure the subcontractor provides at least equivalent protections as required in the BA's agreement with the covered entity
+
+**Chain of liability:**
+
+```
+Covered Entity → BAA → Business Associate → BAA → Subcontractor
+```
+
+All entities in the chain are directly liable for HIPAA violations.
+
+---
+
+## 8. Who is NOT a Business Associate
+
+The following are explicitly excluded from BA status:
+
+| Entity                                             | Reason                                                                                                      |
+| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
+| **Covered entity's own workforce**                 | Employees, volunteers, trainees are subject to workforce training, not BA rules                             |
+| **Another covered entity**                         | When disclosing PHI for treatment (special provisions apply)                                                |
+| **Conduit providers**                              | Entities that transmit PHI but do not access it (e.g., a postal service or pure telecommunications carrier) |
+| **Researchers**                                    | When receiving a limited data set under a data use agreement                                                |
+| **Entities receiving PHI for their own treatment** | A health care provider receiving PHI for treating the patient                                               |
+
+---
+
+## 9. BA Liability Under HIPAA Omnibus Rule
+
+Before the HIPAA Omnibus Rule (2013), only covered entities faced direct enforcement. The Omnibus Rule changed this:
+
+| Violation Type                                        | BA Direct Liability |
+| ----------------------------------------------------- | ------------------- |
+| Impermissible use or disclosure                       | YES                 |
+| Failure to implement required safeguards              | YES                 |
+| Failure to notify covered entity of breach            | YES                 |
+| Failure to provide HHS with records for investigation | YES                 |
+| Failure to obtain BAAs with subcontractors            | YES                 |
+
+Civil monetary penalties apply directly to business associates.
+
+---
+
+## 10. BAA Checklist for Startups
+
+Before launching any health tech product, verify:
+
+- [ ] Identified all third-party services that will touch PHI
+- [ ] AWS / GCP / Azure BAA signed for cloud infrastructure
+- [ ] Database hosting provider BAA signed
+- [ ] Email service provider BAA signed (if sending PHI via email)
+- [ ] Analytics platform either excluded from PHI or covered by BAA
+- [ ] Customer support platform BAA signed
+- [ ] CI/CD pipeline tools reviewed — do they touch production ePHI?
+- [ ] Logging/monitoring services BAA signed
+- [ ] Video conferencing (Zoom/Teams) BAA signed if telehealth features used
+- [ ] Subcontractors identified and BAAs obtained from them
+- [ ] BAA termination clauses reviewed — what happens to data if contract ends?
+- [ ] All BAAs stored securely with termination dates tracked
+
+---
+
+## 11. BAA Termination Obligations
+
+When a BAA terminates (contract ends), the BA must:
+
+1. Return all PHI to the covered entity, OR
+2. Destroy all PHI (and certify destruction)
+3. If return or destruction is not feasible, extend BAA protections for the duration of retention
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `02-hipaa-security-rule.md`, `10-cloud-computing-hipaa.md`, `12-digital-marketing-tracking-risks.md`

datasets/06-phi-definitions-identifiers.md

@@ -0,0 +1,214 @@
+# PHI Definitions and the 18 Identifiers — Comprehensive Dataset
+
+**Source:** 45 CFR § 164.514, 45 CFR § 160.103  
+**Authority:** U.S. Department of Health and Human Services (HHS)
+
+---
+
+## 1. What is Protected Health Information (PHI)?
+
+**Protected Health Information (PHI)** is any information that:
+
+1. Relates to an individual's **past, present, or future physical or mental health** or condition
+2. Relates to the **provision of health care** to the individual
+3. Relates to the **past, present, or future payment** for health care
+4. **Identifies the individual** or could reasonably be used to identify the individual
+5. Is **held or transmitted** by a covered entity or business associate in **any form** (electronic, paper, or oral)
+
+---
+
+## 2. What is Electronic Protected Health Information (ePHI)?
+
+**ePHI** is PHI that is:
+
+- Created, received, maintained, or transmitted in **electronic form**
+
+ePHI is subject to both the Privacy Rule and the Security Rule. Paper PHI is subject only to the Privacy Rule.
+
+---
+
+## 3. Individually Identifiable Health Information
+
+Health information is "individually identifiable" if it:
+
+- Identifies the individual, OR
+- Creates a reasonable basis to believe it could be used to identify the individual
+
+This includes information about the individual's **relatives, employers, and household members**.
+
+---
+
+## 4. The 18 PHI Identifiers (Safe Harbor)
+
+The following 18 categories of identifiers must be removed for data to be considered de-identified under the Safe Harbor method:
+
+| #   | Identifier Category                                              | Specific Examples                                                                                  | Automated Detection Notes                                 |
+| --- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
+| 1   | **Names**                                                        | First name, last name, middle name, initials, suffix, maiden name                                  | Named Entity Recognition (NER)                            |
+| 2   | **Geographic subdivisions smaller than a state**                 | Street address, city, county, precinct, ZIP code (with population rules)                           | Address parser, ZIP lookup                                |
+| 3   | **All elements of dates except year**                            | Birth date, admission date, discharge date, death date, other dates directly related to individual | Date parser (regex + NLP)                                 |
+| 4   | **Telephone numbers**                                            | Cell, home, work, direct lines                                                                     | Regex: `\+?[0-9\-\(\)\s]{7,15}`                           |
+| 5   | **Fax numbers**                                                  | All fax numbers                                                                                    | Regex pattern                                             |
+| 6   | **Email addresses**                                              | Personal and work email                                                                            | Regex: `[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,}` |
+| 7   | **Social Security numbers**                                      | Full or partial SSN                                                                                | Regex: `\d{3}-\d{2}-\d{4}`                                |
+| 8   | **Medical record numbers**                                       | MRN, patient ID, encounter number                                                                  | Pattern matching with context                             |
+| 9   | **Health plan beneficiary numbers**                              | Insurance member ID, group number                                                                  | Pattern matching                                          |
+| 10  | **Account numbers**                                              | Bank account, billing account, credit card                                                         | Luhn algorithm + regex                                    |
+| 11  | **Certificate/license numbers**                                  | Medical license, DEA number, NPI                                                                   | Pattern matching per type                                 |
+| 12  | **Vehicle identifiers and serial numbers**                       | VIN, license plate                                                                                 | VIN regex, plate patterns                                 |
+| 13  | **Device identifiers and serial numbers**                        | Medical device serial, IMEI, MAC address                                                           | Pattern matching                                          |
+| 14  | **Web Universal Resource Locators (URLs)**                       | Personal websites, patient portal URLs                                                             | URL regex                                                 |
+| 15  | **Internet Protocol (IP) addresses**                             | IPv4, IPv6                                                                                         | Regex IP patterns                                         |
+| 16  | **Biometric identifiers**                                        | Fingerprints, voiceprints, retina scans, facial geometry                                           | Metadata tagging, file-type checks                        |
+| 17  | **Full-face photographs and comparable images**                  | Profile photos, photos showing identifying features (tattoos, scars)                               | Image analysis                                            |
+| 18  | **Any other unique identifying number, characteristic, or code** | Catch-all for novel identifiers not listed above                                                   | Context-aware human review                                |
+
+---
+
+## 5. Quasi-Identifiers (Not in 18 but Risk Re-identification)
+
+These fields are not in the 18 Safe Harbor identifiers but may enable re-identification when combined with other data:
+
+| Field                        | Risk Level                         | Rationale                                                              |
+| ---------------------------- | ---------------------------------- | ---------------------------------------------------------------------- |
+| **Gender**                   | Low alone, moderate in combination | Only 2 values — adds to combinations                                   |
+| **Age (exact)**              | Moderate                           | Combined with ZIP and gender = 87% uniquely identified (Sweeney, 2000) |
+| **Race/Ethnicity**           | Moderate in small populations      | Small demographic = small denominator                                  |
+| **Occupation**               | High in rare jobs                  | "Chief Justice of [State]" = unique                                    |
+| **Rare diagnoses**           | Very High                          | ICD codes for ultra-rare diseases                                      |
+| **Detailed clinical events** | High                               | "3rd trimester quadruplet delivery"                                    |
+| **Religious affiliation**    | Moderate                           | Combined with demographics                                             |
+| **Marital status**           | Low                                | Very common attribute                                                  |
+
+---
+
+## 6. PHI vs. Non-PHI Decision Tree
+
+```
+Is it health information? ──NO──→ Not PHI
+          │
+         YES
+          │
+          ↓
+Is it held by a covered entity or BA? ──NO──→ Not PHI (but may be regulated under state law)
+          │
+         YES
+          │
+          ↓
+Does it identify or could it reasonably identify an individual? ──NO──→ De-identified (not PHI)
+          │
+         YES
+          │
+          ↓
+         PHI — HIPAA protections apply
+```
+
+---
+
+## 7. PHI in Different Forms
+
+PHI exists in many forms that are often overlooked in software systems:
+
+| Form                   | Examples                                       | Common Oversight                                |
+| ---------------------- | ---------------------------------------------- | ----------------------------------------------- |
+| **Structured ePHI**    | Database columns, EHR fields                   | Over-permissive database access                 |
+| **Unstructured ePHI**  | Clinical notes, discharge summaries, free text | Often missed in de-identification               |
+| **Images**             | X-rays, MRIs, CT scans, retinal scans          | DICOM metadata contains patient identifiers     |
+| **Audio**              | Recorded patient calls, voice messages         | Voice = biometric identifier                    |
+| **Video**              | Telehealth recordings                          | Face = comparable image identifier              |
+| **PDF/Documents**      | Scanned medical records, EOBs                  | Embedded text + images                          |
+| **Logs**               | Application logs containing patient data       | Critical — often sent to third-party monitoring |
+| **Backups**            | Database backups, file backups                 | Must be encrypted and access-controlled         |
+| **Emails**             | Clinical correspondence                        | Often unencrypted                               |
+| **Push notifications** | "Your oncology appointment is tomorrow"        | Exposed on lock screen — bypasses OS encryption |
+
+---
+
+## 8. PHI Exclusions
+
+The following are **not** PHI even if related to health:
+
+| Information                          | Why Not PHI                                                                            |
+| ------------------------------------ | -------------------------------------------------------------------------------------- |
+| **Employment records**               | Held by employer in employment capacity (not health records)                           |
+| **Education records**                | Covered by FERPA, not HIPAA                                                            |
+| **De-identified health information** | Does not meet the identifiability threshold                                            |
+| **Consumer health information**      | Wearable/app data not held by a covered entity (e.g., Fitbit data on Fitbit's servers) |
+| **Anonymous research data**          | De-identified under Expert Determination or Safe Harbor                                |
+
+---
+
+## 9. DICOM Metadata — Frequently Missed PHI Source
+
+DICOM (Digital Imaging and Communications in Medicine) files used for radiology and imaging contain PHI embedded in metadata headers:
+
+| DICOM Tag   | PHI Field                |
+| ----------- | ------------------------ |
+| (0010,0010) | Patient Name             |
+| (0010,0020) | Patient ID               |
+| (0010,0030) | Patient's Birth Date     |
+| (0010,0040) | Patient's Sex            |
+| (0010,1000) | Other Patient IDs        |
+| (0008,0020) | Study Date               |
+| (0008,0080) | Institution Name         |
+| (0008,0090) | Referring Physician Name |
+
+DICOM de-identification requires specialized tools (e.g., `pydicom`, DCM4CHEE, ClearCanvas) to strip all PHI-bearing tags before any image sharing or AI training.
+
+---
+
+## 10. PHI in Database Schema Design
+
+Engineering best practices for PHI isolation:
+
+```sql
+-- BAD: PHI mixed with operational data
+CREATE TABLE users (
+  id UUID PRIMARY KEY,
+  email TEXT,          -- PHI
+  full_name TEXT,      -- PHI
+  dob DATE,            -- PHI
+  plan_type TEXT,      -- operational, not PHI
+  created_at TIMESTAMPTZ
+);
+
+-- GOOD: PHI segregated into encrypted table
+CREATE TABLE users (
+  id UUID PRIMARY KEY,
+  plan_type TEXT,
+  created_at TIMESTAMPTZ
+);
+
+CREATE TABLE patient_phi (
+  user_id UUID REFERENCES users(id),
+  encrypted_payload BYTEA,  -- AES-256 encrypted JSON blob
+  key_id TEXT,              -- Reference to KMS key ID
+  updated_at TIMESTAMPTZ
+);
+```
+
+**Benefits of PHI isolation:**
+
+- Granular access controls per table
+- Simplified encryption scope
+- Easier audit logging
+- Reduced blast radius on breach
+
+---
+
+## 11. PHI Handling in Logging Systems
+
+> **This is the #1 source of accidental PHI disclosure in modern applications.**
+
+| Log Type                              | PHI Risk                                          | Mitigation                                             |
+| ------------------------------------- | ------------------------------------------------- | ------------------------------------------------------ |
+| **HTTP request logs**                 | URL parameters may contain patient IDs            | Mask/redact ID parameters before logging               |
+| **Application error logs**            | Stack traces may include PHI from request context | Sanitize context objects before logging                |
+| **Database query logs**               | May log full SQL with PHI values                  | Use parameterized queries; disable query value logging |
+| **Third-party APM tools**             | Datadog, New Relic, Splunk may ingest PHI         | Use BAA-covered tier; configure PHI scrubbing rules    |
+| **Browser console logs**              | Frontend debug logs may expose ePHI               | Disable debug logging in production builds             |
+| **Crash reporting (Sentry, Bugsnag)** | Exception context may include user data           | Configure PII scrubbing in SDK settings                |
+
+---
+
+**Related Datasets:** `04-phi-de-identification.md`, `01-hipaa-privacy-rule.md`, `08-technical-safeguards-engineering.md`

datasets/07-patient-rights.md

@@ -0,0 +1,249 @@
+# Patient Rights Under HIPAA — Comprehensive Dataset
+
+**Source:** 45 CFR §§ 164.522–164.528  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/privacy/index.html
+
+---
+
+## 1. Overview
+
+The HIPAA Privacy Rule grants individuals several specific rights with respect to their Protected Health Information (PHI). Covered entities are required to honor these rights and implement the technical and administrative infrastructure to support them.
+
+---
+
+## 2. Right of Access (§ 164.524)
+
+### Core Right
+
+Individuals have the right to inspect and obtain a copy of their PHI maintained in a **designated record set** for as long as the covered entity maintains the record.
+
+### What is a "Designated Record Set"?
+
+| Component                                                         | Includes                                    |
+| ----------------------------------------------------------------- | ------------------------------------------- |
+| **Medical records**                                               | All clinical documentation                  |
+| **Billing records**                                               | Payment and insurance records               |
+| **Health plan enrollment records**                                | Insurance eligibility data                  |
+| **Any other records used to make decisions about the individual** | Case management, utilization review records |
+
+### Timeframe Requirements:
+
+| Condition                  | Deadline                                                            |
+| -------------------------- | ------------------------------------------------------------------- |
+| Standard request           | **30 days** from receipt of request                                 |
+| If records are not on-site | **60 days** (one-time extension of 30 days if written notice given) |
+
+### Format Requirements:
+
+| Request Type                             | Covered Entity Obligation                                                 |
+| ---------------------------------------- | ------------------------------------------------------------------------- |
+| Individual requests electronic copy      | Must provide in the **electronic format requested** if readily producible |
+| Electronic format not readily producible | Must provide in a readable electronic format agreed upon                  |
+| Individual requests paper copy           | Must provide paper copy                                                   |
+| Third-party designation                  | Must transmit directly to designated third party if requested             |
+
+### Fees for Access:
+
+Covered entities may charge a **reasonable cost-based fee** for providing a copy, which may include:
+
+- Labor for copying (but NOT labor for searching and retrieving)
+- Supplies for creating paper or electronic copies
+- Postage (if individual requests mailed copy)
+
+Covered entities **may NOT** charge a fee to review records in person.
+
+### What Can Be Withheld?
+
+Covered entities may deny access in certain circumstances:
+
+| Grounds for Denial                                                 | Reviewable by Another Licensed Professional? |
+| ------------------------------------------------------------------ | -------------------------------------------- |
+| Psychotherapy notes                                                | Not applicable (separate rules)              |
+| Information compiled in anticipation of civil/criminal litigation  | NO                                           |
+| PHI at a correctional institution or under law enforcement custody | NO                                           |
+| Clinical information that could endanger life/safety of another    | YES — must provide review                    |
+| Reference to another person's information                          | YES — must provide review                    |
+| Obtained from a non-covered entity under confidentiality           | YES — must provide review                    |
+
+---
+
+## 3. Right to Amend PHI (§ 164.526)
+
+Individuals may request amendments to their PHI if they believe the information is **inaccurate or incomplete**.
+
+### Covered Entity Response Timeline: 60 days (one 30-day extension possible)
+
+### When Can Amendment Be Denied?
+
+| Reason for Denial                                    | Description                                       |
+| ---------------------------------------------------- | ------------------------------------------------- |
+| Record was not created by the covered entity         | CE may not be in position to judge accuracy       |
+| Record is not part of the designated record set      | Outside scope of amendment right                  |
+| Record is accurate and complete                      | CE reasonably believes the information is correct |
+| Individual would not have right to access the record | e.g., psychotherapy notes                         |
+
+### If Amendment Accepted:
+
+- Covered entity must make the amendment in the designated record set
+- Notify the individual within 60 days
+- Inform relevant parties who received or might rely on the inaccurate PHI
+
+### If Amendment Denied:
+
+- Must provide written denial with reason
+- Individual may submit a written statement of disagreement
+- Covered entity may prepare a rebuttal
+- Disagreement and rebuttal must be appended to the record
+
+---
+
+## 4. Right to an Accounting of Disclosures (§ 164.528)
+
+Individuals have the right to receive an accounting of certain disclosures of their PHI made by the covered entity.
+
+### Lookback Period: 6 years prior to the date of request (but not before April 14, 2003)
+
+### Disclosures that MUST Be Included:
+
+All disclosures except those for:
+
+- Treatment, Payment, and Health Care Operations (TPO)
+- To the individual themselves
+- Pursuant to a valid authorization
+- Incidental to a permitted disclosure
+- National security or intelligence activities
+- Correctional institution or law enforcement custody
+- As part of a limited data set
+
+### Required Content per Disclosure Entry:
+
+| Field                              | Description                 |
+| ---------------------------------- | --------------------------- |
+| Date of disclosure                 | Specific date               |
+| Name and address of recipient      | Who received the PHI        |
+| Brief description of PHI disclosed | What information was shared |
+| Brief statement of purpose         | Why it was shared           |
+
+### Engineering Note: Accounting of Disclosures System
+
+A covered entity must have a logging system that:
+
+- Captures all required disclosures in real-time
+- Can generate reports filtered by individual
+- Covers the 6-year lookback period
+- Distinguishes TPO disclosures (excluded) from reportable disclosures
+- Is accessible to privacy officers for review
+
+---
+
+## 5. Right to Request Restrictions (§ 164.522)
+
+Individuals may request that a covered entity restrict:
+
+- Uses or disclosures for treatment, payment, or health care operations
+- Disclosures to persons involved in the individual's care
+- Disclosures for disaster relief purposes
+
+### Covered Entity's Obligation:
+
+- **Not required** to agree to the requested restriction
+- **Exception — must agree** if:
+  - The disclosure is to a health plan for payment/operations purposes
+  - The PHI pertains solely to a service or item for which the individual (or someone other than the health plan) paid out of pocket in full
+
+### If Covered Entity Agrees to Restriction:
+
+- Must comply with the restriction (except for emergencies)
+- Must inform the individual if restriction is to be terminated
+- Must have individuals agree to terminate the restriction before doing so (unless the individual is told at time of restriction agreement)
+
+---
+
+## 6. Right to Request Confidential Communications (§ 164.522(b))
+
+Individuals may request that a covered entity communicate with them about their PHI by **alternative means or at alternative locations**.
+
+**Example requests:**
+
+- "Send all correspondence to my P.O. box, not my home address"
+- "Call me only on my cell phone, never my home number"
+- "Do not leave voicemails"
+
+### Covered Entity's Obligation:
+
+- **Must accommodate** reasonable requests
+- **Cannot require** individuals to explain their reason for the request
+- May require information about how payment will be handled (if the alternative communication would otherwise be billed to the health plan)
+
+### Engineering Implementation:
+
+- Patient preference fields in profile system
+- Communication routing logic based on preferences
+- Do Not Call / Do Not Mail / Alternative Contact flags
+- Audit logging of communications sent vs. patient preferences
+
+---
+
+## 7. Right to Receive a Notice of Privacy Practices (§ 164.520)
+
+Every individual must receive or have access to a **Notice of Privacy Practices (NPP)** that clearly describes:
+
+| Required NPP Content    | Description                               |
+| ----------------------- | ----------------------------------------- |
+| Uses and disclosures    | How PHI may be used and disclosed         |
+| Individual rights       | Summary of all privacy rights             |
+| Covered entity's duties | CE's legal obligations to protect PHI     |
+| Complaint process       | How to file a complaint with CE and HHS   |
+| Effective date          | Date the NPP is effective                 |
+| Contact information     | Privacy Officer name or title and contact |
+
+### When NPP Must Be Provided:
+
+| Scenario                                 | Requirement                                        |
+| ---------------------------------------- | -------------------------------------------------- |
+| Health care providers (direct treatment) | At **first service delivery**                      |
+| Health plans                             | At enrollment, annual reminders                    |
+| Website                                  | Prominently posted if website exists               |
+| Electronic notice                        | With individual's agreement, can be sent via email |
+
+---
+
+## 8. Right to Opt Out of Fundraising Communications
+
+If a covered entity uses PHI for fundraising, individuals must be given a **clear and conspicuous opportunity to opt out** of receiving fundraising communications.
+
+Once an individual opts out:
+
+- Must not send any further fundraising communications
+- Must honor opt-outs **permanently** (not just for the current campaign)
+
+---
+
+## 9. Right to File a Complaint
+
+Individuals have the right to:
+
+- File a complaint with the covered entity's Privacy Officer
+- File a complaint with the HHS Office for Civil Rights (OCR)
+
+Covered entities may **not retaliate** against individuals for exercising their privacy rights or filing complaints.
+
+---
+
+## 10. Implementation Checklist for Patient Rights
+
+| Right                                | Technical Requirement                                             |
+| ------------------------------------ | ----------------------------------------------------------------- |
+| Right to Access                      | Patient portal with medical records download, 30-day SLA tracking |
+| Right to Amend                       | Amendment request workflow, record flagging system                |
+| Right to Accounting                  | Disclosure audit log, 6-year retention, patient-accessible report |
+| Right to Restrict                    | Restriction preference flags, TPO blocking logic                  |
+| Right to Confidential Communications | Alternative contact preferences, routing logic                    |
+| Right to Receive NPP                 | NPP on website, delivery tracking at intake                       |
+| Right to Opt Out of Fundraising      | Opt-out flag, suppression list integration                        |
+| Right to Complain                    | Complaint intake workflow, OCR complaint procedure documented     |
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `11-consent-vs-authorization.md`, `18-minimum-necessary-standard.md`

datasets/08-technical-safeguards-engineering.md

@@ -0,0 +1,415 @@
+# Technical Safeguards for Software Engineers — HIPAA Engineering Dataset
+
+**Source:** 45 CFR § 164.312, NIST SP 800-66  
+**Authority:** U.S. Department of Health and Human Services (HHS)  
+**Audience:** Software engineers, architects, DevSecOps, CTOs
+
+---
+
+## 1. Overview
+
+This dataset translates HIPAA Security Rule technical safeguards into actionable engineering requirements. It covers the architectural decisions, code-level controls, and infrastructure configurations necessary to build HIPAA-compliant systems.
+
+---
+
+## 2. Identity and Access Management (IAM)
+
+### 2.1 Unique User Identification (Required — § 164.312(a)(2)(i))
+
+Every user who accesses a system containing ePHI must have a **unique identifier**. Shared accounts are prohibited.
+
+```typescript
+// GOOD: UUID-based unique user identity
+const userId = crypto.randomUUID(); // Per-user, never shared
+
+// BAD: Shared service accounts
+const userId = "admin_shared"; // Prohibited for PHI access
+```
+
+### 2.2 Role-Based Access Control (RBAC)
+
+Map HIPAA's "minimum necessary" standard to RBAC:
+
+| Role            | PHI Access Level                         | Example              |
+| --------------- | ---------------------------------------- | -------------------- |
+| Patient         | Own records only                         | Patient portal users |
+| Clinical Staff  | Patients assigned to them                | Nurses, physicians   |
+| Billing Staff   | Billing-relevant PHI only                | Accounts receivable  |
+| Admin           | Operational data, no clinical details    | Scheduling staff     |
+| Privacy Officer | Full audit access                        | Compliance team      |
+| System Admin    | Infrastructure only — no clinical access | DevOps               |
+| AI/RAG Query    | Read-only scoped to authorized documents | AI agents            |
+
+### 2.3 Principle of Least Privilege
+
+```sql
+-- BAD: Broad database access
+GRANT ALL PRIVILEGES ON DATABASE healthcare_db TO app_user;
+
+-- GOOD: Scoped per role
+GRANT SELECT ON patient_demographics TO billing_service;
+GRANT SELECT, UPDATE ON clinical_notes TO clinician_service;
+GRANT SELECT ON audit_logs TO compliance_service;
+-- No role gets DELETE on PHI tables by default
+```
+
+### 2.4 Multi-Factor Authentication (MFA)
+
+Mandatory for:
+
+- All administrative access to systems containing ePHI
+- Remote access (VPN, SSH, bastion hosts)
+- Cloud management consoles (AWS Console, GCP Console)
+- EHR system access
+- Database administration tools
+
+---
+
+## 3. Encryption — At Rest
+
+### 3.1 Database Encryption
+
+| Level                                 | Approach                                                   | Notes                                                     |
+| ------------------------------------- | ---------------------------------------------------------- | --------------------------------------------------------- |
+| **Transparent Data Encryption (TDE)** | Full database encrypted at OS level                        | Minimal performance impact; protects against stolen disks |
+| **Column-Level Encryption**           | Encrypt specific PHI columns with application-managed keys | Strongest protection; enables granular access control     |
+| **Application-Level Encryption**      | Encrypt before writing to database                         | Key management in application layer                       |
+
+```sql
+-- Example: Column-level encryption with pgcrypto (PostgreSQL)
+-- Encrypt on write:
+UPDATE patient_phi
+SET ssn_encrypted = pgp_sym_encrypt(ssn_plaintext, current_setting('app.encryption_key'));
+
+-- Decrypt on read (only roles with key access can decrypt):
+SELECT pgp_sym_decrypt(ssn_encrypted, current_setting('app.encryption_key')) AS ssn
+FROM patient_phi
+WHERE user_id = $1;
+```
+
+### 3.2 File and Object Storage Encryption
+
+```
+# S3 Bucket — Server-Side Encryption Required
+aws s3api put-bucket-encryption \
+  --bucket my-hipaa-bucket \
+  --server-side-encryption-configuration '{
+    "Rules": [{
+      "ApplyServerSideEncryptionByDefault": {
+        "SSEAlgorithm": "aws:kms",
+        "KMSMasterKeyID": "arn:aws:kms:..."
+      }
+    }]
+  }'
+```
+
+### 3.3 Backup Encryption
+
+All backups containing ePHI must be encrypted before storage:
+
+- Encrypt before sending to S3/GCS/Azure Blob
+- Maintain encryption keys separately from encrypted data
+- Test decryption as part of backup verification process
+
+---
+
+## 4. Encryption — In Transit
+
+### 4.1 TLS Configuration
+
+```nginx
+# nginx TLS configuration for HIPAA compliance
+server {
+  listen 443 ssl;
+
+  ssl_certificate /path/to/cert.pem;
+  ssl_certificate_key /path/to/key.pem;
+
+  # TLS 1.2 minimum (1.3 preferred)
+  ssl_protocols TLSv1.2 TLSv1.3;
+
+  # Strong cipher suites only
+  ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384;
+  ssl_prefer_server_ciphers off;
+
+  # HSTS — force HTTPS
+  add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload";
+
+  # Prevent HTTP fallback
+  return 301 https://$host$request_uri;
+}
+```
+
+### 4.2 API Security Headers
+
+```typescript
+// Express.js security headers for HIPAA environments
+app.use(
+  helmet({
+    strictTransportSecurity: {
+      maxAge: 63072000,
+      includeSubDomains: true,
+      preload: true,
+    },
+    contentSecurityPolicy: {
+      directives: {
+        defaultSrc: ["'self'"],
+        connectSrc: ["'self'", "https://your-api-domain.com"],
+        // Block third-party analytics that may capture PHI
+        scriptSrc: ["'self'"],
+      },
+    },
+    referrerPolicy: { policy: "no-referrer" },
+  }),
+);
+```
+
+---
+
+## 5. Audit Logging Architecture
+
+### 5.1 Required Audit Log Fields
+
+```typescript
+interface HIPAAAuditLog {
+  event_id: string; // UUID
+  timestamp: string; // ISO 8601 UTC
+  user_id: string; // Who performed the action
+  user_role: string; // Role at time of action
+  patient_id: string; // Whose PHI was affected (if applicable)
+  resource_type: string; // Type of PHI resource accessed
+  resource_id: string; // Specific record ID
+  action: AuditAction; // READ | CREATE | UPDATE | DELETE | EXPORT | PRINT
+  outcome: "SUCCESS" | "FAILURE";
+  ip_address: string; // Originating IP
+  user_agent: string; // Client information
+  session_id: string; // Session identifier
+  request_id: string; // Request trace ID
+}
+```
+
+### 5.2 Immutable Audit Logs
+
+Audit logs must be write-once and tamper-evident:
+
+```sql
+-- PostgreSQL Row-Level Security for audit immutability
+ALTER TABLE audit_logs ENABLE ROW LEVEL SECURITY;
+
+-- Only INSERT allowed for the application role
+CREATE POLICY audit_insert_only ON audit_logs
+  FOR INSERT TO app_role WITH CHECK (true);
+
+-- No UPDATE or DELETE for any application role
+CREATE POLICY audit_no_update ON audit_logs
+  FOR UPDATE TO PUBLIC USING (false);
+
+CREATE POLICY audit_no_delete ON audit_logs
+  FOR DELETE TO PUBLIC USING (false);
+```
+
+### 5.3 Log Retention
+
+| Log Type               | Minimum Retention | Reason                               |
+| ---------------------- | ----------------- | ------------------------------------ |
+| Audit logs             | **6 years**       | HIPAA document retention requirement |
+| Access logs            | **6 years**       | Accounting of disclosures            |
+| Security incident logs | **6 years**       | Enforcement investigation support    |
+| System activity logs   | **6 years**       | OCR investigation support            |
+
+---
+
+## 6. Session Management
+
+### 6.1 Automatic Logoff (Addressable — § 164.312(a)(2)(iii))
+
+```typescript
+// Session configuration for HIPAA-compliant apps
+const session = {
+  // Maximum idle time: 15-30 minutes recommended
+  idleTimeoutMs: 15 * 60 * 1000,
+
+  // Absolute maximum session duration
+  absoluteTimeoutMs: 8 * 60 * 60 * 1000, // 8 hours
+
+  // Secure cookie settings
+  cookie: {
+    secure: true, // HTTPS only
+    httpOnly: true, // No JS access
+    sameSite: "strict", // CSRF protection
+    maxAge: 8 * 60 * 60 * 1000,
+  },
+};
+```
+
+### 6.2 JWT Token Security
+
+```typescript
+// JWT claims for HIPAA-aware tokens
+const tokenPayload = {
+  sub: userId,
+  role: userRole,
+  patient_scope: patientIds, // Limit which patients this token can access
+  iat: Math.floor(Date.now() / 1000),
+  exp: Math.floor(Date.now() / 1000) + 15 * 60, // 15-minute expiry
+  jti: crypto.randomUUID(), // Token ID for revocation tracking
+};
+
+// Token revocation list (for logout and breach response)
+const revokedTokens = new Set<string>();
+```
+
+---
+
+## 7. PHI Scrubbing in Logging Pipelines
+
+The most common source of accidental PHI disclosure is application logs.
+
+```typescript
+// Log sanitizer middleware
+const PHI_PATTERNS = [
+  { pattern: /\b\d{3}-\d{2}-\d{4}\b/g, replacement: "[SSN_REDACTED]" },
+  {
+    pattern: /\b[A-Za-z0-9._%+\-]+@[A-Za-z0-9.\-]+\.[A-Z|a-z]{2,}\b/g,
+    replacement: "[EMAIL_REDACTED]",
+  },
+  {
+    pattern: /\b\d{3}[-.]?\d{3}[-.]?\d{4}\b/g,
+    replacement: "[PHONE_REDACTED]",
+  },
+  {
+    pattern: /patient_id["':\s]+["']?[A-Za-z0-9\-]+["']?/g,
+    replacement: "patient_id: [REDACTED]",
+  },
+];
+
+function sanitizeForLogging(data: unknown): unknown {
+  if (typeof data === "string") {
+    return PHI_PATTERNS.reduce(
+      (str, { pattern, replacement }) => str.replace(pattern, replacement),
+      data,
+    );
+  }
+  if (typeof data === "object" && data !== null) {
+    return Object.fromEntries(
+      Object.entries(data as Record<string, unknown>).map(([k, v]) => [
+        k,
+        sanitizeForLogging(v),
+      ]),
+    );
+  }
+  return data;
+}
+```
+
+---
+
+## 8. Database Security Architecture
+
+### 8.1 PHI Table Isolation Pattern
+
+```
+┌─────────────────────────────────────────┐
+│             Application Layer           │
+├────────────────┬────────────────────────┤
+│  Operational   │     PHI Service        │
+│  DB (no PHI)   │  (strict controls)     │
+│                │  - Encrypted columns   │
+│  users         │  - Row-level security  │
+│  appointments  │  - Audit triggers      │
+│  billing_codes │  - No direct access    │
+└────────────────┴────────────────────────┘
+         ↑                    ↑
+    App credentials      PHI-specific
+    (broad access)       credentials
+                         (scoped, MFA)
+```
+
+### 8.2 Encryption Key Management
+
+```
+NEVER store encryption keys in:
+- Application code
+- Environment variables in plain text
+- Git repositories
+- Log files
+- The same database as encrypted data
+
+ALWAYS use:
+- AWS KMS / GCP Cloud KMS / Azure Key Vault
+- HashiCorp Vault for self-hosted
+- Separate key rotation schedule from data rotation
+- Key access logging as part of audit trail
+```
+
+---
+
+## 9. Prompt Injection and AI Security in Healthcare
+
+When deploying AI/RAG systems on PHI:
+
+| Attack Vector                 | Description                                                            | Defense                                                 |
+| ----------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------- |
+| **Prompt injection**          | User manipulates AI to expose system instructions or cross-tenant data | Input validation, sandboxed execution, output filtering |
+| **Data exfiltration via AI**  | AI summarizes or exports PHI to unauthorized parties                   | Output monitoring, access control on AI responses       |
+| **Jailbreak + PHI access**    | Jailbreak prompts combined with PHI context                            | System prompt hardening, refusal fine-tuning            |
+| **Indirect prompt injection** | PHI documents contain injected instructions                            | Document sanitization before ingestion                  |
+
+```typescript
+// PHI detection before AI ingestion
+async function validatePromptForPHI(prompt: string): Promise<void> {
+  const phi_indicators = [
+    /\b\d{3}-\d{2}-\d{4}\b/, // SSN pattern
+    /\b(DOB|date of birth|born on)\b/i, // Birth date references
+    /\b(patient|MRN|medical record)\s+#?\d+/i, // MRN references
+  ];
+
+  const containsPHI = phi_indicators.some((pattern) => pattern.test(prompt));
+
+  if (containsPHI) {
+    throw new Error(
+      "HIPAA VIOLATION DETECTED: Unmasked PHI identified in prompt. " +
+        "Apply context-preserving tokenization before AI submission.",
+    );
+  }
+}
+```
+
+---
+
+## 10. Infrastructure Security Controls Checklist
+
+### Network Security:
+
+- [ ] VPC with private subnets for databases and ePHI stores
+- [ ] No public internet exposure for database endpoints
+- [ ] Security groups restrict traffic to required ports only
+- [ ] VPN or private link for remote access
+- [ ] Network flow logs enabled
+
+### Compute Security:
+
+- [ ] OS patching automated and current (within 30 days of critical patches)
+- [ ] No root/administrator login enabled
+- [ ] SSH key-based authentication (no passwords)
+- [ ] Endpoint detection and response (EDR) installed
+- [ ] Full-disk encryption on all compute instances
+
+### Secrets Management:
+
+- [ ] All secrets stored in KMS / Vault
+- [ ] No secrets in environment variables or code
+- [ ] Secret rotation schedule in place
+- [ ] Secret access audit logging enabled
+
+### Monitoring and Alerting:
+
+- [ ] Real-time alerting on unusual access patterns
+- [ ] Failed login attempt thresholds
+- [ ] After-hours access alerts
+- [ ] Bulk data download alerts
+- [ ] Geo-anomaly alerts (access from unexpected countries)
+
+---
+
+**Related Datasets:** `02-hipaa-security-rule.md`, `10-cloud-computing-hipaa.md`, `09-real-world-compliance-pitfalls.md`, `16-rag-system-architecture.md`

datasets/09-real-world-compliance-pitfalls.md

@@ -0,0 +1,318 @@
+# Real-World HIPAA Compliance Pitfalls — Practitioner Dataset
+
+**Source:** Healthcare developer communities, r/hipaa, r/healthIT, r/cybersecurity, compliance officers, MSP forums  
+**Context:** Common real-world failures encountered by healthcare startups, software engineers, and MSPs
+
+---
+
+## 1. The MVP Delay Anti-Pattern
+
+### The Problem
+
+The most recurring theme in healthcare developer discussions is the fatal misconception that HIPAA compliance is a "feature" that can be bolted on after achieving product-market fit.
+
+> "We'll handle compliance once we have real customers."
+
+**Why this fails:**
+
+| Stage                         | Cost of Compliance Retrofit                                             |
+| ----------------------------- | ----------------------------------------------------------------------- |
+| Pre-launch (before users)     | Low — architectural changes are cheap                                   |
+| Post-launch (small user base) | Medium — requires downtime and refactoring                              |
+| Post-enterprise-contract      | Critical — 300-question security assessments; full data pipeline audits |
+| Post-breach                   | Catastrophic — regulatory penalties + reputational destruction          |
+
+### The Architectural Debt Cascade
+
+Startups that use real patient data on non-compliant infrastructure create compounding debt:
+
+1. Database built without column-level encryption → requires full migration
+2. No audit logging → 6-year retroactive gap in compliance record
+3. No BAAs signed → every prior data processing event was a violation
+4. No access controls → impossible to demonstrate minimum necessary compliance
+
+**Industry consensus:** HIPAA is a foundational infrastructure requirement from day one — not an administrative checklist.
+
+---
+
+## 2. Cloud Services Without BAAs
+
+### The Pattern
+
+Developers spin up services on popular platforms without verifying BAA availability:
+
+```
+Common mistakes:
+- Firebase Realtime Database used for patient data
+- Twilio SMS sending appointment reminders without BAA
+- Intercom handling patient support tickets without BAA
+- Netlify/Vercel form submissions collecting PHI without BAA
+- GitHub Copilot or AI coding tools processing code that contains PHI
+```
+
+### The Misconception: "HIPAA Compliant" Marketing
+
+Many vendors advertise themselves as "HIPAA Compliant." This marketing is meaningless without:
+
+1. A signed Business Associate Agreement (BAA)
+2. Proper configuration of the HIPAA-eligible features
+3. Evidence that PHI flows only through covered service tiers
+
+> **Example failure:** AWS S3 is HIPAA-eligible — but only if you've signed the AWS BAA AND configured the bucket with proper encryption, access controls, and logging. An unconfigured S3 bucket from an account without an AWS BAA is non-compliant regardless of the AWS marketing page.
+
+---
+
+## 3. Encryption Fallacy
+
+### The Belief
+
+"We encrypt data at rest and in transit — we're compliant."
+
+### Why This Is Wrong
+
+Encryption protects against **physical theft and network interception only**. It provides zero protection against:
+
+| Vulnerability                           | Example                                                 | Encryption Does NOT Help                              |
+| --------------------------------------- | ------------------------------------------------------- | ----------------------------------------------------- |
+| SQL injection                           | `SELECT * FROM patients WHERE id = '1' OR '1'='1'`      | Data is decrypted before query returns                |
+| IDOR (Insecure Direct Object Reference) | `/api/patient/123` accessible to any authenticated user | Encrypted at rest; decrypted on legitimate API call   |
+| Compromised credentials                 | Stolen session token used to access records             | Authenticated request bypasses encryption             |
+| Insider threat                          | Employee dumps database they have legitimate access to  | Access-controlled systems needed; not just encryption |
+| Over-permissive API                     | API returns all patients instead of current patient     | Scope validation is the control, not encryption       |
+
+### What Encryption Actually Covers
+
+Encryption satisfies the **breach notification safe harbor** — if encrypted data is stolen from storage (e.g., a hard drive), no notification is required. This is its primary regulatory benefit.
+
+---
+
+## 4. Logging Architecture Failures
+
+### Critical Failure Modes in Production Systems
+
+#### 4.1 Payload Logging
+
+```javascript
+// VIOLATION: Full HTTP request body logged
+app.use((req, res, next) => {
+  console.log("Request:", JSON.stringify(req.body)); // Contains PHI
+  next();
+});
+
+// Compliant: Sanitize before logging
+app.use((req, res, next) => {
+  logger.info("Request received", {
+    path: req.path,
+    method: req.method,
+    userId: req.user?.id, // Log user ID, not PHI content
+  });
+  next();
+});
+```
+
+#### 4.2 Third-Party APM Ingesting PHI
+
+Common scenario: Datadog or New Relic is configured to capture full request/response bodies for debugging. In a health app, these bodies contain patient data. The APM vendor receives PHI — and unless they've signed a BAA and the account is HIPAA-configured, this is a violation.
+
+**Resolution:**
+
+- Review what APM agents send by default
+- Configure PHI field scrubbing in APM SDK settings
+- Sign BAA with APM vendor (Datadog, Splunk, New Relic offer HIPAA options)
+- Use structured logging with explicit field allowlists instead of full payload capture
+
+#### 4.3 Error Reporting Context
+
+```python
+# VIOLATION: Sentry captures full request context including PHI
+sentry_sdk.capture_exception(error)
+# By default, captures: request URL, headers, body, session data
+
+# Compliant: Restrict Sentry data scrubbing
+sentry_sdk.init(
+    dsn=SENTRY_DSN,
+    before_send=sanitize_event,  # Custom PHI scrubber
+    send_default_pii=False       # Disable PII capture
+)
+```
+
+---
+
+## 5. Mobile Application Blind Spots
+
+### 5.1 Push Notifications
+
+A critical and often overlooked vulnerability: push notifications that contain clinical information are displayed on **device lock screens** — bypassing all OS-level device encryption.
+
+**Examples of HIPAA-violating push notification content:**
+
+- "Your oncology follow-up is scheduled for 3 PM tomorrow"
+- "Lab results for John Smith are ready"
+- "Reminder: HIV medication refill due"
+- "Dr. Johnson accepted your mental health appointment"
+
+**Compliant approach:**
+
+```
+GOOD: "You have a new message from your care team" (generic, no clinical detail)
+GOOD: "Your appointment reminder is available in the app"
+BAD:  "Mammogram results available: see Dr. Chen's notes"
+BAD:  "Refill for Metformin 500mg is ready at CVS Pharmacy"
+```
+
+### 5.2 Analytics SDK Leakage
+
+Analytics SDKs embedded in health apps (Firebase Analytics, Amplitude, Mixpanel) automatically capture:
+
+- Screen names (which may include condition-specific terms: "DiabetesManagement", "CancerTracker")
+- User properties (could include health metrics)
+- Event names (e.g., "blood_glucose_logged", "insulin_dose_recorded")
+- Deep link parameters (may contain diagnostic codes)
+
+**Mitigation:**
+
+- Audit every analytics event for PHI leakage
+- Use generic event names (not condition-specific)
+- Anonymize user IDs before sending to analytics platforms
+- Review SDK data collection docs carefully
+
+### 5.3 Clipboard Exposure
+
+Health applications that copy medical data (diagnoses, lab values, prescriptions) to the system clipboard expose that data to:
+
+- Other apps on the device (clipboard sniffing)
+- iCloud Clipboard sync to other devices
+- Screenshot sharing
+
+---
+
+## 6. Digital Marketing and Tracking Pixels
+
+### The Core Problem
+
+Healthcare organizations use marketing tools (Meta Pixel, Google Ads tags, GA4) to optimize ad spend. These tools automatically transmit **user behavior data** to advertising networks.
+
+When a patient:
+
+- Visits `/book-appointment/oncology`
+- Clicks a "Schedule HIV Test" button
+- Views a "diabetes management" page
+- Logs into a patient portal and navigates to specific condition pages
+
+...this behavioral data is sent to Meta/Google servers. Meta and Google **refuse to sign BAAs**. Therefore, this is an unauthorized disclosure of PHI.
+
+### Legal Enforcement
+
+The FTC and HHS have both issued guidance confirming that health-related tracking pixel use is a HIPAA violation. Multiple major healthcare organizations have faced enforcement actions and class action suits.
+
+**Examples of enforcement actions:**
+
+- Hospital website had Meta Pixel on appointment scheduling pages → $18.5M settlement
+- Telehealth platform used Google Analytics on authenticated patient pages → OCR investigation
+
+### Technical Solutions
+
+| Solution                            | Description                                                                         |
+| ----------------------------------- | ----------------------------------------------------------------------------------- |
+| **Server-side conversion tracking** | Send conversion events from your server to Meta/Google using hashed, non-PHI data   |
+| **Content Security Policy**         | Block third-party script execution on authenticated/PHI pages                       |
+| **Tag Manager rules**               | Suppress analytics tags on pages containing PHI (authenticated, condition-specific) |
+| **Proxy tracking**                  | Route analytics through your own server to strip PHI before forwarding              |
+| **Consent Management Platform**     | Obtain explicit HIPAA authorization before activating tracking (rare)               |
+
+---
+
+## 7. Customer Support System Exposure
+
+### The Pattern
+
+Patients submit support tickets containing medical information. Support staff forward issues with screenshots. Tickets are stored in platforms like Zendesk or Intercom that haven't signed BAAs.
+
+**Data flow:**
+
+```
+Patient submits "I can't access my lab results"
++ attaches screenshot of lab report
+     ↓
+Ticket stored in Zendesk (no BAA)
+     ↓
+Support agent copies screenshot to Slack channel (no BAA)
+     ↓
+Developer reviews screenshot in Sentry issue (may have BAA, may not)
+```
+
+**Every step without a BAA is a potential breach.**
+
+### Mitigation:
+
+- Sign BAAs with all support platforms used for healthcare customers
+- Train support staff to reject PHI-containing attachments
+- Build screenshot redaction into support intake workflows
+- Use compliant communication channels for PHI-containing support interactions
+
+---
+
+## 8. Consent vs. Authorization Confusion
+
+### The Semantic Problem
+
+Two of the most commonly confused terms in HIPAA compliance:
+
+| Term                       | Definition                                      | When Required                                                          |
+| -------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------- |
+| **Consent for Treatment**  | Patient agrees to receive treatment             | Required by many states; not HIPAA                                     |
+| **HIPAA Authorization**    | Patient authorizes a specific disclosure of PHI | Required for non-TPO disclosures                                       |
+| **Release of Information** | Process of providing PHI to a third party       | Requires either authorization, treatment purpose, or other legal basis |
+
+### The Practical Failure Modes
+
+1. **Over-authorization:** Clinics require HIPAA authorization for a patient to access their own records — this is **wrong**. The Right of Access does not require authorization.
+
+2. **Under-authorization:** Using a simple "consent for treatment" form to justify complex secondary disclosures (e.g., sharing records with research companies) — this is **wrong** and insufficient.
+
+3. **Overbroad authorization:** An authorization that says "you may share my information with any party for any purpose" — this fails the requirement that authorizations specify:
+   - Who may receive the PHI
+   - For what purpose
+   - What specific PHI
+   - An expiration date
+
+---
+
+## 9. EHR Integration Complexity
+
+### Interoperability ≠ Integration
+
+Organizations often confuse HL7 FHIR interoperability standards with practical integration:
+
+| Assumption                                                 | Reality                                                                |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------- |
+| "The EHR supports FHIR, so integration is straightforward" | FHIR is a standard, but implementations vary wildly between vendors    |
+| "Data exported from EHR is clean and structured"           | EHR data is frequently incomplete, inconsistent, and poorly structured |
+| "We can use the patient's data as-is"                      | Normalization and validation are required before processing            |
+
+### Data Quality Issues in EHR Feeds:
+
+- Duplicate patient records with conflicting data
+- Inconsistent coding (ICD-9 vs. ICD-10 vs. custom codes)
+- Missing required fields
+- Inconsistent date formats
+- Free-text fields containing structured data
+- Historical records not migrated from legacy systems
+
+---
+
+## 10. Workforce Training Failures
+
+The most overlooked administrative safeguard:
+
+| Training Gap                                  | Real-World Consequence                       |
+| --------------------------------------------- | -------------------------------------------- |
+| Staff not trained on phishing                 | Credentials stolen → unauthorized PHI access |
+| Staff not knowing correct disposal procedures | Paper PHI in recycling bins → breach         |
+| Staff sharing login credentials               | "It's easier" → no individual accountability |
+| Remote workers using personal devices         | PHI on unmanaged, unencrypted devices        |
+| Staff not knowing what counts as PHI          | Discussing patient cases in public spaces    |
+
+---
+
+**Related Datasets:** `05-business-associates.md`, `08-technical-safeguards-engineering.md`, `12-digital-marketing-tracking-risks.md`, `11-consent-vs-authorization.md`

datasets/10-cloud-computing-hipaa.md

@@ -0,0 +1,263 @@
+# HIPAA and Cloud Computing — Comprehensive Dataset
+
+**Source:** HHS Guidance on HIPAA & Cloud Computing  
+**Authority:** U.S. Department of Health and Human Services (HHS), NIST SP 800-145  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/special-topics/cloud-computing/index.html
+
+---
+
+## 1. Overview
+
+Cloud computing, as defined by NIST Special Publication 800-145, provides "ubiquitous, on-demand network access to a shared pool of configurable computing resources." The explosive adoption of cloud infrastructure in healthcare creates specific HIPAA compliance obligations that are broadly misunderstood.
+
+**Core Rule:** Any Cloud Service Provider (CSP) that creates, receives, maintains, or transmits ePHI on behalf of a covered entity or business associate is a **Business Associate** — regardless of whether the CSP holds decryption keys.
+
+---
+
+## 2. Cloud Service Models and HIPAA Applicability
+
+| Service Model                          | NIST Definition                 | HIPAA BA Status if Handling ePHI | BAA Required? |
+| -------------------------------------- | ------------------------------- | -------------------------------- | ------------- |
+| **SaaS** (Software as a Service)       | Vendor-managed application      | YES — BA                         | YES           |
+| **PaaS** (Platform as a Service)       | Application runtime environment | YES — BA                         | YES           |
+| **IaaS** (Infrastructure as a Service) | Compute, storage, networking    | YES — BA                         | YES           |
+
+### No-View CSP Rule
+
+HHS explicitly states: A CSP that stores only **encrypted** ePHI and has no ability to view, decrypt, or otherwise access the underlying information is **still a Business Associate**.
+
+> Reason: Even though the CSP cannot see the data, it "maintains" ePHI. The risk of an unauthorized disclosure exists at the infrastructure level.
+
+---
+
+## 3. HIPAA-Eligible Services by Major Provider
+
+### Amazon Web Services (AWS)
+
+AWS offers a BAA for HIPAA-eligible services. Not all AWS services are covered under the BAA.
+
+| HIPAA-Eligible AWS Services (Selected) | Not HIPAA-Eligible by Default        |
+| -------------------------------------- | ------------------------------------ |
+| EC2, ECS, EKS (compute)                | Most free-tier services              |
+| S3 (with encryption configured)        | CloudFront (requires careful config) |
+| RDS, Aurora (databases)                | Some IoT services                    |
+| Lambda (with proper config)            | Development/sandbox services         |
+| CloudWatch, CloudTrail (logging)       | AI/ML services (case-by-case)        |
+| KMS (key management)                   | —                                    |
+| VPC, Direct Connect (networking)       | —                                    |
+| Cognito (identity)                     | —                                    |
+
+**Action required:** Sign the AWS BAA in the account before processing any ePHI. The BAA is account-level; each account using ePHI needs its own BAA.
+
+### Google Cloud Platform (GCP)
+
+GCP offers a Cloud Data Processing Addendum (DPA) that serves as the HIPAA BAA.
+
+| HIPAA-Eligible GCP Services (Selected)        |
+| --------------------------------------------- |
+| Compute Engine, Google Kubernetes Engine      |
+| Cloud Storage                                 |
+| Cloud SQL, Cloud Spanner, Firestore, BigQuery |
+| Cloud Functions                               |
+| Cloud KMS                                     |
+| Cloud Logging, Cloud Monitoring               |
+| Healthcare API (FHIR, DICOM, HL7)             |
+
+**Note:** Google Healthcare API is purpose-built for HIPAA use cases with built-in FHIR support.
+
+### Microsoft Azure
+
+Azure provides a standard contractual clause for HIPAA/HITECH that covers most Azure services.
+
+| HIPAA-Covered Azure Services (Selected) |
+| --------------------------------------- |
+| Azure Virtual Machines                  |
+| Azure Blob Storage, Azure Files         |
+| Azure SQL Database, Cosmos DB           |
+| Azure Functions                         |
+| Azure Key Vault                         |
+| Azure Monitor, Log Analytics            |
+| Azure Active Directory                  |
+| Azure Health Data Services (FHIR)       |
+
+---
+
+## 4. Shared Responsibility Model in Healthcare
+
+Cloud providers operate on a **Shared Responsibility Model**. This model defines which security controls the vendor handles vs. which the customer must implement.
+
+| Responsibility Layer              | AWS                    | Customer |
+| --------------------------------- | ---------------------- | -------- |
+| Physical data center security     | ✓                      | —        |
+| Hardware and hypervisor security  | ✓                      | —        |
+| Network infrastructure            | ✓                      | —        |
+| OS patching (managed services)    | ✓                      | —        |
+| OS patching (EC2, self-managed)   | —                      | ✓        |
+| Database encryption at rest       | Configuration required | ✓        |
+| S3 bucket policies and ACLs       | Configuration required | ✓        |
+| Application-level access controls | —                      | ✓        |
+| User authentication and MFA       | —                      | ✓        |
+| Audit logging configuration       | —                      | ✓        |
+| Data classification               | —                      | ✓        |
+| PHI masking in logs               | —                      | ✓        |
+| BAA compliance                    | BAA execution          | ✓        |
+
+> **Critical insight:** Signing a BAA with a cloud provider does NOT make you compliant. The BAA establishes legal accountability. You still must configure every service correctly.
+
+---
+
+## 5. Common Cloud Misconfigurations
+
+### 5.1 Public S3 Buckets (AWS)
+
+One of the most frequently reported healthcare data exposures:
+
+```
+# Check for public access blocks (should all be TRUE)
+aws s3api get-public-access-block --bucket your-bucket-name
+
+Expected output:
+{
+  "PublicAccessBlockConfiguration": {
+    "BlockPublicAcls": true,
+    "IgnorePublicAcls": true,
+    "BlockPublicPolicy": true,
+    "RestrictPublicBuckets": true
+  }
+}
+```
+
+### 5.2 Database Exposure
+
+```
+# RDS PostgreSQL — ensure NOT publicly accessible
+aws rds describe-db-instances --query 'DBInstances[*].[DBInstanceIdentifier,PubliclyAccessible]'
+
+# Any 'true' value = violation for PHI databases
+```
+
+### 5.3 CloudTrail Not Enabled
+
+AWS CloudTrail must be enabled to satisfy audit logging requirements:
+
+```bash
+# Verify CloudTrail is logging all regions
+aws cloudtrail describe-trails
+aws cloudtrail get-trail-status --name your-trail-name
+
+# Verify log file validation is enabled
+# "LogFileValidationEnabled": true must appear in output
+```
+
+### 5.4 KMS Key Rotation
+
+```bash
+# Verify automatic key rotation is enabled for PHI encryption keys
+aws kms get-key-rotation-status --key-id your-key-id
+
+# "KeyRotationEnabled": true required for HIPAA best practice
+```
+
+---
+
+## 6. Multi-Tenant Cloud Architecture for Healthcare
+
+In a multi-tenant healthcare SaaS product, data isolation between tenants is critical:
+
+### Tenant Isolation Strategies:
+
+| Strategy                | Description                                | HIPAA Fit                                         |
+| ----------------------- | ------------------------------------------ | ------------------------------------------------- |
+| **Database per tenant** | Each customer gets a separate database     | Strong isolation; expensive at scale              |
+| **Schema per tenant**   | Shared DB, separate schemas                | Good isolation; manageable scale                  |
+| **Row-level security**  | Shared DB, shared schema with RLS policies | Most efficient; requires rigorous implementation  |
+| **Separate accounts**   | Each customer in separate cloud account    | Strongest isolation; highest operational overhead |
+
+**Recommended:** For regulated healthcare data (ePHI), row-level security with comprehensive audit logging at minimum; schema-per-tenant preferred for high-value clients.
+
+```sql
+-- PostgreSQL Row-Level Security for PHI tenant isolation
+CREATE POLICY tenant_isolation ON patient_phi
+  USING (organization_id = current_setting('app.current_org_id')::uuid);
+
+ALTER TABLE patient_phi ENABLE ROW LEVEL SECURITY;
+ALTER TABLE patient_phi FORCE ROW LEVEL SECURITY;
+```
+
+---
+
+## 7. Disaster Recovery and Business Continuity
+
+HIPAA Security Rule requires covered entities to have:
+
+- Data backup plan (§ 164.308(a)(7)(ii)(A) — Required)
+- Disaster recovery plan (§ 164.308(a)(7)(ii)(B) — Required)
+- Emergency mode operation plan (§ 164.308(a)(7)(ii)(C) — Required)
+- Testing and revision procedures (§ 164.308(a)(7)(ii)(D) — Addressable)
+
+### Recovery Time and Recovery Point Objectives for Healthcare Systems:
+
+| System Type                 | Target RTO | Target RPO   |
+| --------------------------- | ---------- | ------------ |
+| Emergency care systems      | < 1 hour   | < 15 minutes |
+| Inpatient clinical systems  | < 4 hours  | < 1 hour     |
+| Outpatient clinical systems | < 8 hours  | < 4 hours    |
+| Administrative systems      | < 24 hours | < 24 hours   |
+| Analytics/reporting         | < 72 hours | < 24 hours   |
+
+---
+
+## 8. Cloud-Native HIPAA Compliance Stack (Reference Architecture)
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    HIPAA Cloud Architecture                  │
+├─────────────────────────────────────────────────────────────┤
+│  WAF (Web Application Firewall)                             │
+│    └── Blocks injection attacks, rate limiting              │
+├─────────────────────────────────────────────────────────────┤
+│  API Gateway (HTTPS only, TLS 1.2+)                         │
+│    └── JWT validation, rate limiting, request logging       │
+├─────────────────────────────────────────────────────────────┤
+│  Application Layer (Private Subnet)                         │
+│    └── Containerized services (ECS/EKS)                    │
+│    └── No direct internet access                           │
+│    └── Secrets from KMS/Vault only                         │
+├─────────────────────────────────────────────────────────────┤
+│  Data Layer (Isolated Private Subnet)                       │
+│    └── RDS/PostgreSQL with encryption at rest              │
+│    └── Column-level encryption for PHI fields              │
+│    └── No public endpoint                                  │
+│    └── Automated backups to encrypted S3                   │
+├─────────────────────────────────────────────────────────────┤
+│  Security and Compliance Layer                              │
+│    └── CloudTrail / Cloud Logging (all API calls)          │
+│    └── GuardDuty / Security Command Center                 │
+│    └── Config rules (compliance monitoring)                │
+│    └── SIEM integration (immutable log aggregation)        │
+├─────────────────────────────────────────────────────────────┤
+│  Key Management                                             │
+│    └── KMS customer-managed keys                          │
+│    └── Automatic annual rotation                          │
+│    └── Key usage logging                                  │
+└─────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## 9. Zero-Trust Architecture for Healthcare
+
+Zero-trust ("never trust, always verify") is increasingly recommended for HIPAA environments:
+
+| Zero-Trust Principle       | Healthcare Implementation                            |
+| -------------------------- | ---------------------------------------------------- |
+| Verify explicitly          | MFA for all access; continuous session validation    |
+| Use least privilege access | RBAC scoped to minimum necessary PHI                 |
+| Assume breach              | Lateral movement prevention; micro-segmentation      |
+| Log everything             | Comprehensive audit trails; anomaly detection        |
+| Encrypt in transit         | mTLS between services; no plaintext internal traffic |
+| Device compliance          | MDM enrollment required before PHI access            |
+
+---
+
+**Related Datasets:** `05-business-associates.md`, `02-hipaa-security-rule.md`, `08-technical-safeguards-engineering.md`

datasets/11-consent-vs-authorization.md

@@ -0,0 +1,215 @@
+# Consent, Authorization, and Release of Information — HIPAA Dataset
+
+**Source:** 45 CFR §§ 164.506, 164.508, 164.524  
+**Authority:** U.S. Department of Health and Human Services (HHS)
+
+---
+
+## 1. Overview: The Three Distinct Concepts
+
+One of the most frequently cited administrative failures in HIPAA compliance is the **semantic and legal confusion** between three distinct concepts:
+
+| Concept                   | HIPAA Term                     | Purpose                                      | Required By HIPAA?                              |
+| ------------------------- | ------------------------------ | -------------------------------------------- | ----------------------------------------------- |
+| **Consent for Treatment** | "Consent"                      | Patient agrees to receive medical care       | NO — not required by HIPAA (state law may vary) |
+| **HIPAA Authorization**   | "Authorization"                | Patient authorizes a specific PHI disclosure | YES — required for non-TPO disclosures          |
+| **Right of Access**       | "Individual's Right of Access" | Patient receives their own records           | NO authorization required — it's a legal right  |
+
+---
+
+## 2. Consent for Treatment
+
+### What It Is
+
+Consent for treatment is a patient's agreement to receive medical care. It is a concept from medical ethics and state law — **not a HIPAA requirement**.
+
+### What It Is NOT
+
+Consent for treatment does **NOT** authorize disclosures of PHI beyond what is necessary for treatment. Using a consent for treatment form to justify sharing PHI with third parties (researchers, marketers, data brokers) is a HIPAA violation.
+
+### Common Misuse Pattern
+
+```
+WRONG: Patient signs a "consent for treatment" form.
+       Organization uses this consent to share patient records with a
+       pharmaceutical company for marketing purposes.
+       → HIPAA VIOLATION — separate authorization required
+
+WRONG: Organization requires a patient to sign a HIPAA authorization
+       form just to access their own medical records.
+       → HIPAA VIOLATION — right of access does not require authorization
+```
+
+---
+
+## 3. HIPAA Authorization (§ 164.508)
+
+### When Authorization is Required
+
+A valid HIPAA authorization is required for any use or disclosure of PHI that is **not permitted** by the Privacy Rule for Treatment, Payment, or Healthcare Operations.
+
+**Always requires authorization:**
+
+- Disclosures for marketing purposes (with narrow exceptions)
+- Sale of PHI
+- Uses or disclosures of psychotherapy notes (except by the originating provider for treatment)
+- Research that does not qualify for a waiver
+- Uses for purposes not related to TPO
+
+### Core Elements of a Valid Authorization
+
+A HIPAA authorization is only valid if it contains **all** of the following:
+
+| Element                             | Description                                                                     | Example                                                                     |
+| ----------------------------------- | ------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
+| **Description of PHI**              | Specific and meaningful description of the information to be used or disclosed  | "Medical records from visits between January 1, 2024 and December 31, 2024" |
+| **Authorized Recipients**           | Name(s) of the person(s) or class of persons to whom the disclosure may be made | "XYZ Research Institute"                                                    |
+| **Authorized Requestors**           | Who is authorized to make the use or disclosure                                 | "ABC Healthcare Clinic"                                                     |
+| **Purpose**                         | Each purpose for which the information will be used                             | "Cancer research study approved by IRB #2024-001"                           |
+| **Expiration**                      | Expiration date or expiration event                                             | "December 31, 2025" or "Upon completion of the research study"              |
+| **Individual's Signature and Date** | Valid signature of the patient or personal representative                       | Signed handwritten or electronic signature                                  |
+| **Right to Revoke Statement**       | Individual must be informed they may revoke the authorization                   | "You may revoke this authorization at any time..."                          |
+| **Consequences of Refusal**         | Whether treatment, payment, or enrollment depends on authorization (if it does) | "Your treatment will not be conditioned on signing this form"               |
+| **Re-disclosure Statement**         | Whether disclosed information may be re-disclosed and is no longer protected    | Required if applicable                                                      |
+
+### What Makes an Authorization Invalid
+
+An authorization is **not valid** if:
+
+- It has expired
+- It was not filled out completely
+- The covered entity knows it has been revoked
+- Contains conditions prohibited by HIPAA (conditioning treatment on signing for non-TPO uses)
+- Was combined with another document in violation of compound authorization rules
+
+---
+
+## 4. Authorization Compound Rules
+
+HIPAA prohibits combining certain types of authorizations:
+
+| Prohibited Combination                                          | Rule                                  |
+| --------------------------------------------------------------- | ------------------------------------- |
+| Psychotherapy notes authorization + authorization for other PHI | Cannot be combined — must be separate |
+| Research authorization + other authorizations                   | May be combined for research only     |
+| Conditioned authorization + unconditioned authorization         | Cannot be combined                    |
+
+---
+
+## 5. Right of Access vs. Authorization
+
+This is the most common administrative confusion:
+
+### Patient's Right to Their Own Records
+
+Under § 164.524, a patient has the **right to access their own designated record set** without providing an authorization.
+
+| Aspect                       | Right of Access                    | Authorization                                |
+| ---------------------------- | ---------------------------------- | -------------------------------------------- |
+| Who initiates                | Patient requests their own records | Patient authorizes disclosure to third party |
+| Authorization form required? | **NO**                             | **YES**                                      |
+| Timeline                     | 30 days (60 with extension)        | Depends on use — no fixed timeline           |
+| Can be denied?               | Only in limited circumstances      | Patient can revoke anytime                   |
+| Fee allowed?                 | Reasonable cost-based fee only     | No fee restrictions                          |
+
+### What Covered Entities Cannot Do
+
+- Require a patient to complete an authorization form to access their own records
+- Require a patient to explain why they want their records
+- Require a patient to use a specific EHR portal if they request a different format
+- Charge excessive fees for access
+
+---
+
+## 6. Release of Information (ROI)
+
+Release of Information (ROI) is the operational process through which PHI is provided to a requestor. It is the **mechanism** by which authorizations and access rights are operationalized.
+
+### Permissible Bases for ROI
+
+| Basis                             | Description                                       |
+| --------------------------------- | ------------------------------------------------- |
+| **Patient's own right of access** | No authorization needed; 30-day response timeline |
+| **Valid HIPAA authorization**     | Must verify all required elements are present     |
+| **Treatment relationship**        | Treating provider requesting for care purposes    |
+| **Payment activities**            | Insurer requesting for billing/claims             |
+| **Healthcare operations**         | Quality improvement, accreditation, auditing      |
+| **Required by law**               | Court order, subpoena, public health reporting    |
+| **Law enforcement**               | Limited purposes with proper legal process        |
+
+### ROI Verification Checklist:
+
+Before releasing any PHI:
+
+- [ ] Is the requestor authorized to receive this information?
+- [ ] Does the authorization cover the specific records requested?
+- [ ] Has the authorization expired?
+- [ ] Has the patient revoked the authorization?
+- [ ] Is the request limited to minimum necessary PHI?
+- [ ] Is the request logged in the disclosure accounting system?
+- [ ] Is the recipient's identity verified?
+
+---
+
+## 7. Psychotherapy Notes — Special Rules
+
+Psychotherapy notes receive **heightened protection** under HIPAA:
+
+| Rule                              | Description                                                                                                                                                  |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Definition**                    | Notes by a mental health professional documenting or analyzing the content of a therapy session, kept separate from the rest of the patient's medical record |
+| **Authorization always required** | Cannot be disclosed even for TPO without explicit authorization                                                                                              |
+| **Exceptions**                    | Treatment by the originating therapist; oversight activities; legal defense; serious threat to health/safety; required by law                                |
+| **Cannot be combined**            | Psychotherapy notes authorization must be separate from all other authorizations                                                                             |
+| **Right of access limitation**    | Covered entity may deny access to psychotherapy notes                                                                                                        |
+
+---
+
+## 8. Minor Patient Edge Cases
+
+### The Problem
+
+When a minor patient controls access to their own encounter data, legal complexity multiplies because:
+
+- HIPAA generally allows parents/guardians to access minors' records as personal representatives
+- **Exception:** When the minor is the personal representative of their own care (i.e., can consent to care under state law without parental consent)
+
+### Scenarios Where Minor Controls Their Own Records:
+
+| Scenario                                           | Varies by State                          |
+| -------------------------------------------------- | ---------------------------------------- |
+| Reproductive healthcare (contraception, pregnancy) | YES — many states allow minor to consent |
+| STI testing and treatment                          | YES — most states allow minor to consent |
+| Mental health treatment                            | YES — varies significantly by state      |
+| Substance abuse treatment                          | YES — federal 42 CFR Part 2 applies      |
+
+### Engineering Implication:
+
+Multi-state healthcare platforms must implement **state-specific access control rules** for minor patient records. A one-size-fits-all approach to parental access is non-compliant in many states.
+
+---
+
+## 9. Accounting of Authorizations and Disclosures
+
+Organizations must maintain records of:
+
+- All authorizations received (stored for 6 years)
+- All disclosures made pursuant to authorizations
+- All disclosures made without authorization (for accounting purposes)
+- Revocations of authorizations
+
+---
+
+## 10. Revocation of Authorization
+
+Patients may revoke a previously granted authorization at any time, in writing.
+
+**Effect of revocation:**
+
+- Covered entity must honor revocation for future disclosures
+- Revocation does NOT affect disclosures already made while authorization was valid
+- Covered entity must document the revocation
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `07-patient-rights.md`, `09-real-world-compliance-pitfalls.md`

datasets/12-digital-marketing-tracking-risks.md

@@ -0,0 +1,224 @@
+# Digital Marketing and PHI Tracking Risks — HIPAA Dataset
+
+**Source:** HHS Office for Civil Rights (OCR) guidance, FTC enforcement actions  
+**Relevant Rules:** HIPAA Privacy Rule § 164.502, FTC Section 5 (unfair/deceptive practices)
+
+---
+
+## 1. Overview
+
+The intersection of digital marketing technologies and healthcare represents one of the fastest-growing HIPAA liability vectors. Technologies including the Meta Pixel, Google Analytics, LinkedIn Insight Tag, and other client-side tracking scripts are **fundamentally incompatible** with HIPAA requirements when deployed on pages where patients may disclose health information.
+
+**Core Problem:** Client-side tracking scripts automatically collect and transmit user behavior data to third-party advertising networks. Major advertising platforms (Meta, Google) universally refuse to sign Business Associate Agreements. Therefore, any PHI transmitted through these channels is an unauthorized disclosure.
+
+---
+
+## 2. What Constitutes PHI in a Digital Marketing Context
+
+The following user behaviors on healthcare websites constitute disclosures of PHI when they identify or can be used to identify an individual:
+
+| User Action                                      | PHI Component                           | Why It's PHI                                     |
+| ------------------------------------------------ | --------------------------------------- | ------------------------------------------------ |
+| Navigating to `/diabetes-management` after login | Health condition + user identity        | Reveals condition to third party                 |
+| Clicking "Schedule Oncology Appointment"         | Health condition + user intent          | Reveals cancer-related health condition          |
+| Filling out a symptom checker form               | Health condition information            | Direct PHI disclosure                            |
+| Viewing a specific medication page in a portal   | Medication = health condition           | Reveals treatment information                    |
+| Completing a "Find a Therapist" form             | Mental health status                    | Reveals mental health condition                  |
+| Booking an HIV test appointment                  | Health condition                        | Highly sensitive condition disclosure            |
+| Patient portal login + navigation pattern        | Identity + health record access pattern | Combined = individually identifiable health info |
+
+---
+
+## 3. Tracking Technologies at Risk
+
+### 3.1 Meta Pixel (Facebook Pixel)
+
+The Meta Pixel is a JavaScript snippet that:
+
+- Fires on page load and user interaction events
+- Sends to Meta: URL visited, actions performed, IP address, browser fingerprint, referrer
+- Enables retargeting of users based on pages visited
+
+**Meta's BAA Policy:** Meta does not offer Business Associate Agreements for any service.
+
+**Consequence:** Any healthcare organization using Meta Pixel on:
+
+- Appointment scheduling pages
+- Patient portal pages
+- Condition-specific landing pages
+- Mental health, reproductive health, or substance abuse pages
+
+...is **in violation of HIPAA** with every pixel fire.
+
+**Documented enforcement:** Multiple hospital networks and telehealth companies have faced multi-million dollar class action suits and OCR investigations for Meta Pixel use on patient-facing pages.
+
+### 3.2 Google Analytics 4 (GA4) — Client-Side
+
+Standard Google Analytics client-side (gtag.js) implementation:
+
+- Sends to Google: page URL, user interactions, Google/device IDs, IP address
+- Google does not sign BAAs for standard GA4 accounts
+
+**Note:** Google Analytics 360 (enterprise, paid tier) offers a BAA specifically for users who are covered entities. Standard GA4 does not.
+
+### 3.3 LinkedIn Insight Tag
+
+- Tracks page visits and conversions, sends to LinkedIn
+- LinkedIn does not offer healthcare BAAs
+
+### 3.4 TikTok Pixel, Pinterest Tag, Twitter Pixel
+
+- None offer HIPAA BAAs
+- Cannot be deployed on any authenticated or PHI-touching pages
+
+---
+
+## 4. The Compliant Digital Marketing Stack
+
+### 4.1 Server-Side Tracking Architecture
+
+Server-side conversion API eliminates the client-side privacy risk:
+
+```
+Traditional Client-Side (VIOLATION):
+User Browser → pixel.js → Meta/Google Servers
+(URL, health condition, user ID all transmitted)
+
+Compliant Server-Side:
+User Browser → Your Server (de-identified conversion event)
+Your Server → Meta Conversion API / Google Enhanced Conversions
+(Only sends hashed, non-PHI data: hashed email, hashed phone)
+```
+
+**How it works:**
+
+1. User converts on your site (books appointment, fills out form)
+2. Your server receives the event
+3. Server strips all PHI and sends only hashed demographic data (optional) and conversion metadata
+4. Meta/Google Ads conversion API receives conversion signal without PHI
+
+### 4.2 Content Security Policy (CSP)
+
+Block third-party tracking scripts on authenticated or PHI-touching pages:
+
+```html
+<!-- Non-authenticated pages (marketing) — tracking allowed -->
+<meta
+  http-equiv="Content-Security-Policy"
+  content="script-src 'self' https://connect.facebook.net https://www.googletagmanager.com;"
+/>
+
+<!-- Authenticated patient pages — tracking blocked -->
+<meta
+  http-equiv="Content-Security-Policy"
+  content="script-src 'self'; connect-src 'self';"
+/>
+```
+
+### 4.3 Tag Manager Configuration
+
+Google Tag Manager rule to suppress all tracking on authenticated pages:
+
+```javascript
+// GTM Custom Variable: isAuthenticatedPage
+// Returns true if user is logged into patient portal
+
+function() {
+  return (
+    window.location.pathname.startsWith('/portal') ||
+    window.location.pathname.startsWith('/patient') ||
+    document.cookie.includes('auth_session=') ||
+    window.__isAuthenticated === true
+  );
+}
+
+// GTM Trigger: Fire tracking tags ONLY when isAuthenticatedPage = false
+```
+
+---
+
+## 5. HIPAA-Compliant Analytics Alternatives
+
+When standard analytics tools cannot be used, these alternatives support BAAs:
+
+| Tool                      | BAA Available                   | Notes                                                             |
+| ------------------------- | ------------------------------- | ----------------------------------------------------------------- |
+| **Google Analytics 360**  | YES — with enterprise agreement | Expensive; requires specific healthcare configuration             |
+| **Piwik PRO**             | YES                             | European-based, privacy-first analytics; healthcare BAA available |
+| **Mixpanel (HIPAA tier)** | YES — with enterprise agreement | Requires HIPAA add-on                                             |
+| **Amplitude (HIPAA)**     | YES — enterprise tier           | Requires HIPAA business associate agreement                       |
+| **AWS Pinpoint**          | YES — via AWS BAA               | Event tracking within AWS ecosystem                               |
+| **Segment (HIPAA)**       | YES — Business/Enterprise       | CDP with HIPAA support; controls data routing                     |
+
+---
+
+## 6. Web Beacon and Email Tracking
+
+Email tracking pixels are also a liability:
+
+| Scenario                                       | Risk                                                                    |
+| ---------------------------------------------- | ----------------------------------------------------------------------- |
+| Appointment reminder email with tracking pixel | Pixel fires = sends to email provider that ePHI was opened              |
+| Marketing email with open-tracking             | If sent to patients about conditions, opening behavior = PHI disclosure |
+| Click tracking on health-related email links   | Click path reveals health topics                                        |
+
+**Compliant email approach:**
+
+- Use HIPAA-compliant email platforms with BAAs (Paubox, LuxSci, Proton Business for healthcare)
+- Disable tracking pixels in transactional health emails
+- Use secure, encrypted email for any PHI communications
+
+---
+
+## 7. Cookie Consent and HIPAA
+
+**Key distinction:** GDPR/CCPA cookie consent frameworks do NOT satisfy HIPAA.
+
+| Framework           | What It Covers                                     | Does It Satisfy HIPAA?                                    |
+| ------------------- | -------------------------------------------------- | --------------------------------------------------------- |
+| GDPR consent banner | EU user consent for tracking                       | NO                                                        |
+| CCPA opt-out        | California consumer data rights                    | NO                                                        |
+| HIPAA Authorization | Patient authorization for specific PHI disclosures | YES — but only for that disclosure, not general marketing |
+
+A consent banner saying "we use cookies to improve your experience" does **not** constitute a valid HIPAA authorization for disclosing PHI to advertising networks.
+
+---
+
+## 8. Regulatory Enforcement Landscape
+
+### OCR (HHS Office for Civil Rights)
+
+OCR has issued explicit guidance that use of tracking technologies that transmit PHI to third parties without BAAs violates the Privacy and Security Rules. Issued December 2022 and updated March 2024.
+
+**OCR Bulletin Key Points:**
+
+- Tracking technologies on patient portals and other authenticated pages constitute impermissible disclosures
+- IP addresses combined with health condition page visits = PHI under specific circumstances
+- Regulated entities must conduct risk analyses specific to tracking technology use
+
+### FTC
+
+The FTC has brought enforcement actions under Section 5 (unfair and deceptive practices) against health companies for tracking pixel disclosures. FTC Health Breach Notification Rule also applies to health apps not covered by HIPAA.
+
+### State Attorneys General
+
+Multiple state AGs (Washington, Illinois, Connecticut) have brought actions under state health privacy laws that are more stringent than HIPAA.
+
+---
+
+## 9. Audit Checklist: Marketing Technology Review
+
+- [ ] Inventory all third-party scripts loaded on any page where patients can identify themselves or log in
+- [ ] Map which pages are accessible to authenticated patients
+- [ ] For every tracking script: verify BAA status with vendor
+- [ ] Remove or block all non-BAA scripts from authenticated pages
+- [ ] Implement CSP headers blocking third-party scripts on patient-facing pages
+- [ ] Configure GTM to suppress non-compliant tags on health-condition pages
+- [ ] Move conversion tracking to server-side APIs
+- [ ] Review email marketing platform for BAA coverage
+- [ ] Audit analytics dashboards — are they built on BAA-covered tools?
+- [ ] Document all decisions and risk assessments
+
+---
+
+**Related Datasets:** `05-business-associates.md`, `09-real-world-compliance-pitfalls.md`, `01-hipaa-privacy-rule.md`

datasets/13-hitech-act.md

@@ -0,0 +1,185 @@
+# HITECH Act — Comprehensive Dataset
+
+**Source:** Health Information Technology for Economic and Clinical Health (HITECH) Act, 2009  
+**Codified:** 42 U.S.C. §§ 17921–17954  
+**Authority:** U.S. Department of Health and Human Services (HHS)
+
+---
+
+## 1. Overview
+
+The Health Information Technology for Economic and Clinical Health (HITECH) Act was enacted as part of the American Recovery and Reinvestment Act (ARRA) of 2009. HITECH fundamentally transformed HIPAA enforcement and expanded the scope of healthcare data privacy requirements.
+
+**Primary objectives of HITECH:**
+
+1. Promote adoption and meaningful use of health information technology (specifically EHRs)
+2. Strengthen HIPAA privacy and security protections
+3. Expand civil and criminal penalties for HIPAA violations
+4. Extend direct HIPAA liability to business associates
+
+---
+
+## 2. Key HITECH Provisions
+
+### 2.1 Direct Business Associate Liability
+
+Before HITECH, only covered entities faced direct HIPAA enforcement. HITECH changed this:
+
+**Before HITECH (pre-2009):**
+
+- Business associates were bound only through their BAA with the covered entity
+- No direct government enforcement against BAs
+- BAs were only civilly liable to the covered entity
+
+**After HITECH (2009) → Codified by Omnibus Rule (2013):**
+
+- Business associates are directly subject to HIPAA
+- OCR can investigate and penalize BAs directly
+- Subcontractors of BAs also directly liable
+- Civil monetary penalties apply to BAs as well as covered entities
+
+### 2.2 Enhanced Civil Monetary Penalties
+
+HITECH introduced a tiered penalty structure based on culpability:
+
+| Violation Category                                                     | Per Violation     | Annual Cap |
+| ---------------------------------------------------------------------- | ----------------- | ---------- |
+| **Did not know** (reasonable diligence could not have known)           | $100 – $50,000    | $1,919,173 |
+| **Reasonable cause** (knew or should have known; not willful neglect)  | $1,000 – $50,000  | $1,919,173 |
+| **Willful neglect, corrected** (corrected within 30 days of discovery) | $10,000 – $50,000 | $1,919,173 |
+| **Willful neglect, not corrected**                                     | $50,000           | $1,919,173 |
+
+> **Note:** The annual cap applies per violation category, per year. An organization can face up to $1.9M per category, meaning a single breach involving multiple violations can result in penalties exceeding $5M annually.
+
+### 2.3 Breach Notification Requirement
+
+HITECH introduced mandatory breach notification, later codified in 45 CFR §§ 164.400–414 (the Breach Notification Rule). Key provisions:
+
+- **60-day notification window** for individual notice
+- **500+ person breaches** require simultaneous HHS notification and media notice
+- **Annual log** for breaches affecting fewer than 500 individuals
+- **Business associate notification** to covered entity without unreasonable delay
+
+### 2.4 Accounting of Disclosures Expansion (Future Provision)
+
+HITECH required HHS to establish regulations expanding the accounting of disclosures to include disclosures made through Electronic Health Records for treatment, payment, and operations (which were previously excluded). As of 2026, HHS has proposed but not finalized this rule.
+
+---
+
+## 3. Meaningful Use and Electronic Health Records
+
+HITECH created the EHR Incentive Programs (later renamed Promoting Interoperability) to drive adoption of certified EHR technology.
+
+### Meaningful Use Stages:
+
+| Stage       | Period    | Focus                       |
+| ----------- | --------- | --------------------------- |
+| **Stage 1** | 2011–2012 | Data capture and sharing    |
+| **Stage 2** | 2014      | Advanced clinical processes |
+| **Stage 3** | 2017+     | Improved outcomes           |
+
+### Certified EHR Technology (CEHRT) Requirements:
+
+For software vendors building EHR-integrated applications, the ONC (Office of the National Coordinator) requires certified technology to meet:
+
+- Interoperability standards (HL7 FHIR)
+- Security requirements
+- Privacy protections
+- Patient access capabilities
+
+---
+
+## 4. HITECH and Patient Access Rights
+
+HITECH strengthened patient access rights, including:
+
+- **Electronic access:** Patients must be able to receive an electronic copy of their records from EHR systems
+- **Transmission:** Covered entities must accommodate requests to transmit ePHI directly to a third party designated by the individual
+- **Reduced fees:** No or very low fees for electronic copies (labor for copying only)
+
+---
+
+## 5. HITECH and Security Rule Strengthening
+
+HITECH required all covered entities and business associates to:
+
+- Implement HIPAA Security Rule safeguards (previously only strongly encouraged)
+- Conduct regular risk analyses
+- Apply civil penalties to willful neglect with no reasonable cause exception (willful neglect = automatic penalty)
+
+---
+
+## 6. 42 CFR Part 2 — Substance Abuse Records
+
+While technically separate from HITECH, healthcare AI systems must understand 42 CFR Part 2 (Confidentiality of Substance Use Disorder Patient Records), which provides **stricter protections** than HIPAA for substance use disorder (SUD) records:
+
+| Aspect               | HIPAA                                   | 42 CFR Part 2                                                             |
+| -------------------- | --------------------------------------- | ------------------------------------------------------------------------- |
+| Treatment disclosure | Permitted without authorization for TPO | Requires patient authorization for most disclosures                       |
+| Law enforcement      | Can disclose with proper legal process  | Highly restricted; cannot be used in criminal proceedings without consent |
+| Re-disclosure        | Permitted with appropriate controls     | Generally prohibited without patient consent                              |
+| AI/RAG use           | De-identified data may be used          | Extra caution required; SUD diagnoses = ultra-sensitive PHI               |
+
+---
+
+## 7. HITECH and AI/Technology Implications
+
+### 7.1 Increased Enforcement in Tech-Adjacent Healthcare
+
+HITECH's enhanced penalties have been applied to:
+
+- Health apps that suffered data breaches
+- Cloud service providers without BAAs
+- Telehealth platforms with inadequate security
+- EHR systems with insufficient access controls
+
+### 7.2 State-Level HITECH-Like Laws
+
+Several states have enacted laws that go beyond HITECH and HIPAA:
+
+| State      | Law                                               | Key Provision                                               |
+| ---------- | ------------------------------------------------- | ----------------------------------------------------------- |
+| California | CMIA (Confidentiality of Medical Information Act) | Stricter than HIPAA; penalties up to $250,000 per violation |
+| Washington | My Health MY Data Act (2023)                      | Extends beyond HIPAA to cover consumer health data          |
+| Nevada     | NRS 603A                                          | Strict data security requirements                           |
+| Texas      | Texas Medical Records Privacy Act                 | Stricter consent requirements                               |
+| New York   | SHIELD Act                                        | Comprehensive breach notification                           |
+
+---
+
+## 8. ONC Interoperability and Information Blocking Rule
+
+The 21st Century Cures Act (2016) and subsequent ONC rules prohibit "information blocking" — practices that interfere with access, exchange, or use of electronic health information.
+
+**Key provisions for developers:**
+
+- Health IT developers cannot build systems that intentionally prevent data sharing (with narrow exceptions)
+- APIs must be available for patients and third parties to access EHR data
+- FHIR R4 compliance required for all certified EHR systems
+
+**Exceptions to information blocking prohibition:**
+
+1. Privacy Exception — protecting patient privacy
+2. Security Exception — preventing security threats
+3. Preventing Harm Exception — protecting patient or population safety
+4. Infeasibility Exception — technical or practical infeasibility
+5. Health IT Performance Exception — system maintenance
+6. Content and Manner Exception — reasonable business terms
+7. Licensing Exception — reasonable IP licensing
+8. Fees Exception — reasonable fees for data access
+
+---
+
+## 9. HITECH Enforcement Actions: Historical Examples
+
+| Year | Entity                 | Penalty | Reason                                          |
+| ---- | ---------------------- | ------- | ----------------------------------------------- |
+| 2019 | Texas Health Resources | $2.4M   | Lack of access controls; no risk analysis       |
+| 2020 | Premera Blue Cross     | $6.85M  | Security vulnerabilities; 10.4M records exposed |
+| 2021 | Excellus Health Plan   | $5.1M   | Security rule violations; 9.3M records breached |
+| 2022 | Banner Health          | $1.25M  | Risk analysis failures; unauthorized access     |
+| 2023 | L.A. Care Health Plan  | $1.3M   | Risk analysis; IT system security               |
+
+---
+
+**Related Datasets:** `02-hipaa-security-rule.md`, `03-breach-notification-rule.md`, `14-enforcement-penalties.md`

datasets/14-enforcement-penalties.md

@@ -0,0 +1,205 @@
+# HIPAA Enforcement and Civil Monetary Penalties — Dataset
+
+**Source:** 45 CFR Part 160, Subpart D and E  
+**Authority:** HHS Office for Civil Rights (OCR)  
+**Enforcement Agency:** Office for Civil Rights (OCR), U.S. Department of Justice (DOJ)
+
+---
+
+## 1. Overview
+
+HIPAA enforcement is administered by the **HHS Office for Civil Rights (OCR)**. Criminal violations are referred to the **Department of Justice (DOJ)**. The HITECH Act (2009) dramatically increased maximum penalties and created a tiered enforcement framework based on culpability.
+
+---
+
+## 2. Civil Monetary Penalties (CMPs)
+
+### Current Penalty Tiers (Post-HITECH, as adjusted for inflation)
+
+| Tier       | Standard                        | Description                                                                                        | Per Violation     | Annual Cap |
+| ---------- | ------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------- | ---------- |
+| **Tier 1** | Did Not Know                    | Entity did not know and, by exercising reasonable diligence, would not have known of the violation | $100 – $50,000    | $1,919,173 |
+| **Tier 2** | Reasonable Cause                | Violation was due to reasonable cause and not willful neglect                                      | $1,000 – $50,000  | $1,919,173 |
+| **Tier 3** | Willful Neglect — Corrected     | Violation due to willful neglect but corrected within 30 days of discovery                         | $10,000 – $50,000 | $1,919,173 |
+| **Tier 4** | Willful Neglect — Not Corrected | Violation due to willful neglect and not corrected within 30 days                                  | $50,000           | $1,919,173 |
+
+> **Note:** The annual cap per violation category is approximately $1.9M. Multiple violation categories in a single incident can result in combined penalties exceeding $5–10M.
+
+### Key Enforcement Principle
+
+**Willful Neglect = No Escape from Penalty.** Under HITECH, violations due to willful neglect must result in CMPs — OCR has no discretion to waive them.
+
+---
+
+## 3. Criminal Penalties
+
+Criminal penalties apply to individuals who knowingly obtain or disclose PHI in violation of HIPAA:
+
+| Level of Offense                                                                                     | Penalty                                             |
+| ---------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
+| **Knowingly** (basic violation)                                                                      | Up to 1 year in prison and/or up to $50,000 fine    |
+| **Under false pretenses**                                                                            | Up to 5 years in prison and/or up to $100,000 fine  |
+| **With intent to sell, transfer, or use for commercial advantage, personal gain, or malicious harm** | Up to 10 years in prison and/or up to $250,000 fine |
+
+Criminal prosecutions are referred to the DOJ. Individuals — including employees — can be personally criminally liable, not just organizations.
+
+---
+
+## 4. State Attorney General Enforcement
+
+The HITECH Act granted state attorneys general the authority to bring civil actions on behalf of state residents for HIPAA violations:
+
+- Can seek injunctive relief to stop violations
+- Can recover up to $25,000 in damages per violation category per year on behalf of state residents
+- Multiple state AGs may simultaneously pursue actions for multi-state breaches
+- AGs may act independently of OCR
+
+---
+
+## 5. OCR Enforcement Process
+
+### How OCR Investigations Begin
+
+1. **Complaints:** Filed by individuals through the HHS complaint portal
+2. **Breach Reports:** Breaches affecting 500+ individuals trigger automatic OCR review
+3. **Compliance Reviews:** OCR may audit any covered entity or BA proactively
+4. **Referrals:** From other federal agencies (CMS, DOJ, FBI)
+
+### OCR Investigation Stages
+
+```
+Complaint / Breach Report Filed
+         ↓
+OCR Intake and Review (determine if HIPAA applies)
+         ↓
+Investigation (request documents, conduct interviews)
+         ↓
+Preliminary Findings
+         ↓
+Informal Resolution (attempt to resolve through technical assistance)
+         ↓
+If not resolved: Determination Letter
+         ↓
+Civil Monetary Penalty Assessment
+         ↓
+Covered Entity may appeal to HHS Departmental Appeals Board
+         ↓
+Federal Court (if further appeal)
+```
+
+### What OCR Requests During Investigation
+
+Common document requests in HIPAA investigations:
+
+- Policies and procedures for Privacy and Security Rules
+- Most recent risk analysis documentation
+- Evidence of workforce training
+- Business Associate Agreements
+- Incident response documentation
+- Access control policies
+- Audit logs
+- Breach notification records
+
+---
+
+## 6. Most Common OCR Enforcement Violations
+
+Based on historical OCR settlements and enforcement actions:
+
+| Violation                                               | % of Enforcement Actions |
+| ------------------------------------------------------- | ------------------------ |
+| **Impermissible uses and disclosures of PHI**           | ~35%                     |
+| **Lack of safeguards for PHI**                          | ~15%                     |
+| **Failure to provide patients access to their PHI**     | ~15%                     |
+| **Failure to enter into BAAs**                          | ~10%                     |
+| **Failure to perform security risk analysis**           | ~10%                     |
+| **Using or disclosing more than minimum necessary PHI** | ~5%                      |
+| **No notice of privacy practices**                      | ~5%                      |
+| **Other**                                               | ~5%                      |
+
+---
+
+## 7. Major OCR Settlements (2018–2025)
+
+| Year | Entity                                 | Settlement Amount | Violation                                                            |
+| ---- | -------------------------------------- | ----------------- | -------------------------------------------------------------------- |
+| 2018 | Anthem Inc.                            | $16,000,000       | Largest HIPAA settlement at time; 78.8M records; inadequate security |
+| 2019 | University of Rochester Medical Center | $3,000,000        | Lost unencrypted mobile devices; no encryption policy                |
+| 2020 | CHSPSC (Community Health Systems)      | $5,000,000        | 6.1M records; inadequate security measures                           |
+| 2021 | Peachstate Health Management           | $25,000           | Small entity; risk analysis failure                                  |
+| 2022 | Norwood Clinic                         | $350,000          | Ransomware attack; prior security failures                           |
+| 2023 | iHealth Solutions                      | $75,000           | Failure to provide patient access                                    |
+| 2024 | Banner Health                          | $1,250,000        | Risk analysis failures; unauthorized access                          |
+
+---
+
+## 8. The "Right of Access" Initiative
+
+In 2019, OCR launched a specific enforcement initiative targeting violations of the individual right of access (§ 164.524). Since then, OCR has settled numerous cases specifically for:
+
+- Failure to provide records within 30 days
+- Charging excessive fees for copies
+- Providing records in wrong format
+- Requiring authorization when access right applies
+
+Penalties in Right of Access enforcement have ranged from $3,500 to $240,000 per case.
+
+---
+
+## 9. Corrective Action Plans (CAPs)
+
+Most OCR settlements include a **Corrective Action Plan (CAP)** requiring the entity to:
+
+- Implement specific policies and procedures
+- Conduct workforce training
+- Perform security risk analysis updates
+- Submit periodic compliance reports to OCR for 1–3 years
+- Allow OCR to monitor compliance
+
+Failure to comply with a CAP can result in additional penalties.
+
+---
+
+## 10. Factors That Affect Penalty Amount
+
+OCR considers these factors when determining penalty amounts:
+
+| Factor                             | Effect on Penalty                               |
+| ---------------------------------- | ----------------------------------------------- |
+| **Nature and extent of violation** | More violations = higher penalty                |
+| **Nature and extent of harm**      | PHI actually used maliciously = higher          |
+| **History of prior violations**    | Prior violations → higher penalties             |
+| **Financial condition of entity**  | Smaller entities may receive reduced penalties  |
+| **Level of cooperation**           | Full cooperation → mitigating factor            |
+| **Good faith efforts to comply**   | Documented compliance efforts → mitigating      |
+| **Deliberate indifference**        | Knowing disregard of requirements → aggravating |
+
+---
+
+## 11. Safe Harbor for Willful Neglect
+
+An entity can avoid higher Tier 3/4 penalties if:
+
+- The violation was due to willful neglect
+- The entity **corrects the violation within 30 days** of discovery (or of when it should have been known)
+- The correction moves the violation from Tier 4 to Tier 3
+
+**Action:** Any compliance violation discovered must be immediately assessed and actively remediated.
+
+---
+
+## 12. Documentation as Defense
+
+Organizations that face OCR investigation are significantly better positioned if they can demonstrate:
+
+1. Completed, documented risk analysis (with date and methodology)
+2. Risk management plan implementing risk analysis findings
+3. Workforce training records with completion dates
+4. Policies and procedures version history
+5. BAA inventory with execution dates
+6. Incident response records
+7. Evidence of periodic security reviews
+
+---
+
+**Related Datasets:** `13-hitech-act.md`, `03-breach-notification-rule.md`, `02-hipaa-security-rule.md`

datasets/15-hhs-faq-categories.md

@@ -0,0 +1,176 @@
+# HHS FAQ Categories and Key Compliance Q&A — Dataset
+
+**Source:** HHS HIPAA FAQs for Professionals  
+**URL:** https://www.hhs.gov/hipaa/for-professionals/faq/index.html  
+**Purpose:** Reference for RAG indexing and Q&A retrieval
+
+---
+
+## 1. FAQ Index Overview
+
+The HHS maintains a comprehensive FAQ database that resolves edge cases and ambiguities not explicitly addressed in the regulatory text. The following categories represent the highest-value ingestion targets for a HIPAA compliance RAG system.
+
+| FAQ Category                             | Question Count | Core Topics                                                                            |
+| ---------------------------------------- | -------------- | -------------------------------------------------------------------------------------- |
+| **Smaller Providers and Businesses**     | 145 Questions  | Operational compliance for clinics; minimal viable safeguards; cost-effective controls |
+| **Right to Access and Research**         | 58 Questions   | Patient access rights; electronic transmission; research data use agreements           |
+| **Business Associates**                  | 41 Questions   | BAA requirements; Cloud Service Provider obligations; breach reporting chains          |
+| **Health Information Technology**        | 39 Questions   | EHR integration; interoperability; HITECH intersections                                |
+| **Security Rule & Safeguards**           | 37 Questions   | Encryption standards; access controls; audit logging; disaster recovery                |
+| **Treatment, Payment, Operations (TPO)** | 31 Questions   | Permitted disclosures without authorization; billing; debt collection                  |
+| **Notice of Privacy Practices**          | 20 Questions   | NPP retention; patient acknowledgment; treatment refusal                               |
+| **Incidental Uses and Disclosures**      | 18 Questions   | When incidental disclosures are permitted                                              |
+| **Minimum Necessary**                    | 16 Questions   | Standard application to specific scenarios                                             |
+| **Breach Notification**                  | 15 Questions   | 60-day rule; media notification; business associate notification                       |
+
+---
+
+## 2. Key Q&A: Business Associates
+
+**Q: Is a cloud service provider that stores encrypted ePHI but has no decryption key still a business associate?**
+
+A: Yes. A cloud service provider that creates, receives, maintains, or transmits ePHI on behalf of a covered entity is a business associate — even if the CSP holds no decryption keys and cannot view the data. The CSP "maintains" ePHI by virtue of storing it on its infrastructure. A Business Associate Agreement is required.
+
+---
+
+**Q: What happens if a vendor refuses to sign a BAA?**
+
+A: If a vendor will not sign a BAA, the covered entity or business associate cannot use that vendor for any service that involves PHI. If the vendor's services are essential, the covered entity must either find a compliant alternative vendor or implement technical controls that fully prevent PHI from ever reaching that vendor's systems (e.g., de-identification before transmission, server-side proxying).
+
+---
+
+**Q: Does a BAA itself need to use any particular format or language?**
+
+A: No. HHS does not require a specific format, but the BAA must include all required provisions. Many vendors provide their own standard BAA language; covered entities have the right to negotiate terms. A BAA that lacks required provisions is not a valid BAA.
+
+---
+
+## 3. Key Q&A: Patient Right of Access
+
+**Q: Can a covered entity require patients to use a patient portal to access their records?**
+
+A: No. While a covered entity may offer a patient portal as an option, it cannot require patients to use it as the only means of accessing their records. Patients may request records via other means (phone, in-person, fax).
+
+---
+
+**Q: Can a covered entity charge for providing access to records?**
+
+A: Yes, but only a reasonable, cost-based fee. The fee may include: labor costs for copying (not for searching); supplies; postage. A covered entity may NOT charge labor for searching and retrieving records, nor charge for viewing records in person, nor charge fees that would effectively block the patient from accessing their records.
+
+---
+
+**Q: What if a patient's requested format is not readily producible?**
+
+A: If the requested electronic format is not readily producible, the covered entity must provide the records in a readable electronic format agreed upon by both parties. If no electronic format is agreed upon, a paper copy must be provided.
+
+---
+
+**Q: Must a covered entity provide records to a third party designated by the patient?**
+
+A: Yes. If a patient makes a clear and specific request to transmit their records to a designated third party, the covered entity must do so. The covered entity may require the request to be in writing, signed by the individual.
+
+---
+
+## 4. Key Q&A: Breach Notification
+
+**Q: When does the 60-day breach notification clock start?**
+
+A: The clock starts on the date of **discovery** — the first day on which the breach is known, or by exercising reasonable diligence would have been known. If a business associate discovers the breach, the BA must notify the covered entity without unreasonable delay and within 60 days. The covered entity's 60-day clock to notify individuals starts from when the covered entity discovered (or should have discovered) the breach.
+
+---
+
+**Q: If only 5 people were affected by a breach, do we need to notify HHS?**
+
+A: Yes, but not immediately. For breaches affecting fewer than 500 individuals, the covered entity must maintain a log and report all such breaches to HHS annually — no later than 60 days after the end of the calendar year.
+
+---
+
+**Q: Does encryption provide full safe harbor from breach notification?**
+
+A: Yes, if the encryption meets HHS-specified standards. PHI is considered "secured" (and thus not subject to breach notification) if it is encrypted using a process that makes it unreadable, unusable, or indecipherable to unauthorized individuals, and the decryption key was not compromised. The HHS has published specific guidance on acceptable encryption standards (NIST-approved algorithms; AES-256 at rest; TLS 1.2+ in transit).
+
+---
+
+## 5. Key Q&A: Minimum Necessary Standard
+
+**Q: Does the minimum necessary standard apply to disclosures for treatment?**
+
+A: No. The minimum necessary standard does NOT apply to disclosures to or requests by a health care provider for treatment purposes. The standard also does not apply to disclosures to the individual themselves, disclosures made pursuant to a valid authorization, disclosures required by law, or disclosures to HHS for compliance activities.
+
+---
+
+**Q: How should a covered entity determine what counts as "minimum necessary"?**
+
+A: Covered entities must make reasonable efforts and develop policies that limit access to PHI based on the roles of workforce members. Policies should identify which classes of employees need access to which categories of PHI, and limit access to only the minimum amount necessary to accomplish their job functions.
+
+---
+
+## 6. Key Q&A: Security Rule
+
+**Q: Is encryption required under the Security Rule?**
+
+A: Encryption is an "addressable" implementation specification under both the Access Control standard (§ 164.312(a)(2)(iv)) and the Transmission Security standard (§ 164.312(e)(2)(ii)). Addressable means the entity must assess whether encryption is reasonable and appropriate given its specific circumstances. If encryption is not implemented, the entity must document why and implement an equivalent alternative. In practice, the inability to justify not encrypting ePHI is extremely rare — encryption is effectively mandatory.
+
+---
+
+**Q: Is a risk analysis required every year?**
+
+A: The Security Rule requires periodic risk analyses but does not mandate annual reviews specifically. However, organizations must update their risk analysis whenever there are significant changes to operations, technologies, or the environment. OCR recommends at minimum an annual review and update.
+
+---
+
+**Q: What constitutes a "workforce member" under HIPAA?**
+
+A: Workforce members include employees, volunteers, trainees, and other persons whose conduct, in the performance of work for a covered entity, is under the direct control of the entity — whether or not paid. This includes contractors who work on-site or under direct supervision.
+
+---
+
+## 7. Key Q&A: Smaller Providers
+
+**Q: A small clinic has only 3 employees. Are we exempt from HIPAA?**
+
+A: No. HIPAA applies to all covered entities regardless of size — there is no small business exemption. However, the Security Rule allows flexibility: "addressable" specifications mean small entities can tailor their security measures to their specific risk environment and resources. The same Privacy Rule, Security Rule, and Breach Notification Rule apply to a solo physician practice as to a large hospital system.
+
+---
+
+**Q: We are a startup that doesn't process insurance claims electronically. Are we a covered entity?**
+
+A: Not necessarily. Health care providers are covered entities only if they conduct standard electronic health care transactions (like submitting insurance claims electronically). A provider that only accepts cash payments and does not conduct any electronic transactions is not a covered entity. However, if you ever send an electronic claim, you become a covered entity.
+
+---
+
+**Q: As a small clinic, do we need a formal Security Officer?**
+
+A: Yes. A designated Security Official (Security Officer) is a Required standard under § 164.308(a)(2). The Security Official is responsible for developing and implementing security policies and procedures. In a small practice, this can be any staff member with appropriate knowledge — it does not require a full-time dedicated position, but the role must be formally assigned.
+
+---
+
+## 8. Key Q&A: Health Information Technology
+
+**Q: If we use an EHR that is "HIPAA Certified," are we compliant?**
+
+A: No. No EHR product can be "HIPAA certified" — HIPAA certification does not exist as an official designation. EHR products can be certified by ONC as meeting interoperability standards, but this is separate from HIPAA compliance. Using a compliant EHR does not mean you are HIPAA compliant — the covered entity is still responsible for all administrative, physical, and technical safeguards.
+
+---
+
+**Q: Does HIPAA require us to use FHIR APIs?**
+
+A: Not directly under HIPAA. However, the ONC 21st Century Cures Rule (separate from HIPAA) requires certified EHR systems to support HL7 FHIR R4 APIs for patient data access. If your software is a Certified EHR, FHIR support is required by ONC rules.
+
+---
+
+## 9. Key Q&A: Digital Health and Mobile Apps
+
+**Q: Does HIPAA apply to mobile health apps?**
+
+A: It depends. HIPAA applies to mobile apps developed by or on behalf of covered entities and business associates. A general wellness app that collects health data but is not provided by or on behalf of a covered entity is not subject to HIPAA — though the FTC Health Breach Notification Rule may apply, and state laws may also apply.
+
+---
+
+**Q: Can we use AI or machine learning models trained on patient data?**
+
+A: Yes, but the training data must either: (1) be properly de-identified under the Safe Harbor or Expert Determination method before use in training, (2) be used under a valid authorization from each patient, or (3) qualify for a research exception with IRB approval. Simply training an internal model without de-identification or authorization is a HIPAA violation.
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `02-hipaa-security-rule.md`, `03-breach-notification-rule.md`, `05-business-associates.md`, `07-patient-rights.md`, `17-covered-entities.md`

datasets/16-rag-system-architecture.md

@@ -0,0 +1,349 @@
+# RAG System Architecture for HIPAA Compliance — Dataset
+
+**Audience:** Software engineers, AI architects, ML engineers building healthcare RAG systems  
+**Context:** Mojar.ai-specific RAG implementation for HIPAA compliance agents
+
+---
+
+## 1. Overview
+
+Retrieval-Augmented Generation (RAG) systems in healthcare require specialized architectural controls to prevent PHI exposure, ensure regulatory accuracy, and resist adversarial manipulation. This dataset documents the full technical architecture and engineering requirements for a HIPAA-compliant RAG deployment.
+
+---
+
+## 2. RAG Pipeline Architecture for Healthcare
+
+### 2.1 Standard RAG vs. Healthcare RAG
+
+| Component        | Standard RAG           | Healthcare RAG                                      |
+| ---------------- | ---------------------- | --------------------------------------------------- |
+| **Ingestion**    | Direct document upload | PHI sanitization → de-identification → ingestion    |
+| **Chunking**     | Semantic chunking      | Context-preserving chunking with PHI-awareness      |
+| **Embeddings**   | Any embedding model    | HIPAA-covered embedding service or on-premise model |
+| **Vector Store** | Any vector DB          | BAA-covered vector store with access controls       |
+| **Query**        | Direct user query      | Query PHI scanning → sanitization → retrieval       |
+| **Retrieval**    | Top-k similarity       | Access-controlled retrieval per user role           |
+| **Generation**   | LLM response           | Grounded response with citation enforcement         |
+| **Output**       | Free-form text         | Passage-level citations + hallucination controls    |
+
+### 2.2 Full Pipeline Architecture
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│                    INGESTION PIPELINE                            │
+│                                                                  │
+│  Source Documents (PDF, HTML, DOCX)                             │
+│           ↓                                                      │
+│  [PHI Scanner] — NER + pattern matching                        │
+│           ↓                                                      │
+│  [De-identification Layer] — Remove/replace identifiers        │
+│           ↓                                                      │
+│  [Context-Preserving Tokenization] — Surrogate tokens          │
+│           ↓                                                      │
+│  [Semantic Chunker] — Split by meaning, not character count    │
+│           ↓                                                      │
+│  [Embedding Model] — Generate vectors                          │
+│           ↓                                                      │
+│  [Vector Store] — Store with metadata and access controls      │
+└─────────────────────────────────────────────────────────────────┘
+
+┌─────────────────────────────────────────────────────────────────┐
+│                    QUERY PIPELINE                                │
+│                                                                  │
+│  User Query                                                      │
+│           ↓                                                      │
+│  [Prompt Injection Scanner] — Detect adversarial inputs        │
+│           ↓                                                      │
+│  [PHI Scanner] — Alert if user submits unmasked PHI            │
+│           ↓                                                      │
+│  [Query Embedding] — Embed sanitized query                     │
+│           ↓                                                      │
+│  [Access-Controlled Retrieval] — Enforce user role scoping     │
+│           ↓                                                      │
+│  [Top-k Relevant Chunks] — Retrieved with source metadata      │
+│           ↓                                                      │
+│  [LLM Generation] — Grounded response with strict context      │
+│           ↓                                                      │
+│  [Citation Enforcement] — Passage-level quotes required        │
+│           ↓                                                      │
+│  [Output PHI Filter] — Final scan before delivery              │
+│           ↓                                                      │
+│  Response with Citations → User                                 │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## 3. Document Ingestion Layer
+
+### 3.1 PHI Detection Before Ingestion
+
+Before any document enters the vector store, it must be scanned for PHI:
+
+```python
+import re
+from typing import Optional
+
+PHI_PATTERNS = {
+    "ssn": re.compile(r'\b\d{3}-\d{2}-\d{4}\b'),
+    "phone": re.compile(r'\b(\+?1[-.\s]?)?\(?\d{3}\)?[-.\s]?\d{3}[-.\s]?\d{4}\b'),
+    "email": re.compile(r'\b[A-Za-z0-9._%+\-]+@[A-Za-z0-9.\-]+\.[A-Z|a-z]{2,}\b'),
+    "date_of_birth": re.compile(r'\b(DOB|date of birth|born)\b.*?\d{1,2}[/\-]\d{1,2}[/\-]\d{2,4}', re.IGNORECASE),
+    "mrn": re.compile(r'\b(MRN|medical record number|patient id)[:#\s]+[A-Z0-9\-]+\b', re.IGNORECASE),
+    "ip_address": re.compile(r'\b(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\b'),
+}
+
+def scan_document_for_phi(text: str) -> dict[str, list[str]]:
+    """Returns a dict of found PHI patterns."""
+    findings = {}
+    for phi_type, pattern in PHI_PATTERNS.items():
+        matches = pattern.findall(text)
+        if matches:
+            findings[phi_type] = matches
+    return findings
+
+def should_block_ingestion(text: str) -> bool:
+    """Block ingestion if high-confidence PHI is detected."""
+    findings = scan_document_for_phi(text)
+    high_risk = {"ssn", "mrn", "date_of_birth"}
+    return bool(findings.keys() & high_risk)
+```
+
+### 3.2 Context-Preserving Tokenization
+
+Simple redaction destroys semantic value. Use surrogate tokenization:
+
+```python
+from dataclasses import dataclass
+import uuid
+
+@dataclass
+class TokenizationResult:
+    tokenized_text: str
+    token_map: dict[str, str]  # surrogate → original (stored encrypted separately)
+
+def tokenize_phi(text: str) -> TokenizationResult:
+    """Replace PHI with semantically neutral surrogate tokens."""
+    token_map = {}
+    tokenized = text
+
+    # Names: [PERSON_001], [PERSON_002]...
+    # SSNs: [SSN_REDACTED]
+    # Dates: [DATE_REDACTED] or [YEAR:1978]
+    # Phones: [PHONE_REDACTED]
+
+    for phi_type, pattern in PHI_PATTERNS.items():
+        def replace_match(m):
+            surrogate = f"[{phi_type.upper()}_{uuid.uuid4().hex[:6].upper()}]"
+            token_map[surrogate] = m.group(0)
+            return surrogate
+        tokenized = pattern.sub(replace_match, tokenized)
+
+    return TokenizationResult(tokenized_text=tokenized, token_map=token_map)
+```
+
+### 3.3 Semantic Chunking Strategy
+
+For regulatory documents (HIPAA rules, HHS guidance), use **semantic chunking** rather than fixed-size character splits:
+
+| Chunking Strategy                        | Use Case                                         |
+| ---------------------------------------- | ------------------------------------------------ |
+| Fixed character split (e.g., 512 tokens) | Simple documents; poor for complex legal text    |
+| Sentence-level split                     | Better; but loses paragraph context              |
+| **Semantic/topic-aware split**           | Best for regulatory documents; preserves meaning |
+| Paragraph-level with overlap             | Good for legal text with cross-references        |
+
+**Recommended approach for HHS regulatory docs:**
+
+- Split at heading boundaries (## sections)
+- Preserve table integrity (never split mid-table)
+- Maintain 128-token overlap between chunks
+- Include document metadata in each chunk (source URL, rule citation, section)
+
+---
+
+## 4. Vector Store Access Controls
+
+Healthcare RAG systems require document-level access controls on the vector store:
+
+```python
+# Example: Document metadata with access control
+document_chunk = {
+    "id": "chunk_uuid",
+    "text": "The 60-day breach notification window begins...",
+    "embedding": [...],  # vector
+    "metadata": {
+        "source_url": "https://www.hhs.gov/hipaa/for-professionals/breach-notification/",
+        "regulation": "45 CFR § 164.400",
+        "topic": "breach_notification",
+        "sensitivity": "public",           # public | internal | restricted
+        "allowed_roles": ["all"],           # or ["compliance_officer", "legal"]
+        "document_type": "hhs_official",
+        "last_verified": "2026-01-01",
+        "chunk_index": 3,
+        "total_chunks": 12
+    }
+}
+
+# Query with access control enforcement
+def retrieve_with_access_control(
+    query_embedding: list[float],
+    user_role: str,
+    top_k: int = 5
+) -> list[dict]:
+    """Only return chunks the user's role is allowed to access."""
+    results = vector_store.similarity_search(
+        query_embedding,
+        top_k=top_k * 2,  # Over-fetch then filter
+        filter={"allowed_roles": {"$in": ["all", user_role]}}
+    )
+    return results[:top_k]
+```
+
+---
+
+## 5. Hallucination Prevention for Regulatory RAG
+
+LLMs hallucinate facts — this is catastrophic in a compliance context. Mitigation strategies:
+
+### 5.1 Grounding Rules in System Prompt
+
+```
+RULE 1: You must ONLY make factual claims about HIPAA regulations that are
+        directly supported by text in the retrieved context.
+
+RULE 2: If the retrieved context does not contain the answer, respond:
+        "The requested information is not available in the current
+        official documentation. Please consult HHS.gov directly."
+
+RULE 3: Never extrapolate or infer regulatory requirements beyond what is
+        explicitly stated in the retrieved source.
+
+RULE 4: Every regulatory claim must be accompanied by a source citation
+        that includes the CFR section (e.g., 45 CFR § 164.524) or the
+        specific HHS FAQ number.
+```
+
+### 5.2 Passage-Level Citation Enforcement
+
+The Mojar.ai snippet tool enables passage-level citation:
+
+```xml
+<!-- Required format for all regulatory citations -->
+<snippet id="breach-60-day-rule" url="https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html">
+  Covered entities must provide notification of a breach without unreasonable delay
+  and in no case later than 60 days following discovery of the breach.
+</snippet>
+
+The above passage establishes the 60-day notification window that begins from the
+date of discovery (not the date of the breach itself). Engineering teams should implement
+a breach incident tracking system that records the discovery timestamp and triggers
+automated reminders at 30, 45, and 55 days.
+```
+
+### 5.3 Confidence Scoring
+
+Implement retrieval confidence thresholds:
+
+```python
+def generate_response_with_confidence(
+    query: str,
+    retrieved_chunks: list[dict],
+    min_relevance_score: float = 0.75
+) -> str:
+
+    # Filter low-confidence retrievals
+    high_confidence = [
+        chunk for chunk in retrieved_chunks
+        if chunk["relevance_score"] >= min_relevance_score
+    ]
+
+    if not high_confidence:
+        return (
+            "I was unable to find sufficiently relevant official documentation "
+            "to answer this question with confidence. Please consult "
+            "https://www.hhs.gov/hipaa/for-professionals/index.html directly."
+        )
+
+    # Generate grounded response
+    context = "\n\n".join([c["text"] for c in high_confidence])
+    return llm.generate(query=query, context=context)
+```
+
+---
+
+## 6. Prompt Injection Defense
+
+In healthcare RAG, prompt injection attacks can:
+
+- Manipulate the AI into disclosing other users' data
+- Cause the AI to ignore HIPAA restrictions
+- Trick the AI into generating non-compliant guidance
+
+### Detection Patterns:
+
+```python
+INJECTION_PATTERNS = [
+    r'ignore (previous|all|above) instructions',
+    r'forget (your|all) instructions',
+    r'you are now',
+    r'act as (if you are|a different)',
+    r'DAN mode',
+    r'developer mode',
+    r'bypass (safety|hipaa|compliance)',
+    r'reveal (system|hidden) (prompt|instructions)',
+    r'pretend (hipaa|privacy) (doesn.t|does not) (exist|apply)',
+]
+
+def detect_prompt_injection(user_input: str) -> bool:
+    """Returns True if injection attempt detected."""
+    user_lower = user_input.lower()
+    return any(re.search(pattern, user_lower) for pattern in INJECTION_PATTERNS)
+```
+
+---
+
+## 7. Maintenance Agents
+
+A production HIPAA RAG system requires background maintenance:
+
+| Maintenance Task                  | Frequency                    | Purpose                                                        |
+| --------------------------------- | ---------------------------- | -------------------------------------------------------------- |
+| **Staleness Detection**           | Weekly                       | Flag documents not verified against recent HHS updates         |
+| **Broken Link Checker**           | Daily                        | Verify source URLs still resolve to correct content            |
+| **Content Drift Detection**       | Monthly                      | Compare ingested content against live HHS pages for changes    |
+| **Deprecated Reference Scanning** | Monthly                      | Identify references to sunset regulations or outdated policies |
+| **Conflict Detection**            | On new document ingestion    | Find contradictions between documents                          |
+| **Embedding Refresh**             | Quarterly or on model update | Re-embed documents when embedding model is updated             |
+
+---
+
+## 8. Token Efficiency in Healthcare Compliance RAG
+
+HIPAA regulations are dense. Token efficiency is essential:
+
+| Strategy                       | Description                                                     | Benefit                                            |
+| ------------------------------ | --------------------------------------------------------------- | -------------------------------------------------- |
+| **Semantic compression**       | Summarize preamble and retain only normative text               | Reduce chunk token count                           |
+| **Structural metadata**        | Store CFR section numbers in metadata, not chunk body           | Faster filtering without full-text scan            |
+| **Hierarchical retrieval**     | First retrieve relevant rule; then sub-retrieve specific clause | Reduce context window pressure                     |
+| **Role-based context loading** | Only load context relevant to the user's question domain        | Avoid overwhelming LLM with irrelevant regulations |
+| **Citation-first design**      | Return citations first; elaborate only if follow-up requested   | Reduce unnecessary generation                      |
+
+---
+
+## 9. HIPAA-Compliant Vector Database Options
+
+| Database                   | BAA Available                         | Self-Hosted Option | Notes                                    |
+| -------------------------- | ------------------------------------- | ------------------ | ---------------------------------------- |
+| **Pinecone**               | YES (Enterprise)                      | No                 | Cloud-native; popular for production RAG |
+| **Weaviate**               | YES (Weaviate Cloud Enterprise)       | YES                | Open-source option for self-hosting      |
+| **Chroma**                 | Self-hosted = customer responsibility | YES                | Lightweight; common in dev               |
+| **pgvector (PostgreSQL)**  | Via PostgreSQL host BAA               | YES                | Leverage existing RDS BAA                |
+| **Qdrant**                 | Self-hosted = customer responsibility | YES                | High performance; open source            |
+| **Azure Cognitive Search** | YES — via Azure BAA                   | No                 | Strong enterprise integration            |
+| **AWS OpenSearch**         | YES — via AWS BAA                     | Via EC2            | Flexible; familiar for AWS users         |
+
+---
+
+**Related Datasets:** `02-hipaa-security-rule.md`, `04-phi-de-identification.md`, `06-phi-definitions-identifiers.md`, `08-technical-safeguards-engineering.md`

datasets/17-covered-entities.md

@@ -0,0 +1,189 @@
+# Covered Entities and Their Obligations — HIPAA Dataset
+
+**Source:** 45 CFR § 160.103; 45 CFR Part 164  
+**Authority:** U.S. Department of Health and Human Services (HHS)
+
+---
+
+## 1. Definition of a Covered Entity
+
+A **covered entity** is any of the following three categories of organizations or individuals that are subject to HIPAA:
+
+| Category                       | Definition                                                                       | Examples                                                                                                       |
+| ------------------------------ | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| **Health Plans**               | Individual or group plans that provide or pay for health care                    | Health insurance companies, HMOs, Medicare, Medicaid, employer-sponsored health plans, long-term care insurers |
+| **Health Care Clearinghouses** | Entities that process nonstandard health information into standard data elements | Billing services, repricing companies, value-added networks                                                    |
+| **Health Care Providers**      | Providers that conduct covered electronic health care transactions               | Hospitals, physician practices, dental offices, pharmacies, nursing homes, home health agencies, psychologists |
+
+---
+
+## 2. Covered Electronic Transactions
+
+Health care providers are covered entities **only if** they transmit health information electronically in connection with any of the following standard transactions:
+
+| Transaction                                   | Description                                         |
+| --------------------------------------------- | --------------------------------------------------- |
+| **Health care claims**                        | Submit claims to health plans (ANSI X12 837)        |
+| **Health care payment and remittance advice** | Receive explanation of benefits (ANSI X12 835)      |
+| **Health care claim status**                  | Check status of submitted claims (ANSI X12 276/277) |
+| **Enrollment/disenrollment in a health plan** | (ANSI X12 834)                                      |
+| **Eligibility for a health plan**             | (ANSI X12 270/271)                                  |
+| **Referral certification and authorization**  | (ANSI X12 278)                                      |
+| **Health plan premium payments**              | (ANSI X12 820)                                      |
+| **Coordination of benefits**                  | —                                                   |
+
+> **Key Exception:** A physician who only accepts cash and never submits claims electronically is **not** a covered entity — even though they provide health care.
+
+---
+
+## 3. Health Plans
+
+### 3.1 Covered Health Plan Types
+
+| Health Plan                                                                                                 | HIPAA Covered?                               |
+| ----------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
+| Individual health insurance plans                                                                           | YES                                          |
+| Group health plans with 50+ participants                                                                    | YES                                          |
+| Group health plans with fewer than 50 participants (self-administered)                                      | YES                                          |
+| Small employer group health plans (self-insured, fewer than 50 participants with third-party administrator) | YES                                          |
+| Medicare Part A and B                                                                                       | YES                                          |
+| Medicaid                                                                                                    | YES                                          |
+| Medicare Advantage                                                                                          | YES                                          |
+| Indian Health Service                                                                                       | YES                                          |
+| Federal Employees Health Benefits                                                                           | YES                                          |
+| Long-term care insurance                                                                                    | YES (if covers medically necessary services) |
+| Workers' compensation                                                                                       | **NO**                                       |
+| Auto insurance (medical coverage only)                                                                      | **NO**                                       |
+| Life insurance                                                                                              | **NO**                                       |
+| Fixed indemnity plans                                                                                       | **NO**                                       |
+| Short-term disability                                                                                       | **NO**                                       |
+
+---
+
+## 4. Key Obligations of Covered Entities
+
+### 4.1 Privacy Rule Obligations
+
+| Obligation                  | Description                                           |
+| --------------------------- | ----------------------------------------------------- |
+| Notice of Privacy Practices | Provide NPP at first point of service                 |
+| Individual rights           | Implement processes for all 8 individual rights       |
+| Minimum Necessary           | Limit PHI use and disclosure to the minimum necessary |
+| Training                    | Train all workforce members on Privacy policies       |
+| Documentation               | Maintain privacy policies for 6 years                 |
+| Complaint process           | Establish process for individuals to file complaints  |
+| Sanction policy             | Apply sanctions for privacy violations by workforce   |
+
+### 4.2 Security Rule Obligations
+
+| Obligation                   | Description                                              |
+| ---------------------------- | -------------------------------------------------------- |
+| Risk Analysis                | Conduct and document comprehensive risk analysis         |
+| Risk Management              | Implement a risk management plan based on analysis       |
+| Security Officer             | Designate a Security Official                            |
+| Workforce training           | Train all workforce on security policies                 |
+| Access controls              | Implement technical access controls for ePHI             |
+| Audit controls               | Implement audit logging for ePHI access                  |
+| Contingency Plan             | Backup, disaster recovery, emergency operations          |
+| Business Associate Contracts | Execute BAAs with all BAs                                |
+| Evaluations                  | Conduct periodic technical and non-technical evaluations |
+
+### 4.3 Breach Notification Obligations
+
+| Obligation              | Description                                          |
+| ----------------------- | ---------------------------------------------------- |
+| Individual notification | Notify affected individuals within 60 days           |
+| HHS notification        | Notify HHS within 60 days (500+) or annually (<500)  |
+| Media notification      | Notify media within 60 days (500+ in a state)        |
+| BA notification receipt | Receive and act on breach notifications from BAs     |
+| Documentation           | Document all breach investigations and notifications |
+
+---
+
+## 5. Hybrid Entities
+
+A **hybrid entity** is a single legal entity that performs both covered and non-covered functions.
+
+**Example:** A large corporation that operates both a health plan for employees and a manufacturing division. The corporation may designate only the health care components as the "covered health care component" for HIPAA purposes.
+
+**Requirements for hybrid entities:**
+
+- Must designate the covered functions in writing
+- Must establish firewalls between covered and non-covered components
+- Covered component must comply with all applicable HIPAA rules
+- Non-covered component may not use PHI from the covered component for non-covered purposes
+
+---
+
+## 6. Affiliated Covered Entities (ACE)
+
+Multiple covered entities under common ownership or control may designate themselves as a single **Affiliated Covered Entity (ACE)** for HIPAA purposes. This allows them to:
+
+- Share PHI without the need for BAAs between affiliated entities
+- Consolidate HIPAA compliance programs
+- Be treated as a single covered entity in some enforcement contexts
+
+**Designation must be:**
+
+- In writing
+- Limited to entities under common ownership or control
+
+---
+
+## 7. Organized Health Care Arrangements (OHCA)
+
+An **Organized Health Care Arrangement (OHCA)** is a clinically integrated care setting in which individuals typically receive health care from more than one health care provider. Members of an OHCA may share PHI for health care operations without a BAA.
+
+**Examples:**
+
+- A hospital and its medical staff
+- A multi-entity health system
+- An employer and a group health plan
+
+---
+
+## 8. Small Provider Compliance Considerations
+
+Small and solo practices face the same HIPAA obligations as large health systems, but with less capacity:
+
+| Challenge                    | Practical Approach for Small Providers                                        |
+| ---------------------------- | ----------------------------------------------------------------------------- |
+| Security Officer designation | Can be the practice owner or any trained staff member                         |
+| Risk analysis                | Simplified risk analysis tools available from HHS                             |
+| Staff training               | Online training programs (1-2 hours annually sufficient for basic compliance) |
+| Technical safeguards         | Cloud-based EHR vendors often provide compliant infrastructure — verify BAA   |
+| Physical safeguards          | Locked cabinets, screen privacy filters, visitor sign-in                      |
+| BAA management               | Most clearinghouses, billing services, and EHR vendors provide standard BAAs  |
+
+---
+
+## 9. When Are Non-Covered Entities Subject to HIPAA?
+
+HIPAA does not apply to non-covered entities directly. However:
+
+| Scenario                                                                    | HIPAA Applicability                                                                  |
+| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| Non-covered entity receives PHI from a covered entity                       | Not subject to HIPAA — but covered entity is still responsible for proper disclosure |
+| Non-covered entity acts as a Business Associate                             | Directly subject to HIPAA as a BA                                                    |
+| Consumer health app (Fitbit, Apple Health) not working for a covered entity | NOT subject to HIPAA (but FTC Health Breach Notification Rule may apply)             |
+| App developer building tools for a covered entity                           | Business Associate — subject to HIPAA                                                |
+| Researcher receiving de-identified data                                     | Not PHI — not subject to HIPAA                                                       |
+
+---
+
+## 10. Self-Determination Checklist
+
+Use this checklist to determine if an organization is a covered entity:
+
+| Question                                                                   | If YES                                                         |
+| -------------------------------------------------------------------------- | -------------------------------------------------------------- |
+| Do we provide health care services?                                        | Potential covered entity — check electronic transactions       |
+| Do we electronically submit claims to insurance?                           | Likely a covered entity (health care provider)                 |
+| Do we offer a health plan to employees?                                    | Likely a covered entity (health plan)                          |
+| Do we process health information on behalf of other organizations?         | Possible health care clearinghouse                             |
+| Do we only provide health care for cash payment with no electronic claims? | Probably NOT a covered entity                                  |
+| Do we provide services to a covered entity that require PHI access?        | Business Associate — not a covered entity, but still regulated |
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `05-business-associates.md`, `14-enforcement-penalties.md`

datasets/18-minimum-necessary-standard.md

@@ -0,0 +1,277 @@
+# Minimum Necessary Standard — HIPAA Dataset
+
+**Source:** 45 CFR §§ 164.502(b), 164.514(d)  
+**Authority:** U.S. Department of Health and Human Services (HHS)
+
+---
+
+## 1. Core Principle
+
+The **minimum necessary standard** requires covered entities to make reasonable efforts to limit the use of, disclosure of, and requests for PHI to the minimum amount necessary to accomplish the intended purpose.
+
+> **Legal Text (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."_
+
+---
+
+## 2. Explicit Exceptions — When the Standard Does NOT Apply
+
+The minimum necessary standard does **not** apply to:
+
+| Exception                                                                       | Basis                |
+| ------------------------------------------------------------------------------- | -------------------- |
+| **Disclosures to or requests by a health care provider for treatment purposes** | § 164.502(b)(2)(i)   |
+| **Disclosures to the individual who is the subject of the PHI**                 | § 164.502(b)(2)(ii)  |
+| **Uses or disclosures pursuant to a valid patient authorization**               | § 164.502(b)(2)(iii) |
+| **Disclosures to HHS for compliance and enforcement purposes**                  | § 164.502(b)(2)(iv)  |
+| **Uses or disclosures required by law**                                         | § 164.502(b)(2)(v)   |
+| **Uses or disclosures required for compliance with other HIPAA standards**      | § 164.502(b)(2)(vi)  |
+
+> **Critical Engineering Note:** Treatment disclosures between providers are fully exempt. A physician asking a consulting specialist for complete medical history does not violate minimum necessary. A billing department accessing the same records for coding purposes is subject to the standard.
+
+---
+
+## 3. Scope of Application
+
+The minimum necessary standard applies to:
+
+| Context                                                | Applies?               |
+| ------------------------------------------------------ | ---------------------- |
+| **Internal use** of PHI by workforce members           | YES                    |
+| **Disclosures** to external parties                    | YES                    |
+| **Requests** for PHI from other covered entities       | YES                    |
+| **Disclosures for treatment** by health care providers | NO (exception applies) |
+| **Disclosures to the patient**                         | NO (exception applies) |
+| **Research disclosures with proper authorization**     | NO (exception applies) |
+| **Disclosures to HHS**                                 | NO (exception applies) |
+
+---
+
+## 4. Required Implementation
+
+### 4.1 Workforce Access Policies (§ 164.514(d)(2))
+
+Covered entities must:
+
+1. Identify classes of workforce members who need access to PHI to do their jobs
+2. For each class, identify the category or categories of PHI they need access to
+3. Make reasonable efforts to limit access accordingly
+
+| Workforce Role          | Appropriate PHI Access                                  |
+| ----------------------- | ------------------------------------------------------- |
+| Treating physician      | Complete medical record                                 |
+| Billing specialist      | Diagnosis codes, procedure codes, insurance information |
+| Front desk / scheduling | Appointment data, basic demographics                    |
+| IT administrator        | System logs only — not clinical content                 |
+| Compliance officer      | Access to investigate specific complaints               |
+| HR generalist           | Employment data only — not clinical PHI                 |
+
+### 4.2 Routine vs. Non-Routine Disclosures (§ 164.514(d)(3), (4))
+
+| Type                  | Description                                      | Approach                                                                          |
+| --------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------- |
+| **Routine/Recurring** | Disclosures that occur regularly and predictably | Pre-define standard protocols; staff follow protocols without case-by-case review |
+| **Non-Routine**       | Disclosures that don't fit a standard protocol   | Require case-by-case review against minimum necessary criteria                    |
+
+### 4.3 Requests from Other Entities (§ 164.514(d)(5))
+
+When a covered entity makes a request for PHI from another covered entity or BA, it must limit the request to the minimum necessary to accomplish the purpose.
+
+---
+
+## 5. Engineering Implications
+
+### 5.1 Role-Based Access Control (RBAC)
+
+RBAC is the primary technical mechanism for enforcing minimum necessary:
+
+```sql
+-- Example: Role-based view restricting billing staff to non-clinical fields only
+CREATE VIEW billing_patient_view AS
+SELECT
+    patient_id,
+    first_name,
+    last_name,
+    date_of_birth,
+    insurance_member_id,
+    payer_id,
+    diagnosis_code,
+    procedure_code
+FROM patients
+-- billing staff cannot access: clinical_notes, medication_list, lab_results
+WHERE current_user_role() = 'billing';
+
+-- Treating providers get the full record
+CREATE VIEW clinical_patient_view AS
+SELECT *
+FROM patients
+WHERE current_user_role() IN ('physician', 'nurse', 'specialist');
+```
+
+### 5.2 Least Privilege Database Queries
+
+Enforce minimum necessary at the query level:
+
+```typescript
+// BAD: returns entire patient record for billing lookup
+async function getBillingInfo(patientId: string) {
+  return await db.patient.findUnique({ where: { id: patientId } }); // returns ALL fields
+}
+
+// GOOD: returns only the fields needed for billing
+async function getBillingInfo(patientId: string) {
+  return await db.patient.findUnique({
+    where: { id: patientId },
+    select: {
+      patientId: true,
+      firstName: true,
+      lastName: true,
+      dateOfBirth: true,
+      insuranceMemberId: true,
+      payerId: true,
+      diagnosisCode: true,
+      procedureCode: true,
+      // clinicalNotes: false  <-- implicitly excluded
+    },
+  });
+}
+```
+
+### 5.3 API Scoping
+
+API endpoints should be scoped to return only what is needed for each use case:
+
+```typescript
+// Separate endpoints for separate use cases
+router.get(
+  "/patient/:id/demographics",
+  requireRole("front-desk"),
+  getDemographics,
+);
+router.get("/patient/:id/billing", requireRole("billing"), getBillingInfo);
+router.get(
+  "/patient/:id/clinical",
+  requireRole("clinician"),
+  getClinicalRecord,
+);
+router.get("/patient/:id", requireRole("physician"), getFullRecord);
+```
+
+### 5.4 Prompt Minimization in AI Systems
+
+In RAG and LLM-based systems, minimum necessary applies to what PHI is included in prompts:
+
+```
+BAD prompt construction:
+"Here is the full patient record for John Smith (DOB 1965-03-14, SSN 123-45-6789,
+MRN 9982233): [full 200-field record]. Based on this, generate a summary for
+billing purposes."
+
+GOOD prompt construction:
+"Based on the following information: Diagnosis Code ICD-10 J44.1, Procedure Code
+99214, Payer ID BC001, Member ID MB00234 — generate the billing code description
+for the insurance submission."
+```
+
+For AI agents with PHI access:
+
+- Pass only the fields needed to answer the question
+- Do not pre-populate prompts with full records speculatively
+- Log what PHI was included in each LLM call for audit purposes
+
+### 5.5 Data Export Controls
+
+When implementing data export features:
+
+```typescript
+interface ExportRequest {
+  requestedBy: string; // User ID
+  purpose: string; // Business justification
+  fieldsRequested: string[]; // Explicit field list
+}
+
+async function processExportRequest(req: ExportRequest) {
+  // Validate that purpose is legitimate
+  if (!VALID_EXPORT_PURPOSES.includes(req.purpose)) {
+    throw new Error("Invalid export purpose");
+  }
+
+  // Validate that all requested fields are within the approved set for this purpose
+  const allowedFields = ALLOWED_FIELDS_BY_PURPOSE[req.purpose];
+  const unauthorized = req.fieldsRequested.filter(
+    (f) => !allowedFields.includes(f),
+  );
+
+  if (unauthorized.length > 0) {
+    throw new Error(
+      `Requested fields not allowed for purpose '${req.purpose}': ${unauthorized.join(", ")}`,
+    );
+  }
+
+  // Proceed with minimum necessary export
+  return db.patient.findMany({
+    select: Object.fromEntries(req.fieldsRequested.map((f) => [f, true])),
+  });
+}
+```
+
+---
+
+## 6. Verification for Non-Routine Disclosures
+
+For non-standard PHI disclosure requests, covered entities should implement a verification process:
+
+1. **Identify the requestor** — Who is asking? What is their identity?
+2. **Identify the purpose** — What is the stated purpose of the request?
+3. **Assess minimum necessary** — Is the amount of PHI being requested the minimum required for that purpose?
+4. **Document the decision** — Record the basis for disclosure and the minimum necessary determination
+
+---
+
+## 7. Common Violations of Minimum Necessary
+
+| Violation                   | Description                                                                      |
+| --------------------------- | -------------------------------------------------------------------------------- |
+| Mass records export         | Exporting entire patient database for a task requiring only a subset             |
+| Over-broad database queries | `SELECT *` queries when only specific fields are needed                          |
+| Fax/email blunder           | Sending complete record when only specific documents were requested              |
+| Access control gaps         | Giving all staff equal access regardless of role                                 |
+| AI prompt over-inclusion    | Including full PHI record in prompts when only specific fields are needed        |
+| Copy-all forwards           | Forwarding entire email chain with embedded PHI when only current context needed |
+| Reporting over-inclusion    | Including patient identifiers in aggregate reports when not needed               |
+
+---
+
+## 8. Business Associates and Minimum Necessary
+
+Business Associates are bound by the minimum necessary standard as follows:
+
+- BAs must only request and use the minimum PHI necessary to perform the contracted service
+- The BAA should specify the scope of PHI the BA is permitted to access
+- BAs may not use PHI for any purpose beyond the contracted services
+- If a BA receives more PHI than necessary, it should notify the CE and not use the excess
+
+---
+
+## 9. Minimum Necessary and the Right of Access
+
+The minimum necessary standard does **not** apply when an individual requests their own PHI under the Right of Access. Covered entities cannot use minimum necessary as a justification for withholding records from patients.
+
+> The individual who is the subject of the PHI is explicitly exempt from minimum necessary restrictions. Patients are entitled to request their **entire** designated record set.
+
+---
+
+## 10. Documentation Requirements
+
+Covered entities must document their minimum necessary policies and procedures:
+
+| Document                                                                     | Retention                                    |
+| ---------------------------------------------------------------------------- | -------------------------------------------- |
+| Minimum necessary policies (who can access what)                             | 6 years from creation or last effective date |
+| Non-routine disclosure decisions and justifications                          | 6 years                                      |
+| Workforce access level assignments                                           | 6 years                                      |
+| Requests received from external parties and the basis for what was disclosed | 6 years                                      |
+
+---
+
+**Related Datasets:** `01-hipaa-privacy-rule.md`, `07-patient-rights.md`, `08-technical-safeguards-engineering.md`, `17-covered-entities.md`

datasets/20-45-cfr-part-162-verbatim.md

@@ -0,0 +1,1438 @@
+# 45 CFR Part 162 — Verbatim Regulatory Text
+
+Source: https://www.ecfr.gov/api/versioner/v1/full/2026-04-24/title-45.xml
+
+Source URLs:
+
+- Canonical Part URL: https://www.ecfr.gov/current/title-45/part-162
+- Full Title 45 API Snapshot: https://www.ecfr.gov/api/versioner/v1/full/2026-04-24/title-45.xml
+- Title 45 Parts 160-164 Landing Page: https://www.ecfr.gov/current/title-45/parts-160-164
+
+Retrieved: 2026-04-28
+
+Notes:
+
+- This file contains the exact XML subtree for 45 CFR Part 162 from the official eCFR API.
+- The content below is verbatim regulatory text with original structural tags preserved.
+
+```xml
+<DIV5 N="162" TYPE="PART" VOLUME="2">
+<HEAD>PART 162—ADMINISTRATIVE REQUIREMENTS
+</HEAD>
+<AUTH>
+<HED>Authority:</HED><PSPACE>42 U.S.C. 1320d—1320d-9 and secs. 1104 and 10109 of Pub. L. 111-148, 124 Stat. 146-154 and 915-917.
+
+
+</PSPACE></AUTH>
+<SOURCE>
+<HED>Source:</HED><PSPACE>65 FR 50367, Aug. 17, 2000, unless otherwise noted.
+
+
+
+
+</PSPACE></SOURCE>
+
+<DIV6 N="A" TYPE="SUBPART">
+<HEAD>Subpart A—General Provisions</HEAD>
+
+
+<DIV8 N="162.100" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.100   Applicability.</HEAD>
+<P>Covered entities (as defined in § 160.103 of this subchapter) must comply with the applicable requirements of this part.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.103" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.103   Definitions.</HEAD>
+<XREF ID="20260324" REFID="55" AMDINSN="4">Link to an amendment published at 91 FR 14404, Mar. 24, 2026.</XREF>
+<P>For purposes of this part, the following definitions apply:
+</P>
+<P><I>Code set</I> means any set of codes used to encode data elements, such as tables of terms, medical concepts, medical diagnostic codes, or medical procedure codes. A code set includes the codes and the descriptors of the codes.
+</P>
+<P><I>Code set maintaining organization</I> means an organization that creates and maintains the code sets adopted by the Secretary for use in the transactions for which standards are adopted in this part.
+</P>
+<P><I>Covered health care provider</I> means a health care provider that meets the definition at paragraph (3) of the definition of “covered entity” at § 160.103.
+</P>
+<P><I>Data condition</I> means the rule that describes the circumstances under which a covered entity must use a particular data element or segment.
+</P>
+<P><I>Data content</I> means all the data elements and code sets inherent to a transaction, and not related to the format of the transaction. Data elements that are related to the format are not data content.
+</P>
+<P><I>Data element</I> means the smallest named unit of information in a transaction.
+</P>
+<P><I>Data set</I> means a semantically meaningful unit of information exchanged between two parties to a transaction.
+</P>
+<P><I>Descriptor</I> means the text defining a code.
+</P>
+<P><I>Designated standard maintenance organization (DSMO)</I> means an organization designated by the Secretary under § 162.910(a).
+</P>
+<P><I>Direct data entry</I> means the direct entry of data (for example, using dumb terminals or web browsers) that is immediately transmitted into a health plan's computer.
+</P>
+<P><I>Format</I> refers to those data elements that provide or control the enveloping or hierarchical structure, or assist in identifying data content of, a transaction.
+</P>
+<P><I>HCPCS</I> stands for the Health [Care Financing Administration] Common Procedure Coding System.
+</P>
+<P><I>Maintain</I> or <I>maintenance</I> refers to activities necessary to support the use of a standard adopted by the Secretary, including technical corrections to an implementation specification, and enhancements or expansion of a code set. This term excludes the activities related to the adoption of a new standard or implementation specification, or modification to an adopted standard or implementation specification.
+</P>
+<P><I>Maximum defined data</I> set means all of the required data elements for a particular standard based on a specific implementation specification.
+</P>
+<P><I>Operating rules</I> means the necessary business rules and guidelines for the electronic exchange of information that are not defined by a standard or its implementation specifications as adopted for purposes of this part.
+</P>
+<P><I>Segment</I> means a group of related data elements in a transaction.
+</P>
+<P><I>Stage 1 payment initiation</I> means a health plan's order, instruction or authorization to its financial institution to make a health care claims payment using an electronic funds transfer (EFT) through the ACH Network.
+</P>
+<P><I>Standard transaction</I> means a transaction that complies with an applicable standard and associated operating rules adopted under this part.
+</P>
+<CITA TYPE="N">[65 FR 50367, Aug. 17, 2000, as amended at 68 FR 8374, Feb. 20, 2003; 74 FR 3324, Jan. 16, 2009; 76 FR 40495, July 8, 2011; 77 FR 1589, Jan. 10, 2012; 77 FR 54719, Sept. 5, 2012; 84 FR 57629, Oct. 28, 2019]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="B-C" TYPE="SUBPART">
+<HEAD>Subparts B-C [Reserved]</HEAD>
+
+</DIV6>
+
+
+<DIV6 N="D" TYPE="SUBPART">
+<HEAD>Subpart D—Standard Unique Health Identifier for Health Care Providers</HEAD>
+
+<SOURCE>
+<HED>Source:</HED><PSPACE>69 FR 3468, Jan. 23, 2004, unless otherwise noted.
+
+
+</PSPACE></SOURCE>
+
+<DIV8 N="162.402" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.402   [Reserved]</HEAD>
+</DIV8>
+
+
+<DIV8 N="162.404" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.404   Compliance dates of the implementation of the standard unique health identifier for health care providers.</HEAD>
+<P>(a) <I>Health care providers.</I> A covered health care provider must comply with the implementation specifications in § 162.410 no later than May 23, 2007.
+</P>
+<P>(b) <I>Health plans.</I> A health plan must comply with the implementation specifications in § 162.412 no later than one of the following dates:
+</P>
+<P>(1) A health plan that is not a small health plan—May 23, 2007.
+</P>
+<P>(2) A small health plan—May 23, 2008.
+</P>
+<P>(c) <I>Health care clearinghouses.</I> A health care clearinghouse must comply with the implementation specifications in § 162.414 no later than May 23, 2007.
+</P>
+<CITA TYPE="N">[69 FR 3468, Jan. 23, 2004, as amended at 77 FR 54719, Sept. 5, 2012]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.406" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.406   Standard unique health identifier for health care providers.</HEAD>
+<P>(a) <I>Standard.</I> The standard unique health identifier for health care providers is the National Provider Identifier (NPI). The NPI is a 10-position numeric identifier, with a check digit in the 10th position, and no intelligence about the health care provider in the number.
+</P>
+<P>(b) <I>Required and permitted uses for the NPI.</I> (1) The NPI must be used as stated in §§ 162.410, 162.412, and 162.414.
+</P>
+<P>(2) The NPI may be used for any other lawful purpose.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.408" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.408   National Provider System.</HEAD>
+<P><I>National Provider System.</I> The National Provider System (NPS) shall do the following:
+</P>
+<P>(a) Assign a single, unique NPI to a health care provider, provided that—
+</P>
+<P>(1) The NPS may assign an NPI to a subpart of a health care provider in accordance with paragraph (g); and
+</P>
+<P>(2) The Secretary has sufficient information to permit the assignment to be made.
+</P>
+<P>(b) Collect and maintain information about each health care provider that has been assigned an NPI and perform tasks necessary to update that information.
+</P>
+<P>(c) If appropriate, deactivate an NPI upon receipt of appropriate information concerning the dissolution of the health care provider that is an organization, the death of the health care provider who is an individual, or other circumstances justifying deactivation.
+</P>
+<P>(d) If appropriate, reactivate a deactivated NPI upon receipt of appropriate information.
+</P>
+<P>(e) Not assign a deactivated NPI to any other health care provider.
+</P>
+<P>(f) Disseminate NPS information upon approved requests.
+</P>
+<P>(g) Assign an NPI to a subpart of a health care provider on request if the identifying data for the subpart are unique.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.410" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.410   Implementation specifications: Health care providers.</HEAD>
+<P>(a) A covered entity that is a covered health care provider must:
+</P>
+<P>(1) Obtain, by application if necessary, an NPI from the National Provider System (NPS) for itself or for any subpart of the covered entity that would be a covered health care provider if it were a separate legal entity. A covered entity may obtain an NPI for any other subpart that qualifies for the assignment of an NPI.
+</P>
+<P>(2) Use the NPI it obtained from the NPS to identify itself on all standard transactions that it conducts where its health care provider identifier is required.
+</P>
+<P>(3) Disclose its NPI, when requested, to any entity that needs the NPI to identify that covered health care provider in a standard transaction.
+</P>
+<P>(4) Communicate to the NPS any changes in its required data elements in the NPS within 30 days of the change.
+</P>
+<P>(5) If it uses one or more business associates to conduct standard transactions on its behalf, require its business associate(s) to use its NPI and other NPIs appropriately as required by the transactions that the business associate(s) conducts on its behalf.
+</P>
+<P>(6) If it has been assigned NPIs for one or more subparts, comply with the requirements of paragraphs (a)(2) through (a)(5) of this section with respect to each of those NPIs.
+</P>
+<P>(b) An organization covered health care provider that has as a member, employs, or contracts with, an individual health care provider who is not a covered entity and is a prescriber, must require such health care provider to—
+</P>
+<P>(1) Obtain an NPI from the National Plan and Provider Enumeration System (NPPES); and
+</P>
+<P>(2) To the extent the prescriber writes a prescription while acting within the scope of the prescriber's relationship with the organization, disclose the NPI upon request to any entity that needs it to identify the prescriber in a standard transaction.
+</P>
+<P>(c) A health care provider that is not a covered entity may obtain, by application if necessary, an NPI from the NPS.
+</P>
+<CITA TYPE="N">[69 FR 3468, Jan. 23, 2004, as amended at 77 FR 54719, Sept. 5, 2012]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.412" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.412   Implementation specifications: Health plans.</HEAD>
+<P>(a) A health plan must use the NPI of any health care provider (or subpart(s), if applicable) that has been assigned an NPI to identify that health care provider on all standard transactions where that health care provider's identifier is required.
+</P>
+<P>(b) A health plan may not require a health care provider that has been assigned an NPI to obtain an additional NPI.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.414" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.414   Implementation specifications: Health care clearinghouses.</HEAD>
+<P>A health care clearinghouse must use the NPI of any health care provider (or subpart(s), if applicable) that has been assigned an NPI to identify that health care provider on all standard transactions where that health care provider's identifier is required.
+
+
+</P>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="E" TYPE="SUBPART">
+<HEAD>Subpart E [Reserved]</HEAD>
+
+</DIV6>
+
+
+<DIV6 N="F" TYPE="SUBPART">
+<HEAD>Subpart F—Standard Unique Employer Identifier</HEAD>
+
+<SOURCE>
+<HED>Source:</HED><PSPACE>67 FR 38020, May 31, 2002, unless otherwise noted.
+
+
+</PSPACE></SOURCE>
+
+<DIV8 N="162.600" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.600   Compliance dates of the implementation of the standard unique employer identifier.</HEAD>
+<P>(a) <I>Health care providers.</I> Health care providers must comply with the requirements of this subpart no later than July 30, 2004.
+</P>
+<P>(b) <I>Health plans.</I> A health plan must comply with the requirements of this subpart no later than one of the following dates:
+</P>
+<P>(1) <I>Health plans other than small health plans</I>—July 30, 2004.
+</P>
+<P>(2) <I>Small health plans</I>—August 1, 2005.
+</P>
+<P>(c) <I>Health care clearinghouses.</I> Health care clearinghouses must comply with the requirements of this subpart no later than July 30, 2004.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.605" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.605   Standard unique employer identifier.</HEAD>
+<P>The Secretary adopts the EIN as the standard unique employer identifier provided for by 42 U.S.C. 1320d-2(b).
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.610" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.610   Implementation specifications for covered entities.</HEAD>
+<P>(a) The standard unique employer identifier of an employer of a particular employee is the EIN that appears on that employee's IRS Form W-2, Wage and Tax Statement, from the employer.
+</P>
+<P>(b) A covered entity must use the standard unique employer identifier (EIN) of the appropriate employer in standard transactions that require an employer identifier to identify a person or entity as an employer, including where situationally required.
+</P>
+<P>(c) Required and permitted uses for the Employer Identifier.
+</P>
+<P>(1) The Employer Identifier must be used as stated in § 162.610(b).
+</P>
+<P>(2) The Employer Identifier may be used for any other lawful purpose.
+</P>
+<CITA TYPE="N">[67 FR 38020, May 31, 2002, as amended at 69 FR 3469, Jan. 23, 2004]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="G-H" TYPE="SUBPART">
+<HEAD>Subparts G-H [Reserved]</HEAD>
+
+</DIV6>
+
+
+<DIV6 N="I" TYPE="SUBPART">
+<HEAD>Subpart I—General Provisions for Transactions</HEAD>
+
+
+<DIV8 N="162.900" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.900   [Reserved]</HEAD>
+</DIV8>
+
+
+<DIV8 N="162.910" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.910   Maintenance of standards and adoption of modifications and new standards.</HEAD>
+<P>(a) <I>Designation of DSMOs.</I> (1) The Secretary may designate as a DSMO an organization that agrees to conduct, to the satisfaction of the Secretary, the following functions:
+</P>
+<P>(i) Maintain standards adopted under this subchapter.
+</P>
+<P>(ii) Receive and process requests for adopting a new standard or modifying an adopted standard.
+</P>
+<P>(2) The Secretary designates a DSMO by notice in the <E T="04">Federal Register.</E>
+</P>
+<P>(b) <I>Maintenance of standards.</I> Maintenance of a standard by the appropriate DSMO constitutes maintenance of the standard for purposes of this part, if done in accordance with the processes the Secretary may require.
+</P>
+<P>(c) <I>Process for modification of existing standards and adoption of new standards.</I> The Secretary considers a recommendation for a proposed modification to an existing standard, or a proposed new standard, only if the recommendation is developed through a process that provides for the following:
+</P>
+<P>(1) Open public access.
+</P>
+<P>(2) Coordination with other DSMOs.
+</P>
+<P>(3) An appeals process for each of the following, if dissatisfied with the decision on the request:
+</P>
+<P>(i) The requestor of the proposed modification.
+</P>
+<P>(ii) A DSMO that participated in the review and analysis of the request for the proposed modification, or the proposed new standard.
+</P>
+<P>(4) Expedited process to address content needs identified within the industry, if appropriate.
+</P>
+<P>(5) Submission of the recommendation to the National Committee on Vital and Health Statistics (NCVHS).
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.915" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.915   Trading partner agreements.</HEAD>
+<P>A covered entity must not enter into a trading partner agreement that would do any of the following:
+</P>
+<P>(a) Change the definition, data condition, or use of a data element or segment in a standard or operating rule, except where necessary to implement State or Federal law, or to protect against fraud and abuse.
+</P>
+<P>(b) Add any data elements or segments to the maximum defined data set.
+</P>
+<P>(c) Use any code or data elements that are either marked “not used” in the standard's implementation specification or are not in the standard's implementation specification(s).
+</P>
+<P>(d) Change the meaning or intent of the standard's implementation specification(s).
+</P>
+<CITA TYPE="N">[65 FR 50367, Aug. 17, 2000, as amended at 76 FR 40495, July 8, 2011]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.920" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.920   Availability of implementation specifications and operating rules.</HEAD>
+<XREF ID="20260324" REFID="56" AMDINSN="5">Link to an amendment published at 91 FR 14404, Mar. 24, 2026.</XREF>
+<P>Certain material is incorporated by reference into this subpart with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. To enforce any edition other than that specified in this section, the Department of Health and Human Services (the Department) must publish a document in the <E T="04">Federal Register</E> and the material must be available to the public. All approved incorporation by reference (IBR) material is available for inspection at the Centers for Medicare &amp; Medicaid Services (CMS) and at the National Archives and Records Administration (NARA). Contact CMS at: 7500 Security Boulevard, Baltimore, Maryland 21244; phone: (410) 786-6597; email: <I>administrativesimplification@cms.hhs.gov</I>. For information on the availability of this material at NARA, visit <I>www.archives.gov/federal-register/cfr/ibr-locations</I> or email <I>fr.inspection@nara.gov</I>. The material may be obtained from the following sources:
+
+
+</P>
+<P>(a) <I>ASC X12N specifications and the ASC X12 Standards for Electronic Data Interchange Technical Report Type 3.</I> The implementation specifications for the ASC X12N and the ASC X12 Standards for Electronic Data Interchange Technical Report Type 3 (and accompanying Errata or Type 1 Errata) may be obtained from the ASC X12, 7600 Leesburg Pike, Suite 430, Falls Church, VA 22043; Telephone (703) 970-4480; and FAX (703) 970-4488. They are also available through the internet at <I>http://www.X12.org.</I> A fee is charged for all implementation specifications, including Technical Reports Type 3. Charging for such publications is consistent with the policies of other publishers of standards. The transaction implementation specifications are as follows:
+
+
+
+
+</P>
+<P>(1) The ASC X12N 837—Health Care Claim: Dental, Version 4010, May 2000, Washington Publishing Company, 004010X097 and Addenda to Health Care Claim: Dental, Version 4010, October 2002, Washington Publishing Company, 004010X097A1, as referenced in § 162.1102 and § 162.1802.
+</P>
+<P>(2) The ASC X12N 837—Health Care Claim: Professional, Volumes 1 and 2, Version 4010, May 2000, Washington Publishing Company, 004010X098 and Addenda to Health Care Claim: Professional, Volumes 1 and 2, Version 4010, October 2002, Washington Publishing Company, 004010X098A1, as referenced in § 162.1102 and § 162.1802.
+</P>
+<P>(3) The ASC X12N 837—Health Care Claim: Institutional, Volumes 1 and 2, Version 4010, May 2000, Washington Publishing Company, 004010X096 and Addenda to Health Care Claim: Institutional, Volumes 1 and 2, Version 4010, October 2002, Washington Publishing Company, 004010X096A1 as referenced in § 162.1102 and § 162.1802.
+</P>
+<P>(4) The ASC X12N 835—Health Care Claim Payment/Advice, Version 4010, May 2000, Washington Publishing Company, 004010X091, and Addenda to Health Care Claim Payment/Advice, Version 4010, October 2002, Washington Publishing Company, 004010X091A1 as referenced in § 162.1602.
+</P>
+<P>(5) ASC X12N 834—Benefit Enrollment and Maintenance, Version 4010, May 2000, Washington Publishing Company, 004010X095 and Addenda to Benefit Enrollment and Maintenance, Version 4010, October 2002, Washington Publishing Company, 004010X095A1, as referenced in § 162.1502.
+</P>
+<P>(6) The ASC X12N 820—Payroll Deducted and Other Group Premium Payment for Insurance Products, Version 4010, May 2000, Washington Publishing Company, 004010X061, and Addenda to Payroll Deducted and Other Group Premium Payment for Insurance Products, Version 4010, October 2002, Washington Publishing Company, 004010X061A1, as referenced in § 162.1702.
+</P>
+<P>(7) The ASC X12N 278—Health Care Services Review—Request for Review and Response, Version 4010, May 2000, Washington Publishing Company, 004010X094 and Addenda to Health Care Services Review—Request for Review and Response, Version 4010, October 2002, Washington Publishing Company, 004010X094A1, as referenced in § 162.1302.
+</P>
+<P>(8) The ASC X12N-276/277 Health Care Claim Status Request and Response, Version 4010, May 2000, Washington Publishing Company, 004010X093 and Addenda to Health Care Claim Status Request and Response, Version 4010, October 2002, Washington Publishing Company, 004010X093A1, as referenced in § 162.1402.
+</P>
+<P>(9) The ASC X12N 270/271—Health Care Eligibility Benefit Inquiry and Response, Version 4010, May 2000, Washington Publishing Company, 004010X092 and Addenda to Health Care Eligibility Benefit Inquiry and Response, Version 4010, October 2002, Washington Publishing Company, 004010X092A1, as referenced in § 162.1202.
+</P>
+<P>(10) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Dental (837), May 2006, ASC X12N/005010X224, and Type 1 Errata to Health Care Claim Dental (837), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X224A1, as referenced in § 162.1102 and § 162.1802.
+</P>
+<P>(11) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Professional (837), May 2006, ASC X12, 005010X222, as referenced in § 162.1102 and § 162.1802.
+</P>
+<P>(12) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Institutional (837), May 2006, ASC X12/N005010X223, and Type 1 Errata to Health Care Claim: Institutional (837), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X223A1, as referenced in § 162.1102 and § 162.1802.
+</P>
+<P>(13) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim Payment/Advice (835), April 2006, ASC X12N/005010X221, as referenced in § 162.1602.
+</P>
+<P>(14) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Benefit Enrollment and Maintenance (834), August 2006, ASC X12N/005010X220, as referenced in § 162.1502.
+</P>
+<P>(15) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Payroll Deducted and Other Group Premium Payment for Insurance Products (820), February 2007, ASC X12N/005010X218, as referenced in § 162.1702.
+</P>
+<P>(16) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Services Review—Request for Review and Response (278), May 2006, ASC X12N/005010X217, and Errata to Health Care Services Review—Request for Review and Response (278), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, April 2008, ASC X12N/005010X217E1, as referenced in § 162.1302.
+</P>
+<P>(17) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim Status Request and Response (276/277), August 2006, ASC X12N/005010X212, and Errata to Health Care Claim Status Request and Response (276/277), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, April 2008, ASC X12N/005010X212E1, as referenced in § 162.1402.
+</P>
+<P>(18) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Eligibility Benefit Inquiry and Response (270/271), April 2008, ASC X12N/005010X279, as referenced in § 162.1202.
+
+
+</P>
+<P>(b) <I>Retail pharmacy specifications and Medicaid pharmacy subrogation implementation guides.</I> The implementation specifications for the retail pharmacy standards and the implementation specifications for the batch standard for the Medicaid pharmacy subrogation transaction may be obtained from the National Council for Prescription Drug Programs, 9240 East Raintree Drive, Scottsdale, AZ 85260. Telephone (480) 477-1000; FAX (480) 767-1042. They are also available through the internet at <I>www.ncpdp.org.</I> A fee is charged for all NCPDP Implementation Guides. Charging for such publications is consistent with the policies of other publishers of standards. The transaction implementation specifications are as follows:
+
+
+</P>
+<P>(1) The Telecommunication Standard Implementation Guide Version 5, Release 1 (Version 5.1), September 1999, National Council for Prescription Drug Programs, as referenced in §§ 162.1102, 162.1202, 162.1302, 162.1602, and 162.1802.
+</P>
+<P>(2) The Batch Standard Batch Implementation Guide, Version 1, Release 1 (Version 1.1), January 2000, supporting Telecommunication Standard Implementation Guide, Version 5, Release 1 (Version 5.1) for the NCPDP Data Record in the Detail Data Record, National Council for Prescription Drug Programs, as referenced in §§ 162.1102, 162.1202, 162.1302, and 162.1802.
+</P>
+<P>(3) The National Council for Prescription Drug Programs (NCPDP) equivalent NCPDP Batch Standard Batch Implementation Guide, Version 1, Release 0, February 1, 1996, as referenced in §§ 162.1102, 162.1202, 162.1602, and 162.1802.
+</P>
+<P>(4) The Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007, National Council for Prescription Drug Programs, as referenced in §§ 162.1102, 162.1202, 162.1302, and 162.1802.
+</P>
+<P>(5) The Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), January 2006, National Council for Prescription Drug Programs, as referenced in §§ 162.1102, 162.1202, 162.1302, and 162.1802.
+</P>
+<P>(6) The Batch Standard Medicaid Subrogation Implementation Guide, Version 3, Release 0 (Version 3.0), July 2007, National Council for Prescription Drug Programs, as referenced in § 162.1902.
+</P>
+<P>(7) The Telecommunication Standard Implementation Guide Version F6 published January 2020; as referenced in §§ 162.1102; 162.1202; 162.1302; 162.1802.
+</P>
+<P>(8) The Batch Standard Implementation Guide, Version 15, published October 2017; as referenced in §§ 162.1102; 162.1202; 162.1302; 162.1802.
+</P>
+<P>(9) The Subrogation Implementation Guide for Batch Standard, Version 10, republished September 2019; as referenced in § 162.1902.
+
+
+
+
+
+
+</P>
+<P>(c) Council for Affordable Quality Healthcare's (CAQH) Committee on Operating Rules for Information Exchange (CORE), 601 Pennsylvania Avenue, NW. South Building, Suite 500 Washington, DC 20004; Telephone (202) 861-1492; Fax (202) 861- 1454; E-mail <I>info@CAQH.org</I>; and Internet at <I>http://www.caqh.org/benefits.php.</I>
+</P>
+<P>(1) CAQH, Committee on Operating Rules for Information Exchange, CORE Phase I Policies and Operating Rules, Approved April 2006, v5010 Update March 2011.
+</P>
+<P>(i) Phase I CORE 152: Eligibility and Benefit Real Time Companion Guide Rule, version 1.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(ii) Phase I CORE 153: Eligibility and Benefits Connectivity Rule, version 1.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(iii) Phase I CORE 154: Eligibility and Benefits 270/271 Data Content Rule, version 1.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(iv) Phase I CORE 155: Eligibility and Benefits Batch Response Time Rule, version 1.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(v) Phase I CORE 156: Eligibility and Benefits Real Time Response Time Rule, version 1.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(vi) Phase I CORE 157: Eligibility and Benefits System Availability Rule, version 1.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(2) ACME Health Plan, HIPAA Transaction Standard Companion Guide, Refers to the Implementation Guides Based on ASC X12 version 005010, CORE v5010 Master Companion Guide Template, 005010, 1.2, (CORE v 5010 Master Companion Guide Template, 005010, 1.2), March 2011, as referenced in §§ 162.1203, 162.1403, and 162.1603.
+</P>
+<P>(3) CAQH, Committee on Operating Rules for Information Exchange, CORE Phase II Policies and Operating Rules, Approved July 2008, v5010 Update March 2011.
+</P>
+<P>(i) Phase II CORE 250: Claim Status Rule, version 2.1.0, March 2011, as referenced in § 162.1403.
+</P>
+<P>(ii) Phase II CORE 258: Eligibility and Benefits 270/271 Normalizing Patient Last Name Rule, version 2.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(iii) Phase II CORE 259: Eligibility and Benefits 270/271 AAA Error Code Reporting Rule, version 2.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(iv) Phase II CORE 260: Eligibility &amp; Benefits Data Content (270/271) Rule, version 2.1.0, March 2011, as referenced in § 162.1203.
+</P>
+<P>(v) Phase II CORE 270: Connectivity Rule, version 2.2.0, March 2011, as referenced in § 162.1203 and § 162.1403.
+</P>
+<P>(4) Council for Affordable Quality Healthcare (CAQH) Phase III Committee on Operating Rules for Information Exchange (CORE) EFT &amp; ERA Operating Rule Set, Approved June 2012, as specified in this paragraph and referenced in § 162.1603.
+</P>
+<P>(i) Phase III CORE 380 EFT Enrollment Data Rule, version 3.0.0, June 2012.
+</P>
+<P>(ii) Phase III CORE 382 ERA Enrollment Data Rule, version 3.0.0, June 2012.
+</P>
+<P>(iii) Phase III 360 CORE Uniform Use of CARCs and RARCs (835) Rule, version 3.0.0, June 2012.
+</P>
+<P>(iv) CORE-required Code Combinations for CORE-defined Business Scenarios for the Phase III CORE 360 Uniform Use of Claim Adjustment Reason Codes and Remittance Advice Remark Codes (835) Rule, version 3.0.0, June 2012.
+</P>
+<P>(v) Phase III CORE 370 EFT &amp; ERA Reassociation (CCD+/835) Rule, version 3.0.0, June 2012.
+</P>
+<P>(vi) Phase III CORE 350 Health Care Claim Payment/Advice (835) Infrastructure Rule, version 3.0.0, June 2012, except Requirement 4.2 titled “Health Care Claim Payment/Advice Batch Acknowledgement Requirements”.
+</P>
+<P>(d) The National Automated Clearing House Association (NACHA), The Electronic Payments Association, 1350 Sunrise Valle Drive, Suite 100, Herndon, Virginia 20171 (Phone) (703) 561-1100; (Fax) (703) 713-1641; Email: <I>info@nacha.org;</I> and Internet at <I>http://www.nacha.org.</I> The implementation specifications are as follows:
+</P>
+<P>(1) 2011 NACHA Operating Rules &amp; Guidelines, A Complete Guide to the Rules Governing the ACH Network, NACHA Operating Rules, Appendix One: ACH File Exchange Specifications (Operating Rule 59) as referenced in § 162.1602.
+</P>
+<P>(2) 2011 NACHA Operating Rules &amp; Guidelines, A Complete Guide to the Rules Governing the ACH Network, NACHA Operating Rules Appendix Three: ACH Record Format Specifications (Operating Rule 78), Part 3.1, Subpart 3.1.8 Sequence of Records for CCD Entries as referenced in § 162.1602.
+
+
+</P>
+<CITA TYPE="N">[68 FR 8396, Feb. 20, 2003, as amended at 69 FR 18803, Apr. 9, 2004; 74 FR 3324, Jan. 16, 2009; 76 FR 40495, July 8, 2011; 77 FR 1590, Jan. 10, 2012; 77 FR 48043, Aug. 10, 2012; 89 FR 100787, Dec. 13, 2024]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.923" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.923   Requirements for covered entities.</HEAD>
+<P>(a) <I>General rule.</I> Except as otherwise provided in this part, if a covered entity conducts, with another covered entity that is required to comply with a transaction standard adopted under this part (or within the same covered entity), using electronic media, a transaction for which the Secretary has adopted a standard under this part, the covered entity must conduct the transaction as a standard transaction.
+</P>
+<P>(b) <I>Exception for direct data entry transactions.</I> A health care provider electing to use direct data entry offered by a health plan to conduct a transaction for which a standard has been adopted under this part must use the applicable data content and data condition requirements of the standard when conducting the transaction. The health care provider is not required to use the format requirements of the standard.
+</P>
+<P>(c) <I>Use of a business associate.</I> A covered entity may use a business associate, including a health care clearinghouse, to conduct a transaction covered by this part. If a covered entity chooses to use a business associate to conduct all or part of a transaction on behalf of the covered entity, the covered entity must require the business associate to do the following:
+</P>
+<P>(1) Comply with all applicable requirements of this part.
+</P>
+<P>(2) Require any agent or subcontractor to comply with all applicable requirements of this part.
+</P>
+<CITA TYPE="N">[65 FR 50367, Aug. 17, 2000, as amended at 74 FR 3325, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.925" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.925   Additional requirements for health plans.</HEAD>
+<P>(a) <I>General rules.</I> (1) If an entity requests a health plan to conduct a transaction as a standard transaction, the health plan must do so.
+</P>
+<P>(2) A health plan may not delay or reject a transaction, or attempt to adversely affect the other entity or the transaction, because the transaction is a standard transaction.
+</P>
+<P>(3) A health plan may not reject a standard transaction on the basis that it contains data elements not needed or used by the health plan (for example, coordination of benefits information).
+</P>
+<P>(4) A health plan may not offer an incentive for a health care provider to conduct a transaction covered by this part as a transaction described under the exception provided for in § 162.923(b).
+</P>
+<P>(5) A health plan that operates as a health care clearinghouse, or requires an entity to use a health care clearinghouse to receive, process, or transmit a standard transaction may not charge fees or costs in excess of the fees or costs for normal telecommunications that the entity incurs when it directly transmits, or receives, a standard transaction to, or from, a health plan.
+</P>
+<P>(6) During the period from March 17, 2009 through December 31, 2011, a health plan may not delay or reject a standard transaction, or attempt to adversely affect the other entity or the transaction, on the basis that it does not comply with another adopted standard for the same period.
+</P>
+<P>(b) <I>Coordination of benefits.</I> If a health plan receives a standard transaction and coordinates benefits with another health plan (or another payer), it must store the coordination of benefits data it needs to forward the standard transaction to the other health plan (or other payer).
+</P>
+<P>(c) <I>Code sets.</I> A health plan must meet each of the following requirements:
+</P>
+<P>(1) Accept and promptly process any standard transaction that contains codes that are valid, as provided in subpart J of this part.
+</P>
+<P>(2) Keep code sets for the current billing period and appeals periods still open to processing under the terms of the health plan's coverage.
+</P>
+<CITA TYPE="N">[65 FR 50367, Aug. 17, 2000, as amended at 74 FR 3325, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.930" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.930   Additional rules for health care clearinghouses.</HEAD>
+<P>When acting as a business associate for another covered entity, a health care clearinghouse may perform the following functions:
+</P>
+<P>(a) Receive a standard transaction on behalf of the covered entity and translate it into a nonstandard transaction (for example, nonstandard format and/or nonstandard data content) for transmission to the covered entity.
+</P>
+<P>(b) Receive a nonstandard transaction (for example, nonstandard format and/or nonstandard data content) from the covered entity and translate it into a standard transaction for transmission on behalf of the covered entity.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.940" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.940   Exceptions from standards to permit testing of proposed modifications.</HEAD>
+<P>(a) <I>Requests for an exception.</I> An organization may request an exception from the use of a standard from the Secretary to test a proposed modification to that standard. For each proposed modification, the organization must meet the following requirements:
+</P>
+<P>(1) <I>Comparison to a current standard.</I> Provide a detailed explanation, no more than 10 pages in length, of how the proposed modification would be a significant improvement to the current standard in terms of the following principles:
+</P>
+<P>(i) Improve the efficiency and effectiveness of the health care system by leading to cost reductions for, or improvements in benefits from, electronic health care transactions.
+</P>
+<P>(ii) Meet the needs of the health data standards user community, particularly health care providers, health plans, and health care clearinghouses.
+</P>
+<P>(iii) Be uniform and consistent with the other standards adopted under this part and, as appropriate, with other private and public sector health data standards.
+</P>
+<P>(iv) Have low additional development and implementation costs relative to the benefits of using the standard.
+</P>
+<P>(v) Be supported by an ANSI-accredited SSO or other private or public organization that would maintain the standard over time.
+</P>
+<P>(vi) Have timely development, testing, implementation, and updating procedures to achieve administrative simplification benefits faster.
+</P>
+<P>(vii) Be technologically independent of the computer platforms and transmission protocols used in electronic health transactions, unless they are explicitly part of the standard.
+</P>
+<P>(viii) Be precise, unambiguous, and as simple as possible.
+</P>
+<P>(ix) Result in minimum data collection and paperwork burdens on users.
+</P>
+<P>(x) Incorporate flexibility to adapt more easily to changes in the health care infrastructure (such as new services, organizations, and provider types) and information technology.
+</P>
+<P>(2) <I>Specifications for the proposed modification.</I> Provide specifications for the proposed modification, including any additional system requirements.
+</P>
+<P>(3) <I>Testing of the proposed modification.</I> Provide an explanation, no more than 5 pages in length, of how the organization intends to test the standard, including the number and types of health plans and health care providers expected to be involved in the test, geographical areas, and beginning and ending dates of the test.
+</P>
+<P>(4) <I>Trading partner concurrences.</I> Provide written concurrences from trading partners who would agree to participate in the test.
+</P>
+<P>(b) <I>Basis for granting an exception.</I> The Secretary may grant an initial exception, for a period not to exceed 3 years, based on, but not limited to, the following criteria:
+</P>
+<P>(1) An assessment of whether the proposed modification demonstrates a significant improvement to the current standard.
+</P>
+<P>(2) The extent and length of time of the exception.
+</P>
+<P>(3) Consultations with DSMOs.
+</P>
+<P>(c) <I>Secretary's decision on exception.</I> The Secretary makes a decision and notifies the organization requesting the exception whether the request is granted or denied.
+</P>
+<P>(1) <I>Exception granted.</I> If the Secretary grants an exception, the notification includes the following information:
+</P>
+<P>(i) The length of time for which the exception applies.
+</P>
+<P>(ii) The trading partners and geographical areas the Secretary approves for testing.
+</P>
+<P>(iii) Any other conditions for approving the exception.
+</P>
+<P>(2) <I>Exception denied.</I> If the Secretary does not grant an exception, the notification explains the reasons the Secretary considers the proposed modification would not be a significant improvement to the current standard and any other rationale for the denial.
+</P>
+<P>(d) <I>Organization's report on test results.</I> Within 90 days after the test is completed, an organization that receives an exception must submit a report on the results of the test, including a cost-benefit analysis, to a location specified by the Secretary by notice in the <E T="04">Federal Register.</E>
+</P>
+<P>(e) <I>Extension allowed.</I> If the report submitted in accordance with paragraph (d) of this section recommends a modification to the standard, the Secretary, on request, may grant an extension to the period granted for the exception.
+
+
+</P>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="J" TYPE="SUBPART">
+<HEAD>Subpart J—Code Sets</HEAD>
+
+
+<DIV8 N="162.1000" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1000   General requirements.</HEAD>
+<P>When conducting a transaction covered by this part, a covered entity must meet the following requirements:
+</P>
+<P>(a) <I>Medical data code sets.</I> Use the applicable medical data code sets described in § 162.1002 as specified in the implementation specification adopted under this part that are valid at the time the health care is furnished.
+</P>
+<P>(b) <I>Nonmedical data code sets.</I> Use the nonmedical data code sets as described in the implementation specifications adopted under this part that are valid at the time the transaction is initiated.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.1002" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1002   Medical data code sets.</HEAD>
+<P>The Secretary adopts the following maintaining organization's code sets as the standard medical data code sets:
+</P>
+<P>(a) For the period from October 16, 2002 through October 15, 2003:
+</P>
+<P>(1) <I>International Classification of Diseases, 9th Edition, Clinical Modification, (ICD-9-CM), Volumes 1 and 2</I> (including The Official ICD-9-CM Guidelines for Coding and Reporting), as maintained and distributed by HHS, for the following conditions:
+</P>
+<P>(i) Diseases.
+</P>
+<P>(ii) Injuries.
+</P>
+<P>(iii) Impairments.
+</P>
+<P>(iv) Other health problems and their manifestations.
+</P>
+<P>(v) Causes of injury, disease, impairment, or other health problems.
+</P>
+<P>(2) <I>International Classification of Diseases, 9th Edition, Clinical Modification, Volume 3 Procedures</I> (including The Official ICD-9-CM Guidelines for Coding and Reporting), as maintained and distributed by HHS, for the following procedures or other actions taken for diseases, injuries, and impairments on hospital inpatients reported by hospitals:
+</P>
+<P>(i) Prevention.
+</P>
+<P>(ii) Diagnosis.
+</P>
+<P>(iii) Treatment.
+</P>
+<P>(iv) Management.
+</P>
+<P>(3) <I>National Drug Codes</I> (NDC), as maintained and distributed by HHS, in collaboration with drug manufacturers, for the following:
+</P>
+<P>(i) Drugs
+</P>
+<P>(ii) Biologics.
+</P>
+<P>(4) <I>Code on Dental Procedures and Nomenclature,</I> as maintained and distributed by the American Dental Association, for dental services.
+</P>
+<P>(5) The combination of <I>Health Care Financing Administration Common Procedure Coding System (HCPCS),</I> as maintained and distributed by HHS, and <I>Current Procedural Terminology, Fourth Edition (CPT-4),</I> as maintained and distributed by the American Medical Association, for physician services and other health care services. These services include, but are not limited to, the following:
+</P>
+<P>(i) Physician services.
+</P>
+<P>(ii) Physical and occupational therapy services.
+</P>
+<P>(iii) Radiologic procedures.
+</P>
+<P>(iv) Clinical laboratory tests.
+</P>
+<P>(v) Other medical diagnostic procedures.
+</P>
+<P>(vi) Hearing and vision services.
+</P>
+<P>(vii) Transportation services including ambulance.
+</P>
+<P>(6) The <I>Health Care Financing Administration Common Procedure Coding System (HCPCS),</I> as maintained and distributed by HHS, for all other substances, equipment, supplies, or other items used in health care services. These items include, but are not limited to, the following:
+</P>
+<P>(i) Medical supplies.
+</P>
+<P>(ii) Orthotic and prosthetic devices.
+</P>
+<P>(iii) Durable medical equipment.
+</P>
+<P>(b) For the period on and after October 16, 2003 through September 30, 2015:
+</P>
+<P>(1) The code sets specified in paragraphs (a)(1), (a)(2),(a)(4), and (a)(5) of this section.
+</P>
+<P>(2) <I>National Drug Codes (NDC),</I> as maintained and distributed by HHS, for reporting the following by retail pharmacies:
+</P>
+<P>(i) Drugs.
+</P>
+<P>(ii) Biologics.
+</P>
+<P>(3) <I>The Healthcare Common Procedure Coding System (HCPCS),</I> as maintained and distributed by HHS, for all other substances, equipment, supplies, or other items used in health care services, with the exception of drugs and biologics. These items include, but are not limited to, the following:
+</P>
+<P>(i) Medical supplies.
+</P>
+<P>(ii) Orthotic and prosthetic devices.
+</P>
+<P>(iii) Durable medical equipment.
+</P>
+<P>(c) For the period on and after October 1, 2015:
+</P>
+<P>(1) The code sets specified in paragraphs (a)(4), (a)(5), (b)(2), and (b)(3) of this section.
+</P>
+<P>(2) International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM) (including The Official ICD-10-CM Guidelines for Coding and Reporting), as maintained and distributed by HHS, for the following conditions:
+</P>
+<P>(i) Diseases.
+</P>
+<P>(ii) Injuries.
+</P>
+<P>(iii) Impairments.
+</P>
+<P>(iv) Other health problems and their manifestations.
+</P>
+<P>(v) Causes of injury, disease, impairment, or other health problems.
+</P>
+<P>(3) International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS) (including The Official ICD-10-PCS Guidelines for Coding and Reporting), as maintained and distributed by HHS, for the following procedures or other actions taken for diseases, injuries, and impairments on hospital inpatients reported by hospitals:
+</P>
+<P>(i) Prevention.
+</P>
+<P>(ii) Diagnosis.
+</P>
+<P>(iii) Treatment.
+</P>
+<P>(iv) Management.
+</P>
+<CITA TYPE="N">[65 FR 50367, Aug. 17, 2000, as amended at 68 FR 8397, Feb. 20, 2003; 74 FR 3362, Jan. 16, 2009; 77 FR 54720, Sept. 5, 2012; 79 FR 45134, Aug. 4, 2014]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1011" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1011   Valid code sets.</HEAD>
+<P>Each code set is valid within the dates specified by the organization responsible for maintaining that code set.
+
+
+</P>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="K" TYPE="SUBPART">
+<HEAD>Subpart K—Health Care Claims or Equivalent Encounter Information</HEAD>
+
+
+<DIV8 N="162.1101" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1101   Health care claims or equivalent encounter information transaction.</HEAD>
+<P>The health care claims or equivalent encounter information transaction is the transmission of either of the following:
+</P>
+<P>(a) A request to obtain payment, and the necessary accompanying information from a health care provider to a health plan, for health care.
+</P>
+<P>(b) If there is no direct claim, because the reimbursement contract is based on a mechanism other than charges or reimbursement rates for specific services, the transaction is the transmission of encounter information for the purpose of reporting health care.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.1102" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1102   Standards for health care claims or equivalent encounter information transaction.</HEAD>
+<P>The Secretary adopts the following standards for the health care claims or equivalent encounter information transaction:
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009:
+</P>
+<P>(1) <I>Retail pharmacy drugs claims.</I> The National Council for Prescription Drug Programs (NCPDP) Telecommunication Standards Implementation Guide, Version 5, Release 1, September 1999, and equivalent NCPDP Batch Standards Batch Implementation Guide, Version 1, Release 1, (Version 1.1), January 2000, supporting Telecomunication Version 5.1 for the NCPDP Data Record in the Detail Data Record. (Incorporated by reference in § 162.920).
+</P>
+<P>(2) <I>Dental, health care claims.</I> The ASC X12N 837—Health Care Claim: Dental, Version 4010, May 2000, Washington Publishing Company, 004010X097. and Addenda to Health Care Claim: Dental, Version 4010, October 2002, Washington Publishing Company, 004010X097A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(3) <I>Professional health care claims.</I> The ASC X12N 837—Health Care Claims: Professional, Volumes 1 and 2, Version 4010, may 2000, Washington Publishing Company, 004010X098 and Addenda to Health Care Claims: Professional, Volumes 1 and 2, Version 4010, October 2002, Washington Publishing Company, 004010x098A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(4) <I>Institutional health care claims.</I> The ASC X12N 837—Health Care Claim: Institutional, Volumes 1 and 2, Version 4010, May 2000, Washington Publishing Company, 004010X096 and Addenda to Health Care Claim: Institutional, Volumes 1 and 2, Version 4010, October 2002, Washington Publishing Company, 004010X096A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011, both:
+</P>
+<P>(1)(i) The standards identified in paragraph (a) of this section; and
+</P>
+<P>(ii) For retail pharmacy supplies and professional services claims, the following: The ASC X12N 837—Health Care Claim: Professional, Volumes 1 and 2, Version 4010, May 2000, Washington Publishing Company, 004010X096, October 2002 (Incorporated by reference in § 162.920); and
+</P>
+<P>(2)(i) <I>Retail pharmacy drug claims.</I> The Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007 and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs. (Incorporated by reference in § 162.920.)
+</P>
+<P>(ii) <I>Dental health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3— Health Care Claim: Dental (837), May 2006, ASC X12N/005010X224, and Type 1 Errata to Health Care Claim: Dental (837) ASC X12 Standards for Electronic Date Interchange Technical Report Type 3, October 2007, ASC X12N/005010X224A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(iii) <I>Professional health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Professional (837), May 2006, ASC X12N/005010X222. (Incorporated by reference in § 162.920.)
+</P>
+<P>(iv) <I>Institutional health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Institutional (837), May 2006, ASC X12N/005010X223, and Type 1 Errata to Health Care Claim: Institutional (837) ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X223A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(v) <I>Retail pharmacy supplies and professional services claims.</I> (A) The Telecommunication Standard, Implementation Guide Version 5, Release 1, September 1999. (Incorporated by reference in § 162.920.)
+</P>
+<P>(B) The Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007, and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs (Incorporated by reference in § 162.920); and
+</P>
+<P>(C) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Professional (837), May 2006, ASC X12N/005010X222. (Incorporated by reference in § 162.920.)
+
+
+</P>
+<P>(c) For the period from January 1, 2012 through August 14, 2027, the standards identified in paragraph (b)(2) of this section, except the standard identified in paragraph (b)(2)(v)(A) of this section.
+
+
+</P>
+<P>(d) For the period on and after September 21, 2020 through August 14, 2027, the Quantity Prescribed (460-ET) field, as set forth in the Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007 and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs, must be treated as required where the transmission meets both of the following:
+
+
+</P>
+<P>(1) Is for a Schedule II drug, as defined in 21 CFR 1308.12.
+</P>
+<P>(2) Uses the standard identified in paragraph (b)(2)(i) of this section.
+
+
+</P>
+<P>(e) For the period from August 14, 2027 through April 14, 2028, both of the following:
+</P>
+<P>(1) The standards identified in paragraphs (c) and (d) of this section.
+</P>
+<P>(2) The following standards:
+</P>
+<P>(i) <I>Retail pharmacy drug claims.</I> The NCPDP Telecommunication Standard Implementation Guide Version F6, January 2020 and equivalent NCPDP Batch Standard Implementation Guide, Version 15, October 2017 (both incorporated by reference in § 162.920).
+</P>
+<P>(ii) <I>Dental health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Dental (837), May 2006, ASC X12N/005010X224, and Type 1 Errata to Health Care Claim: Dental (837) ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X224A1 (both incorporated by reference in § 162.920).
+</P>
+<P>(iii) <I>Professional health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Professional (837), May 2006, ASC X12N/005010X222 (incorporated by reference in § 162.920).
+</P>
+<P>(iv) <I>Institutional health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Institutional (837), May 2006, ASC X12N/005010X223, and Type 1 Errata to Health Care Claim: Institutional (837) ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X223A1 (both incorporated by reference in § 162.920).
+</P>
+<P>(3) <I>Retail pharmacy supplies and professional services claims.</I> (i) The NCPDP Telecommunication Standard Implementation Guide Version F6, January 2020 and equivalent NCPDP Batch Standard Implementation Guide, Version 15, October 2017 (both incorporated by reference in § 162.920).
+</P>
+<P>(ii) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3-Health Care Claim: Professional (837), May 2006, ASC X12N/005010X222 (incorporated by reference in § 162.920).
+</P>
+<P>(f) For the period on and after April 14, 2028, the standards identified in paragraph (e)(2) of this section.
+
+
+
+
+</P>
+<CITA TYPE="N">[68 FR 8397, Feb. 20, 2003; 68 FR 11445, Mar. 10, 2003, as amended at 74 FR 3325, Jan. 16, 2009; 85 FR 4242, Jan. 24, 2020; 89 FR 100788, Dec. 13, 2024; 90 FR 40749, Aug. 21, 2025]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="L" TYPE="SUBPART">
+<HEAD>Subpart L—Eligibility for a Health Plan</HEAD>
+
+
+<DIV8 N="162.1201" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1201   Eligibility for a health plan transaction.</HEAD>
+<P>The eligibility for a health plan transaction is the transmission of either of the following:
+</P>
+<P>(a) An inquiry from a health care provider to a health plan, or from one health plan to another health plan, to obtain any of the following information about a benefit plan for an enrollee:
+</P>
+<P>(1) Eligibility to receive health care under the health plan.
+</P>
+<P>(2) Coverage of health care under the health plan.
+</P>
+<P>(3) Benefits associated with the benefit plan.
+</P>
+<P>(b) A response from a health plan to a health care provider's (or another health plan's) inquiry described in paragraph (a) of this section.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.1202" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1202   Standards for eligibility for a health plan transaction.</HEAD>
+<P>The Secretary adopts the following standards for the eligibility for a health plan transaction:
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009:
+</P>
+<P>(1) <I>Retail pharmacy drugs.</I> The National Council for Prescription Drug Programs Telecommunication Standard Implementation Guide, Version 5, Release 1 (Version 5.1), September 1999, and equivalent NCPDP Batch Standard Batch Implementation Guide, Version 1, Release 1 (Version 1.1), January 2000 supporting Telecommunications Standard Implementation Guide, Version 5, Release 1 (Version 5.1) for the NCPDP Data Record in the Detail Data Record. (Incorporated by reference in § 162.920).
+</P>
+<P>(2) <I>Dental, professional, and institutional health care eligibility benefit inquiry and response.</I> The ASC X12N 270/271—Health Care Eligibility Benefit Inquiry and Response, Version 4010, May 2000, Washington Publishing Company, 004010X092 and Addenda to Health Care Eligibility Benefit Inquiry and Response, Version 4010, October 2002, Washington Publishing Company, 004010X092A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011 both:
+</P>
+<P>(1) The standards identified in paragraph (a) of this section; and
+</P>
+<P>(2)(i) <I>Retail pharmacy drugs.</I> The Telecommunication Standard Implementation Guide Version D, Release 0 (Version D.0), August 2007, and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs. (Incorporated by reference in § 162.920.)
+</P>
+<P>(ii) <I>Dental, professional, and institutional health care eligibility benefit inquiry and response.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Eligibility Benefit Inquiry and Response (270/271), April 2008, ASC X12N/005010X279. (Incorporated by reference in § 162.920.)
+
+
+
+
+</P>
+<P>(c) For the period from January 1, 2012 through August 14, 2027, the standards identified in paragraph (b)(2) of this section.
+
+
+</P>
+<P>(d) For the period from August 14, 2027 through April 14, 2028, both of the following:
+</P>
+<P>(1) The standards identified in paragraph (c) of this section.
+</P>
+<P>(2) The following standards:
+</P>
+<P>(i) <I>Retail pharmacy drugs.</I> The NCPDP Telecommunication Standard Implementation Guide Version F6, January 2020 and equivalent NCPDP Batch Standard Implementation Guide, Version 15, October 2017 (both incorporated by reference in § 162.920).
+</P>
+<P>(ii) <I>Dental, professional, and institutional health care eligibility benefit inquiry and response.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Eligibility Benefit Inquiry and Response (270/271), April 2008, ASC X12N/005010X279 (incorporated by reference in § 162.920).
+</P>
+<P>(e) For the period on and after April 14, 2028, the standards identified in paragraph (d)(2) of this section.
+
+
+
+
+</P>
+<CITA TYPE="N">[68 FR 8398, Feb. 20, 2003; 68 FR 11445, Mar. 10, 2003, as amended at 74 FR 3326, Jan. 16, 2009; 89 FR 100788, Dec. 13, 2024; 90 FR 40749, Aug. 21, 2025]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1203" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1203   Operating rules for eligibility for a health plan transaction.</HEAD>
+<P>On and after January 1, 2013, the Secretary adopts the following:
+</P>
+<P>(a) Except as specified in paragraph (b) of this section, the following CAQH CORE Phase I and Phase II operating rules (updated for Version 5010) for the eligibility for a health plan transaction:
+</P>
+<P>(1) Phase I CORE 152: Eligibility and Benefit Real Time Companion Guide Rule, version 1.1.0, March 2011, and CORE v5010 Master Companion Guide Template. (Incorporated by reference in § 162.920).
+</P>
+<P>(2) Phase I CORE 153: Eligibility and Benefits Connectivity Rule, version 1.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(3) Phase I CORE 154: Eligibility and Benefits 270/271 Data Content Rule, version 1.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(4) Phase I CORE 155: Eligibility and Benefits Batch Response Time Rule, version 1.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(5) Phase I CORE 156: Eligibility and Benefits Real Time Response Rule, version 1.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(6) Phase I CORE 157: Eligibility and Benefits System Availability Rule, version 1.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(7) Phase II CORE 258: Eligibility and Benefits 270/271 Normalizing Patient Last Name Rule, version 2.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(8) Phase II CORE 259: Eligibility and Benefits 270/271 AAA Error Code Reporting Rule, version 2.1.0. (Incorporated by reference in § 162.920).
+</P>
+<P>(9) Phase II CORE 260: Eligibility &amp; Benefits Data Content (270/271) Rule, version 2.1.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(10) Phase II CORE 270: Connectivity Rule, version 2.2.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(b) Excluding where the CAQH CORE rules reference and pertain to acknowledgements and CORE certification.
+</P>
+<CITA TYPE="N">[76 FR 40496, July 8, 2011]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="M" TYPE="SUBPART">
+<HEAD>Subpart M—Referral Certification and Authorization</HEAD>
+
+
+<DIV8 N="162.1301" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1301   Referral certification and authorization transaction.</HEAD>
+<P>The referral certification and authorization transaction is any of the following transmissions:
+</P>
+<P>(a) A request from a health care provider to a health plan for the review of health care to obtain an authorization for the health care.
+</P>
+<P>(b) A request from a health care provider to a health plan to obtain authorization for referring an individual to another health care provider.
+</P>
+<P>(c) A response from a health plan to a health care provider to a request described in paragraph (a) or paragraph (b) of this section.
+</P>
+<CITA TYPE="N">[74 FR 3326, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1302" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1302   Standards for referral certification and authorization transaction.</HEAD>
+<P>The Secretary adopts the following standards for the referral certification and authorization transaction:
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009:
+</P>
+<P>(1) <I>Retail pharmacy drug referral certification and authorization.</I> The NCPDP Telecommunication Standard Implementation Guide, Version 5, Release 1 (Version 5.1), September 1999, and equivalent NCPDP Batch Standard Batch Implementation Guide, Version 1, Release 1 (Version 1.1), January 2000, supporting Telecommunications Standard Implementation Guide, Version 5, Release 1 (Version 5.1) for the NCPDP Data Record in the Detail Data Record. (Incorporated by reference in § 162.920).
+</P>
+<P>(2) <I>Dental, professional, and institutional referral certification and authorization.</I> The ASC X12N 278—Health Care Services Review—Request for Review and Response, Version 4010, May 2000, Washington Publishing Company, 004010X094 and Addenda to Health Care Services Review—Request for Review and Response, Version 4010, October 2002, Washington Publishing Company, 004010X094A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011 both—
+</P>
+<P>(1) The standards identified in paragraph (a) of this section; and
+</P>
+<P>(2)(i) <I>Retail pharmacy drugs.</I> The Telecommunication Standard Implementation Guide Version D, Release 0 (Version D.0), August 2007, and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs. (Incorporated by reference in § 162.920.)
+</P>
+<P>(ii) <I>Dental, professional, and institutional request for review and response.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Services Review—Request for Review and Response (278), May 2006, ASC X12N/005010X217, and Errata to Health Care Services Review-—Request for Review and Response (278), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, April 2008, ASC X12N/005010X217E1. (Incorporated by reference in § 162.920.)
+
+
+</P>
+<P>(c) For the period from January 1, 2012 through August 14, 2027, the standards identified in paragraph (b)(2) of this section.
+
+
+
+
+</P>
+<P>(d) For the period on and after September 21, 2020 through August 14, 2027, the Quantity Prescribed (460-ET) field, as set forth in the Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007 and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs, must be treated as required where the transmission meets both of the following:
+
+
+</P>
+<P>(1) Is for a Schedule II drug, as defined in 21 CFR 1308.12.
+</P>
+<P>(2) Uses the standard identified in paragraph (b)(2)(i) of this section.
+
+
+</P>
+<P>(e) For the period from August 14, 2027 through April 14, 2028, both of the following:
+</P>
+<P>(1) The standards identified in paragraph (c) and (d) of this section.
+</P>
+<P>(2) The following standards:
+</P>
+<P>(i) <I>Retail pharmacy drugs.</I> The NCPDP Telecommunication Standard Implementation Guide Version F6, January 2020 and equivalent NCPDP Batch Standard Implementation Guide, Version 15, October 2017 (both incorporated by reference in § 162.920).
+</P>
+<P>(ii) <I>Dental, professional, and institutional request for review and response.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Services Review—Request for Review and Response (278), May 2006, ASC X12N/005010X217, and Errata to Health Care Services Review—Request for Review and Response (278), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, April 2008, ASC X12N/005010X217E1 (both incorporated by reference in § 162.920).
+</P>
+<P>(f) For the period on and after April 14, 2028, the standards identified in paragraph (e)(2) of this section.
+
+
+</P>
+<CITA TYPE="N">[68 FR 8398, Feb. 20, 2003, as amended at 74 FR 3326, Jan. 16, 2009; 85 FR 4242, Jan. 24, 2020; 89 FR 100788, Dec. 13, 2024; 90 FR 40749, Aug. 21, 2025]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="N" TYPE="SUBPART">
+<HEAD>Subpart N—Health Care Claim Status</HEAD>
+
+
+<DIV8 N="162.1401" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1401   Health care claim status transaction.</HEAD>
+<P>The health care claim status transaction is the transmission of either of the following:
+</P>
+<P>(a) An inquiry from a health care provider to a health plan to determine the status of a health care claim.
+</P>
+<P>(b) A response from a health plan to a health care provider about the status of a health care claim.
+</P>
+<CITA TYPE="N">[74 FR 3326, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1402" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1402   Standards for health care claim status transaction.</HEAD>
+<P>The Secretary adopts the following standards for the health care claim status transaction:
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009: The ASC X12N-276/277 Health Care Claim Status Request and Response, Version 4010, May 2000, Washington Publishing Company, 004010X093 and Addenda to Health Care Claim Status Request and Response, Version 4010, October 2002, Washington Publishing Company, 004010X093A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011, both:
+</P>
+<P>(1) The standard identified in paragraph (a) of this section; and
+</P>
+<P>(2) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim Status Request and Response (276/277), August 2006, ASC X12N/005010X212, and Errata to Health Care Claim Status Request and Response (276/277), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, April 2008, ASC X12N/005010X212E1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(c) For the period on and after January 1, 2012, the standard identified in paragraph (b)(2) of this section.
+</P>
+<CITA TYPE="N">[74 FR 3326, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1403" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1403   Operating rules for health care claim status transaction.</HEAD>
+<P>On and after January 1, 2013, the Secretary adopts the following:
+</P>
+<P>(a) Except as specified in paragraph (b) of this section, the following CAQH CORE Phase II operating rules (updated for Version 5010) for the health care claim status transaction:
+</P>
+<P>(1) Phase II CORE 250: Claim Status Rule, version 2.1.0, March 2011, and CORE v5010 Master Companion Guide, 00510, 1.2, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(2) Phase II CORE 270: Connectivity Rule, version 2.2.0, March 2011. (Incorporated by reference in § 162.920).
+</P>
+<P>(b) Excluding where the CAQH CORE rules reference and pertain to acknowledgements and CORE certification.
+</P>
+<CITA TYPE="N">[76 FR 40496, July 8, 2011]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="O" TYPE="SUBPART">
+<HEAD>Subpart O—Enrollment and Disenrollment in a Health Plan</HEAD>
+
+
+<DIV8 N="162.1501" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1501   Enrollment and disenrollment in a health plan transaction.</HEAD>
+<P>The enrollment and disenrollment in a health plan transaction is the transmission of subscriber enrollment information from the sponsor of the insurance coverage, benefits, or policy, to a health plan to establish or terminate insurance coverage.
+</P>
+<CITA TYPE="N">[74 FR 3327, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1502" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1502   Standards for enrollment and disenrollment in a health plan transaction.</HEAD>
+<P>The Secretary adopts the following standards for enrollment and disenrollment in a health plan transaction.
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009: ASC X12N 834—Benefit Enrollment and Maintenance, Version 4010, May 2000, Washington Publishing Company, 004010X095 and Addenda to Benefit Enrollment and Maintenance, Version 4010, October 2002, Washington Publishing Company, 004010X095A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011, both:
+</P>
+<P>(1) The standard identified in paragraph (a) of this section; and
+</P>
+<P>(2) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Benefit Enrollment and Maintenance (834), August 2006, ASC X12N/005010X220 (Incorporated by reference in § 162.920)
+</P>
+<P>(c) For the period on and after January 1, 2012, the standard identified in paragraph (b)(2) of this section.
+</P>
+<CITA TYPE="N">[74 FR 3327, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="P" TYPE="SUBPART">
+<HEAD>Subpart P—Health Care Electronic Funds Transfers (EFT) and Remittance Advice</HEAD>
+
+
+<DIV8 N="162.1601" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1601   Health care electronic funds transfers (EFT) and remittance advice transaction.</HEAD>
+<P>The health care electronic funds transfers (EFT) and remittance advice transaction is the transmission of either of the following for health care:
+</P>
+<P>(a) The transmission of any of the following from a health plan to a health care provider:
+</P>
+<P>(1) Payment.
+</P>
+<P>(2) Information about the transfer of funds.
+</P>
+<P>(3) Payment processing information.
+</P>
+<P>(b) The transmission of either of the following from a health plan to a health care provider:
+</P>
+<P>(1) Explanation of benefits.
+</P>
+<P>(2) Remittance advice.
+</P>
+<CITA TYPE="N">[65 FR 50367, Aug. 17, 2000, as amended at 77 FR 1590, Jan. 10, 2012; 77 FR 48043, Aug. 10, 2012]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1602" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1602   Standards for health care electronic funds transfers (EFT) and remittance advice transaction.</HEAD>
+<P>The Secretary adopts the following standards:
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009: Health care claims and remittance advice. The ASC X12N 835—Health Care Claim Payment/Advice, Version 4010, May 2000, Washington Publishing Company, 004010X091, and Addenda to Health Care Claim Payment/Advice, Version 4010, October 2002, Washington Publishing Company, 004010X091A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011, both of the following standards:
+</P>
+<P>(1) The standard identified in paragraph (a) of this section.
+</P>
+<P>(2) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim Payment/Advice (835), April 2006, ASC X12N/005010X221. (Incorporated by reference in § 162.920.)
+</P>
+<P>(c) For the period from January 1, 2012 through December 31, 2013, the standard identified in paragraph (b)(2) of this section.
+</P>
+<P>(d) For the period on and after January 1, 2014, the following standards:
+</P>
+<P>(1) Except when transmissions as described in § 162.1601(a) and (b) are contained within the same transmission, for Stage 1 Payment Initiation transmissions described in § 162.1601(a), all of the following standards:
+</P>
+<P>(i) The National Automated Clearing House Association (NACHA) Corporate Credit or Deposit Entry with Addenda Record (CCD+) implementation specifications as contained in the 2011 NACHA Operating Rules &amp; Guidelines, A Complete Guide to the Rules Governing the ACH Network as follows (incorporated by reference in § 162.920)—
+</P>
+<P>(A) NACHA Operating Rules, Appendix One: ACH File Exchange Specifications; and
+</P>
+<P>(B) NACHA Operating Rules, Appendix Three: ACH Record Format Specifications, Subpart 3.1.8 Sequence of Records for CCD Entries.
+</P>
+<P>(ii) For the CCD Addenda Record (“7”), field 3, of the standard identified in 1602(d)(1)(i), the Accredited Standards Committee (ASC) X12 Standards for Electronic Data Interchange Technical Report Type 3, “Health Care Claim Payment/Advice (835), April 2006: Section 2.4: 835 Segment Detail: “TRN Reassociation Trace Number,” Washington Publishing Company, 005010X221 (Incorporated by reference in § 162.920).
+</P>
+<P>(2) For transmissions described in § 162.1601(b), including when transmissions as described in § 162.1601(a) and (b) are contained within the same transmission, the ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, “Health Care Claim Payment/Advice (835), April 2006, ASC X12N/005010X221. (Incorporated by reference in § 162.920).
+</P>
+<CITA TYPE="N">[77 FR 1590, Jan. 10, 2012]
+
+
+</CITA>
+</DIV8>
+
+
+<DIV8 N="162.1603" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1603   Operating rules for health care electronic funds transfers (EFT) and remittance advice transaction.</HEAD>
+<P>On and after January 1, 2014, the Secretary adopts the following for the health care electronic funds transfers (EFT) and remittance advice transaction:
+</P>
+<P>(a) The Phase III CORE EFT &amp; ERA Operating Rule Set, Approved June 2012 (Incorporated by reference in § 162.920) which includes the following rules:
+</P>
+<P>(1) Phase III CORE 380 EFT Enrollment Data Rule, version 3.0.0, June 2012.
+</P>
+<P>(2) Phase III CORE 382 ERA Enrollment Data Rule, version 3.0.0, June 2012.
+</P>
+<P>(3) Phase III 360 CORE Uniform Use of CARCs and RARCs (835) Rule, version 3.0.0, June 2012.
+</P>
+<P>(4) CORE-required Code Combinations for CORE-defined Business Scenarios for the Phase III CORE 360 Uniform Use of Claim Adjustment Reason Codes and Remittance Advice Remark Codes (835) Rule, version 3.0.0, June 2012.
+</P>
+<P>(5) Phase III CORE 370 EFT &amp; ERA Reassociation (CCD+/835) Rule, version 3.0.0, June 2012.
+</P>
+<P>(6) Phase III CORE 350 Health Care Claim Payment/Advice (835) Infrastructure Rule, version 3.0.0, June 2012, except Requirement 4.2 titled “Health Care Claim Payment/Advice Batch Acknowledgement Requirements”.
+</P>
+<P>(b) ACME Health Plan, CORE v5010 Master Companion Guide Template, 005010, 1.2, March 2011 (incorporated by reference in § 162.920), as required by the Phase III CORE 350 Health Care Claim Payment/Advice (835) Infrastructure Rule, version 3.0.0, June 2012.
+</P>
+<CITA TYPE="N">[77 FR 48043, Aug. 10, 2012]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="Q" TYPE="SUBPART">
+<HEAD>Subpart Q—Health Plan Premium Payments</HEAD>
+
+
+<DIV8 N="162.1701" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1701   Health plan premium payments transaction.</HEAD>
+<P>The health plan premium payment transaction is the transmission of any of the following from the entity that is arranging for the provision of health care or is providing health care coverage payments for an individual to a health plan:
+</P>
+<P>(a) Payment.
+</P>
+<P>(b) Information about the transfer of funds.
+</P>
+<P>(c) Detailed remittance information about individuals for whom premiums are being paid.
+</P>
+<P>(d) Payment processing information to transmit health care premium payments including any of the following:
+</P>
+<P>(1) Payroll deductions.
+</P>
+<P>(2) Other group premium payments.
+</P>
+<P>(3) Associated group premium payment information.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.1702" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1702   Standards for health plan premium payments transaction.</HEAD>
+<P>The Secretary adopts the following standards for the health plan premium payments transaction:
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009: The ASC X12N 820—Payroll Deducted and Other Group Premium Payment for Insurance Products, Version 4010, May 2000, Washington Publishing Company, 004010X061, and Addenda to Payroll Deducted and Other Group Premium Payment for Insurance Products, Version 4010, October 2002, Washington Publishing Company, 004010X061A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011, both:
+</P>
+<P>(1) The standard identified in paragraph (a) of this section, and
+</P>
+<P>(2) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Payroll Deducted and Other Group Premium Payment for Insurance Products (820), February 2007, ASC X12N/005010X218. (Incorporated by reference in § 162.920.)
+</P>
+<P>(c) For the period on and after January 1, 2012, the standard identified in paragraph (b)(2) of this section.
+</P>
+<CITA TYPE="N">[74 FR 3327, Jan. 16, 2009]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="R" TYPE="SUBPART">
+<HEAD>Subpart R—Coordination of Benefits</HEAD>
+
+
+<DIV8 N="162.1801" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1801   Coordination of benefits transaction.</HEAD>
+<P>The coordination of benefits transaction is the transmission from any entity to a health plan for the purpose of determining the relative payment responsibilities of the health plan, of either of the following for health care:
+</P>
+<P>(a) Claims.
+</P>
+<P>(b) Payment information.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.1802" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1802   Standards for coordination of benefits information transaction.</HEAD>
+<P>The Secretary adopts the following standards for the coordination of benefits information transaction.
+</P>
+<P>(a) For the period from October 16, 2003 through March 16, 2009:
+</P>
+<P>(1) <I>Retail pharmacy drug claims.</I> The National Council for Prescription Drug Programs Telecommunication Standard Implementation Guide, Version 5, Release 1 (Version 5.1), September 1999, and equivalent NCPDP Batch Standard Batch Implementation Guide, Version 1, Release 1 (Version 1.1), January 2000, supporting Telecommunications Standard Implementation Guide, Version 5, Release 1 (Version 5.1) for the NCPDP Data Record in the Detail Data Record. (Incorporated by reference in § 162.920).
+</P>
+<P>(2) <I>Dental health care claims.</I> The ASC X12N 837—Health Care Claim: Dental, Version 4010, May 2000, Washington Publishing Company, 004010X097 and Addenda to Health Care Claim: Dental, Version 4010, October 2002, Washington Publishing Company, 004010X097A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(3) <I>Professional health care claims.</I> The ASC X12N 837—Health Care Claim: Professional, Volumes 1 and 2, Version 4010, May 2000, Washington Publishing Company, 004010X098 and Addenda to Health Care Claim: Professional, Volumes 1 and 2, Version 4010, October 2002, Washington Publishing Company, 004010X098A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(4) <I>Institutional health care claims.</I> The ASC X12N 837—Health Care Claim: Institutional, Volumes 1 and 2, Version 4010, May 2000, Washington Publishing Company, 004010X096 and Addenda to Health Care Claim: Institutional, Volumes 1 and 2, Version 4010, October 2002, Washington Publishing Company, 004010X096A1. (Incorporated by reference in § 162.920).
+</P>
+<P>(b) For the period from March 17, 2009 through December 31, 2011, both:
+</P>
+<P>(1) The standards identified in paragraph (a) of this section; and
+</P>
+<P>(2)(i) <I>Retail pharmacy drug claims.</I> The Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007, and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs. (Incorporated by reference in § 162.920.)
+</P>
+<P>(ii) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Dental (837), May 2006, ASC X12N/005010X224, and Type 1 Errata to Health Care Claim: Dental (837), ASC X12 Standards for Electronic Date Interchange Technical Report Type 3, October 2007, ASC X12N/005010X224A1. (Incorporated by reference in § 162.920.)
+</P>
+<P>(iii) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Professional (837), May 2006, ASC X12N/005010X222. (Incorporated by reference in § 162.920.)
+</P>
+<P>(iv) The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Institutional (837), May 2006, ASC X12N/005010X223, and Type 1 Errata to Health Care Claim: Institutional (837), ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X223A1. (Incorporated by reference in § 162.920.)
+
+
+</P>
+<P>(c) For the period from January 1, 2012 through August 14, 2027, the standards identified in paragraph (b)(2) of this section.
+
+
+
+
+</P>
+<P>(d) For the period on and after September 21, 2020 through August 14, 2027, the Quantity Prescribed (460-ET) field, as set forth in the Telecommunication Standard Implementation Guide, Version D, Release 0 (Version D.0), August 2007 and equivalent Batch Standard Implementation Guide, Version 1, Release 2 (Version 1.2), National Council for Prescription Drug Programs, must be treated as required where the transmission meets both of the following:
+
+
+</P>
+<P>(1) Is for a Schedule II drug, as defined in 21 CFR 1308.12.
+</P>
+<P>(2) Uses the standard identified in paragraph (b)(2)(i) of this section.
+
+
+</P>
+<P>(e) For the period from August 14, 2027 through April 14, 2028, both of the following:
+</P>
+<P>(1) The standards identified in paragraphs (c) and (d) of this section.
+</P>
+<P>(2) The following standards:
+</P>
+<P>(i) <I>Retail pharmacy drug claims.</I> The NCPDP Telecommunication Standard Implementation Guide Version F6, January 2020 and equivalent NCPDP Batch Standard Implementation Guide, Version 15, October 2017 (both incorporated by reference in § 162.920).
+</P>
+<P>(ii) <I>Dental health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Dental (837), May 2006, ASC X12N/005010X224, and Type 1 Errata to Health Care Claim: Dental (837) ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X224A1 (both incorporated by reference in § 162.920).
+</P>
+<P>(3) <I>Professional health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Professional (837), May 2006, ASC X12N/005010X222 (incorporated by reference in § 162.920).
+</P>
+<P>(4) <I>Institutional health care claims.</I> The ASC X12 Standards for Electronic Data Interchange Technical Report Type 3—Health Care Claim: Institutional (837), May 2006, ASC X12N/005010X223, and Type 1 Errata to Health Care Claim: Institutional (837) ASC X12 Standards for Electronic Data Interchange Technical Report Type 3, October 2007, ASC X12N/005010X223A1 (incorporated by reference in § 162.920).
+</P>
+<P>(f) For the period on and after April 14, 2028, the standards identified in paragraph (e)(2) of this section.
+
+
+</P>
+<CITA TYPE="N">[68 FR 8399, Feb. 20, 2003, as amended at 74 FR 3327, Jan. 16, 2009; 85 FR 4242, Jan. 24, 2020; 89 FR 100789, Dec. 13, 2024; 90 FR 40749, Aug. 21, 2025]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="S" TYPE="SUBPART">
+<HEAD>Subpart S—Medicaid Pharmacy Subrogation</HEAD>
+
+<SOURCE>
+<HED>Source:</HED><PSPACE>74 FR 3328, Jan. 16, 2009, unless otherwise noted.
+
+
+</PSPACE></SOURCE>
+
+<DIV8 N="162.1901" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1901   Medicaid pharmacy subrogation transaction.</HEAD>
+<P>The Medicaid pharmacy subrogation transaction is the transmission of a claim from a Medicaid agency to a payer for the purpose of seeking reimbursement from the responsible health plan for a pharmacy claim the State has paid on behalf of a Medicaid recipient.
+
+
+</P>
+</DIV8>
+
+
+<DIV8 N="162.1902" TYPE="SECTION" VOLUME="2">
+<HEAD>§ 162.1902   Standard for Medicaid pharmacy subrogation transaction.</HEAD>
+<P>The Secretary adopts the following standards for the Medicaid pharmacy subrogation transaction:
+</P>
+<P>(a) For the period from January 1, 2012 through August 14, 2027—The NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 3.0, July 2007 (incorporated by reference at § 162.920).
+</P>
+<P>(b) For the period from August 14, 2027 through April 14, 2028—
+</P>
+<P>(1) The standards identified in paragraph (a) of this section; and
+</P>
+<P>(2) The NCPDP Subrogation Implementation Guide for Batch Standard, Version 10, September 2019 (incorporated by reference at § 162.920).
+</P>
+<P>(c) For the period on and after April 14, 2028, the standard identified in paragraph (b) of this section.
+
+
+</P>
+<CITA TYPE="N">[89 FR 100789, Dec. 13, 2024, as amended at 90 FR 40749, Aug. 21, 2025]
+
+
+</CITA>
+</DIV8>
+
+</DIV6>
+
+
+<DIV6 N="T" TYPE="SUBPART">
+<HEAD>Subpart T—XXX</HEAD>
+
+<XREF ID="20260324" REFID="57" AMDINSN="6">Link to an amendment published at 91 FR 14405, Mar. 24, 2026.</XREF>
+<P>
+
+
+
+
+</P>
+</DIV6>
+
+</DIV5>
+
+
+
+```

datasets/22-hhs-official-guidance-pages-verbatim.md

@@ -0,0 +1,967 @@
+# HHS Official Guidance Pages — Verbatim Snapshot Dataset
+
+Retrieved: 2026-04-28
+
+Source URLs:
+- https://www.hhs.gov/hipaa/for-professionals/privacy/index.html
+- https://www.hhs.gov/hipaa/for-professionals/security/index.html
+- https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html
+
+Notes:
+- Content captured from browser accessibility snapshots to preserve visible text and linked URLs.
+- Snapshot format includes page title, URL, event metadata, and an accessible tree with URL targets.
+
+## Privacy Rule Page Snapshot
+
+```text
+Page Title: The HIPAA Privacy Rule | HHS.gov
+URL: https://www.hhs.gov/hipaa/for-professionals/privacy/index.html
+Snapshot: 
+- generic [active] [ref=e1]:
+  - link "Skip to main content" [ref=e2] [cursor=pointer]:
+    - /url: "#main"
+  - generic [ref=e4]:
+    - region "Official government website" [ref=e5]:
+      - generic [ref=e8]:
+        - img "U.S. flag" [ref=e10]
+        - paragraph [ref=e12]: An official website of the United States government
+        - button "Here’s how you know" [ref=e13] [cursor=pointer]
+    - generic [ref=e19]:
+      - img "Freedom 250 banner logo" [ref=e20]
+      - link "Join HHS in Celebrating Freedom 250" [ref=e21] [cursor=pointer]:
+        - /url: /freedom250/index.html
+      - img [ref=e22]
+    - banner [ref=e24]:
+      - generic [ref=e25]:
+        - link "Home" [ref=e28] [cursor=pointer]:
+          - /url: /
+          - img [ref=e29]
+        - button "Menu" [ref=e115]
+    - generic [ref=e118]:
+      - navigation "breadcrumb-label-11031616818" [ref=e120]:
+        - generic [ref=e122]:
+          - generic [ref=e123]: Breadcrumb
+          - list [ref=e124]:
+            - listitem [ref=e125]:
+              - link "HHS" [ref=e126] [cursor=pointer]:
+                - /url: /
+            - listitem [ref=e127]:
+              - link "HIPAA Home" [ref=e128] [cursor=pointer]:
+                - /url: /hipaa/index.html
+            - listitem [ref=e129]:
+              - link "For Professionals" [ref=e130] [cursor=pointer]:
+                - /url: /hipaa/for-professionals/index.html
+            - listitem [ref=e131]: Privacy
+      - list [ref=e135]:
+        - listitem [ref=e136]:
+          - checkbox "Adjust Text Size" [ref=e137] [cursor=pointer]:
+            - img [ref=e138]
+        - listitem [ref=e139]:
+          - link "Print" [ref=e140] [cursor=pointer]:
+            - /url: "#"
+            - img [ref=e141]
+        - listitem [ref=e143]:
+          - button "Page sharing options" [ref=e144] [cursor=pointer]:
+            - img [ref=e145]
+            - generic [ref=e147]: Page sharing options
+    - main [ref=e148]:
+      - generic [ref=e152]:
+        - complementary [ref=e153]:
+          - button "Navigate to:" [ref=e156] [cursor=pointer]
+        - generic [ref=e157]:
+          - generic [ref=e160]:
+            - heading "The HIPAA Privacy Rule" [level=1] [ref=e161]
+            - article [ref=e162]:
+              - generic [ref=e163]:
+                - generic [ref=e167]:
+                  - paragraph [ref=e168]: The HIPAA Privacy Rule establishes national standards to protect individuals' medical records and other individually identifiable health information (collectively defined as “protected health information”) and applies to health plans, health care clearinghouses, and those health care providers that conduct certain health care transactions electronically. The Rule requires appropriate safeguards to protect the privacy of protected health information and sets limits and conditions on the uses and disclosures that may be made of such information without an individual’s authorization. The Rule also gives individuals rights over their protected health information, including rights to examine and obtain a copy of their health records, to direct a covered entity to transmit to a third party an electronic copy of their protected health information in an electronic health record, and to request corrections.
+                  - paragraph [ref=e169]:
+                    - text: The Privacy Rule is located at 45 CFR
+                    - link "Part 160 , links to an external website" [ref=e170] [cursor=pointer]:
+                      - /url: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160?toc=1
+                      - text: Part 160
+                      - generic [ref=e172]: ", links to an external website"
+                    - text: and Subparts A and E of
+                    - link "Part 164 , links to an external website" [ref=e173] [cursor=pointer]:
+                      - /url: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164
+                      - text: Part 164
+                      - generic [ref=e175]: ", links to an external website"
+                    - text: .
+                  - paragraph [ref=e176]:
+                    - link "Click here to view the combined regulation text" [ref=e177] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/privacy/laws-regulations/combined-regulation-text/index.html
+                    - text: of all HIPAA Administrative Simplification Regulations found at 45 CFR 160, 162, and 164.
+                  - heading "Privacy Rule History" [level=2] [ref=e178]
+                  - list [ref=e179]:
+                    - listitem [ref=e180]:
+                      - text: April 26, 2024 -
+                      - link "HIPAA Privacy Rule to Support Reproductive Health Care Privacy - Final Rule , links to an external website" [ref=e181] [cursor=pointer]:
+                        - /url: https://www.federalregister.gov/documents/2024/04/26/2024-08503/hipaa-privacy-rule-to-support-reproductive-health-care-privacy
+                        - text: HIPAA Privacy Rule to Support Reproductive Health Care Privacy - Final Rule
+                        - generic [ref=e183]: ", links to an external website"
+                    - listitem [ref=e184]:
+                      - text: April 17, 2023 -
+                      - link "HIPAA Privacy Rule to Support Reproductive Health Care Privacy - Proposed Rule , links to an external website" [ref=e185] [cursor=pointer]:
+                        - /url: https://www.federalregister.gov/documents/2023/04/17/2023-07517/hipaa-privacy-rule-to-support-reproductive-health-care-privacy
+                        - text: HIPAA Privacy Rule to Support Reproductive Health Care Privacy - Proposed Rule
+                        - generic [ref=e187]: ", links to an external website"
+                    - listitem [ref=e188]:
+                      - text: March 10, 2021 -
+                      - link "Extension of Comment Period for Modifications to the HIPAA Privacy Rule to Support, and Remove Barriers to, Coordinated Care and Individual Engagement – Proposed Rule , links to an external website , opens in a new tab" [ref=e190] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2021-03-10/pdf/2021-05021.pdf
+                        - text: Extension of Comment Period for Modifications to the HIPAA Privacy Rule to Support, and Remove Barriers to, Coordinated Care and Individual Engagement – Proposed Rule
+                        - generic [ref=e192]: ", links to an external website"
+                        - generic [ref=e193]: ", opens in a new tab"
+                    - listitem [ref=e194]:
+                      - text: January 21, 2021 -
+                      - link "Modifications to the HIPAA Privacy Rule to Empower Patients, Improve Coordinated Care, and Reduce Regulatory Burdens - Proposed Rule , links to an external website , opens in a new tab" [ref=e196] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2021-01-21/pdf/2020-27157.pdf
+                        - text: Modifications to the HIPAA Privacy Rule to Empower Patients, Improve Coordinated Care, and Reduce Regulatory Burdens - Proposed Rule
+                        - generic [ref=e198]: ", links to an external website"
+                        - generic [ref=e199]: ", opens in a new tab"
+                    - listitem [ref=e200]:
+                      - text: December 14, 2018 -
+                      - link "Modifying the HIPAA Rules to Improve Coordinated Care - Request for Information , links to an external website , opens in a new tab" [ref=e202] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2018-12-14/pdf/2018-27162.pdf
+                        - text: Modifying the HIPAA Rules to Improve Coordinated Care - Request for Information
+                        - generic [ref=e204]: ", links to an external website"
+                        - generic [ref=e205]: ", opens in a new tab"
+                    - listitem [ref=e206]:
+                      - text: January 6, 2016 -
+                      - link "HIPAA Privacy Rule and the National Instant Criminal Background Check System (NICS) - Final Rule , links to an external website , opens in a new tab" [ref=e208] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2016-01-06/pdf/2015-33181.pdf
+                        - text: HIPAA Privacy Rule and the National Instant Criminal Background Check System (NICS) - Final Rule
+                        - generic [ref=e210]: ", links to an external website"
+                        - generic [ref=e211]: ", opens in a new tab"
+                    - listitem [ref=e212]:
+                      - text: February 6, 2014 -
+                      - link "Patients' Access to Test Reports Under the HIPAA Privacy Rule and the Clinical Laboratory Improvement Amendments of 1988 (CLIA) Program - Final Rule , links to an external website , opens in a new tab" [ref=e214] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2014-02-06/pdf/2014-02280.pdf
+                        - text: Patients' Access to Test Reports Under the HIPAA Privacy Rule and the Clinical Laboratory Improvement Amendments of 1988 (CLIA) Program - Final Rule
+                        - generic [ref=e216]: ", links to an external website"
+                        - generic [ref=e217]: ", opens in a new tab"
+                    - listitem [ref=e218]:
+                      - text: January 7, 2014 -
+                      - link "HIPAA Privacy Rule and NICS - Proposed Rule , links to an external website , opens in a new tab" [ref=e220] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2014-01-07/pdf/2014-00055.pdf
+                        - text: HIPAA Privacy Rule and NICS - Proposed Rule
+                        - generic [ref=e222]: ", links to an external website"
+                        - generic [ref=e223]: ", opens in a new tab"
+                    - listitem [ref=e224]:
+                      - text: April 23, 2013 -
+                      - link "HIPAA Privacy Rule and NICS - Advance Notice of Proposed Rulemaking , links to an external website , opens in a new tab" [ref=e226] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2013-04-23/pdf/2013-09602.pdf
+                        - text: HIPAA Privacy Rule and NICS - Advance Notice of Proposed Rulemaking
+                        - generic [ref=e228]: ", links to an external website"
+                        - generic [ref=e229]: ", opens in a new tab"
+                    - listitem [ref=e230]:
+                      - text: January 25, 2013 -
+                      - link "Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules under the Health Information Technology for Economic and Clinical Health (HITECH) Act and the Genetic Information Nondiscrimination Act, and Other Modifications - Final Rule , links to an external website , opens in a new tab" [ref=e232] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2013-01-25/pdf/2013-01073.pdf
+                        - text: Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules under the Health Information Technology for Economic and Clinical Health (HITECH) Act and the Genetic Information Nondiscrimination Act, and Other Modifications - Final Rule
+                        - generic [ref=e234]: ", links to an external website"
+                        - generic [ref=e235]: ", opens in a new tab"
+                      - text: (The "Omnibus HIPAA Final Rule")
+                    - listitem [ref=e236]:
+                      - text: September 14, 2011 -
+                      - link "Patients' Access to Test Reports Under the HIPAA Privacy Rule and CLIA Program - Proposed Rule , links to an external website , opens in a new tab" [ref=e238] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2011-09-14/pdf/2011-23525.pdf
+                        - text: Patients' Access to Test Reports Under the HIPAA Privacy Rule and CLIA Program - Proposed Rule
+                        - generic [ref=e240]: ", links to an external website"
+                        - generic [ref=e241]: ", opens in a new tab"
+                    - listitem [ref=e242]:
+                      - text: May 31, 2011 -
+                      - link "HIPAA Privacy Rule Accounting of Disclosures Under the HITECH Act - Proposed Rule , links to an external website , opens in a new tab" [ref=e244] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2011-05-31/pdf/2011-13297.pdf
+                        - text: HIPAA Privacy Rule Accounting of Disclosures Under the HITECH Act - Proposed Rule
+                        - generic [ref=e246]: ", links to an external website"
+                        - generic [ref=e247]: ", opens in a new tab"
+                    - listitem [ref=e248]:
+                      - text: July 14, 2010 -
+                      - link "Modifications to the HIPAA Privacy, Security, and Enforcement Rules under the HITECH Act - Proposed Rule , links to an external website , opens in a new tab" [ref=e250] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2010-07-14/pdf/2010-16718.pdf
+                        - text: Modifications to the HIPAA Privacy, Security, and Enforcement Rules under the HITECH Act - Proposed Rule
+                        - generic [ref=e252]: ", links to an external website"
+                        - generic [ref=e253]: ", opens in a new tab"
+                    - listitem [ref=e254]:
+                      - text: May 3, 2010 -
+                      - link "HIPAA Privacy Rule Accounting of Disclosures Under the HITECH Act - Request for Information , links to an external website , opens in a new tab" [ref=e256] [cursor=pointer]:
+                        - /url: https://www.govinfo.gov/content/pkg/FR-2010-05-03/pdf/2010-10054.pdf
+                        - text: HIPAA Privacy Rule Accounting of Disclosures Under the HITECH Act - Request for Information
+                        - generic [ref=e258]: ", links to an external website"
+                        - generic [ref=e259]: ", opens in a new tab"
+                    - listitem [ref=e260]:
+                      - text: October 7, 2009 -
+                      - link "HIPAA Privacy Rule; Modifications Under the Genetic Information Nondiscrimination Act - Proposed Rule , opens in a new tab" [ref=e262] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/understanding/special/genetic/ginanprm.pdf
+                        - text: HIPAA Privacy Rule; Modifications Under the Genetic Information Nondiscrimination Act - Proposed Rule
+                        - generic [ref=e263]: ", opens in a new tab"
+                    - listitem [ref=e264]:
+                      - text: August 14, 2002 -
+                      - link "Modifications to the HIPAA Privacy Rule - Final Rule , opens in a new tab" [ref=e266] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/privruletxt.txt
+                        - text: Modifications to the HIPAA Privacy Rule - Final Rule
+                        - generic [ref=e267]: ", opens in a new tab"
+                      - text: (
+                      - link "PDF , opens in a new tab" [ref=e269] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/privrulepd.pdf
+                        - text: PDF
+                        - generic [ref=e270]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e271]:
+                      - text: March 27, 2002 -
+                      - link "Modifications to the HIPAA Privacy Rule - Proposed Rule , opens in a new tab" [ref=e273] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/propmods.txt
+                        - text: Modifications to the HIPAA Privacy Rule - Proposed Rule
+                        - generic [ref=e274]: ", opens in a new tab"
+                      - text: (
+                      - link "PDF , opens in a new tab" [ref=e276] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/2002proposedmods.pdf
+                        - text: PDF
+                        - generic [ref=e277]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e278]:
+                      - text: February 28, 2001 -
+                      - link "Request for Comments on December 28, 2000, Final HIPAA Privacy Rule , opens in a new tab" [ref=e280] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/comment.txt
+                        - text: Request for Comments on December 28, 2000, Final HIPAA Privacy Rule
+                        - generic [ref=e281]: ", opens in a new tab"
+                      - text: (
+                      - link "PDF , links to an external website , opens in a new tab" [ref=e283] [cursor=pointer]:
+                        - /url: https://www.gpo.gov/fdsys/pkg/FR-2001-02-28/pdf/01-4811.pdf
+                        - text: PDF
+                        - generic [ref=e285]: ", links to an external website"
+                        - generic [ref=e286]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e287]:
+                      - text: February 26, 2001 -
+                      - link "Correction of Effective and Compliance Dates of the Final HIPAA Privacy Rule , opens in a new tab" [ref=e289] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/dates.txt
+                        - text: Correction of Effective and Compliance Dates of the Final HIPAA Privacy Rule
+                        - generic [ref=e290]: ", opens in a new tab"
+                      - text: (
+                      - link "PDF , opens in a new tab" [ref=e292] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/dates.pdf
+                        - text: PDF
+                        - generic [ref=e293]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e294]:
+                      - text: December 29, 2000 -
+                      - link "Technical Corrections to the Final HIPAA Privacy Rule , opens in a new tab" [ref=e296] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/pvcfix01.txt
+                        - text: Technical Corrections to the Final HIPAA Privacy Rule
+                        - generic [ref=e297]: ", opens in a new tab"
+                      - text: (
+                      - link "PDF , opens in a new tab" [ref=e299] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/pvcfix01.pdf
+                        - text: PDF
+                        - generic [ref=e300]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e301]:
+                      - text: December 28, 2000 - HIPAA Privacy Rule - Final Rule (
+                      - link "PDF , opens in a new tab" [ref=e303] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/prdecember2000all8parts.pdf
+                        - text: PDF
+                        - generic [ref=e304]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e305]:
+                      - text: November 3, 1999 - HIPAA Privacy Rule - Proposed Rule (
+                      - link "PDF , opens in a new tab" [ref=e307] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/1999nprm.pdf
+                        - text: PDF
+                        - generic [ref=e308]: ", opens in a new tab"
+                      - text: )
+                  - heading "Other Privacy Rule Notices" [level=2] [ref=e309]
+                  - list [ref=e310]:
+                    - listitem [ref=e311]:
+                      - text: March 20, 2003 - Notice of Addresses for Submission of HIPAA Health Information Privacy Complaints (
+                      - link "PDF , opens in a new tab" [ref=e313] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/noticeaddresssubmission.pdf
+                        - text: PDF
+                        - generic [ref=e314]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e315]:
+                      - text: March 11, 2003 -
+                      - link "Notice of Address for Submission of Requests for Preemption Exception Determinations" [ref=e316] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/notice.txt
+                      - text: (
+                      - link "PDF , opens in a new tab" [ref=e318] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/notice.pdf
+                        - text: PDF
+                        - generic [ref=e319]: ", opens in a new tab"
+                      - text: )
+                    - listitem [ref=e320]:
+                      - text: December 28, 2000 -
+                      - link "Statement of Delegation of Authority to the Office for Civil Rights" [ref=e321] [cursor=pointer]:
+                        - /url: /hipaa/for-professionals/privacy/delegation-of-authority/index.html
+                      - text: (
+                      - link "PDF , opens in a new tab" [ref=e323] [cursor=pointer]:
+                        - /url: /sites/default/files/ocr/privacy/hipaa/administrative/privacyrule/fedreg.pdf
+                        - text: PDF
+                        - generic [ref=e324]: ", opens in a new tab"
+                      - text: )
+                  - generic [ref=e326]:
+                    - heading "Other Administrative Simplification Rules" [level=2] [ref=e327]
+                    - list [ref=e329]:
+                      - listitem [ref=e330]:
+                        - link "Code Set Standards , opens in a new tab" [ref=e332] [cursor=pointer]:
+                          - /url: https://www.cms.gov/priorities/key-initiatives/burden-reduction/administrative-simplification/code-sets
+                          - text: Code Set Standards
+                          - generic [ref=e333]: ", opens in a new tab"
+                      - listitem [ref=e334]:
+                        - link "Employer Identifier Standard , opens in a new tab" [ref=e336] [cursor=pointer]:
+                          - /url: https://www.cms.gov/priorities/key-initiatives/burden-reduction/administrative-simplification/unique-identifiers/ein
+                          - text: Employer Identifier Standard
+                          - generic [ref=e337]: ", opens in a new tab"
+                      - listitem [ref=e338]:
+                        - link "National Provider Identifier Standard , opens in a new tab" [ref=e340] [cursor=pointer]:
+                          - /url: https://www.cms.gov/Regulations-and-Guidance/Administrative-Simplification/NationalProvIdentStand
+                          - text: National Provider Identifier Standard
+                          - generic [ref=e341]: ", opens in a new tab"
+                      - listitem [ref=e342]:
+                        - link "Security Rule" [ref=e343] [cursor=pointer]:
+                          - /url: /hipaa/for-professionals/security/index.html
+                      - listitem [ref=e344]:
+                        - link "Enforcement Rule" [ref=e345] [cursor=pointer]:
+                          - /url: /hipaa/for-professionals/special-topics/enforcement-rule/index.html
+                      - listitem [ref=e346]:
+                        - link "Breach Notification Rule" [ref=e347] [cursor=pointer]:
+                          - /url: /hipaa/for-professionals/breach-notification/laws-regulations/index.html
+                      - listitem [ref=e348]:
+                        - link "Transactions , opens in a new tab" [ref=e350] [cursor=pointer]:
+                          - /url: https://www.cms.gov/priorities/key-initiatives/burden-reduction/administrative-simplification/transactions
+                          - text: Transactions
+                          - generic [ref=e351]: ", opens in a new tab"
+                - paragraph [ref=e357]:
+                  - link "Frequently Asked Questions for Professionals" [ref=e358] [cursor=pointer]:
+                    - /url: https://www.hhs.gov/hipaa/for-professionals/faq/index.html
+                  - text: "- Please see the HIPAA FAQs for additional guidance on health information privacy topics."
+          - generic [ref=e368]:
+            - text: Content last reviewed
+            - time [ref=e369]: September 27, 2024
+    - contentinfo [ref=e370]:
+      - link [ref=e371] [cursor=pointer]:
+        - /url: "#top"
+        - img [ref=e372]
+        - generic [ref=e374]: Back to top
+      - generic "Social media links and sign up" [ref=e375]:
+        - generic [ref=e377]:
+          - generic [ref=e378]:
+            - img "Secretary Robert F. Kennedy Jr." [ref=e380]
+            - generic [ref=e381]:
+              - heading "Follow @SecKennedy" [level=2] [ref=e382]
+              - generic [ref=e383]:
+                - link "Visit the Facebook account of Secretary Kennedy" [ref=e385] [cursor=pointer]:
+                  - /url: https://www.facebook.com/SecKennedy
+                  - img [ref=e386]
+                - link "Visit the X account of Secretary Kennedy" [ref=e389] [cursor=pointer]:
+                  - /url: https://x.com/SecKennedy
+                  - img [ref=e390]
+                - link "Visit the Instagram account of Secretary Kennedy" [ref=e393] [cursor=pointer]:
+                  - /url: https://www.instagram.com/seckennedy/
+                  - img [ref=e394]
+                - link "Visit the Truth Social account of Secretary Kennedy" [ref=e397] [cursor=pointer]:
+                  - /url: https://truthsocial.com/@seckennedy
+                  - img [ref=e398]
+                - link "Visit the LinkedIn account of Secretary Kennedy" [ref=e401] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/showcase/secretarykennedy/
+                  - img [ref=e402]
+          - generic [ref=e404]:
+            - img "HHS icon" [ref=e406]
+            - generic [ref=e407]:
+              - heading "Follow @HHSGov" [level=2] [ref=e408]
+              - generic [ref=e409]:
+                - link "Visit the HHS Facebook account" [ref=e411] [cursor=pointer]:
+                  - /url: https://www.facebook.com/HHS
+                  - img [ref=e412]
+                - link "Visit the HHS X account" [ref=e415] [cursor=pointer]:
+                  - /url: https://x.com/hhsgov
+                  - img [ref=e416]
+                - link "Visit the HHS YouTube account" [ref=e419] [cursor=pointer]:
+                  - /url: https://www.youtube.com/user/USGOVHHS?sub_confirmation=1
+                  - img [ref=e420]
+                - link "Visit the HHS Instagram account" [ref=e423] [cursor=pointer]:
+                  - /url: https://www.instagram.com/hhsgov/
+                  - img [ref=e424]
+                - link "Visit the HHS LinkedIn account" [ref=e427] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/company/hhsgov
+                  - img [ref=e428]
+          - generic [ref=e438]:
+            - heading "HHS Email updates" [level=3] [ref=e439]
+            - paragraph [ref=e440]: Receive email updates from HHS.
+            - paragraph [ref=e441]:
+              - link "Subscribe" [ref=e442] [cursor=pointer]:
+                - /url: https://cloud.connect.hhs.gov/subscriptioncenter
+      - contentinfo "Agency logo and contact information" [ref=e443]:
+        - generic [ref=e444]:
+          - link "HHS Logo" [ref=e448] [cursor=pointer]:
+            - /url: https://hhs.gov
+            - img "HHS Logo" [ref=e449]
+          - generic [ref=e450]:
+            - generic [ref=e452]:
+              - heading "HHS Headquarters" [level=3] [ref=e453]
+              - paragraph [ref=e457]:
+                - text: 200 Independence Avenue, S.W.
+                - text: Washington, D.C. 20201
+                - text: "Toll Free Call Center: 1-877-696-6775"
+            - navigation [ref=e459]:
+              - generic [ref=e460]:
+                - list [ref=e462]:
+                  - listitem [ref=e463]:
+                    - link "Contact HHS" [ref=e464] [cursor=pointer]:
+                      - /url: /about/contact-us/index.html
+                  - listitem [ref=e465]:
+                    - link "Careers" [ref=e466] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/careers/
+                  - listitem [ref=e467]:
+                    - link "HHS FAQs" [ref=e468] [cursor=pointer]:
+                      - /url: /answers/index.html
+                  - listitem [ref=e469]:
+                    - link "Nondiscrimination Notice" [ref=e470] [cursor=pointer]:
+                      - /url: /civil-rights/for-individuals/nondiscrimination/index.html
+                - list [ref=e472]:
+                  - listitem [ref=e473]:
+                    - link "Press Room" [ref=e474] [cursor=pointer]:
+                      - /url: /press-room/index.html
+                  - listitem [ref=e475]:
+                    - link "HHS Archive" [ref=e476] [cursor=pointer]:
+                      - /url: /about/archive/index.html
+                  - listitem [ref=e477]:
+                    - link "Accessibility Statement" [ref=e478] [cursor=pointer]:
+                      - /url: /web/section-508/hhs-digital-accessibility-statement/index.html
+                - list [ref=e480]:
+                  - listitem [ref=e481]:
+                    - link "Budget/Performance" [ref=e482] [cursor=pointer]:
+                      - /url: /about/budget/index.html
+                  - listitem [ref=e483]:
+                    - link "Inspector General" [ref=e484] [cursor=pointer]:
+                      - /url: https://oig.hhs.gov/
+                  - listitem [ref=e485]:
+                    - link "Web Site Disclaimers" [ref=e486] [cursor=pointer]:
+                      - /url: /web/policies-and-standards/hhs-web-policies/disclaimer/index.html
+                  - listitem [ref=e487]:
+                    - link "EEO/No Fear Act" [ref=e488] [cursor=pointer]:
+                      - /url: /about/agencies/asa/eeo/no-fear-act/index.html
+                - list [ref=e490]:
+                  - listitem [ref=e491]:
+                    - link "FOIA" [ref=e492] [cursor=pointer]:
+                      - /url: /foia/index.html
+                  - listitem [ref=e493]:
+                    - link "The White House" [ref=e494] [cursor=pointer]:
+                      - /url: https://www.whitehouse.gov/
+                  - listitem [ref=e495]:
+                    - link "USA.gov" [ref=e496] [cursor=pointer]:
+                      - /url: https://www.usa.gov/
+                  - listitem [ref=e497]:
+                    - link "Vulnerability Disclosure Policy" [ref=e498] [cursor=pointer]:
+                      - /url: /vulnerability-disclosure-policy/index.html
+```
+
+## Security Rule Page Snapshot
+
+```text
+Page Title: The Security Rule | HHS.gov
+URL: https://www.hhs.gov/hipaa/for-professionals/security/index.html
+Snapshot: 
+- generic [active] [ref=e1]:
+  - link "Skip to main content" [ref=e2] [cursor=pointer]:
+    - /url: "#main"
+  - generic [ref=e4]:
+    - region "Official government website" [ref=e5]:
+      - generic [ref=e8]:
+        - img "U.S. flag" [ref=e10]
+        - paragraph [ref=e12]: An official website of the United States government
+        - button "Here’s how you know" [ref=e13] [cursor=pointer]
+    - generic [ref=e19]:
+      - img "Freedom 250 banner logo" [ref=e20]
+      - link "Join HHS in Celebrating Freedom 250" [ref=e21] [cursor=pointer]:
+        - /url: /freedom250/index.html
+      - img [ref=e22]
+    - banner [ref=e24]:
+      - generic [ref=e25]:
+        - link "Home" [ref=e28] [cursor=pointer]:
+          - /url: /
+          - img [ref=e29]
+        - button "Menu" [ref=e115]
+    - generic [ref=e118]:
+      - navigation "breadcrumb-label-11786852735" [ref=e120]:
+        - generic [ref=e122]:
+          - generic [ref=e123]: Breadcrumb
+          - list [ref=e124]:
+            - listitem [ref=e125]:
+              - link "HHS" [ref=e126] [cursor=pointer]:
+                - /url: /
+            - listitem [ref=e127]:
+              - link "HIPAA Home" [ref=e128] [cursor=pointer]:
+                - /url: /hipaa/index.html
+            - listitem [ref=e129]:
+              - link "For Professionals" [ref=e130] [cursor=pointer]:
+                - /url: /hipaa/for-professionals/index.html
+            - listitem [ref=e131]: The Security Rule
+      - list [ref=e135]:
+        - listitem [ref=e136]:
+          - checkbox "Adjust Text Size" [ref=e137] [cursor=pointer]:
+            - img [ref=e138]
+        - listitem [ref=e139]:
+          - link "Print" [ref=e140] [cursor=pointer]:
+            - /url: "#"
+            - img [ref=e141]
+        - listitem [ref=e143]:
+          - button "Page sharing options" [ref=e144] [cursor=pointer]:
+            - img [ref=e145]
+            - generic [ref=e147]: Page sharing options
+    - main [ref=e148]:
+      - generic [ref=e152]:
+        - complementary [ref=e153]:
+          - button "Navigate to:" [ref=e156] [cursor=pointer]
+        - generic [ref=e157]:
+          - generic [ref=e160]:
+            - heading "The Security Rule" [level=1] [ref=e161]
+            - article [ref=e162]:
+              - generic [ref=e163]:
+                - generic [ref=e167]:
+                  - paragraph [ref=e168]: The HIPAA Security Rule establishes national standards to protect individuals' electronic protected health information that is created, received, used, or maintained by a covered entity or its business associate. The Security Rule requires implementation of appropriate administrative, physical, and technical safeguards to ensure the confidentiality, integrity, and availability of electronic protected health information.
+                  - paragraph [ref=e169]:
+                    - text: The Security Rule is located at 45 CFR
+                    - link "Part 160 , links to an external website" [ref=e170] [cursor=pointer]:
+                      - /url: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160?toc=1
+                      - text: Part 160
+                      - generic [ref=e172]: ", links to an external website"
+                    - text: and Subparts A and C of
+                    - link "Part 164 , links to an external website" [ref=e173] [cursor=pointer]:
+                      - /url: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164
+                      - text: Part 164
+                      - generic [ref=e175]: ", links to an external website"
+                    - text: .
+                  - paragraph [ref=e176]:
+                    - link "View the combined regulation text" [ref=e177] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/ocr/privacy/hipaa/administrative/combined/index.html?language=es
+                    - text: of all HIPAA Administrative Simplification Regulations found at 45 CFR 160, 162, and 164.
+                - generic [ref=e181]:
+                  - heading "Security Rule History" [level=2] [ref=e182]
+                  - generic [ref=e184]:
+                    - generic [ref=e186]:
+                      - heading "January 6, 2025" [level=3] [ref=e187]
+                      - paragraph [ref=e188]:
+                        - link "HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information – Proposed Rule , links to an external website" [ref=e189] [cursor=pointer]:
+                          - /url: https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information
+                          - text: HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information – Proposed Rule
+                          - generic [ref=e191]: ", links to an external website"
+                      - separator [ref=e192]
+                    - generic [ref=e194]:
+                      - heading "January 25, 2013" [level=3] [ref=e195]
+                      - paragraph [ref=e196]:
+                        - link "Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules under the Health Information Technology for Economic and Clinical Health (HITECH) Act and the Genetic Information Nondiscrimination Act, and Other Modifications – Final Rule , links to an external website , opens in a new tab" [ref=e198] [cursor=pointer]:
+                          - /url: https://www.govinfo.gov/content/pkg/FR-2013-01-25/pdf/2013-01073.pdf
+                          - text: Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules under the Health Information Technology for Economic and Clinical Health (HITECH) Act and the Genetic Information Nondiscrimination Act, and Other Modifications – Final Rule
+                          - generic [ref=e200]: ", links to an external website"
+                          - generic [ref=e201]: ", opens in a new tab"
+                        - text: (The “Omnibus HIPAA Final Rule”)
+                      - separator [ref=e202]
+                    - generic [ref=e204]:
+                      - heading "July 14, 2010" [level=3] [ref=e205]
+                      - paragraph [ref=e206]:
+                        - link "Modifications to the HIPAA Privacy, Security, and Enforcement Rules under the HITECH Act – Proposed Rule , links to an external website , opens in a new tab" [ref=e208] [cursor=pointer]:
+                          - /url: https://www.govinfo.gov/content/pkg/FR-2010-07-14/pdf/2010-16718.pdf
+                          - text: Modifications to the HIPAA Privacy, Security, and Enforcement Rules under the HITECH Act – Proposed Rule
+                          - generic [ref=e210]: ", links to an external website"
+                          - generic [ref=e211]: ", opens in a new tab"
+                      - separator [ref=e212]
+                    - generic [ref=e214]:
+                      - heading "August 4, 2009" [level=3] [ref=e215]
+                      - paragraph [ref=e216]:
+                        - link "Federal Register notice of the Delegation of Authority to OCR (74 FR 38630)" [ref=e217] [cursor=pointer]:
+                          - /url: https://www.hhs.gov/sites/default/files/ocr/privacy/hipaa/administrative/securityrule/srdelegation.pdf?language=es
+                      - separator [ref=e218]
+                    - generic [ref=e220]:
+                      - heading "February 20, 2003" [level=3] [ref=e221]
+                      - paragraph [ref=e222]:
+                        - link "Security Standards – Final Rule" [ref=e223] [cursor=pointer]:
+                          - /url: https://www.hhs.gov/sites/default/files/ocr/privacy/hipaa/administrative/securityrule/securityrulepdf.pdf?language=es
+                      - separator [ref=e224]
+                    - generic [ref=e226]:
+                      - heading "August 12, 1998" [level=3] [ref=e227]
+                      - paragraph [ref=e228]:
+                        - link "Security and Electronic Signature Standards - Proposed Rule" [ref=e229] [cursor=pointer]:
+                          - /url: https://www.hhs.gov/sites/default/files/ocr/privacy/hipaa/administrative/securityrule/srnprm.pdf?language=es
+                      - separator [ref=e230]
+                - generic [ref=e234]:
+                  - heading "HHS Security Risk Assessment Tool" [level=2] [ref=e235]
+                  - paragraph [ref=e236]:
+                    - text: The Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP/ONC) and the HHS Office for Civil Rights (OCR) have jointly launched a
+                    - link "Security Risk Assessment Tool for regulated entities" [ref=e237] [cursor=pointer]:
+                      - /url: https://healthit.gov/privacy-security/security-risk-assessment-tool/
+                    - text: . The tool's features make it useful in assisting small and medium-sized health care practices and business associates as they perform a risk assessment.
+                  - heading "OCR and NIST HIPAA Security Rule Conference" [level=2] [ref=e238]
+                  - paragraph [ref=e239]:
+                    - strong [ref=e240]: "Safeguarding Health Information: Building Assurance Through HIPAA Security"
+                  - paragraph [ref=e241]:
+                    - text: View the presentations from the
+                    - link "OCR and NIST HIPAA Security Rule Conference , links to an external website" [ref=e242] [cursor=pointer]:
+                      - /url: https://www.nist.gov/news-events/events/2024/10/safeguarding-health-information-building-assurance-through-hipaa-security
+                      - text: OCR and NIST HIPAA Security Rule Conference
+                      - generic [ref=e244]: ", links to an external website"
+                    - text: held October 23-24, 2024.
+                  - heading "Security Rule Guidance" [level=2] [ref=e245]
+                  - paragraph [ref=e246]:
+                    - text: See the
+                    - link "Security Rule Guidance" [ref=e247] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/security/guidance/index.html?language=es
+                    - text: and
+                    - link "Cyber Security Guidance" [ref=e248] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/security/guidance/cybersecurity/index.html
+                    - text: webpages for guidance
+          - generic [ref=e258]:
+            - text: Content last reviewed
+            - time [ref=e259]: March 19, 2026
+    - contentinfo [ref=e260]:
+      - link [ref=e261] [cursor=pointer]:
+        - /url: "#top"
+        - img [ref=e262]
+        - generic [ref=e264]: Back to top
+      - generic "Social media links and sign up" [ref=e265]:
+        - generic [ref=e267]:
+          - generic [ref=e268]:
+            - img "Secretary Robert F. Kennedy Jr." [ref=e270]
+            - generic [ref=e271]:
+              - heading "Follow @SecKennedy" [level=2] [ref=e272]
+              - generic [ref=e273]:
+                - link "Visit the Facebook account of Secretary Kennedy" [ref=e275] [cursor=pointer]:
+                  - /url: https://www.facebook.com/SecKennedy
+                  - img [ref=e276]
+                - link "Visit the X account of Secretary Kennedy" [ref=e279] [cursor=pointer]:
+                  - /url: https://x.com/SecKennedy
+                  - img [ref=e280]
+                - link "Visit the Instagram account of Secretary Kennedy" [ref=e283] [cursor=pointer]:
+                  - /url: https://www.instagram.com/seckennedy/
+                  - img [ref=e284]
+                - link "Visit the Truth Social account of Secretary Kennedy" [ref=e287] [cursor=pointer]:
+                  - /url: https://truthsocial.com/@seckennedy
+                  - img [ref=e288]
+                - link "Visit the LinkedIn account of Secretary Kennedy" [ref=e291] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/showcase/secretarykennedy/
+                  - img [ref=e292]
+          - generic [ref=e294]:
+            - img "HHS icon" [ref=e296]
+            - generic [ref=e297]:
+              - heading "Follow @HHSGov" [level=2] [ref=e298]
+              - generic [ref=e299]:
+                - link "Visit the HHS Facebook account" [ref=e301] [cursor=pointer]:
+                  - /url: https://www.facebook.com/HHS
+                  - img [ref=e302]
+                - link "Visit the HHS X account" [ref=e305] [cursor=pointer]:
+                  - /url: https://x.com/hhsgov
+                  - img [ref=e306]
+                - link "Visit the HHS YouTube account" [ref=e309] [cursor=pointer]:
+                  - /url: https://www.youtube.com/user/USGOVHHS?sub_confirmation=1
+                  - img [ref=e310]
+                - link "Visit the HHS Instagram account" [ref=e313] [cursor=pointer]:
+                  - /url: https://www.instagram.com/hhsgov/
+                  - img [ref=e314]
+                - link "Visit the HHS LinkedIn account" [ref=e317] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/company/hhsgov
+                  - img [ref=e318]
+          - generic [ref=e328]:
+            - heading "HHS Email updates" [level=3] [ref=e329]
+            - paragraph [ref=e330]: Receive email updates from HHS.
+            - paragraph [ref=e331]:
+              - link "Subscribe" [ref=e332] [cursor=pointer]:
+                - /url: https://cloud.connect.hhs.gov/subscriptioncenter
+      - contentinfo "Agency logo and contact information" [ref=e333]:
+        - generic [ref=e334]:
+          - link "HHS Logo" [ref=e338] [cursor=pointer]:
+            - /url: https://hhs.gov
+            - img "HHS Logo" [ref=e339]
+          - generic [ref=e340]:
+            - generic [ref=e342]:
+              - heading "HHS Headquarters" [level=3] [ref=e343]
+              - paragraph [ref=e347]:
+                - text: 200 Independence Avenue, S.W.
+                - text: Washington, D.C. 20201
+                - text: "Toll Free Call Center: 1-877-696-6775"
+            - navigation [ref=e349]:
+              - generic [ref=e350]:
+                - list [ref=e352]:
+                  - listitem [ref=e353]:
+                    - link "Contact HHS" [ref=e354] [cursor=pointer]:
+                      - /url: /about/contact-us/index.html
+                  - listitem [ref=e355]:
+                    - link "Careers" [ref=e356] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/careers/
+                  - listitem [ref=e357]:
+                    - link "HHS FAQs" [ref=e358] [cursor=pointer]:
+                      - /url: /answers/index.html
+                  - listitem [ref=e359]:
+                    - link "Nondiscrimination Notice" [ref=e360] [cursor=pointer]:
+                      - /url: /civil-rights/for-individuals/nondiscrimination/index.html
+                - list [ref=e362]:
+                  - listitem [ref=e363]:
+                    - link "Press Room" [ref=e364] [cursor=pointer]:
+                      - /url: /press-room/index.html
+                  - listitem [ref=e365]:
+                    - link "HHS Archive" [ref=e366] [cursor=pointer]:
+                      - /url: /about/archive/index.html
+                  - listitem [ref=e367]:
+                    - link "Accessibility Statement" [ref=e368] [cursor=pointer]:
+                      - /url: /web/section-508/hhs-digital-accessibility-statement/index.html
+                - list [ref=e370]:
+                  - listitem [ref=e371]:
+                    - link "Budget/Performance" [ref=e372] [cursor=pointer]:
+                      - /url: /about/budget/index.html
+                  - listitem [ref=e373]:
+                    - link "Inspector General" [ref=e374] [cursor=pointer]:
+                      - /url: https://oig.hhs.gov/
+                  - listitem [ref=e375]:
+                    - link "Web Site Disclaimers" [ref=e376] [cursor=pointer]:
+                      - /url: /web/policies-and-standards/hhs-web-policies/disclaimer/index.html
+                  - listitem [ref=e377]:
+                    - link "EEO/No Fear Act" [ref=e378] [cursor=pointer]:
+                      - /url: /about/agencies/asa/eeo/no-fear-act/index.html
+                - list [ref=e380]:
+                  - listitem [ref=e381]:
+                    - link "FOIA" [ref=e382] [cursor=pointer]:
+                      - /url: /foia/index.html
+                  - listitem [ref=e383]:
+                    - link "The White House" [ref=e384] [cursor=pointer]:
+                      - /url: https://www.whitehouse.gov/
+                  - listitem [ref=e385]:
+                    - link "USA.gov" [ref=e386] [cursor=pointer]:
+                      - /url: https://www.usa.gov/
+                  - listitem [ref=e387]:
+                    - link "Vulnerability Disclosure Policy" [ref=e388] [cursor=pointer]:
+                      - /url: /vulnerability-disclosure-policy/index.html
+```
+
+## Breach Notification Rule Page Snapshot
+
+```text
+Page Title: Breach Notification Rule | HHS.gov
+URL: https://www.hhs.gov/hipaa/for-professionals/breach-notification/index.html
+Snapshot: 
+- generic [active] [ref=e1]:
+  - link "Skip to main content" [ref=e2] [cursor=pointer]:
+    - /url: "#main"
+  - generic [ref=e4]:
+    - region "Official government website" [ref=e5]:
+      - generic [ref=e8]:
+        - img "U.S. flag" [ref=e10]
+        - paragraph [ref=e12]: An official website of the United States government
+        - button "Here’s how you know" [ref=e13] [cursor=pointer]
+    - generic [ref=e19]:
+      - img "Freedom 250 banner logo" [ref=e20]
+      - link "Join HHS in Celebrating Freedom 250" [ref=e21] [cursor=pointer]:
+        - /url: /freedom250/index.html
+      - img [ref=e22]
+    - banner [ref=e24]:
+      - generic [ref=e25]:
+        - link "Home" [ref=e28] [cursor=pointer]:
+          - /url: /
+          - img [ref=e29]
+        - button "Menu" [ref=e115]
+    - generic [ref=e118]:
+      - navigation "breadcrumb-label-11751584064" [ref=e120]:
+        - generic [ref=e122]:
+          - generic [ref=e123]: Breadcrumb
+          - list [ref=e124]:
+            - listitem [ref=e125]:
+              - link "HHS" [ref=e126] [cursor=pointer]:
+                - /url: /
+            - listitem [ref=e127]:
+              - link "HIPAA Home" [ref=e128] [cursor=pointer]:
+                - /url: /hipaa/index.html
+            - listitem [ref=e129]:
+              - link "For Professionals" [ref=e130] [cursor=pointer]:
+                - /url: /hipaa/for-professionals/index.html
+            - listitem [ref=e131]: Breach Notification Rule
+      - list [ref=e135]:
+        - listitem [ref=e136]:
+          - checkbox "Adjust Text Size" [ref=e137] [cursor=pointer]:
+            - img [ref=e138]
+        - listitem [ref=e139]:
+          - link "Print" [ref=e140] [cursor=pointer]:
+            - /url: "#"
+            - img [ref=e141]
+        - listitem [ref=e143]:
+          - button "Page sharing options" [ref=e144] [cursor=pointer]:
+            - img [ref=e145]
+            - generic [ref=e147]: Page sharing options
+    - main [ref=e148]:
+      - generic [ref=e152]:
+        - complementary [ref=e153]:
+          - button "Navigate to:" [ref=e156] [cursor=pointer]
+        - generic [ref=e157]:
+          - generic [ref=e160]:
+            - heading "Breach Notification Rule" [level=1] [ref=e161]
+            - article [ref=e162]:
+              - generic [ref=e167]:
+                - paragraph [ref=e168]:
+                  - text: The HIPAA Breach Notification Rule, 45 CFR §§ 164.400-414, requires HIPAA covered entities and their business associates to provide notification following a breach of unsecured protected health information. Similar breach notification provisions implemented and enforced by the
+                  - link "Federal Trade Commission (FTC) , links to an external website" [ref=e169] [cursor=pointer]:
+                    - /url: http://business.ftc.gov/privacy-and-security/health-privacy/health-breach-notification-rule
+                    - text: Federal Trade Commission (FTC)
+                    - generic [ref=e171]: ", links to an external website"
+                  - text: ", apply to vendors of personal health records and their third party service providers, pursuant to section 13407 of the HITECH Act."
+                - heading "Definition of Breach" [level=2] [ref=e172]
+                - paragraph [ref=e173]: "A breach is, generally, an impermissible use or disclosure under the Privacy Rule that compromises the security or privacy of the protected health information. An impermissible use or disclosure of protected health information is presumed to be a breach unless the covered entity or business associate, as applicable, demonstrates that there is a low probability that the protected health information has been compromised based on a risk assessment of at least the following factors:"
+                - list [ref=e174]:
+                  - listitem [ref=e175]: The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification;
+                  - listitem [ref=e176]: The unauthorized person who used the protected health information or to whom the disclosure was made;
+                  - listitem [ref=e177]: Whether the protected health information was actually acquired or viewed; and
+                  - listitem [ref=e178]: The extent to which the risk to the protected health information has been mitigated.
+                - paragraph [ref=e179]: Covered entities and business associates, where applicable, have discretion to provide the required breach notifications following an impermissible use or disclosure without performing a risk assessment to determine the probability that the protected health information has been compromised.
+                - paragraph [ref=e180]: There are three exceptions to the definition of “breach.” The first exception applies to the unintentional acquisition, access, or use of protected health information by a workforce member or person acting under the authority of a covered entity or business associate, if such acquisition, access, or use was made in good faith and within the scope of authority. The second exception applies to the inadvertent disclosure of protected health information by a person authorized to access protected health information at a covered entity or business associate to another person authorized to access protected health information at the covered entity or business associate, or organized health care arrangement in which the covered entity participates. In both cases, the information cannot be further used or disclosed in a manner not permitted by the Privacy Rule. The final exception applies if the covered entity or business associate has a good faith belief that the unauthorized person to whom the impermissible disclosure was made, would not have been able to retain the information.
+                - heading "Unsecured Protected Health Information and Guidance" [level=2] [ref=e181]
+                - paragraph [ref=e182]: Covered entities and business associates must only provide the required notifications if the breach involved unsecured protected health information. Unsecured protected health information is protected health information that has not been rendered unusable, unreadable, or indecipherable to unauthorized persons through the use of a technology or methodology specified by the Secretary in guidance.
+                - paragraph [ref=e183]: This guidance was first issued in April 2009 with a request for public comment. The guidance was reissued after consideration of public comment received and specifies encryption and destruction as the technologies and methodologies for rendering protected health information unusable, unreadable, or indecipherable to unauthorized individuals. Additionally, the guidance also applies to unsecured personal health record identifiable health information under the FTC regulations. Covered entities and business associates, as well as entities regulated by the FTC regulations, that secure information as specified by the guidance are relieved from providing notifications following the breach of such information.
+                - paragraph [ref=e184]:
+                  - link "View the Guidance Specifying the Technologies and Methodologies that Render Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals." [ref=e185] [cursor=pointer]:
+                    - /url: /hipaa/for-professionals/breach-notification/guidance/index.html
+                - heading "Breach Notification Requirements" [level=2] [ref=e186]
+                - paragraph [ref=e187]: Following a breach of unsecured protected health information, covered entities must provide notification of the breach to affected individuals, the Secretary, and, in certain circumstances, to the media. In addition, business associates must notify covered entities if a breach occurs at or by the business associate.
+                - heading "Individual Notice" [level=3] [ref=e188]
+                - paragraph [ref=e189]: Covered entities must notify affected individuals following the discovery of a breach of unsecured protected health information. Covered entities must provide this individual notice in written form by first-class mail, or alternatively, by e-mail if the affected individual has agreed to receive such notices electronically. If the covered entity has insufficient or out-of-date contact information for 10 or more individuals, the covered entity must provide substitute individual notice by either posting the notice on the home page of its web site for at least 90 days or by providing the notice in major print or broadcast media where the affected individuals likely reside. The covered entity must include a toll-free phone number that remains active for at least 90 days where individuals can learn if their information was involved in the breach. If the covered entity has insufficient or out-of-date contact information for fewer than 10 individuals, the covered entity may provide substitute notice by an alternative form of written notice, by telephone, or other means.
+                - paragraph [ref=e190]: These individual notifications must be provided without unreasonable delay and in no case later than 60 days following the discovery of a breach and must include, to the extent possible, a brief description of the breach, a description of the types of information that were involved in the breach, the steps affected individuals should take to protect themselves from potential harm, a brief description of what the covered entity is doing to investigate the breach, mitigate the harm, and prevent further breaches, as well as contact information for the covered entity (or business associate, as applicable).
+                - paragraph [ref=e191]: With respect to a breach at or by a business associate, while the covered entity is ultimately responsible for ensuring individuals are notified, the covered entity may delegate the responsibility of providing individual notices to the business associate. Covered entities and business associates should consider which entity is in the best position to provide notice to the individual, which may depend on various circumstances, such as the functions the business associate performs on behalf of the covered entity and which entity has the relationship with the individual.
+                - heading "Media Notice" [level=3] [ref=e192]
+                - paragraph [ref=e193]: Covered entities that experience a breach affecting more than 500 residents of a State or jurisdiction are, in addition to notifying the affected individuals, required to provide notice to prominent media outlets serving the State or jurisdiction. Covered entities will likely provide this notification in the form of a press release to appropriate media outlets serving the affected area. Like individual notice, this media notification must be provided without unreasonable delay and in no case later than 60 days following the discovery of a breach and must include the same information required for the individual notice.
+                - heading "Notice to the Secretary" [level=3] [ref=e194]
+                - paragraph [ref=e195]:
+                  - text: In addition to notifying affected individuals and the media (where appropriate), covered entities must notify the Secretary of breaches of unsecured protected health information. Covered entities will notify the Secretary by visiting the HHS web site and
+                  - link "filling out and electronically submitting a breach report form" [ref=e196] [cursor=pointer]:
+                    - /url: /hipaa/for-professionals/breach-notification/breach-reporting/index.html
+                  - text: . If a breach affects 500 or more individuals, covered entities must notify the Secretary without unreasonable delay and in no case later than 60 days following a breach. If, however, a breach affects fewer than 500 individuals, the covered entity may notify the Secretary of such breaches on an annual basis. Reports of breaches affecting fewer than 500 individuals are due to the Secretary no later than 60 days after the end of the calendar year in which the breaches are discovered.
+                - heading "Notification by a Business Associate" [level=2] [ref=e197]
+                - paragraph [ref=e198]: If a breach of unsecured protected health information occurs at or by a business associate, the business associate must notify the covered entity following the discovery of the breach. A business associate must provide notice to the covered entity without unreasonable delay and no later than 60 days from the discovery of the breach. To the extent possible, the business associate should provide the covered entity with the identification of each individual affected by the breach as well as any other available information required to be provided by the covered entity in its notification to affected individuals.
+                - heading "Administrative Requirements and Burden of Proof" [level=2] [ref=e199]
+                - paragraph [ref=e200]: "Covered entities and business associates, as applicable, have the burden of demonstrating that all required notifications have been provided or that a use or disclosure of unsecured protected health information did not constitute a breach. Thus, with respect to an impermissible use or disclosure, a covered entity (or business associate) should maintain documentation that all required notifications were made, or, alternatively, documentation to demonstrate that notification was not required: (1) its risk assessment demonstrating a low probability that the protected health information has been compromised by the impermissible use or disclosure; or (2) the application of any other exceptions to the definition of “breach.”"
+                - paragraph [ref=e201]: Covered entities are also required to comply with certain administrative requirements with respect to breach notification. For example, covered entities must have in place written policies and procedures regarding breach notification, must train employees on these policies and procedures, and must develop and apply appropriate sanctions against workforce members who do not comply with these policies and procedures.
+                - heading "Instructions for Covered Entities to Submit Breach Notifications to the Secretary" [level=2] [ref=e202]
+                - paragraph [ref=e203]:
+                  - link "Submit a Breach Notification to the Secretary" [ref=e204] [cursor=pointer]:
+                    - /url: /hipaa/for-professionals/breach-notification/breach-reporting/index.html
+                - heading "View Breaches Affecting 500 or More Individuals" [level=2] [ref=e205]
+                - paragraph [ref=e207]:
+                  - text: Breaches of Unsecured Protected Health Information affecting 500 or more individuals.
+                  - link "View a list of these breaches." [ref=e208] [cursor=pointer]:
+                    - /url: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
+                - paragraph [ref=e209]
+          - generic [ref=e219]:
+            - text: Content last reviewed
+            - time [ref=e220]: July 26, 2013
+    - contentinfo [ref=e221]:
+      - link [ref=e222] [cursor=pointer]:
+        - /url: "#top"
+        - img [ref=e223]
+        - generic [ref=e225]: Back to top
+      - generic "Social media links and sign up" [ref=e226]:
+        - generic [ref=e228]:
+          - generic [ref=e229]:
+            - img "Secretary Robert F. Kennedy Jr." [ref=e231]
+            - generic [ref=e232]:
+              - heading "Follow @SecKennedy" [level=2] [ref=e233]
+              - generic [ref=e234]:
+                - link "Visit the Facebook account of Secretary Kennedy" [ref=e236] [cursor=pointer]:
+                  - /url: https://www.facebook.com/SecKennedy
+                  - img [ref=e237]
+                - link "Visit the X account of Secretary Kennedy" [ref=e240] [cursor=pointer]:
+                  - /url: https://x.com/SecKennedy
+                  - img [ref=e241]
+                - link "Visit the Instagram account of Secretary Kennedy" [ref=e244] [cursor=pointer]:
+                  - /url: https://www.instagram.com/seckennedy/
+                  - img [ref=e245]
+                - link "Visit the Truth Social account of Secretary Kennedy" [ref=e248] [cursor=pointer]:
+                  - /url: https://truthsocial.com/@seckennedy
+                  - img [ref=e249]
+                - link "Visit the LinkedIn account of Secretary Kennedy" [ref=e252] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/showcase/secretarykennedy/
+                  - img [ref=e253]
+          - generic [ref=e255]:
+            - img "HHS icon" [ref=e257]
+            - generic [ref=e258]:
+              - heading "Follow @HHSGov" [level=2] [ref=e259]
+              - generic [ref=e260]:
+                - link "Visit the HHS Facebook account" [ref=e262] [cursor=pointer]:
+                  - /url: https://www.facebook.com/HHS
+                  - img [ref=e263]
+                - link "Visit the HHS X account" [ref=e266] [cursor=pointer]:
+                  - /url: https://x.com/hhsgov
+                  - img [ref=e267]
+                - link "Visit the HHS YouTube account" [ref=e270] [cursor=pointer]:
+                  - /url: https://www.youtube.com/user/USGOVHHS?sub_confirmation=1
+                  - img [ref=e271]
+                - link "Visit the HHS Instagram account" [ref=e274] [cursor=pointer]:
+                  - /url: https://www.instagram.com/hhsgov/
+                  - img [ref=e275]
+                - link "Visit the HHS LinkedIn account" [ref=e278] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/company/hhsgov
+                  - img [ref=e279]
+          - generic [ref=e289]:
+            - heading "HHS Email updates" [level=3] [ref=e290]
+            - paragraph [ref=e291]: Receive email updates from HHS.
+            - paragraph [ref=e292]:
+              - link "Subscribe" [ref=e293] [cursor=pointer]:
+                - /url: https://cloud.connect.hhs.gov/subscriptioncenter
+      - contentinfo "Agency logo and contact information" [ref=e294]:
+        - generic [ref=e295]:
+          - link "HHS Logo" [ref=e299] [cursor=pointer]:
+            - /url: https://hhs.gov
+            - img "HHS Logo" [ref=e300]
+          - generic [ref=e301]:
+            - generic [ref=e303]:
+              - heading "HHS Headquarters" [level=3] [ref=e304]
+              - paragraph [ref=e308]:
+                - text: 200 Independence Avenue, S.W.
+                - text: Washington, D.C. 20201
+                - text: "Toll Free Call Center: 1-877-696-6775"
+            - navigation [ref=e310]:
+              - generic [ref=e311]:
+                - list [ref=e313]:
+                  - listitem [ref=e314]:
+                    - link "Contact HHS" [ref=e315] [cursor=pointer]:
+                      - /url: /about/contact-us/index.html
+                  - listitem [ref=e316]:
+                    - link "Careers" [ref=e317] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/careers/
+                  - listitem [ref=e318]:
+                    - link "HHS FAQs" [ref=e319] [cursor=pointer]:
+                      - /url: /answers/index.html
+                  - listitem [ref=e320]:
+                    - link "Nondiscrimination Notice" [ref=e321] [cursor=pointer]:
+                      - /url: /civil-rights/for-individuals/nondiscrimination/index.html
+                - list [ref=e323]:
+                  - listitem [ref=e324]:
+                    - link "Press Room" [ref=e325] [cursor=pointer]:
+                      - /url: /press-room/index.html
+                  - listitem [ref=e326]:
+                    - link "HHS Archive" [ref=e327] [cursor=pointer]:
+                      - /url: /about/archive/index.html
+                  - listitem [ref=e328]:
+                    - link "Accessibility Statement" [ref=e329] [cursor=pointer]:
+                      - /url: /web/section-508/hhs-digital-accessibility-statement/index.html
+                - list [ref=e331]:
+                  - listitem [ref=e332]:
+                    - link "Budget/Performance" [ref=e333] [cursor=pointer]:
+                      - /url: /about/budget/index.html
+                  - listitem [ref=e334]:
+                    - link "Inspector General" [ref=e335] [cursor=pointer]:
+                      - /url: https://oig.hhs.gov/
+                  - listitem [ref=e336]:
+                    - link "Web Site Disclaimers" [ref=e337] [cursor=pointer]:
+                      - /url: /web/policies-and-standards/hhs-web-policies/disclaimer/index.html
+                  - listitem [ref=e338]:
+                    - link "EEO/No Fear Act" [ref=e339] [cursor=pointer]:
+                      - /url: /about/agencies/asa/eeo/no-fear-act/index.html
+                - list [ref=e341]:
+                  - listitem [ref=e342]:
+                    - link "FOIA" [ref=e343] [cursor=pointer]:
+                      - /url: /foia/index.html
+                  - listitem [ref=e344]:
+                    - link "The White House" [ref=e345] [cursor=pointer]:
+                      - /url: https://www.whitehouse.gov/
+                  - listitem [ref=e346]:
+                    - link "USA.gov" [ref=e347] [cursor=pointer]:
+                      - /url: https://www.usa.gov/
+                  - listitem [ref=e348]:
+                    - link "Vulnerability Disclosure Policy" [ref=e349] [cursor=pointer]:
+                      - /url: /vulnerability-disclosure-policy/index.html
+```

datasets/23-hhs-faq-page-verbatim.md

@@ -0,0 +1,281 @@
+# HHS HIPAA FAQ Page — Verbatim Snapshot Dataset
+
+Retrieved: 2026-04-28
+
+Source URL:
+- https://www.hhs.gov/hipaa/for-professionals/faq/index.html
+
+Notes:
+- Captured from browser accessibility snapshot to preserve visible page text and linked URLs.
+- Page references archived FAQ material at https://archive-it.org/collections/4657.
+
+## FAQ Page Snapshot
+
+```text
+Page Title: HIPAA FAQs for Professionals | HHS.gov
+URL: https://www.hhs.gov/hipaa/for-professionals/faq/index.html
+Snapshot: 
+- generic [active] [ref=e1]:
+  - link "Skip to main content" [ref=e2] [cursor=pointer]:
+    - /url: "#main"
+  - generic [ref=e4]:
+    - region "Official government website" [ref=e5]:
+      - generic [ref=e6]:
+        - generic [ref=e8]:
+          - img "U.S. flag" [ref=e10]
+          - paragraph [ref=e12]: An official website of the United States government
+          - button "Here’s how you know" [ref=e13] [cursor=pointer]
+        - generic [ref=e15]:
+          - generic [ref=e16]:
+            - img "Dot gov" [ref=e17]
+            - paragraph [ref=e19]:
+              - strong [ref=e20]: Official websites use .gov
+              - text: A
+              - strong [ref=e21]: .gov
+              - text: website belongs to an official government organization in the United States.
+          - generic [ref=e22]:
+            - img "HTTPS" [ref=e23]
+            - paragraph [ref=e25]:
+              - strong [ref=e26]: Secure .gov websites use HTTPS
+              - text: A
+              - strong [ref=e27]: lock
+              - text: (
+              - img "Lock A locked padlock" [ref=e29]
+              - text: ) or
+              - strong [ref=e31]: https://
+              - text: means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
+    - generic [ref=e37]:
+      - img "Freedom 250 banner logo" [ref=e38]
+      - link "Join HHS in Celebrating Freedom 250" [ref=e39] [cursor=pointer]:
+        - /url: /freedom250/index.html
+      - img [ref=e40]
+    - banner [ref=e42]:
+      - generic [ref=e43]:
+        - link "Home" [ref=e46] [cursor=pointer]:
+          - /url: /
+          - img [ref=e47]
+        - button "Menu" [ref=e133]
+    - generic [ref=e136]:
+      - navigation "breadcrumb-label" [ref=e138]:
+        - generic [ref=e140]:
+          - generic [ref=e141]: Breadcrumb
+          - list [ref=e142]:
+            - listitem [ref=e143]:
+              - link "HHS" [ref=e144] [cursor=pointer]:
+                - /url: /
+            - listitem [ref=e145]:
+              - link "HIPAA Home" [ref=e146] [cursor=pointer]:
+                - /url: /hipaa/index.html
+            - listitem [ref=e147]:
+              - link "For Professionals" [ref=e148] [cursor=pointer]:
+                - /url: /hipaa/for-professionals/index.html
+            - listitem [ref=e149]: HIPAA FAQs for Professionals
+      - list [ref=e153]:
+        - listitem [ref=e154]:
+          - checkbox "Adjust Text Size" [ref=e155] [cursor=pointer]:
+            - img [ref=e156]
+        - listitem [ref=e157]:
+          - link "Print" [ref=e158] [cursor=pointer]:
+            - /url: "#"
+            - img [ref=e159]
+        - listitem [ref=e161]:
+          - button "Page sharing options" [ref=e162] [cursor=pointer]:
+            - img [ref=e163]
+            - generic [ref=e165]: Page sharing options
+    - main [ref=e166]:
+      - generic [ref=e170]:
+        - complementary [ref=e171]:
+          - button "Navigate to:" [ref=e174] [cursor=pointer]
+        - generic [ref=e175]:
+          - generic [ref=e178]:
+            - heading "HIPAA FAQs for Professionals" [level=1] [ref=e179]
+            - article [ref=e180]:
+              - generic [ref=e185]:
+                - generic [ref=e186]:
+                  - paragraph [ref=e187]: Search frequently asked questions about HIPAA by category, number, or keyword.
+                  - paragraph [ref=e188]:
+                    - text: Please note that some older FAQs have been sent to archive. This content is searchable using the search term ‘HIPAA FAQs’ at
+                    - link "https://archive-it.org/collections/4657 , links to an external website , opens in a new tab" [ref=e189] [cursor=pointer]:
+                      - /url: https://archive-it.org/collections/4657
+                      - text: https://archive-it.org/collections/4657
+                      - generic [ref=e191]: ", links to an external website"
+                      - generic [ref=e192]: ", opens in a new tab"
+                    - text: .
+                - paragraph [ref=e193]
+            - generic [ref=e203]:
+              - generic [ref=e204]: FAQs by Category
+              - combobox "FAQs by Category" [ref=e206]:
+                - option "Select a Category" [selected]
+                - option "Authorizations"
+                - option "Business Associates"
+                - option "Compliance Dates"
+                - option "Covered Entities"
+                - option "Decedents"
+                - option "Disclosures for Law Enforcement Purposes"
+                - option "Disclosures for Rule Enforcement"
+                - option "Disclosures in Emergency Situations"
+                - option "Disclosures Required by Law"
+                - option "Disclosures to Family and Friends"
+                - option "Disposal of Protected Health Information"
+                - option "Facility Directories"
+                - option "Family Medical History Information"
+                - option "FERPA and HIPAA"
+                - option "Group Health Plans"
+                - option "Incidental Uses and Disclosures"
+                - option "Judicial and Administrative Proceedings"
+                - option "Minimum Necessary"
+                - option "Notice of Privacy Practice"
+                - option "Preemption of State Law"
+                - 'option "Privacy Rule: General Topics"'
+                - option "Protected Health Information"
+                - option "Public Health Uses and Disclosures"
+                - option "Research Uses and Disclosures"
+                - option "Right to an Accounting of Disclosures"
+                - option "Right to File a Complaint"
+                - option "Right to Request a Restriction"
+                - option "Safeguards"
+                - option "Security Rule"
+                - option "Smaller Providers and Businesses"
+                - option "Student Immunizations"
+                - option "Transition Provisions"
+                - option "Treatment, Payment, and Health Care Operations Disclosures"
+                - option "Workers Compensation Disclosures"
+                - option "Limited Data Set"
+                - option "Marketing"
+                - option "Marketing - Refill Reminders"
+                - option "Personal Representatives and Minors"
+                - option "Right to Access and Research"
+                - option "Mental Health"
+                - option "Health Information Technology"
+                - option "Telehealth"
+              - button "View" [ref=e208] [cursor=pointer]
+            - generic [ref=e209]:
+              - heading "Search HIPAA FAQs by questions or keywords:" [level=2] [ref=e210]
+              - search [ref=e213]:
+                - generic [ref=e214]:
+                  - generic:
+                    - generic:
+                      - generic [ref=e215]: Search HIPAA FAQs by questions or keywords
+                      - searchbox "Search HIPAA FAQs by questions or keywords" [ref=e216]
+                - button "Search" [ref=e217] [cursor=pointer]:
+                  - generic [ref=e218]: Search
+          - generic [ref=e228]:
+            - text: Content last reviewed
+            - time [ref=e229]: October 12, 2017
+    - contentinfo [ref=e230]:
+      - link [ref=e231] [cursor=pointer]:
+        - /url: "#top"
+        - img [ref=e232]
+        - generic [ref=e234]: Back to top
+      - generic "Social media links and sign up" [ref=e235]:
+        - generic [ref=e237]:
+          - generic [ref=e238]:
+            - img "Secretary Robert F. Kennedy Jr." [ref=e240]
+            - generic [ref=e241]:
+              - heading "Follow @SecKennedy" [level=2] [ref=e242]
+              - generic [ref=e243]:
+                - link "Visit the Facebook account of Secretary Kennedy" [ref=e245] [cursor=pointer]:
+                  - /url: https://www.facebook.com/SecKennedy
+                  - img [ref=e246]
+                - link "Visit the X account of Secretary Kennedy" [ref=e249] [cursor=pointer]:
+                  - /url: https://x.com/SecKennedy
+                  - img [ref=e250]
+                - link "Visit the Instagram account of Secretary Kennedy" [ref=e253] [cursor=pointer]:
+                  - /url: https://www.instagram.com/seckennedy/
+                  - img [ref=e254]
+                - link "Visit the Truth Social account of Secretary Kennedy" [ref=e257] [cursor=pointer]:
+                  - /url: https://truthsocial.com/@seckennedy
+                  - img [ref=e258]
+                - link "Visit the LinkedIn account of Secretary Kennedy" [ref=e261] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/showcase/secretarykennedy/
+                  - img [ref=e262]
+          - generic [ref=e264]:
+            - img "HHS icon" [ref=e266]
+            - generic [ref=e267]:
+              - heading "Follow @HHSGov" [level=2] [ref=e268]
+              - generic [ref=e269]:
+                - link "Visit the HHS Facebook account" [ref=e271] [cursor=pointer]:
+                  - /url: https://www.facebook.com/HHS
+                  - img [ref=e272]
+                - link "Visit the HHS X account" [ref=e275] [cursor=pointer]:
+                  - /url: https://x.com/hhsgov
+                  - img [ref=e276]
+                - link "Visit the HHS YouTube account" [ref=e279] [cursor=pointer]:
+                  - /url: https://www.youtube.com/user/USGOVHHS?sub_confirmation=1
+                  - img [ref=e280]
+                - link "Visit the HHS Instagram account" [ref=e283] [cursor=pointer]:
+                  - /url: https://www.instagram.com/hhsgov/
+                  - img [ref=e284]
+                - link "Visit the HHS LinkedIn account" [ref=e287] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/company/hhsgov
+                  - img [ref=e288]
+          - generic [ref=e298]:
+            - heading "HHS Email updates" [level=3] [ref=e299]
+            - paragraph [ref=e300]: Receive email updates from HHS.
+            - paragraph [ref=e301]:
+              - link "Subscribe" [ref=e302] [cursor=pointer]:
+                - /url: https://cloud.connect.hhs.gov/subscriptioncenter
+      - contentinfo "Agency logo and contact information" [ref=e303]:
+        - generic [ref=e304]:
+          - link "HHS Logo" [ref=e308] [cursor=pointer]:
+            - /url: https://hhs.gov
+            - img "HHS Logo" [ref=e309]
+          - generic [ref=e310]:
+            - generic [ref=e312]:
+              - heading "HHS Headquarters" [level=3] [ref=e313]
+              - paragraph [ref=e317]:
+                - text: 200 Independence Avenue, S.W.
+                - text: Washington, D.C. 20201
+                - text: "Toll Free Call Center: 1-877-696-6775"
+            - navigation [ref=e319]:
+              - generic [ref=e320]:
+                - list [ref=e322]:
+                  - listitem [ref=e323]:
+                    - link "Contact HHS" [ref=e324] [cursor=pointer]:
+                      - /url: /about/contact-us/index.html
+                  - listitem [ref=e325]:
+                    - link "Careers" [ref=e326] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/careers/
+                  - listitem [ref=e327]:
+                    - link "HHS FAQs" [ref=e328] [cursor=pointer]:
+                      - /url: /answers/index.html
+                  - listitem [ref=e329]:
+                    - link "Nondiscrimination Notice" [ref=e330] [cursor=pointer]:
+                      - /url: /civil-rights/for-individuals/nondiscrimination/index.html
+                - list [ref=e332]:
+                  - listitem [ref=e333]:
+                    - link "Press Room" [ref=e334] [cursor=pointer]:
+                      - /url: /press-room/index.html
+                  - listitem [ref=e335]:
+                    - link "HHS Archive" [ref=e336] [cursor=pointer]:
+                      - /url: /about/archive/index.html
+                  - listitem [ref=e337]:
+                    - link "Accessibility Statement" [ref=e338] [cursor=pointer]:
+                      - /url: /web/section-508/hhs-digital-accessibility-statement/index.html
+                - list [ref=e340]:
+                  - listitem [ref=e341]:
+                    - link "Budget/Performance" [ref=e342] [cursor=pointer]:
+                      - /url: /about/budget/index.html
+                  - listitem [ref=e343]:
+                    - link "Inspector General" [ref=e344] [cursor=pointer]:
+                      - /url: https://oig.hhs.gov/
+                  - listitem [ref=e345]:
+                    - link "Web Site Disclaimers" [ref=e346] [cursor=pointer]:
+                      - /url: /web/policies-and-standards/hhs-web-policies/disclaimer/index.html
+                  - listitem [ref=e347]:
+                    - link "EEO/No Fear Act" [ref=e348] [cursor=pointer]:
+                      - /url: /about/agencies/asa/eeo/no-fear-act/index.html
+                - list [ref=e350]:
+                  - listitem [ref=e351]:
+                    - link "FOIA" [ref=e352] [cursor=pointer]:
+                      - /url: /foia/index.html
+                  - listitem [ref=e353]:
+                    - link "The White House" [ref=e354] [cursor=pointer]:
+                      - /url: https://www.whitehouse.gov/
+                  - listitem [ref=e355]:
+                    - link "USA.gov" [ref=e356] [cursor=pointer]:
+                      - /url: https://www.usa.gov/
+                  - listitem [ref=e357]:
+                    - link "Vulnerability Disclosure Policy" [ref=e358] [cursor=pointer]:
+                      - /url: /vulnerability-disclosure-policy/index.html
+```

datasets/24-ocr-resolution-agreements-index-verbatim.md

@@ -0,0 +1,841 @@
+# OCR Resolution Agreements Index — Verbatim Snapshot Dataset
+
+Retrieved: 2026-04-28
+
+Source URL:
+- https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/index.html
+
+Notes:
+- Captured from browser accessibility snapshot to preserve visible text and linked URLs.
+- Includes a long list of historical OCR settlements, resolution agreements, and CMP notices.
+
+## Resolution Agreements Page Snapshot
+
+```text
+Page Title: Resolution Agreements | HHS.gov
+URL: https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/index.html
+Snapshot: 
+- generic [active] [ref=e1]:
+  - link "Skip to main content" [ref=e2] [cursor=pointer]:
+    - /url: "#main"
+  - generic [ref=e4]:
+    - region "Official government website" [ref=e5]:
+      - generic [ref=e8]:
+        - img "U.S. flag" [ref=e10]
+        - paragraph [ref=e12]: An official website of the United States government
+        - button "Here’s how you know" [ref=e13] [cursor=pointer]
+    - generic [ref=e19]:
+      - img "Freedom 250 banner logo" [ref=e20]
+      - link "Join HHS in Celebrating Freedom 250" [ref=e21] [cursor=pointer]:
+        - /url: /freedom250/index.html
+      - img [ref=e22]
+    - banner [ref=e24]:
+      - generic [ref=e25]:
+        - link "Home" [ref=e28] [cursor=pointer]:
+          - /url: /
+          - img [ref=e29]
+        - button "Menu" [ref=e115]
+    - generic [ref=e118]:
+      - navigation "breadcrumb-label-1213176406" [ref=e120]:
+        - generic [ref=e122]:
+          - generic [ref=e123]: Breadcrumb
+          - list [ref=e124]:
+            - listitem [ref=e125]:
+              - link "HHS" [ref=e126] [cursor=pointer]:
+                - /url: /
+            - listitem [ref=e127]:
+              - link "HIPAA Home" [ref=e128] [cursor=pointer]:
+                - /url: /hipaa/index.html
+            - listitem [ref=e129]:
+              - link "For Professionals" [ref=e130] [cursor=pointer]:
+                - /url: /hipaa/for-professionals/index.html
+            - listitem [ref=e131]:
+              - link "HIPAA Compliance and Enforcement" [ref=e132] [cursor=pointer]:
+                - /url: /hipaa/for-professionals/compliance-enforcement/index.html
+            - listitem [ref=e133]: Resolution Agreements
+      - list [ref=e137]:
+        - listitem [ref=e138]:
+          - checkbox "Adjust Text Size" [ref=e139] [cursor=pointer]:
+            - img [ref=e140]
+        - listitem [ref=e141]:
+          - link "Print" [ref=e142] [cursor=pointer]:
+            - /url: "#"
+            - img [ref=e143]
+        - listitem [ref=e145]:
+          - button "Page sharing options" [ref=e146] [cursor=pointer]:
+            - img [ref=e147]
+            - generic [ref=e149]: Page sharing options
+    - main [ref=e150]:
+      - generic [ref=e154]:
+        - complementary [ref=e155]:
+          - button "Navigate to:" [ref=e158] [cursor=pointer]
+        - generic [ref=e159]:
+          - generic [ref=e162]:
+            - heading "Resolution Agreements" [level=1] [ref=e163]
+            - article [ref=e164]:
+              - generic [ref=e169]:
+                - heading "Resolution Agreements and Civil Money Penalties" [level=2] [ref=e170]
+                - paragraph [ref=e171]: A resolution agreement is a settlement agreement signed by HHS and a covered entity or business associate in which the covered entity or business associate agrees to perform certain obligations and make reports to HHS, generally for a period of three years. During the period, HHS monitors the covered entity’s compliance with its obligations. A resolution agreement may include the payment of a resolution amount. If HHS cannot reach a satisfactory resolution through the covered entity’s demonstrated compliance or corrective action through other informal means, including a resolution agreement, civil money penalties (CMPs) may be imposed for noncompliance against a covered entity.
+                - list [ref=e172]:
+                  - listitem [ref=e173]:
+                    - link "HHS’ Office for Civil Rights Settles HIPAA Investigation of MMG Fusion, LLC Breach , opens in a new tab" [ref=e175] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-mmg-fusion-hipaa-agreement.pdf
+                      - text: HHS’ Office for Civil Rights Settles HIPAA Investigation of MMG Fusion, LLC Breach
+                      - generic [ref=e176]: ", opens in a new tab"
+                    - text: "- March 5, 2026"
+                  - listitem [ref=e177]:
+                    - paragraph [ref=e178]:
+                      - link "HHS’ Office for Civil Rights Settles HIPAA Ransomware Security Rule Investigation with BST & Co. CPAs, LLP , opens in a new tab" [ref=e180] [cursor=pointer]:
+                        - /url: /sites/default/files/hhs-ocr-bst-hipaa-settlement.pdf
+                        - text: HHS’ Office for Civil Rights Settles HIPAA Ransomware Security Rule Investigation with BST & Co. CPAs, LLP
+                        - generic [ref=e181]: ", opens in a new tab"
+                      - text: "- August 18, 2025"
+                  - listitem [ref=e182]:
+                    - link "HHS’ Office for Civil Rights Settles HIPAA Ransomware Investigation with Syracuse ASC , opens in a new tab" [ref=e184] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-hipaa-racap-syracuse-asc.pdf
+                      - text: HHS’ Office for Civil Rights Settles HIPAA Ransomware Investigation with Syracuse ASC
+                      - generic [ref=e185]: ", opens in a new tab"
+                    - text: "- July 23, 2025"
+                  - listitem [ref=e186]:
+                    - link "HHS’ Office for Civil Rights Settles HIPAA Privacy and Security Rule Investigation with a Behavioral Health Provider , opens in a new tab" [ref=e188] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-hipaa-racap-deer-oaks.pdf
+                      - text: HHS’ Office for Civil Rights Settles HIPAA Privacy and Security Rule Investigation with a Behavioral Health Provider
+                      - generic [ref=e189]: ", opens in a new tab"
+                    - text: "- July 7, 2025"
+                  - listitem [ref=e190]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation with Comstar, LLC" [ref=e191] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/hhs-hipaa-agreement-comstar/index.html
+                    - text: "- May 30, 2025"
+                  - listitem [ref=e192]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Security Rule Investigation with a Florida Health Care Provider , opens in a new tab" [ref=e194] [cursor=pointer]:
+                      - /url: /sites/default/files/hhs-ocr-hipaa-baycare-agreement.pdf
+                      - text: HHS Office for Civil Rights Settles HIPAA Security Rule Investigation with a Florida Health Care Provider
+                      - generic [ref=e195]: ", opens in a new tab"
+                    - text: "- May 28, 2025"
+                  - listitem [ref=e196]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Cybersecurity Investigation with Vision Upright MRI" [ref=e197] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/hhs-ocr-hipaa-racap-vum/index.html
+                    - text: "- May 15, 2025"
+                  - listitem [ref=e198]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation with Neurology Practice , opens in a new tab" [ref=e200] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-hipaa-racap-np.pdf
+                      - text: HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation with Neurology Practice
+                      - generic [ref=e201]: ", opens in a new tab"
+                    - text: "- April 25, 2025"
+                  - listitem [ref=e202]:
+                    - link "HHS Office for Civil Rights Settles Phishing Attack Breach with Health Care Network for $600,000 , opens in a new tab" [ref=e204] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-hipaa-racap-pih.pdf
+                      - text: HHS Office for Civil Rights Settles Phishing Attack Breach with Health Care Network for $600,000
+                      - generic [ref=e205]: ", opens in a new tab"
+                    - text: "- April 23, 2025"
+                  - listitem [ref=e206]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation with Public Hospital , opens in a new tab" [ref=e208] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-hipaa-recap-gmha.pdf
+                      - text: HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation with Public Hospital
+                      - generic [ref=e209]: ", opens in a new tab"
+                    - text: "- April 17, 2025"
+                  - listitem [ref=e210]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Security Rule Investigation with Northeast Radiology , opens in a new tab" [ref=e212] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-hipaa-settlement-nerad.pdf
+                      - text: HHS Office for Civil Rights Settles HIPAA Security Rule Investigation with Northeast Radiology
+                      - generic [ref=e213]: ", opens in a new tab"
+                    - text: "- April 4, 2025"
+                  - listitem [ref=e214]:
+                    - link "HHS’ Office for Civil Rights Settles HIPAA Security Rule Investigation with Health Fitness Corporation , opens in a new tab" [ref=e216] [cursor=pointer]:
+                      - /url: /sites/default/files/ocr-health-fitness-ra-cap.pdf
+                      - text: HHS’ Office for Civil Rights Settles HIPAA Security Rule Investigation with Health Fitness Corporation
+                      - generic [ref=e217]: ", opens in a new tab"
+                    - text: "- March 21, 2025"
+                  - listitem [ref=e218]:
+                    - link "HHS Office for Civil Rights Imposes a $200,000 Penalty Against Oregon Health & Science University for Failure to Provide Timely Access to Patient Records" [ref=e219] [cursor=pointer]:
+                      - /url: /about/news/2025/03/06/hhs-office-civil-rights-imposes-200000-penalty-against-oregon-health-science-university-failure-provide-timely-access-patient-records.html
+                    - text: "- March 6, 2025"
+                  - listitem [ref=e220]:
+                    - link "HHS Office for Civil Rights Imposes a $1,500,000 Civil Money Penalty Against Warby Parker in HIPAA Cybersecurity Hacking Investigation" [ref=e221] [cursor=pointer]:
+                      - /url: /about/news/2025/02/20/hhs-imposes-1500000-penalty-against-warby-parker-hipaa-hacking.html
+                    - text: "- February 20, 2025"
+                  - listitem [ref=e222]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation for $10,000" [ref=e223] [cursor=pointer]:
+                      - /url: /about/news/2025/01/15/hhs-office-civil-rights-settles-hipaa-ransomware-cybersecurity-investigation-northeast-surgical-group.html
+                    - text: "- January 15, 2025"
+                  - listitem [ref=e224]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Case Against Memorial Healthcare System Over Patient Access to Records" [ref=e225] [cursor=pointer]:
+                      - /url: /about/news/2025/01/15/hhs-office-civil-rights-settles-hipaa-case-against-memorial-healthcare-system-over-patient-access-records.html
+                    - text: "- January 15, 2025"
+                  - listitem [ref=e226]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Phishing Cybersecurity Investigation with Solara Medical Supplies, LLC for $3,000,000" [ref=e227] [cursor=pointer]:
+                      - /url: /about/news/2025/01/14/hhs-office-civil-rights-settles-hipaa-phishing-cybersecurity-investigation-solara-medical-supplies-3000000.html
+                    - text: "- January 14, 2025"
+                  - listitem [ref=e228]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Security Rule Investigation with USR Holdings, LLC Concerning the Deletion of Electronic Protected Health Information" [ref=e229] [cursor=pointer]:
+                      - /url: /about/news/2025/01/08/hhs-office-civil-rights-settles-hipaa-security-rule-investigation-usr-holdings-llc-concerning-deletion-electronic-protected-health-information.html
+                    - text: "- January 8, 2025"
+                  - listitem [ref=e230]:
+                    - link "HHS Office for Civil Rights Settles 9th Ransomware Investigation with Virtual Private Network Solutions" [ref=e231] [cursor=pointer]:
+                      - /url: /about/news/2025/01/07/hhs-office-civil-rights-settles-9th-ransomware-investigation-virtual-private-network-solutions.html
+                    - text: "- January 7, 2025"
+                  - listitem [ref=e232]:
+                    - link "HHS Office for Civil Rights Settles 8th Ransomware Investigation with Elgon Information Systems" [ref=e233] [cursor=pointer]:
+                      - /url: /about/news/2025/01/07/hhs-office-civil-rights-settles-8th-ransomware-investigation-elgon-information-systems.html
+                    - text: "- January 7, 2025"
+                  - listitem [ref=e234]:
+                    - link "HHS Office for Civil Rights Settles with Health Care Clearinghouse, Inmediata Health Group, Over HIPAA Impermissible Disclosure" [ref=e235] [cursor=pointer]:
+                      - /url: /about/news/2024/12/10/hhs-office-civil-rights-settles-health-care-clearinghouse-inmediata-health-group-hipaa-impermissible-disclosure.html
+                    - text: "- December 10, 2024"
+                  - listitem [ref=e236]:
+                    - link "HHS Office for Civil Rights Imposes a $548,265 Penalty Against Children’s Hospital Colorado for HIPAA Privacy and Security Rules Violations" [ref=e237] [cursor=pointer]:
+                      - /url: /about/news/2024/12/05/hhs-ocr-imposes-548-265-penalty-against-childrens-hospital-colorado-hipaa-privacy-security-rules-violations.html
+                    - text: "- December 5, 2024"
+                  - listitem [ref=e238]:
+                    - link "HHS Office for Civil Rights Imposes a $1.19 Million Penalty Against Gulf Coast Pain Consultants for HIPAA Security Rule Violations" [ref=e239] [cursor=pointer]:
+                      - /url: /about/news/2024/12/03/hhs-ocr-imposes-penalty-against-gulf-coast-pain-consultants.html
+                    - text: "- December 3, 2024"
+                  - listitem [ref=e240]:
+                    - link "HHS Office for Civil Rights Settles with Holy Redeemer Family Medicine Over Disclosure of Patient’s Protected Health Information, Including Reproductive Health Information" [ref=e241] [cursor=pointer]:
+                      - /url: /about/news/2024/11/26/hhs-office-civil-rights-settles-holy-redeemer-hospital-disclosure-patients-protected-health-information-including-reproductive-health-information.html
+                    - text: "- November 26, 2024"
+                  - listitem [ref=e242]:
+                    - link "HHS Office for Civil Rights Imposes a $100,000 Penalty Against Mental Health Center for Failure to Provide Timely Access to Patient Records" [ref=e243] [cursor=pointer]:
+                      - /url: /about/news/2024/11/19/hhs-office-civil-rights-imposes-penalty-mental-health-center-failure-provide-timely-access-patient-records.html
+                    - text: "- November 19, 2024"
+                  - listitem [ref=e244]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation for $90,000" [ref=e245] [cursor=pointer]:
+                      - /url: /about/news/2024/10/31/hhs-office-for-civil-rights-settles-hipaa-ransomware-cybersecurity-investigation-for-90000-dollars.html
+                    - text: "- October 31, 2024"
+                  - listitem [ref=e246]:
+                    - link "HHS Office for Civil Rights Settles Ransomware Cybersecurity Investigation for $500,000" [ref=e247] [cursor=pointer]:
+                      - /url: /about/news/2024/10/31/hhs-office-civil-rights-settles-ransomware-cybersecurity-investigation-500000.html
+                    - text: "- October 31, 2024"
+                  - listitem [ref=e248]:
+                    - link "HHS Office for Civil Rights Imposes a $70,000 Civil Monetary Penalty Against Gums Dental Care for Failure to Provide Timely Access to Patient Records" [ref=e249] [cursor=pointer]:
+                      - /url: /about/news/2024/10/17/hhs-office-civil-rights-imposes-70000-civil-monetary-penalty-against-gums-dental-care-failure-provide-timely-access-patient-records.html
+                    - text: "- October 17, 2024"
+                  - listitem [ref=e250]:
+                    - link "HHS Office for Civil Rights Imposes a $240,000 Civil Monetary Penalty Against Providence Medical Institute in HIPAA Ransomware Cybersecurity Investigation" [ref=e251] [cursor=pointer]:
+                      - /url: /about/news/2024/10/03/hhs-ocr-imposes-civil-monetary-penalty-against-providence-medical-institute-hipaa-ransomware-cybersecurity-investigation.html
+                    - text: "- October 3, 2024"
+                  - listitem [ref=e252]:
+                    - link "HHS Office for Civil Rights Settles Ransomware Cybersecurity Investigation under HIPAA Security Rule for $250,000" [ref=e253] [cursor=pointer]:
+                      - /url: /about/news/2024/09/26/hhs-office-civil-rights-settles-ransomware-cybersecurity-investigation-under-hipaa-security-rule-250-000.html
+                    - text: "- September 26, 2024"
+                  - listitem [ref=e254]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Security Rule Failures for $950,000" [ref=e255] [cursor=pointer]:
+                      - /url: /about/news/2024/07/01/hhs-office-civil-rights-settles-hipaa-security-rule-failures-950000.html
+                    - text: – July 1, 2024
+                  - listitem [ref=e256]:
+                    - link "HHS OCR Imposes a CMP on NJ Nursing Facility for Failing to Provide Timely Access to Patient Records" [ref=e257] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/hackensack-meridian-health-west-caldwell-care-center/index.html#nfd
+                    - text: "- April 1, 2024"
+                  - listitem [ref=e258]:
+                    - link "HHS’ OCR Settles HIPAA Investigation with Phoenix Healthcare" [ref=e259] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/phoenix-healthcare/index.html
+                    - text: "- March 29, 2024"
+                  - listitem [ref=e260]:
+                    - link "HHS OCR Work with Hospital to Improve Access to Kosher Electronic Devices Use for Virtual Patient Visitation" [ref=e261] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/about/news/2024/03/05/hhs-office-civil-rights-works-hospital-improve-access-kosher-electronic-devices-used-virtual-patient-visitation.html
+                    - text: "- March 5, 2024"
+                  - listitem [ref=e262]:
+                    - link "HHS Finalizes New Provisions to Enhance Integrated Care and Confidentiality for Patients with Substance Use Conditions" [ref=e263] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/regulatory-initiatives/fact-sheet-42-cfr-part-2-final-rule/index.html
+                    - text: – February 8, 2024
+                  - listitem [ref=e264]:
+                    - link "HHS’ Office for Civil Rights Settles Malicious Insider Cybersecurity Investigation for $4.75 Million" [ref=e265] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/montiefore/index.html
+                    - text: "- February 6, 2024"
+                  - listitem [ref=e266]:
+                    - link "Voluntary Resolution Agreement Between The United States Department of Health and Human Services, Office for Civil Rights (“HHS”) and Montiefore" [ref=e267] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/montiefore/index.html
+                    - text: – November 16, 2023
+                  - listitem [ref=e268]:
+                    - link "HHS’ Office for Civil Rights Settles Optum Medical Care" [ref=e269] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/optum-medical-care.html
+                    - text: "- November 15, 2023"
+                  - listitem [ref=e270]:
+                    - link "HHS’ Office for Civil Rights Settles HIPAA Investigation of St. Joseph’s Medical Center for Disclosure of Patients’ Protected Health Information to a News Reporter" [ref=e271] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/sjmc-ra-cap/index.html
+                    - text: "- November 20, 2023"
+                  - listitem [ref=e272]:
+                    - link "HHS’ Office for Civil Rights Settles Ransomware Cyber-Attack Investigation with Doctors’ Management Services" [ref=e273] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/dms-ra-cap/index.html
+                    - text: "- October 31, 2023"
+                  - listitem [ref=e274]:
+                    - link "Green Ridge Behavioral Health, LLC Resolution Agreement and Corrective Action Plan" [ref=e275] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/green-ridge-behavioral-health-ra-cap/index.html
+                    - text: "- October 30, 2023"
+                  - listitem [ref=e276]:
+                    - link "HHS Office for Civil Rights Settles with L.A. Care Health Plan Over Potential HIPAA Security Rule Violations" [ref=e277] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/la-care-health-plan/index.html
+                    - text: "- September 11, 2023"
+                  - listitem [ref=e278]:
+                    - link "Voluntary Resolution Agreement Between The United States Department of Health and Human Services, Office for Civil Rights (“HHS”) and UnitedHealthcare Insurance Company" [ref=e279] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/uhc-ra-cap/index.html
+                    - text: – August 24, 2023
+                  - listitem [ref=e280]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Investigation with iHealth Solutions Regarding Disclosure of Protected Health Information on an Unsecured Server for $75,000" [ref=e281] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/ihealth-ra-cap/index.html
+                    - text: – June 28, 2023
+                  - listitem [ref=e282]:
+                    - link "Snooping in Medical Records by Hospital Security Guards Leads to $240,000 HIPAA Settlement" [ref=e283] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/yakima-ra-cap/index.html
+                    - text: – June 15, 2023
+                  - listitem [ref=e284]:
+                    - link "HHS Office for Civil Rights Reaches Agreement with Health Care Provider in New Jersey That Disclosed Patient Information in Response to Negative Online Reviews" [ref=e285] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/manasa-ra-cap/index.html
+                    - text: – June 5, 2023
+                  - listitem [ref=e286]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Investigation with Arkansas Business Associate MedEvolve Following Unlawful Disclosure of Protected Health Information on an Unsecured Server for $350,000" [ref=e287] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/medevolve-ra-cap/index.html
+                    - text: – May 16, 2023
+                  - listitem [ref=e288]:
+                    - link "HHS Office for Civil Rights Enters Into $15,000 Settlement Resolving Potential HIPAA Violation Under the Right of Access Initiative" [ref=e289] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/mente-ra-cap/index.html
+                    - text: – May 8, 2023
+                  - listitem [ref=e290]:
+                    - link "HHS Office for Civil Rights Settles HIPAA Investigation with Arizona Hospital System Following Cybersecurity Hacking" [ref=e291] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/banner-health/index.html
+                    - text: "- February 2, 2023"
+                  - listitem [ref=e292]:
+                    - link "Lab Pays $16,500 Settlement to HHS, Resolving Potential HIPAA Violation over Medical Records Request" [ref=e293] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/life-hopes-ra-cap/index.html
+                    - text: "- January 3, 2023"
+                  - listitem [ref=e294]:
+                    - link "HHS Civil Rights Office Resolves HIPAA Right of Access Investigation with $20,000 Settlement" [ref=e295] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/health-specialists-ra-cap/index.html
+                    - text: "- December 15, 2022"
+                  - listitem [ref=e296]:
+                    - link "HHS Civil Rights Office Enters Settlement with Dental Practice Over Disclosures of Patients’ Protected Health Information" [ref=e297] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/new-vision-ra-cap/index.html
+                    - text: "- December 14, 2022"
+                  - listitem [ref=e298]:
+                    - link "OCR Settles Three Cases with Dental Practices for Patient Right of Access under HIPAA" [ref=e299] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/september-2022-right-of-access-initiative/index.html
+                    - text: "- September 20, 2022"
+                  - listitem [ref=e300]:
+                    - link "OCR Settles Case Concerning Improper Disposal of Protected Health Information" [ref=e301] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/nedlc-ra-cap/index.html
+                    - text: "- August 23, 2022"
+                    - list [ref=e302]:
+                      - listitem [ref=e303]:
+                        - link "Read OCR's FAQs concerning HIPAA and the disposal of protected health information , opens in a new tab" [ref=e305] [cursor=pointer]:
+                          - /url: /sites/default/files/disposalfaqs.pdf
+                          - text: Read OCR's FAQs concerning HIPAA and the disposal of protected health information
+                          - generic [ref=e306]: ", opens in a new tab"
+                  - listitem [ref=e307]:
+                    - link "Eleven Enforcement Actions Uphold Patients’ Rights Under HIPAA" [ref=e308] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/july-2022-hipaa-enforcement/index.html
+                    - text: "- July 15, 2022"
+                  - listitem [ref=e309]:
+                    - link "Oklahoma State University - Center for Health Services Pays $875,000 to Settle Hacking Breach" [ref=e310] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/osu/index.html
+                    - text: "- July 14, 2022"
+                  - listitem [ref=e311]:
+                    - link "Four HIPAA enforcement actions hold healthcare providers accountable with compliance" [ref=e312] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/march-2022-hipaa-enforcement/index.html
+                    - text: "- March 28, 2022"
+                  - listitem [ref=e313]:
+                    - link "Five enforcement actions hold healthcare providers accountable for HIPAA Right of Access" [ref=e314] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/2021-right-of-access-initiative/index.html
+                    - text: "- November 30, 2021"
+                  - listitem [ref=e315]:
+                    - link "OCR Resolves Twentieth Investigation in HIPAA Right of Access Initiative with $80,000 Settlement" [ref=e316] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/chmc/index.html
+                    - text: "- September 10, 2021"
+                  - listitem [ref=e317]:
+                    - link "OCR Settles Nineteenth Investigation in HIPAA Right of Access Initiative" [ref=e318] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/delc/index.html
+                    - text: "- June 2, 2021"
+                  - listitem [ref=e319]:
+                    - link "Clinical Laboratory Pays $25,000 to Settle Potential HIPAA Security Rule Violations" [ref=e320] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/peachstate/index.html
+                    - text: "- May 25, 2021"
+                  - listitem [ref=e321]:
+                    - link "OCR Settles Eighteenth Investigation in HIPAA Right of Access Initiative" [ref=e322] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/vps/index.html
+                    - text: "- March 26, 2021"
+                  - listitem [ref=e323]:
+                    - link "OCR Settles Seventeenth Investigation in HIPAA Right of Access Initiative" [ref=e324] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/arbour/index.html
+                    - text: "- March 24, 2021"
+                  - listitem [ref=e325]:
+                    - link "OCR Settles Sixteenth Investigation in HIPAA Right of Access Initiative" [ref=e326] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/sharp/index.html
+                    - text: "- February 12, 2021"
+                  - listitem [ref=e327]:
+                    - link "OCR Settles Fifteenth Investigation in HIPAA Right of Access Initiative" [ref=e328] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/renown/index.html
+                    - text: "- February 10, 2021"
+                  - listitem [ref=e329]:
+                    - link "Health Insurer Pays $5.1 Million to Settle Data Breach Affecting Over 9.3 Million People" [ref=e330] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/excellus/index.html
+                    - text: "- January 15, 2021"
+                  - listitem [ref=e331]:
+                    - link "OCR Settles Fourteenth Investigation in HIPAA Right of Access Initiative" [ref=e332] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/banner/index.html
+                    - text: "- January 12, 2021"
+                  - listitem [ref=e333]:
+                    - link "OCR Settles Thirteenth Investigation in HIPAA Right of Access Initiative" [ref=e334] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/elite-primary-care/index.html
+                    - text: "- December 22, 2020"
+                  - listitem [ref=e335]:
+                    - link "OCR Settles Twelfth Investigation in HIPAA Right of Access Initiative" [ref=e336] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/ucmc/index.html
+                    - text: "- November 19, 2020"
+                  - listitem [ref=e337]:
+                    - link "OCR Settles Eleventh Investigation in HIPAA Right of Access Initiative" [ref=e338] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/bhayani/index.html
+                    - text: "- November 12, 2020"
+                  - listitem [ref=e339]:
+                    - link "OCR Settles Tenth Investigation in HIPAA Right of Access Initiative" [ref=e340] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/riverside/index.html
+                    - text: "- November 6, 2020"
+                  - listitem [ref=e341]:
+                    - link "City Health Department failed to terminate former employee’s access to protected health information" [ref=e342] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/new-haven/index.html
+                    - text: "- October 30, 2020"
+                  - listitem [ref=e343]:
+                    - link "Aetna Pays $1,000,000 to Settle Three HIPAA Breaches" [ref=e344] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/aetna/index.html
+                    - text: "- October 28, 2020"
+                  - listitem [ref=e345]:
+                    - link "OCR Settles Ninth Investigation in HIPAA Right of Access Initiative" [ref=e346] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/nyspine/index.html
+                    - text: "- October 9, 2020"
+                  - listitem [ref=e347]:
+                    - link "OCR Settles Eighth Investigation in HIPAA Right of Access Initiative" [ref=e348] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/sjhmc/index.html
+                    - text: "- October 7, 2020"
+                  - listitem [ref=e349]:
+                    - link "Health Insurer Pays $6.85 Million to Settle Data Breach Affecting Over 10.4 Million People" [ref=e350] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/premera/index.html
+                    - text: "- September 25, 2020"
+                  - listitem [ref=e351]:
+                    - link "HIPAA Business Associate Pays $2.3 Million to Settle Breach Affecting Protected Health Information of Over 6 million Individual" [ref=e352] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/chspsc/index.html
+                    - text: "- September 23, 2020"
+                  - listitem [ref=e353]:
+                    - link "Orthopedic Clinic Pays $1.5 Million to Settle Systemic Noncompliance with HIPAA Rules" [ref=e354] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/athens-orthopedic/index.html
+                    - text: "- September 21, 2020"
+                  - listitem [ref=e355]:
+                    - link "OCR Settles Five More Investigations in HIPAA Right of Access Initiative" [ref=e356] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/right-of-access-initiative/index.html
+                    - text: "- September 15, 2020"
+                  - listitem [ref=e357]:
+                    - link "Lifespan Pays $1,040,000 to OCR to Settle Unencrypted Stolen Laptop Breach" [ref=e358] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/lifespan/index.html
+                    - text: "- July 27, 2020"
+                  - listitem [ref=e359]:
+                    - link "Small Health Care Provider Fails to Implement Multiple HIPAA Security Rule Requirements" [ref=e360] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/metro/index.html
+                    - text: – July 23, 2020
+                  - listitem [ref=e361]:
+                    - link "Health Care Provider Pays $100,000 Settlement to OCR for Failing to Implement HIPAA Security Rule Requirements" [ref=e362] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/porter/index.html
+                    - text: "- March 3, 2020"
+                  - listitem [ref=e363]:
+                    - link "Ambulance Company Pays $65,000 to Settle Allegations of Longstanding HIPAA Noncompliance" [ref=e364] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/westgeorgia/index.html
+                    - text: "- December 30, 2019"
+                  - listitem [ref=e365]:
+                    - link "OCR Settles Second Case in HIPAA Right of Access Initiative" [ref=e366] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/korunda/index.html
+                    - text: "- December 12, 2019"
+                  - listitem [ref=e367]:
+                    - link "OCR Secures $2.175 Million HIPAA Settlement After Hospitals Failed to Properly Notify HHS of a Breach of Unsecured Protected Health Information" [ref=e368] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/sentara/index.html
+                    - text: "- November 26, 2019"
+                  - listitem [ref=e369]:
+                    - link "OCR Imposes a $1.6 Million Civil Money Penalty against Texas Health and Human Services Commission for HIPAA Violations" [ref=e370] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/txhhsc/index.html
+                    - text: "- November 7, 2019"
+                  - listitem [ref=e371]:
+                    - link "Failure to Encrypt Mobile Devices Leads to $3 Million HIPAA Settlement" [ref=e372] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/urmc/index.html
+                    - text: "- November 5, 2019"
+                  - listitem [ref=e373]:
+                    - link "OCR Imposes a $2.15 Million Civil Money Penalty against Jackson Health System for HIPAA Violations" [ref=e374] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/jackson/index.html
+                    - text: "- October 23, 2019"
+                  - listitem [ref=e375]:
+                    - link "Dental Practice Pays $10,000 to Settle Social Media Disclosures of Patients’ Protected Health Information" [ref=e376] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/elite/index.html
+                    - text: "- October 2, 2019"
+                  - listitem [ref=e377]:
+                    - link "OCR Settles First Case in HIPAA Right of Access Initiative" [ref=e378] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/bayfront/index.html
+                    - text: "- September 9, 2019"
+                  - listitem [ref=e379]:
+                    - link "Indiana Medical Records Service Pays $100,000 to Settle HIPAA Breach" [ref=e380] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/mie/index.html
+                    - text: "- May 23, 2019"
+                  - listitem [ref=e381]:
+                    - link "Tennessee Diagnostic Medical Imaging Services Company Pays $3,000,000 to Settle Breach Exposing Over 300,000 Patients' Protected Health Information" [ref=e382] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/tmi/index.html
+                    - text: "- May 6, 2019"
+                  - listitem [ref=e383]:
+                    - link "OCR Concludes 2018 with All-Time Record Year for HIPAA Enforcement" [ref=e384] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/2018enforcement/index.html
+                    - text: "- February7, 2019"
+                  - listitem [ref=e385]:
+                    - link "Cottage Health Settles Potential Violations of HIPAA Rules for $3 Million" [ref=e386] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/cottage/index.html
+                    - text: "- February 7, 2019"
+                  - listitem [ref=e387]:
+                    - link "Colorado hospital failed to terminate former employee’s access to electronic protected health information" [ref=e388] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/pagosasprings/index.html
+                    - text: "- December 11, 2018"
+                  - listitem [ref=e389]:
+                    - link "Florida contractor physicians' group shares protected health information with unknown vendor without a business associate agreement" [ref=e390] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/ach/index.html
+                    - text: "- December 4, 2018"
+                  - listitem [ref=e391]:
+                    - link "Allergy Practice pays $125,000 to settle doctor's disclosure of patient information to a reporter" [ref=e392] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/allergyassociates/index.html
+                    - text: "- November 26, 2018"
+                  - listitem [ref=e393]:
+                    - link "Anthem pays OCR $16 Million in record HIPAA settlement following largest health data breach in history" [ref=e394] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/anthem/index.html
+                    - text: – October 15, 2018
+                  - listitem [ref=e395]:
+                    - link "Unauthorized Disclosure of Patients’ Protected Health Information During ABC Documentary Filming Results in Multiple HIPAA Settlements Totaling $999,000" [ref=e396] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/bostoncases/index.html
+                    - text: – September 20, 2018
+                  - listitem [ref=e397]:
+                    - link "Judge rules in favor of OCR and requires a Texas cancer center to pay $4.3 million in penalties for HIPAA violations" [ref=e398] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/mdanderson/index.html
+                    - text: "- June 18, 2018"
+                  - listitem [ref=e399]:
+                    - link "Consequences for HIPAA violations don’t stop when a business closes" [ref=e400] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/filefax/index.html
+                    - text: "- February 13, 2018"
+                  - listitem [ref=e401]:
+                    - link "Five breaches add up to millions in settlement costs for entity that failed to heed HIPAA’s risk analysis and risk management rules" [ref=e402] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/fmcna/index.html
+                    - text: "- February 1, 2018"
+                  - listitem [ref=e403]:
+                    - link "Failure to protect the health records of millions of people costs entity millions of dollars" [ref=e404] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/21CO/index.html
+                    - text: "- December 28, 2017"
+                  - listitem [ref=e405]:
+                    - link "Careless handling of HIV information jeopardizes patient’s privacy, costs entity $387k" [ref=e406] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/stlukes/index.html
+                    - text: "- May 23, 2017"
+                  - listitem [ref=e407]:
+                    - link "Texas health system settles potential HIPAA violations for disclosing patient information" [ref=e408] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/MHHS/index.html
+                    - text: "- May 10, 2017"
+                  - listitem [ref=e409]:
+                    - link "$2.5 million settlement shows that not understanding HIPAA requirements creates risk" [ref=e410] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/cardionet/index.html
+                    - text: "- April 24, 2017"
+                  - listitem [ref=e411]:
+                    - link "No Business Associate Agreement? $31K Mistake" [ref=e412] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/ccdh/index.html
+                    - text: "- April 20, 2017"
+                  - listitem [ref=e413]:
+                    - link "Overlooking risks leads to breach, $400,000 settlement" [ref=e414] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/MCPN.html
+                    - text: "- April 12, 2017"
+                  - listitem [ref=e415]:
+                    - link "$5.5 million HIPAA settlement shines light on the importance of audit controls" [ref=e416] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/memorial/index.html
+                    - text: "- February 16, 2017"
+                  - listitem [ref=e417]:
+                    - link "Lack of timely action risks security and costs money" [ref=e418] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/childrens/index.html
+                    - text: "- February 1, 2017"
+                  - listitem [ref=e419]:
+                    - link "HIPAA settlement demonstrates importance of implementing safeguards for ePHI" [ref=e420] [cursor=pointer]:
+                      - /url: /about/news/2017/01/18/hipaa-settlement-demonstrates-importance-implementing-safeguards-ephi.html
+                    - text: "- January 18, 2017"
+                  - listitem [ref=e421]:
+                    - link "First HIPAA enforcement action for lack of timely breach notification settles for $475,000" [ref=e422] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/presence/index.html
+                    - text: "- January 9, 2017"
+                  - listitem [ref=e423]:
+                    - link "UMass settles potential HIPAA violations following malware infection" [ref=e424] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/umass/index.html
+                    - text: "- November 22, 2016"
+                  - listitem [ref=e425]:
+                    - link "$2.14 million HIPAA settlement underscores importance of managing security risk" [ref=e426] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/sjh/index.html
+                    - text: "- October 17, 2016"
+                  - listitem [ref=e427]:
+                    - link "HIPAA settlement illustrates the importance of reviewing and updating, as necessary, business associate agreements" [ref=e428] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/wih/index.html
+                    - text: "- September 23, 2016"
+                  - listitem [ref=e429]:
+                    - link "Advocate Health Care Settles Potential HIPAA Penalties for $5.55 Million" [ref=e430] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/ahcn/index.html
+                    - text: "- August 4, 2016"
+                  - listitem [ref=e431]:
+                    - link "Multiple alleged HIPAA violations result in $2.75 million settlement with the University of Mississippi Medical Center (UMMC)" [ref=e432] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/UMMC/index.html
+                    - text: "- July 21, 2016"
+                  - listitem [ref=e433]:
+                    - link "Widespread HIPAA vulnerabilities result in $2.7 million settlement with Oregon Health & Science University" [ref=e434] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/ohsu/index.html
+                    - text: "- July 18, 2016"
+                  - listitem [ref=e435]:
+                    - link "Business Associate’s Failure to Safeguard Nursing Home Residents’ PHI Leads to $650,000 HIPAA Settlement" [ref=e436] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/catholic-health-care-services/index.html
+                    - text: "- June 29, 2016"
+                  - listitem [ref=e437]:
+                    - link "Unauthorized Filming for “NY Med” Results in $2.2 Million Settlement with New York Presbyterian Hospital" [ref=e438] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/new-york-presbyterian-hospital/index.html
+                    - text: "- April 21, 2016"
+                  - listitem [ref=e439]:
+                    - link "$750,000 settlement highlights the need for HIPAA business associate agreements" [ref=e440] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/raleigh-orthopaedic-clinic/index.html
+                  - listitem [ref=e441]:
+                    - link "Improper disclosure of research participants’ protected health information results in $3.9 million HIPAA settlement" [ref=e442] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/feinstein/index.html
+                    - text: "- March 17, 2016"
+                  - listitem [ref=e443]:
+                    - link "$1.55 million settlement underscores the importance of executing HIPAA business associate agreements" [ref=e444] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/north-memorial-health-care/index.html
+                    - text: "- March 16, 2016"
+                  - listitem [ref=e445]:
+                    - link "Physical therapy provider settles violations that it impermissibly disclosed patient information" [ref=e446] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/complete-pt/index.html
+                    - text: "- February 16, 2016"
+                  - listitem [ref=e447]:
+                    - link "Administrative Law Judge rules in favor of OCR enforcement, requiring Lincare, Inc. to pay $239,800" [ref=e448] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/lincare/index.html
+                    - text: "- February 3, 2016"
+                  - listitem [ref=e449]:
+                    - link "$750,000 HIPAA Settlement Underscores the Need for Organization Wide Risk Analysis" [ref=e450] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/university-of-washington-medicine/index.html
+                    - text: "- December 14, 2015"
+                  - listitem [ref=e451]:
+                    - link "Triple-S Management Corporation Settles HHS Charges by Agreeing to $3.5 Million HIPAA Settlement" [ref=e452] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/triple-s-management/index.html
+                    - text: "- November 30, 2015"
+                  - listitem [ref=e453]:
+                    - link "HIPAA Settlement Reinforces Lessons for Users of Medical Devices" [ref=e454] [cursor=pointer]:
+                      - /url: /hipaa/for-professionals/compliance-enforcement/agreements/lahey.html
+                    - text: "- November 24, 2015"
+                  - listitem [ref=e455]:
+                    - link "750,000 HIPAA Settlement Emphasizes the Importance of Risk Analysis and Device and Media Control Policies" [ref=e456] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/cancercare.html
+                    - text: "- August 31, 2015"
+                  - listitem [ref=e457]:
+                    - link "HIPAA Settlement Highlights Importance of Safeguards When Using Internet Applications" [ref=e458] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/SEMC/semc.html
+                    - text: "- June 10, 2015"
+                  - listitem [ref=e459]:
+                    - link "HIPAA Settlement Highlights the Continuing Importance of Secure Disposal of Paper Medical Records" [ref=e460] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/cornell/index.html
+                    - text: "- April 22, 2015"
+                  - listitem [ref=e461]:
+                    - link "HIPAA Settlement Underscores the Vulnerability of Unpatched and Unsupported Software" [ref=e462] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/acmhs/index.html
+                    - text: "- December 2, 2014"
+                  - listitem [ref=e463]:
+                    - link "$800,000 HIPAA Settlement in Medical Records Dumping Case" [ref=e464] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/parkview.html
+                    - text: "- June 23, 2014"
+                  - listitem [ref=e465]:
+                    - link "Data Breach Results in $4.8 Million HIPAA Settlements" [ref=e466] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/jointbreach-agreement.html
+                    - text: "- May 7, 2014"
+                  - listitem [ref=e467]:
+                    - link "Concentra Settles HIPAA Case for $1,725,220" [ref=e468] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/stolenlaptops-agreements.html
+                    - text: "- April 22, 2014"
+                  - listitem [ref=e469]:
+                    - link "QCA Settles HIPAA Case for $250,000" [ref=e470] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/stolenlaptops-agreements.html
+                    - text: "- April 22, 2014"
+                  - listitem [ref=e471]:
+                    - link "County Government Settles Potential HIPAA Violations" [ref=e472] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/skagit-agreement.html
+                    - text: "- March 7, 2014"
+                  - listitem [ref=e473]:
+                    - link "Resolution Agreement with Adult & Pediatric Dermatology, P.C. of Massachusetts" [ref=e474] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/apderm-agreement.html
+                    - text: "- December 20, 2013"
+                  - listitem [ref=e475]:
+                    - link "HHS Settles with Health Plan in Photocopier Breach Case" [ref=e476] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/affinity-agreement.html
+                    - text: "- August 14, 2013"
+                  - listitem [ref=e477]:
+                    - link "WellPoint Settles HIPAA Security Case for $1,700,000" [ref=e478] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/wellpoint-agreement.html
+                    - text: "- July 11, 2013"
+                  - listitem [ref=e479]:
+                    - link "Shasta Regional Medical Center Settles HIPAA Privacy Case for $275,000" [ref=e480] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/shasta-agreement.html
+                    - text: "- June 13, 2013"
+                  - listitem [ref=e481]:
+                    - link "Idaho State University Settles HIPAA Security Case for $400,000" [ref=e482] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/isu-agreement.html
+                    - text: "- May 21, 2013"
+                  - listitem [ref=e483]:
+                    - link "HHS announces first HIPAA breach settlement involving less than 500 patients" [ref=e484] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/honi-agreement.html
+                    - text: "- December 31, 2012"
+                  - listitem [ref=e485]:
+                    - link "Massachusetts Provider Settles HIPAA Case for $1.5 Million" [ref=e486] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/meei-agreement.html
+                    - text: "- September 17, 2012"
+                  - listitem [ref=e487]:
+                    - link "Alaska DHSS Settles HIPAA Security Case for $1,700,000" [ref=e488] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/alaska-agreement.html
+                    - text: "- June 26, 2012"
+                  - listitem [ref=e489]:
+                    - link "HHS Settles Case with Phoenix Cardiac Surgery for Lack of HIPAA Safeguards" [ref=e490] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/pcsurgery_agreement.html
+                    - text: "- April 13, 2012"
+                  - listitem [ref=e491]:
+                    - link "HHS settles HIPAA case with BCBST for $1.5 million" [ref=e492] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/bcbstagrmnt.html
+                    - text: "- March 13, 2012"
+                  - listitem [ref=e493]:
+                    - link "Resolution Agreement with the University of California at Los Angeles Health System" [ref=e494] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/uclaagreement.html
+                    - text: "- July 6, 2011"
+                  - listitem [ref=e495]:
+                    - link "Resolution Agreement with General Hospital Corp. & Massachusetts General Physicians Organization, Inc." [ref=e496] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/massgeneralra.html
+                    - text: "- February 14, 2011"
+                  - listitem [ref=e497]:
+                    - link "Civil Money Penalty issued to Cignet Health of Prince George's County, MD" [ref=e498] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/cignetcmp.html
+                    - text: "- February 4, 2011"
+                  - listitem [ref=e499]:
+                    - link "Resolution Agreement with Management Services Organization Washington, Inc." [ref=e500] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/msoresagr.html
+                    - text: "- December 13, 2010"
+                  - listitem [ref=e501]:
+                    - link "Resolution Agreement with Rite Aid Corporation" [ref=e502] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/riteaidresagr.html
+                    - text: "- July 27, 2010"
+                  - listitem [ref=e503]:
+                    - link "Resolution Agreement with CVS Pharmacy, Inc." [ref=e504] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/cvsresolutionagreement.html
+                    - text: "- January 16, 2009"
+                  - listitem [ref=e505]:
+                    - link "Resolution Agreement with Providence Health & Services" [ref=e506] [cursor=pointer]:
+                      - /url: /ocr/privacy/hipaa/enforcement/examples/providenceresolutionagreement.html
+                    - text: "- July 16, 2008"
+          - generic [ref=e516]:
+            - text: Content last reviewed
+            - time [ref=e517]: March 5, 2026
+    - contentinfo [ref=e518]:
+      - link [ref=e519] [cursor=pointer]:
+        - /url: "#top"
+        - img [ref=e520]
+        - generic [ref=e522]: Back to top
+      - generic "Social media links and sign up" [ref=e523]:
+        - generic [ref=e525]:
+          - generic [ref=e526]:
+            - img "Secretary Robert F. Kennedy Jr." [ref=e528]
+            - generic [ref=e529]:
+              - heading "Follow @SecKennedy" [level=2] [ref=e530]
+              - generic [ref=e531]:
+                - link "Visit the Facebook account of Secretary Kennedy" [ref=e533] [cursor=pointer]:
+                  - /url: https://www.facebook.com/SecKennedy
+                  - img [ref=e534]
+                - link "Visit the X account of Secretary Kennedy" [ref=e537] [cursor=pointer]:
+                  - /url: https://x.com/SecKennedy
+                  - img [ref=e538]
+                - link "Visit the Instagram account of Secretary Kennedy" [ref=e541] [cursor=pointer]:
+                  - /url: https://www.instagram.com/seckennedy/
+                  - img [ref=e542]
+                - link "Visit the Truth Social account of Secretary Kennedy" [ref=e545] [cursor=pointer]:
+                  - /url: https://truthsocial.com/@seckennedy
+                  - img [ref=e546]
+                - link "Visit the LinkedIn account of Secretary Kennedy" [ref=e549] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/showcase/secretarykennedy/
+                  - img [ref=e550]
+          - generic [ref=e552]:
+            - img "HHS icon" [ref=e554]
+            - generic [ref=e555]:
+              - heading "Follow @HHSGov" [level=2] [ref=e556]
+              - generic [ref=e557]:
+                - link "Visit the HHS Facebook account" [ref=e559] [cursor=pointer]:
+                  - /url: https://www.facebook.com/HHS
+                  - img [ref=e560]
+                - link "Visit the HHS X account" [ref=e563] [cursor=pointer]:
+                  - /url: https://x.com/hhsgov
+                  - img [ref=e564]
+                - link "Visit the HHS YouTube account" [ref=e567] [cursor=pointer]:
+                  - /url: https://www.youtube.com/user/USGOVHHS?sub_confirmation=1
+                  - img [ref=e568]
+                - link "Visit the HHS Instagram account" [ref=e571] [cursor=pointer]:
+                  - /url: https://www.instagram.com/hhsgov/
+                  - img [ref=e572]
+                - link "Visit the HHS LinkedIn account" [ref=e575] [cursor=pointer]:
+                  - /url: https://www.linkedin.com/company/hhsgov
+                  - img [ref=e576]
+          - generic [ref=e586]:
+            - heading "HHS Email updates" [level=3] [ref=e587]
+            - paragraph [ref=e588]: Receive email updates from HHS.
+            - paragraph [ref=e589]:
+              - link "Subscribe" [ref=e590] [cursor=pointer]:
+                - /url: https://cloud.connect.hhs.gov/subscriptioncenter
+      - contentinfo "Agency logo and contact information" [ref=e591]:
+        - generic [ref=e592]:
+          - link "HHS Logo" [ref=e596] [cursor=pointer]:
+            - /url: https://hhs.gov
+            - img "HHS Logo" [ref=e597]
+          - generic [ref=e598]:
+            - generic [ref=e600]:
+              - heading "HHS Headquarters" [level=3] [ref=e601]
+              - paragraph [ref=e605]:
+                - text: 200 Independence Avenue, S.W.
+                - text: Washington, D.C. 20201
+                - text: "Toll Free Call Center: 1-877-696-6775"
+            - navigation [ref=e607]:
+              - generic [ref=e608]:
+                - list [ref=e610]:
+                  - listitem [ref=e611]:
+                    - link "Contact HHS" [ref=e612] [cursor=pointer]:
+                      - /url: /about/contact-us/index.html
+                  - listitem [ref=e613]:
+                    - link "Careers" [ref=e614] [cursor=pointer]:
+                      - /url: https://www.hhs.gov/careers/
+                  - listitem [ref=e615]:
+                    - link "HHS FAQs" [ref=e616] [cursor=pointer]:
+                      - /url: /answers/index.html
+                  - listitem [ref=e617]:
+                    - link "Nondiscrimination Notice" [ref=e618] [cursor=pointer]:
+                      - /url: /civil-rights/for-individuals/nondiscrimination/index.html
+                - list [ref=e620]:
+                  - listitem [ref=e621]:
+                    - link "Press Room" [ref=e622] [cursor=pointer]:
+                      - /url: /press-room/index.html
+                  - listitem [ref=e623]:
+                    - link "HHS Archive" [ref=e624] [cursor=pointer]:
+                      - /url: /about/archive/index.html
+                  - listitem [ref=e625]:
+                    - link "Accessibility Statement" [ref=e626] [cursor=pointer]:
+                      - /url: /web/section-508/hhs-digital-accessibility-statement/index.html
+                - list [ref=e628]:
+                  - listitem [ref=e629]:
+                    - link "Budget/Performance" [ref=e630] [cursor=pointer]:
+                      - /url: /about/budget/index.html
+                  - listitem [ref=e631]:
+                    - link "Inspector General" [ref=e632] [cursor=pointer]:
+                      - /url: https://oig.hhs.gov/
+                  - listitem [ref=e633]:
+                    - link "Web Site Disclaimers" [ref=e634] [cursor=pointer]:
+                      - /url: /web/policies-and-standards/hhs-web-policies/disclaimer/index.html
+                  - listitem [ref=e635]:
+                    - link "EEO/No Fear Act" [ref=e636] [cursor=pointer]:
+                      - /url: /about/agencies/asa/eeo/no-fear-act/index.html
+                - list [ref=e638]:
+                  - listitem [ref=e639]:
+                    - link "FOIA" [ref=e640] [cursor=pointer]:
+                      - /url: /foia/index.html
+                  - listitem [ref=e641]:
+                    - link "The White House" [ref=e642] [cursor=pointer]:
+                      - /url: https://www.whitehouse.gov/
+                  - listitem [ref=e643]:
+                    - link "USA.gov" [ref=e644] [cursor=pointer]:
+                      - /url: https://www.usa.gov/
+                  - listitem [ref=e645]:
+                    - link "Vulnerability Disclosure Policy" [ref=e646] [cursor=pointer]:
+                      - /url: /vulnerability-disclosure-policy/index.html
+```

datasets/24-q-and-a.md

@@ -0,0 +1,510 @@
+Here is a compilation of real-world scenarios, common edge cases, and practical Q&A pairs specifically tailored to the daily operational challenges faced by healthcare staff. You can use these scenarios as foundational data to train your AI agent and build your knowledge base.
+
+### Category 1: Digital Communication (Texting & Emailing)
+
+**Q: Can I send emails or text messages to patients regarding their appointments or care?**
+**A:** Yes, but with strict technical safeguards. You must use HIPAA-compliant, encrypted platforms that maintain access controls and audit trails ``. Furthermore, you must obtain explicit, written patient consent detailing the risks of communication, especially if they agree to receive information over unencrypted channels ``. Always double-check recipient information before sending, as misdirected texts and emails are leading causes of reportable data breaches ``. 
+
+**Q: If a patient reaches out to me on a standard text messaging app, can I reply with their test results?**
+**A:** No. You should share only the absolute minimum necessary information to direct them to a secure, HIPAA-compliant patient portal to view sensitive topics like test results ``.
+
+### Category 2: Breakrooms, Hallways, and "Snooping"
+
+**Q: Can healthcare staff discuss a patient's condition in the breakroom or at the nursing station?**
+**A:** Staff are permitted to orally coordinate services at nursing stations or discuss conditions for treatment purposes, but they must apply the "minimum necessary" rule ``. However, discussing patient information in public or insecure settings where unauthorized people can overhear—such as cafeterias, elevators, or waiting rooms—is a HIPAA violation ``. 
+
+**Q: I saw a celebrity or an old friend was admitted to our hospital. Can I check their medical chart just to see how they are doing?**
+**A:** No. Accessing patient files without authorization—often called "snooping"—is one of the most common HIPAA violations resulting in termination ``. You may only access a patient's chart if it is required for your specific job duties regarding their treatment, payment, or healthcare operations ``.
+
+**Q: Can I discuss a patient with another nurse if we don't say the patient's name?**
+**A:** Stripping the name is not always enough. If the nature of the discussion is not for a permissible clinical reason, and you disclose any unique clinical details (such as a rare condition, procedure date, or age) that could be used by the listener to identify the individual, it is a HIPAA violation ``.
+
+### Category 3: Family, Friends, and Employers
+
+**Q: If a patient's employer calls to verify their medical status or ask about their sick leave, can I provide that information?**
+**A:** No. A healthcare provider cannot give an employer any medical information without the patient's explicit, written authorization, except in highly specific legal cases like workers' compensation claims or OSHA compliance ``. 
+
+**Q: Can I share medical updates with a patient's family members or friends who are in the room?**
+**A:** Yes, if the patient is present and does not object, or if you can reasonably infer from the circumstances that they do not object (e.g., the patient asked their friend to come into the treatment room) ``. However, you may only discuss the information that the specific person needs to know about the patient's current care or payment ``.
+
+### Category 4: Social Media & Testimonials
+
+**Q: A patient posted a highly positive testimonial about their treatment at our clinic on their public Facebook page. Can our clinic repost it on our website?**
+**A:** No. Even if a patient publicizes their own treatment, they have not waived their HIPAA rights ``. Providers cannot disclose Protected Health Information (PHI), which includes confirming the person is a patient by sharing their name or testimonial, without a valid, written HIPAA authorization signed in advance ``.
+
+**Q: Our nursing team wants to take a "unit selfie" to post on the hospital's social media. Is this allowed?**
+**A:** You must be extremely careful. Real-world breaches frequently occur when staff take innocent photos that accidentally capture a patient whiteboard, a computer screen, or medical paperwork in the background, making patients identifiable ``. 
+
+### Category 5: Minors and Guardianship
+
+**Q: Do parents automatically have access to their teenager's medical records?**
+**A:** In most cases, parents act as personal representatives and have access to their minor child's records ``. However, exceptions exist based on state laws. If a state law allows a minor to independently consent to specific services (such as reproductive health, STI/HIV testing, or substance use treatment), those specific records generally remain confidential to the teen, and parents cannot access them without the teen's authorization ``.
+
+**Q: Can a step-parent request medical records for a child?**
+**A:** A step-parent or unassigned caregiver asking for PHI without legal authority cannot be granted access ``. You must verify their identity and legal authority, or obtain the legal parent/guardian's authorization before sharing health information ``.
+
+### Category 6: Emergencies and Law Enforcement
+
+**Q: Can I share patient information with the police if they ask for it?**
+**A:** Yes, but only under specific exceptions. You can share information to comply with a court order or warrant, to report a crime that occurred on the clinic's premises, or to answer a request to locate a suspect, fugitive, or missing person ``. 
+
+**Q: Are HIPAA rules suspended during a declared natural disaster, like a hurricane or flood?**
+**A:** No, it is a common misconception that HIPAA is suspended during natural disasters ``. However, during declared public health emergencies, the HHS may issue "1135 waivers." These waivers temporarily lift certain penalties for hospitals that have instituted disaster protocols, but they are very narrow in scope and typically only remain in place for 72 hours after the disaster protocol is deployed ``.
+
+W
+
+**General HIPAA Knowledge**
+*   **What is HIPAA?** Enacted in 1996, the Health Insurance Portability and Accountability Act is a federal law that provides data privacy and security provisions to safeguard protected health information (PHI).
+*   **Who must comply with HIPAA?** "Covered entities" (healthcare providers, health plans, and healthcare clearinghouses) and their "business associates".
+*   **What are the basic rules of HIPAA?** The law relies on two main pillars: the Privacy Rule, which addresses the use and disclosure of individuals' health information, and the Security Rule, which sets national standards for protecting electronic PHI (ePHI).[1]
+*   **When does HIPAA not apply?** It only applies to businesses involved in healthcare treatment, payment, or operations and their contracted vendors. If an entity does not fit these categories, HIPAA does not govern their data.
+*   **Are HIPAA laws different in each state?** HIPAA is a federal baseline, but states can have overlapping laws regarding health data privacy that may be more stringent.
+
+**Protected Health Information (PHI) & Patient Rights**
+*   **What is considered PHI?** PHI includes demographic data and information relating to a patient's physical/mental health, healthcare provision, or payment. It encompasses names, addresses, dates (birth, admission, discharge), phone and fax numbers, email addresses, Social Security Numbers, medical record numbers, account numbers, and biometric identifiers.
+*   **Is billing information protected under HIPAA?** Yes, billing information is considered PHI.
+*   **Do patients have the right to access their medical records?** Yes, the Privacy Rule gives patients the right to request and access their medical records from their healthcare provider.
+*   **Can a patient request that their PHI be changed?** Yes, patients can request amendments to their medical records if they believe there is an error.
+*   **Can individuals request that a covered entity restrict the disclosure of their PHI?** Yes, individuals have the right to request restrictions on how their data is shared.
+*   **Does the covered entity have to accept all restriction requests?** No, exceptions apply, and entities are not legally forced to accept every request without exception.
+*   **Does the family medical history of deceased members lose protection after 50 years?** Yes, the HIPAA Privacy Rule protects a decedent's health information for exactly 50 years following their death.[2]
+
+**Everyday Clinical & Administrative Scenarios**
+*   **Can I call out a patient's name in the reception area?** Yes, calling out a name is generally considered an allowable "incidental disclosure".
+*   **Do sign-in sheets at the front desk protect us from HIPAA violations?** While sign-in sheets are permitted, using them does not inherently protect a practice from other HIPAA violations.
+*   **Is faxing PHI to another physician allowed?** Yes, faxing personal health information to another physician for treatment purposes is permitted under HIPAA.
+*   **If a patient's family calls to ask about their condition, do they have to give proof of identity?** Providers must verify identity if their internal policies require it, but they can legally share information if the patient does not object or if it is deemed in the patient's best interest.[2]
+*   **Can someone else pick up a patient's prescription drugs?** Yes, a provider or pharmacy can allow another person to pick up prescriptions, medical supplies, or X-rays.[2]
+*   **Can a family member violate HIPAA?** Technically, no. A family member is not bound by HIPAA, but a *healthcare provider* can violate HIPAA by disclosing PHI to a family member without proper patient authorization.
+*   **Can a covered entity discuss health information with an interpreter?** Yes, the Privacy Rule permits this to facilitate care.[2]
+*   **Can I talk about my patients outside of work if I don't use their names?** Even without names, sharing stories or data that contain other identifying details (like specific dates, locations, or unique circumstances) is a HIPAA violation.
+*   **What should I do if I find an open recycling bin full of paper with patient names and phone numbers?** You should show it to a supervisor immediately to determine if the information needs to be properly shredded.
+*   **If my sister's friend is having surgery, can I check the hospital database to find her room?** No. Searching for a patient's name in the registration database when it is not required for your specific job duties is a strict HIPAA violation.
+
+**Business Associates & IT Security**
+*   **Who is a Business Associate (BA)?** A BA is an outside person or vendor that needs access to, or stores, electronic PHI to provide services to a covered entity (e.g., IT providers, billing companies, transcription services).
+*   **Do I need a Business Associate Agreement with our cleaning company?** Generally, no; cleaning companies are not usually considered Business Associates because accessing PHI is not a regular part of their services.
+*   **Is a financial institution processing our payments a Business Associate?** No, financial institutions are exempt from being Business Associates if their only service to you is payment processing.
+*   **Are business associates required to complete a Security Risk Analysis (SRA)?** Yes, since 2009, BAs must complete an SRA and maintain a formal compliance program just like covered entities.
+*   **Do encrypted computers ensure HIPAA compliance?** No. While encryption is a crucial technical safeguard, true compliance also requires administrative risk analysis, physical policies, and staff training.
+*   **Is ransomware considered a reportable breach?** Yes, it is very possible that a ransomware attack is a reportable breach, requiring a thorough investigation of the facts to confirm the extent of the exposure.
+*   **What happens to a person who knowingly violates patient privacy for personal gain?** They can face disciplinary action, loss of access privileges, massive fines, and imprisonment.
+*   **Does the Privacy Rule require that every risk of an incidental disclosure be eliminated?** No, it requires reasonable and appropriate safeguards, not the impossible elimination of every conceivable risk.
+
+**Training & Compliance Management**
+*   **When can an organization officially say it is "HIPAA compliant"?** When it makes a "good faith" effort, which includes performing a recent Security Risk Analysis, implementing active risk management processes, signing BAAs, and completing employee training.
+*   **How often should staff members undergo HIPAA training?** Training must be completed at least annually, and new staff should be trained as soon as possible before handling PHI.
+*   **How long should a practice keep training records?** Documentation of completed training (like certificates) must be saved for a minimum of six years.
+*   **Why is continuous monitoring important in HIPAA compliance?** It helps detect, report, and mitigate potential security threats before they escalate, ensuring systems adapt to evolving cyber threats and requirements.
+
+
+
+
+
+
+HIPAA Q&A (200 Items)
+🔹 Basics (1–25)
+What is HIPAA?
+A U.S. law protecting patient health information.
+What is PHI?
+Protected Health Information—identifiable health data.
+Who must follow HIPAA?
+Covered entities and business associates.
+What are covered entities?
+Providers, insurers, and clearinghouses.
+What is a business associate?
+A third party handling PHI for a covered entity.
+What is the Privacy Rule?
+Controls use/disclosure of PHI.
+What is the Security Rule?
+Protects electronic PHI (ePHI).
+What is ePHI?
+Electronic Protected Health Information.
+What is the Minimum Necessary Rule?
+Only access the least PHI needed.
+What is a HIPAA violation?
+Improper use/disclosure of PHI.
+What are HIPAA penalties?
+Fines and possible criminal charges.
+Can patients access their records?
+Yes.
+Do patients need to sign consent?
+Often, for certain disclosures.
+What is a Notice of Privacy Practices?
+Explains how PHI is used.
+Can PHI be shared for treatment?
+Yes.
+Can PHI be shared for billing?
+Yes.
+Can PHI be shared without consent?
+In certain cases (e.g., emergencies).
+What is de-identified data?
+Data with no identifiable info.
+Is HIPAA only for hospitals?
+No.
+Does HIPAA apply outside the U.S.?
+Generally no.
+What is an identifier?
+Info linking data to a person.
+Are names PHI?
+Yes, when tied to health info.
+Is age PHI?
+Sometimes.
+Is gender PHI?
+Yes if linked to health data.
+Who enforces HIPAA?
+HHS Office for Civil Rights (OCR).
+🔹 Doctors & Clinical Staff (26–75)
+Can doctors share PHI with other doctors?
+Yes, for treatment.
+Can doctors discuss patients in public?
+No.
+Can PHI be emailed?
+Yes, if secure.
+Can doctors text PHI?
+Only via secure systems.
+Can staff access family records?
+Only if authorized.
+Can you leave voicemails with PHI?
+Limited info only.
+Can PHI be discussed in elevators?
+No.
+Can charts be left unattended?
+No.
+Can staff look up celebrities?
+No, unless treating them.
+Can nurses share info with family?
+If permitted.
+What is incidental disclosure?
+Unavoidable minimal exposure.
+Can whiteboards show patient info?
+Limited, non-sensitive info.
+Can staff take photos of patients?
+Only with consent.
+Can you use personal phones?
+Only if compliant.
+What is role-based access?
+Access based on job role.
+Can interns access records?
+If necessary for duties.
+Can staff discuss cases for training?
+Yes, if de-identified.
+Can PHI be faxed?
+Yes, with safeguards.
+Can doctors access old records?
+Yes, if needed.
+Can staff access records out of curiosity?
+No.
+Can PHI be used in research?
+With approval.
+What is patient authorization?
+Permission to disclose PHI.
+Can staff post about patients online?
+No.
+Can PHI be printed?
+Yes, but must be secured.
+Can you dispose of PHI in trash?
+No, must shred.
+What is a breach?
+Unauthorized disclosure.
+Must breaches be reported?
+Yes.
+Can doctors talk to insurers?
+Yes, for payment.
+Can staff share login credentials?
+No.
+What is audit logging?
+Tracking system access.
+Can staff access their own records?
+Usually through proper channels.
+Can you discuss patients at home?
+No.
+Can you use patient cases in presentations?
+If de-identified.
+Can PHI be stored on USB?
+Only if encrypted.
+Can staff override access controls?
+No.
+Can records be accessed after patient death?
+Yes, with rules.
+Can you confirm patient presence?
+Yes, unless restricted.
+Can staff use social media about work?
+No PHI allowed.
+Can doctors share PHI with police?
+In limited cases.
+Can staff access ex-patient records?
+Only if needed.
+Can PHI be stored in cloud?
+Yes, if compliant.
+Can doctors discuss patients with students?
+Yes, if appropriate.
+Can PHI be used in case studies?
+If anonymized.
+Can staff copy records?
+Only as needed.
+Can PHI be verbally shared?
+Yes, appropriately.
+Can staff use shared computers?
+Yes, with logout.
+Can doctors access unrelated patient files?
+No.
+Can staff view records during downtime?
+Only necessary info.
+Can PHI be used in teaching rounds?
+Yes.
+Can staff ignore HIPAA training?
+No.
+🔹 Nurses & Support Staff (76–120)
+Can nurses share shift notes openly?
+No.
+Can aides access PHI?
+Only necessary info.
+Can nurses discuss patients at station?
+Quietly and appropriately.
+Can patient names be on doors?
+Limited info allowed.
+Can staff call patients by full name publicly?
+Use discretion.
+Can staff use personal email?
+No.
+Can nurses access records remotely?
+If secure.
+Can staff take notes home?
+No.
+Can nurses share info with coworkers?
+If necessary.
+Can PHI be left on printers?
+No.
+Can staff use shared passwords?
+No.
+Can nurses check family records?
+No.
+Can staff access VIP records?
+Only if assigned.
+Can staff read charts for learning?
+No unless involved.
+Can staff use speakerphone?
+With caution.
+Can staff discuss cases in cafeteria?
+No.
+Can nurses carry paper charts?
+Yes, securely.
+Can staff photograph records?
+No.
+Can staff disclose room numbers?
+Sometimes.
+Can staff confirm appointments?
+Yes.
+Can staff leave messages with family?
+Limited info only.
+Can nurses access lab results?
+Yes, if needed.
+Can staff reuse passwords?
+No.
+Can staff bypass login?
+No.
+Can staff share PHI accidentally?
+Still a breach.
+Must staff report breaches?
+Yes.
+Can nurses share shift updates electronically?
+Securely only.
+Can staff use WhatsApp?
+Not for PHI.
+Can nurses access archived data?
+If needed.
+Can staff access records during breaks?
+Only for work.
+Can nurses discuss cases in training?
+Yes, de-identified.
+Can staff send PHI via SMS?
+No.
+Can nurses share discharge info?
+Yes, appropriately.
+Can staff store PHI locally?
+Only securely.
+Can nurses talk to pharmacists?
+Yes.
+Can staff discuss patient death?
+Respect privacy.
+Can staff keep patient lists?
+Securely.
+Can nurses use tablets?
+If compliant.
+Can staff access ER records?
+If assigned.
+Can staff leave files unattended?
+No.
+Can nurses verify identity before sharing?
+Yes.
+Can staff use sticky notes with PHI?
+No.
+Can staff store PHI in lockers?
+Securely only.
+Can nurses print summaries?
+Yes, secure them.
+Can staff discuss cases in hallways?
+No.
+🔹 Insurance & Admin (121–160)
+Can insurers access PHI?
+Yes, for payment.
+Can claims include PHI?
+Yes.
+Can insurers share PHI?
+With limits.
+Can admin staff access all records?
+No, only necessary.
+Can billing staff view diagnoses?
+Yes, if needed.
+Can insurers deny access requests?
+Rarely.
+Can PHI be used for audits?
+Yes.
+Can admin email PHI?
+Securely.
+Can insurers sell PHI?
+No.
+Can PHI be used for marketing?
+With consent.
+Can insurers share with employers?
+Limited.
+Can admin staff discuss claims publicly?
+No.
+Can insurers request full records?
+Sometimes.
+Can admin store PHI on laptops?
+Encrypted only.
+Can insurers disclose PHI for fraud checks?
+Yes.
+Can billing errors expose PHI?
+Yes, breach risk.
+Can admin print invoices with PHI?
+Yes, secure them.
+Can insurers use PHI for research?
+With rules.
+Can admin access celebrity files?
+No.
+Can insurers share with other insurers?
+Limited.
+Can admin share PHI with vendors?
+With agreements.
+What is a BAA?
+Business Associate Agreement.
+Is a BAA required?
+Yes, for vendors handling PHI.
+Can insurers store data offshore?
+With compliance.
+Can admin use spreadsheets with PHI?
+Securely.
+Can insurers contact patients?
+Yes.
+Can admin verify identity?
+Yes.
+Can insurers use call recordings?
+With safeguards.
+Can admin forward emails with PHI?
+Securely.
+Can insurers disclose PHI to lawyers?
+Sometimes.
+Can admin access records after hours?
+If needed.
+Can insurers share PHI for underwriting?
+Restricted.
+Can admin use cloud storage?
+If compliant.
+Can insurers use PHI for analytics?
+De-identified preferred.
+Can admin send PHI via fax?
+Yes, secure.
+Can insurers share PHI internationally?
+Limited.
+Can admin archive PHI?
+Yes.
+Can insurers deny corrections?
+If justified.
+Can admin update records?
+Yes, authorized only.
+Can insurers track access logs?
+Yes.
+🔹 Security, Breaches & Compliance (161–200)
+What is a data breach?
+Unauthorized PHI exposure.
+Must breaches be reported to patients?
+Yes.
+Must breaches be reported to government?
+Yes.
+What is encryption?
+Data protection method.
+Is encryption required?
+Strongly recommended.
+What is access control?
+Restricting system access.
+What is authentication?
+Verifying identity.
+What is multi-factor authentication?
+Extra login security.
+What is phishing?
+Fraudulent data request.
+Can phishing cause breaches?
+Yes.
+What is ransomware?
+Malicious data lock.
+Are backups required?
+Yes.
+What is risk assessment?
+Evaluating vulnerabilities.
+How often train staff?
+Regularly.
+What is compliance audit?
+Review of HIPAA adherence.
+Can fines be large?
+Yes.
+Can employees be fired for violations?
+Yes.
+Can criminal charges occur?
+Yes.
+What is least privilege access?
+Minimal necessary access.
+What is a firewall?
+Network security barrier.
+What is antivirus?
+Malware protection.
+What is secure login timeout?
+Auto logout.
+What is audit trail?
+Record of access.
+What is incident response?
+Handling breaches.
+What is data integrity?
+Accuracy of data.
+What is secure disposal?
+Proper data destruction.
+What is shredding?
+Destroying paper PHI.
+What is device encryption?
+Securing hardware data.
+Can lost devices cause breaches?
+Yes.
+What is remote wipe?
+Erase lost device data.
+What is user training?
+Staff education.
+What is policy enforcement?
+Applying rules.
+What is compliance culture?
+Organization mindset.
+Can small clinics violate HIPAA?
+Yes.
+Are audits random?
+Sometimes.
+What is corrective action?
+Fixing violations.
+What is documentation?
+Record keeping.
+What is privacy officer?
+HIPAA compliance lead.
+What is security officer?
+IT security lead.
+Why is HIPAA important?
+Protects patient trust and data.

tmp/title-45-2026-04-24.xml

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bd9dbc429021a58d1db4a776a7b8f7aebc34b23180900be4c1c0d2afa4d022c
+size 14201519