Study guide

10.1 Official Guidelines and Code Assignment

RHIA Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: RHIA Eligibility, Application, Fees, Format, Scoring, and Retakes

1.1 RHIA Purpose and Administrator-Level Scope 1.2 HIM-Only Eligibility Routes 1.3 MyAHIMA Application, Transcripts, and the 120-Day Scheduling Window 1.4 Fees, Format, and Appointment Time 1.5 Passing Score and Score Interpretation 1.6 Retakes, Certification Maintenance, and Current Statistics

2 2023 RHIA Outline, Exam Functionality, Pretest Items, and Study Strategy

2.1 Current 2023 Outline and Why It Controls Study 2.2 Domain Weights and Study-Time Allocation 2.3 Scored Items, Pretest Items, and Answer Discipline 2.4 Navigation, Flagging, Review, and Submit Workflow 2.5 Test Center Day and No-Resource Requirement 2.6 Official Task-Based Study Strategy

3 Data and Information Governance I: Documentation Integrity and Quality Reporting

3.1 Documentation Integrity as Governance 3.2 Complete, Accurate, and Timely Records 3.3 Documentation Standards and Clarification Workflows 3.4 Clinical Data Elements for Quality Reporting 3.5 Data Quality Validation for Reporting 3.6 Governance Committees, Metrics, and Remediation

4 Data and Information Governance II: Data Dictionaries, Retention, MPI, and Policy

4.1 Data Dictionary Standardization 4.2 Documentation and Data Standards 4.3 Data Analysis to Inform Management 4.4 Policies and Procedures for Information Governance 4.5 Retention and Destruction Policies 4.6 Master Patient Index Integrity

5 Compliance I: Access, Use, Disclosure, Patient Rights, ROI, and HIE

5.1 Domain 2 Compliance Decision Frame 5.2 Patient Access and Portal Governance 5.3 Advocacy for Patients and Families 5.4 ROI Intake, Validation, and Scope Control 5.5 Disclosure Documentation and Audit Trails 5.6 HIE and External Access Governance

6 Compliance II: Security, Breach Workflows, Cybersecurity, and Disaster Recovery

6.1 Request Workflow Controls and Escalation 6.2 Breach Protocols from Report to Resolution 6.3 Privacy and Security Initiatives 6.4 Cybersecurity Risks for HIM Leaders 6.5 Disaster Recovery and Downtime Readiness 6.6 Monitoring, Metrics, Tabletops, and Continuous Improvement

7 Data Analytics and Informatics I: EHR Support, Reporting, Databases, and Dashboards

7.1 EHR Support and HIM Administration 7.2 Reporting Lifecycle and Data Requests 7.3 Visualizations, Dashboards, and Executive Views 7.4 Database Management and Data Dictionaries 7.5 Data Mining and Analytics Workflows 7.6 Statistics Validation for Stakeholders

8 Data Analytics and Informatics II: CDI, Workflows, HIE, Integrations, and SDLC

8.1 Focused Documentation Audits for CDI, Quality, and Safety 8.2 CDI Workflows and Query Governance 8.3 Workflow Optimization Through Health Information Technology 8.4 HIE Governance and Exchange Controls 8.5 Software Integrations and Health Information Impact 8.6 Systems Development Life Cycle and HIM Participation

9 Revenue Cycle Management I: Reimbursement, Coding Validation, CDI, and Claims

9.1 Domain 4 Revenue Cycle Management Frame 9.2 Reimbursement Models and Provider Education 9.3 Coding Accuracy Validation Controls 9.4 HHS Documentation Requirements and CDI 9.5 Claims Workflow and Clean-Claim Controls 9.6 CDM, DNFB, and A/R Management

10 Revenue Cycle Management II: Revenue Integrity, Denials, Fraud, and Official Guidelines

10.1 Official Guidelines and Code Assignment 10.2 Groupings and Payment Data Validation 10.3 Revenue Integrity Program Design 10.4 Coding Audits, Monitoring, and Corrective Action 10.5 Denials Management and Appeals 10.6 Fraud Prevention and Compliance Escalation

11 Management and Leadership: Strategy, HR, Work Design, Training, Budgeting, and Projects

Strategy, Goals, and Change Management Contracting and Outsourcing Governance Human Resources, Staffing, and Performance Work Design and Process Improvement Training and Development Budgets, Accreditation, Compliance, and Projects

12 Final RHIA Review: Domain Integration, Exam Week, and Career Next Steps

Integrated Scenario Patterns Across Domains Final Week Domain-Weighted Review Test-Center Day, Functionality, and Pacing Results, Retakes, and RHIA Maintenance RHIA, RHIT, CHDA, CHPS, and CCS Career Map Readiness Checklist and Next-Step Plan

10.1 Official Guidelines and Code Assignment

Key Takeaways Explain This Topic AI

AHIMA's RHIA Domain 4 (Revenue Cycle Management) tests diagnosis and procedure code assignment under official guidelines, not coding for the highest payment.

The ICD-10-CM/PCS Official Guidelines for Coding and Reporting are FY-dated (Oct 1 to Sep 30) and approved by the four Cooperating Parties: AHA, AHIMA, CMS, and NCHS.

When documentation, guidelines, and payment preference conflict, the documented record and official guidelines control the code, not reimbursement.

The RHIA manages the system around assignment: reference access, query policy, audits, escalation, and grouper controls.

Last updated: June 2026

Official Guidelines as the Revenue Cycle Anchor

The RHIA exam is 150 multiple-choice questions (130 scored, 20 unscored pretest) over 3.5 hours , with a scaled passing score of 300 on a 100–400 scale. Revenue Cycle Management is Domain 4 of the five RHIA domains, weighted 20-23%. Within it, AHIMA tests diagnosis and procedure code assignment and groupings under official guidelines . The phrasing matters: revenue cycle management is never a license to pick codes by desired payment. The provider documentation, code-set conventions, the ICD-10-CM/PCS Official Guidelines for Coding and Reporting , and facility policy define what may be reported.

The Official Guidelines are fiscal-year dated (October 1 through September 30) and are approved by the four Cooperating Parties : the American Hospital Association (AHA) , American Health Information Management Association (AHIMA) , the Centers for Medicare & Medicaid Services (CMS) , and the National Center for Health Statistics (NCHS) . The FY 2026 set took effect October 1, 2025. A common trap answer cites an outdated edition; the credible RHIA always uses the guidelines current for the date of service.

What the RHIA Actually Controls

A coder applies guidelines to one record. The RHIA administrator manages the system that helps coders apply them consistently: current reference access, training, query policy , audit criteria, escalation, encoder/grouper edits, and provider feedback. When claims, denials, or audits surface errors, the RHIA uses official rules to decide whether the root cause is documentation, coding, charge capture, payer interpretation, or workflow.

Scenario clue Guideline-centered action Trap (weak) answer

Principal diagnosis disputed Apply UHDDS definition ("condition established after study chiefly responsible for admission") and official sequencing Choose the diagnosis paying the most

Procedure code shifts the DRG Validate the operative report and PCS rules Accept the higher-weighted result without review

Condition clinically plausible but undocumented Issue a compliant, non-leading query Code from lab values or indicators alone

Payer requests records Compare submitted codes, documentation, and payer policy first Send records without confirming the claim is defensible

  • Repeated audit errors Fix education, policy, or edits Treat each finding as one coder's isolated mistake
  • Setting Drives the Rules

Setting changes the code set and rules. Inpatient facility coding uses ICD-10-CM diagnoses plus ICD-10-PCS procedures and follows UHDDS sequencing into MS-DRGs . Outpatient facility and professional coding use CPT/HCPCS with modifiers, ICD-10-CM for medical necessity, and report under APCs or the physician fee schedule. A guideline that is correct inpatient — for example, coding a condition documented only as "possible," "probable," or "rule out" as if confirmed — is forbidden in the outpatient setting , where uncertain diagnoses are not coded.

The exam may not require code lookup, but it will ask which rule applies and who resolves the question.

A Defensible Assignment Process

Confirm the encounter setting and applicable code set.

Review provider documentation and required reports (operative, pathology, discharge summary).

Apply the Official Guidelines, code conventions, and facility policy.

Issue a compliant query when documentation is ambiguous, incomplete, conflicting, or imprecise — following the AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice : queries must be non-leading and may not suggest a higher-paying diagnosis.

Validate the resulting grouping and claim effect.

Trend repeated variances for education, workflow fixes, or compliance referral.

On the exam, reject answers that bypass this process: holding only the claims that reduce payment, coding conditions because they appear in lab data, or ignoring denials without record review. The credible answer is methodical — define the rule, apply it to the documentation, preserve the audit trail, and fix the process that produced the variance.

A Worked Sequencing Example

Consider an inpatient admitted with chest pain who, after study, is found to have an acute non-ST-elevation myocardial infarction (NSTEMI); the chest-pain symptom is integral to the confirmed condition. Under the UHDDS (Uniform Hospital Discharge Data Set) definition, the principal diagnosis is the condition established after study to be chiefly responsible for the admission — here the NSTEMI, not the presenting symptom. A coder who sequences "chest pain" first because it appears earliest in the chart has applied the wrong rule and will produce the wrong MS-DRG.

The RHIA control that prevents this is not a one-off correction; it is sequencing education plus a second-level review trigger on symptom-versus-definitive-diagnosis conflicts.

Now add a query dimension. Suppose the discharge summary says "troponin elevation" but never states "NSTEMI." The coder cannot assume the diagnosis from the lab value alone — coding from lab data is a classic exam trap. The correct move is a compliant, non-leading query : it presents the clinical indicators (troponin, symptoms, EKG findings) and asks the provider to clarify the diagnosis without naming or suggesting the higher-paying answer.

Per the AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice , a query that says "Please document NSTEMI to support DRG assignment" is leading and non-compliant ; one that lists indicators and asks the provider to specify is acceptable.

Distinguishing the RHIA Lens from the Coder Lens

Exam stems frequently present a coding dispute and ask what the administrator should do. The coder-level answer is "assign the correct code." The RHIA-level answer addresses the system: was the reference current, was the query policy followed, does the audit plan catch this error type, and is the variance trending across a service line? Choosing the systems answer over the single-chart answer is how Domain 4 items separate administrators from coders. Official guideline discipline is what keeps reimbursement defensible when the claim is supported and protects the organization when a requested change is not.