ECO Roll Out

ECO ROLL OUT
JUNE 17, 2015
NEW PROCESS FOR CHILD OUTCOMES
COLLECTION
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 #.

UNIQUE IDENTIFIER
DATA ENTRY
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.

DATA ENTRY
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.
TIPS FROM ADAM
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)
TIPS FROM ADAM
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.

DATA ENTRY
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 31st of a given year.

OUTCOME DESCRIPTOR STATEMENT
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.

INCLUDING PARENTS IN THE PROCESS
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.

A FAMILY GUIDE TO PARTICIPATING IN THE
CHILD OUTCOMES MEASUREMENT PROCESS
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.

IFSP OUTCOMES
o
There are four new boxes on the IFSP outcomes
page.




o
o
o
Positive Social Relationships.
Acquiring and Using Knowledge and Skills.
Taking Action to Meet Needs.
Family Outcome
This should not change your IFSP outcomes
development process.
Mark which Early Childhood Outcome the IFSP
outcome ties to. This comes after the IFSP
outcomes are developed.
More than one Early Childhood Outcome area
may be marked.
IFSP OUTCOMES
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.

TRANSITION
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.

TRANSITION
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.

TRANSITION
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.

WORD IFSP USERS
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.

FINAL PROGRESS MEETING

1.
2.
3.
4.
A final progress meeting is essential to this
process;
With the family, determine progress that has
been made on current IFSP outcomes.
Choose a final Outcome Descriptor Statement
for each outcome area based on child’s
functioning at exit.
Record on the Final Progress/Outcome
Summary form.
Enter Exit Information into ITS database.
FINAL OUTCOME DESCRIPTOR STATEMENT
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.

FINAL OUTCOME DESCRIPTOR STATEMENT
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.

FINAL PROGRESS REPORT/OUTCOME
DESCRIPTOR STATEMENT
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).

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.

QUESTIONS?
Wait! What???