Study guide
2.2 HIPAA Security Rule, Safeguards & Breach Notification
NCRA Oncology Data Specialist ODS-C
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The ODS-C Exam, the Oncology Data Specialist Profession & Standard Setters
1.1 ODS Exam Structure, Timing, Scoring & 2026 Testing Windows 1.2 From CTR to ODS: The Credential, Eligibility Routes & the Registrar's Role 1.3 Standard-Setting Organizations & the Manuals They Publish
2 Chapter 2: Legal Framework, HIPAA & State Reporting Laws
2.1 HIPAA Privacy Rule & the Public Health Reporting Exception 2.2 HIPAA Security Rule, Safeguards & Breach Notification 2.3 State Mandatory Cancer Reporting Laws & Statutory Authority
3 Chapter 3: Confidentiality, Release of Information, Ethics & Credential Maintenance
3.1 Patient Confidentiality Protocols & Data Access Policies 3.2 Handling Subpoenas, Discovery & Registry Immunity Statutes 3.3 NCRA Code of Ethics & ODS Credential Maintenance
4 Chapter 4: Registry Organization, Staffing & Information Systems
4.1 Types of Cancer Registries, Their Functions & Registry Operating Protocols 4.2 Registry Staffing Formulas, Time Studies & Resource Allocation 4.3 Electronic Registry Systems, Security & Disaster Recovery Planning
5 Chapter 5: Cancer Committee, Cancer Conferences & Quality Improvement
5.1 The Cancer Committee: CoC Standards 2.1–2.4, the CLP & Annual Program Activities 5.2 Multidisciplinary Cancer Case Conferences (CoC Standard 2.5) 5.3 Quality Improvement Principles & CoC Chapter 7 (Standards 7.1–7.3)
6 Chapter 6: CoC Accreditation Standards, NCDB & Data Quality
6.1 CoC Accreditation: Standards Structure, Program Categories & Accreditation Awards 6.2 The National Cancer Database (NCDB), RCRS Submission & CoC Quality Measures 6.3 Quality Control Plans & Audit Techniques (CoC Standard 6.1)
7 Chapter 7: Surveillance Programs, NAACCR Standards, Epidemiology & Statistics
7.1 National Cancer Surveillance Programs: SEER & CDC NPCR 7.2 NAACCR Data Exchange Standards, XML Data Specifications & Registry Certification 7.3 Basic Cancer Epidemiology & Descriptive Statistics 7.4 Basic Statistics: Frequency Distributions, Central Tendency, Risk Ratios & Odds Ratios 7.5 Survival Analysis, Life Tables & Presentation of Registry Data
8 Chapter 8: Medical Terminology, Anatomy & Types of Cancer
8.1 Medical Terminology & Standard Abbreviations for Cancer Abstracting 8.2 Human Anatomy & Physiology for Registrars: Tissues, Organ Walls, Subsites & Lymphatic Drainage 8.3 Types & Characteristics of Cancer: Benign vs. Malignant, Tumor Families, Spread & Precursors
9 Chapter 9: Casefinding & Reportability
9.1 Principles of Casefinding & Facility Reference Dates 9.2 Casefinding Sources: Pathology, Cytology, Disease Index & Logs 9.3 Reportability: What CoC, SEER and NPCR Require, Including Non-Malignant CNS Tumors 9.4 Ambiguous Terminology: Reportable Terms, Cytology, Discrepancies & "References of Last Resort"
10 Chapter 10: Diagnostic Procedures, Pathology Reporting, Lab Methods & Prognostic Indicators
10.1 Diagnostic & Staging Procedures: Imaging, Endoscopy, Biopsy & How They Are Coded 10.2 Pathology Reporting, CAP Cancer Protocols & Electronic Pathology (CoC Standard 5.1) 10.3 Specialty Laboratory Testing Methods: IHC, FISH, PCR/RT-PCR, NGS, Flow Cytometry & Cytogenetics 10.4 Prognostic Indicators & Site-Specific Data Items (SSDIs): HPV, KRAS, HER2 and More
11 Chapter 11: Class of Case, Key Dates & Case Identifiers
11.1 Class of Case, Date of First Contact, Date of Diagnosis & Accession/Sequence Numbers 11.2 Analytic Classes of Case (00, 10–14, 20–22): Definitions & Decision Rules 11.3 Nonanalytic Classes of Case (30–49, 99) & Why Central Registries Need Them
12 Chapter 12: Follow-Up, Vital Status & Recurrence
12.1 Follow-Up Purpose, Active & Passive Methods, and Follow-Up Source Codes 12.2 CoC Standard 6.5 Follow-Up Rates: Windows, Exclusions & Calculations 12.3 Vital Status, Date of Last Contact, Cancer Status & Death Clearance 12.4 Recurrence: Type of First Recurrence [1880], Date of First Recurrence [1860] & Recurrence vs. New Primary
13 Chapter 13: Abstracting, ICD-O-3.2 Site & Histology Coding, and Grade
13.1 The Abstracting Process: Workflow, Source Documents, Timeliness & Text Documentation 13.2 ICD-O-3.2 Topography, Primary Site Rules & Laterality 13.3 ICD-O-3.2 Morphology: Histology, Behavior & the Solid Tumor Histology Rules 13.4 Grade: The Four Time-Specific Grade Items & Site-Specific Grade Tables
14 Chapter 14: Solid Tumor Rules & Hematopoietic Coding Rules
14.1 Solid Tumor Rules: Purpose, Site Groups, Navigation & Timing Principles 14.2 Solid Tumor Rules for Breast, Colon/Rectum & Lung: The Multiple Primary Rules in Order 14.3 Solid Tumor Rules for Head & Neck, Kidney, Urinary, CNS, Melanoma & Other Sites 14.4 Hematopoietic & Lymphoid Neoplasms: Heme Manual, Heme DB, Multiple Primary & Primary Site Rules
15 Chapter 15: Staging: AJCC TNM (8th Edition & Version 9 Lung) and Summary Stage 2018
15.1 AJCC TNM Principles: Categories, Prefixes, Suffixes, General Rules & Registry Items 15.2 AJCC Time Frames: Clinical, Pathological, Post-Therapy (yc, yp), Recurrence & Autopsy 15.3 Breast Staging (AJCC 8th Edition, Part XI): T, N, M, Anatomic & Prognostic Stage Groups 15.4 Lung Staging (AJCC Version 9, 2025+): T, N2a/N2b, M1c1/M1c2 & New Stage Groups 15.5 Male Genital & Urinary Tract Staging (AJCC 8th Parts XIII–XIV): Prostate, Testis, Kidney, Bladder, Renal Pelvis & Ureter 15.6 SEER Summary Stage 2018: Codes, Timing, General Rules & Site Examples
16 Chapter 16: First-Course Treatment Coding (STORE 2025) & EDITS
16.1 Treatment Types, First Course of Treatment & Evidence-Based Guidelines (NCCN) 16.2 Surgery Coding: Rx Summ–Surg 2023 [1291], Lymph Node Surgery [1292], Other Site [1294], Margins & Reason for No Surgery 16.3 Radiation, Systemic, Transplant, Other & Palliative Treatment Coding (STORE 2025) 16.4 NAACCR EDITS, Over-ride Flags & Data Validation
2.2 HIPAA Security Rule, Safeguards & Breach Notification
Key Takeaways Explain This Topic AI
The HIPAA Security Rule (45 CFR Part 164, Subpart C) establishes administrative, physical, and technical safeguards specifically protecting electronic Protected Health Information (ePHI).
Implementation specifications are categorized as either 'Required' (strictly mandatory) or 'Addressable' (must implement, implement an equivalent alternative, or formally justify non-implementation).
The HITECH Act establishes a statutory presumption that any unauthorized acquisition or disclosure of unencrypted PHI constitutes a breach unless a 4-factor risk assessment proves a low probability of compromise.
Encryption that meets the NIST-based HHS guidance makes PHI "secured," so loss or theft of properly encrypted data with an uncompromised key is not a reportable breach.
Breaches affecting 500 or more individuals require individual notifications within 60 calendar days, notification to major media outlets, and concurrent electronic notice to the HHS Secretary.
Last updated: September 2026
2.2 HIPAA Security Rule, Safeguards & Breach Notification
While the HIPAA Privacy Rule establishes broad protections for patient health data across all formats (paper, oral, and electronic), the HIPAA Security Rule , codified at 45 CFR Part 164, Subpart C (§§ 164.302–164.318) , focuses specifically on safeguarding electronic Protected Health Information (ePHI) . In the modern cancer registry, virtually 100% of casefinding, abstracting, electronic data linkage, and central registry transmission is conducted electronically. Consequently, oncology data specialists must understand the operational mechanics of the Security Rule, the distinction between required and addressable specifications, and the statutory mandates governing data breach investigation and reporting.
The CIA Triad & Statutory Purpose
Under 45 CFR § 164.306(a), covered entities and business associates must ensure three fundamental security principles known in information security as the CIA Triad :
Confidentiality : Ensuring that ePHI is not made available or disclosed to unauthorized persons or processes.
Integrity : Ensuring that ePHI has not been altered, corrupted, or destroyed in an unauthorized manner.
Availability : Ensuring that ePHI is accessible and usable upon demand by an authorized person (e.g., ensuring cancer registry databases are operational during clinical multidisciplinary conferences and emergency care).
Additionally, covered entities must protect against any reasonably anticipated threats or hazards to the security or integrity of ePHI, protect against reasonably anticipated unauthorized uses or disclosures, and ensure compliance by their workforce.
Required vs. Addressable Implementation Specifications
Within the Security Rule, standards are operationalized through Implementation Specifications . A critical concept tested on national credentialing examinations is the legal distinction between Required and Addressable specifications (45 CFR § 164.306(d)):
Required Specifications : The covered entity or business associate must implement the specification exactly as outlined in the regulation. Compliance is non-negotiable.
Addressable Specifications : The term "addressable" does NOT mean optional or voluntary. When confronted with an addressable specification, the covered entity must assess whether the specification is a reasonable and appropriate safeguard in its specific operating environment. The entity must then choose one of three actions:
- Implement the addressable specification as written;
- Implement one or more alternative security measures that achieve the same statutory purpose; or
If neither is reasonable and appropriate, formally document the rationale, risk assessment, and justification showing how the standard is otherwise met.
Failing to address an addressable specification or treating it as optional represents a direct federal regulatory violation.
The Tripartite Safeguard Framework
The Security Rule organizes all protective controls into three discrete categories: Administrative , Physical , and Technical Safeguards .
Safeguard Category Regulatory Citation Safeguard Standard Required vs. Addressable Specification
Administrative 45 CFR § 164.308 Security Management: Risk Analysis Required : Comprehensive assessment of potential vulnerabilities
Administrative 45 CFR § 164.308 Security Management: Risk Management Required : Measures to reduce risks to reasonable levels
Administrative 45 CFR § 164.308 Sanction Policy Required : Disciplinary consequences for workforce non-compliance
Administrative 45 CFR § 164.308 Information System Activity Review Required : Routine audit of logs, access reports, and tracking
Administrative 45 CFR § 164.308 Workforce Security Required standard with addressable specifications: authorization/supervision, workforce clearance, termination procedures
Administrative 45 CFR § 164.308 Security Awareness & Training Required standard with addressable specifications: security reminders, protection from malicious software, log-in monitoring, password management
Administrative 45 CFR § 164.308 Contingency Plan Required : data backup plan, disaster recovery plan, emergency mode operation plan; Addressable : testing and revision, applications and data criticality analysis
Physical 45 CFR § 164.310 Facility Access Controls Addressable : Contingency operations, access validation, facility security plan
Physical 45 CFR § 164.310 Workstation Use Required : Policies governing workstation functions and permissible environments
Physical 45 CFR § 164.310 Workstation Security Required : Physical safeguards (e.g., privacy screens, locked registry rooms)
Physical 45 CFR § 164.310 Device & Media Controls: Disposal Required : Permanent degaussing, cross-cut shredding, physical destruction
Physical 45 CFR § 164.310 Device & Media Controls: Re-use Required : Data sanitization before hardware reallocation
Physical 45 CFR § 164.310 Device & Media Controls: Tracking Addressable : Record of device movement and responsible custodian
Technical 45 CFR § 164.312 Unique User Identification Required : Assigning an individual name or number for tracking user identity
Technical 45 CFR § 164.312 Emergency Access Procedure Required : Documented break-glass protocol to obtain ePHI during crises
Technical 45 CFR § 164.312 Automatic Logoff Addressable : Terminating electronic sessions after a specified period of inactivity
Technical 45 CFR § 164.312 Encryption and Decryption Addressable : Algorithmic transformation of ePHI at rest and in transit
Technical 45 CFR § 164.312 Audit Controls Required : Hardware, software, and procedural activity recording and examination
Technical 45 CFR § 164.312 Integrity Controls Addressable : Electronic verification (e.g., checksums, hashes) against improper alteration
Technical 45 CFR § 164.312 Person or Entity Authentication Required : Procedures to verify that a person seeking access to ePHI is who they claim to be
Technical 45 CFR § 164.312 Transmission Security Addressable : Integrity controls and encryption for ePHI sent over electronic networks
Practical Cancer Registry Safeguards
In daily operations, oncology data specialists must adhere to rigorous safeguard practices:
Workstation Security : Registrars working on dual monitors reviewing pathology reports, imaging scans, and staging algorithms must ensure screens cannot be viewed by visitors, transport staff, or non-clinical personnel. Privacy filters and password-protected screen locks are common safeguards; the lock interval is set by each organization's risk analysis, not by the Security Rule.
Remote Abstracting Protocols : Remote or telecommuting registrars must access facility EHR and registry databases exclusively through encrypted Virtual Private Networks (VPN) with Multi-Factor Authentication (MFA) . Printing paper records at a home office is strictly prohibited; if printed, documents must be stored in locked file cabinets and disposed of via certified cross-cut shredding.
Audit Trails : Modern cancer registry database systems maintain automated audit logs capturing every user login, record creation, record edit, export, and deletion. Compliance teams routinely audit these logs to detect unauthorized access to medical records of public figures, hospital colleagues, or relatives (a practice known as "snooping"), which triggers immediate disciplinary termination under mandatory sanction policies.
The HITECH Act & Breach Notification Rule (45 CFR §§ 164.400–414)
Enacted as part of the American Recovery and Reinvestment Act of 2009, the Health Information Technology for Economic and Clinical Health (HITECH) Act dramatically expanded HIPAA enforcement, increased civil monetary penalties, extended direct liability to business associates, and created the Breach Notification Rule .
Definition of a Breach
A Breach is defined under 45 CFR § 164.402 as the unauthorized acquisition, access, use, or disclosure of protected health information in a manner not permitted under the HIPAA Privacy Rule which compromises the security or privacy of the protected health information.
The Statutory Presumption & The 4-Factor Risk Assessment
Under federal law, any unauthorized acquisition, access, use, or disclosure of unencrypted PHI is presumed to be a breach unless the covered entity or business associate demonstrates through a formal risk assessment that there is a low probability that the PHI has been compromised .
The covered entity must evaluate all four statutory factors:
The Nature and Extent of the PHI : Evaluates the types of identifiers and the likelihood of re-identification (e.g., does the exposed data contain patient names, Social Security numbers, clinical cancer stages, or detailed pathology text?).
The Unauthorized Person Who Used or Received the Data : Evaluates whether the unauthorized recipient is another covered entity bound by HIPAA (e.g., a misdirected fax sent to an affiliated oncologist's office) versus an unknown external entity or malicious attacker.
Whether the PHI Was Actually Acquired or Viewed : Forensic evaluation to determine if files were opened, copied, or accessed (e.g., forensic analysis of a recovered stolen laptop showing files were never opened or accessed).
The Extent to Which Risk Has Been Mitigated : Immediate corrective actions taken, such as obtaining a reliable, signed legal attestation of destruction from a trusted recipient or immediate remote device wiping.
The Encryption "Safe Harbor"
Under the HHS guidance issued under HITECH, PHI is secured (not "unsecured") when it is encrypted consistent with the NIST publications HHS cites (NIST SP 800-111 for data at rest and NIST standards such as SP 800-52 for data in motion) or when the media have been destroyed. Strong algorithms such as AES are typical examples.
The Safe Harbor Rule : If an encrypted laptop, thumb drive, or backup tape containing cancer registry files is lost or stolen, and the encryption key was not compromised, the event is NOT classified as a breach under federal law. No individual notifications, media notices, or reports to HHS OCR are required, because the data remained unreadable, unusable, and indecipherable to unauthorized individuals.
Breach Notification Requirements & Deadlines
If a breach of unsecured (unencrypted) PHI occurs, the covered entity must execute strict statutory notifications without unreasonable delay: BREACH DISCOVERY
- │
- ┌──────────────────────┴──────────────────────┐
- ▼ ▼
- Fewer than 500 Individuals 500 or More Individuals
- │ │
- ┌───────────┴───────────┐ ┌───────────┼───────────┐
- ▼ ▼ ▼ ▼ ▼
- Individual Notice HHS OCR Notice Individual Notice Media Notice HHS OCR Notice
- (Within 60 Days) (Annual Submission: (Within 60 Days) (Within 60 (Within 60 Days
- Within 60 Days of Days: 500+ Electronic via
- End of Cal. Yr.) Residents) OCR Portal)
- 1. Individual Notification (45 CFR § 164.404)
Timeline : Written notice must be provided without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.
Method : Written notification sent via first-class mail to the last known address of the individual, or secure email if the individual has formally consented to electronic notices.
Substitute Notice : If contact information for 10 or more individuals is insufficient or out-of-date, the entity must post a conspicuous notice on its website home page for at least 90 days or publish notice in major print/broadcast media, including a toll-free telephone number.
2. Media Notice (45 CFR § 164.406)
Threshold : Required when a breach of unsecured PHI affects 500 or more residents of a single State or jurisdiction .
Timeline : Without unreasonable delay and within 60 calendar days of discovery.
Method : Formal press release issued to prominent media outlets serving the state or jurisdiction.
3. Notice to the Secretary of HHS (45 CFR § 164.408)
Breaches Affecting 500 or More Individuals : The covered entity must notify the Secretary of HHS electronically via the OCR website concurrently with individual notifications (within 60 calendar days of discovery). These breaches are publicly posted on the federal HHS breach portal.
Breaches Affecting Fewer Than 500 Individuals : The covered entity must maintain an internal breach log and report all smaller breaches to HHS OCR electronically no later than 60 days following the end of the calendar year in which the breaches were discovered.
4. Business Associate Notification (45 CFR § 164.410)
A business associate that discovers a breach must notify the covered entity without unreasonable delay and in no case later than 60 calendar days (though standard BAA contracts routinely enforce a much shorter window, such as 24 to 72 hours).