Human Resources, Staffing, and Performance

HR Decisions in HIM Operations

Human resources is part of Domain 5 because people are a central control in HIM operations. Staff decisions affect documentation integrity, ROI workflows, coding accuracy, data reporting, privacy monitoring, and revenue cycle performance. The exam often puts you in a manager role and asks for the next best action when performance is weak, workloads shift, or a new requirement changes the work.

Diagnose before you discipline

A strong HR answer starts with diagnosis. If turnaround is poor, ask whether volume rose, the queue changed, staffing is short, training is incomplete, or the system is slow. If one employee repeatedly mishandles requests after clear training and documented feedback, progressive discipline may apply: the standard sequence is verbal warning, written warning, suspension, then termination, with documentation at each step. If the entire team struggles after a new EHR workflow, the answer is workflow review and retraining, not discipline.

Staff with data: FTE and productivity math

Staffing plans use numbers, not headcount guesses. A common exam calculation uses the full-time equivalent (FTE): one FTE equals 2,080 paid hours per year (40 hours x 52 weeks), or about 1,840 productive hours after subtracting paid time off and breaks. Productivity benchmarks let you convert volume to FTEs. For example, inpatient coding runs roughly 2 to 3 charts per hour and outpatient/ED coding much faster. If a facility codes 24 inpatient charts per shift and a coder averages 3 per hour over a 7.5-hour productive day (about 22.5 charts), you need just over one coder per shift, plus coverage for absence and complexity.

Competency, fairness, and traps

Competency validation matters because mistakes create access delays, privacy incidents, claim problems, or bad data. A sign-in sheet proves attendance, not competence; stronger validation uses case examples, observed work, quality review, system demonstrations, or post-training audits. Performance management must be fair and documented: staff need clear duties, current procedures, training, feedback, and the tools to do the work before corrective action is defensible.

Common traps: choosing the most forceful answer (termination) without first checking expectations, tools, training, and process design; supporting a staffing request with "everyone feels busy" instead of volume, backlog age, productivity, quality, and risk data; and counting attendance as proof of competency. A staffing proposal at the RHIA level explains the operational need, the supporting data, the expected benefit, and the risk of doing nothing.

Job descriptions, recruitment, and the legal frame

AHIMA expects RHIA leaders to understand the HR lifecycle and its legal guardrails. A job description anchors recruitment, performance standards, and competency expectations; it lists essential functions, which matters under the Americans with Disabilities Act (ADA) when evaluating reasonable accommodation. Interviewing must avoid questions about protected characteristics under Title VII of the Civil Rights Act (race, color, religion, sex, national origin), the Age Discrimination in Employment Act (ADEA), and the ADA.

The Fair Labor Standards Act (FLSA) governs overtime and the exempt/non-exempt classification that drives how a backlog can be staffed with extra hours. On the exam, an interview question about an applicant's age, religion, or disability is the wrong choice; a question about ability to perform essential functions is correct.

Structuring performance management

Performance management is a cycle, not an annual event: set clear standards, observe and document, give timely feedback, and use a performance improvement plan (PIP) with specific goals and a defined review period before escalating. Progressive discipline (verbal, written, suspension, termination) protects both the employee and the organization by creating a documented, defensible record. The exam keys to the next proportionate step, never skipping straight to termination for a first, training-related error.

Retention, engagement, and the cost of turnover

Turnover is expensive: replacing a skilled coder or ROI specialist can cost a large fraction of annual salary in recruiting, onboarding, and lost productivity, and it raises compliance risk while new staff learn. The RHIA leader analyzes turnover drivers, workload, scheduling, recognition, career growth, supervision, and addresses the root cause rather than simply rehiring into the same conditions. Cross-training and succession planning reduce single-point-of-failure risk and improve coverage during absences.

A retention strategy framed around engagement, clear career ladders, and competitive scheduling is the administrator-level answer; reactively backfilling positions without diagnosis is the trap. Tying every HR decision back to documentation integrity, privacy, revenue, and data quality is what distinguishes RHIA-level reasoning from line-supervisor habit.