A data quality plan describes how the study will prevent, detect, manage, and report quality problems. It may be a standalone document or part of the broader data management plan.
The plan should be prepared before data collection begins and should be reviewed whenever the protocol, database, or workflow changes.
The plan should identify critical data and critical processes. Critical data are data that affect participant safety, primary and secondary outcomes, eligibility, informed consent, regulatory reporting, or key analysis variables. Critical processes are study processes that, if performed poorly, could compromise participant protection or data reliability. Examples include consent documentation, randomization, adverse event reporting, laboratory result transfer, and primary outcome assessment.
The plan should define the checks to be performed. These may include missing form reports, range checks, date logic checks, duplicate checks, cross-form consistency checks, adverse event reconciliation, laboratory reconciliation, query aging reports, audit trail review, and site performance dashboards. Each check should have an owner, frequency, expected action, and escalation pathway.
Frequency should be risk-based. Some checks may run daily, such as serious adverse event review or safety dashboard monitoring. Others may run weekly, such as missing forms, entry lag, and open queries. Some may run monthly, such as site trend reviews or audit trail sampling. The plan should also specify what happens when problems are detected. Who raises queries? Who responds? When are unresolved issues escalated? How are repeated problems handled?
Data quality planning is not only technical. It requires collaboration with investigators, coordinators, monitors, and statisticians. The statistician may identify variables that require special cleaning rules. Coordinators may identify workflow constraints. Monitors may identify source verification priorities. Investigators may decide clinical plausibility rules. The data manager integrates these perspectives into a practical quality plan.
Foundations of Clinical Research Data Management
An introductory course covering how clinical research data is collected, managed, cleaned, and prepared for analysis while ensuring quality and regulatory compliance.
0/12
Protocol Translation and Case Report Form (CRF) Design
Focuses on translating study protocols into structured data requirements and designing clear, accurate Case Report Forms (CRFs) that support efficient and compliant data collection.
0/12
Database Design in REDCap
The REDCap database design phase transforms well-designed CRFs into a functional electronic data capture system.
0/15
Data Entry, Validation, and Access Control
This chapter explores the operational aspects of data collection within REDCap, including data entry workflows, validation procedures, user rights management, audit trails, and quality assurance activities that help ensure research data remain reliable and compliant with regulatory standards.
0/12
Data Quality Management and Query Resolution
This topic is about ensuring that data is accurate, complete, and consistent. It covers identifying, investigating, and correcting errors or discrepancies in data. It also focuses on timely resolution of data queries to maintain data integrity and reliability.
0/13
Introduction to R for Clinical Data Management.
This topic introduces R, an open-source programming language used for statistical analysis, data management, and visualization. In clinical research, R is applied to clean, analyze, and report data in a reproducible and reliable manner.
0/1