Study guide

Passcodes, Passwords, and Secure Work Environment

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

Passcodes, Passwords, and Secure Work Environment

Key Takeaways Explain This Topic AI

Unique user IDs and passwords are individual credentials under the HIPAA Security Rule and must never be shared.

The Security Rule organizes safeguards into administrative, physical, and technical categories.

Automatic logoff, encryption, audit controls, and access controls are technical safeguards that protect electronic PHI (ePHI).

Remote and hybrid coders must protect ePHI from household members, visitors, public Wi-Fi, and unsecured storage.

Last updated: June 2026

The Security Rule safeguard categories

The HIPAA Security Rule (45 CFR Part 164, Subpart C) protects electronic protected health information (ePHI) through three categories of safeguards. The CCA exam frequently asks you to classify a control into the correct bucket.

Administrative safeguards — policies, the security risk analysis, workforce training, sanction policy, role-based access management, contingency planning, and incident-response procedures.

Physical safeguards — facility access controls, locked rooms, workstation security and use policies, device and media controls, privacy screens, and secure disposal.

Technical safeguards — unique user identification , automatic logoff , encryption/decryption , audit controls (logs), access controls, and integrity/transmission security.

Safeguards are further labeled required or addressable . Addressable does not mean optional; it means the entity must implement it, an equivalent measure, or document why it is not reasonable. Encryption, for example, is addressable but expected in most settings.

Credentials and daily habits

A unique user ID ties every access to one person so audit logs are meaningful. Sharing a login, writing a password on a monitor, borrowing a coworker's credentials, or letting someone chart under another account destroys accountability and is a reportable violation. When an account is locked, the answer is always to contact IT or a supervisor for proper access recovery — never to share or reuse credentials.

A coder working from home or in a shared space still must protect ePHI: lock the screen, avoid public Wi-Fi without a VPN, keep paper and devices secured, and prevent shoulder-surfing by household members or visitors.

Common exam traps

  • Unsafe behavior Better answer Safeguard type
  • Share a password so work can continue Contact IT for proper individual access Technical/administrative
  • Leave the EHR open during lunch Lock or log off (automatic logoff backup) Technical
  • Discuss a case in an elevator Move to a private work area Administrative
  • Put paper PHI in regular trash Use approved confidential destruction Physical
  • Email ePHI unencrypted to a personal account Use approved secure messaging Technical

Security is not solely IT's job. CCA-level staff are expected to use only assigned access, protect devices and paper, report suspicious activity, and avoid workarounds that expose PHI.

Audit controls and accountability

Audit controls are a required technical safeguard: systems record hardware, software, and procedural activity in audit logs that show who accessed which record, when, and from where. Because shared credentials make these logs meaningless, the unique-user-ID standard underpins the entire accountability model. The exam often pairs these — a snooping investigation succeeds only because each login was unique. Coders should expect that their access is logged and routinely audited, and that periodic audits of high-profile or 'VIP' patients are a normal control, not a sign of distrust.

Encryption, transmission, and devices

Encryption renders ePHI unreadable to unauthorized people and is the key reason a lost device may not trigger a breach: under the Breach Notification Rule, properly encrypted PHI is considered secured and its loss is generally not a reportable breach. That is why emailing PHI must use secure (encrypted) messaging, why a personal email account is never acceptable, and why USB drives holding PHI must be encrypted or avoided. Transmission security and integrity controls protect data moving across networks from interception or alteration.

Workstation and device checklist

Lock or log off whenever stepping away; rely on automatic logoff as a backup.

Position screens away from public view; use privacy filters in open areas.

Never write passwords on monitors, desks, or under keyboards.

Use only encrypted, approved devices and secure messaging for ePHI.

Store and dispose of paper PHI using approved, locked, confidential methods.

For remote work, secure the home space, use a VPN, and prevent shoulder-surfing.

Sanctions and the contingency angle

The administrative-safeguards category includes a sanction policy — documented discipline for workforce members who violate security or privacy rules — and contingency planning (data backup, disaster recovery, and emergency-mode operations) so PHI remains available and protected during outages. CCA scenarios may ask what should happen after a deliberate password share or snooping incident; the answer references the sanction policy applied consistently, not an informal warning.

Security therefore runs on three legs together — administrative policies, physical protections, and technical controls — and a strong exam answer rarely relies on a single category alone.

Worked example

A remote coder finishes a shift at a kitchen table where family members come and go. The laptop is facility-issued and encrypted, but the coder leaves the EHR open to grab lunch and props a printed worksheet of patient names and diagnoses next to the keyboard. Which controls are at risk, and what should happen? The open EHR session exposes ePHI to anyone in the room, so the technical answer is to lock or log off, backed by automatic logoff. The printed worksheet is a physical-safeguard problem: it should be secured during use and destroyed through approved confidential disposal afterward, never left in view or in household trash.

The shared home space is an administrative concern addressed by the facility's remote-work policy, which typically requires a private workspace, a VPN, and no household access to PHI. Notice that no single control fixes this — the correct response combines technical (lock the screen), physical (secure and shred the paper), and administrative (follow the remote-work policy) measures, which is precisely how the Security Rule's three categories are designed to work together.