Student Special Education Events

studentSpecialEducationAssociationEvents

This view captures student Special Education Program event data as published in the StudentSpecialEducationAssociationEvent resource within the Student Program category. The layout includes the Student’s Unique ID, School reference, Event Type Code, Event Date, Event Reason, Non-Compliance Reason, Last Publish Date, and Publishing ID.

Note: In order for a student’s Special Education event data to publish, they must have a published StudentSpecialEducationProgramAssociation record.

Primary PowerSchool Source Data

• [Students]

• [ReEnrollments]

• [S_NM_STU_X]

• [S_NM_STU_SPEDEVENTS_C]

Selection Criteria

Records are published if the following criteria are met:

• StudentUniqueId must be populated in PowerSchool.

• The student must not be excluded from state reporting.

• The school must not be excluded from state reporting.

• The student must be identified as a Special Education student.

  • [S_NM_STU_X]SpEd38_YN = Y (for a current special education student) or N (for a student that has exited special education).

  • The date range between the following fields must span some part of the reporting year.

    • [S_NM_STU_X]SpedEntryDate

    • [S_NM_STU_X]SpEdExitDate

• The Special Education Event Date is within 365 days of the first day of school.

Publish Special Education Event Record for Specific Scenarios

Functionality available to publish Special Education Event records for the following specific scenarios:

• Students that were evaluated for Special Ed but did not qualify for whatever reason (DNQ students).

• Students that exited Special Education prior to the current school year and therefore don’t have a parent Special Education record in the current year.

• Students are currently in Special Education, but PED is reporting a certain event is missing on their side that is outside of the normal PowerSchool publishing logic (Sped Event record took place more than 365 days from the start of the current school year).

For the scenarios outlined above, this functionality allows end users to select a year value, for a given Sped Event record (the year should reflect the school year in which the Sped Event record must publish), in the Force this record to publish? field. Once a year is selected, the next time a Publish All is done, a Special Education parent program record will be generated, and the Sped Event record (or records) will be published.

Note: Due to Special Education Events being dependent on a Special Education parent program record, if the student’s Special Ed data is unable to get a parent Sped record (students that exited Special Education in a previous school year or DNQ students), this functionality will generate a parent Sped program record to enable to the selected Sped Event to publish.

The generated Sped program record will have the following fields:

• beginDate

  • The event date of the event record that needs to be sent.

• programReference

  • Existing logic

• studentReference

  • Existing logic

• endDate

  • The event date of the event record that needs to be sent.

• specialEducationLevelOfIntegrationDescriptor

  • Required field in the ODS. A valid value will be published that will not be stored in the PowerSchool database.

• primaryAreaOfExceptionalityDescriptor

  • Required field in the ODS. A valid value will be published that will not be stored in the PowerSchool database.

• alternateInstruction

  • Required field in the ODS. A valid value will be published that will not be stored in the PowerSchool database.

Resource Output

• A separate record is published for each enrollment period the student was in Special Education.

• The StudentSpecialEducationProgramAssociation resource is dependent on the prior publishing of the following resources: Student and StudentSchoolAssocation.

• LEAs and Schools may upload (publish) data to the Ed-Fi ODS in real-time or on-demand ("Run Now" button).