CEDS-Elements
CEDS-Elements copied to clipboard
CEDStandards
Add new element to collect the number of days the initial IEP was late
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Doris Mann
Authoring Organization(s)
State of Michigan/CEPI
Email address
Use Case Title Provide a concise description that defines the use case.
Add new element to collect the number of days the initial IEP was late
Use Case Description List the proposed element name(s), definition(s), and/or option set(s).
New element to collect the number of calendar days that the evaluation and completion of the initial IEP went beyond the 30 school-day timeline or agreed-upon written extension.
K12 -> K12 Student -> Individualized Program -> Eligibility -> Evaluation -> Days Beyond Timeline
Use Case Background Provide information related to why these changes/additions are needed.
As there may be more than one agreed-upon extensions, it is more efficient and less burden to the districts to report the number of calendar days the Initial IEP/Evaluation, including Part C to B transition, was held late.
Location of Element in the Domain Entity Schema
K12 -> K12 Student -> Individualized Program -> Eligibility -> Evaluation -> Days Beyond Timeline
(63, 73) IEP plan development date tracking
Add new element to collect the number of days the initial IEP was late
Add elements to track the timeliness status for the evaluation of eligibility
This is a valid new concept that is not presently docmented by the data model. However, the proposed strategy is not incomplete. Also, it is incorrect to place the new details in the eligibility element.
It would be better to create a new grouping element such as
K12 -> K12 Student -> Individualized Program->planDevelopmentSchedule
with elements such as
thirtyDayClockStartDate daysBeyondTimeline (less than one means schedule was met) reasonForDelay (null value means schedule was met)
