10.1 Official Guidelines and Code Assignment

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.

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

1. Confirm the encounter setting and applicable code set.
2. Review provider documentation and required reports (operative, pathology, discharge summary).
3. Apply the Official Guidelines, code conventions, and facility policy.
4. 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.
5. Validate the resulting grouping and claim effect.
6. 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.