Free CCA Exam Flashcards

Foundational coding and health information work: interpreting records, assigning codes, applying reimbursement rules, recognizing compliance risks, and protecting health data.

The CCA exam has scored questions and unscored pretest questions mixed together. Because pretest items are not identified, answer every question as if it counts.

CCA uses a scaled passing score of 300. Do not treat that as a fixed raw percentage; use domain practice results and timed accuracy to judge readiness.

After an unsuccessful attempt, plan for a new application, a new fee, and at least a 30-day wait before the new application can be approved.

When exam facts or coding rules conflict, use the current AHIMA, Pearson VUE, official coding guideline, codebook, or payer source that controls the situation.

Use the alphabetic index to start a search, then verify the code, notes, exclusions, sequencing rules, and required characters in the tabular list or table.

Choose the most specific code supported by documentation and the classification. Do not add laterality, acuity, episode, or relationship details that are not documented.

The care setting changes the coding logic. Inpatient cases use principal-diagnosis and PCS concepts, while outpatient encounters often use first-listed diagnosis and CPT/HCPCS rules.

Coders assign codes from provider documentation and official rules. Clinical clues can support a query, but they do not let the coder diagnose for the provider.

For inpatient reporting, the principal diagnosis is the condition established after study as chiefly responsible for the admission.

For many outpatient encounters, report the diagnosis, condition, problem, or reason chiefly responsible for the service using outpatient coding rules.

A combination code captures linked concepts in one code, such as a condition with a manifestation or complication. Do not split the concepts unless instructions require more codes.

When instructions identify an underlying cause and a manifestation, sequence the cause first and the manifestation second unless a specific guideline says otherwise.

Inpatient discharge coding has specific rules for uncertain diagnoses. Outpatient coding generally does not report uncertain conditions as confirmed diagnoses.

A sequela is a residual effect after the acute phase has ended. Code the current residual condition and the appropriate sequela code when both are supported.

POA indicators show whether a condition was present when an inpatient admission began. They affect quality reporting, hospital-acquired condition review, and reimbursement integrity.

PCS codes use seven characters, with each character representing a defined axis such as section, body system, root operation, body part, approach, device, or qualifier.

The root operation describes the objective of the procedure. Choose it from what was actually done, not from a loose verb in the operative note.

Resection means all of a body part was removed. Excision means only a portion was removed. The distinction depends on extent, not incision size.

Approach describes how the body part was reached, such as open, percutaneous, percutaneous endoscopic, or through a natural or artificial opening.

A PCS device is material or an appliance that remains after the procedure. Instruments, scopes, and temporary supplies used during the procedure are not device values.

CPT is commonly used for professional and outpatient procedures and services. Code selection depends on section guidelines, descriptors, parenthetical notes, and documentation.

HCPCS Level II describes many supplies, drugs, durable medical equipment, ambulance services, and other items or services not fully captured by CPT.

Modifiers add reporting detail without changing the base code. They may identify laterality, distinct service, professional component, reduced service, or other payer-relevant circumstances.

Evaluation and management coding depends on the applicable CPT rules for the service type. Match the documented work to the allowed method rather than relying on habit.

A service can be technically coded correctly and still deny if the documented diagnosis, payer policy, or coverage rule does not support medical necessity.

Inpatient DRG assignment depends on principal diagnosis, significant secondary diagnoses, procedures, patient factors, discharge status, and complication or comorbidity logic.

APCs are outpatient prospective payment groupings. They use outpatient codes, edits, packaging, status indicators, and payer rules rather than inpatient DRG logic.

NCCI edits identify code pairs that are not normally reported together. A modifier is appropriate only when documentation supports a distinct, allowed service.

Local and national coverage determinations help decide whether a service is covered and what diagnosis or documentation support is needed for payment.

A denial review compares the claim, codes, coverage rule, documentation, edits, and payer response. The goal is to find the correct fix, not just rebill faster.

HCC work depends on complete, accurate, documented diagnoses that affect expected resource use. Unsupported or stale diagnoses should not be carried forward as current.

Bundling rules prevent separate payment for services considered part of a broader service. Unbundling is risky unless a rule and documentation support separate reporting.

Quantitative analysis checks whether required record parts are present, complete, signed, and dated according to facility policy and legal requirements.

Qualitative analysis reviews whether documentation is clear, consistent, clinically meaningful, and sufficient to support coding, care, billing, and reporting.

The master patient index links a patient to the correct health records across encounters. Duplicate or overlaid records can cause coding, billing, and safety errors.

Abstraction pulls relevant facts such as diagnoses, procedures, dates, provider statements, discharge status, POA indicators, and required reporting elements.

Before fulfilling a documentation request, verify patient identity, requester authority, requested date range, requested content, and any privacy restrictions.

Assign codes accurately and completely from documentation and rules. Reimbursement pressure does not justify unsupported coding, omitted codes, or exaggerated severity.

Query when documentation is conflicting, ambiguous, incomplete, clinically unsupported, or missing specificity needed for accurate code assignment.

A compliant query is clear, neutral, supported by relevant clinical indicators, and allows the provider to give an answer other than the one the coder expects.

Strong audit preparation preserves the record trail: code rationale, source rule, documentation support, query history, claim data, and any correction steps.

Chargemaster updates should connect codes, descriptions, prices, departments, payer edits, and documentation workflows so charges remain accurate and defensible.

Use or disclose only the protected health information needed for the assigned task, unless an exception applies. Access should match the work purpose.

Protect records by locking screens, using strong credentials, avoiding shared passwords, securing printed material, and discussing patient information only in appropriate settings.

If a privacy issue is suspected, follow policy, report through the correct channel, preserve facts, and avoid informal disclosure or cleanup that hides what happened.

Useful coded data should be accurate, complete, consistent, timely, and reliable. Weak data quality can affect reimbursement, reporting, research, and patient care.

Encoders help locate codes and rules, but the coder must still verify documentation, sequencing, edits, and final code selection.

CAC can suggest codes from documentation, but it can miss context, accept copied terms, or overselect codes. Validate every suggestion before reporting it.

Coding data reports can show productivity, denials, case mix, quality indicators, and error patterns. Review definitions before comparing teams, facilities, or time periods.