0% found this document useful (0 votes)
8 views

3. [MIDTERMS] HMIS Data Quality

2nd Year | Health Information System

Uploaded by

Johan Malabanan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views

3. [MIDTERMS] HMIS Data Quality

2nd Year | Health Information System

Uploaded by

Johan Malabanan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Medical lab.

science 1st semester


S.y 2024 - |
2025
health information system
[TRANS] HMIS data quality
Outline  Helps ensure that a development team is working to deliver and
a. Data quality complete tasks on time.
a. Lot quality assessment (LQAS)  Ensure that the communication between those who are
involved in the project will not encounter any issues.
b. Routine data quality assessment
sampling (RDQA)
c. Development implementation plan Data quality tools
b. Data quality tools  Analyzes information and identifies incomplete or incorrect
c. Techniques in root cause analysis data.
a. Ask why 5 times  Cleansing such data follows after the completion of the
b. Failure mode and effects analysis profiling of data concerns, which could range anywhere from
removing abnormalities to merging repeated information.
(FMEA)
c. Pareto analysis
Parsing and standardization
d. Fault tree analysis
 Refers to the decomposition of fields into component parts and
e. Current reality tree (CRT)
formatting the values into consistent layouts based on industry
f. Fishbone/ishikawa/cause-and-
standards and patterns and user-defined business rule.
effect diagrams
g. Kepner-tregoe technique
Generalizes “Cleansing”
h. Rpr problem diagnosis  Means the modification of data values to meet domain
restrictions, constraints on integrity or other rules that define
Data quality data quality as sufficient for the organization.
 The overall utility of a datasets(s) as a function of its ability to
be processed easily and analyzed for a database, data matching
warehouse, or data analytics system.  This is the identification and merging related entries within or
across data sets.
Low data quality
 Generates costs. profiling
 Affects the customer satisfaction, company’s reputation and  Refers to the analysis of data to capture statistics or metadata
even the strategic decisions of the management. to determine the quality of the data and identify data quality
issues.
High data quality
 Useful and consistent. monitoring
 Data cleansing can be done to raise the quality of available  The deployment of controls to ensure conformity of data to
data. business rules set by the organization.

Lot quality assessment sampling enrichment


 Enhancing the value of the data by using related attributes from
 A tool that allows the use of small random samples to
external sources such as consumer demographic attributes or
distinguish between different groups of data elements (or Lots)
geographic descriptors.
with high and low data quality.

Techniques in root cause analysis (RCA)


Routine data quality assessment sampling
 A class of problem solving methods aimed at identifying the
 A simplified version of the Data Quality Audit (DQA) which
root causes of the problems or events instead of simply
allows programs and projects to verify and assess the quality of
addressing the obvious symptoms.
their reported data.
 Among the core building blocks in the continuous improvement
 Aims to strengthen their data management and reporting
efforts of the organization.
systems.
 Keep in mind that root cause analysis alone will not produce
any results.
Development implementation plan
 Project management tool that shows how a project will evolve
Ask why 5 times
at a high level.

“They made it hard on purpose” – Meredith Grey Johan


|1
(Lecture) hmis data quality | HIS
 By identifying the problem, and then asking “WHY” five times –  No matter what term you use for the fishbone diagram, the
getting progressively deeper into the problem, the root cause truth is, that it is a useful technique that will help you in your
can be strategically identified and tackled. root cause analysis.
Failure mode and effects analysos (FMEA)  A fisbone diagram will group causes into categories including:
o People
 Is a technique which is aimed to find various modes for failure
within a system o Measurements
 FMEA is often performed and updated any time when: o Methods
o A new product or process is generated o Materials
o When changes are made to current conditions, or to o Environment
the design o Machines
o When new regulations occur
o When there is a problem determined through
customer feedback

Pareto analysis
 Operates using pareto Principles (20% of the work creates 80%
of the results).
 Runs any time when there are multiple potential cause to a Kepner-tregoe tregoe technique
problem.  Also known as rational process is intended to break a problem
down to its root causes by not only identifying the causes but
Fault tree analysis by appraising the situation as well.

 Uses Boolean logic to determine the root causes of an


undesirable event.
 This technique is usually used in risk analysis and safety
analysis.

RPR problem diagnosis


 Deals with diagnosing the causes of recurrent problems.
1. Discover – team members gather data and analyze
their findings.
2. Investigate – a diagnostic plan is created and the root
Current reality tree
cause is identified through careful analysis of the
 Analyzes a system at once. It would be used when many diagnostic data.
problems exist and you want to get to the root causes of all the 3. Fix – the problem is fixed and monitored to ensure
problems. that the proper root cause was identified.

Fishbone/ishikawa/cause-and-effect diagrams

“They made it hard on purpose” – Meredith Grey Johan


|2

You might also like