Getting A Little Behind?. ILP Database Late Data Entry Discussion. Analyzing data informs policy and practice decisions, with the ultimate goal of improving outcomes for the families you serve . But data itself is a tool, not a solution. . To get any benefit from it,
ILP Database Late Data Entry Discussion
informs policy and practice decisions,
with the ultimate goal
the families you serve.
you need to know what information
is in your database,
how to use it and
be assured is it timely and accurate.
For federal and state reporting purposes we take a snapshot of the data –
freezing a copy of the live data.
This frozen snapshot tells
your story from year to year.
Timely and accurate data is critical to show true trends from year to year.
A frozen data set misses data points
and missed data
will not be represented on any annual reports.
While we can be proud of the small discrepancies, these differences translate to
extra data cleaning for you
non-compliant status with a corrective action plan when in reality you are doing better than the data indicates.
your database reports are not
as accurate as
they could be.
Data entered in January 2013
examined to see how long after the event occurred
it was entered.
Definition of late data used for this exercise:
any data entered >30 days after the occurrence.
(ie: PT evaluation completed 11/15/12 was entered into the database on 1/5/13)
FY14 grant agreements will require attention to data on a monthly basis.
Send suggestions for additional items on the cleaning and/or ` other reports
feedback as to how
monthly data cleaning will affect your data entry system.
We are available for TA support.
Alaska EI/ILP must report annually
to the public the performance
of each early intervention service (EIS) program
located in the State on the targets in its
Part C – SPP