Purpose of Root Cause Analysis
Root cause analysis is a structured method for identifying the underlying cause of a problem rather than simply addressing its symptoms. RHIA candidates should recognize root cause analysis as a critical tool used after sentinel events, near misses, and recurring quality or coding errors to prevent recurrence.
The Five Whys Technique
The five whys technique involves repeatedly asking "why" a problem occurred, typically five times, drilling down from the immediate symptom to the systemic cause. For example, asking why a medication error occurred might eventually reveal that a system-level labeling issue, rather than an individual's carelessness, was the true root cause.
Fishbone or Ishikawa Diagrams
A fishbone diagram organizes potential causes of a problem into categories, often including people, process, equipment, materials, environment, and management, visually mapping how multiple contributing factors converge to produce the observed effect. This tool helps teams avoid fixating on a single obvious cause and instead consider the full range of contributing factors.
Applying Root Cause Analysis in HIM
- Investigating a spike in coding-related claim denials to determine whether the cause is a documentation gap, a coder training issue, or a system edit failure
- Analyzing a data breach to determine whether the root cause was a technical vulnerability, a policy gap, or a training deficiency
- Reviewing a sentinel event involving misidentified patient records to trace the failure back to a specific step in the registration workflow
Failure Mode and Effects Analysis
Unlike root cause analysis, which is reactive and examines an event that has already occurred, failure mode and effects analysis is a proactive tool that evaluates a process before failure occurs, scoring potential failure points by severity, likelihood of occurrence, and detectability to prioritize preventive action.
Documentation and Action Planning
A thorough root cause analysis concludes with a documented action plan assigning responsibility, timelines, and measurable outcomes for each corrective action, along with a follow-up mechanism to verify the action was implemented and effective.
Exam Tip
Be able to distinguish reactive tools, such as root cause analysis and the five whys, from proactive tools, such as failure mode and effects analysis, since exam questions often test this timing distinction.