Verify Incident Management Setup

Incident types, codes, and subcodes are set up at the district level. Use the following to load, verify, and edit incident management types, codes, and subcodes.

To create DIRS/Federal incidents, security groups must be granted access to the Incident Types that have the caret (^) at the end of the Incident Type Name. Refer to System Help in PowerSchool for more information on how to set up group-level permissions.

Codes and Subcodes

Code types are used as an organizational tool to categorize incidents. PowerSchool includes 11 system-defined, non-editable code types that provide the basis from which all user-defined incident codes, subcodes, and secondary subcodes are created.

Auto Setup

You can load the code and subcode values automatically using a one-time Minnesota configuration file.

Navigation: Start Page > District Setup > District Info > Load Codes/Subcodes > Codes and Subcodes Load Information

Click Load Codes and Subcodes.
Note: The new Incident Management codes will be added to the database after either a) the hourly process runs, or b) PowerSchool is restarted.

Manual Setup and Verification

Navigation: Start Page > District Setup > Incident Management > Code & Subcode Setup

Use the expand/collapse icon to display the code type list. After selecting a code type, the code and subcodes for that type are displayed at the bottom of the page with another expand/collapse icon. For a list of codes and subcodes, see Incident Management Codes and Subcodes.

To verify that a code exists:

Click a Code Type. A section for the Code Type appears at the bottom of the page.
Review the list of codes. Add new codes if applicable.
Repeat steps 1 and 2 for all Code Types.

To add a new code:

Click a Code Type. A section for the Code Type appears at the bottom of the page.
Click the Add icon (plus sign).
Complete the fields, and click Submit.
Repeat this process to create subcodes, selecting the appropriate code in step 1 instead of the code type.

Data Element	Additional Information	[Table]FieldName
Action Codes	Action codes are used to assign disciplinary action to a behavior.	[Incident_LU_Code]Code_Type=actioncode [Incident_LU_Code]Incident_Category
Action Subcodes	Action subcodes are used to further define action codes.	[Incident_LU_Sub_Code]Sub_Category [Incident_LU_Sub_Code]State_Detail_Report_Code
Attribute Codes	Attribute codes are used to describe further details about an incident.	[Incident_LU_Code]Code_Type=attributecode [Incident_LU_Code]Incident_Category
Behavior Codes	Behavior codes are used to associate a behavior (alcohol, fights, vandalism, etc.) to an offender in an incident.	[Incident_LU_Code]Code_Type=behaviorcode [Incident_LU_Code]Incident_Category
Behavior Subcodes	Behavior subcodes are used to further define behavior codes.	[Incident_LU_Sub_Code]Sub_Category [Incident_LU_Sub_Code]State_Detail_Report_Code
Participant Attribute Codes	Participant attribute codes are used to describe detail about a participant.	[Incident_LU_Code]Code_Type=participantattributecode [Incident_LU_Code]Incident_Category
Location Codes	Location codes are used to identify the location of an incident.	[Incident_LU_Code]Code_Type=locationcode [Incident_LU_Code]Incident_Category
Location Subcodes	Location subcodes are used to further define location codes.	[Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code
Object Codes	Object codes are used to describe an item used in the incident.	[Incident_LU_Code]Code_Type=objectcode [Incident_LU_Code]Incident_Category
Participant Role Codes	The following participant role codes are set up by default and should not be edited: Offender Victim Witness Reporter	N/A
Time Codes	Time codes are used to assign a time of day (during school hours, outside school hours, etc.) to an incident.	[Incident_LU_Code]Code_Type=timecode [Incident_LU_Code]Incident_Category
Duration Codes	Duration (days) is assigned to a disciplinary action as the result of a reportable behavior in an incident.	[Incident_LU_Code]Code_Type=durationcode [Incident_LU_Code]Incident_Category
Action Change Codes	Action change codes are used to describe the reasons an action was changed. These codes are not used in DIRS or Federal Reporting.	[Incident_LU_Code]Code_Type=actionchangecode [Incident_LU_Code]Incident_Category
Action Attributes	Action attributes are used to describe further details about an action taken in response to an incident.	[Incident_LU_Code]Code_Type=actionattribute [Incident_LU_Code]Incident_Category

Incident Types

Use this page to manually create or edit the Minnesota incident management type.
Any incident type that has the caret (^) at the end of the name (i.e. (DIRS/CRDC) Discipline^) will be used for DIRS and Federal reporting.
Codes that have been defined with a 'State Aggregate Report Code' or a 'State Detail Report Code' within these incident types will be pulled into the DIRS and Federal reporting.

Note: To create incidents, security groups must be granted access to the an incident type.

Refer to System Help in PowerSchool for more information on how to set up group-level permissions.

Navigation: Start Page > District Setup > Incident Management > Incident Types

Data Element

Additional Information

[Table]FieldName

Name

Using incident types, you can control which users can view and enter specific types of incidents. See the PowerSchool System Help for more information.

The following incident type must not be removed or edited.

(DIRS/CRDC) Discipline^

[Incident_LU_Code]Incident_Category

[Incident_LU_Code]Code_Type=incidenttype