Bringing radiopharmaceutical production into the digital age
A web-based platform that brings equipment management, production planning, quality control documentation, licence tracking and staff coordination into a single secure environment — built around the vocabulary of cyclotron-based radiopharmaceutical production rather than adapted from a generic tool.
- Nuclear Medicine
- Full-Stack Development
- Multi-Tenant SaaS
- Industry
- Nuclear medicine / radiopharmaceutical production
- Engagement
- Full-stack product development
- Platform
- Web, works in any browser
- Stack
- React 19 · NestJS · MongoDB · Keycloak · KrakenD · Docker
Project summary
A specialised production domain with no software built for it
The tracer injected for a PET scan is produced that same morning, a few kilometres away, and starts losing potency the moment it is made. By the time the patient arrives the dose has to be the right activity, from a batch that passed quality control, made to a documented procedure, by staff whose qualifications are current, on equipment that has been maintained and calibrated. Every one of those requirements generates paperwork, and for decades the answer to where it lives has been: check the binder.
Client summary
About NucMatX
- 8
- Areas of the production lifecycle covered
- 28
- Permission roles in the access model
- 128
- API paths at the gateway, 207 routed endpoints
- 90 · 60 · 30
- Days before expiry the system alerts
Client goals
What the facility needed the platform to do
-
Replace the binder
The cyclotron logbook, the SOP folder on the network drive, the qualification spreadsheet and the printed batch record forms, as one structured record.
-
Speak the domain, not a data model
Targets with their own beam currents and isotopes, hot cells with clean room classifications, products with yields that depend on the configuration used — as first-class concepts rather than custom fields.
-
Make every handoff explicit
Cyclotron operator, radiochemist, QC analyst and release authority each see their own view of the production record and sign their own step, at the moment they complete it.
-
Never lose track of an expiry date
Facility operating licences and individual staff qualifications monitored by the system, with the certificate stored beside the records that reference it.
-
Keep a record nobody can quietly edit
Every record created, every field updated, every document uploaded, logged with who did it and what changed — and not editable or deletable afterwards.
The challenge
A single source of truth where generic tools could only hold part of it
Facilities that try to digitise this work reach for a general laboratory system and end up with workarounds: custom fields with non-obvious names, free-text boxes where structured data belongs, and spreadsheets living alongside the system because the system cannot do the calculation. What they get is a source of partial truth — which, under regulatory scrutiny, is close to as difficult as paper.
Frontend
React 19
Two Vite applications: the facility workspace and an admin console.
Gateway
KrakenD 2.9
One entry point in front of every service, validating a Keycloak token and its roles on 205 of the 207 routed endpoints.
Services
NestJS
Four services — auth, platform, logger and mailer — over MongoDB, with the audit log written by a service of its own.
Our contribution
The production lifecycle, end to end
-
Equipment and configuration history
Cyclotrons with their target configurations and operating parameters, hot cells with their clean room classifications and synthesis modules, and quality control instruments. Every modification is recorded, so each device carries its full configuration history.
-
Radiochemistry master data
The facility's catalogue of radioisotopes and products, each entry a complete production specification: which cyclotrons and targets can produce it, the expected yields, how long synthesis and QC take, the QC criteria and the SOPs that apply to each phase.
-
Production orders and planning
An order starts as a draft — the product, the dose time, the required activity — and the master data generates the plan: when irradiation begins, how long synthesis takes, when QC must be complete, what the yield will be at dispensing.
-
Digital batch records
Pre-production checks, cyclotron parameters, synthesis data, QC results and dispensing, each section filled in by the person responsible at the time they complete the step, with timestamped digital signatures.
-
Licence and qualification tracking
Expiry dates monitored for facility operating licences and staff certificates, with alerts at 90, 60 and 30 days, and the documents themselves stored in the system beside the records that cite them.
-
An audit trail of its own
The log is written by a service independent of the one writing production data, so it stays intact even if the application does not, and credentials are stripped from entries before they are stored.
01 · Equipment
The cyclotron register, with every target configuration
- Configuration history
- Hot cells & QC instruments
- Search & filter
02 · Production
A production order from draft to release
- Draft → upcoming → in progress
- Planned from master data
- Expected yield at dispensing
03 · Records
The batch record, signed section by section
- Timestamped signatures
- SOP version in use
- Complete on release
Results
What the platform delivered
-
Paper logbooks, SOP folders and qualification spreadsheets replaced by one structured record, deployed at an operating nuclear medicine facility.
-
A complete, searchable audit trail of every action by every user, written by a service independent of the one writing production data.
-
Licence and staff qualification expiries surfaced at 90, 60 and 30 days instead of depending on someone's calendar.
Technologies used
- React 19
- TypeScript
- Material UI
- NestJS
- MongoDB
- Keycloak
- KrakenD
- Docker