Creating an Initial IFSP
  • 02 May 2025
  • 3 Minutes to read
  • Dark
    Light

Creating an Initial IFSP

  • Dark
    Light

Article summary

NOTE: An Evaluation/Screening record must be created prior to creating an Initial IFSP.

  1. If a child is determined Eligible based on an Established Condition, the Evaluation Screening is entered on the Client Case by local EIB service coordinator PRIOR to creating an Initial IFSP.

  2. If a child is determined eligible based on a significant delay, EI Screening/Evaluation results are documented by the evaluation team via the EI Provider Portal.  That Evaluation/Screening record will populate from the EI Referral Case to Client Case upon creation.

Users will create a new IFSP from the Client Case.

  1. From the Client Case, click on the NEW IFSP button in upper right corner

Graphical user interface, text, application  Description automatically generated

  1. New IFSP: Initial box will pop up

  2. Populate fields only in the Information section at the top

  3. The Client Case will automatically populate

  4. IFSP Meeting Date - Enter the date that the IFSP team met to develop the IFSP

  5. Primary Setting

  6. Home

  7. Community

  8. Other

Note: This field is to be completed when services have been identified. Users can complete this field on the IFSP details section, IFSP Home visual force under EI Services Agreement tab, or the Client Case. Best practice is to enter the primary setting on each IFSP

  1. Status

    1. In Progress – Pending (ex. waiting approval from supervisor)

    2. Active – Active/Open

    3. Closed

  2. IFSP Late Reason - If the Initial IFSP date is more than 45 days from the date of referral, select an IFSP Late Reason:

    1. Sys – AU/CCB reschedule Meeting originally scheduled with the family and a participant representing the Local Early Intervention Program had to cancel and reschedule

    2. Sys – MDA not timely – If the reason the IFSP meeting was late was because a child’s multidisciplinary (MD) evaluation could not be scheduled in order to meet the 45-day timeline

    3. Sys – No interpreter availableMeeting is delayed because the family requires an interpreter, and one cannot be found

    4. Sys – Required participant not avail – One or more of the required participants do not participate.  This is applicable even if the meeting occurs

    5. Fam – Child HospitalizedFor children who were previously inpatient in a Level III NICU.  Used if the timing of the referral and discharge are such that the IFSP is developed beyond the required 45-day timeline

    6. Fam – Child or fam illness – Meeting is scheduled and has to be cancelled and rescheduled due to the child or a member of the child’s family being ill

    7. Fam – Family scheduleIf a family is offered several options for meeting, or the family is only available at specific times that are difficult for the rest of the participants

    8. Fam – Request date >45 – If the family specifically requests to meet on a date later than the 45-day required timeline

    9. Fam – No show – If the meeting or MD evaluation is scheduled and confirmed with the family and the family does not show at the scheduled time and the meeting cannot be rescheduled to meet the timeline  

    10. Fam – Difficulty reaching family – After receiving the referral, the family is difficult to reach when trying to schedule the MD evaluation or IFSP meeting

    11. Fam – No bio parent signature – Instances where a biological parent still retains parental rights for the child and getting signatures to permit evaluation were difficult to obtain  

    12. Fam – Severe weather – Circumstances in which severe, documented, adverse weather conditions exist which makes travel dangerous for any or all participants

    13. Sys Natural Disaster/Pandemic – Meeting is delayed due to extenuating circumstances such as wildfire, flood, pandemic etc.

  3. Verify that the Active? box is checked and the Status is In Progress

  4. Click Save

For questions, content edits, or other inquiries on this document, contact the EI Data Team.


Was this article helpful?