Study guide
9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs)
NHA Certified Electronic Health Records Specialist CEHRS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About the NHA CEHRS Exam The CEHRS Test Plan & How to Use This Guide
2 Chapter 1: Foundations — Medical Terminology, Health Care Settings & the EHR
1.1 Medical Terminology I: Roots, Prefixes, Suffixes & Combining Forms 1.2 Medical Terminology II: Body Systems, Directional Terms & Clinical Abbreviations 1.3 Health Care Systems, Settings, Personnel & Credentials 1.4 Parts of the EHR & Core Functions of the Electronic Record 1.5 Regulatory Agencies, Professional Standards & Population Health Concepts
3 Chapter 2: Non-Clinical Operations — Patient Registration & Scheduling
2.1 Patient Registration & Intake Workflows 2.2 Master Patient Index (MPI) & Demographic Management 2.3 Appointment Scheduling & Resource Management 2.4 Patient Communication, Portals & Front-Office Operations 2.5 Encounter Documentation: Face Sheets, Labels, Armbands & Check-Out
4 Chapter 3: Non-Clinical Operations — Health Record Administration & Archiving
3.1 Health Record Types, Hybrid Systems & Data Conversion 3.2 Record Retention, Storage & Archival Policies 3.3 Release of Information (ROI) & Authorization Procedures 3.4 Auditing, Chart Maintenance & Record Integrity
5 Chapter 4: Non-Clinical Operations — Data Sources, Devices & EHR User Support
4.1 Retrieving Patient Data from Internal Databases (Provider, Payer & Financial) 4.2 Acquiring Patient Data from External Sources 4.3 Importing from Integrated Devices & Managing EHR Hardware Inventory 4.4 Identifying, Reporting & Reconciling Data Discrepancies 4.5 End-User EHR Training, Competency & Training Documentation 4.6 Communicating Software Updates, IT Troubleshooting & Escalation
6 Chapter 5: Clinical Operations — Clinical Intake, Point-of-Care & Vitals
5.1 Clinical Intake, Rooming & Vital Signs Documentation 5.2 Chief Complaint, History of Present Illness (HPI) & ROS 5.3 Physical Exam Documentation & Clinical Notes Formatting (SOAP) 5.4 Allergy Documentation, Adverse Reaction Logging & Safety Alerts 5.5 Problem Lists, Medical History & Immunization Tracking 5.6 Patient Education Materials in the EHR & Scope of Practice
7 Chapter 6: Clinical Operations — Templates, Documentation Review & Data Retrieval
6.1 Developing Clinical Templates for Data Capture 6.2 Reviewing Clinical Documentation for Completeness & Accuracy 6.3 Point-of-Care EHR Support & Telehealth Workflows 6.4 Navigating the EHR to Retrieve Requested Patient Data 6.5 Securely Transmitting & Exchanging Patient Data
8 Chapter 7: Clinical Operations — CPOE, Orders & Decision Support
7.1 Computerized Provider Order Entry (CPOE) Fundamentals 7.2 Laboratory & Diagnostic Test Order Entry and Results Tracking 7.3 Medication Reconciliation, e-Prescribing & Formulary Checks 7.4 Clinical Decision Support Systems (CDSS) & Practice Guidelines 7.5 Clinical Care Coordination, Referrals & Discharge Planning
9 Chapter 8: Revenue Cycle & Financial Management
8.1 Insurance Verification, Eligibility (EDI 270/271) & Prior Authorization 8.2 Superbills, Charge Capture & Encounter Form Management 8.3 Coding Fundamentals for EHR: ICD-10-CM, CPT & HCPCS Level II 8.4 Claim Submission (EDI 837), Remittance (EDI 835) & Revenue Cycle 8.5 Providing Estimated Patient Costs & Good Faith Estimates 8.6 Patient Statements, Payment Collection & Balance Reconciliation
10 Chapter 9: Regulatory Compliance, HIPAA & Security
9.1 HIPAA Privacy Rule & Protected Health Information (PHI) 9.2 Minimum Necessary Rule, Permitted Uses & Patient Rights 9.3 HIPAA Security Rule: Administrative, Physical & Technical Safeguards 9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs) 9.5 Information Blocking Rules, 21st Century Cures Act & Compliance Audits 9.6 Allocating & Verifying EHR Access Controls and Role-Based Privileges 9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation 9.8 Abbreviation Policies, Professional Standards & EHR Downtime Procedures
11 Chapter 10: Data Management, Reporting & Health IT Standards
10.1 Health IT Interoperability: HL7, FHIR & Health Information Exchanges (HIE) 10.2 Standardized & Ad Hoc Financial Reports 10.3 Standardized & Ad Hoc Clinical Reports 10.4 Verifying Report Accuracy & Avoiding Common Reporting Errors 10.5 Quality Reporting, MIPS, Promoting Interoperability & Clinical Dashboards 10.6 Data Abstraction, Quality Improvement Studies & EHR System Security Management
9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs)
Key Takeaways Explain This Topic AI
The HITECH Act of 2009 expanded HIPAA enforcement, increased statutory penalties, and applied direct liability to Business Associates.
A Business Associate Agreement (BAA) is legally required before a third-party vendor creates, receives, maintains, or transmits PHI for a Covered Entity.
A breach is defined as the unauthorized acquisition, access, use, or disclosure of unencrypted PHI compromising data security or privacy.
PHI rendered unusable, unreadable, or indecipherable through encryption meeting HHS guidance (NIST-based, such as AES-256) is exempt from breach notification under the Safe Harbor.
Breaches affecting 500 or more individuals require immediate reporting to HHS OCR, individual written notices within 60 days, and media announcements.
Last updated: August 2026
- HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs)
- The HITECH Act Framework
Enacted as part of the American Recovery and Reinvestment Act (ARRA) of 2009, the Health Information Technology for Economic and Clinical Health (HITECH) Act transformed healthcare IT regulation. HITECH accelerated nationwide EHR adoption through Meaningful Use incentives while expanding HIPAA enforcement authority, introducing tiered Civil Monetary Penalties, and establishing direct statutory compliance obligations for Business Associates (BAs) .
Business Associate Agreements (BAAs)
A Business Associate (BA) is an individual or entity—other than a workforce member—that creates, receives, maintains, or transmits Protected Health Information (PHI) on behalf of a covered entity for a regulated function or service.
Business Associates vs. Non-BAs
Entity Category Operational Examples BAA Requirement
Business Associates Cloud EHR software vendors, medical billing services, transcription contractors, IT security auditors, e-prescribing networks. YES — BAA mandatory prior to PHI exposure.
Subcontractors IT infrastructure vendors hired by a Business Associate to host or backup ePHI databases. YES — BA must execute a BAA with its subcontractor.
Conduits (Exempt) U.S. Postal Service (USPS), UPS, FedEx, internet service providers acting strictly as data conduits without routine access. NO — Transient conduit exemption applies.
Mandatory BAA Contractual Terms
Under HIPAA and HITECH, a Business Associate Agreement (BAA) must specify:
Permitted and required uses and disclosures of PHI by the Business Associate.
Mandates that the BA will not use or disclose PHI other than as permitted by contract or required by law.
Requirements to implement Administrative, Physical, and Technical Safeguards under the HIPAA Security Rule.
Mandatory reporting of security incidents and privacy breaches to the covered entity without unreasonable delay.
Assurances that any subcontractors agree to the exact same restrictions and safeguards.
Requirements to return or destroy all PHI upon contract termination.
Under HITECH, Business Associates face direct statutory liability and can be audited and fined directly by HHS OCR for HIPAA Security Rule non-compliance.
The Breach Notification Rule
The HITECH Act established the HIPAA Breach Notification Rule , requiring covered entities and business associates to issue formal notifications following a breach of unencrypted PHI.
Definition of a Breach
A breach is defined as the unauthorized acquisition, access, use, or disclosure of PHI under the Privacy Rule that compromises the security or privacy of the information.
Encryption Safe Harbor Provision
If PHI is rendered unusable, unreadable, or indecipherable to unauthorized persons using an encryption method consistent with HHS guidance — which points to NIST-validated processes such as AES-256 for data at rest — the exposure is exempt from breach notification requirements under the Safe Harbor . Two conditions matter: the encryption must meet that standard, and the decryption key must not have been compromised .
4-Factor Risk Assessment for Low Probability of Compromise
An unauthorized acquisition or disclosure of unencrypted PHI is presumed to be a breach unless the covered entity or business associate demonstrates through a documented risk assessment that there is a low probability the PHI has been compromised :
Nature and extent of PHI involved: Types of identifiers, clinical details, and likelihood of re-identification.
Unauthorized person who received or used the PHI: Whether the recipient is bound by HIPAA or confidentiality obligations.
Whether PHI was actually viewed or acquired: Forensic evaluation of system logs.
Extent of risk mitigation: Immediate remediation actions taken (e.g., obtaining a signed destruction affidavit).
Mandatory Breach Notification Protocols & Timelines
When an unencrypted PHI breach occurs, covered entities must execute strict notification workflows governed by statutory timelines:
Notification Recipient Breach Scope Statutory Notification Timeline Operational Notification Protocol
Affected Individuals All breaches (1+ individuals) Without unreasonable delay and no later than 60 calendar days after breach discovery. Written notification via first-class mail (or secure email if individual opted in). Details breach event, data involved, protective steps, and facility contact details.
HHS OCR (Small Breaches) Fewer than 500 individuals (< 500) Within 60 days of the end of the calendar year in which the breach occurred. Submitted electronically through the HHS OCR online breach reporting portal.
HHS OCR (Large Breaches) 500 or more individuals (500+) Without unreasonable delay and no later than 60 calendar days after breach discovery. Submitted electronically simultaneously with individual notices; listed publicly on the HHS OCR online reporting wall.
Prominent Media Outlets 500 or more residents of a state or jurisdiction Without unreasonable delay and no later than 60 calendar days after breach discovery. Formal press release issued to major media outlets in the affected jurisdiction detailing breach specifics.