本文へ移動
cccskills
無料GitHub で公開

hitech-act-privacy

Implements HITECH Act privacy and security requirements including breach notification expansion, four-tier penalty structure, state attorney general enforcement authority, EHR meaningful use privacy conditions, and business associate direct liability. Keywords: HITECH Act, breach notification, penalty tiers, state AG enforcement, meaningful use, EHR privacy.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md12.8 KB
  • assets/template.md1.8 KB
  • references/standards.md1.5 KB
  • references/workflows.md4.8 KB
  • scripts/process.py9.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

HITECH Act Privacy and Security Requirements

Overview

The Health Information Technology for Economic and Clinical Health (HITECH) Act was enacted as Title XIII of the American Recovery and Reinvestment Act of 2009 (Pub. L. 111-5). HITECH fundamentally transformed HIPAA enforcement by establishing breach notification requirements, creating a four-tier penalty structure with significantly increased penalties, granting enforcement authority to state attorneys general, extending HIPAA Security Rule requirements directly to business associates, and tying privacy and security compliance to the Electronic Health Record (EHR) meaningful use incentive program. The 2013 Omnibus Rule (78 FR 5566) implemented most HITECH provisions into the HIPAA regulatory framework.

Breach Notification — HITECH §13402

Establishment of Federal Healthcare Breach Notification

Prior to HITECH, HIPAA had no breach notification requirement. HITECH §13402 created the obligation for covered entities and business associates to notify individuals, HHS, and in some cases the media, following a breach of unsecured PHI.

Key provisions enacted by HITECH:

ProvisionHITECH SectionImplementation
Individual notification within 60 days§13402(a)Codified at 45 CFR §164.404
HHS notification for breaches of 500+ immediately; under 500 annually§13402(e)(1)-(3)Codified at 45 CFR §164.408
Media notification for 500+ in a state/jurisdiction§13402(e)(2)Codified at 45 CFR §164.406
State AG notification for 500+ in a state§13402(e)(3)45 CFR §164.408(c)
BA obligation to notify CE§13402(b)Codified at 45 CFR §164.410
Unsecured PHI definition and safe harbor for encryption/destruction§13402(h)HHS guidance at 74 FR 19006

Evolution of the Breach Standard

HITECH originally used a "harm standard" — notification was required only if there was a significant risk of financial, reputational, or other harm. The 2013 Omnibus Rule replaced this with the "low probability of compromise" standard under the four-factor risk assessment (§164.402(2)), which is more protective of individuals. Under this standard, an impermissible use or disclosure is presumed to be a breach unless the entity demonstrates low probability of compromise.

Penalty Structure — HITECH §13410

Four-Tier Civil Monetary Penalty Framework

HITECH §13410(d) replaced the single-tier HIPAA penalty structure with a graduated system based on culpability:

TierCulpability LevelPer Violation (2024 adjusted)Annual Cap (2024 adjusted)Correction Possible
ADid not know and would not have known by exercising reasonable diligence$137 – $68,928$2,067,813Must correct within 30 days
BReasonable cause (not willful neglect)$1,379 – $68,928$2,067,813Must correct within 30 days
CWillful neglect — timely corrected$13,785 – $68,928$2,067,813Corrected within 30 days of knowledge
DWillful neglect — not timely corrected$68,928 – $2,067,813$2,067,813Investigation/penalty mandatory

Penalty amounts are adjusted annually for inflation under the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015.

Criminal Penalties

HITECH preserved and enhanced criminal penalties under 42 USC §1320d-6:

TierConductMaximum Penalty
1Knowingly obtaining or disclosing PHIUp to $50,000 fine and 1 year imprisonment
2Offenses committed under false pretensesUp to $100,000 fine and 5 years imprisonment
3Offenses with intent to sell, transfer, or use for commercial advantage, personal gain, or malicious harmUp to $250,000 fine and 10 years imprisonment

Percentage of CMPs and Settlements to Affected Individuals — §13410(c)(2)

HITECH §13410(c)(2) directed HHS to establish methods for distributing a percentage of CMPs and settlement amounts to individuals harmed by HIPAA violations. HHS has not yet issued final regulations implementing this provision, but OCR has included equitable relief provisions in certain settlement agreements.

State Attorney General Enforcement — HITECH §13410(e)

Authority Granted

HITECH §13410(e) authorized state attorneys general to bring civil actions in federal district court on behalf of state residents who may have been affected by HIPAA violations. This was a significant expansion — previously only HHS/OCR could enforce HIPAA.

Requirements for State AG Actions

RequirementDetail
Prior notice to HHSState AG must provide notice to the Secretary of HHS before filing suit
HHS intervention rightHHS may intervene and assume primary responsibility for the action
No action during pending HHS actionState AG may not bring action during a pending HHS action against the same entity for the same violation
Remedies availableInjunctive relief, damages (up to $100 per violation, $25,000 per calendar year per identical violation), attorneys' fees

State AG Enforcement Precedents

StateYearEntityOutcome
Connecticut2010Health Net of Connecticut$250,000 settlement — first state AG action under HITECH; loss of unencrypted hard drive with PHI of 1.5 million individuals
Minnesota2011Accretive Health$2.5 million settlement — unauthorized access to PHI; failure to have BAA
Indiana2014WellPoint (Anthem)$1.9 million penalty — application vulnerability exposing ePHI of 612,402 individuals; state AG used HITECH authority alongside state law
New York2021EyeMed Vision Care$600,000 settlement — email phishing breach exposing PHI of 2.1 million; state AG cited HITECH and state consumer protection
New Jersey2019Virtua Medical Group$418,000 settlement — disclosure of PHI to vendor without BAA

Business Associate Direct Liability — HITECH §13401

Pre-HITECH vs Post-HITECH

AspectPre-HITECHPost-HITECH (§13401)
Security Rule complianceContractual obligation through BAA only; no direct regulatory liabilityBAs directly subject to Security Rule; enforceable by OCR and state AGs
Privacy RuleBAs bound only by BAA termsBAs directly liable for impermissible uses/disclosures; subject to minimum necessary
PenaltiesOnly covered entities subject to HIPAA penalties; BAs subject only to breach of contractBAs subject to same civil and criminal penalties as covered entities
SubcontractorsNo regulatory requirementsSubcontractors treated as BAs; must have BAAs in place

Impact on Asclepius Health Network

Asclepius Health Network manages 47 business associate relationships. Post-HITECH, each BA must:

  • Independently comply with all Security Rule administrative, physical, and technical safeguards
  • Report breaches to Asclepius within 5 business days per the BAA
  • Demonstrate compliance through annual security assessments
  • Flow down BAA requirements to their subcontractors

EHR Meaningful Use Privacy Conditions — HITECH §13401(b)

Privacy and Security as Prerequisites for Incentive Payments

HITECH created the Medicare and Medicaid EHR Incentive Programs (now known as Promoting Interoperability) with total payments exceeding $38 billion. Privacy and security compliance is a prerequisite for receiving incentive payments:

Meaningful Use StagePrivacy/Security Requirements
Stage 1 (2011-2013)Conduct or review a security risk analysis; implement security updates; correct identified security deficiencies
Stage 2 (2014-2016)All Stage 1 requirements plus: address encryption/security of data at rest; enable patient electronic access to health information
Stage 3 / Promoting Interoperability (2017+)Security risk analysis; patient electronic access; secure messaging; API access; ONC Health IT Certification privacy and security criteria

Privacy Requirements in Health IT Certification

ONC Health IT Certification Criteria (45 CFR Part 170) require certified EHR technology to support:

  • Authentication, access control, and authorization
  • Auditable events and tamper-resistance
  • Automatic access time-out
  • Emergency access
  • End-user device encryption
  • Integrity verification
  • Accounting of disclosures
  • Amendments to health information
  • Consent management (including segmentation for Part 2 and state-specific restrictions)

Asclepius Health Network uses ONC-certified Epic EHR and verifies that each software version maintains certification for privacy and security criteria. The Promoting Interoperability dashboard tracks privacy measure compliance for CMS attestation.

Accounting of Disclosures Expansion — HITECH §13405(c)

HITECH Expansion

HITECH §13405(c) expanded the right to an accounting of disclosures to include disclosures through an electronic health record for treatment, payment, and healthcare operations (previously excluded under HIPAA §164.528). The accounting period was set at 3 years (rather than HIPAA's 6 years) for EHR disclosures.

Status: HHS published a Notice of Proposed Rulemaking in 2011 (76 FR 31426) proposing an "access report" approach but withdrew the NPRM and has not issued a final rule. The HITECH provision is self-executing in the statute but implementation guidance remains pending.

Restrictions on Sale of PHI — HITECH §13405(d)

HITECH §13405(d) prohibits a covered entity or business associate from receiving direct or indirect remuneration in exchange for PHI without a valid authorization from the individual that states whether the PHI can be further exchanged for remuneration.

Exceptions

ExceptionDescription
Public healthDisclosures for public health activities under §164.512(b)
ResearchReasonable cost-based fee for preparing and transmitting PHI for research
Treatment and paymentNormal treatment and payment activities
Transfer of businessSale, transfer, merger of covered entity
BA servicesRemuneration is for services BA provides on behalf of CE
Individual requestIndividual requests own PHI
HHS-determined exceptionsOther purposes determined by HHS through regulation

Minimum Necessary Enhancement — HITECH §13405(b)

HITECH directed HHS to issue guidance making the minimum necessary standard more specific:

  • Until HHS issues guidance, the limited dataset standard (§164.514(e)) is the floor for minimum necessary when PHI is in electronic form and a limited dataset would accomplish the purpose
  • HHS has not issued the final rule, but the provision is self-executing to the extent described

Enforcement Milestones Under HITECH

YearActionSignificance
2009HITECH enactedFour-tier penalties, breach notification, BA liability, state AG enforcement
2010Interim Final Breach Notification RuleInitial implementation of breach notification with harm standard
2011First resolution agreement post-HITECH (Cignet Health, $4.3M)Demonstrated willingness to impose significant penalties
2013Omnibus RuleComprehensive implementation of HITECH provisions into HIPAA regulations
2016Advocate Medical Group ($5.55M)Largest fine at the time; multiple breaches involving unencrypted devices
2018Anthem ($16M)Largest HIPAA settlement; demonstrated HITECH penalty levels for major breaches
2020-2024Annual penalty adjustmentsInflation-adjusted penalties increasing annually

Integration Points

  • hipaa-breach-notify: HITECH created the breach notification framework implemented in the Breach Notification Rule
  • hipaa-privacy-rule: HITECH strengthened Privacy Rule provisions including restrictions on sale of PHI and minimum necessary
  • hipaa-security-rule: HITECH extended Security Rule directly to business associates
  • hipaa-baa-management: HITECH created BA direct liability and subcontractor requirements
  • hipaa-risk-analysis: Risk analysis is a prerequisite for EHR meaningful use/Promoting Interoperability attestation

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Preparing EU AI Act compliance documentation for high-risk AI systems. Covers Annex III classification, technical documentation under Art. 11, conformity assessment, risk management systems, and CE marking requirements. Keywords: EU AI Act, high-risk AI, Annex III, conformity assessment, CE marking.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements GDPR Art. 22 automated decision-making and AI Act Art. 14 human oversight requirements for AI systems. Covers identification of solely automated decisions, meaningful human intervention design, logic explanation mechanisms, and contestation procedures. Keywords: Art. 22, automated decision, human oversight, AI Act, profiling, contestation.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

mukul975 のスキルをすべて見る

このスキルの問題を報告する