You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > Support Center > Admin Procedures > Creating a New Student Record
Creating a New Student Record
print icon
Create a new SIRAS student record only after confirming an existing record cannot be transferred or obtained.
This article covers manual record creation and the historical-data fallback used when an already-eligible student's original referral/initial-entry dates cannot be obtained. For the broader arrival review, start with 289 — New or Returning Students.
SIRAS click path:
Student Info → + New Student
Do not create a duplicate record.
Before creating a student, determine whether a record with the same SSID already exists on your SIRAS server or another SIRAS server that can transfer the record. If you do not yet know whether the student has an SSID, complete that due diligence before continuing.

Before You Create a Record

  1. Know why the record is being created. Determine whether the student is a true new referral, an already-eligible incoming/returning student, an IFSP/Part C student, or another situation.
  2. Search for an existing record first. Use Request Student Transfer / the request-transfer process with the SSID when an existing SIRAS record may be available.
  3. If the student came from a different SIRAS server and the record cannot be obtained through the normal transfer workflow, contact [email protected] for assistance rather than creating a duplicate.
  4. Confirm the SSID. Do not knowingly create a second record for the same student.
  5. For a new or returning IEP-age student, complete the due-diligence review in New or Returning Students so you know what eligibility, participation, plan, enrollment, and historical information the new record must represent.
District SIS integration:
Check with your district office to determine whether your SIS integration/import process creates new SIRAS records automatically. If so, entering the correct information in the SIS may create the record through the next scheduled import rather than requiring manual creation.
Existing SIRAS screenshot retained from the prior New Student record instructions
Existing screenshot retained from the prior article for the new-record / SIS workflow.

Back to top

Create the Record

  1. Go to Student Info → + New Student.
  2. Complete the required fields. SIRAS highlights required fields in red.
  3. If your district uses Aeries integration and the Update by API option is available, use it to pull the available student information.
  4. Choose the student's status based on the actual situation. A true Initial Evaluation is normally Pending; an already-eligible and participating student may be Active. See SIRAS Record Status.
  5. At the top right of the New Student page, choose + Create Record, or Create and Add Another New Student when appropriate.
  6. If the student is already eligible, continue to the next section and fully reconstruct the MIS Summary before creating a Plan Adoption, assigning providers, or opening new meeting work.

Back to top

Student Is Already Eligible

When the student already has an existing U.S.-based special education eligibility, the goal is to represent the student's actual incoming history—not to create a new referral simply because the SIRAS record is new.

Do not treat a new SIRAS record as a new special education history.
The student may have years of valid eligibility, referral, evaluation, plan, and participation history that must be represented even though the receiving district is creating the SIRAS record today.

Back to top

If Historical Referral / Initial-Entry Dates Cannot Be Obtained

Use this fallback only after you establish that the student is already eligible and that the missing values are historical.
A prior district being unable to provide referral information does not by itself prove that those fields should be recreated. First determine what actually happened using the student's available IEP paperwork, CALPADS history, family information, and current district/IEP-team knowledge.

If there is no clear Referral By, Referral Date, Parent Consent Date, Initial Evaluation Date, or Special Ed. Initial Entry Start Date, look for the earliest date known to the family or shown in the available paperwork that indicates when the student started special education.

When no more specific historical dates can be established, use that earliest known special education start date for:

FieldHistorical fallback
Referral ByUse Other.
Referral DateUse the earliest known date indicating when the student started special education.
Parent Consent DateUse the same earliest known date when the actual date cannot be established.
Initial Evaluation DateUse the same earliest known date when the actual date cannot be established.
Special Ed. Initial Entry Start DateUse the same earliest known date when the actual historical entry date cannot be established.
This is a reconstruction fallback, not a new-referral shortcut.
Do not use today's date or manufacture a new referral simply because original historical documents are unavailable. If the student is actually being newly referred now, use Initial Evaluation Process.
Special Ed. Initial Entry Start Date is not CA Entry Date.
Special Ed. Initial Entry represents the historical start of the student's special education participation/eligibility history. For an eligibility established in another U.S. state that is being introduced into California CALPADS special education reporting for the first time, use Out-of-State IEP Fields — SELPA From & CA Entry Date to determine the separate CA Entry Date requirement.

Back to top

Special Arrival Scenarios

Returning student with an existing SSID

Use the transfer/search process first. Do not create a new record merely because the student is returning. Start with New or Returning Students.

Part C / IFSP to Part B

If the student is currently in the Part C / IFSP system, use the specialized Part C/Part B workflow rather than treating the situation as an ordinary new IEP-age record. When an IFSP record is held by another district, coordinate the appropriate SIRAS access/next-district process before creating a duplicate record.

Preschool / SSID after parental consent

For a preschool child who does not yet have an SSID, obtain the SSID as required once parental consent for an Initial Evaluation establishes the reporting obligation. Preserve the existing external training reference: CDE training on SSID requirements after parental consent.

Out-of-state U.S. IEP

Do not choose SELPA From = Out of State merely because the student most recently lived outside California. First check the student's existing California CALPADS special education history.

  • If CALPADS already contains the student's valid eligibility / Special Education Initial Entry history, preserve that history and use the normal incoming/returning workflow.
  • If the student's eligibility was established in another U.S. state and CALPADS has no California special education history for that eligibility, use Out-of-State IEP Fields — SELPA From & CA Entry Date and Plan Adoption.

Developmental Delay on an out-of-state IEP

The prior article documented the following SIRAS/CALPADS disability mapping for an adopted out-of-state IEP that uses Developmental Delay:

  • 281 — Established Medical Disability for students age 3–5; or
  • 280 — Other Health Impairment for students age 6–9.

Confirm the student's current age and the applicable reporting guidance before using the disability code.

Back to top

Choose the Correct SIRAS Status

For Special Education records, Active should represent all three of the following being true:

  • Enrollment = Yes
  • Eligibility = Yes
  • Participation = Yes

If one of those is not true, the appropriate SIRAS status may be Pending or Inactive depending on the actual situation. Use SIRAS Record Status and the onboarding decision in New or Returning Students.

Back to top

Duplicate Records

SIRAS can detect possible duplicate records using identifying information such as Name + DOB, SSID, or Student ID. When SIRAS identifies a possible duplicate, compare the record using the SSID and locate/request the existing record. Do not knowingly create duplicate student records.

Existing SIRAS duplicate-record warning example retained from the prior article
Existing duplicate-record warning example retained from the prior article.
Existing SIRAS duplicate-record follow-up example retained from the prior article
Existing duplicate-record follow-up example retained from the prior article.
Verify the result:
After creation/onboarding, confirm the record represents the student's verified current eligibility, participation, enrollment, and known historical information; then continue to the correct incoming-plan, Initial Evaluation, or other workflow.

Back to top

scroll to top icon