Field note · September 4, 2024

Five minutes with bmi in clinical-trial

900 rows, 199 distinct values, and the one fact about bmi that changes how you query it.

1 min read ·Data quality ·quality practice

Someone asked what is in bmi on clinical-trial, and the honest answer took one query.

900 rows, no nulls, 199 distinct values. Body mass index at baseline.

The five-number version: min 16.00, p10 21.79, median 27.10, p90 32.70, max 40.90. The mean is 27.13.

The p10 to p90 band — 21.79 to 32.70 — is where ordinary rows live, and it is the pair worth quoting when somebody asks what to expect. Min and max describe the two strangest rows in the table and nothing else; they are useful for spotting impossible values and misleading for everything else.

sql
select
  count(*)              as rows,
  count(bmi)            as present,
  count(*) - count(bmi) as nulls,
  count(distinct bmi)   as distinct_values
from clinical_trial;

Nothing dramatic: the mean and median are within 0.1% of each other, so an average is a fair summary. That is worth confirming rather than assuming — it is not true of most money columns.

Where this matters: a symmetric column is one you can average, threshold and chart without hedging, which makes it unusually cheap to work with. Knowing which of your columns are like this and which are not is most of knowing when to be careful.

The grain is one row per enrolled subject, which is the context every one of those numbers depends on. None of them survive a change of grain, which is why "profile the column" and "profile the table" are the same job. Full schema, and the CSV, on the dataset page.