Skip to content

UK Healthcare TUG

UK Healthcare Tableau User Group 26 Feb 2026

UK Healthcare TUG - FDP and Tableau - February 2026

51 min 8,864 words transcribed

Summary

The UK Healthcare Tableau User Group's February 2026 meeting, FDP and Tableau, recorded by the group on its own YouTube channel and republished here with credit. Host Rowan Bradnum, with Sara Sekelj, opens the group's first meeting on Teams and sets out the layers: NHS England's Federated Data Platform (FDP), the Palantir Foundry machinery inside it, and Tableau dashboards on top. Miles Henderson of NHS England then walks through, step by step, how he built and published the national care home COVID and flu vaccination dashboard from FDP data. He starts with the brief: a reliable denominator of eligible residents, the numerator of recorded vaccinations, and healthcare professional visits, so that low uptake can be read as a capacity, refusal or data quality problem; and why current CQC data matters when hundreds of care homes open and close in a season. He builds the aggregated, de-identified dataset with PySpark in a controlled code repository, moving calculations upstream so Tableau needs fewer calculated fields; completes a data egress request and data protection impact assessment with information governance; has developers review the pull request and remove data classification markings; connects Tableau with the Palantir Foundry connector and a personal token; publishes the extract as a data source on Tableau Server with its own refresh schedule, swaps the workbook onto it and keeps a master copy still connected to FDP; and grants access through Okta, tracking use with Who has seen this view. Questions cover data suppression for small care homes, ontology objects, the CQC API, timescales for approvals, what happens to tokens when someone leaves, version control, group-based user management for national dashboards, ODBC drivers, and the future of Tableau in NHS England.

Key points

  • Start with the brief: an accurate denominator, a numerator and an operational measure such as visits together explain why uptake is low.
  • Use current CQC data; hundreds of care homes can open and close within one vaccination season.
  • Push calculations upstream into the FDP code so the Tableau workbook needs fewer calculated fields and performs better.
  • Publishing FDP data to Tableau needs an egress request, a data protection impact assessment and a developer-reviewed pull request; later code changes do not need a new DPIA.
  • Connect with the Palantir Foundry connector and a personal FDP token, then publish the extract as a separate data source with its own refresh schedule.
  • Keep a master copy of the workbook connected directly to FDP so you can still edit calculations and republish if a token expires or its owner leaves.
  • Swapping a dashboard's data source to FDP does not change who can access it; access still runs through Okta.
  • Build the approval timescales into project plans; the governance steps take longer than the build.

Jump to a chapter (15)

  1. 0:00 Welcome, and FDP, Foundry and Tableau explained
  2. 3:04 Miles Henderson: from FDP to a Tableau dashboard
  3. 3:34 Understanding the brief: denominator, numerator and visits
  4. 5:35 Actionable insights and the data sources
  5. 7:32 Working with stakeholders and keeping CQC data current
  6. 12:21 Q&A: suppression, ontology and the CQC API
  7. 14:21 The data pipeline, and doing calculations upstream
  8. 17:11 Egress request, DPIA and developer review
  9. 20:43 Q&A: approvals and timescales
  10. 24:04 Connecting Tableau with the Foundry connector
  11. 25:59 Publishing the data source and the dashboard
  12. 30:12 Access through Okta and tracking use
  13. 31:24 Q&A: tokens, master copies and versions
  14. 36:54 Q&A: national dashboards, drivers and Tableau's future
  15. 47:24 Prize draw and next meetings

Transcript

0:02 Rowan Bradnum: Uh, recording is on. I will probably need, or one of us may well… unless it's Charlotte, uh, who's, uh, Mrs. Admin herself, uh, will need a bit of reminder to do that. So if you do spot us having forgotten that, please do let us know, 'cause I think in the Bevy platform it just auto, auto did that. But yeah, as usual, we'll record, we'll make the recordings, uh, uh, available and so on.

0:25 Uh, so yeah. So you've got, um, myself and Sara on the call today as, as your TUG leaders. Uh, Charlotte and Steve are able to join us on, on today's, uh, today's one. Um, please also let us know if any of your colleagues have trouble getting on, and we'll see what we can do and fix in the background, uh, around that. Um, today we only really have kind of one main focus, and that's Miles.

0:49 We're gonna have a bit more time for him to go through some of what he's been, uh, talking about recently from a, a slightly different angle with the, uh, Tableau and Palantir integration within his, his work product. Uh, I had a little play with, uh, ChatGPT and, um, uh, yeah, this is, uh, what we came up with today, uh, trying to understand and explain sort of the different layers between what we have here.

1:14 So this is, this is my interpretation, this is not Miles' interpretation, but I liked, I liked putting him in there as the mechanic. I felt… I quite enjoyed that, that picture there. But yeah, uh, the FDP is the kind of overall platform, uh, or the h- uh, that, that it all exists on. And Palantir Foundry side of it maybe being some of the machinery that builds out the roads and so on, but very much where the data actually flows and what it flows in, those cars and those dashboards being the Tableau product that sort of sits, uh, sits on top of it.

1:46 So this is, uh, yeah, what, what I threw in there. Um, uh, yeah, but I think without too much further ado, I think we'll hand over to Miles. I'll, uh, I'll stop, um, I'll stop sharing.

2:01 Uh, and Miles, if you wanna share your screen-

2:04 Miles Henderson: Okay

2:04 Rowan Bradnum: … at this point.

2:06 Uh, and yeah. Um, if you haven't met Miles before, he's been on a few of these TUGs already. He works, uh, within NHS England. Um, I'll let him do a bit more of a deeper introduction himself, but he's a very, uh, yeah… His, his work has been really, got a lot of, um, attention recently for very good reasons because obviously the NHS is going through massive changes, and Tableau within that is, is something that is being, um…

2:33 Its future is kind of shifting a little bit within that. But Miles is very much at the forefront of where we can actually see the two technologies work side by side, hand in hand with each other. Um, we don't really wanna dive too deep into politics or what the, what, what we think of FDP or Palantir or Foundry, all those things. That's not the purpose of this call, but we're excited to be showcasing what can be done in conjunction and what, uh, Miles has been able to do in the constraints of that landscape.

3:02 Um, so yeah.

3:03 Over to you, Miles.

3:05 Miles Henderson: Okay. So I'm having a bit of difficulty here, bear with me one moment.

3:09 Rowan Bradnum: Okay, no problem.

3:11 Miles Henderson: Some…

3:13 It's not letting me do what I wanna do. Okay.

3:16 Um, if I just, uh-

3:18 Rowan Bradnum: Let me check if I can-

3:21 Miles Henderson: You see my screen?

3:24 Rowan Bradnum: Yeah, we can see your screen.

3:25 Miles Henderson: Oh, cool, cool.

3:27 If I just increase the size a little bit.

3:29 So I've just, um, taken some inspiration from you and just done some AI pictures.

3:34 Rowan Bradnum: I love it.

3:34 Miles Henderson: So basically, uh, this is just the, um, bas- basically an overview of the process I went through to get the care home dashboard that I showed you guys last month published.

3:49 So I've tried to include everything. I've made assumptions that people might have more… might know what I'm talking about when I'm talking about Tableau, but I'll have to make a start.

3:58 So, um, pretty much the first thing you need to do is, um, I had to do was understand the brief. So the first step to complete is to understand what the most impetric, me- most important metrics the dashboard will need to show. In terms of the care, care home dashboard, it's important to show the denominator, the total number of residents eligible for C- COVID and flu vaccination.

4:22 This defines the size of the cohort. Without an accurate data denominator, uptake percentages are meaningless. So the numerator, the number of residents who have received a recorded vaccination, and this data is sourced from GP records where vaccination events are logged. And then visits. The number of he- healthcare professional visits made to each care home measures operational delivery.

4:45 If uptake is low but visits are also low, the issues may be logistical rather than hesitancy. So, um, I like this term. Hamza suggest- said about this couple to me like when I used to work with him. So one of the things we look at is, um, identify the actionable insights. So, um, one of the things the dashboard would need to do is highlight underperformance, flag regions below seventy-five percent uptake, identify individual care homes below the threshold, and so variance between regions.

5:18 Um, enable root cause analysis. By combining uptake of visit data, you can show low uptake and low visits, capacity or scheduling issue, low uptake and high visits, possible refusal, data quality issue, high uptake and low visits, efficient delivery model. So, um, um, support regional accountability, so regional breakdowns, map visualizations to quickly spot geographic gaps, um, downloadall- downloadable spreadsheets for operational follow-up, um, drive target improvements with direct additional vaccination teams, escalate underperforming providers, and improve data recording where numerator inaccuracy exists.

6:02 So basically this is just like, this is all discussed with the, um, project team. So the, um, care home- Visits are managed by the performance team. So we discuss, we have meetings, performance team decide to discuss what they want to see in the dashboard.

6:19 Um, the next step is to identify the, our FDP data sources and complete the data transformation. So the next step is to identify the required FDP data sources and combine them, um, combine them using PySpark within a controlled code repository. So the data sources we use are the residence cohort data, so we define the denominator.

6:45 Vaccination event data, so recorded COVID and flu vaccinations to calculate the numerator.

6:52 And visit data rec- records of healthcare professional visits to care homes.

6:57 So the data transformation processor, we're using PySpark, the data sets were cleaned and standardized, filtered to the reporting period, joined using appropriate identifiers, and aggregated so we can calculate, um, total eligible residents, total vaccinated residents, and uptake.

7:17 So the final data set used for reporting was fully aggregated at care home or regional level, free from patient-identifiable information, compliant of data protection and governance standards.

7:30 Um, so this ensured the dashboard's data-

7:32 Rowan Bradnum: Miles, can I-

7:33 Miles Henderson: But-

7:33 Rowan Bradnum: Can I jump in and ask a couple of questions-

7:35 Miles Henderson: Yeah, sure

7:35 Rowan Bradnum: … as you, as you're going through? What was that process, you know, going back to number two that you were doing there, what was that process like meeting with the performance team in the care homes? Did they-

7:44 Miles Henderson: Um-

7:44 Rowan Bradnum: Were they really clear on what they wanted and needed-

7:47 Miles Henderson: Yeah

7:47 Rowan Bradnum: … or was that a challenging process?

7:49 Miles Henderson: Um, I think as with anything when you're discussing things with stakeholders, sometimes their, some, their understanding of the data and the process isn't as great as yours.

8:01 So you have to be really good at explaining what, um, in- intricacies of the different data points are.

8:10 So for example, they, they might make an assumption on the data, and it, it is, it's just really good to be really clear. Um, one of the issues we had was that we were using, um, CQC data to identify the care homes that were gonna be in scope for the vaccination period.

8:31 But I'm sure as many people are aware, you're often seeing on the news the care homes are closing and opening-

8:37 Rowan Bradnum: Mm

8:37 Miles Henderson: … or being closed on quite a regular basis. They're going out of business, et cetera. So the care home estate can change quite regularly. So for example, we could use August CQC data to identify the care homes for a season, but by Decem- by December, 300 of those care homes have closed, and 300 new ones have, um, opened up.

9:00 Rowan Bradnum: Mm.

9:00 Miles Henderson: Either in the original, in, in the premises of the closed homes or new homes altogether.

9:06 Rowan Bradnum: Mm.

9:06 Miles Henderson: So it's really important to use up-to-date CQC data. So, um, one of the things I did was when we used old CQC data from the beginning of the season, I actually logged how many care homes opened and closed throughout the season. And I, I now have the, I was, then had the evidence to go back to my stakeholders and say that we've now, we can now, if we use the most up-to-date data for CQC, we're gonna have a much more accurate picture of what's going on out there.

9:38 And, um, we'll have a better uptake figure. Because by using old, out-of-date CQC data, we're actually excluding homes.

9:46 Rowan Bradnum: Mm.

9:46 Miles Henderson: New homes have come on board where residents have now been transferred to from the closed homes. So that was a really good way of showing h- how we were progressing. Um, did you have any more questions, Rowan?

10:00 Rowan Bradnum: No, that's really helpful.

10:01 Miles Henderson: Yeah.

10:01 Rowan Bradnum: I presume you're using the kind of public available API within the CQC, within all of that sort of thing?

10:06 Miles Henderson: Well, that's-

10:07 Rowan Bradnum: 'Cause-

10:08 Miles Henderson: That's very interesting you say that, Rowan, 'cause, um, we have, we, we, we go through a process of uploading CQC data into FDP manually 'cause, um, we've tried using-

10:18 Rowan Bradnum: Oh, really?

10:18 Miles Henderson: … API and it hasn't worked. So-

10:19 Rowan Bradnum: Ah

10:20 Miles Henderson: … um, if you have any knowledge that could help us with using the API, that'd be most appreciated.

10:24 Rowan Bradnum: Yeah, I'll catch up with you about that. We did a whole project-

10:26 Miles Henderson: Brilliant

10:26 Rowan Bradnum: … on that at one point.

10:27 Miles Henderson: Thank you.

10:28 Rowan Bradnum: So.

10:28 Miles Henderson: Oh, okay.

10:29 Rowan Bradnum: Yeah.

10:29 Miles Henderson: Thank you.

10:30 Rowan Bradnum: Um, yeah. But, uh, were you familiar with that data before you got into those client meetings, or was this something you were learning on the fly-

10:37 Miles Henderson: Um, I-

10:37 Rowan Bradnum: … in conjunction with talking to the clients?

10:40 Miles Henderson: I literally, um, was handed… So essentially, originally, the care home data was, um, done manually by using something called Capacity Tracker, which was a online form the care homes logged into and updated-

10:54 Rowan Bradnum: Okay

10:54 Miles Henderson: … with number of residents and vaccinations.

10:57 And this is downloaded as a spreadsheet. But sometimes the data was a month out of date, so it was never current.

11:03 So they used to send out, the guy who used to do it before me, used to send out spreadsheets twice a week-

11:09 Rowan Bradnum: Mm

11:09 Miles Henderson: … using these manual downloads. So idea behind using FDP and Tableau was to use as much current up-to-date data as possible, and, um, literally have it very visual.

11:24 Rowan Bradnum: Mm.

11:25 Miles Henderson: And, um, the CQC data is very interesting. I mean, I've been using this since, um, March '24.

11:35 Rowan Bradnum: Okay.

11:35 Miles Henderson: So, um-

11:36 Rowan Bradnum: So you're quite familiar with it?

11:37 Miles Henderson: Yeah. I'm very familiar with it, yes, yes. And, um, it's very interesting to see, like, the, um, the data is very, um, good. They've added a couple of columns last year, which caused a little bit of confusion, but they were very helpful. Because one of the things we used to have with care homes is that if you had a dual provider site, a care home was being listed twice.

12:01 Rowan Bradnum: Ah.

12:01 Miles Henderson: So they added a column which allowed us to see what the primary provider was.

12:05 So we were able to filter out the secondary provider and just go by the primary provider. So that was very useful.

12:11 Rowan Bradnum: Mm.

12:12 Miles Henderson: But if I, um, if I just go on to the next bit-

12:16 Rowan Bradnum: Just before you do-

12:17 Miles Henderson: Mm-hmm

12:17 Rowan Bradnum: … um, there's a question that came in.

12:19 Miles Henderson: Yeah. Okay.

12:20 Rowan Bradnum: A couple of questions.

12:21 Miles Henderson: Yeah.

12:21 Rowan Bradnum: Uh, Wolf asks, "Was there a need for data suppression at smaller care homes?" Do you wanna take that one, just to-

12:27 Miles Henderson: Um-

12:27 Rowan Bradnum: … speak to that first?

12:29 Miles Henderson: Yeah. Um, that's a very good question, actually, and this actually came up in another project I'm working on. So, um, with, uh, with terms of data suppression, so the whole idea of the dashboard was to ensure that all care home residents are vaccinated full, um, of COVID, COVID vaccinations.

12:49 So, um, we had a conversation of our information government department, and they said as long as the care homes know who, who's in their care homes and who hasn't been vaccinated.

13:01 So there wasn't really a need to do any data suppression because we're doing these figures at care home level.

13:08 Um, some care homes could only have one or two stu- one or two residents if they're extremely small, so there, there wasn't really a requirement for that.

13:18 Rowan Bradnum: Okay.

13:19 Miles Henderson: Yeah. Um-

13:20 Rowan Bradnum: And then Ruby a- asks-

13:21 Miles Henderson: Oh

13:22 Rowan Bradnum: … uh, "Did you need to put your aggregated data set into an olo- ontology object type?" And then asks, "Is the CQC data not in UDL to pull through into FDP?"

13:32 Miles Henderson: Um, the CQC data is in UDL. A colleague, Jim Lockier, uses that to identify the most recent CQC care home ID when he assigns a care home ODS code to a resident. But, um, in terms of what we use it for, he d- we, we can't actually access that because it's on a, a different server used by eng, by the engineers. But, um, I'm hoping with what you just said about the API and being able to help, we'll be able to automate that ourselves.

14:03 Rowan Bradnum: Yeah, we definitely use some interim technology.

14:05 Miles Henderson: Yeah.

14:05 Rowan Bradnum: So I, I can't not make any promises you're gonna-

14:07 Miles Henderson: Yeah, yeah

14:07 Rowan Bradnum: … but we'll definitely share our expertise with you on that-

14:09 Miles Henderson: Okay

14:09 Rowan Bradnum: … so I'll get my data engineer who was involved with that on a call with you-

14:13 Miles Henderson: Okay

14:13 Rowan Bradnum: … to figure that out.

14:13 Miles Henderson: Okay. Well, it be, it will need to be one of our data developers, but, um, I'm more than happy to coordinate that.

14:20 Rowan Bradnum: Yeah.

14:20 Miles Henderson: Um, I might-

14:21 Rowan Bradnum: We'll, we'll try that side.

14:22 Miles Henderson: Okay. And then basically, another thing I wanna say, this is like a pipeline I created, so I have lots of different transformations that all merge together in the final data sets, which is all aggregated. So we, so all of these, um, yellow boxes here have all got transformations using the patient's side ID, but as soon as it goes into the final data set, it, it turns into…

14:43 It's all aggregated, and we remove all the patient's identifiable information.

14:49 If I go down-

14:49 Rowan Bradnum: Okay

14:49 Miles Henderson: … to the next step, we, we then complete an egress request. So before the data-

14:54 Rowan Bradnum: Can I-

14:55 Miles Henderson: Sorry

14:55 Rowan Bradnum: One last, one last question on that.

14:57 Miles Henderson: Yeah.

14:57 Rowan Bradnum: Just 'cause that's a topic that we're kind of dealing with at, at the moment.

15:00 Miles Henderson: Okay. Yeah.

15:01 Rowan Bradnum: In terms of a lot of that's data production and transformation-

15:04 Miles Henderson: Yeah

15:04 Rowan Bradnum: … and cleaning and so on.

15:05 Miles Henderson: Yeah.

15:05 Rowan Bradnum: Was there anything in that particular, in those steps that you can speak to for us as a group-

15:09 Miles Henderson: Yeah

15:09 Rowan Bradnum: … where you prepared the data so it was particularly Tableau friendly? Was there anything that you did that, you know, to change the shape of the data or pivot in a certain way, or a- any- anything in particular that is useful for us as a group to understand this is a good step to do upstream of Tableau to get the most-

15:27 Miles Henderson: Yes

15:27 Rowan Bradnum: … out of your data-

15:27 Miles Henderson: Absolutely

15:28 Rowan Bradnum: … to then put into Tableau?

15:29 Miles Henderson: I-

15:29 Rowan Bradnum: Can you speak to that a little?

15:31 Miles Henderson: I can do that, I can do that example. So I'm currently doing another dashboard for HPV vaccinations, and I had all the data going into the Tableau dashboard, and I thought… And I was, like, writing all these different c- calculated formulas to say, "What is the student den- student denominator for girls? What is the student denominator for boys?" And I wrote a formula that said gender equals male, then the student denominator.

15:56 And I thought, "Why am I doing all of this in Tableau?" So I literally went back to, um, the Tableau code, the, um, FDP code, and actually wrote those formulas into the FDP data.

16:10 So when I then… So then when it went in back into Tableau afterwards, it was already there, so I didn't have to write those formulas.

16:18 So it is-

16:19 Rowan Bradnum: And was that the sort of performance benefit? Is that why you do it?

16:21 Miles Henderson: Yeah. Performance benefit, yes. So I didn't have to have so many, um, manual formulas in Tableau. So what I tend to do is if I've created a data set in FDP and transport it into Tableau, and realize, oh, I've forgotten to do that, or I could have done that better, I go back to FDP and write the, write the formula into the actual code.

16:43 So then I don't have to have… We're not, not… And I'm not having to rely on so many calculated formulas in Tableau.

16:50 Rowan Bradnum: Okay. That makes a lot of sense.

16:51 Miles Henderson: Yeah.

16:51 Rowan Bradnum: Uh, I think Ruby really would like an answer to the question of if whether the final data set went into the ontology object type.

16:59 Miles Henderson: I'm not quite sure about that one.

17:02 Rowan Bradnum: Okay.

17:02 Miles Henderson: Um-

17:02 Rowan Bradnum: Maybe one we can pick up and get back.

17:04 Miles Henderson: Yeah. One that's probably one we can pick up. I'll take that away.

17:08 Rowan Bradnum: Okay. I'll stop interrupting you. You crack on.

17:11 Miles Henderson: Um, and the next bit we do… So that's basically the data pipeline. So next one we do is complete an egress request. So basically put, like, a little form together. So this is, like, a very, a similar form to what we have to fill in on the FDP. So before the data can be used in Tableau, the analyst must complete a data egress request form and submit it to information governance.

17:35 IG will arrange a meeting to complete a DPIA, a data protection impact assessment, to understand the intended audience for the go- dashboard and confirm how the data will be used.

17:48 So the DPIA is a formal risk assessment process required in the UK GDPR, where processing data is likely to result in the high risk to individuals' rights and freedoms, particularly when handling hen- health or sensitive data.

18:04 Once satisfied, EG, IG will issue a reference number confirming approval.

18:10 So this reference number then must, must then… Sorry. This reference number must then be provided to developers to finalize the ingestion process and a- enable the data set to be used in Tableau.

18:23 So without the IG approval reference, the data cannot be used for reporting, so the de- the develop- the developers will not remove security markings for ingress into Tableau without it, without the EM support.

18:37 And then, um, once we have the code approval and IG have approved it, um, we have to then submit something called a pull request. So the code repository, um, has a…

18:54 We create a pull request, so it finalizes so the data- so it… When you create a pull request, it ma- it finalizes the data in the code repository so it can't be edited anymore, and then you submit it to the developer. They will then add some additional code to the code to ensure to remove any information government markings that would stop it from being used, and they'll also review the final dataset and make sure it's fully aggregated, make sure there's no patient-identifiable information, and, as I said, as I just said, remove the data classification markings within the transformation code.

19:36 Um, if these markings are not removed, the dataset remain restricted, cannot be used in Tableau. Now, the good thing here is they only have to add those, um, data marking, data removal markings once. So if I go… If I've created a dataset, put it in Tableau, and I realized I've forgotten something, I have to go back to Tableau, create a new bra FDP, create a new branch of the code repository, make the changes to the code, and then create another pull request and ask the developer to approve it.

20:09 But when they approve it a second time, what they will get is a view of the code as it was in the first version, the code as it is in the second version, and they can see exactly where the code has been changed.

20:23 So if there's no datasets been added in or nothing else has been added in and needs IT approval, they're usually quite happy just to approve it straightaway, and that usually takes a couple of days or… at most. It's… They, they're really quick in approving them.

20:41 And then it goes into linking in Tableau. So-

20:44 Rowan Bradnum: Cool. Can I ask a couple of questions on that?

20:46 Miles Henderson: Yes, sure.

20:46 Rowan Bradnum: Because a few-

20:46 Miles Henderson: Please

20:46 Rowan Bradnum: … questions come in from the group. So-

20:48 Miles Henderson: Yeah

20:48 Rowan Bradnum: … first, a quick one, just to confirm.

20:50 Miles Henderson: Yeah.

20:51 Rowan Bradnum: Uh, the… You talked a bit about code changes here, um, within these checks. Do the code changes also require their own, uh, DPIA or is that just-

21:00 Miles Henderson: No

21:00 Rowan Bradnum: … a one, one-off process?

21:02 Miles Henderson: It's just a one-off process. So the DPIA is done in the first instance. Once that's approved and the code has been approved the first time, any further changes to the code, if you're just changing the name of a column or adding a new formula, that isn't, um, subject to a new DPIA. That just gets put… That can just be put through.

21:22 Rowan Bradnum: Okay. No, that makes sense.

21:24 Miles Henderson: Yeah.

21:24 Rowan Bradnum: And then is this approval process for the whole of the national FDP instance, or is it just local t- or, like, what approvals will need to happen in local tenancies? D- do you know that answer?

21:35 Miles Henderson: I don't know the answer to that one.

21:37 Rowan Bradnum: Okay.

21:37 Miles Henderson: Um-

21:37 Rowan Bradnum: I don't think so

21:37 Miles Henderson: … I know this, this, this is, uh… I think this is, um…

21:41 I think this would probably be a, an overarching process. Um, I know it's definitely in place for vaccinations and screenings, but I imagine it's gonna be all over, um-

21:52 Rowan Bradnum: Yeah, you'd think so.

21:54 Miles Henderson: Yeah.

21:54 Rowan Bradnum: Um, then the other question's just timeframes.

21:56 Miles Henderson: Yeah.

21:56 Rowan Bradnum: What are the timeframes and timescales, uh, in terms of these processes, both in terms of the DPIA checks as well as the developer checks and things like that? So the

22:05 Miles Henderson: Um-

22:05 Rowan Bradnum: … approval, at least

22:06 Miles Henderson: …

22:07 so when we did the care home dashboard, which was back in March '24, um, it was a little bit time-consuming because nobody really was aware of the, um, process. I'd already had some, um, knowledge of it because I'd worked on a couple of other dashboards with a previous team I was in.

22:25 But, um, once we got over the IG clearance, et cetera, um, it… I don't think it took more than about two or three weeks.

22:34 But with this-

22:35 Rowan Bradnum: Okay. How long did the IG take?

22:37 Miles Henderson: Pretty quick, really. I think one of the things we came up against with developers, um, were a bit overzealous. So as I said, when we had, like, one, one school with, like, two students and they said, "Well, there's patient-identifiable…

22:54 There's res- there's school-identif- um, patient-identifiable information in there," and they didn't think it should be approved for us. When we went back to IG, they said, "No, that's fine because the students have to be vaccinated." They says, "We don't kn- we… It's, um… And the schools know who the patients are, um, so it's fine to go ahead."

23:16 Rowan Bradnum: Yeah. No, it makes sense.

23:18 Miles Henderson: Yeah.

23:18 Rowan Bradnum: I think it's just worth us bearing in mind as Tableau developers, I guess-

23:21 Miles Henderson: Yeah

23:21 Rowan Bradnum: … primarily on this call, that-

23:23 Miles Henderson: Yeah

23:23 Rowan Bradnum: … as we're developing data that might touch other systems-

23:27 Miles Henderson: Yeah

23:28 Rowan Bradnum: … whether it's this one or other ones, that we need to make sure when we're speaking to stakeholders and planning the process out that it is time-consuming to go through these various-

23:36 Miles Henderson: Yeah

23:37 Rowan Bradnum: … it's not, it's not just getting the work done. It's the approval checks and so on-

23:40 Miles Henderson: Yeah

23:40 Rowan Bradnum: … that, uh, uh, create delays that need to be factored-

23:44 Miles Henderson: Yeah

23:44 Rowan Bradnum: … into the process.

23:45 Miles Henderson: Yeah. Um, the lady we deal with, um, she's very well, well sort of aware of what it is we do, the process now, and I think she's sort of got confidence that I sort of understand what I need to do.

23:56 So, um, it goes through a bit quicker now.

24:00 Rowan Bradnum: Okay.

24:00 Miles Henderson: But I mean-

24:00 Rowan Bradnum: That's good.

24:01 Miles Henderson: Yeah.

24:01 Rowan Bradnum: Hopefully quicker and quicker.

24:03 Miles Henderson: Yeah.

24:04 Rowan Bradnum: Okay, cool.

24:04 Miles Henderson: Um, and then the next bit is linking to Tableau. So if the egress application authorize, developer will approve the changes and merge the changes to the dataset. This approval will ensure that all data sensitive markings will be removed.

24:19 The da- developers will also create a photo, folder in FDP specific to the egress request. In this care case, the folder will be called care home egress.

24:28 The analyst will then need to create a view of the data in FDP and set up a refresh schedule so the report updates daily at a specific time.

24:37 Usually, it's best to make the schedule dependent on when core data sets refresh. So here I've got a screenshot from Tableau, which shows that the, um… So you create– You connect to the data, and you use the Palantir Foundry data sets by Palantir connection.

24:53 And that now will open up this box here, which is the Foundry data sets by Palantir.

24:58 You'll be asked to sign in with a token.

25:01 Now, this token will last for a few months, and this connects your da- Tableau dashboard to the data set you've created on your profile in FDP.

25:11 So you can access this. You can create a token by accessing your user, your F- your profile in FDP, and it's very clear. It's, it, it literally says, says on the token there. It says… You click Tokens, and then where it says Create token, you click on Create token, and it will give you a unique ID, which is about 40 letters and numbers all muddled up.

25:35 And you just u- I– What I tend to do is I copy that, put it into a Notepad, and every time I need to use it to log into Tableau, I just copy and paste it from Notepad and put it into Tableau.

25:46 And then once you've done all of that, you will then be asked, prompted to enter name of the egress folder from Tab FDP and the name associated with the view.

25:56 Once complete, the data will be ready to use in Tableau to create a dashboard. So in the project, you enter the name of the egress folder, and in the dataset, you just create the… You just enter the name of the view you've created, and then literally you press on Connect, and it will then bring the data into Tableau, and then you can create your dashboard.

26:20 Um, once you've created your dashboard, you need to then publish your dataset to Tableau Public Server. So, um, yeah, I've forgotten to add the end. I forgot to add that bit into this, um, presentation. So, um, I'm not sure if anybody's had experience in Tableau of creating an extract.

26:39 So what I tend to do is I'll set up my dataset in Tableau. If I've added any formulas or calculated formulas, I'll add those, and I'll create an extract.

26:50 And then once we have the extract, we will then publish the data source, not the, not the da- the thing, the thing we need to remember here is where we're, we're, we're actually publishing the data that feeds the da- dashboard separately to the dashboard.

27:09 So what you need to do is, um…

27:13 Sorry, what do I need to say? So you… So we have this little form here that comes up, Publish data source to the Tableau Server.

27:21 Type in the name of the loc- Type in the location and the name of the dataset. So this is the name that the dataset will appear under on Tableau Server.

27:30 You set a refresh schedule. So you say you want the data to refresh from FDP at nine AM every morning.

27:38 And then you set authentication. So any authentication, you're gonna have to… You have to select Allow refresh access.

27:46 And that will make sure that the, the actual data will update from FDP on a daily basis. Now, the big thing to remember here, this is a different refresh schedule to the one I mentioned earlier in FDP.

27:59 So the one in FDP refreshes on a daily bes- basis to get the latest information on vaccinations that took place the day before.

28:07 This refresh is actually making sure that the data that was taken from FDP yesterday is ref- uh, refreshed to the latest version today.

28:18 Um, and then once you've published the data source, we need to be linked back to the dashboard by selecting Data, New Data Source, and selecting Ta- selecting Tableau Server.

28:31 Um, then searching for the ta- data source that's just been uploaded.

28:35 User then will… The user will then need to use the Replace Data Source option to change the data being used to look by the report to the published data source. So basically, what you're doing is you've got a data source connection from FDP, and then what you're doing, you're creating a new data s- You're then creating a new connection to the data source you've just published to F…

28:56 to Tableau Server, and then you're swapping them over. So when you use, um, Replace Data Source, you're actually replacing the data source from FDP with a data source you've published to, to Tableau Server. And what that does is it makes… It publishes… It ensures that this, when you upload the, publish the workbook, which is the actual dashboard, it's not publishing the data with it, 'cause that will slow performance.

29:25 So what you're doing is you create the extract, you publish the data source, and you c- and you connect it back into the workbook and then remove the connection to FDP.

29:38 And then once you do that, you publish the dashboard. So now the completed dashboard is linked to the data source, it can be com- published.

29:46 Using the form available under the Server menu option, Publish Workbook.

29:51 The next step is to email ITV s- IT service desk the list of, list of users. These u- users, individuals, should then be given adequate permissions to access the dashboard. And enable th- In order for them to be able to do that, they need to have Okta access.

30:08 So every time they go and log on to view the dashboard, if they haven't, um, saved a password, they'll be prompted to enter a password every day, but it tends to save the password in the box anyway.

30:23 And the next thing you can do is, um, by accessing the dashboard in Tableau Server, the user will be able to identify the num- people, number of people accessing daily. So- Um, we have, in there we have an option to say, if you click on the care homes main page and click on access, it says, "Who has seen this view?" You click on that, and you get a list of all the people that have been accessing the dashboard, the time they last viewed it, and the n- number of times they've accessed it.

30:53 And then by clicking on the icon here, which is on the, um, left-hand side, you can click on cross tab and download it to a spreadsheet, and then use that as evidence of how many people are using the dashboard.

31:07 So I was able to tell, using this data, that during the last COVID vaccination season, on average, 65 people a day were using the dashboard.

31:18 Um, I think that's the end of my presentation now. Um, is, has anybody got any extra questions at all?

31:24 Rowan Bradnum: Yeah, I've, I've got a few. And, uh-

31:26 Miles Henderson: Yeah

31:26 Rowan Bradnum: … we'll, it's good that we've got a good chunk of time, so please do just raise your hand if you've got a question you wanna come off and talk about. There's been a lot of great chats, and it's exactly we wanna, want to take place, uh, uh, behind the scenes as well to let you know miles about, uh-

31:39 Miles Henderson: Yeah

31:40 Rowan Bradnum: … some of the ontology and the, those questions, bits that you were gonna kinda go away and figure some stuff out-

31:45 Miles Henderson: Yeah

31:45 Rowan Bradnum: … and maybe come back to the group on. So there's-

31:47 Miles Henderson: Yeah

31:47 Rowan Bradnum: … there's quite a bit in there just to, to, uh-

31:49 Miles Henderson: Okay

31:50 Rowan Bradnum: … make you alert of. But can you scroll back up a little bit? The-

31:53 Miles Henderson: Yeah

31:53 Rowan Bradnum: …

31:54 I'm curious about the token side of things.

31:56 Miles Henderson: Yeah.

31:56 Rowan Bradnum: Um, the, is this a token assigned to your personal user within FDP?

32:03 Miles Henderson: Yes.

32:03 Rowan Bradnum: And is this, is this what the refresh goes, uh, kind of, is communicated along? Is this part of that refresh-

32:10 Miles Henderson: Yes

32:10 Rowan Bradnum: … pull process?

32:11 Miles Henderson: Yes.

32:11 Rowan Bradnum: So what would happen if you, as an individual user, um, uh, had to leave the NHS, for example, uh, and that you had to be removed from FDP? I guess that token would need reassigning as well as the Tableau workbook itself-

32:27 Miles Henderson: No

32:27 Rowan Bradnum: … needing reassigning.

32:29 Miles Henderson: You wouldn't need to reassign the token. So a colleague, you'd need to hand it over to a colleague, and the colleague would then need to create a token in their name.

32:39 And then when it would go back to the data, you republish the data source with, with the c- new code, and then we publish it that way. The other thing I have to, I'd probably, good information to suggest, is that before you publish the data source to the Tableau Server and remove the actual connection to the actual FDP, it's a good idea to create a copy of the dashboard and use that as a master copy, which is still linked to the FDP.

33:12 So if that does happen, and t- token does expire, so, or the person leaves who's created it, you can create a cop- you can, um, go back to the master copy of the dashboard and republish the data using the new token.

33:28 Rowan Bradnum: Okay. That makes sense.

33:29 Miles Henderson: This, here's one of the problems we have, is once we've published a dashboard and used, and then used a data source as the one published to Tableau, you can't edit the, um, calculations. So then you have to have a master copy which is connected to the original FDP data source-

33:47 Rowan Bradnum: Mm

33:47 Miles Henderson: … to enable you to continue editing any formulas.

33:50 Rowan Bradnum: Yeah, I think a lot of us have run into that problem-

33:52 Miles Henderson: Yeah

33:52 Rowan Bradnum: … once you've published-

33:53 Miles Henderson: Yeah

33:53 Rowan Bradnum: … a data set-

33:53 Miles Henderson: Yeah

33:54 Rowan Bradnum: … and you wanna go back and change calculated fields. I think that's quite a global-

33:57 Miles Henderson: Yeah

33:57 Rowan Bradnum: … challenge.

33:57 Miles Henderson: Yeah.

33:57 Rowan Bradnum: So that's a really good way around that.

34:00 Miles Henderson: Yeah.

34:02 Rowan Bradnum: Um, couple of questions coming through. Uh-

34:06 Miles Henderson: Yeah

34:06 Rowan Bradnum: … before I get to a couple of specifics, I guess one of the concerns coming up within the chat is-

34:12 Miles Henderson: Yeah

34:13 Rowan Bradnum: … the idea of duplication or different versions of the same data or just governance and that sort of thing. W- how are you… Are there things that you can speak to in this process?

34:26 Miles Henderson: I use version-

34:26 Rowan Bradnum: Sort of just a little bit convoluted to make sure that you're kinda managing that.

34:31 Miles Henderson: I use version controls.

34:35 Rowan Bradnum: Okay. Do you-

34:36 Miles Henderson: And I, um, I tend to sa- I mean, the da- I mean, we don't, I mean, we tend to save over… I've got, um, backups on Word of any code I create. But, um, uh, we tend to, to, because the name of the data set is s- a specific name, you have to save over. If you make any changes to code, you have to save over the original.

35:00 You can't change the name of the final data set. You have to keep the same name.

35:06 Rowan Bradnum: And obviously, your, your Tableau dashboard is, uh-

35:09 Miles Henderson: Yeah

35:10 Rowan Bradnum: … serving a certain purpose, building a certain product on top of-

35:13 Miles Henderson: Yeah

35:13 Rowan Bradnum: … your data.

35:14 Miles Henderson: Yeah.

35:14 Rowan Bradnum: But do you see wider uses for the data set that you've produced? Is, is that communicated to other teams? Do oth- other people have access to that data? Um, is there a way that that can be a collaborative process and people-

35:27 Miles Henderson: Um-

35:27 Rowan Bradnum: … can go on from what you have?

35:29 Miles Henderson: So you do have the option. So, um, the dashboard, the first care home dashboard I created was available to regions and ICBs.

35:40 Um, and there was an option in there to download some information if they needed to. Um, we have spoken to…

35:49 Because, um, I mu- uh, I'm not sure if you remember, earlier I spoke about something called Capacity Tracker. Now, I don't, it, there is a DHSC tool which is, um, updated by care homes with resident totals and vaccination totals.

36:05 Now, that data set, um, Capacity Tracker, now that isn't, we met with them last year, and they're actually not gonna use Capacity Tracker anymore to update care homes for COVID vaccinations, because we've, using this Tableau dashboard and using all the data quality improvements we've made, and we've, well, we've actually been in a position where we've been able to improve the population figures in FDP to a high degree.

36:32 So we've got much more current and specific informa- um, numbers now for care home populations.

36:40 So there is a bit of, there is a bit of duplication there, but this tool is pretty much, um, ensured that we don't have that duplication anymore.

36:50 I think, hopefully it answers the question.

36:53 Rowan Bradnum: Yeah, I think so.

36:54 Miles Henderson: Yes.

36:54 Rowan Bradnum: I've got a few questions to work through and some hands up-

36:57 Miles Henderson: Yes

36:57 Rowan Bradnum: … so let's just, I will go through that list, which is excellent. I think a lot of interest in what you're doing here, Miles, and lots of-

37:03 Miles Henderson: Yeah

37:04 Rowan Bradnum: … positive comments coming through as well.

37:06 Uh, I think I'm gonna… I always get this mixed up with our NHS names. I think it's Philip Graham is asking, uh, does this way of user management scale? For example, nationally aimed dashboards, are you using group management?

37:21 Miles Henderson: I'm not sure about that. What con- what, um, what do you mean by group management? Is that in terms of people accessing?

37:28 Rowan Bradnum: Yeah, I would imagine so.

37:30 Miles Henderson: Yeah. Yeah.

37:30 Rowan Bradnum: Um, and Philip, feel free to come in.

37:34 Philip Graham: Uh, hi. Yeah.

37:35 Miles Henderson: Yeah.

37:35 Philip Graham: Um, so it's just in, when you were talking about having to add users-

37:39 Miles Henderson: Yeah

37:39 Philip Graham: … because obviously, um, there's, there's scope for a product that is aimed nationally. You know, imagine a dashboard-

37:46 Miles Henderson: Yeah

37:46 Philip Graham: … on a national topic that everyone's-

37:48 Miles Henderson: Yeah

37:48 Philip Graham: … RTT or something.

37:50 Miles Henderson: Yeah.

37:50 Philip Graham: You are not going to be able to manage users in that way, I don't think-

37:55 Miles Henderson: Yeah

37:55 Philip Graham: … when you are looking at users across multiple organizations-

37:59 Miles Henderson: Yeah

37:59 Philip Graham: … for a national product. So, um, I was just interested in, in whether your, you know, group management is the obvious way to, to manage in that circumstance-

38:07 Miles Henderson: Yeah

38:07 Philip Graham: … where you create groups of similar users.

38:10 Miles Henderson: I, I'm not quite sure about that. I'd have to speak to, um, a lady called Joanne Silby, who deals with that for us. I think Rowan will know her. Um, and she usually… I could ask her about that, but I'm not sure of the answer myself.

38:25 Philip Graham: Okay, thanks.

38:26 Miles Henderson: Okay.

38:29 Rowan Bradnum: Um, cool. Then we've got one, um, from Delish, uh, saying, "Do I need an ODBC driver installing by IT to connect-

38:37 Miles Henderson: Oh, yes you do

38:38 Rowan Bradnum: … to Palantir desktop?"

38:39 Miles Henderson: Yeah, absolutely, yes. We, um, yeah, we… They upgraded them before Christmas, so I had to have them reinstalled recently, yes. But I've had, um, I have, I think the drivers have been updated every couple of years, I think. I think the first time I had it done was in '23 when I started using Tableau, and I had it done late last year as well when they upgraded the Tableau Server.

39:05 All right. Okay, cheers. Thanks. 'Cause we have to put in, like, a non-standard service request in for it.

39:09 Yeah, 'cause, um- I'll check… it's all on the Palantir.

39:13 On FDP, there's a user guide, and it gives you the links to the drivers there. So I can help with that if you need be.

39:19 Okay, thanks.

39:20 Yeah.

39:24 Rowan Bradnum: Great. Uh, and then, uh, Karen Jones, you've got your hand up. Thanks for waiting so patiently for us.

39:29 Miles Henderson: Okay.

39:30 Rowan Bradnum: Uh, you've got a question or a comment. Uh, feel free to come in.

39:36 Karen Jones: Yeah. So I do have a, uh, national, um, nationally accessed Tableau dashboard that would be-

39:43 Miles Henderson: Yeah

39:44 Karen Jones: … uh, would probably… It already exists, though I'd be needing to migrate that to a FDP back end. And-

39:50 Miles Henderson: Yeah

39:50 Karen Jones: … I think one of my concerns has be- been to be sure that those national users, who are mostly in providers, um, will still be able to access it. And, um, it sounds as though Okta, the Okta-

40:04 Miles Henderson: Yeah

40:04 Karen Jones: … single sign-on system is still in place.

40:07 Miles Henderson: Yeah.

40:07 Karen Jones: So all of my current users have an Okta account and, you know, will they still be able to use that? Will they, in fact, already have-

40:18 Miles Henderson: I think you should be able to

40:18 Karen Jones: … you know, just be able to-

40:20 Miles Henderson: I think you should be able to-

40:21 Karen Jones: Yeah

40:21 Miles Henderson: … 'cause you've already got a Tableau dashboard they're using. It's already uploaded to a server, or you're actually change-

40:27 Karen Jones: Yeah

40:27 Miles Henderson: … if you change this to FDP data, all you're actually doing is changing the data source. You're not actually changing-

40:34 Karen Jones: Yeah, okay

40:34 Miles Henderson: … the access to the, to the actual dashboard, so I think that should be fine. 'Cause I've changed the data source to the care home dashboard a couple of times, and it didn't affect people's access.

40:46 Should, I think that should be fine.

40:49 Karen Jones: It's a relief to know that we still have Okta-

40:52 Miles Henderson: Yeah

40:52 Karen Jones: … to manage user access. Um, the other question is, you know, the, the, the, uh, as far as I'm aware, the, the Tableau, um, the Tableau software itself i- is being removed by NHSE at the end of December 26th, so, you know, is it still a viable option for us to move our back ends to FDP?

41:14 Um, or are we gonna have to look for a new front end rather than Tableau? Perhaps this is not the right environment to discuss this, but-

41:21 Miles Henderson: Um, but, um, I did hear something about that, but I wasn't quite sure it was as soon as December 26th. Um, I think one of the issues we have with FDP is that, um, the reports you can build, um, I don't think they're quite as visual as Tableau, and there's not s- quite so much, um, uh, deg- degree of, um, visual and elements you can do.

41:50 But I- I- I-

41:51 Karen Jones: Yeah

41:51 Miles Henderson: … I'm not sure about that at all. I, I, I, I don't really know enough about the future of Tableau.

41:57 Well, I pretty much know-

41:58 Karen Jones: Okay

41:58 Miles Henderson: … about what's going on now.

42:01 Karen Jones: Yeah.

42:01 Miles Henderson: We should be able to-

42:02 Karen Jones: It would be ideal if we could just, if we could-

42:04 Miles Henderson: Yeah, we should be-

42:04 Karen Jones: If we could continue to use Tableau and migrate the data to FDP, then that would be the ideal.

42:10 Miles Henderson: Yeah. I mean, it's, I think it's more user-friendly. I think with, um, FDP, there is a, sometimes there can be a cost involved if people keep on logging into it and refreshing controls and reports, et cetera. Whereas by doing, using Tableau, I think it's, it, it, you don't have, don't have that de- degree.

42:31 Um-

42:31 Karen Jones: Mm-hmm

42:31 Miles Henderson: …

42:32 yeah, I'm not sure, but I, um, I know there was murmurings about Tableau's future, but I wasn't sure it was recently as, as, as soon as December 26th, so-

42:43 Rowan Bradnum: Yeah. Let's maybe not get too deep into the-

42:46 Miles Henderson: Yeah

42:46 Rowan Bradnum: … exact politics around it.

42:48 Miles Henderson: Yeah.

42:48 Rowan Bradnum: Karen, does that answer your question around that?

42:51 Karen Jones: Yeah. Thank, thank you.

42:53 Rowan Bradnum: But I, I will be misbehaved for a second and hope I get away with it.

42:57 Miles Henderson: Yeah.

42:57 Rowan Bradnum: What, what, uh… 'cause obviously there's a lot of this conversation pinging about, and a lot of this kind of thing coming up anyway.

43:03 W- what did you see as the advantages to building this in Tableau, um, and what was that process like in terms of getting that sign-off from whatever execs, et cetera, above you to, to make that decision?

43:18 Miles Henderson: I came from a team that was… We had a meeting. I think if everybody, people remember the presentation that Hamza and Anthony did last time. We were in a position during COVID of sending out PowerPoint presentations that could be in excess of 50 pages, where there was a lot of information, and by the time they were collated and sent out, they became out of date anyway.

43:42 So, um, one of the ideas behind using Tableau was to have connections to the most recent data accessible via a dashboard, and we spent a lot of time developing these. Unfortunately, during the last restructure, the team was disbanded, and as I was the, um, the sole NHS employee, I was, um, very gratefully accepted by my current team.

44:09 And I'd already taken… I'd already had a handover of care home work when I was in Hamza's team, and then when I came into the new team I was in now, the guy dealing with care, the contractor dealing with care homes, left quite quickly, and I literally had one more day of handover.

44:28 And I, I, I think I'd already started developing something in Tableau, so it just continued from there. It seemed a shame at the time to bin all the Tableau work we'd done and set up in, um, use NDP at the time, so that's what we continued to do. It ended up being a lifesaver as well because, um, when we used FDP, instead of having to rebuild everything in FDP, if we'd built it all in NDP, we could just re- um, we just had, we could just continue using Tableau.

45:01 Rowan Bradnum: Okay. Were there any particular features? W- were you questioned at any point to say, "No, you need to go down a different route," or you just left to get on with it?

45:10 Miles Henderson: I literally, I think they had confidence in what I'd built previously in Tableau, and just-

45:15 Rowan Bradnum: Okay

45:15 Miles Henderson: … allowed me to continue it.

45:17 Rowan Bradnum: And there's no, you're not aware of any current conversations to shift it over to anything else?

45:23 Miles Henderson: Um, the dash- the care home dashboard as it is has now come to an end in Tableau. So, um, the care home dashboard is very, it was very in-depth. It looked into a lot of different metrics.

45:36 Um, but now it's gone into what's called business as usual, so we're not so concerned about care home visits. We're not so concerned about, um, activity, et cetera. So now it's just gonna be like a very plain table in FDP, which is just gonna show uptake.

45:53 Rowan Bradnum: Okay.

45:54 Miles Henderson: But, um, we are developing a Tableau dashboard for something else. But, um, the care home one has come to an end as it is in, in its current iter- iteration.

46:05 Rowan Bradnum: Okay.

46:08 Um, great. Are there, uh… There's a question from Ruby to say, "Can we get access to your slides?" Are you happy to share those?

46:15 Miles Henderson: Absolutely, that's fine.

46:16 Rowan Bradnum: Okay, great.

46:16 Miles Henderson: But I need to go back in there and change a couple things, 'cause there's a couple things I'd forgot to add when I was reading through, so, um-

46:23 Rowan Bradnum: Okay

46:24 Miles Henderson: … yeah.

46:24 Rowan Bradnum: We'll, we'll take that offline and figure out how to get that across to everybody. Um, but yeah-

46:28 Miles Henderson: Okay

46:28 Rowan Bradnum: … we'll get that through.

46:30 Um, are there any last minute questions before we get onto the fun bit of the wheel of, uh, prizes?

46:41 I may have missed someone's question in and amongst all the chat, so please do let me know if I did and you do have a question for Miles.

46:53 Okay, we'll take that silence as, uh, a completion of that stage. Thank you, Miles. Uh, personally, I found that really interesting. Loads of great chat coming through as well. Really relevant and topical, and really clear. So really appreciate the time and effort you put into preparing all that an- and taking us through.

47:10 Miles Henderson: Thank you.

47:10 Rowan Bradnum: I think we'll give you a break now, having wheeled you out and, like, repeated TUG, so you can take a breath. But yeah, thank you so much. Really appreciate that.

47:18 Um, yeah. Onto you, Sara, to do the, uh, wheel fun.

47:24 Sara Sekelj: Thanks, and thank you, Miles. A really, really great talk.

47:28 Um, I will share my screen. As a thank you for joining us, we have a couple of prizes to give away.

47:35 Um, and, uh, I hopefully managed to put everyone's name into this. Um, so what we will do, 'cause I'm not too sure if you are able to direct message me here, um, I will drop my email, um, in the chat, and if you're selected, if you could just send us a, a quick note so that we're able to post the prize o- over to you, that would be fantastic.

48:00 Um, so let's see if this works.

48:12 Neha, if you're still with us, uh, please drop me a note over email and we'll be in touch to get your, uh, prize over to you. And then we have two more to choose.

48:33 Okay. Imran, you're our second winner. And one more.

48:50 Stopping, stopping. Joanna, um, if when you have a spare minute, if you just drop me a quick note over email, and we'll be in touch from our end.

49:04 I will attempt to stop sharing. Yes, hopefully that worked.

49:11 Um, Rowan, do you want me to do a bit of a what to expect next?

49:16 Rowan Bradnum: Yeah. I was, I was gonna have you take that. Excellent.

49:19 Sara Sekelj: Yeah.

49:20 Um, so just as a quick note, if you're new to Tableau, um, there is a newbie Tableau user group happening in March. It's the 11th of March at 4:00 PM.

49:30 And, uh, the whole topic of TUGs in 2026 for them is Road to Certification.

49:37 Um, I'll pop a link in the chat in case anyone is interested to join that, um, and is new to Tableau.

49:46 Um, in terms of what to expect from us, we have our March, uh, Tableau user group planned. It'll be happening on the 24th of March at 6:00 PM.

49:57 Um, now back in September last year, we had a presentation from Miriam, and, uh, we got a lot of feedback, um, to say that people really enjoyed, um, seeing other people's dashboards and layouts because they can often be clunky, um, maybe take a while to, to develop and, um, to achieve that clarity. So our focus for March will be dashboard layouts, um, and, uh, some of the kind of tips and tricks and starting points that everyone can use, um, to make the journey a bit smoother.

50:29 We'll be joined by Ryan Gensel. He, um, worked at Apple as the head of data visualization. You might have seen his work in Dashboards that Deliver, um, more recently in The Big Book of Dashboards as well. Um, so it's gonna be a, a very fun, uh, data viz focused session all about layouts. I hope you can join us 24th of March at 6:00 PM, and the invite link will go out shortly after our session today.

50:57 That's all from me, Rowan.

50:58 Rowan Bradnum: Great. I think that's all from us. Thanks so much for coming along. Uh, glad you found us here on to Teams and, uh, we look forward to seeing you next March.

51:07 Next month in March.

51:08 Okay.

51:09 Miles Henderson: Thank you.

51:10 Bye.

51:10 Rowan Bradnum: Bye.

51:10 Sara Sekelj: Thanks, everyone.

51:11 Miles Henderson: Thank you.

51:11 Sara Sekelj: See you soon.

Leave a comment

Your email address will not be published. Required fields are marked *