Legislative intelligence / 90R
SESSION 2027View project ↗

Health and Safety Code § 161.00705: RECORDING ADMINISTRATION OF IMMUNIZATION AND MEDICATION FOR DISASTERS AND EMERGENCIES

1 bill in the 90th Legislature would change this section

  • SB 81 amends this section

Part of Health and Safety Code Chapter 161, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 161.00705. RECORDING ADMINISTRATION OF IMMUNIZATION AND MEDICATION FOR DISASTERS AND EMERGENCIES. (a) The department shall maintain a registry of persons who receive an immunization or antiviral administered to prepare for a potential disaster, public health disaster, terrorist attack, hostile military or paramilitary action, or extraordinary law enforcement emergency or in response to a declared disaster, public health disaster, terrorist attack, hostile military or paramilitary action, or extraordinary law enforcement emergency. A health care provider who administers an immunization or antiviral shall provide the data elements to the department. At the request and with the authorization of the health care provider, the data elements may be provided through a health information exchange as defined by Section 182.151.

(b) The department shall maintain the registry as part of the immunization registry required by Section 161.007.

(c) The department shall track adverse reactions to an immunization or antiviral administered to prepare for a potential disaster, public health disaster, terrorist attack, hostile military or paramilitary action, or extraordinary law enforcement emergency or in response to a declared disaster, public health disaster, terrorist attack, hostile military or paramilitary action, or extraordinary law enforcement emergency. A health care provider who administers an immunization or antiviral may provide data related to adverse reactions to the department.

(d) Sections 161.007, 161.0071, 161.0072, and 161.0074 apply to the data elements submitted to the department under this section, unless a provision in those sections conflicts with a requirement in this section.

(e) The executive commissioner by rule shall determine the period during which the information collected under this section must remain in the immunization registry following the end of the disaster, public health emergency, terrorist attack, hostile military or paramilitary action, or extraordinary law enforcement emergency.

(f) Unless an individual or the individual's legally authorized representative consents in writing or electronically to continued inclusion of the individual's information in the registry, the department shall remove the immunization records collected under this section from the registry on expiration of the period prescribed under Subsection (e).

(g) The immunization information of a child or other individual received by the department under this section, including individually identifiable information, may be released only:

(1) on consent of the individual or, if a child, the child's parent, managing conservator, or guardian; or

(2) to a state agency or health care provider consistent with the purposes of this subchapter or the purposes of aiding or coordinating communicable disease prevention and control efforts during a declared disaster, public health emergency, terrorist attack, hostile military or paramilitary action, or extra

The section continues: whole chapter.

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.