How MedRegWatch is built and run
Written for the person who has to assess us as a supplier. Everything here describes the system as it runs today; if you need the full vendor pack for your quality system, email mustafa@doctor-data.co.uk.
Where the alerts come from
- MHRA alerts are read from GOV.UK’s public content API. They are published under the Open Government Licence v3.0 and are quoted verbatim, with a link to the original on every page.
- If GOV.UK later edits an alert in place (a class escalation, an added licence), it is fetched again and the record updated — and anyone newly affected is notified.
- The whole archive is kept in a version-controlled repository, so every addition and every change to it is traceable.
Freshness and monitoring
- The pipeline checks GOV.UK about every six hours. The checks are scheduled runs, which can start hours late, so the gap between two checks is sometimes longer. Every run is logged with its outcome.
- Each check is followed by a watchdog that reviews the run log and emails the operator if a recent run recorded an error, if the last successful check is more than 16 hours old, if a recall notification is stuck unsent, or if the newest alert in the archive is more than 21 days old.
- The weekly digest is sent on Mondays, except in a week with no new alerts, and each issue is recorded.
- The latest alert in the archive is shown in the footer of every page, so you can see for yourself how current the data is.
How matching works
- The pipeline extracts product licence (PL) numbers from each alert. The licences you enter are normalised to the same canonical form, so the two sides compare like with like.
- In an alert, these forms are read: a PL, PLGB or PLNI prefix with a four- or five-digit holder number, with or without a one-letter suffix (PL 12345/0001, PLGB 1234/0001, PL 12345/0001R), and parallel-import numbers written PLPI, PL PI or PL(PI). PLGB and PLNI are read as the plain PL number, which errs towards showing you an extra alert rather than missing one.
- In the licences you enter, a five-digit holder number can also be written without its prefix (12345/0001). A four-digit holder number needs its prefix (PL 1234/0001), because on its own it is too easily confused with a date or a batch number.
- Every matched alert shows which of your licences it matched, so a match can be explained at inspection.
- When a new alert names a licence you watch, a notification record is written for each recipient before any email is sent. A failed send is retried on later runs until it is delivered.
What matching can and cannot catch
Matching compares licence numbers and nothing else, so it is only as complete as the numbers printed in the alerts.
- It catches a new alert whose body prints one of your licence numbers in a form that is read (see above).
- A PL number and the parallel-import (PLPI) number with the same digits are matched to each other: watching PLPI 12345/0001 also finds an alert that prints PL 12345/0001, and the other way round. Such a match is labelled with the form the alert printed, so you can confirm it is your product. A PL number with a letter suffix has no such twin.
- It cannot catch an alert with no licence number we can read. About one in five medicines recalls in the archive (121 of 592) are like this. Some print no licence number, some give an EU/1/… number instead of a PL number, and some print a number in a form that is not read.
- In an alert, these forms are not read: a number without its PL prefix (12345/0001), a space inside the prefix (PL GB 12345/0001), a hyphen after it (PL-12345/0001), and a number with fewer than four digits after the slash (PL 12345/001).
- The pipeline reads the body of each alert on GOV.UK. A number printed only in the alert’s title, or only in a document attached to it, is not read.
- An alert that identifies your product only by its name, active ingredient, company or batch number is not matched.
- A letter suffix is part of the number: watching PL 12345/0001 does not match an alert that prints PL 12345/0001R, or the other way round.
An alert that matches nothing is still in the archive. Stay subscribed to MHRA’s own alerts.
The register
- Register entries are never edited. A correction is a new entry. The only way an entry is removed is if you delete the whole workspace it belongs to.
- Each entry carries the email of the person who made it and a server-side timestamp.
- Exports are point-in-time snapshots and are stamped with when they were generated. Entries for a licence you have since removed from the watchlist stay in the export.
Where data is held
| Provider | What it does | Where |
|---|---|---|
| Supabase | Database: accounts, watchlists, register entries, the alert index | London (eu-west-2) |
| Vercel | Hosts the website and application; TLS | Global content network |
| Resend | Sends login codes, notifications and the digest | United States |
| GitHub | Runs the six-hourly pipeline and holds the version-controlled archive | United States |
Register content is never sent to any AI service. No patient data is processed anywhere in the system. There are no analytics scripts on the site.
Access and security
- Sign-in is passwordless: a six-digit code is emailed to you, stored only as a hash, valid for ten minutes, single-use, and locked after five wrong attempts.
- Sessions are signed cookies (HttpOnly, Secure) that expire after 30 days. Signing out clears the session.
- Row-level security is enabled on every database table and no browser-side key can read or write anything. All access goes through server code that checks the organisation on every query.
- Every page is served over TLS with HSTS and standard hardening headers. The endpoints that send email are rate-limited. GOV.UK alert text is sanitised against an allowlist before it is rendered.
Your data and leaving
- What you type into the register belongs to you.
- You can export your register (PDF and CSV) at any time.
- If you cancel, export stays available for 90 days; after that your workspaces and register entries are deleted.
Positioning for your quality system
MedRegWatch is a convenience and record-keeping layer over MHRA’s own alerting service. It is not the authoritative source, it does not replace your subscription to MHRA’s alerts, and it makes no regulatory judgements. Where your procedures require a written supplier assessment, the vendor pack (SOP summary, architecture and monitoring description, data-integrity statement) is available on request.