What was said
What this says
Current to 11 Oct 26Onboarding call with Josh Fairburn, a data analyst, to connect the incident log. The first pull worked. Severity codes and records with no home need confirming with the customer's quality team before anything is summarised.
What happened: Hamza Akhtar added the incident log connector and ran the first pull. Records loaded and the field list looked right, but severity arrives as free text in some rows and as number codes in others.
Customer view: Josh is doing this alongside his day job and apologised that the home mapping was not finished. He is about two thirds through it and will add both names for the two homes renamed after a merger.
Open points: Josh will confirm the severity codes with the quality team. A few records have no home, probably raised by head office staff, and will show as unassigned rather than be dropped.
Watch: Josh is the only customer contact on the call and the work depends on his spare time. Family contact data is the next source and its owner is not yet known.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Josh to confirm the severity code list with the quality team and finish the home mapping.
- Josh to check the refresh status page first thing on Monday and report anything odd.
- Josh to find where family contact data lives and who owns it before the next call.
Risks
Current to 9 Oct 26- Severity codes are unconfirmed, so nothing can be summarised by severity until the quality team confirms them.
- Home mapping is unfinished and depends on Josh finding time next to his day job.
- Records with no home may be dropped or miscounted if their origin is not confirmed.
Opportunities
Current to 9 Oct 26- Showing unassigned records openly supports the evidence trail the customer's quality team wants.
- Family contact is the next source to connect, which would deepen the connectors in use.
Transcript
- Hamza Akhtar NoneAfternoon Josh. Can you see my screen yet or shall I wait?
- Josh Fairburn NoneAfternoon. Not yet. Oh, there it is. Yes, got it. It's quite small, hang on.
- Hamza Akhtar NoneI'll zoom in. Right, so today is the incident log, as we said. Do you have the service account?
- Josh Fairburn NoneI have. It took a bit of arguing, but it's read only, like you asked. I've put the details in the secure note.
- Hamza Akhtar NoneLovely. Okay, I'm going to add the connector now and let it do the first pull. This will take a few minutes, so while it's going, did you get the template for the home mapping?
- Josh Fairburn NoneI did, I've done about two thirds of it. The ones I'm not sure about are the homes that were renamed after a merger. Two have a different name in the log from what they're called now.
- Hamza Akhtar NonePut both names in, one row, and flag the row. That's what it's for. If you leave them blank, the brain will treat them as separate homes and the counts will look odd.
- Josh Fairburn NoneRight, I'll do that tonight. Sorry, it should have been finished.
- Hamza Akhtar NoneIt's absolutely fine. You're doing this next to your day job. Okay, the first pull is done. Let's have a look at what came in.
- Hamza Akhtar NoneSo, records are loading and the field list looks right. But I can see the severity field is coming through as free text in some rows, and as a number code in others. Does that ring a bell?
- Josh Fairburn NoneYes. The older homes used to type it. Newer ones pick from a list. We changed the form some time last year.
- Hamza Akhtar NoneOkay, that makes sense. I'll write a small rule that treats the typed values as the same categories as the codes. Can you tell me what the codes mean? Because I don't want to guess which is serious.
- Josh Fairburn NoneI'd have to look it up. The safeguarding ones are the top two bands, but let me confirm with the quality team so I give you the real list, not what I remember.
- Hamza Akhtar NoneThat's the right call. Natasha will want it checked anyway. Meanwhile I'll leave the severity field as it came, and nothing gets summarised by severity until you've confirmed.
- Josh Fairburn NoneOkay. One more thing. A few records have no home at all. Is that a bug?
- Hamza Akhtar NoneI'd say it's your data, not the connector. Let me filter for those. Right, there are a few. They look like records raised by head office staff. Who'd raise an incident from head office?
- Josh Fairburn NoneProbably the regional managers, when they're told about something on a visit. Hmm. I'd have to ask. I think that's fine, but I'd like Natasha to see that.
- Hamza Akhtar NoneI'll note it as a question rather than fix it. Better we show them as unassigned than quietly drop them. Natasha's evidence trail point.
- Josh Fairburn NoneYes, she'd be annoyed if something vanished.
- Hamza Akhtar NoneExactly. Now the refresh. It'll run overnight and should be complete before seven in the morning your time on working days. Can you check it first thing on Monday and tell me if anything looks off?
- Josh Fairburn NoneYes, I'll look at it before the stand-up. How will I know if it hasn't run?
- Hamza Akhtar NoneThere's a status page in the admin area, and I'll show you where. It will show the last successful load per connector. If it's stale, it'll say so in plain words.
- Josh Fairburn NoneGood. I'll put it in my Monday routine.
- Hamza Akhtar NoneGreat. Next time I'd like to do family contact, so if you can find out where that lives and who owns it, that would be a big help.
- Josh Fairburn NoneI think it's in the care records system, in the notes. Not great, to be honest. I'll find out.
- Hamza Akhtar NoneThanks. Speak next week, Josh.
- Josh Fairburn NoneCheers, Hamza. Bye.