Special Education Meetings (MEET)
(Updated 9/19/2023)
For authorized users, the Special Education Meetings history displays when a user clicks the container on the Student Details. The system will display a button next to each record to open the record in read-only. The UI is depicted below followed by its screen elements table. Following by user interaction section and the system operations section with the additional expected system functions, requirements, and possible processes. The system will display all records by default in reverse chronological order.
Account Roles Needed
Users need the following roles to access and edit this section of the Student Details page.
- Student Search
- SPED View: Provides functionality to only view MEET via Online Maintenance. Provides functionality to request and retrieve MEET Rejected Records Extracts and request and retrieve MEET ODS Extract.
- SPED Edit: Provides functionality to create and manage MEET records using the online and batch interface.
- School Level Users with SPED Edit will NOT be able to Add/Edit/Delete the MEET record(s) due to no School level field to allow authorization.
An authorized user may perform the following functions through this interface:
- View a student’s existing Special Education Meetings record.
- Select to edit or delete an existing record reported by the LEA the user is associated to.
- Add new Special Education Meetings record
- Return to the Student Detail page
Special Education Meetings Container
The Special Education Meetings Container (MEET) page displays when the user clicks to expand the container header within the student details. The system will display a button next to each record to open the record The UI is depicted below followed by its screen elements table. Following by user interaction section and the system operations section with the additional expected system functions, requirements and possible processes. The system will display all Student Special Education Program records by default in reverse chronological order.
Clicking on the Special Education Meetings header expands the container and reveals existing records.
Add New Record button enables user to create a new Special Education Meetings record.
Container column headers enable users to sort or filter existing records based on parameters set.
Open button enable users to view details of the record. The record details cannot be modified regardless if the LEA owns the record and the user has Edit roles.
Since the container only shows limited records at a time, the page buttons allow users to move to the next set of records.
Special Education Meetings Modal
The Special Education Meetings Details UI is depicted below followed by a screen elements table. If the user clicks to open an existing record, the modal page appears with the values from the student’s selected record.
| Screen Label | Required | Validation/Business Rule |
|---|---|---|
| Header Data | ||
| N/A | (Contents derived from most current SENR, SINF AND SELA data) | |
| MEET Data | ||
| Academic Year ID | N | 1) Academic Year ID must be a valid academic school year combination and no more than one year in the future 2) Academic Year ID must be the academic school year associated with the Special Education Meeting Date or Pending Date |
| SSID | Y | 1) SSID must be a valid CALPADS SSID in the ODS 2) Only one record may exist in the file with the same SSID and Reporting LEA, and Special Education Meeting Date, Pending As of Date |
| Local Record ID | N | N/A |
| Local Student ID | N | N/A |
| Local Special Education Student ID | Y | N/A |
| Reporting LEA | Y | 1) Reporting LEA must equal institution identifier of submitter User ID 2) If Charter School is an independently reporting Charter School for SPED reporting, then Reporting LEA and School of Attendance must reflect the same Charter School |
| Reporting SELPA | Y | 1) SELPA code must be a valid 4-digit SELPA code 2) SELPA must be a valid Entity Code and have an active reporting relationship with the Reporting LEA |
| Special Education Referral Date | If Meeting Activity - Evaluation Type Code = 10 (Initial Part B) or 15 (Initial Part C) Then Y; Else N |
1) Special Education Referral Date must a future date 2) Special Education Referral Date must be greater than or equal to Student Birth Date 3) Special Education Referral Date must be less than or equal to the Initial Evaluation Parental Consent Date |
| Referring Party Code | If Special Education Referral Date is populated Then Y; Else N |
N/A |
| Initial Evaluation Parental Consent Date | If Meeting Activity - Evaluation Type Code = 10 (Initial Part B) or 15 (Initial Part C) Then Y; Else N |
1) Initial Evaluation Parental Consent Date must be greater than or equal to the Special Education Referral Date |
| Special Education Meeting Date | If Pending As of Date is null, Then Y; Otherwise must be blank/null |
1) Special Education Meeting Date must be greater than or equal to Initial Evaluation Parental Consent Date 2) Special Education Meeting Date must less than or equal to current date 3) Must not be populated if Pending As of Date is populated |
| Pending As Of Date | If Special Education Meeting is null, Then Y; Otherwise must be blank/null |
1) Must not be populated if Special education meeting date is populated |
| Meeting Delay Code | If Meeting Activity - Evaluation Type Code = 10 (Initial Part B) or 15 (Initial Part C) and Special Education Meeting Date is greater than 60 days from the Initial Evaluation Parental Consent Date Then Y, Else N |
1) Meeting Activity-Evaluation Type Code and Meeting Delay Code must be a valid combination as defined in the CALPADS Valid Code Combinations document 2) Meeting Delay Code must be null or equal to 30, 50, 60, 70, 75, 80, or 90 when Meeting Activity - Plan Review Indicator = Y and Meeting Activity - Evaluation Type Code is null or blank |
| Meeting Activity - Evaluation Type Code | If Meeting Activity-Plan Review Indicator is blank Then Y, Else N |
1) Meeting Activity - Evaluation Type Code and Evaluation Outcome Code must be a valid combination as defined in the CALPADS Valid Code Combinations document 2) Meeting Activity-Evaluation Type Code and Meeting Delay Code must be a valid combination as defined in the CALPADS Valid Code Combinations document If no evaluation occurred during a meeting, this field should be left blank. |
| Meeting Activity - Plan Review Indicator | If Meeting Activity-Evaluation Type Code is blank, then Y, Else N |
This field should only be populated with a "Y" if the meeting would satisfy the statutory requirements for the required review of a student's established special education plan at least once annually. |
| Evaluation Outcome Code | If Special Education Meeting Date is populated and Meeting Activity - Evaluation Type Code is populated, Then Y, Otherwise must be Blank/Null |
Evaluation Type Code and Evaluation Outcome Code must be a valid combination as defined in the CALPADS Valid Code Combinations document |
| Parental Involvement Facilitation Code | If Meeting Activity-Plan Review Indicator = Y or Meeting Activity-Evaluation Type = 10 Then Y; Else N | This is collected during the annual Education Plan meetings. The collection method is up to the LEA's discretion (form or verbal). |
Additional Resources
CALPADS Special Education FAQ
This document list current Special Education- related frequently asked questions.
CALPADS Error List
This document contains descriptions for each error generated when submitting data to CALPADS. It also provides suggested resolutions.
CALPADS File SpecificationsForm
Look for Student Special Education Tab
CALPADS Code Sets
This document contains the current code values referenced in the file specifications for the coded value data elements. Appropriate SPED codes are included in this document.