WI DPI WISEdata Ed-Fi Docs
Use Cases for the 2022-23 SY
Jaidaa Shafaei
Informational: IB Schools (/schools) - Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Retrieving the 2022-23 School data (School ID, School Name, Grade Level, IB Indicator, etc.) from the WISEdata API | SIS vendors should be able to (not required to) do a GET on /schools and ingest the school details into their system.
| GET on /schools |
Tribal Affiliation, Non-binary Gender, and SATA (/studentEducationOrganizationAssociations) - All LEAs
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Sending the student's Tribal Affiliation |
| POST on /StudentEducationOrganizationAssociations: OR |
2.0 | Sending the Gender for a transgender or non-binary student | Starting in the 2022-23 school year, Non-Binary (X) will be added as a gender option.
| POST on /studentEducationOrganizationAssociations |
3.0 | Sending student Characteristics: State Assessment Type-Alternate (SATA) | LEAs are no longer required to submit SATA as a student characteristic.
| Should not submit SATA as a studentCharacteristicDescriptor on /studentEducationOrganizationAssociations. |
Exit Type Changes (/studentSchoolAssociations) - All LEAs
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Updating the ExitWithdrawTypeDescriptor code values | Simply updating the ExitWithdrawTypeDescriptor code values on the existing /studentSchoolAssociation endpoint.
| POST on /studentSchoolAssociations: |
Language Instruction Services (/studentLanguageInstructionProgramAssociation & /section) - Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Sending Language Instruction Services for English Learners | The codes values and definitions for the LanguageInstructionProgramServiceDescriptor have been changed for the 2022-23 SY. (See descriptor details above: /studentLanguageInstructionProgramAssociation (Public LEA Only) | Descriptors & Programs: ) | POST on /studentLanguageInstructionProgramAssociation: |
2.0 | Sending Language Instruction Services as ‘OTHER’ | When school districts select ‘OTHER’ as a language instruction educational program, the program must be described for review and approval as outlined in the Title III-A English Learners section of the ESSA LEA Plan (through the WISEgrants Application).
| POST on /studentLanguageInstructionProgramAssociation: |
3.0 | Sending the Language of Instruction on the class level as par tof Roster data. | LEAs should send the primary “predominant” language of Instruction (not the language of learner).
This data set will allow DPI teams to correlate student academic performance data with education program model and academic subjects taught in English versus languages other than English (LOTE). It will also help DPI identify cohorts of educators for professional learning and growth related to this work. | POST on /section: |
4.0 | Sending language program services for a student who is proficient in English but still receiving language program services | If the student is receiving language instruction services beyond the second year of monitoring, such as a Bilingual/ESL program, LEA may choose (not required) to submit that data as a regular student program association /studentProgramAssociation (SPA).
| POST on /studentEducationOrganizationAssociation: limitedEnglishProficiencyDescriptor: uri://dpi.wi.gov/LimitedEnglishProficiencyDescriptor#6 POST on /studentProgramAssociation: programTypeDescriptor: uri://dpi.wi.gov/ProgramTypeDescriptor#LIEP-ESL |
5.0 | Sending a student who a native English speaker sitting in bilingual language program class | In some exceptional cases, students could be native English speaker and receiving language program services. In such cases, LEAs do not submit /SLIPA and instead may choose (not required) to submit /SPA.
| POST on /studentEducationOrganizationAssociation: limitedEnglishProficiencyDescriptor: uri://dpi.wi.gov/LimitedEnglishProficiencyDescriptor#7 POST on /studentProgramAssociation: programTypeDescriptor: uri://dpi.wi.gov/ProgramTypeDescriptor#LIEP-Bilingual |
Timely Initial Evaluations (/studentSpecialEducationProgramEligibilityAssociations & /studentEducationOrganizationResponsibilityAssociation ) - Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Sending a school-aged (3-21) student whose evaluation process is completed within in 60 days with no exception. | When parents provide consent for evaluation and the evaluation is completed within the 60-day timeframe, then the that LEA completed the evaluation submits /studentSpecialEducationProgramEligibilityAssociation (SSEPEA)
When the LEA receives a referral to evaluate the student and determine their eligibility for special education services, then the LEA must do the following within 15 business days:
The 60 calendar day timeline begins either:
| POST on /studentSpecialEducationProgramEligibilityAssociation |
1.1 | Sending a student who is IDEA eligible Completed within 60 days | When the evaluation is completed and the IDEA eligibility indicator is ‘True’, then the LEA completed the evaluation submits a /studentSchoolAssociation (SSA) record and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record | POST on /studentSpecialEducationProgramEligibilityAssociation: |
1.2 | Sending a student who is not IDEA eligible Completed within 60 days | When the evaluation is completed and the IDEA eligibility indicator is ‘False’, then the Resident LEA (FAPE district) submits a /studentSchoolAssociation (SSA) record and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record | POST on /studentSchoolAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation |
2.0 | Sending a school-aged student whose evaluation was completed beyond the 60-day timeline | When parents provide consent for evaluation and the evaluation was completed past the 60-day timeframe, then the LEA completed the evaluation submits /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) and provide a valid Evaluation Delay Reason to the 60-day timeframe that applied or provide at least one Late Reason.
Prereq:
| POST on /studentSpecialEducationProgramEligibilityAssociation: |
2.1 | Sending a student who is IDEA eligible Completed after 60 days | When the evaluation is completed and the IDEA eligibility indicator is ‘True’, then the LEA completed the evaluation submits a /studentSchoolAssociation (SSA) record and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record | POST on /studentSchoolAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation: |
2.2 | Sending a student who is not IDEA eligible Completed after 60 days | When the evaluation is completed and the IDEA eligibility indicator is ‘False’, then the LEA completed the evaluation submits a a /studentSchoolAssociation (SSA) record and a /studentSpecialEducationProgramEligibilityAssociation (SEPEA) record. | POST on /studentSpecialEducationProgramEligibilityAssociation: |
3.0 | Sending a school-aged student whose evaluation is completed, but the student is homeschooled and not enrolled at the LEA. | When parents provide consent for evaluation and the evaluation is completed for homeschooled student, then the district where the homeschooled student resides submits a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. Prereq: In this case, a student enrollment records (SSA) doesn’t exist; therefore, the LEA needs to create a student WISEid and submit /studentEducationOrganizationResponsibilityAssociation (SEORA) in order to be authorized to post /SSEPEA.
| POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation |
3.1 | Sending a student who is IDEA eligible | When the evaluation is completed and the IDEA eligibility is True’, then the LEA completed the evaluation needs to create a student WISEid then submits a /studentEducationOrganizationResponsibilityAssociation (SEORA) record and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation: |
3.2 | Sending a student who is not IDEA eligible | When the evaluation is completed and the IDEA eligibility indicator is ‘False’, then the LEA completed the evaluation needs to create a student WISEid then submits a /studentEducationOrganizationResponsibilityAssociation (SEORA) and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation: |
4.0 | Sending a school-aged student whose evaluation is completed, but the student enrolled in a private school (not the LEA who completed the evaluation) | When parents provide consent for evaluation and the student is enrolled in a private school, then the district where the private student resides submits a /studentSpecialEducationProgramEligibilityAssociation (SEPEA) record. NOTE: if the private school that is located outside of the resident district, then the district in which the private school is located will complete the evaluation and would complete the Indicator 11 reporting. Prereq: In this case, a student enrollment records (SSA) doesn’t exist; therefore, the LEA needs to create a student WISEid and submit /studentEducationOrganizationResponsibilityAssociation (SEORA) in order to be authorized to post /SEPEA. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation |
4.1 | Sending a student who is IDEA eligible | When the evaluation is completed and the IDEA eligibility indicator is ‘True’, then the LEA completed the evaluation needs to create a student WISEid then submits a /studentEducationOrganizationResponsibilityAssociation (SEORA) record and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation: |
4.2 | Sending a student who is not IDEA eligible | When the evaluation is completed and the IDEA eligibility indicator is ‘False’, then the LEA completed the evaluation needs to create a student WISEid then submits a /studentEducationOrganizationResponsibilityAssociation (SEORA) and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation: |
5.0 | Sending a student whose evaluation was completed in an MPS school (e.g. Riverside Hi), but is enrolled in either Carmen or MCP schools (e.g. Carmen Mid/Hi Northwest Campus or Milw College Prep--Lloyd St) This use case is only for vendors who support Milwaukee Public Schools (MPS). | Carmen Schools of Science and Technology and Milwaukee College Prep (MCP) are Charter Schools authorized by Milwaukee Public Schools (MPS). For more information, visit Currently Operating Charter Schools The student’s initial evaluation is generally completed by the resident school district, which is in this case the MPS school. Therefore, the MPS school submits a /studentEducationOrganizationResponsibilityAssociation (SEORA) record and a/studentSpecialEducationProgramEligibilityAssociation (SEPEA) record. NOTE: The Carmen or the MCP school, where the student is enrolled, is responsible for submitting the school enrollment record (SSA) along with other data element to WISedata Portal. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation |
6.0 | Sending a student below compulsory school attendance age (0-3) whose evaluation is completed for under three years of age program | Data for children below the compulsory school attendance age is not collected in WISEdata. This means SSA cannot be submitted for these students. Therefore, When parents provide consent and the evaluation is completed , then the LEA is required to create a student WISEid and submit a /studentEducationOrganizationResponsibilityAssociation (SEORA) and a /studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. | POST on /studentEducationOrganizationResponsibilityAssociation AND POST on /studentSpecialEducationProgramEligibilityAssociation |
7.0 | Sending a student below compulsory school attendance age whose evaluation is completed by county school for under three years of age program | When a county schools evaluates the student, then it is not required to submit a /studentSpecialEducationProgramEligibilityAssociation (SEPEA) record to WISEdata. | Nothing to POST |
8.0 | Sending a school-aged student who is enrolled in an LEA that picked up an evaluation that another LEA completed for transfer students | When a student transfers from LEA A, who completed the evaluation, to another LEA B, then:
Prereq:
| LEA B POST on /studentSchoolAssociation AND LEA A POST on /studentSpecialEducationProgramEligibilityAssociation |
9.0 | Sending a school-aged student whose evaluation process was not completed in LEA A, then the student moved to LEA B to continue the evaluation. The student is enrolled in LEA B. |
Prereq:
| LEA B POST on /studentSchoolAssociation AND /studentSpecialEducationProgramEligibilityAssociation |
10.0 | Sending a school-aged student whose evaluation process was not completed, and the parent stops the evaluation (revoked consent or transferred to another LEA) |
| LEA receives parental consent for evaluation: POST on /studentSpecialEducationProgramEligibilityAssociation If the student is not enrolled in the LEA, then POST on /studentEducationOrganizationResponsibilityAssociation Parent stops the evaluation: DELETE on /studentSpecialEducationProgramEligibilityAssociation |
11.0 | Sending the initial evaluation for a student whose consent is received is in the 22-23 SY, but the eligibility is determined for the 23-24 SY | The reporting year is based on when the 60 calendar day timeline begins (July 1, YY through June 30, YY+1). It may include children for whom consent to conduct the evaluation was received during the summer months. In this case, the child would be included in the 2022-23 SY data as the consent to evaluate was received during that school year. | POST on /studentSpecialEducationProgramEligibilityAssociation If the student is not enrolled in the LEA, then POST on /studentEducationOrganizationResponsibilityAssociation |
12.0 | Sending the initial evaluation for a student whose consent is received is in the 22-23 SY, but the eligibility is not determined before either Nov 2023 or Feb 2024 | Data for Indicator 11 needs to be included in the Annual Performance Report (APR) that is due on February 1 of each year. The data included in the APR is for the prior reporting year (example, Indicator 11 reported on Feb, 2023 for the 22-23 SY). Therefore, LEA must submit data to WISEdata by November 15. In this case, LEA will submit the studentSpecialEducationProgramEligibilityAssociation (SSEPEA) within 60 days of receiving parental consent for evaluation as not determined.
| POST on /studentSpecialEducationProgramEligibilityAssociation: |
13.0 | Sending the initial evaluation for a student who is open enrolled-out in a non-resident district | The non-resident district (the attending district where the student is enrolled) completes the evaluation and submits the studentSpecialEducationProgramEligibilityAssociation (SSEPEA) record. | POST on /studentSpecialEducationProgramEligibilityAssociation |
14.0 | Sending the initial evaluation for a student whose Last Evaluation date on /SSEPA is the same as the initial evaluation | It is possible that the Last Evaluation Date on studentSpecialEducationProgramAssociation (SSEPA) is the same date as the Eligibility Determination Dated on studentSpecialEducationProgramEligibilityAssociation (SSEPEA). | POST on /studentSpecialEducationProgramEligibilityAssociation |
15.0 | Sending multiple eligibility in the same school year and same LEA | If a student is found ineligible the first time, then the LEA may send a second evaluation. However, there can’t be an overlap in the initial evaluation process from the same LEA
| POST on /studentSpecialEducationProgramEligibilityAssociation |
16.0 | Sending multiple eligibility in the same school year but different LEAs | A parently-placed private student can have evaluations done in two district: the resident district and the district where the private school is located. These SSEPEA records could overlap. | POST on /studentSpecialEducationProgramEligibilityAssociation |
17.0 | Deleting the eligibility records for a student |
SIS vendors should handle deleting child records before deleting the enrollment record (studentSchoolAssociation). | DELETE on /studentEducationOrganizationResponsibilityAssociation DELETE on /studentSchoolAssociation |
Change in the DisabilityDescriptor (studentSpecialEducationProgramAssociation)- Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Sending ‘Deaf and Hard of Hearing' as a primary disability | The description for Deaf and Hard of Hearing has been modified (replace the ‘or’ with ‘and’). The code value will remain unchanged 'H'.
| POST on /studentSpecialEducationProgramAssociation: |
Food Service Eligibility (studentSchoolFoodServicesProgramAssociation) - All LEAs
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Sending ‘Unknown' as a Food Services Eligibility | The value “Unknown” must to be available as an option in the SIS, and reported to WISEdata when selected by the user. For schools not participating in the Community Eligibility Provision (CEP), National School Lunch Program (NSLP), or Seamless Summer Option (SSO) and using the alternate household income form for WISEdata reporting, they should report a student identified as economically disadvantaged on this form as “True” and “Unknown” for Food Service Eligibility.
| POST on /studentSchoolFoodServiceProgramAssociation: |
Student Learning Modality (/studentProgramAssociation) - Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Sending the Learning Modality for how students are participating in instruction (school level) | Public schools will submit the school level indicator via WISEgrants in which they can indicate which learning modalities the school is offering and if that modality is: Offered to all students, Offered to some students, Offered to no students. | NA - Informational only |
2.0 | Sending the Learning Modality for how each student is participating in instruction (student level) | Public schools should submit a studentProgramAssociation record detailing what modality each student is in (e.g. In-person or Remote). When a Learning Modality program type is not present for a student in WISEdata, then it is assumed that the student is in the default modality for the school.
| POST on /studentProgramAssociation: programReference: |
3.0 | Sending the student learning modality when modality of an individual student changes, and the student is attending a non-virtual school. | When a student attending a non-virtual school has a long-term modality shift in their learning modality, e.g. FROM ‘in-person’ TO ‘hybrid’ or ‘remote’, then a new student program record needs to be submitted and the previous student program record needs to be ended.
| POST on /studentProgramAssociation: programReference: POST on /studentProgramAssociation: programReference: |
4.0 | Sending the student learning modality when modality of an individual student changes, and the student is attending a virtual school. | When a student has a long-term modality shift FROM attending remote in a virtual school TO an in-person in a non-virtual school, then the student's enrollment in the virtual school should be ended, and and a new enrollment should be created for a non-virtual school. In this scenario, no student program record detailing modality would be expected as the modality default would apply based on the type of school. | /studentProgramAssociation with learning modality is not expected. LEA is expected to end the existing /studentSchoolAssociation and send a new one from the new school. |
Transition from SCED 8.0 to SCED 9.0 (/courses ) - Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Retrieving the 2022-23 course data (SCED 9.0) from the WISEdata API | SIS vendors should be able to do a GET on /courses and ingest the course details into their system
| GET on /Courses |
World Language Education - Public Only
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|---|---|---|
1.0 | Submit world language coursework for 6-12 grade levels | DPI has been performing data quality checks for grade levels 9 to 12. DPI is expanding this effort to 6 -12 grade levels along with the submission of world language coursework data. The change in the 2022-23 SY is that schools, who have not been sending roster data, need to send data for 6 - 8 grade levels as well as world language data for 6 -12 grade levels. | Submit Roster endpoints to grade levels 6-12 |
2.0 | Sending a student who participates in a WL program that has been changed in the 2022-23 SY | LEAs are required to send WL program type on /studentsectionAssociation
For more details, see https://wisconsindpi.atlassian.net/wiki/pages/createpage.action?spaceKey=widpiedfi&title=World%20Language%20Education%20%28keep%29&linkCreation=true&fromPageId=4456492 . For the World Language Program Definitions, visit Programs
| POST on /studentSectionAssociaton: programs:
|
3.0 | Sending a student who participates in a WL program that is new in 2022-23SY | LEAs are required to send WL program type on /studentsectionAssociation New WL programs are:
For more details, see https://wisconsindpi.atlassian.net/wiki/pages/createpage.action?spaceKey=widpiedfi&title=World%20Language%20Education%20%28keep%29&linkCreation=true&fromPageId=4456492 For the World Language Program Definitions, visit Programs | POST on /studentSectionAssociaton: programs:
|
Pupil Count Report for Membership - Public Only
SIS Requirements for the Choice Audit - Choice Only
SIS vendors must have the following reports and functionality in their SIS to assist auditors that perform the September and January Enrollment Audits:
(For additional details, visit the Private School Choice Programs-September Enrollment Audit page).
1. User and Role Access Report:
SIS should provide details of the function and data security privileges granted to specified users or roles. The report must identify each user and their role, and include who has administrator rights. The individual with administrator rights is the only individual who should be able to add new authorized users.
All teachers and staff must have a separate username and password.
The teachers cannot have access to add pupil names.
2. Official Attendance Records:
SIS should provide a listing of all kindergarten through grade 12 pupils enrolled in the school by grade level that identifies the attendance for each pupil. The official attendance records should have the attendance for every day of the school year. As part of the September and January Enrollment Audits, the school will need to provide the official attendance records for the count date (3rd Friday in September and 2nd Friday in January) or any day before and after the count date. The official attendance records must have an identifier of who is a Choice student or the school must have a separate Choice Identifier Report. See below for information on the Choice Identifier Report requirements.
3. Choice Identifier Report:
If the official attendance records do not include the Choice identifier, the school must have a Choice Identifier Report from the SIS. The Choice Identifier Report should provide a list of pupil names and their Choice program participant indicator on the count date (3rd Friday in September and 2nd Friday in January).
SIS must track changes to the Choice Program Participant indicator for students who are choice participants for only part of the year (the choice identifier should not be year-specific).
SIS must have the ability to track changes to the choice identifier locally in the SIS, but only send the most recent Choice Program Participant indicator to WISEdata Portal.
For more details, see the studentSchoolAssociation use cases: 4.0, 5.0, and 6.0.
4. SNSP Identifier Report (optional):
SIS should provide a list of pupil names, and their SNSP identifier if available in the SIS.
5. Original Classroom Records:
The school must have classroom grade books or other records maintained by teachers identifying daily attendance or absences, grades, or other indications of instruction such as progress reports. Some schools may want a report from the SIS that is an original classroom record. The original classroom record must be a different report than the official attendance records.
6. SIS Data Changes Report:
SIS should provide a list of changes made to SIS data. This list of changes should include the change made (including the student identifier such as the student name, id, etc., if applicable) and the SIS user that made the change. This list of changes should include changes to the attendance data. SIS vendors may choose to provide separate reports to show changes in student data and in attendance data.
7. Backup and Recovery:
SIS users must demonstrate their ability to backup and restore the school’s final data.
all student records and attendance must be retained for 6 years
3 years (the current year and the last 2 years) must be accessible for editing through the SIS.
SIS must perform secure automated backups (at least monthly) and easy restore options for their schools.
SIS users must demonstrate their ability to perform a manual backup and to restore the manual and/or automated backups. That test should be documented, even if it is just a screenshot showing the data restored.
Related content
Wisconsin Department of Public Instruction