Troubleshooting Logic Model
1. Observe or recognize symptoms.
A working knowledge of how a system operates to obtain results helps an operator recognize symptoms when something is wrong.
Example observations:
- Error codes or messages generated
- Symptoms (noises, leaks, trends in controls)
2. Categorize symptoms into categories of variables that can affect the generation of a result.
Symptoms can be categorized into the variables that affect the generation of a result. This allows the operator to group like symptoms or problems together to focus on the steps needed to isolate a root cause. Without performing this step, a novice may jump down to resolution steps before they have identified the root cause. This results in wasted time and money.
Example variables:
- Analyzer
- Reagent
- Operator
- Environment
3. Isolate the root cause using diagnostic tools.
It is important that diagnostic, maintenance or analytical tools are used to identify the root cause before repair or replacement procedures begin. This saves time, money and frustration.
Example tools:
- Operation Manual Instructions
- Error message descriptions
- Logs - instrument error or message logs, maintenance logs, etc.
- Maintenance procedures
- Diagnostic procedures
- Troubleshooting flowcharts
4. Resolve the problem.
Once the root cause is identified, then resolution procedures can be done. This reduces the chances of changing components unnecessarily.
Example resolution steps:
- Adjust (tighten connections, remove jams)
- Calibrate (system or assay calibrations)
- Replace or Repair components
- Run new control bottle or lot number
5. Verify the resolution worked.
To verify if the resolution worked, the same isolation/diagnostic tools used to identify the root cause can be performed. The operator could then assay control material before analyzing patient samples.
Example verifications:
- Use the same diagnostic procedures as used in step 3
- Check control values, if appropriate
