SIRAS Built-in Validation System
SIRAS built-in validations identify missing required information, invalid combinations, compliance concerns, and other data-quality conditions before or during normal SIRAS work.
This article covers messages generated by SIRAS. When CALPADS rejects a submitted transaction and returns an IVR to SIRAS, use CALPADS IVR Errors Posted in SIRAS.
Correcting a SIRAS validation before submission can prevent a later CALPADS IVR, but not every SIRAS warning is a CALPADS reporting error.
Screenshots from the SIRAS Training Server contain fake or demonstration student and user information.
Which Article Do I Need?
| SIRAS Built-in Validation SystemSIRAS displayed the message before submission. | CALPADS IVR Errors Posted in SIRASCALPADS rejected a transaction and the error now appears in SIRAS. |
| CALPADS Error SummaryLook up the meaning and first checks for a CALPADS code or message. | Process for Error ResolutionUse the governing investigation and correction process. |
| CALPADS Submission Log HelpA transaction appears missing or rejected, but no error is posted in SIRAS. | Reporting Data to CALPADSReview the complete generate, send, import-error, and resend cycle. |
Contents
| When SIRAS Validates a Record | Where Errors and Warnings Appear |
| Errors, Warnings, and Colorization | Meeting Workflow Guidance |
| How to Respond | When to Use Another Article |
When SIRAS Validates a Record
Each student record is checked for errors and warnings:
- each time the student is selected;
- when a user clicks Validate on the MIS Summary;
- when a meeting with updated data is finalized; and
- at other workflow points where SIRAS must determine whether required data or conditions are present.
Many validation rules reflect CALPADS requirements, but SIRAS also uses validations to guide local workflow, meeting compliance, and completion of required forms.
Where Errors and Warnings Appear
Choose Student list
The E and W columns show counts for errors and warnings. A red count indicates an error; a yellow count or icon indicates a warning.
Predefined Validation Errors and Warnings list
Use the predefined Data Monitoring list to find records with one or more SIRAS validation errors or warnings.
Student Lists
Student Lists can display the Validation Errors and Validation Warnings columns so staff can review the actual messages across a found set.
Validations also appear on the MIS Summary after clicking Validate and within the applicable meeting workflow.
Errors, Warnings, and Colorization
| Display | Meaning | Expected response |
|---|---|---|
| Red required field | Required information is missing. | Enter the accurate value before completing the applicable workflow or reporting transaction. |
| Red error message | A value or combination is invalid, such as a program setting that is not valid for the student's grade or plan. | Review the complete message and correct the underlying data. |
| Yellow warning | SIRAS identified a concern requiring review, such as an overdue IEP date or a potentially incomplete workflow. | Determine whether action is needed. A warning may be accurate and still require documentation or follow-up. |
| Required versus optional form colorization | The meeting workflow identifies forms or fields expected for the meeting type. | Complete the required items and review optional items that apply to the student. |
A missing or invalid value may prevent SIRAS from evaluating a later rule. Validate again after correcting required information.
Meeting Workflow Guidance
Preventing an inappropriate second Initial Evaluation
SIRAS can prevent creation of a secondary Initial Evaluation when the student already has an Initial Evaluation Date.
Required and optional meeting forms
Meeting forms are color coded to guide completion. Required items appear in red and optional items appear in yellow.
Meeting-specific required dates and follow-up
SIRAS highlights meeting-specific requirements. In the example below, Assessment Plan Sent and Assessment Plan Received are required for the Triennial/Reevaluation workflow, and a warning identifies goals requiring final progress review.
How to Respond
- Read the complete SIRAS message.
- Identify the field, form, date, status, or combination being evaluated.
- Confirm what actually occurred before changing the record.
- Correct the underlying data or complete the required workflow.
- Validate the record again.
- When a warning remains, determine whether it describes an accurate condition that requires follow-up rather than a data correction.
When the message does not match the verified field event, review the related record history or contact SIRAS Support.
When to Use Another Article
- CALPADS returned an IVR to SIRAS: use CALPADS IVR Errors Posted in SIRAS.
- You need the meaning of a CALPADS code: use CALPADS Error Summary.
- You need the investigation method: use Process for Error Resolution.
- A transaction appears missing without a posted error: use CALPADS Submission Log Help.
