Stanedge Healthcare / BG-Demo – Demo
Callcompleted
Stanedge Healthcare · 16 Mar 2026 15:30
Theo Gallagher demoed search, chat and the dashboards builder on an anonymised extract. Graeme Outram and Caroline Westby focused on freshness, read-only access, revocation and patient data. Deal total still around £140k.
What was said
What this says
As at Fri 9 Oct 2026Theo Gallagher demoed search, chat and the dashboards builder on an anonymised extract. Graeme Outram and Caroline Westby focused on freshness, read-only access, revocation and patient data. Deal total still around £140k.
What happened: Theo ran the demo on the sample Graeme prepared. Caroline saw the evidence timeline she struggles to build by hand.
Customer view: Graeme welcomed relief from one-off report requests and asked about freshness, read-only source access and clean revocation. Caroline must take patient-identifiable field restrictions to the information governance lead.
Commercial: Tom restated the deal at around £140k, to be confirmed in writing, and 12 May 2026 as a target for a decision. Caroline said she cannot speak for Jeremy on the date.
Watch: The sample was small, so Graeme wants a larger extract test before any performance claim. Enterprise SSO and provisioning was shown as relevant to governance.
Themes
As at Fri 9 Oct 2026Theme
Demo, governance and access
Importance
upsell
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Theo Gallagher to send the governance answers, role definition and exit plan, marked as drafts where they are drafts.
- Graeme Outram to consider a larger extract for a volume test.
- Tom Ashdown to take the comparison and confirmed figure to Jeremy Platts.
Risks
As at Fri 9 Oct 2026- Information governance sign-off on patient-identifiable fields is outstanding.
- Performance at full volume is unproven until a larger extract is tested.
- Caroline cannot commit Jeremy to the 12 May 2026 target.
Opportunities
As at Fri 9 Oct 2026- Enterprise SSO and provisioning answers a governance concern Caroline said matters to them.
- The dashboards builder could ease Graeme's load of one-off report requests.
Transcript
Tom AshdownAfternoon all. Can everyone hear me? Theo, you're on mute, I think.
Theo GallagherThanks Tom. Is that better? Good afternoon, everyone.
Caroline WestbyGood afternoon. Yes, we can hear you both. Graeme is with me, we're in the same room today, so apologies if there's a bit of echo.
Graeme OutramHello. I've turned my laptop speakers off so it should be alright.- Tom AshdownBrilliant. How's the week treating you? Caroline, any more from that insurer?
- Caroline WestbyFunnily enough, yes. They've come back wanting the referral history by hospital. Which hospital, which month. It's the same pattern, and it's rather the reason I wanted today to go ahead.
- Tom AshdownWell, let's see if we can help. Theo's going to drive today. Theo, do you want to say how you'd like to run it?
- Theo GallagherYes. I always start with what is open, so you know where we stand. One, the information governance questions from your side. Caroline holds those, and I owe her the written answers on where the data sits and who can see it. Two, the connectors. Graeme, you are the owner for access to your Snowflake account, and we need your confirmation of what we can read. Three, the sample data you shared. I have loaded a small anonymised extract, so what you see today is your shape, not invented examples.
- Graeme OutramThat all sounds right. I did the extract on Thursday. I took out names and kept the hospital and the insurer codes, as Caroline asked.
- Theo GallagherThank you, that is exactly what I needed. Right, I'll share my screen. Can you see the home page?
- Caroline WestbyWe can. It looks quite plain, which I like.
- Theo GallagherPlain is deliberate. This is the search and chat view. I will ask the same question Caroline raised: show me the authorisation history for one insurer, by hospital.
- Theo GallagherIt returns a summary, and under it the records it used. Each line has a source, so you can click through to the email, the helpdesk ticket or the finance entry. That is what I mean by we can evidence that. The answer is never just text.
- Caroline WestbySo what does the insurer see? If I send them this, is it the same as what we've got?
- Theo GallagherIt is what is in your records, and it shows you which records. If the insurer's view differs, you can see where the gap is. I would not claim it tells you what the insurer holds, only what you hold and how it lines up.
- Caroline WestbyThat's a careful answer, thank you. I'd rather it was careful.
- Tom AshdownTheo does careful. It's why I let him loose on the demos.
- Theo GallagherLet me try a patient services question. A complaint about a delayed result at one site. I will ask what happened, in order.
- Theo GallagherIt builds a timeline: the referral, the email to the hospital, the helpdesk ticket, the reply. Notice the gap in the middle. Nothing is recorded for several days. That is the sort of thing a complaints handler would want to see before they write back.
- Caroline WestbyYes. That is exactly the evidence we struggle to put together. Which hospital is that one?
- Theo GallagherIt shows in the record. I can filter by site. Here, the second site in your extract.
- Graeme OutramCan I ask about freshness? When I look at this, how current is it? Because if it's a day behind, someone will act on old data.
- Theo GallagherGood question. The refresh runs overnight and should be complete by seven in the morning on business days. The page shows when each source last loaded, so you can see it rather than trust it. If a source stops loading, it shows as flat, and we would want to know quickly.
- Graeme OutramAnd that runs in our account, using our compute?
- Theo GallagherYes. It runs inside your Snowflake account, in a dedicated schema and role that you create and control. I will send you the role definition and the control reference for it, so you can review it before anything is switched on.
- Graeme OutramPlease do. I'd want read access only on the source side, and I'd want to be able to revoke it cleanly.
- Theo GallagherBoth are reasonable. Read only on sources is how it is designed. Revocation is a documented step, and I can give you the exit plan in writing so you can see it works.
- Tom AshdownThat's the bit people forget to ask, to be fair. What happens if you walk away.
- Caroline WestbyJeremy will ask. He always asks.
- Tom AshdownHe did last time. Which is fine, no drama. I've got the whole-life view with him already.
- Theo GallagherShall I show the dashboards next? Graeme, I suspect this part is for you.
- Graeme OutramGo on then.
- Theo GallagherThis is the dashboards builder. I will build one live: complaints by hospital by month, with the insurer split. It takes a question and turns it into a chart you can save and share.
- Graeme OutramSo it's not a replacement for our reporting tool, it sits alongside?
- Theo GallagherAlongside. If your team already has reports that work, keep them. The value is when somebody who is not an analyst can ask a new question without raising a request with you.
- Graeme OutramThat would take some pressure off, I won't pretend otherwise. I get a lot of one off requests.
- Caroline WestbyHe does. I'm one of the culprits.
- Tom AshdownHa. Aren't we all.
- Theo GallagherA last piece on access, as governance will want it. Enterprise includes single sign on and user provisioning, so people are added and removed from your own directory. When someone leaves, their access goes with them.
- Caroline WestbyThat matters to us. And patient identifiable information, can we restrict who sees what?
- Theo GallagherPermissions follow what you set in your own account. I would not want to overstate it, though. Which fields are held back is a decision for your governance team and Graeme, and we would document it with you. I can walk through the control reference at the next session and show how we evidence it.
- Caroline WestbyGood. I'll need to take that to our information governance lead before I say anything further.
- Tom AshdownSensible. I'll not push on that.
- Graeme OutramOne thing before we finish. The sample was small. Would the answers hold up at full volume?
- Theo GallagherFair challenge. The behaviour is the same, but I would not promise performance until we have tried it on a larger extract. That would be part of the first weeks if you proceed, and I can propose a test before that if you prefer.
- Graeme OutramI'd prefer that, yes.
- Tom AshdownRight. Let me pull together where we've got to. Theo, you'll send the written governance answers, the role definition and the exit plan. Graeme, you'll think about a larger extract. Caroline, the information governance lead. And I'll go back to Jeremy with the comparison he asked for, with the deal total still at around £140k, which I'll confirm in writing, and the target of 12 May 2026 for a decision.
- Caroline WestbyThat is fine. I can't speak for Jeremy on the date, as you know.
- Tom AshdownUnderstood. It's a target, not a deadline.
- Theo GallagherI will send the documents by the end of the week, marked as drafts where they are drafts.
- Caroline WestbyThank you both, that was really helpful. Kind regards.
- Graeme OutramCheers all.
- Tom AshdownCheers, speak soon.
Callsmade from