Study guide
9.4 HHS Documentation Requirements and CDI
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
9.4 HHS Documentation Requirements and CDI
Key Takeaways Explain This Topic AI
Tasks 3 and 4 of Domain 4 cover monitoring HHS (CMS/OIG) documentation requirements and conducting CDI for revenue and quality improvement.
A compliant query clarifies documentation that is conflicting, incomplete, ambiguous, or illegible without leading the provider toward a specific, payment-favorable answer.
AHIMA's query practice brief allows multiple-choice, open-ended, and yes/no formats but prohibits leading queries and queries unsupported by clinical indicators.
CDI outcomes are measured across revenue, quality, denial, provider response, and documentation-integrity indicators — not payment alone.
Last updated: June 2026
HHS Documentation Requirements
Domain 4 Task 3 is monitoring U.S. Department of Health and Human Services (HHS) clinical documentation requirements. In practice this means tracking the rules set by HHS agencies — chiefly the Centers for Medicare & Medicaid Services (CMS) through its Conditions of Participation, manuals, and National/Local Coverage Determinations, and the Office of Inspector General (OIG) through its Work Plan and compliance guidance. These define what documentation must exist to support a service: a signed and dated note, authentication of orders, medical necessity, and timely completion.
Key documentation anchors the RHIA monitors:
Authentication — every entry signed/dated by its author; CMS prohibits unsigned or back-dated entries.
Medical necessity — documentation must support that the service was reasonable and necessary (NCD/LCD criteria).
Completeness and timeliness — records completed within facility/medical-staff deadlines, supporting POA and discharge coding.
Copy-forward control — cloned notes are an OIG audit target; the record must reflect the current encounter.
CDI as Documentation Governance
Domain 4 Task 4 is conducting clinical documentation integrity (CDI) activities for revenue and quality. The exam framing is critical: CDI improves the clarity, completeness, consistency, and reliability of the record. Better-paying claims and better quality scores are downstream effects of accurate documentation, never the stated goal. A CDI program that exists only to raise the case-mix index is the wrong answer.
The central CDI tool is the compliant query . A query is appropriate when documentation is conflicting, incomplete, ambiguous, imprecise, illegible, or clinically inconsistent. Per AHIMA's Guidelines for Achieving a Compliant Query Practice , a query must be supported by clinical indicators in the record and must not lead the provider toward a particular answer.
Query attribute Compliant Non-compliant (exam trap)
Trigger Conflicting, ambiguous, or incomplete documentation with clinical indicators A desire to reach a higher-weight DRG
Format Open-ended, multiple-choice with clinically reasonable options, or yes/no Forces a single diagnosis the provider has not documented
- Tone Presents indicators, asks for clarification Suggests the "correct" answer or implies financial impact
- Options Includes "unable to determine" / "clinically undetermined" Offers only the payment-favorable choice
- Record Query and response retained per policy Verbal query with no documentation trail
- A Worked Example
A patient has a documented sodium of 128 mEq/L, fluid restriction, and hypertonic saline orders, but no diagnosis of hyponatremia. A compliant multiple-choice query lists the clinical indicators and offers options including hyponatremia, another clinically reasonable cause, "other," and "clinically undetermined." A leading query that simply states "Please document hyponatremia" is non-compliant because it supplies the answer without letting the provider exercise clinical judgment.
Measuring CDI
Measure CDI across a balanced set of indicators so the program is judged on integrity, not just dollars:
Query metrics — query rate, response rate, and agreement rate.
Documentation impact — CC/MCC capture, specificity improvement, SOI/ROM (severity of illness / risk of mortality) shifts.
Quality — accuracy of risk-adjusted measures, mortality and complication indices.
Revenue — case-mix index trend and DRG shifts, reviewed for plausibility, not as a target.
Denials — reduction in clinical-validation and documentation-related denials.
Common Exam Traps
The wrong answers issue leading queries, query without clinical indicators, set DRG or CMI targets for CDI staff, or hide queries from the record. The defensible choice clarifies genuine ambiguity, offers clinically reasonable options including an undetermined choice, documents the query and response, and measures the program on documentation integrity and quality alongside revenue. When a stem describes a query that names a single diagnosis with no alternatives, recognize it as leading and reject it.
Verbal Queries and the Documentation Trail
Queries may be written or verbal, but every query and its response must be documented and retained according to facility policy. A verbal query left unrecorded is non-compliant because it cannot be audited and creates the appearance that a diagnosis was added through undocumented conversation. The exam often hides this defect inside an otherwise reasonable query: the clinical indicators are present and the options are fair, but the query was made by phone with no record. Recognize that as the flaw.
The compliant practice memorializes the verbal exchange in the record, including who was queried, the indicators presented, and the provider's response.
Equally important, the query response must result in a documented diagnosis in the body of the record before it is coded. A provider answering a query form is not enough on its own; the agreed diagnosis must appear in a signed progress note or discharge summary so the code rests on the record, not on the query form alone. This protects the code if the claim is later audited.
When Not to Query, and Retrospective Limits
The administrator must also know when a query is inappropriate. Do not query to confirm a diagnosis that is already clearly and consistently documented, do not query without clinical indicators in the record, and do not issue a query whose only purpose is to reach a higher-weight DRG. Post-discharge and retrospective queries are permitted but carry tighter rules: they should still be supported by clinical indicators present at the time of care, and they must not introduce conditions the record never suggested. A pattern of post-bill queries that consistently raise the DRG is itself an OIG audit flag.
Finally, governance the program with a query policy approved by HIM, CDI, the medical staff, and compliance, defining triggers, formats, escalation for unanswered queries, and retention. When a stem pits a CDI specialist against a provider who will not respond, the defensible answer escalates through the documented policy and the medical staff, never by the CDI specialist resolving the ambiguity unilaterally or coding an unsupported diagnosis.