Under /tools/data export

Select Data Set = Service Data

Labels vs Codes:  Service code 415 is Speech and Language. Code exports 415, Label exports Speech and Language.

 

When the Data Set is first selected as 'Service Data' , SIRAS automatically populates the export fields to include most of the mapped service fields.

You can add more student data to the export. See detailed screenshot at bottom of page.

 

Keep in mind: Since this is a service level export, if a student has 6 services, you will see the student data replicated 6 times for each unique service.

 

Consolidate Services:

 

If you don't want to see every version of SAI services and want them consolidated to unique services, use the 'Consolidate Services' checkbox, SIRAS will do a normalization calculation on the frequency and duration. If you are doing a service report, you may not want to use this option to see all details of each duplicated service. Ex. SAI math, SAI english, SAI history would all be combined if they were 'consolidated'

 

Consolidating + Filtering Start/End Dates:

 

The "Consolidate Services" function also performs some operations on the service data involving Start and End Dates.  Sometimes a student record will, as indicated on the IEP documents, include service data including both past and/or planned future services as well as currently effective services, and these distinct periods of different services will be indicated with Start and End dates.  While it is preferable to have a single set of services indicated for the year, it is sometimes considered necessary to have the changes indicated as occurring mid-year. 

 

To accommodate for this, the Service Export (with the consolidation function enabled) will analyze the start and end dates and filter out only the services that have Start/End date coinciding with the relevant date.  The relevant date is the Current date (date of export) for Current records, and for archived records it is the Plan Effective Date.  This ensures that the services that are reported to CALPADS are those that are effective as of the date that the plan goes into effect.  There is some additional logic included with the filtering function which accounts for data entry errors where no services start/end date ranges coincide.