C-RHI common mistakes
C-RHI · Understand the traps and how to avoid them.
Treating the legal health record as identical to the complete chart in the EHR, so questions about what must be disclosed or retained get answered with 'everything in the system.'
Candidates study the EHR as a software tool rather than learning that the legal health record is a policy-defined subset designated by the organization, and that metadata, audit trails, and shadow files are usually outside it.
What to do instead
Before the exam, write out a one-page distinction between the designated legal record, the full EHR, and secondary/derived data. For every practice question mentioning disclosure or retention, first ask 'is this element part of the designated record set?' and reject answers that assume the whole database travels with the patient.
Applying the minimum retention period as if it were a single national number and ignoring the longer of federal, state, and payer requirements.
Retention rules are set largely at the state level and vary by record type (adult, minor, behavioral health, occupational), so candidates memorize one figure and misapply it across scenarios.
What to do instead
Build a comparison table with columns for federal Medicare conditions of participation, state statute, and payer contract, and drill the rule 'the longest applicable period governs.' Practice classifying record types before selecting a period.
Choosing an analytic method by the tool name rather than by the question being asked, such as using regression to describe a pattern or a bar chart to show correlation.
Exam items describe a business question and expect the candidate to map it to descriptive, diagnostic, predictive, or prescriptive analytics; candidates instead match on familiar vocabulary like 'predict' or 'trend.'
What to do instead
Practice restating each scenario as a question type first ('what happened,' 'why,' 'what will happen,' 'what should we do'), then select the method. Keep a short decision tree and apply it to at least twenty stems before test day.
Confusing data governance with data quality, answering 'improve accuracy' when the item is about stewardship, ownership, or policy authority.
Both domains use overlapping vocabulary, and candidates blur accountability structures with cleansing activities, so they pick the operationally appealing answer over the governance one.
What to do instead
Memorize the governance triad: who decides (policy and standards), who owns (data steward or owner accountability), and who executes (quality monitoring and correction). Sort each answer option into one of those three buckets before choosing.
Calculating revenue cycle indicators with the wrong denominator, for example dividing denials by total charges instead of by total claims or allowed amounts.
Candidates memorize formulas as strings without tracking what the numerator and denominator represent, and exam items deliberately supply several plausible numbers to punish that.
What to do instead
For each metric (clean claim rate, denial rate, days in accounts receivable, net collection rate, cost to collect), write the formula in words and state the unit of the denominator. Practice with items that include distractor figures and label each number's role before computing.
Treating a denial as a coding problem by default and proposing a code change, when the root cause is registration, eligibility, authorization, or timely filing.
Candidates over-weight the coding domain they know best and skip the front-end and mid-cycle causes that produce most denials.
What to do instead
Use a fixed triage sequence on every denial scenario: eligibility and registration, authorization, coding and medical necessity, then billing and timely filing. State which stage the evidence points to before selecting a corrective action, and practice items where the fix is process, not code.
Answering privacy questions from general principle instead of from the specific permission structure, such as assuming consent is always required for treatment disclosures or that authorization is needed for every use.
The HIPAA framework distinguishes uses and disclosures for treatment, payment, and operations from those requiring authorization, and adds permissions for psychotherapy notes, marketing, and fundraising; candidates flatten these into one rule.
What to do instead
Create a grid of disclosure purpose versus permission required versus patient rights that attach. Drill the exceptions (public health, research with waiver, oversight, serious threat) separately, and for each practice item name the category before evaluating the options.
Selecting an answer that solves the immediate compliance problem without addressing the accountability and reporting obligations that follow, such as breach notification timelines and documentation.
Candidates focus on the precipitating event and stop at containment, forgetting that exam items often test the downstream obligation, including who must be notified and when.
What to do instead
For every incident scenario, run a checklist: detect, contain, assess risk, notify internally, notify individuals and regulators within the required window, document, and remediate. Practice writing the full sequence rather than only the first step.
Confusing leadership and management behaviors, choosing a directive management action when the item calls for strategic leadership, or the reverse.
Textbook definitions overlap and candidates respond to the surface verb ('decide,' 'plan') rather than the underlying function of setting direction versus maintaining operations.
What to do instead
Anchor on the distinction: leadership sets vision, direction, and change; management allocates resources and maintains processes. Classify the scenario's time horizon (long-term direction versus near-term execution) before selecting, and practice items where both options sound reasonable.
Coding from a diagnosis statement alone without verifying documentation specificity, laterality, or combination-code requirements in the classification system.
Candidates transfer clinical familiarity into code selection and skip the formal steps of locating the term, reading the tabular guidance, and confirming conventions such as sequencing and excludes notes.
What to do instead
Practice a rigid routine: identify the main term, follow index entries and cross-references, verify in the tabular list, check conventions, then confirm documentation supports the specificity chosen. Query when documentation is ambiguous rather than defaulting to an unspecified code.
Reading a rate, ratio, or percentage as if it measured the same thing across different denominators, such as comparing a crude mortality rate between facilities with very different case mix.
Candidates apply formulas mechanically without adjusting for risk, population, or time period, and exam items exploit comparisons that look numerically obvious but are statistically invalid.
What to do instead
Before answering any comparison item, identify the denominator, the time frame, and whether risk adjustment or stratification is present. Practice explaining in one sentence why an unadjusted comparison is misleading, then select the answer that adjusts or stratifies.
Treating a quality improvement scenario as a one-time correction rather than a cyclical process, so the chosen answer omits measurement, remeasurement, or sustainment.
Candidates remember improvement models by acronym but not their iterative structure, and they pick the intervention step while ignoring the study and act phases.
What to do instead
Map every improvement item onto plan-do-study-act and ask which phase the scenario describes. Ensure the selected answer includes a feedback loop, and practice identifying whether the question is about designing, testing, implementing, or sustaining a change.