Pocket O&G
A searchable clinical reference for O&G — 40+ guidelines, 18 decision flowcharts, a drug reference, consent docs, and clinical calculators, all running client-side on a phone.
Tired of hunting through PDFs mid-clerking. I wanted fast, searchable guidelines built for the moment you actually need them.
What it is
Pocket O&G is a clinical search engine for O&G — a way to get to the right trust protocol or NICE guideline in seconds, without hunting through a shared drive or ctrl-F-ing through a PDF while a patient is waiting.
It is built for ward use: fast, mobile-first, and designed to surface the answer at the moment you actually need it.
What I built
Six content areas, all client-side, all loading fast on a phone.
- Full-text search across 40+ guidelines with synonym expansion — search "clot" and VTE guidance surfaces
- Filter by source: trust protocols, RCOG, or NICE
- 18 interactive decision flowcharts with animated step-through and colour-coded pathways
- IOL Prioritiser for induction of labour decisions
- Drug reference (Rx) covering antibiotics, anticoagulants, analgesia, antiemetics, and antihypertensives
- Consent documentation for common O&G procedures
- Clinical calculators
- Cross-linking between guidelines — tap a term and see related protocols
- Source-PDF links on every guideline
Why it grew
The first version was five days of work: search, flowcharts, a phone-sized layout.
Clinical tools have a way of revealing the next problem once you've solved the first one. Guidelines kept getting added. Then came the Rx tab, the consent section, the calculators, the cross-linking. Each addition was the smallest fix for a real gap.
What started as a simple search tool now covers most of what you'd reach for mid-clerking.
Stack
React 19, Vite, and Tailwind CSS, tested with Vitest, deployed on Vercel.
No backend. The search engine and synonym expansion run entirely client-side, which keeps the app lightweight and quick to load on a phone with patchy hospital WiFi.
What I learned
Client-side search with synonym expansion sounds like it should require a backend. It does not — and keeping it on the client turned out to be the right call. Fast, no server costs, works offline in the hospital basement.
Designing for clinical use forced me to think hard about information hierarchy. In this kind of tool, a missed result or a confusing pathway is not just bad UX — it can matter to patient care.