2.3 Scored Items, Pretest Items, and Answer Discipline

Pretest Items Without Overthinking Them

The RHIA exam contains 150 items: 130 scored and 20 pretest (unscored). AHIMA uses pretest items to validate new questions for future exam forms; they are randomly distributed throughout the test and are not flagged. The single testing principle that follows is decisive: because you cannot tell which item is which, every item must be answered with identical care.

Pretest items sometimes feel different — newer wording, an unusual scenario, or a task connection that is not obvious. None of that reveals item status. A hard or odd question may well be scored, and a comfortable-looking question may be pretest. Hunting for pretest items only burns the time you need for reasoning.

Answer discipline starts with the stem. First, name the role the question implies: HIM director, privacy officer, revenue-integrity lead, data analyst, CDI specialist, or department manager. The defensible answer often depends on whose authority and accountability the scenario assumes. Second, name the governing rule — a HIPAA standard, a state retention requirement, the minimum-necessary principle, an official coding guideline, a budget constraint, or an accreditation standard.

Third, read the action level. Stems that ask what to do first usually reward assessment, verification, or immediate risk control before any broad rollout — for example, contain and investigate a suspected breach before notifying media. Stems that ask the best long-term approach reward a sustainable workflow, monitoring process, or governance structure. The word best tells you to compare defensibility, not just pick an option that is merely possible. Most appropriate and next step signal sequencing.

Watch the classic RHIA traps. Distractors that are technically true but violate minimum-necessary, that skip a required authorization, that act before verifying facts, or that solve a symptom rather than the root cause are common wrong answers. An option can be a real HIM activity and still be the wrong first action.

Practice with deliberately unfamiliar items so you learn to stay calm under uncertainty. When a question feels strange, slow down only enough to classify it by domain and task, choose the best-supported option, flag it, and move on. After each practice set, review the odd items and ask whether the difficulty came from content, vocabulary, scenario interpretation, or weak elimination. That turns pretest-style uncertainty into productive training rather than panic.

A Four-Step Elimination Routine

Apply a repeatable routine to every scenario item. Step 1 — strike the impossible: remove any option that violates a hard rule, such as disclosing PHI without authorization where none of the permitted exceptions apply, or destroying records before the retention period ends. Step 2 — strike the premature: remove options that act before verifying facts when the stem asks for the first step. Step 3 — strike the symptom-fixer: between two lawful, well-sequenced options, prefer the one that addresses the root cause or builds a sustainable control over the one that patches a single instance.

Step 4 — confirm scope: make sure the surviving answer matches the role and authority the stem assigns; a director-level fix on a clerk-level stem is often a distractor.

Worked Example

A stem reads: "A patient requests an amendment to a clinical note the attending physician believes is accurate. What should the HIM professional do first?" The impossible option ("delete the original note") is struck immediately — amendments never erase the original. The premature option ("deny the request") skips required process. The defensible first step is to forward the amendment request to the author/provider for review within the required timeframe, documenting the request. Naming the rule (HIPAA amendment rights and the provider's decision authority) is what makes the answer defensible rather than a guess.

• Never try to identify pretest items.
• Read each stem for role, rule, risk, and action level.
• Map command words: first/next = sequence; best = defensibility.
• Reject options that breach minimum-necessary or skip verification.
• Use flagging for uncertainty, then review odd items after practice.

Don't Let Pretest Items Erode Confidence

A subtle danger of pretest items is psychological, not logistical. If you hit three unusually hard or oddly worded questions in a row, it is tempting to conclude you are failing and to spiral into rushing or second-guessing. Recognize that a cluster of strange items is statistically normal when 20 unscored experimental questions are scattered through 150, and that an experimental item may be poorly calibrated by design — that is exactly why AHIMA is testing it.

The correct internal response is to reset: classify the item by task, apply the four-step elimination routine, flag if needed, and move on without drawing conclusions about your overall performance. Your score depends on the 130 scored items as a whole, never on any single difficult question, so no individual item is worth a confidence collapse.