Study guide

HIPAA and State Privacy Basics for Exam Scenarios

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

HIPAA and State Privacy Basics for Exam Scenarios

Key Takeaways Explain This Topic AI

HIPAA permits use and disclosure of PHI for treatment, payment, and health care operations (TPO) without patient authorization; most other purposes require a written authorization.

When a state law or a special federal rule (such as 42 CFR Part 2) is more protective than HIPAA, the stricter rule governs the workflow.

The 18 HIPAA identifiers (name, MRN, dates, addresses, account numbers, etc.) make information PHI when combined with health data held by a covered entity.

CCA scenarios reward protecting the information first and escalating to the privacy officer or HIM leader when the boundary is unclear.

Last updated: June 2026

HIPAA and the TPO framework

The Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Parts 160 and 164) sets the national floor for protecting protected health information (PHI) . PHI is individually identifiable health information created or held by a covered entity or business associate.

The rule lists 18 identifiers that, when tied to health data, make information PHI: name, geographic data smaller than a state, all date elements (birth, admission, discharge, death), phone/fax, email, Social Security number, medical record number (MRN) , account number, health-plan number, vehicle and device identifiers, URLs, IP addresses, biometric identifiers, full-face photos, and any other unique code.

The single most tested concept is treatment, payment, and health care operations (TPO) . HIPAA permits a covered entity to use and disclose PHI for TPO without patient authorization. Coding, billing, abstracting, claim support, and quality review all fall under payment and operations, so a coder may access records for assigned work. Disclosures outside TPO — to an attorney, an employer, a life insurer, marketing — generally require a signed authorization.

When stricter rules apply

HIPAA is a floor, not a ceiling. A more stringent state law or special federal rule controls when it gives the patient greater privacy or access. Common stricter categories include behavioral health, HIV/AIDS status, genetic information, minors' reproductive or sexual-health care, and substance use disorder (SUD) records under 42 CFR Part 2 . The 2024 Part 2 Final Rule implementing CARES Act changes (compliance required by February 16, 2026) allows one consent for future TPO uses and disclosures. HIPAA covered entities and business associates that receive records under that consent may redisclose them as HIPAA permits, while Part 2 retains protections such as restrictions on using or disclosing records in legal proceedings against the patient without consent or a court order.

Exam decision aid

  • Scenario clue Best CCA mindset
  • TPO task (code, bill, quality review) Use only the PHI needed; no authorization required
  • Family member or attorney asks for details Verify authorization or a permitted/required exception first
  • Staff discuss a patient in a public area Treat as a potential incident and report through policy
  • State law or 42 CFR Part 2 is stricter Follow the more stringent protection
  • Records de-identified (all 18 identifiers removed) No longer PHI; HIPAA restrictions do not apply

Privacy spans verbal, paper, and electronic information. A hallway conversation, a printer tray, a misrouted fax, an email, a coding worksheet, or a screenshot can all disclose PHI. The strongest exam answers protect the information first, limit disclosure to the minimum necessary, and route uncertainty to the privacy officer, HIM director, supervisor, or compliance line rather than guessing.

Covered entities, business associates, and patient rights

The CCA exam expects you to know who HIPAA regulates. A covered entity is a health plan, a health care clearinghouse, or a health care provider that transmits health information electronically (the hospital or clinic where the coder works). A business associate is an outside vendor that creates, receives, maintains, or transmits PHI on the covered entity's behalf — for example, an outsourced coding company, a release-of-information vendor, or a cloud EHR host. Business associates must sign a business associate agreement (BAA) and are directly liable under HIPAA.

A scenario describing a contractor handling PHI without a signed BAA is a compliance gap.

Patients hold enforceable rights that drive many scenario answers: the right to access and obtain a copy of their record (a provider must act within 30 days), the right to request an amendment , the right to an accounting of disclosures outside TPO, the right to request restrictions and confidential communications, and the right to receive the Notice of Privacy Practices (NPP) . When a question describes a patient asking for their own information, minimum necessary does not limit it and the access request process applies.

How the exam frames Domain 6

Domain 6, Confidentiality and Privacy, includes privacy, security, and confidentiality and is weighted 6-10% on the 105-question CCA exam. Questions are scenario-based: they describe a workplace event and ask for the best first action . The pattern that earns points is consistent — identify whether a permitted purpose (TPO, authorization, required disclosure) exists, protect the PHI, apply the stricter rule when one exists, and escalate uncertainty through policy. Watch for distractors that sound helpful but bypass the privacy officer, disclose from memory, or rely on personal judgment about whether a rule applies.

The penalties behind these rules are real: civil money penalties scale by culpability tier, and willful neglect can reach into the millions, while criminal violations for selling PHI carry prison time.

Worked example

A coder is assigned to finalize the codes on a surgical inpatient stay. While reviewing the operative report, the coder notices the patient is a coworker from another department. Nothing in the chart is needed beyond the operative and pathology documentation, and the coworker's status is obvious. What is the HIPAA-correct sequence? First, the coder confirms a legitimate purpose exists — the encounter is assigned for coding under payment, so accessing the needed documents is permitted. Second, the coder limits review to the documents that support code assignment, ignoring unrelated visits.

Third, the coder does not mention the coworker's admission to anyone, because the diagnosis and even the fact of admission are PHI. Finally, if the coder feels uncomfortable coding a known person, the right move is to ask the supervisor to reassign, not to abandon the task or discuss it. This single scenario touches permitted access, minimum necessary, confidentiality of verbal information, and escalation — the exact blend Domain 6 tests.