How PharmBit content is made.

Most pharmacology study material is a list of facts about drugs. PharmBit is built on the view that the list is the symptom rather than the subject, because almost every fact on it follows from one thing the drug does at a receptor or an enzyme. This page documents how that view turns into content, what standard each lesson is written against, and how it is checked.

Mechanism first, effects derived

Every lesson starts at the molecular target and works outward. We establish what the drug binds and what that binding changes in normal physiology, then derive the therapeutic effect from that change, then derive the adverse effects from the same action appearing in a different tissue. The order matters, because a student who knows that beta-2 receptors dilate bronchi can work out why a nonselective beta-blocker is a problem in asthma, whereas a student who memorised the warning has to recall it correctly under pressure.

This is also why interactions and contraindications are not taught as separate lists. They are consequences of the same mechanism meeting a different context, so presenting them as unrelated facts discards the structure that makes them memorable.

Written against a specification, not freehand

Consistency in a large library cannot depend on how carefully each piece happened to be written, so there is a written content specification that every lesson and post is built against. It fixes section order, the depth expected in a mechanism paragraph, the vocabulary level, how practice questions are constructed, and an explicit list of claims that may never appear regardless of context.

The vocabulary rule is worth stating because it runs against the usual instinct. We do not simplify technical terms. The audience already knows what a receptor is, and replacing a precise word with a vaguer one loses the distinction that examinations actually test. Clarity comes from shorter sentences and a clearer causal order, never from avoiding the correct term.

Automated validation before anything publishes

Every post is checked mechanically against that specification before it goes live, and the check fails the piece rather than producing a warning somebody can ignore. It confirms minimum depth, that mandatory sections such as the conclusion and key takeaways are present, that the piece carries a minimum number of citations to recognised sources, that internal linking falls within a defined range, and that banned claim patterns are absent. Drug lessons are checked further, including limits on mechanism paragraph length and confirmation that every quiz answer matches its own explanation.

We are specific about what this does and does not achieve. Automated validation cannot judge whether an explanation is correct, and it never replaces subject knowledge. What it reliably prevents is the class of failure that comes from scale: the post that ran short, the citation nobody added, the section that was skipped, the quiz whose answer key drifted out of step with its explanation. Those errors are invisible individually and corrosive in aggregate, and they are precisely what human proofreading misses.

Sources we write from

Content is written from regulatory product information, published guidance and peer-reviewed literature rather than from other study websites. In practice that means FDA prescribing information and EMA summaries of product characteristics, DailyMed, NHS and BNF guidance where licensing is relevant, NCBI Bookshelf and PubMed, and the published blueprints of the examinations we cover across the United States, United Kingdom, Canada, Australia and Nigeria. Blog posts carry numbered references with links, so any individual claim can be followed back to its origin.

Review dates and correction

Drug information changes, so every lesson carries a last-reviewed date, and that date is the honest signal of how current it is. Fast-moving areas are rechecked first, which means antimicrobials, anticoagulants and diabetes therapeutics ahead of more stable topics. When guidance changes materially the lesson is updated and the date moves with it.

Corrections are welcome and acted on. Email hello@pharmbit.app with the lesson name and what you believe is wrong, and a verified fix ships with an updated review date.

What we do not claim

We do not have a second, independent pharmacist reviewing every lesson before publication, and we do not say otherwise. Bylines read as the PharmBit Pharmacy Team because no individual reviewer has been appointed, and claiming independent review that is not happening would undermine the point of having standards at all. Who writes and who checks is set out in full on our editorial standards page.

PharmBit is a study aid for examinations and understanding, not clinical guidance, and it does not replace professional judgement, local formularies or supervision. The complete position is in our medical disclaimer.