Study guide
27.3 HIPAA Security, HITECH & Interoperability
FACHE Board of Governors Exam in Healthcare Management Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 About the FACHE Credential 1.2 Current Exam Facts 1.3 Eligibility, Application & Recertification
2 Healthcare Systems & Trends
2.1 Healthcare and Medical Terminology 2.2 Healthcare Trends 2.3 Continuum of Care Levels
3 Healthcare Organizations & Services
3.1 Levels of Service from a Business Perspective 3.2 Types of Healthcare Organizations 3.3 Ancillary and Support Services
4 Integration, Clinicians & Staff Perspectives
4.1 Integration, Competition & Partnerships 4.2 Clinician Roles and Qualifying Criteria 4.3 Staff Perspectives & Evidence-Based Management
5 Patient Perspective & Care Delivery
5.1 Patient vs Provider Perspective 5.2 Access, Quality, Cost & Community 5.3 Care Delivery Models and Access Points
6 Digital Health, Population Health & Prevention
6.1 Digital Health 6.2 Population Health Concepts 6.3 Social Determinants & Preventative Medicine
7 Management Planning & Organizational Systems
7.1 Implementation Planning 7.2 Emergency Preparedness & NIMS 7.3 Organizational Systems & Management Functions
8 Leadership, Teams & Change
8.1 Leadership and Communication Styles 8.2 Team-Building Techniques 8.3 Change Management & Organizational Development
9 Collaboration, DEIJ & Networks
9.1 Stakeholder Collaboration 9.2 DEIJ & Resource Allocation 9.3 Network Structures & Collective Bargaining
10 Financial Accounting & Budgeting
10.1 Financial Accounting and Ratios 10.2 Operating Budgets 10.3 Capital Budgeting
11 Reimbursement, Productivity & Controls
11.1 Reimbursement Methodologies 11.2 Productivity Measures 11.3 Financial Controls
12 Revenue, Business Cases & Capital Finance
12.1 Revenue Generation and Payer Mix 12.2 Business Cases & Financial Decision Impacts 12.3 Asset Management & Financing
13 Philanthropy, Supply Chain & Revenue Cycle
13.1 Philanthropy and Foundations 13.2 Supply Chain Management 13.3 Revenue Cycle
14 HR Laws, Recruitment & Staffing
14.1 HR Laws and Regulations 14.2 Recruitment and Retention 14.3 Staffing Methodologies
15 Performance, Engagement & Compensation
15.1 Performance Management Systems 15.2 Motivation, Development & Engagement 15.3 Compensation and Benefits
16 Workplace Safety, Conflict & Labor Relations
16.1 Employee Safety, Security & Health 16.2 Conflict, Grievances & Selection 16.3 Labor Relations & HR Decision Impacts
17 Job Design, Succession & Coaching
17.1 Job Design 17.2 Succession Planning, Mentorship & Coaching
18 Confidentiality, Compliance & Payment Rules
18.1 Confidentiality and Privacy Laws 18.2 Healthcare Compliance Laws 18.3 Medicare, Medicaid & Third-Party Payment Regulations
19 Accreditation, Patient Rights & Ownership Rules
19.1 Accreditation & Inspection Standards 19.2 Patients' Rights Laws 19.3 Nonprofit vs For-Profit Requirements
20 Regulatory Impacts, Labor Law & M&A
20.1 Regulatory Impact on Executive Decisions 20.2 Collective Bargaining Laws 20.3 Legal Implications of Mergers & Acquisitions
21 Benchmarking, Peer Review & Risk
21.1 Benchmarking & Best Practices 21.2 Medical Staff Peer Review 21.3 Risk Management Programs
22 Improvement Methods & Measurement
22.1 PDSA, Lean & Six Sigma 22.2 Clinical Performance Improvement & Pathways 22.3 Quality Measurement & HCAHPS
23 Utilization, Patient Safety & Quality Impacts
23.1 Utilization Review & Case Management 23.2 Patient Safety Tools 23.3 How Quality Impacts Operations
24 Strategic Planning, Business Planning & Contracts
24.1 Strategic Planning Process 24.2 Business Planning for Services 24.3 Business Contracts
25 Socioeconomic Context, Marketing & Media
25.1 Socioeconomic Environment 25.2 Marketing Principles 25.3 Media, Social Media & Community Relations
26 Negotiation & Business Decision Impacts
26.1 Contract Negotiation 26.2 Business Decision Impacts
27 Health IT Operations, Trends & Regulation
27.1 IT in Business Operations 27.2 Technology Trends & Clinical Applications 27.3 HIPAA Security, HITECH & Interoperability
28 Informatics, IT Impacts & Continuity
28.1 Health Informatics for Operational Decisions 28.2 IT Decision Impacts 28.3 Information Systems Continuity
29 IT Acquisition & Analytics
29.1 IT Selection, Acquisition & Maintenance 29.2 Healthcare Analytics & Clinical Informatics
30 ACHE Ethics, Patient Rights & Ethics Committees
30.1 ACHE Code of Ethics 30.2 Patients' Rights & Responsibilities 30.3 Ethics Committees
31 Diversity, Conflicts of Interest & Research Ethics
31.1 Cultural & Spiritual Diversity 31.2 Conflict of Interest 31.3 Unethical Actions & Human-Subject Research
32 Professional Norms, Ethical Culture & Diversity Statement
32.1 Professional Norms & Standards 32.2 Creating an Ethical Culture 32.3 ACHE Statement on Diversity
33 Governance Theory, Structure & Medical Staff
33.1 Governance Theory 33.2 Governance Structure & Operations 33.3 Medical Staff Structure
34 Board Accountability & Public Policy
34.1 Board Role, Accountability & Fiduciary Duty 34.2 Public Policy & Advocacy
27.3 HIPAA Security, HITECH & Interoperability
Key Takeaways Explain This Topic AI
The HIPAA Security Rule requires administrative, physical, and technical safeguards to protect electronic protected health information (ePHI); risk analysis and risk management are foundational executive duties.
HITECH strengthened HIPAA enforcement, breach notification expectations, business associate accountability, and incentives that accelerated EHR adoption and later interoperability policy.
Promoting Interoperability (and related CMS/ONC programs) ties certified EHR use, electronic exchange, and patient access to payment and public program participation expectations.
Interoperability depends on standards (e.g., HL7 FHIR, USCDI), information blocking rules, APIs, and governance—not portals alone or one-way fax culture.
FACHE leaders own security culture, BA agreements, incident response readiness, and exchange strategy as enterprise risk and strategy issues—not only compliance paperwork.
Last updated: August 2026
HIPAA Security, HITECH & Interoperability
Quick Answer: FACHE executives must understand HIPAA Security Rule safeguards for ePHI , how HITECH raised the stakes for breach, enforcement, and EHR adoption , and how promoting interoperability and information-blocking rules reshape exchange and patient access . Privacy statutes appear in the Laws domain; this section focuses on security, HITECH-era policy, and interoperability as technology leadership .
Healthcare Technology and Information Management items often present ransomware downtime, a cloud vendor gap, a stalled HIE connection, or a patient-access API failure. Strong answers treat these as governance and operations problems with legal overlays—not purely technical tickets for the CISO alone.
HIPAA Security Rule: Core Structure
The HIPAA Security Rule applies to covered entities and business associates that create, receive, maintain, or transmit electronic protected health information (ePHI) . It is flexible and scalable —organizations must implement reasonable and appropriate safeguards given size, complexity, and risk—but flexibility is not optional compliance.
Safeguards fall into three categories:
Category Intent Illustrative controls (examples)
Administrative Policies, workforce, risk management Risk analysis, security officer, workforce training, contingency planning, BA oversight, access management policies
Physical Facility and device protection Facility access controls, workstation security, device/media controls, secure disposal
Technical Technology-enforced protections Access control, audit controls, integrity protections, authentication, transmission security
Many specifications are required ; others are addressable —addressable does not mean ignorable. If an addressable specification is not implemented, the organization must document why it is not reasonable and appropriate and what equivalent alternative is used.
Risk Analysis and Risk Management (Executive Non-Negotiables)
OCR and industry practice treat risk analysis as foundational. Executives should ensure:
- Inventory of systems and data flows involving ePHI (including cloud, medical devices, backups, shadow IT)
- Threat and vulnerability assessment appropriate to the environment
- Likelihood and impact evaluation with documented results
- Risk management plan with owners, funding, and timelines
- Periodic updates when technology, vendors, or threats change (mergers, new EHR modules, telehealth scale-up)
A paper policy binder without a living risk analysis is a common failure mode after incidents. Boards should receive cybersecurity and privacy risk in language comparable to other enterprise risks—likelihood, impact, residual risk, and resource requests.
Contingency Planning and Clinical Continuity
Security Rule contingency expectations connect directly to care delivery: data backup, disaster recovery, emergency mode operation, and testing. Ransomware and extended downtime scenarios require downtime procedures clinicians can actually execute (paper order sets, result routing, medication safety checks) and restoration priorities that put life-safety systems first. Executives own the resourcing of drills, immutable backups, and decision rights during cyber events—including when to divert or limit services.
HITECH: Why It Still Matters for Leaders
The Health Information Technology for Economic and Clinical Health (HITECH) Act (2009) reshaped the health IT landscape in ways still relevant on the exam:
Breach notification — heightened expectations for assessing and notifying breaches of unsecured PHI; public and reputational consequences for large incidents
- Stronger enforcement — increased penalties and audit/enforcement posture under HIPAA
- Business associates — clearer direct accountability and contractual expectations for vendors handling PHI/ePHI
EHR adoption incentives — Meaningful Use programs that drove certified EHR adoption across hospitals and eligible professionals
Foundation for later interoperability policy — the shift from “adopt EHR” toward use, exchange, and patient access
For executives, HITECH’s lasting lesson is that health IT policy pairs carrots and sticks : incentives accelerate adoption, while breach and enforcement raise the cost of weak security and poor vendor oversight. Business associate agreements (BAAs) and vendor risk management are operational controls, not closing-checklist formalities.
From Meaningful Use to Promoting Interoperability
Federal programs evolved from Meaningful Use to Promoting Interoperability (PI) under CMS (with ONC certification and standards work in parallel). The strategic intent for leaders:
- Use certified electronic health record technology (CEHRT) where program participation requires it
- Exchange health information with other providers and public health where applicable
- Enable patient electronic access to their health information
- Report on measures that demonstrate active, not passive, use of health IT
Exact measure sets change over program years; FACHE-level mastery is the managerial purpose : payment and reputation increasingly assume that organizations can send, receive, find, and use electronic data and give patients electronic access. Failure modes include checkbox portal features patients cannot use, unidirectional “export” that never becomes care coordination, and public health reporting interfaces that break after upgrades.
Interoperability: Standards, Exchange, and Information Blocking
Interoperability is the ability of systems and organizations to exchange and use data cooperatively. Layers executives should distinguish:
Layer Examples Why leaders care
Transport / connectivity HIEs, Direct, nationwide networks, payer connections Referrals, transitions, ADT alerts
- Content standards C-CDA documents, USCDI data classes What travels and whether it is usable
- APIs / modern exchange HL7 FHIR APIs, apps Patient access, third-party apps, bulk data
Semantic consistency Coding (ICD, LOINC, SNOMED, RxNorm), identity matching Safe reuse without misinterpretation
Policy / governance Consent, minimum necessary, information blocking rules Legal and competitive behavior
21st Century Cures Act interoperability and information blocking provisions (as implemented through HHS/ONC rules) constrain practices that unreasonably interfere with access, exchange, or use of electronic health information (EHI). Exceptions exist and are technical; the executive takeaway is cultural: data hoarding as competitive strategy is legally and reputationally risky . Organizations should train HIM, IT, legal, and clinical leaders on how requests are handled, documented, and escalated.
Patient access via APIs and third-party apps expands empowerment and also identity, privacy, and support challenges. Leaders should clarify what the organization controls (its API and authorization) versus what third-party apps do with data after patient-directed transfer.
Security, Interoperability, and the Trade-Off Myth
A false dichotomy claims organizations must choose either security or sharing. Competent programs do both: strong authentication and audit enable trusted exchange; weak identity matching and uncontrolled interfaces create both security incidents and clinical risk. Zero-trust principles, least-privilege access, encryption in transit and at rest where appropriate, continuous monitoring, and vendor SOC/assurance reviews are enablers of safe interoperability.
Executive Program Elements
A practical executive checklist:
- Named security and privacy leadership with authority and board reporting lines
- Current enterprise risk analysis and funded remediation roadmap
- BA inventory, BAAs, and ongoing vendor risk reviews (especially cloud and clinical apps)
- Incident response plan with legal, communications, clinical operations, and cyber forensics
- Downtime and disaster recovery drills that include clinical leaders
- Interoperability strategy: HIE participation, ADT notifications, referral loops, API patient access
- Information blocking compliance process and documentation
- Workforce training beyond annual click-through—phishing drills, clean desk, device handling
Metrics: patch latency, MFA coverage, backup restore tests, exchange volumes/usability, patient access success rates, incident mean time to contain
Pitfalls
Confusing HIPAA Privacy Rule concepts with Security Rule technical safeguards (both matter; they are not identical)
- Treating BAAs as one-time legal documents without operational monitoring
- Believing “we have a portal” equals interoperability or Promoting Interoperability readiness
- Ignoring medical device and IoT networks as ePHI or clinical uptime risks
- Paying ransomware without a decision framework, legal counsel, and restoration plan
- Blocking exchange to protect market share without legal analysis and patient-centered rationale
- Underinvesting in identity management—wrong-patient errors and inappropriate access both rise
- Executive Decision Lens
When a cyber threat, vendor proposal, or exchange request lands on the executive desk, FACHE leaders ask: Where does ePHI flow, and who is accountable? Is our risk analysis current for this change? Do BA and security terms match the data sensitivity? How will clinicians work if systems fail? Does our interoperability stance improve care transitions and patient access within the law? Security, HITECH-era accountability, and promoting interoperability are not separate hobbies—they are one leadership system for trusted digital care .