Clinical data are collected. Evidence must be built.
From data collection to reliable clinical evidence.
Clinical Data Management is more than collecting, cleaning and delivering datasets. It translates clinical research requirements into structured, traceable, quality-controlled data processes that support reliable analysis and interpretation [2,4].
My approach combines hands-on experience across clinical studies, data standardisation and digital solutions with a commitment to making complex data management principles understandable and applicable.
Collecting data is not the same as ensuring data quality.
A technically valid dataset can still contain inconsistencies, ambiguous definitions, missing information or data that are difficult to interpret in their clinical context.
Ambiguous definitions
Variables and clinical concepts interpreted differently [2, 4]
Limited traceability
Insufficient visibility into changes and data provenance [1, 3]
Inconsistent data
Conflicting values, formats and relationships [2, 4]
Late quality detection
Issues discovered when correction is costly or impractical [1]
Data quality begins before the first patient is enrolled. [2]
CLINICAL DATA MANAGEMENT ACROSS THE STUDY LIFECYCLE
Clinical Data Management spans study planning, conduct and closure. Its activities overlap, evolve and require coordination across multiple functions. The six operational stages below provide a structured view of this work, while the timeline illustrates how responsibilities interact throughout the study.
STUDY PLANNING
STAGE 01
Protocol & Data Requirements
Study objectives, endpoints, variables and data specifications.
STAGE 02
Data Collection Design
CRFs, eCRFs, metadata, edit checks and validation plans.
STUDY CONDUCT
STAGE 03
Data Acquisition & Integration
Clinical data capture, external sources and data reconciliation.
STAGE 04
Data Review & Quality Control
Queries, data cleaning, review and discrepancy resolution.
STUDY CLOSURE
STAGE 05
Database Finalisation
Final checks, reconciliation and database lock.
STAGE 06
Analysis-Ready Data & Preservation
Documented data delivery, statistical analysis support and archiving.
Clinical Operation
Data Management
Regulatory activities
Hospital activities
Monitoring
Statistics
Colours identify the functional areas involved in each stage; segment widths do not represent workload or responsibility.
CONTINUOUS PRINCIPLES
Data Quality
Quality built into study design, data collection and review.
Risk Management
Controls proportionate to risks affecting critical data and processes.
Traceability
Documented data origin, transformations and changes.
Change Control
Controlled and documented changes to systems, specifications and data.
These principles apply throughout study planning, conduct and closure. They inform how clinical data are designed, collected, reviewed and managed, rather than representing separate sequential activities. [1, 2, 4]
Timeline adapted from the author’s Clinical Data Management teaching materials (University of Milano-Bicocca, MEDAL programme). Illustrative sequence; actual activities and timelines vary by study.
Three lessons from the timeline
01 — Quality starts before enrolment
Protocol review, CRF design, eCRF implementation and data validation planning begin during study preparation, before the first patient is enrolled.
02 — Data review is iterative
Data capture, queries and cleaning overlap during study conduct. Quality control is an ongoing activity, not a single step performed before database lock.
03 — Database lock is not the end of the study
Database lock marks a key data finalisation milestone, while statistical analysis, reporting and other study closure activities may continue afterwards.
MY APPROACH
Clinical understanding first. Reliable data by design.
My approach to Clinical Data Management combines an understanding of clinical requirements, structured data processes and practical solutions to data complexity. The goal is to make clinical data reliable, interpretable and fit for their intended use.
01 — Understand the clinical context
Start from study objectives, clinical workflows and the meaning of each data element—not simply from the fields to be collected.
02 — Design for quality and traceability
Translate requirements into consistent data structures, validation rules and documented processes that support quality throughout the study.
03 — Turn complexity into usable data
Address fragmented sources, inconsistent formats and operational constraints through standardisation, integration and pragmatic automation.
FROM PRACTICE TO EVIDENCE
Making clinical data usable in the real world.
Clinical Data Management becomes valuable when sound principles translate into practical solutions. The following examples illustrate how I have addressed clinical complexity, data quality and heterogeneous information across different research settings.
CASE 01 · CLINICAL CONTEXT
Standardising data across multiple clinics
Challenge — Different clinical workflows and data definitions made information difficult to compare across centres.
Action — Worked on a shared data dictionary and the standardisation of clinical variables, aligning data structures with the operational context.
Outcome — Established a more consistent basis for cross-centre data interpretation and subsequent integration.
CASE 02 · QUALITY & TRACEABILITY
Building structured clinical data processes
Challenge — Clinical research teams needed consistent data collection and documented operational procedures.
Action — Developed eCRF structures, data management procedures, and quality controls for clinical research.
Outcome — Supported more standardised, documented and reproducible data management workflows.
CASE 03 · DATA COMPLEXITY
From unstructured clinical documents to structured data
Challenge — Processed approximately 20,000 clinical PDF documents to extract information for a multinational real-world evidence project.
Action — Developed an R-based extraction and processing workflow using text-processing techniques and quality checks.
Outcome — Produced structured information for downstream review and feasibility assessment, while identifying limitations in source-data quality and comparability.
FROM PRACTICE TO TEACHING
Turning clinical data expertise into practical knowledge.
Teaching is a natural extension of my professional practice. I bring real clinical research workflows, data management challenges and operational decisions into the learning environment, connecting technical principles with the realities of clinical studies.
Clinical context before technology
Explaining why data are collected, how they support study objectives and what makes them clinically meaningful.
From principles to workflows
Connecting protocols, CRF design, validation, data cleaning and database finalisation through realistic operational examples.
Learning through application
Using practical scenarios to help learners recognise data quality issues, understand their consequences and evaluate possible solutions.
TEACHING EXPERIENCE
Clinical Data Management education
University of Milano-Bicocca · MEDAL programme University of Milano · Coordination and Management of Clinical Studies programme
Connecting theory with the study lifecycle
Course materials developed from clinical research processes, including the planning, conduct and closure activities illustrated earlier on this page.
THE BIGGER PICTURE
Reliable clinical data do not happen in isolation.
Clinical Data Management establishes the foundations for reliable, interpretable and traceable data within clinical research. But the value of health data increasingly depends on what happens beyond an individual study, system or organisation.
Health Data Governance addresses this broader context: how data quality, accountability, interoperability, access and appropriate reuse are managed across the data lifecycle. Together, these disciplines help create the conditions for health data to remain trustworthy and useful beyond their original purpose.
From study-level reliability to ecosystem-level trust.
Explore how data governance extends the perspective from individual clinical datasets to the wider health data ecosystem.