RHIA common mistakes
RHIA · Understand the traps and how to avoid them.
Selects 'minimum necessary' as the governing rule any time an item mentions a request for or release of PHI, including a request from a treating physician or emergency provider.
The minimum necessary standard is drilled as a headline principle, and item stems rarely use the phrase 'for treatment' explicitly, so candidates pattern-match on 'request for PHI' instead of first identifying the purpose of the disclosure.
What to do instead
Before evaluating answer options, label the purpose in one word on scratch paper: treatment, payment, operations, required by law, authorized, or public interest. Minimum necessary applies to most uses and disclosures, but not to disclosures to or requests by a provider for treatment, disclosures to the individual, or disclosures made under a valid authorization.
Counts disclosures made under a signed authorization, or disclosures for treatment, payment, and operations, when asked what must appear in an accounting of disclosures; also cites a three-year lookback or a lookback beginning at the date of first treatment.
Accounting of disclosures and the authorization-required list are studied as separate memorized lists and get blended under exam pressure, and 'six years' is easily swapped with other regulatory timeframes (three years, seven years).
What to do instead
Memorize the exclusion list as a short, closed set (TPO, disclosures to the individual, authorized disclosures, facility directory, national security/law enforcement under specific provisions) and anchor the timeframe as six years measured back from the date of the individual's request, not before the April 14, 2003 compliance date.
Answers that IT or the software vendor 'owns' the data, or that describes data stewardship as the executive body that sets policy while describing data governance as cleansing and correcting records.
Plain-English meanings of 'governance' overlap with IT operations, and both terms are usually introduced in the same chapter, so the roles get inverted.
What to do instead
Fix the hierarchy: governance = decision rights, policy, standards, and cross-functional accountability at the senior level; stewardship = day-to-day accountability for the quality and correct use of a data domain. IT and vendors are custodians of systems and infrastructure, while the business/data owner is accountable for the content.
Applies one memorized retention number (commonly seven or ten years) to every retention and destruction item, ignoring the record type, the entity type, and whether a legal hold, audit, or open litigation is present.
Candidates memorize a single figure as 'the' retention period instead of the principle that retention is set by state law and organizational policy and varies by record type.
What to do instead
For each item, extract three facts before answering: the record type, the jurisdiction/entity, and whether any hold, subpoena, or open investigation is mentioned. Destruction is suspended whenever a hold or pending proceeding exists, regardless of the scheduled destruction date.
Chooses 'accuracy' or 'granularity' for scenarios that actually describe precision (the same value on repeated collection), consistency (the same value across systems), timeliness (available when needed for care or reporting), or currency.
The AHIMA data quality characteristics read as near-synonyms in ordinary English, so the distinguishing cue in the scenario gets missed.
What to do instead
Build a cue-to-characteristic table with a concrete example in the opposite column (e.g., 'two registrars code the same field identically = consistency'; 'decimal places reported = precision'). On the item, find the phrase that describes the failure mode and match it to the cue, not to the word that sounds most like 'correct data.'
Interprets sensitivity as the probability that a patient with a positive result actually has the condition, reads a p-value as the probability the null hypothesis is true, or reads a correlation in a performance-improvement scenario as proof that the intervention caused the improvement.
These paired concepts are taught together, and the conditional direction (given disease vs. given result) is easy to invert when reading a short stem quickly.
What to do instead
Write each measure as a full sentence that names its denominator before choosing (e.g., 'sensitivity = positives among those with disease'). Sketch a 2x2 table on scratch paper for any screening/diagnostic item, and treat any analytic finding drawn from observational data as association only.
Assigns CPT to an inpatient procedure or looks for ICD-10-PCS on an outpatient claim, or expects an APC payment for an inpatient stay and an MS-DRG for a hospital outpatient encounter.
Inpatient and outpatient coding and payment systems are studied in the same block, and item stems signal the setting only obliquely (through words like 'admitted,' 'same-day,' 'hospital-based clinic').
What to do instead
Make the first step of every coding or reimbursement item an explicit setting-and-payer determination: inpatient vs outpatient vs physician/ASC, and Medicare vs other. Inpatient facility = ICD-10-CM/PCS with MS-DRG (CC/MCC logic); hospital outpatient = ICD-10-CM with CPT/HCPCS and OPPS/APC; physician services = CPT with RVU-based payment.
Computes case-mix index by dividing total charges or total reimbursement by discharges, or by averaging the relative weights of the distinct DRGs present rather than counting discharges.
Charges and revenue are the numbers most visible on financial reports, and 'average DRG weight' sounds equivalent to 'average patient severity.'
What to do instead
Use CMI = sum of DRG relative weights for all discharges divided by the total number of discharges; a DRG with many discharges pulls the index toward its weight, whereas charges are irrelevant. Check whether the stem asks for CMI, a single DRG weight, or a reimbursement calculation before selecting a formula.
Calculates productivity by dividing workload by paid hours or paid FTEs, or divides a monthly workload by an annualized FTE figure.
Paid hours are the figures that appear on payroll and staffing reports, and PTO/benefit time is easily forgotten when pulling a denominator.
What to do instead
Use worked (productive) hours in the denominator, then reconcile to paid FTEs only when the item asks about budgeted staffing. Confirm the numerator and denominator cover the same period, and convert FTE to hours with the organization's standard (e.g., 2,080 annual hours) before comparing.
Selects the action that is procedurally sound but belongs to a different stage of the change effort, such as communicating the vision when the item describes the need to establish urgency, or moving to a disciplinary response when staff resistance stems from not understanding why the workflow changed.
Distractors are written as genuinely correct leadership behaviors, just correct at another point in the process, and candidates choose the most authoritative-sounding action.
What to do instead
Name the stage out loud from the stem (urgency, guiding coalition, vision, communication, empowerment/removing barriers, short-term wins, consolidation, anchoring) and eliminate any option that fits a different stage. When the stem shows resistance or low adoption, prefer communication, involvement, and barrier removal over discipline or escalation.