1. ECO R OLL O UT J UNE 17, 2015

2. N EW P ROCESS FOR C HILD O UTCOMES C OLLECTION No longer OWS. All information will be collected in the Kansas ITS database. No longer will a KIDS ID need to be assigned. All children will randomly receive a KS ITS unique identifier. It will be automatically generated upon a child’s entry into the ITS database. The KS ITS identifier will be KSxxxxxxxx. (eight digits). For a period up to 3 years, a child may have both a KS ITS identifier and a KIDS ID #.

3. U NIQUE I DENTIFIER

4. D ATA E NTRY Please ensure that names are spelled correctly for children and parents Please enter the child’s legal name There is an additional field for an alternate name if the child is commonly called something other than his legal name. This is important for ensuring we are tracking the same child throughout the State.

5. D ATA E NTRY Middle Name Gate! Childs Middle Initial/or Middle Name is required. If more than one middle name, use the first one. If we see numerous NMI in the middle name fields, we will question the accuracy of your data. Implement obtaining middle names into your intake process so that this is not an issue for data entry.

6. T IPS FROM A DAM These are the general guidelines for entering ECO data and IFSP dates through the database. Because each ECO is related to an IFSP, you must first select the type of IFSP and enter the date. After July 1st all IFSP dates will be entered on the ECO screen rather than the Referral, IFSP, & Eligibility screen. ECOs are only entered for Initial and Annual IFSPs. If Review is selected for the type of IFSP, no ECO information is shown. Next you need to select the type of ECO entry being entered. Initial Entry refers to the initial entry into the ECO system (generally with the initial IFSP)

7. T IPS FROM A DAM Local Entry refers to a child who has transferred from another network and already exists in the ECO system Annual entries are entered for an existing child when doing an Annual IFSP When Exit is selected for the type of ECO entry, you will see an additional drop down to select the type of Exit, a field for entering the Exit date, and additional fields for each area of the ECO for describing the progress made. If child is exiting from ECO, an IFSP date is not required.

8. D ATA E NTRY All IFSP data should be completed in 15 business days per your contractual assurances. This includes the Outcome Descriptor Statements as they are part of the IFSP. All ECO entry and exit data must be completed by July 31 st of a given year.

9. O UTCOME D ESCRIPTOR S TATEMENT Outcome Descriptor Statements appear on pages 4, 5 & 6 of IFSP, both Word document and Web based. An Outcome Descriptor Statement is part of the IFSP process. It will happen at each initial and annual IFSP. Choosing the Outcome Descriptor Statement will be part of the process of looking at the child and family’s strengths and needs. It will follow discussion of the child’s functioning during daily activities and routines in each outcome area. “My Child’s Story” in the IFSP.

11. I NCLUDING P ARENTS IN THE P ROCESS It is part of the IFSP, so parents are always included. Teams should meet after evaluation with at least two practitioners and use the My Child’s Story, Documenting Basis for Rating, and Decision Tree. Arrive at an Outcome Descriptor Statement During the IFSP, discuss with the parent all the information you have gathered and how that coincides with what they are seeing. Discuss the Outcome Descriptor Statement and how all previous information led to the Statement chosen.

12. A F AMILY G UIDE TO P ARTICIPATING IN THE C HILD O UTCOMES M EASUREMENT P ROCESS These were introduced at the Spring Combo Available in English and Spanish It is recommended that parents be introduced to the Outcome process prior to the IFSP Designed to inform parents about the process Kansas has added an additional page to discuss the Outcome Descriptor Statement.

13. IFSP O UTCOMES o There are four new boxes on the IFSP outcomes page.  Positive Social Relationships.  Acquiring and Using Knowledge and Skills.  Taking Action to Meet Needs.  Family Outcome o This should not change your IFSP outcomes development process. o Mark which Early Childhood Outcome the IFSP outcome ties to. This comes after the IFSP outcomes are developed. o More than one Early Childhood Outcome area may be marked.

14. IFSP O UTCOMES The process for developing IFSP Outcomes remains the same. They should be based on child and family needs and priorities. The purpose for marking the ECO area on an IFSP outcome page is for categorization, and data collection and linking our system. IFSP Outcomes are based upon routines and activities, not developmental areas! We do not expect or want IFSP Outcomes for each ECO Outcome area.

15. T RANSITION Use Universal Referral to Part B form as your official notification. This form will be required. The date of the form should be the same date that is entered into the database for the referral date. The ITS database will automatically generate the form. Please inform Part B of all children who have a KIDS ID when the referral to Part B is made. As we transition out of OWS, new Part C children will have only the KS ITS number. Note: *This may require a new process for KIDS ID assignment by your Part B partners.

16. T RANSITION In the Transition Plan, there will be three questions to mark. 1. Permission for the conference. 2. Permission to share educational records for the purpose of Transition. 3. Permission to share records for longitudinal data collection.

18. T RANSITION You will need to have permission to share with Part B, in order to share any information other than required referral information. This includes the KS ITS unique identifier. That number does not get shared without permission to share for longitudinal data collection. The Consent to Share/Release of Information Form has been updated to coincide with these questions. Providers will need to be informed about data collection and its potential uses in order to discuss that question with parents. The answers to these questions trigger the ability of the data system to upload to KSDE.

20. W ORD IFSP U SERS Process will be the same when developing the IFSP. Data entry will need to occur in the database to record the ECO Outcome Descriptor Statement Information. Word users will also need to enter the assessments used, when choosing the Outcome Descriptor Statement.

21. F INAL P ROGRESS M EETING A final progress meeting is essential to this process; 1. With the family, determine progress that has been made on current IFSP outcomes. 2. Choose a final Outcome Descriptor Statement for each outcome area based on child’s functioning at exit. 3. Record on the Final Progress/Outcome Summary form. 4. Enter Exit Information into ITS database.

22. F INAL O UTCOME D ESCRIPTOR S TATEMENT An Outcome Descriptor Statement will be chosen upon exit. Must choose yes/no as to progress made. No would only be an option when the final outcome statement is lower than the initial outcome statement. This would be used infrequently. Outcome Descriptor Statements that are the same as an initial Outcome Descriptor Statement indicate progress was made. The child gained skills as he aged.

23. F INAL O UTCOME D ESCRIPTOR S TATEMENT A brief summary of progress is described. This progress summary should be based on IFSP outcome progress (functional) and progress shown on your curriculum based assessment. I.e.: HELP, AEPS. For children being served past the third birthday, (summer birthdays), the child must be exited with an ECO statement by their third birthday. Children for whom contact has been lost for 90 days, should be exited with an ECO statement based on last contact and most recent assessment information.

24. F INAL P ROGRESS R EPORT /O UTCOME D ESCRIPTOR S TATEMENT This is not an IFSP review. May be done in conjunction with a review if the timing warrants this. It is part of your exit process/ final visit. This final progress report would be done when a child leaves a local program, or when there has been loss of contact for 90 days. There is a separate form to record the final statement, and it would be entered into the ITS database. (Not on the IFSP form).

26. EXITS The Exit reason will be marked when choosing a Final Progress Outcome Descriptor Statement This will allow you to make a final Outcome Descriptor Statement for children who are not exiting on the ITS database. Children who are exiting ITS services will exit the ITS database in the usual manner.

27. Q UESTIONS ? Wait! What???