Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

MTY1106 HEALTH INFORMATION SYSTEM FOR MEDICAL TECHNOLOGY (Lecture)

W8
HMIS Data Quality
Ms. Jilian Vanessa Lopez | FEU BS Medical Technology 2023 L8
reference: LOT QUALITY ASSURANCE SAMPLING (LQAS)
HIS for MLS book, handout, lec video
- A tool that allows the use of small random samples to
distinguish between different groups of data elements
OBJECTIVES
(or Lots) with high and low data quality.
At the end of the lesson, the students should be able to:
- Has been widely applied in the healthcare industry for
1. Discuss data quality, quality assessment, and
decades and has been primarily used for quality
development implementation plan
assurance of products.
2. Explain the importance of data quality tools
- The concept and application of LQAS have been adopted
3. Differentiate the different techniques used in root cause
in the context of District Health Information System
analysis
(DHIS) data quality assurance.
DATA QUALITY Steps in Applying LQAS
- Over the years data quality has become a major concern
1. Define the service to be assessed (e.g., DQA of DHIS)
for large companies especially in the areas of customer
2. Identify the unit of interest: a supervisory area, facility,
relationship management (CRM), data integration, and
hospital, district
regulation requirements. Aside from the fact that poor
3. Define the higher and lower thresholds of performance
data quality generates costs, it also affects customer
based on prior information about the expected
satisfaction, company reputation, and even the strategic
performance of the region of interest
decisions of the management
4. Determine the level of acceptable error
- Data quality – the overall utility of a dataset(s) as a
5. From a table, determine the sample size and decision rule
function of its ability to be processed easily and analyzed
for acceptable errors to declare an area as performing
for a database, data warehouse, or data analytics system.
“below expectation”
- Data quality signifies the data’s appropriateness to
6. The number of errors observed (mismatched data
serve its purpose in a given context. Having quality
elements will determine reliability if the facility is
data means that the data useful and consistent.
performing above or below expectation)
- Data cleansing can be done to raise the quality of
available data (Rouse, 2005).
ROUTINE DATA QUALITY ASSESSMENT TOOL (RDQA)
ASPECTS OF DATA QUALITY - A simplified version of the Data Quality Audit (DQA) which
▪ Accuracy – Indicates whether the data is free from allows programs and projects to verify and assess the
significant errors and whether the number seems to make quality of their reported data
sense - It aims to strengthen their data management and
▪ Completeness – Indicates whether there is enough reporting systems.
information to draw a conclusion about the data and
whether enough individuals responded to it to ensure the Objectives
representativeness ✓ Rapidly verify the quality of reported data for key
▪ Update status – The data are up-to-date, and indicators at selected sites.
information is available on time. ✓ Implement corrective measures with action plans for
▪ Relevance – Data should have sufficient detail strengthening data management and reporting system
▪ Consistency – Considers the extent to which data is and improving data quality.
collected using the same process and procedures by ✓ Monitor capacity improvements and performance of
everyone doing the collection and in all locations data management and reporting system to produce
overtime. quality data.
▪ Reliability – The data are measured and collected
consistently over time. The RDQA is a multipurpose tool that is most effective when
▪ Appropriate presentation – If it is suitable for the routinely used. Following are the uses for the RDQA tool
intended purpose. (RDQA User Manual, 2015):
▪ Accessibility – should be easily accessed data
RDQA Use Case Example
TWO TECHNIQUES TO CHECK HMIS DATA ACCURACY: Routine data quality Routine data quality checks
checks as part of on- can be included in already
✓ Lot quality Assurance Sampling (LQAS)
going supervision planned supervision visits at
✓ Routine Data Quality Assessment (RDQA)
the service delivery sites

L. MELANA | 2021 Page 1 of 4


MTY1106 HMIS Data Quality

Initial and follow-up Repeated assessments (e.g., ▪ Designate team member responsibilities
assessments of data biannually, or annually) of a - Create a general team plan with overall roles that
management and system’s ability to collect and each team member will play
reporting systems report quality data at all levels ▪ Define metrics for success
can be used to identify gaps - How will you determine if you have achieved
and monitor necessary your goal?
improvements.
Strengthening of the Monitoring and evaluation
program’s staff capacity (M&E) staff can be trained on DATA QUALITY TOOLS
in data management the RDQA and sensitized to - A data quality tool analyzes information and identifies
and reporting the need to strengthen the key incomplete or incorrect data.
functional areas linked to data - Data cleansing follows after the complete profiling of data
management and reporting in concerns, which could range anywhere from reviewing
order to produce quality data. abnormalities to merging repeated information.
Preparation for a formal The RDQA tool can help - By maintaining data integrity, the process enhances the
data quality audit identify data quality issues and reliability of the information being used by the
areas of weakness in the data organization.
management and reporting - Usually, this data quality software products can share
system that would need to be features with master data management, data integration,
strengthened to increase or big data solutions.
readiness for a formal data
quality audit. - Gartner (2017) explain how these data quality tools are
External assessments Such use of the RDQA for used to address problem in data quality:
by partners of the external assessments could be
quality of data more frequent, more ▪ Parsing and Standardization
streamlined, and less resource - Refers to the decomposition of fields into
intensive than comprehensive component parts and formatting the values into
data quality audits that used consistent layout based on industry’s standards
DQA version for auditing. and patterns and user-defined business rules.
▪ Generalized “cleansing”
- The modification of data values to meet domain
DEVELOPMENT IMPLEMENTATION PLAN restrictions, constraints on integrity, or other
- An implementation plan is a project management tool that rules that define data quality as sufficient for the
illustrates how a project is expected to progress at a high organization.
level. ▪ Matching
- It helps ensure that a development team is working to - The identification and merging of related entries
deliver and complete tasks on time (Visual Paradigm, within or across data sets
2009). ▪ Profiling
- It is also important in ensuring the efficient flow of - Refers to the analysis of data to capture
communication between those who are involved in the statistics, or metadata to determine the quality of
project so as to minimize issues that would delay delivery the data and identify data quality issues
of the project ▪ Monitoring
- Validates the estimation and schedule of the project plan. - Refers to the deployment of controls to ensure
conformity of data to business rules set by the
- It is developed through the following key steps organization
(Smartsheet, 2017) ▪ Enrichment
- The enhancement of the value of the data by
▪ Define Goals/objectives using related attributes from external sources
- Address the question, “What do you want to such as consumer demographic attributes or
accomplish?” geographic descriptors.
▪ Schedule Milestones
- Outline the deadline and timeline in the
implementation phase
▪ Allocate resources
- Determine whether you have sufficient
resources and decide how you will procure those
missing.

L. MELANA | 2021 Page 2 of 4


MTY1106 HMIS Data Quality

ROOT CAUSE ANALYSIS - It lays down the potential causes in a bar graph
- A root cause analysis is a problem solving method that and track the collective percentage in a line
identifies the root causes of the problems or events graph to the top of the table.
instead of simply addressing the obvious symptoms.
- The aim is to improve the quality of the products by using ▪ Fault Tree Analysis (FTA)
systematic ways in order to be effective (Bowen, 2011). - Used in risk and safety analysis
- Among the core building blocks in the continuous - Uses a Boolean logic to determine the root
improvement efforts of an organization in terms of its cause of an undesirable event
operation dynamics, especially in the way it handles
information.
- Root cause analysis alone will not produce any valuable
results.

TECHNIQUES IN ROOT CAUSE ANALYSIS

▪ Failure Mode and Effects Analysis (FMEA)


- FMEA aims to find various modes of failure
within a system and address the following
question for execution: - The undesirable event is listed at the top of the
o What is the mode in which an observed tree and then all the potential causes are listed
failure occurs? down to form the shape of an upside-down tree
o How many times does a cause of failure
occur?
o What actions are implemented to ▪ Currently Reality Tree (CRT)
- Used when the root causes of multiple problem
prevent this cause from occurring
need to be analyzed all at once.
again?
o Are these actions effective and
efficient?
- Used when there is a new product or process or
when there are changes or updates in a product
and when a problem is reported through
customer feedback.

- The problems are listed down followed by the


potential cause for a problem. By doing so, a
cause common to all problems will appear.

▪ Fishbone
▪ Pareto Analysis - Also called Ishikawa or Cause and-effect
- Uses the Pareto Principle which states that 20 diagrams
percent of the work creates 80 percent of the - The diagram looks like a fishbone as it shows
results. the categorized causes and sub causes of a
- Used when there are multiple potential causes problem.
to a problem

- This diagraming technique is useful in grouping


causes into categories (could be 4Ms, 4Ss,
8Ps)

L. MELANA | 2021 Page 3 of 4


MTY1106 HMIS Data Quality

▪ Kepner-Tregoe Technique
- Breaks a problem down to its roots cause by KEY POINTS TO REMEMBER
assessing a situation using priorities and orders ✓ Data quality is the overall utility of a data set(s) as a
of concern specific issues function of its ability to be processed easily and analyzed
- The various decisions that should be made to for a data base, data warehouse, or data analytics
address the problem are then outlined. system.
- Then a potential problem analysis is made to ✓ Lot Quality Assurance Sampling (LQAS) is a tool that
ensure that the actions recommended are allows the use of small random samples to distinguish
sustainable. between different groups of data elements (or lots) with
high and low data quality.
✓ The Routine Data Quality Assessment (RDQA) is a
simplified version of the data quality audit (DQA) which
allows programs and projects to verify and assess the
quality of their reported data.
✓ The development of an implementation plan is important
in ensuring that the communication between those who
are involved in the project will not encounter any issues
and work will also be delivered on time.
▪ Rapid Problem Resolution Problem Diagnosis ✓ A root cause analysis is a problem-solving method aimed
- Diagnoses the causes of recurrent problems by at identifying the root causes of problems or events
following the three phases below instead of simply addressing the obvious symptoms.
o Discover – data gathering and analysis of ✓ Techniques in root cause analysis include failure mode,
the findings and effects analysis (FMEA), Pareto Analysis, Fault Tree
o Investigate – creation of a diagnostic plan Analysis, Currently Reality Tree, Fishbone or Ishikawa or
and identification of the root cause through Cause and-effect diagrams, Kepner-Tregoe Technique,
careful analysis of the diagnostic data and RPR Problems Diagnosis
o Fix – fixing the problem and monitoring to
confirm and validate that the correct root
cause was identified

Sustaining a Culture of Information Use


- Choo, Bergeron, Detlor, and Heaton (2008) state that
information culture affects outcomes of information
use.
- The information culture is determined by the
following variables: mission, history, leadership,
employee traits, industry, and national culture.
- Information culture can also be shaped by cognitive
and epistemic expectations which are influenced by
the way tasks are performed and decisions are
made.

L. MELANA | 2021 Page 4 of 4

You might also like