1. SPED Integrity Rules Resources
Revised Resources to Troubleshoot Integrity Errors
Chris Brown – Director of Operations

2. Revisions in FY18 (Announcement sent April 5th to the field)
NEW Integrity Tools & SPED Integrity Error Messages Revised
Announcement Outline:
SPED Integrity Error Messages have been revised
SPED Integrity Rules Reference Tool has been revised
New SPED Integrity Tools available

3. SPED Integrity Error Messages
SPED integrity error message language has been updated in an effort to clarify the particular failure. Additionally, SPED Participation, SPED Program, or SPED Service is now referred to as Least Restrictive Environment (LRE). Example: Integrity Error Message for Old Message Invalid Need Code for this Service Code New Message Invalid need code for this Least Restrictive Environment (LRE) code I; refer to the Concurrent Need and Least Restrictive Environment (LRE) Code Eligibility matrix.

4. SPED Integrity Rules Reference
A reference sheet for all SPED integrity rules is available on the ESS Data Management website: This reference sheet provides the Error Code, Description of the Error, Error Message, State or FED SPED indicator, and Additional Notes. In the case of from the previous slide, the reference tool notes provides a link to the Concurrent Need and LRE Code Eligibility matrix. This matrix is also available on the ESS Data Management website.

5. New SPED Integrity Tools
Feedback received during AzEDS training sessions in the field indicated the need for slides that could visualize the process of a particular Integrity Rule. Visualizations could be presented to give the field an overall sense of how integrity rules pull particular elements in AzEDS to validate submissions. This helps with the overall understanding of the AzEDS process regarding special education integrity.

6. Example Rule:
Error Message: Student participating in special education must have one Federal Primary Need Indicator (FPNI).
SPED
Need
Entry and Exit dates
Primary or Secondary
LRE
-40050
During the time of the reported LRE, is one of the Needs reported as Federal Primary Need?
Now we are going to go over some examples of integrity errors in detail, and how they function
There are over 30 FED/SPED integrity errors, we are only going to review 5, then discuss more at the end
The process for troubleshooting errors can be similar. You can read each message in the INTEG15 report and look for key words.
We are in the process of updating these messages to use the terminology Least Restrictive Environment (LRE).
In this example we’ll look at Your INTEG15 report would read: There is more than one program/service specified at a single point in time for this need.
40044 will look at the reported dates for a SPED Need and compare them to the reported dates for the LRE. If there is more than one LRE reported for a single day or more, you will receive error
You can troubleshoot this error by verifying your entry and exit dates are correct for the needs and LREs.
Once you have corrected the dates and sent to AzEDS, allow for Integrity to run overnight, then check your SPED72 report to see if the student is now passing.

7. Example Rule: -40050 Troubleshooting Process:
Verify Need and LRE Entry and Exit Dates.
Verify Need FPNI (Federal Primary Need Indicator)
CONSULT THE STUDENT’S IEP TO DETERMINE THE FPNI. FPNI is not determined by funding or order of entry.
Once corrected, allow integrity to run overnight to see if student is passing integrity on SPED72 report.
Now we are going to go over some examples of integrity errors in detail, and how they function
There are over 30 FED/SPED integrity errors, we are only going to review 5, then discuss more at the end
The process for troubleshooting errors can be similar. You can read each message in the INTEG15 report and look for key words.
We are in the process of updating these messages to use the terminology Least Restrictive Environment (LRE).
In this example we’ll look at Your INTEG15 report would read: There is more than one program/service specified at a single point in time for this need.
40044 will look at the reported dates for a SPED Need and compare them to the reported dates for the LRE. If there is more than one LRE reported for a single day or more, you will receive error
You can troubleshoot this error by verifying your entry and exit dates are correct for the needs and LREs.
Once you have corrected the dates and sent to AzEDS, allow for Integrity to run overnight, then check your SPED72 report to see if the student is now passing.

8. SPED Integrity Tools
The ESS Data Management team developed visualizations and troubleshooting tips for most integrity rules. Available as a one-page PDF for each rule, these one-sheet tools are meant to assist when frequent questions arise about a particular integrity error. The Data Management team will maintain these documents as a living file, updated through time with interactions with the field.

9. SPED Integrity Tools
One-sheet tool provides the basic information from the reference tool, plus visualization of the error and troubleshooting tips.

10. Example Rule: -40027 SPED LRE Need
Error Message: Invalid need code for this Least Restrictive Environment (LRE) code I; refer to the Concurrent Need and Least Restrictive Environment (LRE) Code Eligibility matrix.
SPED
LRE
Need
-40027
When the LRE is I, do the student’s needs include at least one of the following: MD, A, SID, OI?
40067 compares the Primary and Secondary LRE sites for a student.
This integrity error will pull the entry and exit dates from the Secondary LRE and ensure that those dates fall within the reported dates of a Primary LRE
If you receive error you can troubleshoot by verifying the entry and exit dates on both the Primary and Secondary sites are entered correctly, and are correctly being sent into AzEDS by using the SPED10 report.
Verify in your SIS and the SPED10 report that one site is marked as Primary during any SPED LRE.
Once you have corrected the dates and sent to AzEDS, allow for Integrity to run overnight, then check your SPED72 report to see if the student is now passing.

11. Example Rule: -40027 Troubleshooting Process:
Verify correct LRE and Needs are reported. The student can have any other reported needs, but must include at least one of MD, A, SID, or OI to be reported with LRE I.
Check the Concurrent Need and Least Restrictive Environment (LRE) Code Eligibility matrix:
Once corrected, allow integrity to run overnight to see if student is passing integrity on SPED72 report.
40067 compares the Primary and Secondary LRE sites for a student.
This integrity error will pull the entry and exit dates from the Secondary LRE and ensure that those dates fall within the reported dates of a Primary LRE
If you receive error you can troubleshoot by verifying the entry and exit dates on both the Primary and Secondary sites are entered correctly, and are correctly being sent into AzEDS by using the SPED10 report.
Verify in your SIS and the SPED10 report that one site is marked as Primary during any SPED LRE.
Once you have corrected the dates and sent to AzEDS, allow for Integrity to run overnight, then check your SPED72 report to see if the student is now passing.

12. SPED Integrity Tools
One-sheet tool provides the basic information from the reference tool, plus visualization of the error and troubleshooting tips.

13. SPED Integrity Tools
When responding to a question about a particular error, the Data Management team can attach one of these tools to assist understanding of the error if needed, particularly when assisting users new to the AzEDS process. All of the one-sheet tools are available on the ESS Data Management website:

14. ESS Data Management Info
ESS Data Management Inbox:
Main Phone:
(602)
Subscribe to the ESS Data Management Listserv:
Peggy Staples Lead Data Management Specialist Maria Durazo Data Management Specialist Judy Olaiz Data Management Coordinator Eric Ashenfelter Business and Program Liaison Chris Brown Director of Operations
Here is our contact information.
Please questions to our group inbox, it is the fastest way to receive a response.
Also, if you haven’t already, here is the link to subscribe to the ESS Data Management listserv.
We send out alerts on data related changes, issues with AzEDS and our applications, reminders, training opportunities, etc. Make sure to select your entity type, we will only send you alerts that applicable to your entity.