Closed claire-hughez closed 3 days ago
From what I know @mason-emily @claire-hughez
It would be good to do some quant analysis on the reasons for this data clash that aren't qual/anecdotal but alas if we don't have them I do think there is enough qual learning to put the weight of data validation on the AB. The real issue is how long it takes the AB to confirm this as the current service rules won't let the ECT start induction without AB confirming the relationship. In induction disco we suggested recording a provisional AB provided by the school that is then overridden by the AB confirmation so as not to stop the process of training and delay the induction in general.
In theory this should be fine because we don't pass this information to LPs later on, but if we are considering resolving that, we should think of some service rules to make sure the data we pass to LPs has been validated but we also don't stop training
I think this also applies for programme type which is reported by ABs too cc @emily-prudence-dfe
It will also apply to induction start date. Would be good to consider all 3 if possible.
EDIT: Descoped, as we'll take the ECT start date from schools as something different.
This analysis is frying my brain.
I have added to this:
@mason-emily if you have time on Thurs and can just sense check the new structure makes sense I'd really appreciate it. Once you have, I'll send over to Nathan or others.
@tonyheadford I had a chat with Pete and I think there's some bits to think through for migrated ECF1 data. Would love your thoughts there please, I left some ideas for general principles but they might be rubbish.
It's so fiddly and confusing! 😢
Emily and Tony have reviewed.
This is going over to Nathan now and we will have a review of how we're going to handle.
Claire has put a call in today for next steps
Claire to write tickets for next steps
@claire-hughez has written tickets and shared to channel
Why?
In ECF2, we're going to consolidate the appropriate body portal from TRA into our database and set of services.
This means that in 1 database, we'll have:
Most of the time (we hope), this will be the same. The school will tell us Teaching School Hub 1 is supporting an ECT's induction, and the appropriate body will come and register that ECT with us.
However, we still need to think about how we hold that in our database and consider the information. Do we just store what schools put? Or what ABs put? Or both?
Mostly importantly, we know sometimes this might differ due to data mistakes. Anecdotally, it seems we should trust the appropriate body more than the school for the truth on who is supporting an ECT's induction. We know schools get confused with the terminology around different organisations that support ECT induction an training.
We also need to think about how we handle this when the AB reported differs from the school to the AB.
What?
Out of scope
Actually prototyping or designing full solutions. For now, we just need a rough idea. For a while, the AB service will be live, and not the schools service.
Helpful links or other information