Legislative intelligence / 90R
SESSION 2027View project ↗

HB 915: Relating to opioid overdose training for peace officers.

Session
90th Texas Legislature, Regular Session
Status
Filed
Filed
Nov 9, 2026
Most recent action
11/09/2026 H Filed
Authors
Bowers
Official subjects
Alcoholism & Drug Abuse; Crimes--Drugs; Law Enforcement; CONTINUING EDUCATION; PEACE OFFICERS; STAFF DEVELOPMENT & TRAINING; LAW ENFORCEMENT, TEXAS COMMISSION ON

AI summary (not official): Requires peace officers to complete training on recognizing opioid overdoses and administering opioid antagonists.

Topics: Public safety. From AI review or caption rules.

Agencies it could affect (possible, not confirmed): Texas Commission on Law Enforcement. From AI review or caption rules.

Laws this bill changes

Bill text (Introduced)

By: Bowers H.B. No. 915

A BILL TO BE ENTITLED

AN ACT

relating to opioid overdose training for peace officers.

BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF TEXAS:

SECTION 1.

Section 1701.253, Occupations Code, is amended by adding Subsection (u) to read as follows:

(u) As part of the minimum curriculum requirements, the commission shall require an officer to complete the training program established under Section 1701.273.

SECTION 2.

Subchapter F, Chapter 1701, Occupations Code, is amended by adding Section 1701.273 to read as follows:

Sec. 1701.273. TRAINING PROGRAM ON OPIOID OVERDOSES. The commission by rule shall establish and maintain a training program on opioid overdoses. The program must include instruction on:

(1) recognizing the signs and symptoms of an opioid overdose; and

(2) administering all types of opioid antagonists, including injectable and nasal opioid antagonists.

SECTION 3.

Subchapter H, Chapter 1701, Occupations Code, is amended by adding Section 1701.3526 to read as follows:

Sec. 1701.3526. CONTINUING EDUCATION ON OPIOID OVERDOSES. As part of the continuing education programs under Section 1701.351(a), an officer shall complete the training program on opioid overdoses established under Section 1701.273.

SECTION 4.

As soon as practicable after the effective date of this Act, the Texas Commission on Law Enforcement shall adopt rules to implement the changes in law made by this Act.

SECTION 5.

The minimum curriculum requirements under Section 1701.253(u), Occupations Code, as added by this Act, apply only to an officer who first begins to satisfy those requirements on or after January 1, 2028.

SECTION 6.

Section 1701.3526, Occupations Code, as added by this Act, applies only with respect to a 24-month continuing education training unit that begins on or after the effective date of this Act. A training unit that begins before the effective date of this Act is governed by the law in effect on the date the training unit began, and the former law is continued in effect for that purpose.

SECTION 7.

This Act takes effect September 1, 2027.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.