Pharmaceutical Analysis Is Science — From STEM to STEAM
The opening frame for the 2026 course: why pharmaceutical analysis is a science in the full sense of the word, and what the ‘A’ in STEAM adds to it.
Everything in this folder is Lecture 1. It is the opening arc of the course, and it moves deliberately in one direction — science → pharma → regs — before turning to the working detail that fills the rest of the term.
It also plants the course’s four movements in one sitting: the measurement and the rules (sections 1–3), the instruments as evidence (implicit in section 2’s four questions), from data to decision (sections 6–7), and putting it to work (sections 4–5, 8). Later weeks slow each of these down.
| # | Section | The one idea |
|---|---|---|
| 1 | Analysis Is Science | Pharmaceutical analysis meets the full definition of science: open data, independent replication, and the obligation to revise. A method is a hypothesis about a molecule. STEM → STEAM — the “A” (judgment, interpretation, design, communication, ethics) is what separates an analyst from a technician. |
| 2 | Pharmaceutical Analysis in Context | What that science is for: discovering, developing, and selling a medicine. The funnel from molecule to market, and where measurement supplies the evidence at each narrowing. |
| 3 | Regulations & Compendial Methods | The regs end of the funnel — the ICH quality guidelines (Q1–Q14), the pharmacopeias (USP–NF, Ph. Eur., JP), and agency expectations. A result that can’t be defended to a regulator doesn’t ship a product. Includes a full page on each ICH quality guideline that touches analysis, from Q1 · Stability through Q14 · Analytical QbD. |
| 4 | Clinical Trials | Clinical development reframed as the progressive removal of uncertainty — Phase 1 → 3 — with analysis supplying the evidence at every step. |
| 5 | Quality Control | QC across the supply chain: quality is assured by accumulated knowledge, not produced by the final test. |
| 6 | Lab Automation & PAT | The measurement moves out of the laboratory and onto the process line — at-line, on-line, in-line — and the analyst moves with it, owning the system and the model rather than the number. |
| 7 | Knowledge Management | What turns the resulting flood of data into durable knowledge about a product. |
| 8 | The Cost of Development | A price on all of it — and why the cost of every activity, and every failure, is recouped from the price of the medicines that reach the market. |
Work through the sections in order. Use the menu on the left to see where you are, the “On this page” list on the right to move within a section, and the ← / → buttons at the foot of each page to step through the whole lecture in sequence.
Later weeks each get their own folder in the left menu.
The opening frame for the 2026 course: why pharmaceutical analysis is a science in the full sense of the word, and what the ‘A’ in STEAM adds to it.
What STEM-to-STEAM looks like once it’s inside a company that has to discover, develop, and ultimately sell a novel medicine — and the science → pharma → regs funnel this course follows.
The ‘regs’ end of the funnel: how ICH guidelines, the pharmacopeias, and agency expectations shape every analytical decision — from method design to release.
Clinical development as the progressive reduction of uncertainty: why the phases exist, how the question changes at each one, and where pharmaceutical analysis supplies the evidence that lets the next decision be made.
Quality control as the standing function that demonstrates control on every batch: methods deployed across the whole supply chain, the combined scientific and regulatory approach, and the partnerships and economics that make a control strategy work.
Where the measurement happens and what it is allowed to do: the automation maturity ladder from manual bench work through instrument and workflow automation to at-line, on-line and in-line PAT, closed-loop control, and exception-based operation; the at-line / on-line / in-line vocabulary; a worked tablet-press scenario that walks from ‘automate the tester’ to ’the press controls itself’; ‘where did the QC lab go’ — the shift from lab pulls to real-time release testing; a catalogue of pharmaceutical automation examples from robotic sample management to continuous manufacturing and automated visual inspection; the evidence a measurement has to carry before it can move onto the line — representativeness, a validated model, drift and sensor failure, specification versus control limits; and how the analyst’s job changes from producing the number to owning the measurement system and the model behind it.
What to do with the flood of data once automation can generate it faster than anyone can read it: the DIKW pyramid (data → information → knowledge → wisdom) as the goal of the whole exercise; why every scientist is now a data scientist and what reproducible data science asks of them; formal versus informal models and why great science pushes from one to the other; a short history of the database from Codd’s relational model to XML and self-describing data, and the arc from databases through data warehouses, data lakes and data meshes; ‘homo sapiens data integration’ and automation as the engine that generates, organizes and analyses; the S88/S95 recipe as the informational framework that ties process, method and QC together — everything is a recipe, even the analytical procedure; linked data and semantic technologies as the future of method and data sharing; and how the analyst’s job grows to include owning the model and the knowledge, not just the number.
The economic frame that closes the arc: what a new medicine actually costs to develop, why clinical development and patient recruitment dominate the bill, how the cost of every failure is recouped from the price of the few drugs that reach the market inside a patent window, why development keeps getting harder — a materials-science problem handed a biological lead, more compounds through flat headcount on shorter timelines, a rising GxP floor — and what ‘spend wisely’ actually asks of the analytical scientist: front-load knowledge, right-size the method and the specification, and treat every experiment as money.