Free RHIA Exam Flashcards

RHIA is AHIMA's administrator-level health information management credential. Think governance, compliance, analytics, revenue cycle, and leadership - not coding-only recall.

Current routes are HIM-specific: CAHIIM-accredited baccalaureate or master's HIM academic requirements, a CAHIIM-approved post-baccalaureate HIM certificate, or approved foreign HIM reciprocity.

Confirm eligibility, apply through MyAHIMA with required documentation, receive eligibility, then schedule the computer-based exam through Pearson VUE.

After eligibility is granted, the candidate must schedule with Pearson VUE within 120 days. Study readiness should be mostly in place before that window starts.

130 items are scored. The exam has 150 total items because 20 pretest items are mixed in and are not identified to candidates.

The appointment is 3 hours 30 minutes total. AHIMA breaks it into 5 minutes of agreement time and 3 hours 25 minutes of exam time.

300 is the official scaled passing score. Do not turn it into a fixed raw-percent target because scoring is based on AHIMA's scale.

$229 for AHIMA members and $299 for non-members. Retake fees are the same as the first-attempt exam fee.

The candidate submits a new application and fee. RHIA retake approval requires a 30-day wait before scheduling.

RHIA uses a 2-year certification period. Credential holders must complete recertification requirements, including required CEUs and the recertification fee.

Data Analytics and Informatics and Management and Leadership are each weighted 23-26%, the largest ranges in the current outline.

It protects health information across its lifecycle by assigning accountability for integrity, availability, confidentiality, usability, retention, and destruction.

The definition tells the organization which records make up the official business record for legal, evidentiary, retention, and disclosure purposes.

The original entry remains visible, the correction is dated and attributable, and the audit trail shows what changed, who changed it, and why.

It defines data element names, meanings, formats, allowed values, sources, owners, and business rules so users and systems interpret data consistently.

A reliable Master Patient Index links the right patient to the right records. Duplicates, overlays, and demographic errors can affect safety, reporting, billing, and privacy.

Follow the governing retention schedule, apply the most stringent applicable rule, pause destruction for holds, and document authorized destruction.

High-quality data is accurate, complete, consistent, timely, valid, reliable, accessible for the right purpose, and traceable to trusted sources.

Validate definitions, source data, mappings, time period, denominator logic, and workflow inputs before redesigning the dashboard or reporting conclusions.

Ask the purpose, authority, requester identity, requested scope, recipient, minimum necessary boundary, and whether policy requires escalation.

Use, request, or disclose only the PHI reasonably needed for the intended purpose, except where HIPAA or policy allows a broader treatment-related use.

Request intake, identity and authority validation, scope review, sensitive-information checks, delivery controls, disposition notes, quality review, and escalation rules.

Make access practical while controlling identity proofing, proxy authority, portal enrollment, delivery tracking, support, denial reasons, and complaint escalation.

It shows what was requested, what authority was verified, what was released, to whom, when, by whom, and under which purpose or legal basis.

Escalate under policy, contain the issue, preserve evidence, investigate facts, assess risk, decide notifications, remediate, and document the full response.

Health information exchange can support continuity of care, but it requires governance for participation, consent or preference rules, matching, access controls, monitoring, and breach escalation.

They protect electronic PHI through administrative, physical, and technical controls such as policies, access management, facility controls, audit logs, and transmission protections.

Stakeholders act on those numbers. Validate definitions, denominators, source systems, missing values, outliers, population mix, time period, and limitations before decisions are made.

Define the workflow problem, involve stakeholders, validate requirements, test realistic records, train users, monitor adoption, and watch for new data quality defects.

Start with the business or clinical question. Then select data, prepare it, analyze, validate, interpret, act, and monitor results.

Data lineage traces data from origin through movement, transformation, reporting, and use. It supports trust, troubleshooting, compliance, and governance decisions.

A useful audit has a clear objective, population, sample method, criteria, trained reviewers, escalation path, feedback loop, and corrective-action monitoring.

It controls clinical indicators, nonleading query format, tracking, provider response monitoring, escalation rules, education, and links to coding and quality reporting.

HIM should participate in planning, requirements, design, testing, implementation, maintenance, change control, downtime planning, and retirement of systems affecting health information.

Missing documents, duplicate patients, broken report counts, incorrect statuses, interface errors, delayed claims, or privacy audit gaps can all signal integration problems.

Protect compliant documentation and reliable coded data first. Revenue speed matters, but it cannot override documentation, official guidance, payer rules, or compliance risk.

Clean claims start before billing through complete documentation, accurate coding, charge capture, authorization checks, edit resolution, and cross-functional handoffs.

Compare coded data to documentation, official coding guidelines, facility policy, payer requirements, and audit criteria. Payment impact alone never proves correctness.

CDI improves clarity and completeness so records accurately support severity, risk, quality reporting, coding, reimbursement, and defensible claims.

Discharged not final billed analysis shows accounts delayed before billing. Sort by root cause and owner, such as coding, documentation, charge, edit, or authorization issues.

It is revenue integrity work that aligns services, supplies, codes, prices, units, departments, payer rules, and change control so charges are accurate and supportable.

Denial trends should feed root-cause review, provider education, coding validation, CDI priorities, payer-policy updates, CDM review, and appeal strategy.

Escalate through compliance channels, preserve evidence, stop unsupported practice, investigate facts, correct claims if needed, and monitor for recurrence.

Use evidence, policy, stakeholder input, risk assessment, communication, training, measurable action, and follow-up instead of isolated quick fixes.

Stakeholder mapping, current-state analysis, clear communication, training, support, go-live planning, resistance management, metrics, and sustained adoption monitoring.

Use workload volume, productivity, quality, turnaround time, risk, competency, service levels, budget impact, and regulatory or accreditation requirements.

Effective training has objectives, role-based content, practice, competency validation, coaching, and follow-up audit data showing whether behavior improved.

Define scope, privacy and security duties, service levels, quality measures, reporting, handoffs, escalation, audit rights, and corrective-action expectations.

Begin with baseline data and root-cause analysis. Then redesign the workflow, assign owners, train staff, measure results, and monitor for unintended effects.

Evidence of policy ownership, current procedures, staff competency, audits, corrective actions, monitoring, and leadership follow-through.