Study guide
1.5 Passing Score and Score Interpretation
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
1.5 Passing Score and Score Interpretation
Key Takeaways Explain This Topic AI
The RHIA passing score is a scaled score of 300 on a 100–400 scale.
Do not convert 300 into a fixed percent-correct target; scaled scoring adjusts for form difficulty.
The 20 pretest items do not count, but candidates cannot identify them, so every item must be answered.
A score plan should target domain balance, careful scenario reading, and an error log that reduces avoidable mistakes.
Last updated: June 2026
Understanding the 300 Passing Score
The official RHIA passing score is 300 , reported on a scaled range (commonly described as 100–400). Treat 300 as the threshold to remember. It is unhelpful to convert it into a fixed percent-correct target because AHIMA uses scaled scoring : raw correct answers are converted so that scores are comparable across exam forms of slightly different difficulty. A harder form may require fewer raw correct answers to reach 300 than an easier form.
Why scaled scoring matters for strategy
Because you cannot know the conversion in advance, chasing "I need 70% correct" is a trap — the real requirement is a scaled 300, which corresponds to demonstrating competency across the blueprint, not hitting an exact raw percentage. Practically, this means broad, balanced mastery beats narrow excellence in one domain.
- Score fact Candidate response
- Passing score is a scaled 300 Memorize the threshold; ignore unofficial percent conversions
- 130 items are scored Cover the full five-domain blueprint, not favorites
- 20 items are pretest (unscored) Do not spend energy detecting them
- Pretest items are randomly distributed Keep steady pacing start to finish
- Scaled scoring adjusts for form difficulty Aim for competency, not an exact raw target
- Domain-balanced preparation
RHIA is broad. A candidate strong in coding validation but weak in information governance, privacy workflows, analytics, or leadership decisions can still fall short of 300. Recall from the blueprint that Data Analytics and Informatics (23-26%) and Management and Leadership (23-26%) carry the most weight, followed by Revenue Cycle Management (20-23%), with Data and Information Governance (17-20%) and Compliance (15-18%) the lightest. Allocate study hours proportionally rather than by comfort.
Avoidable errors are usually reading errors
Scenario items hinge on qualifier words: first, best, most appropriate, monitor, validate, escalate, audit, implement . An administrator-level item may list two or three plausible actions; the credited answer best aligns with policy, law, stakeholder need, data integrity, patient rights, reimbursement accuracy, or governance.
Worked example. A question asks what to do first after discovering a possible PHI breach. "Notify affected patients" and "document the incident" are both real steps, but the first defensible action is typically to contain the breach and begin the risk assessment under the organization's incident-response policy — reading the qualifier first changes the answer.
Build an error log
After each practice set, classify missed items by domain, task, and error type — forgotten fact, misunderstood workflow, weak concept, or rushed answer. That turns a raw score into a work plan and prevents overstudying a topic you enjoy while ignoring point-costing weak spots.
Exam-day behavior
Use the navigation tools to support accuracy: select an answer before moving on, flag questions for review, and return before submitting if time remains. The goal is not a perfect first read but fewer preventable mistakes across all 150 items.
Know that the passing standard is a scaled 300.
Answer every item because pretest items are unlabeled.
Allocate study time to the heaviest-weighted domains.
Make targeted review part of the pacing plan.
How AHIMA sets the standard
The scaled 300 cut score is not arbitrary; it derives from a formal standard-setting study (often a modified-Angoff process) in which subject-matter experts judge the difficulty of each item and the level a minimally competent RHIA should achieve. That panel work establishes the raw passing point, which is then placed on the 100–400 scale and held constant as 300 across forms through equating . The takeaway for candidates is that the bar reflects competency , not a curve against other test-takers on the same day — you are not competing with the people in the room; you are being measured against a fixed professional standard.
Reading the score report
Whether you pass or fail, AHIMA provides a score report. A passing report confirms the credential; a failing report typically shows performance by domain so you can target remediation. Use that breakdown literally: if the report flags Data Analytics and Informatics and Management and Leadership, those carry the heaviest weights (23-26% each), so even modest gains there move the scaled score the most. Do not over-react to a single weak domain that carries lower weight, such as Compliance (15-18%); fix it, but prioritize the high-weight domains for the largest score impact.
Guessing strategy
Because there is no penalty for wrong answers , never leave an item blank. If you cannot reason to a single best answer, eliminate clearly wrong options to improve the odds, choose the best remaining one, flag it, and move on. With four options, eliminating even one raises a blind guess from 25% to 33%. The disciplined sequence — eliminate, commit, flag, return if time allows — protects both your accuracy and your pacing, and it ensures all 150 items receive an answer before submission.
A concrete domain-allocation example
If a candidate has 60 study hours left, a weight-proportional split might be roughly 15 hours each to Data Analytics and Informatics and Management and Leadership, 13 to Revenue Cycle Management, 10 to Data and Information Governance, and 7 to Compliance, then adjust upward for any domain the practice error log flags as weak. Letting the blueprint weights and your error log jointly steer study time is the most reliable route to a scaled 300.