RHIT common mistakes
RHIT · Understand the traps and how to avoid them.
Answering a governance-scenario item with "data steward" or "data custodian" when the stem describes enterprise-level decision rights (who owns the data asset, who approves policy), and vice versa.
Candidates memorize the three or four governance role names as a flat list without attaching an accountability level, so any role name feels equally plausible when the stem is a paragraph long.
What to do instead
Build a one-page role ladder with decision rights attached: governance committee/board (policy approval), data owner (accountable for a domain), data steward (defines quality rules and business meaning), data custodian/IT (technical safeguards and storage). For each practice item, write in the margin which level the stem describes before looking at options.
Applying a state retention schedule, or a HIPAA retention rule, to a Medicare record-retention item (or assuming HIPAA sets a retention period at all).
Retention is taught as one blended topic, so candidates default to the source they studied most recently instead of separating legal drivers by payer and record type.
What to do instead
Use a three-source grid: HIPAA sets no retention period (it governs use/disclosure and requires 6 years of documentation retention); state law sets facility licensure retention; Medicare Conditions of Participation require hospital records be retained 5 years. Tag each practice question with which source the stem is testing.
Applying the minimum-necessary standard to a treatment disclosure, or to a disclosure to the individual, and eliminating the correct answer on that basis.
Minimum necessary is over-generalized during prep as a universal HIPAA rule, and the exceptions list is rarely rehearsed to automaticity.
What to do instead
Memorize the exception set as a short chant: treatment, disclosure to the individual, authorized disclosures, disclosures required by law, and certain HHS/oversight requests. Before selecting, ask "is this disclosure for treatment or to the patient?" - if yes, minimum necessary is not the deciding issue.
Accepting a purported authorization as valid when it omits a required core element such as the expiration date/event, the right to revoke, or the statement about redisclosure.
Candidates recall "a signed, dated authorization" and treat signature plus description of PHI as sufficient, because the six required elements are studied as prose rather than as a checklist.
What to do instead
Drill the four core elements plus the three required statements: description of PHI, identification of the recipient, purpose of the disclosure, expiration date or event; plus signature and date, statement of the right to revoke, and statement that redisclosed information may lose protection. Run every authorization option through the checklist item by item.
Mixing up breach-notification clocks - e.g., applying the 60-day outer limit to the individual notice as if it were a fixed deadline, or assigning the annual HHS log requirement to large breaches.
All breach timelines are taught as "60 days," so the different triggers, recipients, and thresholds collapse into one number.
What to do instead
Build a timeline/recipient table: individuals - without unreasonable delay and no later than 60 days from discovery; HHS - contemporaneously for 500 or more individuals, annually for fewer than 500; media - 500 or more in a state or jurisdiction without unreasonable delay. Rebuild the table from memory weekly until the thresholds and recipients stay attached to the right clock.
Selecting sensitivity when the stem asks for the probability that a patient with a positive screen truly has the condition (or selecting positive predictive value when the stem gives prevalence and asks about the test's ability to rule out).
Sensitivity and predictive value are both "accuracy of a test" and the conditional phrasing ("given a positive result") is easy to skim past under time pressure.
What to do instead
Never answer a test-characteristic item from memory of definitions; draw the 2x2 table with the stem's numbers, then read the denominator the question is asking for. Sensitivity and specificity read across the disease row; predictive values read down the test-result column. State the denominator in words before choosing.
Using the wrong denominator in a healthcare rate - e.g., dividing hospital-acquired infection counts by discharges when the measure is per 1,000 patient days, or using admissions for a readmission rate that is defined per eligible index discharges.
Rate formulas are memorized as "numerator over volume" without the standardized denominator, and several indicators use similar-sounding volumes (admissions, discharges, patient days, cases).
What to do instead
Maintain a personal formula sheet with the denominator written out for each indicator you meet in practice items (patient days, discharges, index admissions, surgical cases, live births). When a stem supplies two candidate volumes, the distractor is usually the one that does not match the indicator's standard definition.
Assigning the wrong prospective payment system to a setting - applying MS-DRGs to hospital outpatient services, APCs to inpatient stays, or RBRVS/MPFS to a facility claim - and then answering a coding or reimbursement item incorrectly.
Payment systems are learned as a list of acronyms rather than as a setting-to-system mapping, and item stems often name the service without naming the care setting explicitly.
What to do instead
Make a two-column matrix (setting → payment system/unit of payment) covering inpatient acute (MS-DRG per discharge), hospital outpatient and ambulatory surgery (APC per service), physician/professional (RBRVS per CPT with GPCI adjustment), and post-acute settings. First classify the setting in the stem, then answer only within that row.
Sequencing revenue-cycle steps incorrectly on process items - placing charge capture after coding, treating the chargemaster as coding's responsibility, or starting denial management before claim submission - and then choosing a plausible but out-of-order option.
The cycle is studied as a list of department names rather than a time-ordered flow with handoffs, so items about "the next step" or "where the failure occurred" defeat recall of names alone.
What to do instead
Draw the cycle as a numbered horizontal flow - scheduling/preregistration, registration and eligibility, service delivery, charge capture, coding and CDI, claim edit and submission, remittance posting, denial and appeal management, collections - and label the owner of each handoff. For any process item, locate the step named in the stem on the diagram before evaluating options.
Choosing the Stark law (physician self-referral) for a scenario that actually turns on the Anti-Kickback Statute, or vice versa - for example, selecting Stark for a marketing arrangement involving non-Medicare federal payers or an intent-based remuneration scheme.
Both statutes involve physician relationships and prohibited financial arrangements, and candidates memorize them as a single compliance concept without the distinguishing triggers.
What to do instead
Hold four discriminators: Stark is strict liability and requires no intent, covers physician referrals for designated health services, and applies to Medicare/Medicaid; the Anti-Kickback Statute requires knowing and willful intent, covers remuneration for referrals or generating business, and applies to all federal healthcare programs. Read the stem for intent language, payer type, and whether the item is a referral for a designated service before selecting.
Defaulting to a participative or laissez-faire style on a leadership scenario that describes a crisis, a novice employee, or a tightly regulated task where directive or coaching behavior is correct.
Candidates anchor on the styles they were taught as "best" (democratic, transformational) and answer by value judgment rather than by reading the follower-readiness and urgency cues in the stem.
What to do instead
Use situational-leadership mapping explicitly: identify the follower's competence and commitment and the time pressure, then match (low readiness → telling/directing; moderate → selling/coaching; high → delegating). Underline the cue words in the stem (new hire, code situation, proven expert, deadline) before choosing a style.