Skip to main content
Skip table of contents

Guidance For Publishing Discipline Data

Introduction

Starting 2023-24, districts are required to submit the Discipline Data using AzEDS publishing. This section describes the publishing logic that has been implemented.

Selection Criteria

  • The student must have a valid enrolment record during the session.

  • The student must not be excluded from State Reporting.

  • The school in which the student is enrolled must not be excluded from State Reporting.

  • The Incident School must be associated with a school in which the student is enrolled (also applicable to Concurrent School Enrollments).

  • The Incident Type must be State Reportable - Mandatory^.

  • The Action Code (Discipline Descriptors) and the Behavior Codes (Behavior Descriptors) must be mapped under Code Set Mappings.

    • Navigation to the Code Set Mappings in the Enhanced UI:

      • From District Office: Start Page, System Management, Data Exchange, Code Set Mappings

    • Navigation to the Code Set Mappings in the Old UI:

      • From District Office: Start Page, District Office, System Administrator, Code Set Mappings

  • Only parent action codes and the parent behavior codes will get published. The sub-codes will neither get considered for publishing nor will get mapped under code-set mappings.

  • The Behavior and the action must be attached to the student.

  • The Incident Record must have a valid school selected, the data does not get published if the District Office or any of the selected schools is excluded from State Reporting.

  • For publishing the Discipline data via Concurrent Enrollment school, the incident record must be created from the Concurrent School Of Enrollment.

The sequence in which the action and behavior must be associated with the student when creating a Detailed Incident Record:

  • If there is only one action and only one behavior for a student then it can be associated in any sequence and the data will get published correctly.

  • If there are more than one action for multiple behaviors, then the behavior must selected first and then the corresponding action must be associated in sequence. Otherwise, the data will not get published correctly or will publish in the wrong sequence.

Resource Output

Three resources containing Students’ Discipline Data were published:

  • Discipline Incidents

  • Student Discipline Incident Behavior Associations

  • Discipline Action

Data Element

Description

[Table]FieldName

Data Type

disciplineIncidents

This resource contains basic elements of the Incident that occurred during the School Year.

incidentIdentifier

ID associated with the Incident Record.

[Incident]Incident_ID

Integer

schoolId

The education organization where the student is enrolled in.

[Incident]Incident_School_Number

Integer

incidentDate

The date on which the Incident occured.

[Incident]Incident_Date

Date

ReporterName

The reporter of the Incident is associated to the Incident Record with participant type as Reporter.

[Incident]Incident.Participant

Varchar

staffUniqueID

State Unique ID of the staff who created the Incident Record.

[S_AZ_USR_X}State_UniqueID present in [Incident]Created_By

Integer

studentDisciplineIncidentBehaviorAssociations

This resource contains elements of the behavior associated with the Incident that occurred during the school year for the student.

studentUniqueId

The student associated with the incident.

[Students]State_StudentNumber

String

incidentIdentifier

ID associated with the Incident Record.

[Incident]Incident_ID

Integer

schoolId

The education organization where the student is enrolled in.

[Incident]Incident_School_Number

Integer

behaviorDescriptorId

Behavior code must be mapped to the Behavior Descriptor under Code Set Mappings.

Behavior Code associated to the student.

See the Appendix for valid values.

[Incident_Action]Action_Incident_Detail_ID

[Incident_Detail]LU_Code_ID – Associates an action code to the incident.

[Incident_LU_Code]Code_Type=actioncode

[Incident_Person_Action]Incident_Person_Detail_ID – Associates an action code to a behavior and a participant.

String

disciplineActions

This resource contains elements of the action associated with the incident that occurred during the school year for the student.

disciplineActionIdentifier

Action ID associated to the student

[Incident_Action]INCIDENT.ACTION

String

studentUniqueId

The student associated with the incident.

[Students]State_StudentNumber

String

disciplineDate

The date associated with the Discipline Action record.

[Incident_Action]Action_Begin_Date

Date

responsibilitySchoolId

Education Organization ID of the Responsible School of the student

Comes from the Student Education Organization Association Record published for the student against the discipline date.

Integer

ActualdisciplineActionLength

Number of assigned days associated with the Action record.

[Incident_Action]Actual_Assigned_Duration if left blank then

[Incident_Action]Action_Assigned_Duration

Integer

disciplineDescriptor

Action code must be mapped to the Discipline Descriptor under Code Set Mappings.

Action Code associated with the students' action.

See the Appendix for valid values,

[Incident_Action]Action_Incident_Detail_ID

[Incident_Detail]LU_Code_ID – Associates an action code to the incident.

[Incident_LU_Code]Code_Type=actioncode

[Incident_Person_Action]Incident_Person_Detail_ID – Associates an action code to a behavior and a participant.

String

schoolId

The education organization where the student is enrolled in.

[Incident]Incident_School_Number

Integer

incidentIdentifier

ID associated with the Incident Record.

[Incident]Incident_ID

Integer

behaviorDescriptor

Behavior code must be mapped to the Behavior Descriptor under Code Set Mappings.

Behavior Code associated to the student.

See the Appendix for valid values.

[Incident_Action]Action_Incident_Detail_ID

[Incident_Detail]LU_Code_ID – Associates an action code to the incident.

[Incident_LU_Code]Code_Type=actioncode

[Incident_Person_Action]Incident_Person_Detail_ID – Associates an action code to a behavior and a participant.

String

DisciplineEndDate

The end date associated with the Discipline Record.

[Incident_Action]Action_End_Date

Date

ParentDeclinedServices

Whether parent has declined SPED Services per IEP while under disciplinary action.

[Incident_Action_Attribute]

Bit

ServicesProvided

Whether SPED Services per IEP were provided while under disciplinary action.

[Incident_Action_Attribute]

Bit

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.