Study guide

Recognizing and Reporting Privacy Violations

CCA Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation, Eligibility, and Exam Strategy

Official Sources, Credential Purpose, and Candidate Profile Eligibility and Recommended Preparation Exam Format, Scoring, Pass Rates, Fees, Retake, Refund, and Delivery Code-Book Rules After 2026-05-01 Navigation and Timing Strategy Under Current AHIMA Instructions 8-14 Week Study Plan

2 Code Books, Guidelines, and Coding Workflow

2026 Code-Book Readiness and Allowed-Resource Mindset Coding Workflow: Read, Abstract, Locate, Assign, Sequence, Validate Medical Terminology, Anatomy, and Pathophysiology Foundation Coding Conventions and Official Guideline Use Query and Documentation Clarification Boundary Error-Log Method for Coding Misses

3 Clinical Classification Systems: ICD-10-CM

ICD-10-CM Structure and Conventions Diagnosis Coding from Documentation Principal/First-Listed Diagnosis and Sequencing by Setting Laterality, Episode/Seventh Character, and Combination Codes Signs/Symptoms vs Confirmed Diagnoses Common Exam Traps and Documentation Support

4 CPT, HCPCS, E/M, Modifiers, and Physician Coding

CPT Structure and Category Logic HCPCS Level II Basics E/M Level Components: History, Exam, MDM, and Time Modifiers, Bundling, Unbundling, and NCCI Edits Physician and Outpatient Coding Scenarios Medical Necessity and Payer Guideline Awareness

5 Inpatient Coding, ICD-10-PCS, and Setting-Based Sequencing

Inpatient Guidelines and UHDDS Concepts ICD-10-PCS Root Operation Thinking Procedure Coding from Operative Documentation Setting-Based Sequencing Differences Abstracting from the Inpatient Record DRG Impact without Upcoding

6 Reimbursement Methodologies and Revenue Cycle

Revenue Cycle Overview for Coders DRG, APC, Fee Schedule, RBRVS, and Risk Adjustment Claim Forms, Charge Capture, and Financial Communication NCCI Edits, LCD/NCD, and Medical Necessity Denials Evaluation and Processing Ethical Payer and Physician Clarification Workflow

7 Health Records, Data Content, and Information Governance

Medical Record Components Quantitative and Qualitative Record Analysis Abstraction and Retrieval Workflows MPI and Patient Identity Data Standards, Vocabularies, and Coding Reports Provider Education on Health Data Standards

8 Compliance, Ethics, Audits, and Clinical Documentation Improvement

Documentation Support and Code Validation Ethical Coding and AHIMA Code-of-Ethics Mindset Physician Queries and CDI Boundaries Fee/Charge Ticket and Chargemaster Updates External Audits and Compliance Preparation Fraud/Abuse Risk and Unsafe Shortcut Patterns

9 Information Technologies, Encoders, CAC, and EHR Workflows

EHR Navigation Encoders, Groupers, and HIM Systems Practice Management Systems CAC Strengths and Validation Limits Data Quality, Interoperability, and Workflow Errors Technology-Related Exam Traps

10 Confidentiality, Privacy, Security, and Minimum Necessary

HIPAA and State Privacy Basics for Exam Scenarios Minimum Necessary Access Passcodes, Passwords, and Secure Work Environment Recognizing and Reporting Privacy Violations Staff Education on Confidentiality ROI and Disclosure Decision Boundaries

11 Integrated CCA Domain Review and Practice Strategy

Blueprint-Weighted Mixed Review Linking Clinical Classification to Reimbursement and Compliance High-Probability Distractors Timed 105-Question Simulation Strategy Codebook Speed Drills and Scenario Triage Final Weak-Domain Remediation

12 Exam Day, Results, Retakes, Recertification, and Career Next Steps

Final 30/14/7 Day Plan Pearson VUE Test-Center Checklist, IDs, Code Books, and ATT Results, Pass/Fail Scoring, and Certificate Availability Retake Timing, Fees, Refunds, and Complaint Rules AHIMA Recertification Over a 2-Year Cycle CCA to CCS, RHIT, and RHIA Career Path

Recognizing and Reporting Privacy Violations

Key Takeaways Explain This Topic AI

Privacy incidents include unauthorized access (snooping), misdirected disclosure, public discussion, lost or stolen devices, and improper disposal.

The best first action is usually to contain the exposure and report through facility policy without further investigating beyond your role.

Under the HIPAA Breach Notification Rule, an impermissible use or disclosure is presumed a breach unless a four-factor risk assessment shows low probability of compromise.

Frontline staff recognize and report incidents; the organization, not the coder, determines whether breach notification is required.

Last updated: June 2026

Recognize the incident types

A privacy violation can involve access, use, disclosure, storage, disposal, or conversation. High-yield examples for the CCA:

Snooping — opening a record (a coworker, celebrity, neighbor, or relative) without a job reason.

Misdirected disclosure — faxing or emailing PHI to the wrong number or address.

Public discussion — talking about an identifiable patient in a cafeteria, elevator, or social media post.

Lost or stolen ePHI — an unencrypted laptop, phone, or USB drive.

Improper disposal — patient labels or worksheets in regular trash.

The breach notification framework

The HIPAA Breach Notification Rule (45 CFR 164.400-414) presumes that any impermissible use or disclosure of unsecured PHI is a breach unless a four-factor risk assessment demonstrates a low probability that PHI was compromised. The four factors are: (1) the nature and extent of the PHI, including identifiers and likelihood of re-identification; (2) the unauthorized person who used or received it; (3) whether the PHI was actually acquired or viewed; and (4) the extent to which risk has been mitigated.

If a breach affects 500 or more individuals, HHS notice is required without unreasonable delay and no later than 60 days. Media notice applies only when the breach affects more than 500 residents of a state or jurisdiction; smaller breaches are logged and reported to HHS annually.

The coder does not perform this assessment alone. The exam answer is to recognize the incident, protect PHI, and report — the privacy/compliance team applies the framework.

Reporting logic

Stop or limit the exposure if it can be done safely.

Do not access more PHI to investigate unless assigned.

Report promptly through the approved channel (supervisor, HIM director, privacy officer, security officer, compliance hotline, or incident system).

Give factual details: what happened, whose information, when, where, and who was involved.

Follow instructions from privacy, security, HIM, or compliance staff.

Reject any answer that hides the event, warns a friend to delete evidence, confronts staff in public, or independently decides no report is needed. Even a near miss may warrant reporting so the organization can assess risk and improve safeguards. Sanctions for snooping are typically severe — up to termination — regardless of intent.

Notification timelines and exceptions

For a confirmed breach, affected individuals must be notified without unreasonable delay and no later than 60 days from discovery. Breaches affecting more than 500 residents of a state or jurisdiction also require media notification ; a breach affecting 500 or more individuals requires contemporaneous HHS notice; breaches under 500 are logged and reported to HHS within 60 days after the end of the calendar year.

The Breach Notification Rule recognizes narrow exceptions that are not breaches: (1) unintentional, good-faith access by a workforce member acting within scope, with no further use or disclosure; (2) inadvertent disclosure between two authorized persons at the same entity; and (3) a disclosure where the entity has a good-faith belief the recipient could not reasonably have retained the information. The exam may describe a fax instantly recalled or returned unopened, which can fall under these exceptions after assessment.

Secured vs. unsecured PHI

Notification obligations attach only to unsecured PHI — PHI not rendered unusable through encryption or destruction meeting HHS guidance. A lost laptop holding encrypted ePHI generally is not a reportable breach, which is why encryption is such a high-value control. This is a frequent CCA distinction: the same physical loss can be a breach or not depending on whether the data was secured.

Incident triage at a glance

Event First step Who decides breach?

  • Snooping in the EHR Stop, report, do not re-access Privacy/compliance
  • Misdirected fax Contain, request return, report Privacy/compliance
  • Lost encrypted laptop Report; likely 'secured' Privacy/compliance
  • Public hallway disclosure Move conversation, report Privacy/compliance

The coder's lane is narrow and reliable: recognize the event, contain it safely, report factually, and cooperate. Determining whether the four-factor assessment results in a breach, drafting notification letters, and notifying HHS belong to the privacy and compliance team, not to frontline coding staff.

Worked example

A coder accidentally emails a spreadsheet containing 40 patients' names, MRNs, and diagnosis codes to an external billing contact whose address auto-completed incorrectly. The data was not encrypted. What does the coder do, and what does the organization do? The coder's immediate steps are to stop sending anything further, attempt to recall the message, document exactly what was sent and to whom, and report to the privacy officer right away — not to quietly hope it goes unnoticed.

The organization then runs the four-factor assessment: the PHI included names, MRNs, and diagnoses (significant); the recipient is an outside party (raises risk); the data was likely received and viewable (acquired); and mitigation may include a recall, a confidentiality attestation, or confirmed deletion. Because the data was unsecured , this very likely qualifies as a reportable breach, and the 40 affected individuals must be notified within 60 days. The coder did everything right by recognizing, containing, and reporting; the privacy team owns the assessment and notifications.

Contrast this with the same file sent encrypted with a secure link — that PHI is 'secured,' and the loss may not be a reportable breach at all.