256.35(3s)(a)3.f. f. Provides a secure environment for emergency communications.
256.35(3s)(a)4. 4. “Operational date,” with respect to a county, means the date determined by the department on which Next Generation 911 begins to be fully operational in the county.
256.35(3s)(a)5. 5. “Service supplier” has the meaning given in sub. (3) (a) 3.
256.35(3s)(a)6. 6. “Service user” has the meaning given in sub. (3) (a) 4.
256.35(3s)(b) (b) Emergency services IP network contracts. The department shall invite bids to be submitted under s. 16.75 and, from the appropriation under s. 20.465 (3) (qm), contract for the creation, operation, and maintenance of an emergency services IP network that to the greatest extent feasible relies on industry standards and existing infrastructure to provide all public safety answering points with the network necessary to implement Next Generation 911.
256.35(3s)(c) (c) Existing contracts and charges.
256.35(3s)(c)1.1. The department shall determine the operational date for each county. If a contract under sub. (3) (b) 3. between a service supplier and a county is in effect immediately before the operational date determined for the county, the contract shall expire on the operational date and, except as provided in subd. 2., beginning on the operational date, the service supplier may not bill any service user for a charge levied by the county under sub. (3) (b) or impose a surcharge approved under sub. (3) (f). At least 30 days before a contract expires under this subdivision, the department shall provide written notice of the expiration to the county and service supplier.
256.35(3s)(c)2. 2. If a contract terminates under subd. 1. before a service supplier has been fully compensated for nonrecurring services described in sub. (3) (b) 3. a., the service supplier may continue to bill service users for the charge levied by the county under sub. (3) (b) or impose a surcharge approved under sub. (3) (f) until the service supplier is fully compensated for those nonrecurring services.
256.35(3s)(d) (d) 911 subcommittee duties. The 911 subcommittee shall do all of the following:
256.35(3s)(d)1. 1. Advise the department on the contracts required under par. (b).
256.35(3s)(d)2. 2. Advise the department on the statewide efforts, leveraging of existing infrastructure, and industry standards that are necessary to transition to Next Generation 911.
256.35(3s)(d)3. 3. Make recommendations to the department regarding federal sources of funding and the sustainable funding streams that are required to enable public safety answering points to purchase and maintain equipment necessary for Next Generation 911.
256.35(3s)(d)4. 4. If funding is made available for the department or another state agency to make grants to public safety answering points for training or upgrading facilities or services or for implementing Next Generation 911, advise the department or other state agency on making the grants, including advising on eligibility criteria for the grants. The criteria shall include basic training and service standards that grant applicants must satisfy.
256.35(3s)(d)5. 5. Conduct a statewide 911 telecommunications system assessment.
256.35(3s)(d)6. 6. Develop recommendations for service standards for public safety answering points.
256.35(3s)(d)7. 7. Promote, facilitate, and coordinate interoperability across all public safety answering points with respect to telecommunications services and data systems, including geographic information systems.
256.35(3s)(d)8. 8. Promote, facilitate, and coordinate consolidation of public safety answering point functions where consolidation would provide improved service, increased efficiency, or cost savings.
256.35(3s)(d)9. 9. Undertake all of its duties in a manner that is competitively and technologically neutral.
256.35(4) (4)Departmental advisory authority. The department may provide information to public agencies, public safety agencies and telecommunications utilities relating to the development and operation of emergency number systems.
256.35(6) (6)Telecommunications utility requirements. A telecommunications utility serving a public agency or group of public agencies which have established a sophisticated system under sub. (2) (e) shall provide by December 31, 1985, or upon establishing a system, whichever is later, such public agency or group of public agencies access to the telephone numbers of subscribers and the addresses associated with the numbers as needed to implement automatic number identification and automatic location identification in a sophisticated system, but such information shall at all times remain under the direct control of the telecommunications utility and a telecommunications utility may not be required to release a number and associated address to a public agency or group of public agencies unless a call to the telephone number “911" has been made from such number. The costs of such access shall be paid by the public agency or group of public agencies.
256.35(7) (7)Liability exemption. All of the following shall not be liable to any person who uses an emergency number system created under this section or makes an emergency telephone call initially routed to a wireless public safety answering point, as defined in sub. (3m) (a) 7., 2015 stats.:
256.35(7)(a) (a) A telecommunications utility.
256.35(7)(b) (b) A wireless provider, as defined in s. 256.35 (3m) (a) 6., 2015 stats.
256.35(7)(c) (c) A local government, as defined in s. 256.35 (3m) (a) 4., 2015 stats.
256.35(7)(d) (d) A person that supplies any service, product, equipment, or database, including any related emergency notification service or process, that is used for or in conjunction with the installation, implementation, operation, or maintenance of the emergency number system and that is used by a public safety answering point.
256.35(9) (9)Joint powers agreement.
256.35(9)(a)(a) In implementing a basic or sophisticated system under this section, public agencies combined under sub. (2) (d) shall annually enter into a joint powers agreement. The agreement shall be applicable on a daily basis and shall provide that if an emergency services vehicle is dispatched in response to a request through the basic or sophisticated system established under this section, such vehicle shall render its services to the persons needing the services regardless of whether the vehicle is operating outside the vehicle's normal jurisdictional boundaries.
256.35(9)(b) (b) Public agencies and public safety agencies which have contiguous or overlapping boundaries and which have established separate basic or sophisticated systems under this section shall annually enter into the agreement required under par. (a).
256.35(9)(c) (c) Each public agency or public safety agency shall cause a copy of the annual agreement required by pars. (a) and (b) to be filed with the department of justice. If a public agency or public safety agency fails to enter into such agreement or to file copies thereof, the department of justice shall commence judicial proceedings to enforce compliance with this subsection.
256.35(10) (10)Penalties.
256.35(10)(a)(a) Any person who intentionally dials the telephone number “911" to report an emergency, knowing that the fact situation which he or she reports does not exist, shall be fined not less than $100 nor more than $600 or imprisoned not more than 90 days or both for the first offense and is guilty of a Class H felony for any other offense committed within 4 years after the first offense.
256.35(10)(b) (b) Any person who discloses or uses, for any purpose not related to the operation of a basic or sophisticated system, any information contained in the database of that system shall be fined not more than $10,000 for each occurrence.
256.35(11) (11)Plans. Every public agency establishing a basic or sophisticated system under this section shall submit tentative plans for the establishment of the system as required under this section to every local exchange telecommunications utility providing service within the respective boundaries of such public agency. The public agency shall submit final plans for the establishment of the system to the telecommunications utility and shall provide for the implementation of the plans.
256.35 Cross-reference Cross-reference: See also ch. PSC 173, Wis. adm. code.
256.40 256.40 Opioid antagonists.
256.40(1) (1) In this section:
256.40(1)(a) (a) “Fire fighter" means any person employed by the state or any political subdivision as a member or officer of a fire department or a member of a volunteer fire department, including the state fire marshal and deputies.
256.40(1)(b) (b) “Law enforcement agency" means an agency of a federally recognized Indian tribe or band or a state or political subdivision of a state, whose purpose is the detection and prevention of crime and enforcement of laws or ordinances.
256.40(1)(c) (c) “Law enforcement officer" means any person employed by a law enforcement agency who is authorized to make arrests for violations of the laws or ordinances that the person is employed to enforce.
256.40(1)(d) (d) “Opioid-related drug overdose" means a condition including extreme physical illness, decreased level of consciousness, respiratory depression, coma, or the ceasing of respiratory or circulatory function resulting from the consumption or use of an opioid, or another substance with which an opioid was combined.
256.40(2) (2)
256.40(2)(a)(a) Subject to par. (b), the department shall permit all emergency medical services practitioners to administer naloxone or another opioid antagonist to individuals who are undergoing or who are believed to be undergoing an opioid-related drug overdose.
256.40(2)(b) (b) The department shall require emergency medical services practitioners to undergo any training necessary to safely and properly administer naloxone or another opioid antagonist as specified under par. (a).
256.40(2)(c) (c) Every ambulance service provider shall do all of the following:
256.40(2)(c)1. 1. Ensure that every emergency medical services practitioner under the ambulance service provider's supervision who has obtained the training necessary to safely and properly administer naloxone or another opioid antagonist has a supply of naloxone or the other opioid antagonist available for administration when he or she is performing his or her duties as an emergency medical services practitioner, to the extent that naloxone or the other opioid antagonist is available to the ambulance service provider.
256.40(2)(c)2. 2. Require each certified emergency medical responder and emergency medical services practitioner under the supervision of the ambulance service provider to, in the manner prescribed by the department, keep a record of each instance in which the certified emergency medical responder or emergency medical services practitioner administers naloxone or another opioid antagonist to an individual who is undergoing or who is believed to be undergoing an opioid-related drug overdose.
256.40(2)(c)3. 3. Submit records under subd. 2. to the department in the manner prescribed by the department.
256.40(3) (3)
256.40(3)(a)(a) A law enforcement agency or fire department may enter into a written agreement to affiliate with an ambulance service provider or a physician for all of the following purposes:
256.40(3)(a)1. 1. Obtaining a supply of naloxone or another opioid antagonist.
256.40(3)(a)2. 2. Allowing law enforcement officers and fire fighters to obtain the training necessary to safely and properly administer naloxone or another opioid antagonist to individuals who are undergoing or who are believed to be undergoing an opioid-related drug overdose.
256.40(3)(b) (b) A law enforcement officer or fire fighter who, reasonably believing another person to be undergoing an opioid-related drug overdose, administers naloxone or another opioid antagonist to that person shall be immune from civil or criminal liability for any outcomes resulting from the administration of the opioid antagonist to that person, if the law enforcement officer or fire fighter is acting pursuant to an agreement and any training obtained under par. (a).
256.40 History History: 2013 a. 200; 2017 a. 12.
Loading...
Loading...
2015-16 Wisconsin Statutes updated through 2017 Wis. Act 64 and all Supreme Court and Controlled Substances Board Orders effective on or before November 20, 2017. Published and certified under s. 35.18. Changes effective after November 20, 2017 are designated by NOTES. (Published 11-20-17)