Judges, Court Personnel trained on Mental Health First Aid Tuesday, May 14, 2024

Nine training sessions were offered throughout the state over the past nine months with 231 court employees, judges, and work group members participating. The court partnered with FirstLink of Fargo to provider the training. FirstLink is a free, confidential service offering listening and support, referrals to resources/help, and crisis intervention 24 hours a day. FirstLink answers the 211 Information & Referral Helpline, and the 988 Suicide & Crisis Lifeline for North Dakota.

Mental Health First Aid training teaches participants how to identify, understand, and respond to signs of mental illness and substance use disorders. The training teaches how to reach out and provide initial support to someone who may be developing a mental health or substance use problem and help connect them to the appropriate care. The day-long program covers common signs and symptoms of mental illness and substance use; how to interact with a person in crisis; and content on trauma, addiction and self-care.

The Workgroup is chaired by Judge Brad Cruff, Southeast Judicial District.

Staff from Unit 4 share their recovery poster.

Unit 1 personnel gather in Grand Forks for training.

Judge Brad Cruff leads a brainstorming activity on active listening.

Unit 3 judges and staff work with Justice Doug Bahr on a group exercise.

Unit 2 personnel work on their recovery project.

Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>