21 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You start by checking the study database (often Medidata or an in-house SQL/Access system) for overnight uploads and new queries. Expect to run quality checks, generate discrepancy queries, and review incoming CRFs (case report forms) or electronic CRFs for missing or inconsistent values.
Afternoon is meetings with study coordinators, biostatisticians, or regulatory leads to resolve data issues and plan data locks. You’ll update the data management plan, prepare datasets for analysis (often exporting to SAS or SPSS), and document every change for audit trail and compliance.
You’ll commonly use Microsoft Excel for quick checks, Microsoft Access or relational databases for study data, and SPSS (IBM SPSS Statistics) or SAS for prepared datasets and basic analyses. Expect to see XML (Extensible Markup Language) files for data transfer and C# or SQL scripts if your site builds custom ETL (extract-transform-load) tools.
Project teams use Microsoft Project for timelines and PowerPoint for status reports. Hospital systems like MEDITECH appear if the study pulls clinical EHR (electronic health record) data.
You set up validation rules and run edit checks in the database, monitor query rates, and generate discrepancy reports that sites must resolve. You also maintain the audit trail—records of who changed what and when—so regulators can verify data integrity.
Compliance means following the data management plan, Good Clinical Practice basics, and any sponsor or site-specific SOPs. You document decisions, prepare datasets for monitoring visits, and ensure datasets are reproducible for inspection.
AI can help summarize reports, draft standard query language, or suggest CRF layouts, but never feed identifiable patient data into public AI tools. Use AI only on de-identified datasets and with vendor contracts that allow clinical data handling.
Keep human review in the loop: machine suggestions should be validated by you or a clinician. Log AI outputs, follow your sponsor’s data protection policy, and ensure audit trails and version control for any AI-assisted changes.
According to the U.S. Bureau of Labor Statistics (BLS), there were about 262,440 employed in related roles with a median annual wage of $120,230. The lowest tenth earned about $67,240 and the top tenth about $199,130 (BLS, 2025).
Pay varies by employer—pharma sponsors, CROs, or hospitals—experience, and location. Specialized skills (EHR integration, programming in C# or advanced SAS/SPSS) usually push pay toward the higher end.
A clinical research coordinator runs day-to-day site activity: consenting patients, collecting samples, and entering CRFs. A clinical data manager focuses on how that data is collected, stored, cleaned, and delivered—database design, queries, ETL, and regulatory documentation.
A biostatistician does the analysis and creates statistical plans. The clinical data manager prepares the clean, locked datasets the biostatistician needs. You’ll coordinate with both parties and operate the databases and tools (Access, XML exports, SPSS/SAS-ready datasets) that connect their work.