Reporting toy-related injury or death
- • rules
(1) Whenever any physician determines or reasonably suspects the injury or death of a person to be toy-related, the physician shall, in accordance with rules adopted under subsection (5) of this section, report the physician’s findings to the Director of the Oregon Health Authority.
(2) The director of any hospital, health care facility, health maintenance organization, public health center, medical center or emergency medical treatment facility where any physician has made a determination or has a reasonable suspicion under subsection (1) of this section as to whether an injury or death is toy-related, shall, in accordance with the rules adopted under subsection (5) of this section, report that physician’s findings to the Director of the Oregon Health Authority.
(3) The Director of the Oregon Health Authority shall review, organize and keep a record of the information set forth in the reports of toy-related injuries and deaths submitted by physicians under this section. The director, on a regular basis, shall make the information recorded under this section available to the United States Consumer Product Safety Commission for inclusion in its Injury or Potential Injury Incident Data Base. The information so recorded shall also be made available to the public for a fee determined by the director.
(4) If the director determines that a specific toy or item poses an immediate danger or potential threat to the safety of the citizens of this state, the director shall immediately issue a public notice warning the public, retail sellers and distributors of the director’s findings and recommendations concerning that toy or item.
(5) The director shall adopt rules to implement this section. [1991 c.325 §1; 2009 c.595 §1053]
Note: 677.491 (Reporting toy-related injury or death) was enacted into law by the Legislative Assembly but was not added to or made a part of ORS chapter 677 by legislative action. See Preface to Oregon Revised Statutes for further explanation.
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.