25.35 — Who Does What, and What Qualification Sits Behind It

You join a call with eleven people from a client. Four have doctorates, two are pharmacists, one is a nurse, one is a statistician, one is a lawyer by training, one runs a factory, and one is a project manager who understands all of them well enough to keep the meeting moving.

Knowing who they are changes how you speak. A statistician wants to know how missing data is handled. A quality lead wants to know what evidence the system produces. A commercial director wants to know when it launches. Giving each of them the other's answer is how a project loses a room.

This chapter is the cast list: what each role does, what qualification usually sits behind it, and what they need from you.

Discovery and preclinical

Medicinal chemist — designs and makes the molecules of Chapter 25.6. Usually a PhD in organic or medicinal chemistry. Needs from you: fast, reliable access to structure and assay data, and never losing a compound registration.

Biologist or pharmacologist — designs the assays and the disease models. PhD, sometimes with postdoctoral work.

Bioinformatician or computational biologist — the omics analysis of Chapter 25.5. A degree in bioinformatics, computational biology, statistics or computer science. The person in the client organisation most like you, and usually your best internal ally.

Toxicologist — designs and interprets the safety studies of Chapter 25.7. Often a PhD or a veterinary degree, frequently with board certification in toxicology.

Study director — the named individual personally responsible for a GLP study. Their signature carries legal weight, which is why systems holding study data must handle their approvals precisely.

Clinical development

Principal investigator — the physician responsible for the trial at a site. A medical degree plus a clinical specialty; in the United States they personally sign a commitment form.

Study coordinator — the person who actually runs the study at the site. Usually a nurse or a life sciences graduate, often with a research certification. They spend more hours in your system than anyone else, and their opinion of it determines whether a site enrols well.

Clinical research associate, the monitor — visits sites and verifies conduct and data. A life sciences degree plus training; it is a demanding travelling job and turnover is high. Needs from you: everything visible in one place, offline tolerance, and no duplicate data entry.

Clinical project manager — owns timelines, budget and vendors across a study or programme. Any scientific background plus project management experience.

Medical monitor — the physician who answers clinical questions and reviews safety in real time. Medical degree, usually with specialty experience.

Clinical data manager — designs the data collection, the edit checks and the cleaning process, and takes the database to lock. Life sciences or informatics background, often with a data management certification.

Biostatistician — designs the analysis and writes the statistical analysis plan of Chapter 25.10. A master's or PhD in statistics or biostatistics. Precise, evidence-driven, and the person most likely to catch a subtle flaw in your data pipeline. Treat their questions as free code review.

Statistical programmer — builds the analysis datasets and outputs, usually in SAS and increasingly R. A programming role inside a scientific function, and a natural entry point for engineers.

Safety and medical

Drug safety associate or case processor — the case work of Chapter 25.22. Typically a pharmacist, nurse or life sciences graduate. High volume, deadline-driven work; the people whose productivity your tooling most directly affects.

Drug safety physician — causality assessment and medical review. Medical degree.

Qualified Person for Pharmacovigilance — the named individual legally accountable for a company's European safety system. A physician or pharmacist with substantial experience, resident in the region.

Medical science liaison — the field scientific role of Chapter 25.23. Almost always a doctorate: PharmD, PhD or MD.

Medical information specialist — answers product questions. Usually a pharmacist or nurse.

Health economist / outcomes researcher — builds the value evidence payers want. A PhD or master's in health economics, epidemiology or public health.

Regulatory

Regulatory affairs associate through director — strategy, submissions, agency interaction. A life sciences degree at entry, frequently a doctorate or pharmacy degree at senior levels, and often a professional regulatory certification. Needs from you: nothing that surprises them, and early warning of anything touching a filed process.

Regulatory operations / publishing specialist — builds and dispatches the electronic submissions of Chapter 25.24. Technical rather than scientific, and an area where good tooling has an immediate effect.

Labelling specialist — owns the approved product text across markets. Detail-obsessed by necessity, since a wrong word is a regulatory event.

Quality and manufacturing

Quality assurance specialist or manager — the system of Chapter 25.17. A science degree plus experience; auditor certification is common.

Quality control analyst — runs the laboratory tests. A chemistry, microbiology or pharmacy background.

Qualified Person — in Europe, the individual who certifies each batch before release. Defined by law: a degree in pharmacy, chemistry, biology or a related field, plus specified subjects and practical experience. This is a personally accountable legal role, not a job title a company can hand out.

Computer system validation specialist — your most frequent counterpart. Often an engineer or scientist who moved into validation, sometimes an IT professional who learned the regulations. Needs from you: evidence produced as a by-product of building, not assembled afterwards.

Process engineer and MSAT scientist — own the manufacturing process and its transfer between sites (Chapter 25.11). Chemical or biochemical engineering.

Production operator and supervisor — run the equipment and complete the batch records. Trained and qualified per task, and the people whose working conditions your interface design directly affects. A confusing screen at three in the morning becomes a deviation.

Supply chain planner — matches production to demand across markets with long lead times and expiry dates.

The payer side

Actuary — prices the plan and projects cost. Actuarial qualification through professional examinations, which are long and hard. They will interrogate your data definitions harder than anyone.

Medical director — the physician who makes coverage and medical necessity decisions.

Utilisation review nurse / care manager — reviews requests against criteria and manages high-cost members. Registered nurse, often with certification.

Claims examiner — adjudicates claims that automation could not.

Provider network manager — negotiates and maintains contracts with providers.

Compliance officer — the fraud, waste and abuse and regulatory obligations of Chapter 25.29.

The provider side

Physician — medical degree plus residency, and board certification in a specialty. Time is their scarcest resource; a system that adds clicks will be resisted for good reason.

Nurse practitioner and physician assistant — advanced practice clinicians, master's level, who diagnose and prescribe within their scope.

Registered nurse — the largest clinical workforce, and the one that uses hospital software most.

Pharmacist — a doctorate in pharmacy, licensed. Dispensing, clinical review, and increasingly direct patient services.

Medical coder — the coding of Chapter 25.28. Certification from a recognised body, with specialisations for inpatient, outpatient and risk adjustment. This is a skilled profession, and treating it as data entry is both wrong and insulting.

Health information management professional — owns the medical record itself: completeness, retention, release of information, and privacy. Formal credentials exist at technician and administrator level.

Clinical informaticist — the bridge between clinicians and systems. Usually a clinician who moved into informatics, sometimes with a formal informatics qualification, and the single most useful person to have on a hospital project.

Electronic health record analyst — configures and supports the record system, typically holding vendor-specific certifications.

Inside your own company

Business analyst — turns what the client says into requirements someone can build and test. In this industry, the good ones know the regulatory context, because a requirement that ignores it is not a requirement.

Solution architect — makes the design decisions of Chapters 25.20 and 25.21 that are cheap now and impossible later.

Validation lead — owns the evidence package.

Delivery or engagement manager — owns the commercial relationship and the schedule.

Subject matter expert — the SME — whoever holds the deepest working knowledge of a specific process or system. Not a grade; a function. The person an investigation, a validation or an inspector will ask for.

And the coordinator role. Every regulated organisation has people whose job is keeping records and workflows moving: triaging incoming items, assigning owners, chasing due dates, preparing review meetings, compiling metrics. The title varies — quality coordinator, process coordinator, programme coordinator, study coordinator — and companies abbreviate them in their own way. Abbreviations for coordinator roles are among the least standardised in the whole industry, so when one appears in a client's documents, ask what it stands for there. Nobody will think less of you for asking, and everyone will notice if you guess wrong.

Which qualification is required at which stage

A rough map, for orientation rather than as a rule. Requirements vary by country and company.

Stage	Typical qualification
Discovery science	PhD in a relevant science
Preclinical safety	PhD, veterinary or toxicology board
Trial conduct at a site	Medical degree; nursing for coordination
Trial operations at sponsor	Life science degree plus experience
Statistics	Master's or PhD in statistics
Pharmacovigilance	Pharmacy, nursing or life sciences; MD for review
Regulatory affairs	Life science degree; certification common
Quality and validation	Science or engineering plus experience
EU batch certification	Legally defined degree plus experience
Manufacturing operations	Technical training to engineering degree
Medical coding	Professional coding certification
Clinical care	Licensed clinical qualification

Two patterns are worth noticing.

The clinical and legally accountable roles have hard qualification requirements — a physician, a pharmacist, a Qualified Person, a coder. Everything else is a matter of degree plus experience, and lateral movement is common: people move from the bench into regulatory, from nursing into safety, from IT into validation.

And this is why a software engineer can become genuinely valuable here faster than in most industries. The domain knowledge is learnable, it is published, and very few of the people who hold it can also build systems. The combination is rare and is priced accordingly.

Next: Chapter 25.36, the acronym dictionary — every abbreviation used in this Part, defined, with where it shows up.