Okla. Admin. Code § 310:675-7-12.1

Current through Vol. 41, No. 24, September 3, 2024
Section 310:675-7-12.1 - Internal facility incident reports
(a)Incident defined. An incident is any accident or unusual occurrence where there is apparent injury or where injury may or may not have occurred. The incident report shall cover all unusual occurrences within the facility, or on the premises, affecting residents, and incidents within the facility or on the premises affecting visitors or employees.
(b)Incident records. Each facility shall maintain an incident report record and shall have incident report forms available.
(c)Incident report format. The incident report shall include, at a minimum: the date, location and type of incident; parties notified in response to the incident; description of the incident; the relevant resident history; summary of the investigation; and name of person completing the report.
(d)Incident report preparation. At the time of the incident, the administrator, or the person designated by the facility with authority to exercise normal management responsibilities in the administrator's absence, shall be notified of the incident and prepare the report. The report shall include the names of the persons witnessing the incident and their signatures where applicable.
(e)Incident records on file. A copy of each incident report shall be on file in the facility.
(f)Incident in clinical record. The resident's clinical record shall describe the incident and indicate the findings on evaluation of the resident for injury.
(g)Incidents: reviewers. All incident reports shall be reviewed by the director of nursing and the administrator and shall include corrective action taken where health and safety are affected.

Okla. Admin. Code § 310:675-7-12.1

Added at 9 Ok Reg 3163, eff 7-1-92 (emergency); Added at 10 Ok Reg 1639, eff 6-1-93; Amended at 24 Ok Reg 2030, eff 6-25-071; Amended at 25 Ok Reg 2482, eff 7-11-08; Amended at 26 Ok Reg 2059, eff 6-25-09
Amended by Oklahoma Register, Volume 34, Issue 24, September 1, 2017, eff. 10/1/2017
1See Editor's Note at beginning of this Chapter.