WI DPI WISEdata Ed-Fi Docs
/disciplineIncident
Jaidaa Shafaei
heather.kluck
An event entity represents an infraction, spanning from minor behavioral disruptions to criminal acts involving law enforcement. Regardless of the number of perpetrators or victims, a single event constitutes one incident. Discipline incidents are events that merit disciplinary action.
This endpoint is NOT expected from Choice schools.
Ed-Fi Tech Docs: v3 Student Discipline > DisciplineIncident - Ed-Fi Certification - Ed-Fi TechDocs
Data Properties:
# | Property Name | Data Type | Public (Required/ Optional/ Conditional) | Choice (Required/ Optional/ Conditional) | Business Definition | Data Element Page |
|---|---|---|---|---|---|---|
1.0 | schoolId | integer | REQ’D | NOT REQ’D | The identifier assigned to a school. | |
2.0 | incidentIdentifier* | string | REQ’D | NOT REQ’D | A locally assigned unique identifier (within the school or school district) to identify each specific DisciplineIncident or occurrence. The same identifier should be used to document the entire DisciplineIncident even if it included multiple offenses and multiple offenders. | |
3.0 | incidentDate | string | REQ’D | NOT REQ’D | The month, day, and year on which the DisciplineIncident occurred. |
Use Cases:
These are the same uses cases for /studentDisciplineIncidentAssociation and /disciplineAction.
# | Use Case Title | Use Case Description | What to Submit/retrieve |
|---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
|---|---|---|---|
1.0 | Sending one student with one discipline action | This is the most common scenario for discipline. One student is the perpetrator in an incident. For this student only one discipline action occurs which must be submitted to WISEdata. Recall that only a subset of discipline incident, discipline type, and behavior information should be submitted to DPI:
| POST one records on /disciplineIncident, disciplineActions, and /studentDisciplineIncidentAssociation |
2.0 | Sending behavior and behavior detailed description | Behavior Description on /studentDisciplineIncidentAssociation is always required. Behavior detailed descriptor has to be submitted only for incidents where:
For firearm-related incidents meeting the above criteria, this description must provide the reason why the student did not receive the mandatory expulsion. | POST on /studentDisciplineIncidentAssociation: |
3.0 | Sending a discipline incident at the end of school year with expulsion in the next school year | The API is school year based. Submit the incident, association, and action resources in the same school year as the incident. NOTE: Even though the expulsion begins in the next school year, no resources for the incident, association, or action are submitted in next school year. Expulsions are the only discipline actions which may occur in a school year later than the incident. For an incident near the end of the school year that school board may not meet until after the end of the school year or the student may be suspended for the remaining days of the year. In these cases the expulsion discipline date is in the next school year. As there are no days removed for the expulsion in the year of the incident, discipline length is zero. Actual discipline action length should be greater than zero, identifying the total number of school days for this student from the expulsion start date to end date. | POST one records on /disciplineIncident, disciplineActions, and /studentDisciplineIncidentAssociation |
One student and multiple discipline incidents | |||
4.0 | Sending one student with one discipline incidents on a single day (for suspensions or IAES removals) | As a suspension or IAES removal must be at least ½ of the student’s day and an expulsion requires a school board hearing, meeting the requirements for two incidents to be reported on the same is very unlikely. In most cases only one incident is submitted. For example, incident A occurs for an IDEA-eligible student who is removed from the classroom for more than ½ their regular day by in-school suspension. For the same student a second Incident (B) occurs later in the day for which the student receives an out of school suspension for the remainder of that day and the next school day. | Incident A Incident B |
5.0 | Sending one student with one discipline incidents on a single day, but only one discipline incident counts | Consider the example where incident A occurs for an IDEA-eligible student who is removed from the classroom for 1 period in the morning. This is an in-school suspension with less than ½ day discipline length. For the same student a second Incident (B) occurs later in the morning. The student receives an out of school suspension for the rest of the day. | Incident A Incident B POST on /disciplineIncident, |
One student multiple discipline actions | |||
6.0 | Sending one student with multiple discipline actions (out-of-school suspension and expulsion) | Often, an expulsion is preceded by an out-of-school suspension for the days the student is removed while awaiting the expulsion hearing.
| POST on /disciplineIncident |
7.0 | Sending one student with multiple discipline actions that overlap in one day | Days of removal may be reported only once. If a student is removed simultaneously for two actions or two incidents, discipline length as reported to DPI must be truncated, as necessary. For example, if a student receives an in-school suspension for the remaining ¾ of the school day. While in the in-school suspension a second incident occurs for which the student receives out-of-school suspension for the remaining ½ of the school day. The student served ¼ day of in-school suspension (not the ¾ originally ordered) and ½ day of out-of-school suspension. | Incident A Incident B POST on /disciplineIncident, |
8.0 | Sending one student with multiple discipline actions for which days of removal overlap | In this case the school must decide how to either submit only the suspension of greater length or to reduce the suspension of greater length by one week for submission purposes. Consider a student receives an out-of-school suspension for several weeks and a second out of school suspension for one week. The school decides to have the student serve the out-of-school suspensions concurrently for only 3 weeks total.  | NA |
Expulsions | |||
9.0 | Sending one student, and one expulsion with early reinstatement and removal for later violation | When a student has returned to the regular classroom prior to the end of the expulsion under early reinstatement conditions, any infraction which revokes the early reinstatement condition must be treated as additional days removed from the original expulsion. Length should be increased, as appropriate.  | POST on /disciplineIncident, |
10.0 | Sending an expulsion that’s spanning two or more school years | When an expulsion start date is in year X and the end date is in year X+1 or later, actual discipline action length will be greater than discipline length. Consider a student removed 13 days in the school year of the incident and the entire next school year (180 days). Length should be reported as 13, while actual discipline action length is 193. | POST on /disciplineIncident |
11.0 | Sending the specification of modified term type | All expulsion submissions require the Modified Term Type to be passed in the disciplineAction record. LEAs should identify if the duration of the expulsion has been modified from the federally required one year of expulsion for a firearms incident. | POST on /disciplineIncident, |
12.0 | Sending the early reinstatement condition | The Early Reinstatement Condition is required to be passed in the disciplineAction record when disciplineAction = Expulsion. Following an expulsion, a student could have early reinstatement condition to return to school prior to the end of the expulsion. Â | POST on /disciplineIncident, |
Multiple students involved in one incident | |||
13.0 | Sending multiple students involved in one incident, but not all students get a discipline action | Only perpetrators with a reportable disciplinary action shall be submitted to WISEdata. For example, an incident occurs between two non-disabled students. One student (A) receives in-school suspension for 2 days, while the other student (b) receives 2 days out of school suspension.  | POST on /disciplineIncident |
14.0 | Sending multiple students involved in one incident, but with different discipline actions | Reconsider the last example (in use case 13.0) for 2 IDEA-eligible students. One student (A) receives in-school suspension for 2 days, while the other student (b) receives 2 days out of school suspension. | Student A: Student B: |
15.0 | Sending multiple students involved in one incident, but from different schools in the same district | If both students are perpetrators, we expect a separate discipline incident for each student with the schoolReference in the disciplineIncident to match the school tied to the students primary enrollment. | POST on /disciplineIncident: (For each student with a schoolReference to the school they are enrolled) |
Special Cases | |||
16.0 | Sending a student who was removed more than ½ day to another room in same school | The student is removed from the regular classroom for more than ½ day to another room in the same school. This is an in-school suspension and must be reported for all IDEA eligible students. NOTE: This could happen at any grade level. | POST on /disciplineIncident |
17.0 | Sending a student who was removed more than ½ day from school grounds | The student is removed from the regular classroom for more than ½ day to another site, a site off school grounds, or is sent home. This is an out-of-school suspension and must be reported for all students. | POST on /disciplineIncident: |
18.0 | Sending a student with a non-standard school schedule | For students with non-standard school schedules, counting of days removed for discipline purposes will be different from counting days for attendance purposes. Discipline uses the student’s regular day, not a ‘regular’ day in the district. Discipline length rounds up for removals over ½ day. Review the data element summary for discipline length to understand how to submit length in this case. | NA |
19.0 | Sending a special education student attending WSD, WCBVI, or a CCDEB | Discipline information will be submitted by the Wisconsin School for the Deaf (WSD), the Wisconsin Center for the Blind and Visually Impaired (WCBVI), the County Children with Disabilities Board (CCDEB) following the scenarios listed previously. The FAPE responsible school will be held accountable. | NA |
20.0 | Sending a student discipline incident at non-primary enrollment | DPI expects the school holding the student’s primary enrollment to submit discipline incident at the non-primary school. See use cases (7.0 and 8.0) from the /studentSchoolAssociation endpoint. | NA |
Exclusions (data not to be submitted) | |||
21.0 | Non-disabled student given in-school suspension | Discipline information for this student should not be submitted to WISEdata. | NA |
22.0 | Non-disabled student given IAES Removals | IAES Removals (IAES by School Personnel and IAES by Hearing Officer) are given only to disabled students, therefore we should never receive IAES removals for students who are not disabled. NOTE: Only submit out-of-school suspensions and expulsions data for non-disabled students. | NA |
23.0 | Special education student with ISP (Parentally Placed Private Student) | Discipline information for this student should not be submitted to WISEdata. | NA |
24.0 | Student attending DOC or DHS schools | Discipline information for this student should not be submitted to WISEdata. | NA |
25.0 | Student with one suspension from summer school | Discipline information for this student should not be submitted to WISEdata. This student is removed zero days from the school year for a suspension, thus no incident or action is submitted. NOTE: if the discipline action was an expulsion, then this disciplineIncident - disciplineActions pair would be submitted. | NA |
26.0 | Student incident results in IAES removal by School Personnel | True or False should be submitted for the seriousBodilyInjury data property on /studentDisciplineIncidentAssociation when disciplineDescriptor on /disciplineActions is 'IAES removal by School Personnel'. | POST on /disciplineIncident |
JSON Sample:
{
"schoolReference": {
"schoolId": 6,
},
"incidentIdentifier": "INCid-12194",
"incidentDate": "2019-07-11",
}Â
Wisconsin Department of Public Instruction