Wash. Admin. Code § 388-60A-0425

Current through Register Vol. 24-12, June 15, 2024
Section 388-60A-0425 - Re-offenses and noncompliance during treatment-What must happen if a participant re-offends or is not compliant while they are in treatment?

Each treatment program certified for any level of domestic violence intervention treatment must ensure:

(1) The treatment program has defined what it means to re-offend, including abusive or controlling behaviors that may or may not be illegal.
(2) The treatment program has established and written consequences if a participant re-offends during treatment or does not comply with program requirements.
(3) The program has documented that the participant was made aware of the consequences of re-offending prior to starting treatment.
(4) If the participant re-offends during treatment the program must document in the participant's record:
(a) The details of the re-offense;
(b) Any changes to the ongoing assessment, treatment plan, level of treatment, or minimum treatment period and requirements for the participant as a result of the re-offense or if the program has discharged the participant because the program feels the participant is unlikely to benefit from additional time at the program; and
(c) The notification of the re-offense to the referral source.
(5) The program must document re-offenses or noncompliance in:
(a) The participant's record;
(b) Reports to the court, if applicable; and
(c) Reports to the victim, if feasible.
(6) When a participant is non-compliant with their contract, program rules, or attendance, within seven days of the non-compliance the program must:
(a) Notify the court or other referral source, if applicable; and
(b) Document in the participant's file:
(i) The details of the non-compliance;
(ii) The consequences imposed by the program and referral source, if applicable; and
(iii) Any changes to the participant's ongoing assessment and treatment plan as a result of the non-compliance.

Wash. Admin. Code § 388-60A-0425

Adopted by WSR 18-12-034, Filed 5/29/2018, effective 6/29/2018