BNC ยท RIIDs in the Field Contents

8. SOP-3: Medical Isotopes & NORM Scenes

8.1 Scenario

The most common alarms in any program are not threats. They are either medical isotopes (a hospital patient discharged after a scan or therapy) or NORM (oilfield pipe scale, granite, fertilizer, tile, ceramics, antique uranium glass, lantern mantles). A confident operator dispatches these in minutes; a confused one creates community fear.

8.2 Objectives

  1. Recognize the signature of common medical isotopes.
  2. Recognize NORM signatures and the contexts they appear in.
  3. Avoid escalating routine events to public-alert level.
  4. Build a clean record so that pattern-of-life data (e.g., recurring NORM at a single facility) is captured.

8.3 Triggers for SOP-3

8.4 The Common Medical Isotopes: What You'll See

Patient context is the strongest clue. The operator should ask the alerting party (officer, hospital staff, citizen): was a recent medical procedure involved? If yes, identification usually takes seconds.

Isotope Use Typical persistence Spectrum hint
Tc-99m Bone scan, cardiac, sentinel node Hours Single peak ~140 keV; common
F-18 PET scan Hours Annihilation peak at 511 keV; gone within a day
I-131 Thyroid therapy/diagnosis Days to weeks Multiple peaks incl. 364 keV; persistent
I-123 Thyroid imaging Hours ~159 keV peak
Lu-177 Targeted radionuclide therapy (oncology) Days Multiple peaks; 113, 208 keV
Ga-67 Inflammation/infection imaging Days Multiple peaks 93, 184, 300, 393 keV
Tl-201 Cardiac perfusion Days Lower-energy gammas + characteristic X-rays

Operator workflow for a suspected medical alarm:

  1. Identify with the SAM handheld.
  2. Confirm patient context with the alerting party.
  3. Document: name (with appropriate privacy handling), procedure, time of dose, isotope.
  4. Release if appropriate; advise patient to carry a wallet card if recurring portal alarms are likely (some hospitals provide these).
  5. Log the event for pattern recognition.

8.5 NORM in the Wild

Naturally occurring radioactive materials produce alarm signatures that operators see again and again:

A NORM ID is not the end of the conversation. A cargo of NORM should be consistent with the manifest. A fertilizer truck reading thorium does not match, that calls for further inspection. A truck of granite slabs reading uranium daughters absolutely matches. Context and identification work together.

8.6 Differentiation in Practice

A patient scan and a Cs-137 industrial source look nothing alike on a spectrum:

The SAM family's CeBr/LaBr resolution makes these distinctions trivial. Operators who once needed reachback for ambiguous calls now resolve them on scene.

8.7 When to Still Escalate

Even a confident medical or NORM identification deserves escalation in some cases:

8.8 SOP-3 Checklist (Tear-Out)

8.8 SOP-3 Checklist (Tear-Out)
  • Identification acquired with SAM handheld
  • Context verified (patient discharge, NORM cargo, antique store, etc.)
  • Spectrum and photos saved
  • Recurring-alarm pattern checked in agency log
  • Reachback only if context inconsistent
  • Patient privacy handling per agency policy
  • Released or escalated per decision tree
  • Event logged for pattern recognition