Radiopharmacist's Notes · FDGtwo™
The two-vessel architecture saves the second operator setup. What it does not save is the second batch record — radiochemical purity, residual solvents, endotoxin and Pharm.Eur. release are per-batch attributes, not session-level ones. This page draws the line between what is shared across the session and what each batch has to carry on its own paperwork.
The middle column is what the two-vessel architecture does not change — both batches need it.
Source: FDGtwo product page — "two independent sets… two productions with one setup"
Source: Pharm.Eur. monograph for [18F]FDG injection + site batch-record SOP
Source: AERB cyclotron-facility licensing path; site SOPs.
Sources: FDGtwo product page; Pharm.Eur. monograph for [18F]FDG injection; AERB cyclotron-facility licensing path; site SOPs.
Scope of this page
The three columns above reflect the workflow a two-vessel synthesizer enables, mapped against the per-batch release attributes the Pharm.Eur. monograph for [18F]FDG injection requires. They are a starting framework for SOP authoring, not a substitute for site SOPs signed off by the radiopharmacy programme. The exact GUI field names, the cleanup-cycle interlocks and the vessel-set identifier convention should be confirmed against the brochure and the in-house validation.
Sources cited on this page
FDGtwo™ Radiosynthesizer
Sibling posts in the FDGtwo family.