HMIS DATA QUALITY AN IMPLEMENTATION PLAN HAS THE FOLLOWING

KEY COMPONENTS:
DATA QUALITY - the overall utility of a dataset(s) as a 1. Define Goal/Objectives: Answers the question “What
function of its ability to be processed easily and analyzed do you want to accomplish?”
for a database, data warehouse, or data analytics system. 2. Schedule Milestones: Outline the high-level schedule in
the implementation phase.
ASPECTS OF DATA QUALITY 3. Allocate Resources: Determine whether you have
• Accuracy sufficient resources, and decide how you will procure
• Completeness what’s missing.
• Update Status 4. Designate Team Member Responsibilities: Create a
• Relevance general team plan with overall roles that each team
• Consistency member will play.
• Reliability 5. Define Metrics for Success: How will you determine if
• Appropriate Presentation you have achieved your goal? (Smartsheet, 2017).
• Accessibility
DATA QUALITY TOOLS
ROUTINE DATA QUALITY ASSESSMENT (RDQA) A Data quality tool analyzes information and identifies
The Routine Data Quality Assessment Tool (RDQA) is a incomplete or incorrect data. Cleansing such data follows
simplified version of the Data Quality Audit (DQA) which after the completion of the profiling of data concerns,
allows programs and projects to verify and assess the which could range anywhere from removing abnormalities
quality of their reported data. It also aims to strengthen to merging repeated information.
their data management and reporting systems. By maintaining data integrity, the process enhances the
reliability of the information being used by a business.
The objectives of RDQA are as follows: Usually these data quality software products can share
VERIFY RAPIDLY IMPLEMENT MONITOR features with master data management, data integration,
1.) the quality of Corrective measures Capacity or big data solutions.
reported data for key with action plans for improvements and
indicators at selected strengthening the performance of the As data quality becomes increasingly all encompassing,
sites and data management data management currently, data integration tools usually include data
2.) the ability of and reporting system and reporting system
data-management and improving data to produce quality quality management functionality.
systems to collect, quality data.
manage and report
quality data. GARTNER (2017) defines these Data Quality tools
used to address the data quality problem:
DEVELOPMENT IMPLEMENTATION PLAN PARSING AND STANDARDIZATION – refers to the
decomposition of fields into component parts and
An Implementation Plan is a project management tool formatting the values into consistent layouts based on
that shows how a project will evolve at a high level. An industry standards and patterns and user-defined business
implementation plan helps ensure that a development rules
team is working to deliver and complete tasks on time GENERALIZED “cleansing” – means the modification of
(Visual Paradigm, 2009). data values to meet domain restrictions, constraints on
integrity or other rules that define data quality as
The development of an Implementation Plan is sufficient for the organization
important to ensure that the communication between MATCHING – this is the identification and merging related
those who are involved in the project will not encounter entries within or across data sets
any issues and work will also be delivered on time. The PROFILING – refers to the analysis of data to capture
plan validates the estimation and schedule of the project statistics or metadata to determine the quality of the data
plan. and identify data quality issues
MONITORING – the deployment of controls to ensure
conformity of data to business rules set by the
organization
ENRICHMENT – enhancing the value of the data by using
related attributes from external sources such as consumer
demographic attributes or geographic descriptors
WHAT IS A ROOT CAUSE ANALYSIS?
A root cause analysis is a class of problem solving
methods aimed at identifying the root causes of the
problems or events instead of simply addressing the
obvious symptoms.
The aim is to improve the quality of the products by using
systematic ways in order to be effective (Bowen,2011).
TECHNIQUES IN ROOT CAUSE ANALYSIS
Root cause analysis is among the core building blocks in
the continuous improvement efforts of the organization.
1. ASK WHY 5 TIMES
This might sound like the technique of a five-year-old
wanting to get out of going to bed, but the five whys
analysis can be quite useful for getting to the underlying
causes of a problem. By identifying the problem, and then
asking "why" five times -getting progressively deeper into
the problem, the root cause can be strategically identified
and tackled.
2. FAILURE MODE AND EFFECTS ANALYSIS (FMEA)
The failure mode and effects analysis (FMEA) is a
technique which is aimed to find various modes for failure
within a system. FMEA requires several steps for
execution:
1.All failure modes (the way in which an observed failure
occurs) must be determined.
2.How many times does a cause of failure occur?
3.What actions are implemented to prevent this cause
from occurring again?
4.Are the actions effective and efficient?
FMEA is often performed and updated any time a new
product or process is generated, when changes are made
to current conditions, or to the design, when new
regulations occur, or when there is a problem determined
through customer feedback.
3. FAULT TREE ANALYSIS (FTA)
uses boolean logic to determine the root causes of an
undesirable event. This technique is usually used in risk
analysis and safety analysis. At the top of the fault tree,
the undesirable result is listed. From this event, all
potential causes tree down from it. Each potential cause is
listed on the diagram in the shape of an upside down tree.
4. CURRENT REALITY TREE (CRT)
The current reality tree analyzes a system at once. It
would be used when many problems exist and you want to
get to the root causes of all the problems. The first step in
creating a current reality tree is listing all of the
undesirables or, problems. Then begin a chart starting with
each of those problems using causal language
(if...and...then). The tree will depict each potential cause
for a problem. Eventually, the tree will show one cause
that is linked to all four problems.
5. FISHBONE OR ISHIKAWA OR CAUSE-AND-EFFECT
DIAGRAMS
No matter what term you use for the fishbone diagram,
the truth is, that it is a useful technique that will help you
in your root cause analysis. A fishbone diagram will group
causes into categories including:
• People
• Measurements
• Methods
• Materials
• Environment
• Machines
6. KEPNER-TREGOE TECHNIQUE
The Kepner-Tregoe technique, also known as rational
process is intended to break a problem down to its root
cause. This process begins with an appraisal of the
situation-what are the priorities and orders for concerns
for specific issues? Next, the problem analysis is
undertaken to get to the cause of undesired events. Then,
a decision analysis is tackled, outlining various decisions
that must be made. Finally, a potential problem analysis is
made to ensure that the actions decided upon in step
three are sustainable.
7. RPR PROBLEM DIAGNOSIS
One final technique used in root cause analysis is the RPR Problem
Diagnosis. RPR stands for “Rapid Problem Diagnosis” and it deals
with diagnosing the causes of recurrent problems.
• Discover – team members gather data and analyze their
findings
• Investigate – diagnostic plan is created and the root cause
is identified through careful analysis of the diagnostic data
• Fix – the problem is fixed and monitored to ensure that the
proper root cause was identified.