<!-- BaNnErBlUrFlE-BoDy-start -->
<!-- Preheader Text : BEGIN -->
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">
Thank you, Adam, and all who commented. PHAROS, the AI compliance agent, and I took the liberty of summarizing the most important changes relevant to RSOs and medical physicists in the table below. The intent was to provide a concise side-by-side</div>
<!-- Preheader Text : END -->
<!-- Email Banner : BEGIN -->
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerStart</div>
<!--[if ((ie)|(mso))]>
<table border="0" cellspacing="0" cellpadding="0" width="100%" style="padding: 0px 0px 10px 0px; direction: ltr" lang="en"><tr><td>
<table border="0" cellspacing="0" cellpadding="0" style="padding: 0px 8px 6px 8px; width: 100%; border-radius:4px; border-top:4px solid #8c8e91;background-color:#cfd3d7;"><tr><td valign="top">
<table align="left" border="0" cellspacing="0" cellpadding="0" style="padding: 0px 8px 4px 8px; font-size: 12px; line-height: 16px">
<tr><td style="color:#000000; font-family: 'Arial', sans-serif; font-weight:bold; font-size:14px; line-height: 20px; direction: ltr">
This Message Is From an External Sender
</td></tr>
<tr><td style="color:#000000; font-weight:normal; font-family: 'Arial', sans-serif; font-size:12px; direction: ltr">
This message came from outside your organization.
</td></tr>
</table>
<![if ie]><br clear="all"><![endif]>
<table align="right" border="0" cellspacing="0" cellpadding="0" style="padding: 0px 0px 4px 0px; font-size: 14px; line-height: 36px"><tr>
<td style="direction: ltr"> <a target="_blank" href="https://us-phishalarm-ewt.proofpoint.com/EWT/v1/KGKeukY!syQTXcjAAujAKhqRHw5ElNJ4a9WqqgmrgTNmtvIwGbyyate2XxtblrzsJpd8wW5y0nQ7D-IcEAT0zNAlTdGFxXRkMcpU2UEqPajNdmlCbDDeeERPBsMUVdHi$" style="mso-padding-alt: 7px; padding: 7px; border-radius: 2px; border: 1px solid #666666; "><strong style="font-weight: normal; color: #000000; text-decoration: none; font-family: 'Arial', sans-serif; font-size: 14px;"> Report Suspicious </strong></a> </td>
</tr></table>
</td></tr></table>
</td></tr></table>
<![endif]-->
<![if !((ie)|(mso))]>
<div dir="ltr" lang="en" id="pfptBanneroq5rusz" style="all: revert !important; display:block !important; text-align: left !important; margin: 0 0 10px 0 !important; padding:7px 16px 8px 16px !important; border-radius: 4px !important; min-width: 200px !important; background-color: #cfd3d7 !important; background-color: #cfd3d7; border-top: 4px solid #8c8e91 !important; border-top: 4px solid #8c8e91;">
<div id="pfptBanneroq5rusz" style="all: unset !important; float:left !important; display:block !important; margin: 1px 0 1px 0 !important; max-width: 600px !important;">
<div id="pfptBanneroq5rusz" style="all: unset !important; display:block !important; visibility: visible !important; background-color: #cfd3d7 !important; color:#000000 !important; color:#000000; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-weight:bold !important; font-weight:bold; font-size:14px !important; line-height:1.29 !important; line-height:1.29">
This Message Is From an External Sender
</div>
<div id="pfptBanneroq5rusz" style="all: unset !important; display:block !important; visibility: visible !important; background-color: #cfd3d7 !important; color:#000000 !important; color:#000000; font-weight:normal; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-size:12px !important; line-height:1.5 !important; line-height:1.5; margin-top:2px !important;">
This message came from outside your organization.
</div>
</div>
<div id="pfptBanneroq5rusz" style="all: unset !important; float: right !important; display: block !important; display: block; margin-left: 16px !important; margin-top: 1px !important; text-align: right !important; width: fit-content !important; font-size: 12px !important">
<a id="pfptBanneroq5rusz" href="https://us-phishalarm-ewt.proofpoint.com/EWT/v1/KGKeukY!syQTXcjAAujAKhqRHw5ElNJ4a9WqqgmrgTNmtvIwGbyyate2XxtblrzsJpd8wW5y0nQ7D-IcEAT0zNAlTdGFxXRkMcpU2UEqPajNdmlCbDDeeERPBsMUVdHi$"
style="all: unset !important; display: inline-block !important; text-decoration: none">
<div class="pfptPrimaryButtonoq5rusz" style="display: inline-block !important; display: inline-block; visibility: visible !important; opacity: 1 !important; color: #000000 !important; color: #000000; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-size: 14px !important; font-weight: normal !important; text-decoration: none !important; border-radius: 2px !important; margin-top: 3px !important; margin-bottom: 3px !important; margin-left: 16px !important; padding: 7.5px 16px !important; white-space: nowrap !important; width: fit-content !important;
border: 1px solid #666666">
Report Suspicious
</div>
</a>
</div>
<div style="clear: both !important; display: block !important; visibility: hidden !important; line-height: 0 !important; font-size: 0.01px !important; height: 0px"> </div>
</div>
<![endif]>
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerEnd</div>
<!-- Email Banner : END -->
<!-- BaNnErBlUrFlE-BoDy-end -->
<html aria-label="message body"><head><!-- BaNnErBlUrFlE-HeAdEr-start -->
<style>
#pfptBanneroq5rusz { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important;
background-color: #cfd3d7 !important;
max-width: none !important; max-height: none !important }
.pfptPrimaryButtonoq5rusz:hover, .pfptPrimaryButtonoq5rusz:focus {
background-color: #adb0b4 !important; }
.pfptPrimaryButtonoq5rusz:active {
background-color: #8c8e91 !important; }
html:root, html:root>body { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important; }
</style>
<!-- BaNnErBlUrFlE-HeAdEr-end -->
<meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Thank you, Adam, and all who commented.</div><div><br></div><div>PHAROS, the AI compliance agent, and I took the liberty of summarizing the most important changes relevant to RSOs and medical physicists in the table below. The intent was to provide a concise side-by-side view of the current framework, the proposed changes, and the practical implications for RSO and medical physics review.</div><div><br></div><div>The main takeaway is that several of the proposals appear to reduce prescriptive licensing and documentation steps, but they also shift more responsibility to the licensee for internal controls, technical justification, and audit-ready recordkeeping. Please feel free to use this as a discussion aid for internal review or for drafting comments.</div><div><br></div><div><div><div>Troy Zhou, PhD, DABR, DABSNM<br>Managing Partner<br>Diagnostic Radiation Physics Services<br>(650) 683-0918<br>troy.zhou@diagnosticradphys.com</div><div><br></div></div></div><div><h2 style="font-family: Arial, Helvetica, sans-serif; font-variant-ligatures: normal; color: rgb(31, 78, 121); margin-bottom: 4px;">NRC Proposed Regulatory Changes — Practice Impact Crosswalk</h2><h2 style="font-family: Arial, Helvetica, sans-serif; font-variant-ligatures: normal; color: rgb(31, 78, 121); margin-bottom: 4px;"><p style="font-weight: 400; font-variant-ligatures: normal; font-size: 12px; color: rgb(74, 74, 74); margin-top: 0px; margin-bottom: 14px;">Five NRC proposed rules issued April–July 2026 under Executive Order 14300. Comment deadlines: Part 37 security <b>closed May 11, 2026</b>; Byproduct Material Use <b>closed July 2, 2026</b>; Materials Licensing <b>August 10, 2026</b>; Radiation Protection Framework <b>August 31, 2026</b>; Reducing Barriers to Medical Use Licensing <b>September 10, 2026</b>. Note that the Radiation Protection Framework rule and the Medical Use rule <b>both amend 10 CFR Part 35</b>, on separate dockets.</p><table cellpadding="7" cellspacing="0" border="1" style="font-variant-caps: normal; border-collapse: collapse; border: 1px solid rgb(176, 184, 193); font-size: 12px; width: 968px;"><thead><tr style="background-color: rgb(220, 230, 241);"><th style="border: 1px solid rgb(176, 184, 193); text-align: left; width: 101.039px;">Topic</th><th style="border: 1px solid rgb(176, 184, 193); text-align: left; width: 130.047px;">Relevant 10 CFR sections</th><th style="border: 1px solid rgb(176, 184, 193); text-align: left; width: 207.406px;">Current practice</th><th style="border: 1px solid rgb(176, 184, 193); text-align: left; width: 246.086px;">Proposed change</th><th style="border: 1px solid rgb(176, 184, 193); text-align: left; width: 207.422px;">Action needed</th></tr></thead><tbody><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Radiation protection basis</b></td><td style="border: 1px solid rgb(176, 184, 193);">§§20.1003 and 20.1101(b)–(d)</td><td style="border: 1px solid rgb(176, 184, 193);">Radiation protection programs are structured around explicit ALARA language as a core management principle for exposures below regulatory limits.</td><td style="border: 1px solid rgb(176, 184, 193);">Remove the ALARA definition and regulatory references. Revised §20.1101(b) would require procedures, engineering controls, and a graded approach to dose management based on sound radiation-protection principles.</td><td style="border: 1px solid rgb(176, 184, 193);">Review the radiation safety manual, ALARA policy, committee charter language, and investigation triggers; draft replacement terminology and threshold-based decision criteria for future use.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Occupational dose management</b></td><td style="border: 1px solid rgb(176, 184, 193);">§20.1201; proposed §20.1205; §§20.1206, 20.2104 and 20.2105</td><td style="border: 1px solid rgb(176, 184, 193);">Worker-dose control relies on annual occupational limits and the existing planned special exposure framework under §20.1206.</td><td style="border: 1px solid rgb(176, 184, 193);">Proposed §20.1205 would create a planned occupational dose-limit extension using available dose from the current and preceding four years, subject to annual and five-year constraints.</td><td style="border: 1px solid rgb(176, 184, 193);">Determine whether dosimetry databases and approval forms could support five-year dose histories, written preauthorization, worker notification, cumulative calculations, and extension records.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Worker monitoring thresholds</b></td><td style="border: 1px solid rgb(176, 184, 193);">§§20.1502 and 20.2106(a)(7)</td><td style="border: 1px solid rgb(176, 184, 193);">Individuals meeting the criteria in §20.1502 must be monitored, with numerical results maintained under §20.2106.</td><td style="border: 1px solid rgb(176, 184, 193);">Proposed §20.2106(a)(7) would allow an annotation instead of a numerical value when monitoring was required but the dose did not exceed 10% of the applicable monitoring criterion — the licensee “may, instead of recording the numerical value of the dose received, annotate that an occupational dose was received but did not exceed the criteria for recording.”</td><td style="border: 1px solid rgb(176, 184, 193);">Review badge-assignment criteria, internal investigation levels, dose-record forms, and dosimetry-system interfaces.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Public dose control</b></td><td style="border: 1px solid rgb(176, 184, 193);">§§20.1301 and 20.1302</td><td style="border: 1px solid rgb(176, 184, 193);">Public-dose compliance is demonstrated through surveys, shielding assumptions, occupancy factors, area monitoring, and adjacent-area assessments. Current §20.1301 includes annual and short-term public-dose criteria.</td><td style="border: 1px solid rgb(176, 184, 193);">Revise §20.1301 to remove the 2-mrem-in-one-hour criterion, establish caregiver provisions, and allow case-specific variances from certain public-dose or accessible-dose-rate limits with adequate controls. The annual public limit itself remains 0.1 rem (1 mSv) per year.</td><td style="border: 1px solid rgb(176, 184, 193);">Review shielding evaluations, area-monitor placement, occupancy assumptions, public-dose worksheets, and procedures for evaluating unusual short-duration exposures.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Caregiver and patient-release framework</b></td><td style="border: 1px solid rgb(176, 184, 193);">§20.1301(c); §20.2107(c)–(d); §§35.2, 35.75 and 35.2075</td><td style="border: 1px solid rgb(176, 184, 193);">Under §35.75, a patient may be released when the dose to another individual is unlikely to exceed 0.5 rem from the release. Caregivers of patients who cannot be released may require an exemption to exceed the ordinary public-dose limit.</td><td style="border: 1px solid rgb(176, 184, 193);">Proposed §35.75 would allow an informed and consenting caregiver to receive up to <b>5 rem</b> following release per administration regimen. Other members of the public would remain limited to 0.5 rem per regimen. Proposed §20.1301(c) would <i>separately</i> allow up to <b>2 rem</b> to a caregiver while caring for a patient who <i>cannot</i> be released, with a 0.5-rem limit for a non-caregiver visitor. The 5-rem and 2-rem figures apply to different situations — do not merge them.</td><td style="border: 1px solid rgb(176, 184, 193);">Update patient-release calculations, caregiver designation and consent, written instructions, occupancy assumptions, cumulative regimen calculations, and pre-release caregiver-dose justification records.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Documentation and recordkeeping</b></td><td style="border: 1px solid rgb(176, 184, 193);">Part 20, Subpart L, §§20.2101–20.2110; §§35.2059, 35.2060, 35.2075, 35.2080 and 35.2093</td><td style="border: 1px solid rgb(176, 184, 193);">Records are maintained under existing Part 20 and Part 35 requirements and applicable license conditions.</td><td style="border: 1px solid rgb(176, 184, 193);">The proposals would add or revise records for continuing education, planned dose extensions, patient release, caregiver exposure, Rb-82 systems, mobile services, and other performance-based determinations.</td><td style="border: 1px solid rgb(176, 184, 193);">Review forms, logs, credentialing packages, dose-assessment memoranda, release records, and audit trails to ensure that each regulatory decision has a documented technical basis.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Authorized User additions</b></td><td style="border: 1px solid rgb(176, 184, 193);">§§35.13(b), 35.24(g)(5), 35.100, 35.190, 35.200 and 35.290</td><td style="border: 1px solid rgb(176, 184, 193);">Adding an Authorized User generally requires the licensing actions specified by §35.13.</td><td style="border: 1px solid rgb(176, 184, 193);">Revised §35.13(b) would remove the amendment requirement for AUs limited to non-written-directive diagnostic uses under §§35.100 and 35.200. Qualification requirements under §§35.190 and 35.290 would remain. New §35.24(g)(5) would require the licensee to give the RSO authority to verify that those requirements are met before authorizing use.</td><td style="border: 1px solid rgb(176, 184, 193);">Establish an internal AU approval process containing qualification verification, training records, preceptor attestations, RSO approval signatures, authorized-use scope, and inspection-ready documentation.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Training and experience pathways</b></td><td style="border: 1px solid rgb(176, 184, 193);">§§35.50, 35.51, 35.55, 35.57–35.59, 35.190, 35.290, 35.390, 35.392, 35.394, 35.396, 35.490, 35.590, 35.690 and proposed 35.790</td><td style="border: 1px solid rgb(176, 184, 193);">Part 35 contains prescriptive training, experience, recentness, board-certification, work-experience, and preceptor-attestation pathways for RSOs, AMPs, ANPs, and AUs.</td><td style="border: 1px solid rgb(176, 184, 193);">Revise selected residency pathways, training hours, cases, board-recognition provisions, and generator experience. Section 35.59 would be retitled “Continuing education.” The seven-year window is not removed — it survives in §35.59(a)(1), (b)(1), and (c) (the last covering RSOs, ARSOs, AMPs, and ANPs). What is removed is the requirement to <i>demonstrate</i> it at the time of application; the obligation becomes continuous and per-use, with records under proposed §35.2059.</td><td style="border: 1px solid rgb(176, 184, 193);">Crosswalk existing physician, AMP, ANP, and RSO files against the proposed pathways. Identify where competency, equivalency, continuing-education, or device-specific training documentation would be required. Do not retire seven-year tracking — re-scope it from an application gate to a continuing per-use check.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Emerging medical technologies</b></td><td style="border: 1px solid rgb(176, 184, 193);">Y-90/microsources: §§35.40, 35.41 and proposed §§35.700, 35.710, 35.790 and 35.2710.<br><br>Rb-82: §§35.60, 35.63, 35.93, 35.204, 35.2060, 35.2093 and 35.3093.<br><br>Other EMTs: §§35.590–35.690 and 35.1000.</td><td style="border: 1px solid rgb(176, 184, 193);">Technologies not fitting established Part 35 subparts are commonly licensed under §35.1000 using technology-specific guidance and license conditions. Rb-82 generator operations currently depend partly on enforcement discretion (EGM 13-003).</td><td style="border: 1px solid rgb(176, 184, 193);">Codify selected mature technologies, including microsources such as Y-90 microspheres, Rb-82 generators, certain GSR systems, ophthalmic sources, and other devices. Generator breakthrough is rebuilt: §35.204’s fixed limits removed, new §35.93 requires licensee-written limits and pre-use training, and new §35.3093 requires telephone notice to the NRC Operations Center <i>and</i> the distributor within 7 calendar days, plus a written report within 30 days.</td><td style="border: 1px solid rgb(176, 184, 193);">Review written directives, administration procedures, device QC, Rb-82 breakthrough testing, infusion-system calibration, microsource accountability, training, surveys, and medical-event procedures. Rewrite generator breakthrough procedures — the fixed limits go away and each licensee sets its own.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Byproduct-material licensing structure</b></td><td style="border: 1px solid rgb(176, 184, 193);">§§30.4, 30.35(g), Appendix B to Part 30, 31.13, proposed 31.16, 32.72 and 32.74; §70.25</td><td style="border: 1px solid rgb(176, 184, 193);">Diagnostic, PET, generator, and radiopharmacy activities generally operate through existing specific-license and distribution pathways.</td><td style="border: 1px solid rgb(176, 184, 193);">Proposed §31.16 would create a Standard General License for certain fixed-site diagnostic medical uses. Section 30.4 would broaden PET consortium eligibility; Appendix B to Part 30 financial-assurance values would be revised (conforming change at §70.25), while §30.35(g) picks up a recordkeeping cross-reference for standard general licensees; and §§32.72 and 32.74 would add microsource distribution pathways.</td><td style="border: 1px solid rgb(176, 184, 193);">Determine whether each diagnostic site could qualify for the Standard General License, subject to NRC or Agreement State adoption. Review PET consortium structure, financial-assurance calculations, and microsource procurement and distribution arrangements.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Security for applicable high-activity material</b></td><td style="border: 1px solid rgb(176, 184, 193);">91 FR 17893: §§37.23, 37.25, 37.43(c)(3), 37.45(d), 37.49, 37.51 and 37.53. 91 FR 38124 separately amends §§37.5 and 37.11. §37.55 existing, not amended.<br><br><i>Source rule: 91 FR 17893, Docket NRC-2025-1238 — comments closed May 11, 2026</i></td><td style="border: 1px solid rgb(176, 184, 193);">Facilities possessing Category 1 or Category 2 quantities follow prescriptive Part 37 access-authorization, training, coordination, monitoring, maintenance, and testing requirements.</td><td style="border: 1px solid rgb(176, 184, 193);">Remove the ten-year reinvestigation in §37.25(c); change security refresher training (§37.43(c)(3)) and law-enforcement coordination (§37.45(d)) from not-to-exceed 12 months to at least every 3 years; remove Category 2 weekly verification and the security communications capability requirement (§37.49(a)(3)(ii) and (c)); remove and reserve §37.51, with §37.43(c)(3)(iv) amended (the codified text retains (iv) and the compatibility table says “Amend,” contradicting the preamble); and permit reliance on vehicle key removal under §37.53(b).</td><td style="border: 1px solid rgb(176, 184, 193);">Map the existing security plan against each affected section. <b>Do not eliminate current controls unless and until the final rule and applicable Agreement State regulations become effective.</b> The rule estimates ~960 affected licensees and names, among them, “medical facilities using stereotactic radiosurgery devices; self-shielded irradiator users (such as those operating blood irradiators); teletherapy unit operators.” Programs that do not think of themselves as security licensees are in scope.</td></tr><tr><td style="border: 1px solid rgb(176, 184, 193); background-color: rgb(242, 245, 249);"><b>Audit readiness</b></td><td style="border: 1px solid rgb(176, 184, 193);">§20.1101(c); §37.55 for applicable Category 1/2 programs; applicable license conditions</td><td style="border: 1px solid rgb(176, 184, 193);">Radiation-protection program reviews and internal audits commonly emphasize records, postings, surveys, training, inventory, and completion of required forms.</td><td style="border: 1px solid rgb(176, 184, 193);">A more performance-based framework would place greater weight on the documented technical basis for licensee decisions. Section 20.1101(c) would continue to require periodic review of the radiation-protection program.</td><td style="border: 1px solid rgb(176, 184, 193);">Expand audits to evaluate the technical basis for dose thresholds, shielding, public-dose assessments, patient release, caregiver calculations, AU credentialing, security controls, and corrective actions.</td></tr></tbody></table><p style="font-weight: 400; font-variant-ligatures: normal; font-size: 11.5px; color: rgb(74, 74, 74); margin-top: 12px;"><b>Status:</b> These are proposed federal changes. Current regulations and license conditions remain controlling until a final rule becomes effective and, where applicable, the Agreement State adopts compatible regulations.</p></h2></div><div><br></div></div></body></html>