How can we enable Wales Audit Office staff to make better use of data? Dyfrig Williams reflects on learning from our Cutting Edge Health Audit prototype.
In my work on the Cutting Edge Audit project, I’ve been looking at how we can bring together data from public bodies in a way that’s open to everyone and easy to access so that we can get further insight as auditors. The Health Team at the Wales Audit Office kindly volunteered to work with us so that we could look at what this might mean in practice.
In order to develop the parameters for the work, I developed personas for staff in various roles so that we could be better informed about what work we needed to undertake. This really helped us to identify how research time is used and who is doing that research.
The feedback that I received was that data is difficult to access, so we’ve developed a prototype to bring useful health data and information together in one place.
Our initial attempt to bring this data together in one place is very much a proof of concept to see how this could be progressed further. Our initial thinking was to try and create a data one-stop shop for each health board, as well as a page for national work that covers the whole of Wales or the UK. When we thought about what a functioning prototype might look like, we decided to use a national site as our test.
We initially decided to use Sharepoint Online because it gave us the opportunity to look at how we could develop our use of the service to make data more accessible internally. Unfortunately whilst this worked as an initial test, we could only make the site available to a selected number of users, as we’re currently testing it with a small user group. We really wanted to share the results throughout the organisation so that staff could think about whether this type of approach would be useful in their work, so we decided to host the information on our intranet (The Hub), which is a Drupal site.
We used feedback from the Performance Support Officer to bring together information feeds in order to save research time. We created widgets from RSS feeds (Really Simple Syndication feeds, which deliver regularly changing web content from news sites, blogs and other online publishers) where available. We also generated our own widget (a small application that can be installed within a web page) for a Twitter feed that we generated from a Good Practice Exchange Twitter list. We embedded these feeds as IFrames within the site.
Making data more user friendly
We wanted to make data easier to understand and use. There was a strong feeling from the staff that I interviewed that knowledge and understanding of data shouldn’t be siloed, so we looked at how we could make data more accessible.
We decided to use Microsoft’s Power BI (a suite of business analytics tools to develop insight) to make health data sets more accessible and easy to understand. This meant that we didn’t have to buy any software, and that we could host the data directly through the Power BI service. We didn’t use any sensitive data for our test so it wasn’t a problem to publish it directly to the web. There was mixed feedback from staff that I interviewed as to whether the site should include private data, so we will need to look at our options again should we choose to go down this route.
The data sets that we used are publicly available and use APIs (Application Programming Interfaces, which access the features or data of an operating system, application, or other web service). This means that the Power BI data tools are linked directly to StatsWales for the data so that there’s no manual downloading of data after its set up. It also means that we’re always using the most current data that’s available.
Where do we go from here?
The use of our prototype has now been developed and extended so that it can be used as a data tool for a Primary Care project in health so that colleagues can use it to analyse data for their own Health Board, so it’s great to know that the work has already been of practical value.
Our use of widgets and APIs mean that the amount of work needed to maintain the current information that the site holds is very limited. However, if we want to develop the data that it holds, we need to think about who might be responsible for its upkeep, should it be seen as valuable.
The next step for us as an organisation is to use the personas that we generated, as well as informal feedback from this work, to look at what an effective data site and service might look like, and how that might be adapted for other parts of the organisation. That will enable us to learn from any mistakes that we’ve made so that we do things differently in the future, and also to build on our successes. And if we can build on that learning, we’ll be well placed to develop our work in order to be the cutting edge audit office that we aspire to be.