Weekly issue

One issue a week, generated from the corpus: what changed in Nuclide, dated regulatory events, the readouts and decisions due in the next month, what the leading journals published, and any corrections. No tracking pixels, no click tracking, no third-party scripts. The latest issue is below; every issue is archived here and published as an Atom feed.

Nuclide weekly, 2026-10-25

latest issue · standalone page

3 upcoming dates. Every item links to its Nuclide page and, through it, to the primary source. Not medical advice.

What changed

No changelog entries this week.

Regulatory events

No dated regulatory events were recorded on product pages in the past seven days.

Upcoming readouts

Upcoming readouts and decisions, next 30 days. Decisions, advisory committees, expected readouts and congresses from the readout calendar. Expected dates are editorial estimates.

2026-11-04 · SNMMI Theranostics Conference 2026, Bethesda, Maryland (4 to 7 November) (confirmed) · Society of Nuclear Medicine and Molecular Imaging, Radioligand therapy (beta emitters), Radioligand dosimetry, Lutetium-177 radioligand therapy · source
2026-11-06 · 65th Annual Meeting of the Korean Society of Nuclear Medicine with the 25th ARCCNM, Seoul (6 to 7 November) (confirmed) · Korean Society of Nuclear Medicine, FutureChem, CellBion · source
2026-11-19 · 66th Annual Scientific Meeting of the Japanese Society of Nuclear Medicine, Himeji (19 to 21 November) (confirmed) · Japanese Society of Nuclear Medicine, PDRadiopharma, Nihon Medi-Physics · source

What the journals said

No pulse items in the past fourteen days.

Corrections

No corrections were logged this week.

How it is made

Each issue is rendered from the same data as the site: the changelog (the newsletter is the changelog, with context), products' dated regulatory events from the past week, the readout calendar for the next thirty days, the research pulse, and corrections. Nobody writes it by hand and nothing is added that is not already on a page here.

Something wrong in an issue? It is wrong in the corpus too: fix it once via Suggest an edit and the next issue is right.