How to Coordinate ESY With Health-Plan ABA Services

Verify each approved service

For Elena, obtain the current IEP, ESY schedule, named school contacts, private treatment recommendation, provider capacity, payer authorization, and family agreement. Record effective dates and limitations. A draft calendar, verbal estimate, or prior summer arrangement is weaker than the current controlling source for the actual program.

Resolve schedule conflicts by authority

When ESY and ABA overlap, show each team the exact conflict, travel time, health needs, student preference, and possible alternatives. The IEP team controls IEP changes. The private clinician controls clinical recommendations within scope. The payer controls authorization, and the family or student makes applicable consent choices. Preserve each decision and its date.

Coordinate focused information

Share Elena's relevant schedule, communication, safety, and support information through a valid route. Keep school records and private clinical records separately authored. A shared one-page plan can list contacts and urgent information without copying full notes. Record when information was sent, received, corrected, and incorporated into staff instructions.

Measure burden and missed access

Track scheduled, offered, delivered, declined, canceled, and missed services separately for Elena. Add travel, transitions, sleep, recovery, meals, preferred activities, family workload, and student feedback. A high attendance rate can coexist with exhaustion or inaccessible communication. Review early enough to change the authorized plan before the short summer window ends.

Prepare Elena's summer calendar

To coordinate ESY and health plan ABA, create Elena's calendar with service, location, provider, travel, transition, health, AAC, meals, rest, and family commitments. Mark authorization and capacity separately from preference and fit. Give each conflict to the responsible school, clinician, payer, provider, or family decision owner and record the resolution before services begin.

Build Elena's source-attributed ESY record

Create a restricted summer cross-service coordination plan for Elena's service, owner, goal, provider, location, schedule, transport, AAC, health, authorization, record, billing, fatigue, conflict, and review. Give every field a source, event or observation date, author, status, owner, next action, due date, correction, and closure evidence. Keep Elena's direct statement, family report, school record, private-provider observation, transport record, and interpretation separately attributed.

Within the summer cross-service coordination plan, separate individualized ESY need, IEP content, school implementation, private clinical recommendation, health-plan authorization, provider capacity, family or student choice, records disclosure, transportation, and delivered service. A shared schedule or goal never combines those authorities.

Protect Elena's access and ordinary needs

Give Elena accessible information, AAC or another communication mode, privacy, enough time, useful choices, breaks, and a way to decline or correct a nonemergency discussion. The ASHA AAC portal says AAC users should always have access to communication tools or devices. Record the student's message separately from adult prediction or interpretation.

Preserve Elena's food, water, bathroom access, mobility, prescribed care, rest, relationships, preferred activities, and emergency help. The BACB Ethics Code guides covered behavior analysts on communication, consent and assent when applicable, competence, assessment, documentation, risk, and referral. It does not assign IEP, school, payer, transportation, or legal authority.

Ask eight ESY evidence questions for Elena

Use these questions in the summer cross-service coordination plan:

• Which student need and FAPE question is the IEP team deciding?
• What does Elena want, value, question, or decline?
• Which current state criterion and record supports the decision?
• What service, schedule, setting, staff, transport, and technology are required?
• Which opportunity, support, prompt, source, and period produced the evidence?
• Which school, clinical, payer, family, or transport owner controls each action?
• What current access or interim support is needed while a decision remains open?
• What evidence and student feedback will close or revise the action?

Classify Elena's fields as complete, failed, pending, declined, disputed, or inapplicable with a reason. Pending work stays visible and blocks only the dependent action.

A fictional ESY example for Elena

Elena is fictional and involved in six weeks of overlapping ESY and health-plan care. Reviewers freeze 32 cross-service controls and complete 25 of 32 by the checkpoint. Missing student, school, provider, transport, AAC, health, privacy, or implementation evidence remains in Elena's denominator with an owner, age, and next action.

The summer cross-service coordination plan reports evidence completion separately from IDEA compliance, FAPE, clinical quality, coverage, student choice, service delivery, educational benefit, and satisfaction. Reviewers preserve the original cohort and all failed or pending states. They do not infer that ESY or one support caused change when instruction, health, access, schedule, experience, and time changed together.

Use compatible ESY denominators for Elena

For Elena's summer cross-service coordination plan, report completed decisions divided by decisions due; required IEP elements documented divided by elements reviewed; service minutes delivered divided by approved service minutes due; accessible communication checks passed divided by checks due; transport arrivals completed by target divided by scheduled rides; and validated corrections divided by corrections due.

Segment Elena's results by school, program, service, setting, provider, communication access, transportation, decision state, missed-service reason, and source version when useful. Publish raw counts with percentages and age open items. Keep different definitions, service units, and maturity windows in separate measures.

Create Elena's dated ESY path

List Elena's request, evidence cutoff, IEP review, decision, notice, IEP update, staffing, transport, AAC readiness, health handoff, first service, missed service, progress review, correction, last service, fall handoff, and retest in chronological order. Distinguish proposed, scheduled, event, entry, receipt, decision, and effective dates.

The joint FERPA-HIPAA guidance classifies records by holder and capacity. Use the current school, state, provider, payer, and student-specific source for each decision. Share purpose-needed information through the applicable route and preserve authorship, receipt, corrections, and privacy.

Explain ESY source scope for Elena

For Elena, 34 CFR 300.106 provides the federal ESY rule: services must be available as necessary for FAPE, the IEP team decides individually, and the public agency cannot use the prohibited categorical or unilateral limits. The general FAPE rule supports this educational duty; it neither authorizes private care nor decides Elena's individualized ESY plan. Current state criteria, procedures, calendars, and dispute routes can add important detail and require direct verification.

The CASP organizational overview supplies broad operations and risk framing for page 4 in this cluster. Give Elena and the authorized adult an accessible summary of decisions, evidence, owners, dates, limits, and review triggers. Keep the page draft and noindex pending named review.