All regulatory updates
718 results found
Louisiana Board of Pharmacy posted Regulatory Proposal 2025-F to revise Controlled Dangerous Substances rules, including incorporating DEA regulations (21 CFR Parts 1300–1399) by reference
The Louisiana Board of Pharmacy has published a regulatory proposal package (Regulatory Proposal 2025-F) to amend its Controlled Dangerous Substances rules (Title 46, Part LIII, Chapter 27). The proposal described in the draft would reduce redundancy by incorporating federal DEA controlled substance regulations (21 CFR Parts 1300–1399) by reference and consolidating Louisiana-specific deviations into a specified section (e.g., §2713), with repeal/cleanup of redundant provisions. If adopted, controlled-substance registrants and pharmacies would need to align procedures and documentation to the updated LAC structure and the incorporated federal requirements as referenced by the Board rule.
Philippines FDA Circular No. 2025-002 implements ASEAN Cosmetic Directive amendments adopted by the ASEAN Cosmetic Committee (ACC)
FDA Philippines issued Circular No. 2025-002 adopting ASEAN Cosmetic Directive (ACD) updates/amendments agreed at the 39th ASEAN Cosmetic Committee (ACC) meeting and related meetings. The circular highlights, among others: (1) DEET (N,N-diethyl-m-toluamide) inclusion in ACD Annex II (prohibited substances) (Ref. A1144); (2) continued allowance/restrictions for Zinc Pyrithione (ZPT) under specified concentration limits for certain rinse-off and leave-on products (as described on the circular page); (3) Acid Yellow 3 restrictions for non-oxidative hair dye; and (4) clarifications/edits affecting Silver Zinc Zeolite (product type wording), Salicylic Acid (product type wording), and Titanium Dioxide (reference correction). Compliance teams in cosmetics should review ingredient compliance against the updated ACD annex positions reflected in the circular and track any stated transition/grace periods referenced in the circular text for marketability/withdrawal of non-compliant products.
Louisiana Board of Pharmacy proposes major Controlled Dangerous Substances rule overhaul adopting 21 CFR Parts 1300–1399 by reference (anticipated effective June 20, 2026)
The Louisiana Board of Pharmacy CDS rulemaking project proposes restructuring LAC 46:LIII, Chapter 27 by adopting federal controlled substance regulations (21 CFR Parts 1300–1399) by reference, consolidating Louisiana-specific deviations into a dedicated section, and repealing redundant provisions. The project also indicates a distributor reporting approach where ARCOS-related reports would be provided upon request (rather than routine submissions). Compliance teams for CDS licensees should plan for potential harmonization with federal DEA requirements and identify Louisiana-specific deltas once finalized, given the stated anticipated effective date.
Louisiana Act 233 (HB 12, 2025) amends UCDSL hemp-related provisions and creates new consumable hemp product offenses (effective Aug 1, 2025)
Louisiana Act 233 (HB 12, 2025 Regular Session) creates new crimes and penalties related to consumable hemp products and explicitly amends Uniform Controlled Dangerous Substances Law-related provisions (including R.S. 40:961.1 and R.S. 40:966(A)(3), per the official résumé digest). Compliance impact: entities manufacturing, distributing, or selling consumable hemp products in Louisiana must implement age-gating and distribution controls, and review product/regulatory conformity requirements to avoid the new criminal exposure; the act also adjusts the boundary/operation of the UCDSL industrial hemp exemption and related controlled-substance applicability. The résumé digest states an effective date of August 1, 2025.
IDFPR reiterates pharmacist protections and limitations under ICSA §311.6(e) for non-electronic controlled substance prescriptions
IDFPR’s Compliance Capsule reiterates key compliance interpretations under 720 ILCS 570/311.6(e) related to electronic controlled substance prescribing: pharmacists dispensing in good faith on a valid non-electronic prescription may be exempt from discipline; pharmacists are not required to ensure prescriber compliance with e-prescribing mandates; and pharmacies should not refuse to fill a valid prescription solely because it is not electronic. Compliance programs should align pharmacy SOPs, training, and refusal criteria to this clarification to reduce disciplinary risk and patient access issues.
No verified SEC-01 amendments or recent updates found in reviewed official sources (baseline policy remains Dec 10, 2024 adoption/approval)
A review of the official WaTech SEC-01 policy PDF and related WaTech board/website materials did not identify any new amendment, emergency revision, newly issued SEC-01 guidance, or changed compliance deadline within the research period. The controlling artifact located remains the SEC-01 Washington State Cybersecurity Program Policy adopted and approved on 2024-12-10 (with sunset review 2027-12-10), which continues to require agencies to maintain an agency cybersecurity program (with at least annual review) and provide annual certification/attestation to WaTech. Compliance teams should treat the current SEC-01 as the baseline and monitor WaTech/TSB channels for future revisions.
Washington Legislature bill SB 6281 proposes cloud-service procurement assessment criteria referencing SEC-01 (including future amendments)
Washington State SB 6281 (2025–26 biennium) includes proposed language that would require an assessment prior to purchase of third-party commercial cloud computing services, including evaluation of cybersecurity and regulatory compliance criteria tied to the 'Washington state cybersecurity program policy' (SEC-01) and any subsequent amendments. This is not an amendment to SEC-01 itself, but it would elevate SEC-01 as a statutory reference point for procurement/compliance assessments if enacted.
TE Connectivity issues PFAS customer letter (Jan 2025) describing PFAS supply-chain inquiry and compliance drivers referenced by TE
TE Connectivity published a customer letter dated January 2025 outlining its approach to PFAS within TE’s product environmental compliance program, which is part of TE’s broader banned/restricted substances expectations. The letter states TE is going beyond currently regulated PFAS and is querying its supply base for PFAS (CAS-number-based) presence across sellable products, and it highlights regulatory/compliance drivers (e.g., TSCA PFAS reporting, EU REACH universal PFAS restriction proposal, and evolving state PFAS product restrictions) as context for TE’s data collection and declarations. This is a company compliance communication (not a law), but it can require supplier responses, updated material declarations, and PFAS presence assessments to meet TE customer/supplier compliance expectations.
NIOSH issues science policy recommending individual quantitative fit-testing for hearing protection, superseding prior derating guidance
NIOSH published an official science policy update recommending employers use individual, quantitative fit testing to evaluate the actual attenuation achieved by workers using hearing protection devices. The policy states it supersedes NIOSH’s earlier hearing protector derating guidance in the 1998 Criteria for a Recommended Standard—Occupational Noise Exposure. This guidance is relevant for occupational hearing conservation programs that previously relied on NRR-based derating assumptions and may drive updates to internal program practices (e.g., adoption of Personal Attenuation Rating (PAR)-based verification).
NIOSH Science Policy Update recommends individual quantitative fit-testing for hearing protection devices (Personal Attenuation Rating)
NIOSH issued a Science Policy Update (Publication 2025-104) recommending employers use individual, quantitative fit testing for hearing protection devices to determine a worker-specific Personal Attenuation Rating (PAR), rather than relying on derating of manufacturer Noise Reduction Ratings (NRR). This guidance affects hearing conservation program practices (fit-testing adoption, documentation, training, and procurement of fit-test systems) for organizations that align programs with NIOSH best practices.
Miami-Dade County publishes/maintains Vendor Insurance requirements for County contracts (COI submission within 10 business days; maintain coverage; airport contractors $5M liability/auto)
Miami-Dade County’s official “Vendor Insurance” procurement page sets/communicates vendor insurance conditions for County contracting. Key compliance points on the page and linked documents include: (1) vendors must carry appropriate insurance to be awarded a County contract; (2) vendors must submit required insurance certificate(s) within 10 business days of procurement notification; (3) awarded vendors must maintain required coverage for the full contract term; and (4) contractors working at Miami International Airport must meet elevated public liability and auto coverage limits of $5 million to access the Airside Operations Area (with restrictions on vehicle authorization). Supporting PDFs provide COI formatting and instructions, including additional-insured and certificate-holder language, and sample letters for waiver/exception scenarios (e.g., no owned vehicles; workers’ compensation exemption request for small employers). The research did not identify a specific recent amendment date or change log; the page footer shows © 2025, so treat this as current official requirements/guidance rather than a newly adopted regulatory change.
EPA final rule updates TSCA New Chemicals regulations (PFAS ineligible for LVE/LoREX; approvals required before manufacture)
EPA finalized updates to TSCA New Chemicals Program regulations (40 CFR parts 720, 721, 723, 725). Key compliance impacts include making PFAS categorically ineligible for Low Volume Exemptions (LVE) and Low Release and Exposure Exemptions (LoREX), and requiring EPA approval of LVE/LoREX before manufacture can commence, along with broader procedural updates aligning with Lautenberg amendments. Companies submitting PMNs/SNUNs/MCANs or relying on exemptions should update internal review timelines, exemption eligibility screening (including PFAS determination), and submission completeness processes.
EPA final rule updates TSCA New Chemicals regulations (including PFAS/PBT ineligibility for LVE/LoREX and updated determination requirements)
EPA finalized amendments to the TSCA new chemicals regulations governing EPA’s review of Premanufacture Notices (PMNs) and Significant New Use Notices (SNUNs). The research summary highlights changes that (a) make PFAS and other PBT chemicals ineligible for certain exemptions (e.g., Low Volume Exemption (LVE) / LoREX) and (b) require EPA to make one of the statutory determinations before manufacture/processing may begin. Compliance teams should review impacts on new chemical submissions, exemption strategies, and any PFAS/PBT-related R&D/manufacturing plans, and update internal submission workflows accordingly.
WaTech issues SEC-01 Washington State Cybersecurity Program Policy replacing portions of IT Standard 141.10 (sections 1.1 and 2.1–2.5)
WaTech/OCIO adopted and the Technology Services Board (TSB) approved SEC-01 “Washington State Cybersecurity Program Policy” (State CIO Adopted and TSB Approved: Dec. 10, 2024). The policy explicitly states it replaces IT Policy 141 and replaces specified portions of IT Security Standard 141.10 (sections 1.1 and 2.1–2.5, originally effective Nov. 13, 2017). Compliance teams tracking OCIO Standard 141.10 should update their control mapping and internal governance documentation to reflect that these sections are now governed by SEC-01 (including program documentation review cadence and enterprise cybersecurity program requirements).
SEC-01-01-G Security Principles Guideline published as companion guidance under SEC-01 (adopted/approved)
WaTech published the SEC-01-01-G Security Principles Guideline, a companion guidance document associated with the SEC-01 Washington State Cybersecurity Program Policy. The guideline sets out security principles intended to inform security programs/policies/standards and security-related decision-making across covered organizations. The document metadata shows it was adopted by the State CIO and approved by the Technology Services Board on 2024-12-10, with a sunset review date of 2027-12-10.
WaTech publishes SEC-01 Washington State Cybersecurity Program Policy (State CIO adopted/TSB approved Dec. 10, 2024)
WaTech has issued SEC-01 (Washington State Cybersecurity Program Policy) as the statewide policy establishing enterprise cybersecurity program requirements for Washington State agencies (e.g., maintaining an agency cybersecurity program aligned to WaTech security policies/standards and related governance expectations). The policy is shown on WaTech’s official policy landing page with an official PDF. For compliance teams, this signals SEC-01 is the governing cybersecurity program policy for Washington State agencies and should be used as the baseline policy reference for agency cybersecurity program structure and oversight expectations.
Washington State SEC-01 Cybersecurity Program Policy adopted and approved (replacing IT Policy 141 and parts of IT Standard 141.10)
WaTech’s SEC-01 Washington State Cybersecurity Program Policy was adopted by the State CIO and approved by the Technology Services Board on 2024-12-10. The policy establishes enterprise cybersecurity program requirements for covered Washington State agencies (and entities using WaTech services for the services provided), including maintaining an agency cybersecurity program, annual review and updates after significant change, annual certification/attestation by agency leadership to WaTech regarding implementation and compliance with enterprise security policies/standards, and alignment of vendor/partner contract language with security requirements. The policy states it replaces prior IT Policy 141 and IT Standard 141.10 (as indicated in the policy metadata). The document also lists a sunset review date of 2027-12-10 (not a compliance deadline).
WaTech publishes SEC-01-01-G Security Principles Guideline (companion guidance under SEC-01)
WaTech issued the SEC-01-01-G Security Principles Guideline as a companion guidance document tied to the SEC-01 Washington State Cybersecurity Program Policy. Compliance teams should review this guideline for implementation expectations and security principles that support SEC-01 program requirements (e.g., how agencies interpret and operationalize security program controls and practices).
WaTech SEC-01 Washington State Cybersecurity Program Policy replaces portions of OCIO Standard 141.10 (sections 1.1 and 2.1–2.5)
WaTech/OCIO issued the SEC-01 Washington State Cybersecurity Program Policy, which explicitly replaces specified portions of OCIO Standard 141.10 (Securing Information Technology Assets), namely sections 1.1 and 2.1–2.5 (previously dated November 13, 2017 per the SEC-01 replacement statement). For compliance teams, this is a governance/control-framework change requiring re-mapping internal policies, control libraries, and audit criteria from the referenced 141.10 sections to SEC-01 requirements and any linked standards/waiver processes referenced by SEC-01.
WaTech adopts SEC-01 Washington State Cybersecurity Program Policy (replacing IT Policy 141 and portions of IT Standard 141.10)
Washington Technology Solutions (WaTech) published the SEC-01 Washington State Cybersecurity Program Policy, adopted by the State CIO and approved by the Technology Services Board on Dec. 10, 2024. The policy replaces legacy statewide security artifacts (IT Policy 141 and specified sections of IT Standard 141.10) and establishes core agency obligations including maintaining an agency cybersecurity program with at least annual review and providing annual agency head/CIO attestation of compliance to WaTech, plus requirements to align vendor/partner contract language with state and agency security requirements.