Health Information & Coding · Independent exam preparation
Registered Health Information Technician (RHIT): Free Preparation Guide Study Guide
Practise record integrity, privacy decisions, healthcare statistics, coding and denial analysis, payment methods, utilization review, and workflow improvement across all six AHIMA RHIT domains.
By CertMedbry · Updated 14 October 2026
Learn to distinguish duplicate records from overlays, choose defensible disclosure actions, calculate meaningful performance measures, and connect documentation, coding, and denial findings to corrective action. This guide follows the AHIMA RHIT outline effective October 1, 2022. Its 60 selected concepts cover every domain; the official outline defines the full examination scope. Additional study is needed for accounting of disclosures, detailed external-data-source and reporting requirements, procedure-code selection, and the full range of payer-specific payment rules. United States federal privacy and Medicare examples identify their jurisdiction, and facility examples state their own assumptions.
Try 20 free practice questionsWhat is the exam format?
Check the question types, timing and outline before planning your revision.
Which credential and educational pathway does this guide cover?
This guide covers AHIMA's Registered Health Information Technician examination. The issuer lists completion of an associate-level, CAHIIM-accredited Health Information Management program or an eligible HIM program under an AHIMA reciprocity agreement. AHIMA states that health informatics programs are not currently accepted for RHIT eligibility. Reciprocity applicants must satisfy the applicable educational competencies; this guide does not substitute another association's examination for AHIMA RHIT.
How many questions are scored, and how much examination time is allowed?
AHIMA lists 150 total questions: 130 scored items and 20 unscored pretest items. Pretest items are randomly distributed and collect performance data. The stated examination time is three hours and thirty minutes. Treat every item seriously because candidates are not given a separate identifiable pretest section.
How is the examination delivered, and can candidates review answers?
AHIMA specifies computer-based testing at a Pearson VUE testing center. Candidates may move between items after selecting an answer, flag items, and return for review before submitting, as time permits.
Which item styles should candidates expect?
The issuer states that AHIMA examinations contain a variety of questions or item types requiring selection of the best answer using knowledge, skills, or experience. Its RHIT specifications do not enumerate a complete item-style inventory. This guide provides 20 independent, four-option, single-best-answer drills; their format does not establish every format used on the certification examination.
Which blueprint applies, and what are its domain weights?
The AHIMA-linked outline is effective October 1, 2022, with copyright 2023. Its ranges are Data Content, Structure, and Information Governance 19–25%; Access, Disclosure, Privacy, and Security 14–18%; Data Analytics and Use 12–18%; Revenue Cycle Management 19–25%; Compliance 13–17%; and Leadership 9–12%. The filename and copyright do not change the effective date. Use the official outline to check every examination task.
AHIMA RHIT Content Outline, effective October 1, 2022 · Registered Health Information Technician (RHIT) | AHIMA
How does this guide distribute its learning material?
The 60 concepts use domain counts of 14, 10, 9, 13, 8, and 6 in official domain order. The questions and flashcards each use counts of 5, 3, 3, 4, 3, and 2. These allocations approximate the published ranges without replacing them with invented fixed weights. Consult every task in the official outline because this selective guide is not the complete syllabus. Accounting of disclosures, detailed external reporting, procedure-code selection, and comprehensive payer-specific payment calculations require additional study.
What passing score, examination fees, and resources are specified?
AHIMA lists a passing score of 300, examination fees of $229 for AHIMA members and $299 for nonmembers, and no required books or resources on examination day. A score of 300 should not be converted into a raw percentage without an issuer-supported conversion. Confirm current administrative terms before applying.
Which coding guideline dates apply to the examples?
Diagnosis-coding examples use the FY 2027 ICD-10-CM guidelines, effective October 1, 2026 through September 30, 2027. Coding-rule dates are separate from the RHIT blueprint's effective date. Apply the code set and guidance governing the encounter or discharge being coded rather than assuming that the examination outline freezes coding rules at 2022.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · AHIMA RHIT Content Outline, effective October 1, 2022
RHIT means Registered Health Information Technician, an AHIMA credential administered through CCHIIM. The workbook label “Technologist” refers to this same listing and does not establish another examination. These independently authored learning materials are not official examination items or AHIMA-endorsed preparation.
Outline used: Current AHIMA-linked RHIT Content Outline, effective October 1, 2022; PDF copyright 2023. Live issuer page and linked outline successfully opened on October 9, 2026, Asia/Hong_Kong; no newer announced outline found. Workbook label 'Registered Health Information Technologist' maps to the official Registered Health Information Technician examination; the assigned slug is preserved.
60 key concepts: understand, apply and avoid the traps
Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.
Data Content, Structure, and Information Governance19-25%
1.How should a documentation correction preserve record integrity?
Preserve identifiable original content and link it to the correction so reviewers can reconstruct what changed, who changed it, and when. This is an integrity recommendation; current Medicare Program Integrity Manual section 3.3.2.5 specifically describes identifiable authors and dates and clearly, permanently denoted changes. CMS Transmittal 12633 characterizes those recordkeeping principles as best practices that should not independently cause denial; applicable signature analysis under section 3.3.2.4 remains separate. An explicit preservation requirement applies to corrected home-health comprehensive assessments: State Operations Manual section 2202.11D requires retention of the original assessment and subsequent corrected assessments. That setting-specific rule should not be presented as the wording of section 3.3.2.5.
Apply it
A clinician discovers that a signed note lists the wrong side for a procedure. HIM directs the clinician to the correction function that preserves the original text, identifies the corrected side, and records the author and correction date. A Medicare reviewer separately evaluates applicable signature requirements and authenticity.
Common pitfall: An unexplained replacement obscures documentation history. Conversely, do not conclude that Medicare must deny a claim solely because a correction lacks a recommended recordkeeping feature.
Medicare Program Integrity Manual, Chapter 3 · r12633pi.pdf · som107c02.pdf
2.When does a delayed entry need separate identification?
A delayed entry adds documentation after the event it describes. It should be clearly identified as delayed, dated when entered, and attributed to its author while accurately identifying the underlying event. Separating event time from entry time allows reviewers to evaluate chronology without mistaking later documentation for contemporaneous evidence. The key distinction is between documenting a remembered event transparently and changing timestamps to imply that the record was completed earlier than it actually was.
Apply it
A provider documents yesterday's discussion today. The entry identifies yesterday's event, today's entry date, the author, and its delayed status. HIM checks those elements rather than changing the electronic timestamp to match the conversation.
Common pitfall: Backdating an entry to the service date hides its actual creation time. A delayed entry also cannot establish an event that the author cannot accurately document.
3.What distinguishes an MPI duplicate from two different patients?
An MPI duplicate occurs when one person has more than one patient record or identifier within the system. Similar names alone do not establish a duplicate because different people may share names and birth dates. Identity review should compare multiple demographic elements and encounter information, resolving conflicts before consolidation. The decision depends on evidence that the records represent the same individual, with an authorized process preserving access to the person's combined history and documenting the merge.
Apply it
Two records share a birth date and similar names but have different addresses. An identity specialist verifies previous names, contact details, and encounter history before deciding whether the records are duplicates or belong to separate people.
Common pitfall: Merging records solely because names resemble each other can create an overlay. Leaving verified duplicates unresolved also fragments information needed for care and reporting.
4.Why does an overlay require a different correction process?
An overlay combines information from different people within one record. Unlike a duplicate, it requires separation of incorrectly attributed information, not consolidation of two records for one individual. Identity investigation must establish which entries belong to each person and consider linked results, orders, portal displays, and downstream systems. The decisive cue is mixed ownership of clinical information. Correcting demographics alone may leave another patient's clinical history attached to the wrong individual and available for future decisions.
Apply it
A patient reports an unfamiliar operation in the portal. Investigation confirms that another person's encounter was attached to the record. The correction team separates the encounter and checks affected results, interfaces, and portal information for remaining misattribution.
Common pitfall: Treating an overlay as a duplicate and merging more records increases contamination. Changing only the displayed name does not correct ownership of clinical entries.
5.How does demographic verification prevent identity errors?
Patient matching depends on accurate, consistently captured demographic information. Registration should obtain and verify identifying details rather than assume that an existing record remains current or that a patient's appearance confirms identity. Open-ended confirmation helps reveal errors that a simple yes-or-no response may miss. The discriminating clue is a discrepancy requiring resolution before record selection or demographic updating. Standard capture practices also improve later matching by reducing inconsistent spelling, incomplete fields, and unsupported demographic assumptions.
Apply it
At registration, a patient supplies a current address that differs from the selected record. Staff verify additional identifiers and whether the address changed before updating the record, ensuring that the discrepancy is not evidence of a different patient.
Common pitfall: Automatically overwriting demographics can conceal a wrong-record selection. Asking a patient merely to agree with information displayed on screen may fail to reveal errors.
Registrar Playbook, Chapter 2: Capturing Patient Demographic Data
6.When should an uncertain patient match receive manual review?
Matching tools support identity decisions but do not eliminate uncertainty. A possible match with conflicting demographics should enter an established review process instead of being automatically accepted because it exceeds a convenient score threshold. Manual review examines additional reliable identifiers and resolves conflicting evidence. The decision should balance avoiding false matches against avoiding unnecessary duplicate creation. The important cue is unresolved identity conflict, especially when the proposed action would combine records or expose information to another person.
Apply it
An automated report proposes merging records with matching names and birth dates but different verified telephone numbers and overlapping encounters. HIM holds the merge and assigns identity review to determine whether the records represent one person.
Common pitfall: A high similarity score is evidence for review, not proof of identity. Creating a new record for every uncertain match can also increase duplicates.
7.Which records belong in a designated record set?
Under the HIPAA right of access, a designated record set includes medical and billing records and other records used, in whole or in part, to make decisions about individuals. Its boundaries depend on function, not simply where information is stored or whether a document appears in the main chart. HIM should identify relevant systems and record owners. The discriminating question is whether the information belongs to the defined record categories or supports decisions about a particular individual.
Apply it
A clinic maintains clinical notes in its EHR and patient-specific billing records in another system. HIM includes both systems when mapping its designated record set rather than limiting the inventory to documents visible in the clinical chart.
Common pitfall: Equating the designated record set with the EHR excludes qualifying information elsewhere. Conversely, every organizational document containing a patient's name does not automatically qualify.
8.How do completion audits differ from content audits?
A completion audit asks whether required documentation elements are present and completed under the applicable standards. A content audit asks whether the documentation itself is accurate, internally consistent, and suitable for its intended use. These dimensions can diverge: a signed note may contain the wrong patient information, while an accurate note may lack required authentication. The RHIT outline includes both record content and completion. Audit criteria should therefore define which dimension is being measured before classifying a deficiency.
Apply it
A facility audit finds a signed discharge document naming the wrong procedure. Under its audit definitions, authentication passes the completion check, but the incorrect procedure fails the content check and requires an appropriate documentation correction.
Common pitfall: Counting signatures alone can produce an impressive completion rate while overlooking inaccurate content. A content concern should not be disguised as a missing-document finding.
AHIMA RHIT Content Outline, effective October 1, 2022 · Medicare Program Integrity Manual, Chapter 3
9.Why does document control require version identification?
Document control coordinates creation, revision, standardization, and use of forms or templates. A practical control process identifies the approved version, responsible owner, effective date, and locations where the document is used. This allows staff to distinguish current instructions from obsolete copies and enables investigators to identify which version governed an earlier encounter. The cue for action is competing versions with different requirements. Revision is incomplete when a new form is approved but older copies remain available in routine workflow.
Apply it
A department approves a revised consent template, but registration still prints an older copy from a shared folder. HIM identifies the approved version, replaces distribution points, and confirms that the workflow now produces the current document.
Common pitfall: Renaming a file “final” does not establish controlled approval or deployment. Removing historical versions indiscriminately can also prevent reconstruction of earlier documentation requirements.
AHIMA RHIT Content Outline, effective October 1, 2022 · HHS-OIG General Compliance Program Guidance, November 2023
10.How can data workflow reveal the source of an error?
Data workflow follows information from initial capture through transfer, transformation, storage, and use. Mapping these steps helps distinguish an incorrect source entry from an interface error or reporting transformation. Investigators should compare the same field at successive points and identify where it first diverges from the verified value. The discriminating clue is the earliest incorrect representation. Correcting only the final report may leave the upstream cause active, allowing the same error to recur in later records and other outputs.
Apply it
A patient's name is correct in registration but truncated in a downstream report. The team compares interface messages, receiving-system fields, and report logic to locate the first truncation rather than repeatedly editing individual report outputs.
Common pitfall: Assuming the final system created the error can misdirect corrective work. A workflow map should reflect actual handoffs, including informal steps that staff routinely perform.
AHRQ: How to Map Workflows in Health Care Settings · AHIMA RHIT Content Outline, effective October 1, 2022
11.Which test cases establish that an EHR change works?
An EHR functionality change should be assessed against its intended behavior and the workflows it affects. Useful cases include valid entries, missing required information, conflicting data, and relevant downstream displays or reports. The test must examine the result, not merely whether the configuration was saved. The decisive cue is whether information remains correctly attributed and usable throughout the affected process. Testing supports the outline's record-integrity and EHR-functionality tasks without assuming that a successful screen change guarantees successful data handling.
Apply it
A facility adds a required discharge field. HIM tests a complete record, a missing-field record, and the exported discharge report to verify both the intended completion control and the accuracy of information passed downstream.
Common pitfall: Testing only a perfect entry overlooks exceptions that cause operational errors. Successful configuration approval does not demonstrate that interfaces, reports, and existing records behave correctly.
AHIMA RHIT Content Outline, effective October 1, 2022 · AHRQ: How to Map Workflows in Health Care Settings
12.How should an exception report support data integrity?
An exception report identifies records that violate a defined rule, such as inconsistent identifiers or an impossible sequence of dates. Its usefulness depends on explicit logic, appropriate source fields, and a process for reviewing findings. A flagged record is a candidate for investigation rather than an automatic finding of misconduct or a confirmed clinical error. The discriminating step is comparison with the underlying record. HIM should also verify that the report detects known exceptions and does not misclassify legitimate variations.
Apply it
An EHR report flags discharges occurring before admissions. HIM reviews sample records and discovers that one interface supplies timestamps in a different time zone. The team corrects the transformation rather than changing valid encounter dates.
Common pitfall: Treating every flag as a confirmed deficiency inflates findings. A report that returns no exceptions may have faulty logic rather than prove that data are flawless.
AHIMA RHIT Content Outline, effective October 1, 2022 · AHRQ: How to Map Workflows in Health Care Settings
13.Why must portal support begin with correct patient identity?
A portal can display the wrong person's information if enrollment or record linkage is incorrect, even when its screens function normally. Support should distinguish a navigation problem from an identity or record-integrity problem. Unfamiliar encounters, conflicting demographics, or another person's documents warrant identity investigation and appropriate protection of access. The cue is evidence of incorrect ownership, not merely an unexpected display. Resolving the account login alone does not correct clinical information that was attached to the wrong patient record.
Apply it
A patient can log in but sees an unfamiliar laboratory encounter. Portal support verifies account linkage and escalates the possible identity error, coordinating record correction and review of affected displays rather than simply resetting the password.
Common pitfall: Calling unfamiliar content a display problem can leave an overlay unresolved. Identity investigation should precede reassuring the patient that every visible record belongs to them.
SAFER Guide: Patient Identification · AHIMA RHIT Content Outline, effective October 1, 2022
14.How should documentation education address a recurring defect?
Documentation education should translate a verified requirement into the specific behavior needed to meet it. Recurring defects should be illustrated with appropriately protected examples and the correct workflow, including authentication or correction when relevant. The educational target is the cause of the defect, not a broad reminder to document better. A useful discriminating cue is whether clinicians can demonstrate the required action in a realistic case. Follow-up review then establishes whether education changed documentation practice rather than merely reached its audience.
Apply it
An audit repeatedly finds corrections that obscure original text. HIM teaches the approved correction function using a sample note, asks clinicians to demonstrate it, and later reviews corrected records for preservation, authorship, and date identification.
Common pitfall: A generic email may document communication without addressing the actual defect. Education cannot compensate for a system function that prevents users from following the required process.
Medicare Program Integrity Manual, Chapter 3 · r12633pi.pdf · som107c02.pdf · HHS-OIG Compliance 201 for Health Care Providers
Access, Disclosure, Privacy, and Security14-18%
15.Which existing information does an individual have a right to access?
HIPAA access includes qualifying medical and billing records maintained by or for a covered entity across relevant systems. Separately maintained psychotherapy notes documenting or analyzing counseling-session contents are excluded; ordinary clinical summaries or SOAP notes are not automatically psychotherapy notes. Information compiled in reasonable anticipation of, or for use in, legal proceedings is also excluded, but underlying qualifying medical and payment records remain accessible. Determine the record's function and applicable exclusion rather than deny access because it is in a billing system, archive, mental-health service, or litigation file.
Apply it
A patient requests billing records, a clinical treatment summary, separately maintained counseling-session psychotherapy notes, and an attorney's litigation-preparation analysis. Process access to the qualifying billing records and clinical summary; distinguish the excluded psychotherapy notes and litigation analysis while preserving access to their underlying qualifying medical and payment records.
Common pitfall: A mental-health setting does not make every clinical note a psychotherapy note. Using a medical record for litigation preparation does not remove the underlying record from the access right.
16.When does an access request ask for a new analysis?
The HIPAA access right generally concerns existing qualifying information; it does not require the covered entity to create a new explanation, analysis, or compilation that it does not already maintain. Distinguish a request for existing records from a request to calculate or interpret new results. The decision should preserve access to the underlying information even when the requested analytical product is not required. This boundary avoids both unnecessary creation duties and an overbroad denial of records already subject to access.
Apply it
A patient asks for existing laboratory reports and a newly calculated decade-long trend analysis that the clinic has never created. HIM provides access to qualifying reports and explains that the access right does not require that new analysis.
Common pitfall: Declining the new analysis does not justify withholding existing records. Conversely, a maintained patient-specific analysis may itself require designated-record-set evaluation rather than automatic exclusion.
17.When is a treatment disclosure exempt from minimum necessary?
HIPAA's minimum necessary standard does not apply to disclosures to, or requests by, healthcare providers for treatment. This exception supports information exchange needed for patient care. Its cue is the purpose and parties to the disclosure, not the requester's professional title alone. The exception does not eliminate other applicable safeguards or authorize unrelated access. It also should not be expanded automatically to every internal workforce use, because HHS separately describes role-based policies for access by members of the covered entity's workforce.
Apply it
A treating specialist requests the patient's records from a covered clinic for continuing care. HIM recognizes the treatment-disclosure exception while verifying the destination and using the clinic's secure transmission process to protect the information.
Common pitfall: Requiring minimum-necessary reduction for every provider treatment disclosure misapplies the exception. A provider requesting records for an unrelated purpose does not qualify merely by occupation.
18.How should workforce access reflect job responsibilities?
For internal uses, HHS describes policies identifying workforce members or classes who need access, the categories of PHI they need, and conditions of access. Role-based access translates those needs into appropriate permissions. The decisive cue is a legitimate work function requiring the information, not curiosity, convenience, or employment alone. Broad access can be justified for a role when needed, but the organization should support that decision through its policies rather than use the treatment-disclosure exception to excuse unrestricted workforce access.
Apply it
A scheduling employee needs contact details and appointment information but has no assigned function requiring unrestricted clinical notes. The clinic configures access around those responsibilities and routes exceptional needs through its established authorization process.
Common pitfall: Being employed by a healthcare organization does not establish a need for every chart. The provider treatment-disclosure exception does not automatically define internal workforce permissions.
19.How does minimum necessary guide a nonroutine disclosure?
When minimum necessary applies, the covered entity should limit PHI to what is reasonably needed for the permitted purpose. HHS distinguishes routine disclosures governed by standard protocols from nonroutine disclosures assessed using established criteria. The mechanism is purpose-based selection of information, not an arbitrary page limit. The discriminating question is which records or data elements are needed to accomplish the request's legitimate objective. First establish that the disclosure is permitted; minimum necessary does not independently create permission to disclose.
Apply it
For a permitted, nonroutine payment review, an analyst requests records supporting a specified service. HIM applies its review criteria to select relevant information rather than automatically send the patient's entire longitudinal record for unrelated encounters.
Common pitfall: A smaller disclosure can still be impermissible if no valid disclosure basis exists. Conversely, minimum necessary may include extensive information when the supported purpose requires it.
20.Why are unique user identifiers necessary for electronic PHI?
The HIPAA Security Rule requires unique user identification so that systems can identify and track each user's activity involving electronic PHI. Shared log-on identities weaken attribution because an access event cannot reliably be connected to the person who performed it. The decisive distinction is between a shared workstation and a shared identity: multiple employees may use the same device while retaining individual credentials. Access investigations and accountability depend on that attribution, supplemented by appropriate authentication and account management.
Apply it
Three staff members use one registration workstation across shifts. Each signs in with an individual account so that demographic changes can be traced to a specific user rather than recorded under a common departmental log-on.
Common pitfall: A paper schedule beside a shared account does not replace unique electronic identification. Individual credentials also lose attribution value when employees routinely lend them to coworkers.
21.What makes Safe Harbor de-identification more than name removal?
Safe Harbor removes all specified identifier categories and requires no actual knowledge that remaining information could identify the person. Remove individual-related date elements except year; aggregate ages over 89 as age 90 or older and remove date elements, including years, that reveal such ages. Remove geography smaller than a state. Retain a three-digit ZIP prefix only when its combined geographic unit exceeds 20,000 people according to current publicly available Census data; otherwise replace it with 000. Review narratives as well as structured fields.
Apply it
For an otherwise eligible dataset, change an admission date of April 12, 2026 to 2026 and age 94 to age 90 or older, suppressing a birth year that reveals that age. Retain a ZIP prefix representing 20,001 people, but replace one representing exactly 20,000 with 000. Remove city and street address, then assess all remaining identifiers and actual knowledge.
Common pitfall: Exactly 20,000 does not meet the ZIP exception. Keeping a birth year that reveals age 94 defeats the age rule; identifiers in free text also count.
HHS Guidance on De-identification of Protected Health Information
22.How does Expert Determination establish de-identification?
Expert Determination uses a qualified expert's statistical and scientific assessment that the risk of identification is very small under the anticipated conditions of use. The expert documents the methods and results supporting that conclusion. Unlike Safe Harbor, it is not simply a checklist of removed fields. The discriminating cue is a defensible, documented risk determination for the particular data and context. An organization's preference to retain useful detail does not itself establish that the retained information is sufficiently protected.
Apply it
Researchers need date detail that would not satisfy Safe Harbor. The organization obtains a qualified expert's assessment of the proposed dataset, recipient context, and identification risk, with documented methods and any required modifications before release.
Common pitfall: An analyst's informal opinion is not a documented Expert Determination. A finding for one dataset or recipient context should not be assumed to cover materially different uses.
HHS Guidance on De-identification of Protected Health Information
23.Which authority determines a medical record retention period?
HHS states that the HIPAA Privacy Rule does not prescribe a medical record retention period. Applicable state law and other governing requirements must therefore be distinguished from HIPAA safeguards and retention obligations for HIPAA-related documentation. A retention decision should identify the record type, jurisdiction, applicable requirements, and any hold preventing destruction. The decisive cue is the authority governing that particular record, not a universal number attributed to HIPAA. Privacy protections continue while the organization maintains the information.
Apply it
A clinic revises its retention schedule for medical charts and HIPAA policy documentation. HIM separates the two record categories, identifies their governing requirements, and checks for holds before approving any scheduled chart destruction.
Common pitfall: Applying a HIPAA documentation period to every medical chart confuses separate obligations. Expiration of a routine retention period does not override an applicable preservation hold.
24.How should disposal protect records approved for destruction?
Retention eligibility and secure disposal are separate decisions. First establish that destruction is authorized under the applicable schedule and that no hold applies. Then use a controlled process that protects PHI through collection, transfer, and destruction. The decisive clue is whether information remains accessible to unauthorized people during disposal, not simply whether it has left active storage. HHS explains that safeguards apply for as long as information is maintained, including disposal; an expired retention period does not make confidential records public.
Apply it
Paper charts are approved for destruction under a facility's verified schedule. Staff place them in controlled destruction containers, document the authorized batch, and use the approved destruction process rather than leave boxes in an open recycling area.
Common pitfall: A record's age does not eliminate confidentiality obligations. A destruction certificate also does not establish that the original decision to destroy complied with retention requirements.
Data Analytics and Use12-18%
25.Why must an analysis define its unit of observation?
The unit of observation determines what each counted row represents, such as a patient, encounter, claim, or document. These units are not interchangeable because one patient may generate several encounters and each encounter may generate multiple documents. Before calculating a proportion or reporting a count, specify the unit and ensure that extraction and aggregation preserve it. The discriminating cue is whether repeated rows represent legitimate separate observations or duplicate representations of the same observation, which would distort the denominator.
Apply it
An analyst joins encounters to documents and obtains three rows for an encounter with three notes. To report encounter-level completion, the analyst reduces the joined data to one assessed result per encounter before calculating the rate.
Common pitfall: Counting joined rows as patients or encounters can inflate totals. Removing every repeated patient identifier would also discard legitimate separate encounters when encounters are the intended unit.
CDC Principles of Epidemiology: Frequency Measures · AHIMA RHIT Content Outline, effective October 1, 2022
26.How should an extracted dataset be validated?
Extraction validation checks whether the dataset matches the intended population, time period, fields, and unit of observation. Compare selected rows with source records and reconcile totals using equivalent definitions. Unexpected missing values or changes in counts may reflect extraction logic rather than changes in care or performance. The decisive cue is agreement between the analytical definition and the source-selection process. Validation should precede interpretation because a mathematically correct calculation remains misleading when its underlying records were selected or transformed incorrectly.
Apply it
A monthly discharge extract appears unusually small. The analyst compares source totals and discovers that the query excluded records with a blank optional field. Correcting the selection logic restores the intended population before statistics are calculated.
Common pitfall: Accepting an extract because the query ran successfully confuses technical execution with validity. Matching totals alone cannot prove that individual fields or records are correct.
CDC Field Epidemiology Manual: Describing Epidemiologic Data · AHIMA RHIT Content Outline, effective October 1, 2022
27.What denominator belongs in a deficiency percentage?
A proportion compares a subset with the whole population that contains it. For a record-deficiency percentage, the numerator might be deficient audited records and the denominator all eligible audited records, multiplied by 100. Counts must refer to the same period, population, and unit. The discriminating clue is whether every numerator observation could also appear in the denominator. Counting deficiencies rather than deficient records creates a different measure when one record can have several defects, so the metric's wording must match its calculation.
Apply it
An audit reviews 240 records and finds at least one deficiency in 36. The deficient-record percentage is 36 divided by 240, multiplied by 100, or 15%, regardless of how many separate defects those records contain.
Common pitfall: Dividing deficient records by compliant records produces a ratio, not the deficient-record proportion. Counting individual defects cannot substitute for counting records with a defect.
28.How should rates from unequal groups be combined?
Combine comparable group proportions by summing their numerators and denominators, then calculating the overall proportion. A simple average of percentages gives equal influence to groups even when their sizes differ. The decisive cue is unequal denominators: larger groups should contribute proportionally more observations. This approach requires compatible definitions and nonoverlapping populations. If definitions differ, pooling counts can create a precise-looking statistic that lacks a coherent meaning; harmonize the measure before calculating a combined result.
Apply it
One unit has 8 deficient records among 40 audited; another has 12 among 160. The overall percentage is 20 divided by 200, or 10%, rather than the simple average of 20% and 7.5%.
Common pitfall: Averaging subgroup percentages without denominator weights misstates pooled performance. Even weighted arithmetic is inappropriate when groups use different deficiency definitions or overlapping records.
CDC Principles of Epidemiology: Frequency Measures · CDC Field Epidemiology Manual: Describing Epidemiologic Data
29.When is the median preferable for typical turnaround time?
The median is the middle observation after values are ordered, or the average of the two middle observations for an even-sized dataset. It is less influenced by extreme observations than the mean. For strongly skewed turnaround times, the median can describe a typical request more effectively. The discriminating cue is an unusually long or short tail. However, the median alone can conceal serious delays, so a useful operational report may also show range, distribution, or the proportion exceeding a defined target.
Apply it
Five completed requests took 1, 2, 2, 3, and 22 days. The median is 2 days, while the mean is 6 days. HIM reports the median with the extreme delay rather than implying that all requests finished promptly.
Common pitfall: The median's resistance to outliers does not make extreme delays unimportant. Selecting it solely because it looks favorable hides operational problems rather than clarifies performance.
CDC Principles of Epidemiology: Choosing Measures of Central Location and Spread
30.What does the mean reveal about workload?
The mean equals the sum of observations divided by their number. It uses every value and therefore reflects the total quantity spread across observations, which can help estimate aggregate workload or processing time. It is also sensitive to extreme values. The decisive cue is the analytical purpose: estimating total resource demand differs from describing the middle case. Before using the mean, verify that values are measured on a compatible scale and consider whether skew or outliers require additional explanation.
Apply it
Four comparable tasks take 10, 15, 15, and 40 minutes. Their mean is 20 minutes, and total time is 80 minutes. A manager uses both figures to discuss workload while noting that one unusually long task affects the average.
Common pitfall: The mean is not necessarily the most common or middle observation. Combining unlike task categories into one average can obscure the resources needed for each category.
CDC Principles of Epidemiology: Choosing Measures of Central Location and Spread
31.How should a chart distinguish volume from performance?
Counts describe volume, whereas proportions or rates relate events to a defined population or exposure. A rising count of deficiencies can accompany an improving deficiency percentage if the number reviewed rises faster. Charts should label the measure, denominator, and time interval and use comparable definitions across periods. The discriminating cue is a changing population size. Time-ordered displays help reveal trends, but visual movement should not be attributed to an intervention without considering changes in volume, selection, definitions, and other plausible explanations.
Apply it
Deficient records increase from 20 of 100 to 30 of 300. A volume chart rises, but the deficient-record percentage falls from 20% to 10%. The report presents both measures so readers do not confuse workload with performance.
Common pitfall: A count alone can imply worsening performance when volume increased. A percentage alone can conceal a growing absolute workload that still requires staffing attention.
CDC Field Epidemiology Manual: Describing Epidemiologic Data · CDC Principles of Epidemiology: Frequency Measures
32.Which time denominator makes productivity comparisons meaningful?
A productivity measure needs an explicit output unit and time denominator. Records coded per productive coding hour differs from records coded per paid hour because the latter may include meetings, training, or other duties. Comparisons should use the same definitions and consider differences in task complexity and quality. The decisive cue is denominator consistency. The RHIT outline includes coding productivity, but a locally selected metric should disclose its calculation rather than present a facility target as a universal professional standard.
Apply it
A coder completes 54 comparable records during 6 coding hours within an 8-hour paid shift. Productivity is 9 records per coding hour or 6.75 per paid hour; the report identifies which denominator it uses.
Common pitfall: Comparing productive-hour rates with paid-hour rates creates an artificial difference. Higher output also does not establish better performance when accuracy or case complexity differs.
AHIMA RHIT Content Outline, effective October 1, 2022 · CDC Principles of Epidemiology: Frequency Measures
33.How should ROI turnaround time be operationally defined?
Release-of-information turnaround measures elapsed time between defined start and end events. A defensible operational definition specifies whether the clock begins at initial receipt or another stated event, whether time uses calendar or business days, and which requests are included. It should also distinguish completed requests from the age of pending work. The decisive cue is whether two departments are timing the same process. Local performance definitions do not replace legal requirements; reports should make their boundaries explicit so improvement claims remain interpretable.
Apply it
Two offices report average ROI turnaround, but one starts at receipt and the other at internal assignment. HIM standardizes the operational definition and recalculates results before comparing performance, while separately tracking the age of pending requests.
Common pitfall: Comparing differently defined clocks produces misleading rankings. Excluding unfinished requests can make a backlog disappear from a completed-request average even while delays accumulate.
AHIMA RHIT Content Outline, effective October 1, 2022 · CDC Field Epidemiology Manual: Describing Epidemiologic Data
Revenue Cycle Management19-25%
34.Which condition is the inpatient principal diagnosis?
For inpatient coding, the principal diagnosis is the condition established after study to be chiefly responsible for occasioning the admission. It is not automatically the first symptom recorded, the most expensive condition, or the diagnosis requiring the greatest effort later in the stay. The decisive cue is the documented relationship between the established condition and the admission, interpreted under applicable sequencing guidance. Review the completed record because information developed after admission may clarify the condition that actually occasioned hospitalization.
Apply it
A patient is admitted for abdominal pain. After study, the provider establishes acute appendicitis as chiefly responsible for the admission. The coder evaluates appendicitis as the principal diagnosis rather than selecting the presenting symptom solely because it appeared first.
Common pitfall: Choosing the highest-paying condition substitutes financial outcome for the principal-diagnosis definition. Special sequencing instructions may further govern selection, so the definition is not the only coding rule.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027
35.How should uncertain diagnoses be handled in outpatient coding?
Outpatient coding does not treat diagnoses documented as probable, suspected, questionable, or similar uncertainty terms as established conditions. Code to the highest degree of certainty known for that encounter, such as documented symptoms, signs, or confirmed findings, using applicable guidelines. The decisive cue is the outpatient setting combined with unresolved diagnostic language. This differs from the applicable inpatient discharge approach to certain uncertain diagnoses. A test ordered to investigate a disease does not itself establish that disease for outpatient coding.
Apply it
At an outpatient visit, the provider documents “possible pneumonia” and cough, with no confirmed pneumonia diagnosis. The coder reports the documented condition known with certainty rather than treating the possible diagnosis as established.
Common pitfall: Importing inpatient uncertainty rules into outpatient coding overstates certainty. Conversely, a confirmed outpatient diagnosis should not be replaced with its routine symptoms without considering guideline instructions.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027
36.Why must an ICD-10-CM index selection be verified?
The Alphabetic Index helps locate a candidate code, but the Tabular List supplies the classification details needed to verify the final assignment. Review the complete code, required specificity, instructional notes, and relevant inclusion or exclusion guidance. The decisive cue is that an index entry is a starting point, not a complete substitute for verification. Coding should also use the applicable year's guidelines and code set. A familiar code recalled from memory can be incomplete or inappropriate for the documented circumstances.
Apply it
A coder locates a candidate diagnosis code in the index. Before finalizing it, the coder checks the Tabular List for required characters and instructions that may affect code selection or sequencing for the documented condition.
Common pitfall: Stopping at an index entry can miss mandatory specificity or instructions. An encoder suggestion likewise requires verification against documentation and the applicable classification rules.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027
37.How do clinical indicators and supplementary documentation support code assignment?
Under ICD-10-CM section I.A.19, diagnosis assignment generally follows the provider's diagnostic statement; the coder does not independently apply clinical criteria to establish or reject the diagnosis. Indicators can support clarification when documentation is missing or conflicting. Section I.B.14 permits specified details from other clinicians authorized to document in the record, such as a dietitian's BMI or a nurse's pressure-ulcer stage. The associated diagnosis, such as obesity or pressure ulcer, must still be documented by the provider. These exceptions permit supplementary detail, not general authority to infer disease. Conflicting documentation warrants a provider query.
Apply it
The provider documents obesity and a dietitian records BMI, allowing consideration of the appropriate BMI code under the guidelines. Likewise, a provider documents a pressure ulcer and an authorized nurse documents its stage. If no provider documents the associated diagnosis, the BMI or stage alone does not establish it; conflicting stages require clarification.
Common pitfall: Do not infer obesity from BMI alone or a pressure-ulcer diagnosis from staging alone. Equally, do not insist that the provider personally document every supplementary detail allowed by I.B.14.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · AHIMA RHIT Content Outline, effective October 1, 2022
38.When does conflicting documentation need clarification?
A clarification request is appropriate when documentation needed for accurate coding is incomplete, conflicting, or unclear and cannot be resolved through applicable coding instructions. The request should identify the specific issue and relevant documented facts so that the responsible provider can clarify the record. The decisive cue is a documentation problem, not a desired reimbursement result. The coder should not silently select the financially favorable statement or rewrite clinical conclusions; the clarification belongs in an attributable documentation process that preserves record integrity.
Apply it
Two provider notes describe different sites for the same documented condition, and the distinction affects code selection. The coder seeks clarification of the conflicting site information rather than choosing whichever note supports the preferred code.
Common pitfall: A request aimed at securing a predetermined diagnosis undermines documentation integrity. Clarification also should not substitute for reading instructions that already resolve a classification question.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · Medicare Program Integrity Manual, Chapter 3
39.How do insurance arrangements determine the applicable coverage pathway?
Distinguish the public program from the organization administering coverage. Medicare is a federal program; [Medicaid](https://www.medicaid.gov/medicaid) is state-administered under federal requirements and jointly funded. Private insurers also provide commercial coverage and administer government-benefit plans. [Medicare Advantage](https://www.medicare.gov/health-drug-plans/health-plans/your-health-plan-options) delivers Medicare benefits through approved private companies. In [Medicare Advantage plan comparisons](https://www.medicare.gov/health-drug-plans/health-plans/your-coverage-options/compare), HMOs generally require network care and specialist referrals, with specified exceptions; PPOs permit out-of-network care, often at greater cost, without specialist referrals. Verify the actual plan, network, referral, and authorization rules. For Medicare coverage review, apply governing policies effective on the service date within the relevant hierarchy and jurisdiction. A valid code alone does not establish coverage or medical necessity.
Apply it
A patient has a Medicare Advantage HMO card, so registration identifies that plan's claims destination and applicable network, referral, and authorization requirements rather than routing the claim as Original Medicare. For a separate denial involving an earlier service, the analyst checks the coverage policy effective on that service date rather than applying a later revision retroactively.
Common pitfall: A private insurer's name does not prove that coverage is commercial. PPO referral flexibility does not eliminate prior-authorization requirements. A local policy cannot override controlling national requirements.
AHIMA RHIT Content Outline, effective October 1, 2022 · Medicare Program Integrity Manual, Chapter 3 · Medicare NCCI FAQ Library | CMS
40.When can an NCCI modifier bypass a PTP edit?
A Medicare NCCI procedure-to-procedure edit identifies a code pair that generally should not be reported together for the same beneficiary, provider, and service date. A modifier indicator of 1 permits bypass under appropriate circumstances; 0 does not permit an NCCI-associated modifier to bypass the edit. The decisive cue combines the indicator with documented circumstances supporting the selected modifier. Separate billing lines or different diagnoses alone do not prove distinct services, and an indicator of 1 does not automatically authorize a modifier.
Apply it
A code pair has an active PTP edit with indicator 1. The coder reviews documentation for the relevant separate encounter or anatomical circumstances and uses an appropriate modifier only if those circumstances support it.
Common pitfall: Appending a modifier solely to obtain payment mistakes permission for justification. NCCI edits concern correct coding and do not independently establish medical necessity or prior authorization.
41.How should code descriptors, charge configuration, and MUEs control billed units?
The unit of service is defined by the code descriptor, not automatically by packages or physical items used. A charge description master change should align the documented service, code, unit conversion, effective date, and resulting claim. Test the downstream calculation before deployment. Then identify the MUE adjudication indicator: MAI 1 assesses each claim line; MAI 2 or 3 sums same-code units for the same provider, beneficiary, and date across lines. Splitting lines does not avoid a date-of-service MUE. Correct units and an accurately configured charge still do not independently establish coverage or medical necessity.
Apply it
A hypothetical supply code represents each 5 units of material. Documentation supports 20 units, so the billed quantity is 4 code units. HIM and billing test the CDM conversion on a sample encounter. In a separate example, two lines each report 3 units of the same code for the same provider, beneficiary, and date; a date-of-service MUE of 4 compares the combined 6 units, not each line's 3.
Common pitfall: Updating a code without testing conversion can multiply billing errors. Treating every MUE as a line-level limit ignores its adjudication indicator; passing an edit does not guarantee payment.
AHIMA RHIT Content Outline, effective October 1, 2022 · Medicare NCCI FAQ Library | CMS
42.What payment unit distinguishes common reimbursement methodologies?
Fee-for-service pays for individual covered services, often using a fee schedule. Per diem uses a covered day as its payment unit. Case-based prospective payment uses a discharge or case: under [Medicare IPPS](https://www.cms.gov/cms-guide-medical-technology-companies-and-other-interested-parties/payment/ipps), the hospital's base payment reflects the MS-DRG rather than separately reimbursing every item, with applicable adjustments and exceptions. Physicians' inpatient professional services are paid separately. [Capitation](https://www.cms.gov/priorities/innovation/key-concepts/capitation-and-pre-payment) pays a set amount per patient for a defined period and service scope. Prospective payment describes predetermined rates, not one universal payment unit; [CMS payment systems](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/html/medicare-payment-systems.html) include both case-based and per-diem arrangements.
Apply it
Compare hypothetical contracts paying $100 per visit, $500 per covered day, $8,000 per qualifying discharge, and $40 per enrolled patient per month for specified services. Identify service, day, case, and patient-period units before estimating payment. Under the stated case contract, an extra routine supply charge does not automatically add a separate payment.
Common pitfall: Charges are not the same as allowed payment. A prospective rate is not necessarily per discharge, and capitation does not mean that every possible service is included in the contracted scope.
AHIMA RHIT Content Outline, effective October 1, 2022 · Case Mix Index | CMS
43.How do remittance codes guide denial analysis?
Remittance advice communicates claim payment and adjustment information. Claim adjustment reason codes explain adjustments, while remittance advice remark codes can provide additional explanation. Analyze these codes with the adjustment group, claim details, and relevant documentation before selecting a response. The decisive cue is the actual reason and supporting detail, not the fact that payment is absent. Missing documentation, coding errors, and coverage issues require different corrective paths; a blanket resubmission or appeal may fail to address the stated problem.
Apply it
A Medicare remittance identifies a medical-necessity adjustment with a remark indicating a missing patient record. The analyst checks whether requested documentation was submitted and follows the appropriate response process rather than changing diagnosis codes without evidence.
Common pitfall: Reading a reason code without its related remark can miss the actionable detail. A denial does not justify altering documentation or coding simply to obtain payment.
CMS Health Care Payment and Remittance Advice · Medicare Program Integrity Manual, Chapter 3
44.What does a DNFB backlog reveal about the revenue cycle?
Discharged Not Final Billed identifies discharged accounts that have not reached final billing. Monitoring should distinguish account count, financial magnitude, age, and reason for delay. A backlog may arise from incomplete documentation, unresolved coding, or another stated billing dependency; the label alone does not identify the cause. The decisive cue is the distribution of delay reasons and aging. This turns a total into actionable workflow information and supports targeted work rather than assuming every delayed account represents a coding-productivity problem.
Apply it
A facility's DNFB report lists 80 accounts, including 50 awaiting provider clarification and 30 awaiting coding. HIM separates these queues and assigns follow-up to the responsible functions instead of treating all 80 as ready-to-code work.
Common pitfall: Account count alone conceals aging and financial differences. Moving an account out of DNFB without resolving its documentation or coding problem does not demonstrate improved integrity.
AHIMA RHIT Content Outline, effective October 1, 2022 · AHRQ: How to Map Workflows in Health Care Settings
45.How should a case-mix index be interpreted?
A case-mix index summarizes the average assigned relative weight for a defined set of cases. Calculate it by dividing the sum of case weights by the number of included cases, with consistent population and weighting definitions. The decisive cue is that it summarizes classification-related case mix rather than directly measuring coding accuracy, clinician quality, or financial success. A change can reflect a different patient population or changes in documentation and coding, so interpretation requires investigation rather than an automatic favorable or unfavorable conclusion.
Apply it
For an explicitly defined example population, three cases carry weights of 1.0, 1.5, and 2.0. Their index is 4.5 divided by 3, or 1.5. HIM examines population and documentation changes before interpreting a later increase.
Common pitfall: A higher index does not independently prove better coding or sicker individual patients. Comparing indexes built from different populations or weight versions can mislead.
AHIMA RHIT Content Outline, effective October 1, 2022 · CDC Principles of Epidemiology: Choosing Measures of Central Location and Spread · Case Mix Index | CMS
46.What does utilization review evaluate, and how does a questioned stay proceed?
Utilization review evaluates appropriateness, medical necessity, and conformity with professionally recognized care standards. Hospital review addresses admissions, duration of stays, and professional services; admission review can occur before, at, or after admission. Gather clinical documentation, apply relevant criteria, and route questioned cases to authorized clinical reviewers. Under the [CMS hospital guidance for 42 CFR 482.30](https://edit.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Downloads/som107ap_a_hospitals.pdf), the UR committee must consult the responsible practitioner before determining that an admission or continued stay is unnecessary. One committee member may decide when the practitioner concurs or does not present views after being afforded the opportunity; otherwise at least two members are required. The objective is appropriate care and supported resource use, not merely reducing billed days.
Apply it
A reviewer questions a continued stay because the available documentation does not demonstrate the applicable need. The case proceeds through clinical review and practitioner consultation, including consideration of additional documented information. Staff record the supported determination rather than automatically deny the stay because a screening criterion was not met.
Common pitfall: A screening flag is not a final necessity determination. NCCI correct-coding edits do not perform utilization review, and an HIM employee should not independently infer diagnoses to justify a stay.
AHIMA RHIT Content Outline, effective October 1, 2022 · som107c02.pdf · Medicare Program Integrity Manual, Chapter 3 · Medicare NCCI FAQ Library | CMS
Compliance13-17%
47.Which risks should receive compliance assessment attention?
A compliance risk assessment identifies potential problems and evaluates their likelihood, impact, and existing controls. OIG guidance supports an organization-specific approach informed by operations, prior findings, and changes in requirements. The decisive cue is the combined risk, not simply the easiest topic to audit or the largest number of transactions. Significant patient-information or payment consequences can justify attention even when volume is modest. Assessment should lead to a documented work plan that targets identified vulnerabilities and can be revised as evidence changes.
Apply it
A clinic identifies frequent low-impact formatting errors and a less frequent process that can disclose records to the wrong recipient. Its assessment considers consequences and control weaknesses when deciding which issue requires the more urgent compliance response.
Common pitfall: Ranking risks solely by volume overlooks serious low-frequency events. A copied work plan may miss vulnerabilities unique to the organization's services, systems, and prior findings.
48.How do routine monitoring and focused audits complement each other?
Routine monitoring follows process measures or control signals over time, while a focused audit examines selected transactions or records against defined criteria. Monitoring can reveal a trend requiring investigation; audit findings can explain whether the trend reflects actual noncompliance and what caused it. The decisive cue is the question being asked: detecting a signal differs from validating the underlying activity. Both need clear definitions and documented follow-up. A favorable dashboard cannot replace examination of records when the measure may conceal an important defect.
Apply it
A dashboard shows rising coding adjustments. Compliance conducts a focused record review to determine whether the increase reflects incorrect code assignment, a changed reporting definition, or another issue before directing corrective education.
Common pitfall: A trend is not a confirmed violation, and one audit snapshot does not establish sustained control. Treating either method as sufficient for every risk weakens oversight.
49.Why should corrective work investigate the cause of a defect?
Effective correction addresses how a defect arose rather than only repairing the affected records. Investigation may identify unclear instructions, system design, missing responsibility, insufficient training, or ineffective controls. The decisive cue is evidence connecting the process weakness to the repeated finding. OIG guidance supports responding to detected problems with corrective action and prevention. Different causes require different interventions: education fits a knowledge gap, whereas a faulty interface requires a technical change and validation of affected information.
Apply it
An audit finds repeated incorrect units on claims. Review shows that a charge configuration multiplies quantities automatically. Compliance coordinates configuration correction, review of affected claims, and validation instead of assuming that every biller needs the same refresher training.
Common pitfall: Blaming the last person in the workflow can overlook a system cause. Correcting sample records alone leaves the mechanism producing future errors intact.
HHS-OIG General Compliance Program Guidance, November 2023 · AHRQ: How to Map Workflows in Health Care Settings
50.What makes a corrective action plan operational?
A corrective action plan should connect a verified problem to actions, responsible owners, completion dates, and evidence used to judge results. It should address affected transactions as well as the process producing them when applicable. The decisive cue is whether someone can determine what must happen, who must do it, and how success will be assessed. OIG guidance supports corrective responses and ongoing oversight. A plan becomes operational through assigned work and measurable follow-up rather than through general promises to improve compliance.
Apply it
A release workflow sends some records to outdated destinations. The plan assigns contact verification changes, identifies an implementation owner and date, reviews affected releases, and specifies a follow-up sample to test the revised process.
Common pitfall: “Staff will be more careful” provides no defined control or accountable action. Completing a plan's tasks does not alone establish that the underlying risk decreased.
51.How can follow-up establish corrective action effectiveness?
Follow-up should evaluate the behavior or outcome the intervention was intended to change, using comparable criteria and a relevant post-implementation period. Training attendance or configuration completion establishes that an action occurred, not that it worked. The decisive cue is improved performance in affected transactions together with evidence that the improvement persists. OIG and Medicare corrective-action guidance emphasize evaluation and further response when problems continue. Interpret results in light of sample selection and definitions rather than assume every lower reported number represents genuine improvement.
Apply it
After coding education, an audit examines new records using the same error definition as the baseline review. Compliance compares error proportions and recurring categories, then continues targeted follow-up if the original pattern remains.
Common pitfall: A certificate of attendance does not demonstrate corrected coding. Comparing different audit populations or definitions can create an apparent improvement without a real change in practice.
HHS-OIG General Compliance Program Guidance, November 2023 · Medicare Program Integrity Manual, Chapter 3
52.How should regulatory changes move into daily operations?
Regulatory monitoring must connect a new requirement to the functions it affects, its applicability and effective date, and the changes needed before implementation. Assign owners to revise policies, system rules, forms, and education, then verify that the revised process operates correctly. The decisive cue is demonstrated deployment by the applicable date, not merely awareness of publication. Distinguish publication, effective, and implementation dates when the source separates them. Earlier transactions may remain governed by earlier requirements, so version control matters during transition.
Apply it
A new requirement changes a facility's documentation workflow on a stated effective date. Compliance identifies affected teams, updates instructions and system logic, trains staff, and tests the revised workflow before reviewing transactions under the new rule.
Common pitfall: Forwarding an announcement does not implement a requirement. Applying a new rule to earlier services without checking applicability can create incorrect audit findings or claim decisions.
HHS-OIG General Compliance Program Guidance, November 2023 · Medicare Program Integrity Manual, Chapter 3
53.What information makes a noncompliance report actionable?
An actionable report identifies the observed issue, relevant requirement or control, affected process, supporting evidence, and apparent extent while distinguishing confirmed facts from unresolved questions. Use the organization's reporting channels so concerns can be assessed and addressed by responsible personnel. The decisive cue is sufficient factual detail for investigation without unsupported accusations. OIG guidance emphasizes communication and response to detected issues. Reporting should preserve relevant evidence and avoid altering records to make the problem disappear before the appropriate review occurs.
Apply it
An employee identifies repeated shared-account use. The report describes the affected workflow, observed dates, and available access evidence through the compliance channel, allowing the organization to assess attribution risk and implement a supported response.
Common pitfall: Labeling an unexplained pattern as proven fraud exceeds the evidence. Omitting specific facts can also prevent investigators from locating the problem and evaluating its extent.
HHS-OIG General Compliance Program Guidance, November 2023 · HHS FAQ: Shared Log-on IDs and the Security Rule
54.Why are participation standards separate from claim coverage decisions?
Medicare conditions of participation establish standards for provider participation, while claim review evaluates coverage, coding, and payment for particular services. The Program Integrity Manual states that contractors should not deny payment solely because they believe a provider fails conditions of participation; the concern is referred to the appropriate oversight authorities. The decisive cue is the type of requirement implicated. A participation concern does not automatically establish a claim-payment error, and a correctly paid claim does not establish compliance with every participation standard.
Apply it
A Medicare reviewer notices a possible participation-standard problem while examining a claim. The service otherwise satisfies applicable payment requirements. The reviewer distinguishes the claim determination from referral of the participation concern to the appropriate authorities.
Common pitfall: Denying every associated claim solely for a participation concern conflates oversight functions. Conversely, satisfactory claim coding does not excuse an identified participation-standard deficiency.
Medicare Program Integrity Manual, Chapter 3 · som107c02.pdf
Leadership9-12%
55.How does mapping the current workflow improve process review?
A current-state workflow map represents how work actually moves through a process, including decisions, queues, and handoffs. AHRQ recommends understanding the process before designing changes. The decisive cue is observed practice rather than an idealized policy sequence. Mapping helps a team identify duplication, delays, missing inputs, and activities that depend on another department. It also gives participants a shared basis for discussing improvement. A proposed future process should then be assessed against the identified problem rather than adopted solely because it looks simpler.
Apply it
HIM maps the actual discharge-to-billing process with coding and clinical staff. The map shows records repeatedly returning for the same missing information, helping the team redesign that handoff instead of increasing effort at every step.
Common pitfall: Mapping only the policy omits workarounds and real bottlenecks. A shorter diagram does not prove an improved process if required checks or responsibilities disappear.
56.When are swim lanes useful for departmental handoffs?
Swim lanes arrange workflow activities by the person, role, or department responsible for them. They make handoffs visible and help reveal activities with unclear ownership or unnecessary transfers. The decisive cue is a process involving multiple participants whose responsibilities are difficult to distinguish in a simple sequence. Each activity should appear in the appropriate lane, with movement showing when responsibility changes. The diagram supports collaboration by clarifying work ownership, but the team must still agree on the operational rules and responsibilities represented.
Apply it
A clarification process stalls between coding, clinicians, and billing. The team creates swim lanes showing who initiates the request, who answers it, who updates coding, and who releases the account, exposing an unassigned follow-up step.
Common pitfall: Naming departments on a diagram does not resolve ambiguous responsibility by itself. A handoff should identify the required output, not merely show an arrow between teams.
57.How should policies and procedures work together?
A policy establishes an organization's rule or expectation, while a procedure describes the actions used to carry it out. Their content should align with applicable requirements and actual workflow. The decisive cue is whether staff can translate the rule into a consistent action, including exceptions and escalation when needed. Revision should involve affected functions and controlled approval and distribution. A clear policy without a workable procedure can produce inconsistent practice, while a detailed procedure that conflicts with governing requirements can standardize the wrong behavior.
Apply it
A facility policy requires attributable record corrections. Its procedure specifies the authorized EHR function, author and date identification, preserved original content, and escalation when a user cannot complete the correction through the standard workflow.
Common pitfall: Copying another organization's procedure may conflict with local systems or responsibilities. Approval alone does not ensure that affected staff receive and can apply the revised instructions.
HHS-OIG General Compliance Program Guidance, November 2023 · Medicare Program Integrity Manual, Chapter 3
58.Which evidence shows that education produced applied competence?
Role-specific education should prepare staff to perform the decisions required by their work. Attendance establishes exposure; a realistic demonstration or review of subsequent work provides evidence of applied competence. The decisive cue is correct performance using relevant facts, such as distinguishing treatment disclosure from internal access or executing a proper correction. Education should address the actual responsibility and identified gap. OIG guidance supports tailored training and communication, with follow-up used to determine whether the organization needs further instruction or a different intervention.
Apply it
After privacy training, release staff review sample requests and explain the disclosure basis, minimum-necessary applicability, and required safeguards. Supervisors then review actual work for the same decisions rather than rely solely on course completion records.
Common pitfall: A high satisfaction rating measures reaction, not correct performance. Testing irrelevant legal trivia also fails to establish competence in the employee's assigned workflow decisions.
HHS-OIG Compliance 201 for Health Care Providers · HHS-OIG General Compliance Program Guidance, November 2023
59.How should interoperability testing protect information meaning?
Interoperability requires collaboration so that transferred information remains correctly attributed and usable in the receiving workflow. Testing should compare source and destination values, patient identity, units, dates, and relevant interpretations or status indicators. The decisive cue is preserved meaning, not simply successful message transmission. An interface can deliver a message without accurately representing its content. HIM contributes knowledge of record integrity and downstream use, while technical and clinical partners verify the elements needed for the receiving system's actual decisions.
Apply it
An interface test confirms that messages arrive, but HIM notices that the receiving report associates a result with the wrong encounter. The team validates identity linkage and receiving-system display before approving routine exchange.
Common pitfall: A successful transport log proves delivery, not correct attribution or interpretation. Testing only one typical record can miss exceptions affecting names, units, or encounter relationships.
AHIMA RHIT Content Outline, effective October 1, 2022 · SAFER Guide: Patient Identification
60.Why do project plans need dependencies and acceptance criteria?
A project plan connects a defined objective to deliverables, responsible participants, dependencies, milestones, and criteria for acceptance. Dependencies identify work that must finish before another task can succeed, such as approving a workflow before training users. Acceptance criteria define observable evidence that the deliverable meets its intended purpose. The decisive cue is readiness demonstrated by results rather than a date on the schedule. The RHIT outline includes project-management principles; applying them helps coordinate HIM changes across departments without mistaking task completion for operational success.
Apply it
A template project requires approved content before configuration and validated configuration before training. The plan assigns these dependencies and defines acceptance as correct behavior in agreed test cases, with affected departments confirming readiness before routine use.
Common pitfall: Training against an unapproved workflow creates avoidable rework. Declaring success because every task is checked off overlooks whether the resulting process actually meets the stated objective.
AHIMA RHIT Content Outline, effective October 1, 2022 · AHRQ: How to Map Workflows in Health Care Settings
What to focus on during revision
The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.
- Use the complete official task outline as your scope map; prioritize record integrity and revenue-cycle decisions while maintaining coverage of all six domains.
- Distinguish duplicates, overlays, demographic discrepancies, and uncertain matches before choosing consolidation or separation.
- Separate designated-record-set access, psychotherapy-note and litigation exclusions, permitted disclosures, minimum-necessary exceptions, and internal role-based access.
- Apply Safe Harbor date, age, and ZIP-population boundaries while checking all identifiers and actual knowledge of identifiability.
- Write the numerator, denominator, observation unit, and time definition before calculating or interpreting a performance measure.
- Identify inpatient versus outpatient setting, documentation certainty, permissible supplementary documentation, and applicable coding dates before choosing a coding action.
- Distinguish service, day, case, and patient-period payment units; identify the actual insurance arrangement and utilization-review pathway.
- Distinguish NCCI coding edits from medical-necessity review, and read modifier or MUE indicators before proposing a claim correction.
- Connect audit evidence to causes, assigned corrective work, comparable follow-up measurements, and clear departmental handoffs.
A practical preparation plan
1. Map every official task
Build a study checklist from the outline effective October 1, 2022. Mark each task as explainable, applicable, or needing review. Use this selective guide to develop decisions while checking the official outline for tasks requiring additional study.
2. Practise record and privacy distinctions
For each mini-case, identify the record owner, information category, purpose, and applicable authority. Explain why a merge, correction, disclosure, or access restriction is supported before considering competing actions.
3. Calculate and interpret together
Recalculate the statistics examples by hand. State what each result measures, what it does not establish, and which denominator or definition change would invalidate comparison.
4. Trace coding and denial decisions
Work from setting and documented facts to classification instructions, coverage requirements, edit indicators, and remittance details. Identify the insurance arrangement and payment unit, and distinguish utilization review from coding edits. Keep coding correctness, coverage, and participation compliance as separate analytical questions.
5. Review errors by mechanism
Complete the 20 questions before reading explanations. For each error, identify the missed cue and explain why every alternative is less appropriate. Use flashcards to recall mechanisms, then revisit the related concept with a new example.
6. Demonstrate transfer across domains
Explain an end-to-end case from registration through documentation, coding, billing, audit, and corrective action. Identify information handoffs, responsible roles, and evidence of improvement without treating a practice score as a certification pass prediction.
Use your sample score as a starting point
The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.
Start the free sampleOfficial sources and updates
- Registered Health Information Technician (RHIT) | AHIMA
- AHIMA RHIT Content Outline, effective October 1, 2022
- Medicare Program Integrity Manual, Chapter 3
- SAFER Guide: Patient Identification
- Registrar Playbook, Chapter 2: Capturing Patient Demographic Data
- HHS FAQ: Information Individuals Have a Right to Access
- HHS Minimum Necessary Requirement
- HHS FAQ: Shared Log-on IDs and the Security Rule
- HHS Guidance on De-identification of Protected Health Information
- HHS FAQ: Medical Record Retention
- CDC Principles of Epidemiology: Frequency Measures
- CDC Principles of Epidemiology: Choosing Measures of Central Location and Spread
- CDC Field Epidemiology Manual: Describing Epidemiologic Data
- ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027
- CMS: How to Use the Medicare NCCI Tools
- CMS Health Care Payment and Remittance Advice
- HHS-OIG General Compliance Program Guidance, November 2023
- HHS-OIG Compliance 201 for Health Care Providers
- AHRQ: How to Map Workflows in Health Care Settings
- Medicare NCCI FAQ Library | CMS
- som107c02.pdf
- r12633pi.pdf
- Case Mix Index | CMS
Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.