Legislative intelligence / 90R
SESSION 2027View project ↗

Health and Safety Code § 61.059: NOTIFICATION OF PROVISION OF EMERGENCY SERVICES

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Health and Safety Code Chapter 61, 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. 61.059. NOTIFICATION OF PROVISION OF EMERGENCY SERVICES. (a) If a nonmandated provider delivers emergency services to a patient who the provider suspects might be eligible for assistance under this subchapter, the provider shall notify the hospital that emergency services have been or will be provided to the patient. The notice shall be made:

(1) by telephone not later than the 72nd hour after the provider determines that the patient resides in the hospital's service area; and

(2) by mail postmarked not later than the fifth working day after the date on which the provider determines that the patient resides in the hospital's service area.

(b) The provider shall attempt to determine if the patient resides in a public hospital's service area when the patient first receives services.

(c) The provider, the patient, and the patient's family shall cooperate with the public hospital in determining if the patient is an eligible resident of the hospital's service area.

(d) Not later than the 14th day after the date on which the public hospital receives sufficient information to determine eligibility, the hospital shall determine if the patient is eligible for assistance from the hospital. If the hospital does not determine the patient's eligibility within that period, the patient is considered to be eligible. The hospital shall notify the provider of its decision.

(e) If the public hospital and the provider disagree on the patient's residence or eligibility, the hospital or the provider may submit the matter to the department as provided by Section 61.004.

(f) If a provider delivers emergency services to a patient who is eligible for assistance under this subchapter and fails to comply with this section, the provider is not eligible for payment for the services from the public hospital serving the area in which the patient resides.

(g) If emergency services are customarily available at a facility operated by a public hospital, that hospital is not liable for emergency services furnished to an eligible resident by another provider in the area the hospital has a legal obligation to serve.

Acts 1989, 71st Leg., ch. 678, Sec. 1, eff. Sept. 1, 1989. Amended by Acts 1999, 76th Leg., ch. 1377, Sec. 1.21, eff. Sept. 1, 1999; Acts 2001, 77th Leg., ch. 1128, Sec. 4, eff. Sept. 1, 2001.

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.