 Hello, thank you for joining us for this talk about the Prisma 2020 Flow Diagram app and the significant updates that have been made over the past year. My name's Chris Pritchard, I'm the current maintainer of the app and I'm a senior lecturer in paramedic practice and emergency care in the Institute of Health and Allied Professions at Nottingham Trent University. My colleague Neil Hadaway, who is the founder and organiser of EsmerConf, has also been a great help with this presentation and was the previous maintainer of the package. In addition to myself and Neil, Luke McGinnis did a lot of work at the start in turning a lot of the concepts into reality and we've also had some additional contributions this year from Hosam Hamadi who works for Rayan and they wanted to implement a function to enable the app to be called directly from within Rayan so they did so and contributed the code back to our community and also to Brennan Chapman who contributed a feature to enable the app to work with tibbles as well as data frames. So what is the app for? Well, the Prisma reporting standards were updated in 2020 as I'm sure you're all aware but within that updated set of standards there was an updated flow diagram to aid in the reporting and visualisation and reviews and I think they're really important in making it clear where articles were identified and which stage in the process they were excluded or reached inclusion. The reporting standards when they're in their update contain a bit more information than in previous versions of the Prisma statement and that made the flow diagram a bit more complex and even before the 2020 update they could be quite time consuming to create so no one's idea of fun is sitting around trying to move text boxes on a word processor but that was often what was needed was some quite fiddly work. So this app was born. So it provides an R package so you can use it directly from within R but also as a hosted shiny app that requires no coding knowledge whatsoever to enable these flow diagrams to be generated and created and then exported in the function in interactive HTML so you can use click on links to take you to other parts of a review but also in PNG SVG and PDF formats for example. In order to actually populate the flow diagram you can enter values directly within the web app or pass them to the functions themselves. You can use a provided template CSV or and this is new for this year. You can call the app directly with some URL parameters to complete the auto fill some of the boxes. So over the past year we've made some significant updates. So there was a big code cleanup last summer and the automatic calculation of node positions is now part of the app so instead of relying on manually calculated and entered values for where each box goes they're calculated relative to each other. This was really needed because otherwise we couldn't move on to the next thing which is conformity to the Prisma extension so for additional reporting standards for the literature search part of your review by being able to include specific databases or registers as you can see from the image in the top left and also then this addition of URL parameters which enable the app to be embedded more easily within other tools. As I said Rayan built this into the premium version of their product and then contributed the code back to the community. So within the code cleanup this was done because the code was a bit difficult to read so lots of functions were perhaps all on one line which made them a bit harder to deal with but also had hard coded figures for example for box heights and box positions variable names that weren't always clear and also lacking comments in places so the code was very functional it did what we wanted it to do but didn't really allow for extensibility and building on that to build in new features. So as such a code review took place so I used Visual Studio code and a package called lintar to really support with that so was able to sort of analyse the source code files and work out what was needed to make them more readable and more consistent. But also within that code review was able to replace hard coded numbers and values with ratios and variables so boxes are positioned relative to each other instead so that's the Prisma getPOS function that enables us to do that and we're also able to programmatically alter the height of a box depending on the number of lines of text in them which again is really useful because it makes it easier to add new nodes to the package. So if for example a new updated set of guidelines was released that required reporting of additional information that would now be easier to add into this package than it was before. That moves us on to talking about the Prisma S conformity so the Prisma S extension is specifically for reporting the literature search part of your review and I'd encourage everyone who's writing up a systematic review to absolutely follow those but they require the number of records retrieved from each individual database or register. So as you can see we now have a way of doing that both through the R package and the template CSV but also from the website so you can see here we've got each database separated by semicolons and that creates a nice straightforward easy to use package. So that's great and finally we can now pre-populate fields in the Shiny app via URL parameters and I'll talk more about that in the tutorial that I'm going to produce in terms of how that actually works but the real valuable and exciting thing about this is it means it can be integrated much more easily within other tools and packages and any numeric field within the CSV file can be passed as a pre-populated field and I would like to work on passing the non-numeric field so for example those specific databases and registers I'd like to work on passing them as values in the near future but for now it supports any numeric field within the CSV file and finally I'd like to talk a little bit about you know what the reach of this package is and the impact so within the hosted version on the Shiny apps.io we use some analytics they're just aggregated statistics rather than any personally identifiable information but we can see that this has been accessed globally and in the last 90 days for example over 18,000 unique visitors to the site so it's a big tool it's being used by lots of people and in part that's because it's recommended on the Prisma statement website it's part of the editorial guidelines for journal submission in some journals including BMJ evidence-based practice but I think the big thing is because it's useful and I just want to say thank you to all of our users because if it wasn't used this much then we wouldn't put the work into making it better so I just want to say yeah again a big thank you for that so thank you for listening to this talk as I said my name is Chris Pritchard I'm more than happy to take questions of our master's on or Twitter and thank you once again for watching