The latest version of ASSIST-CKD (v4.4.3) software was developed with usability and performance in mind. eGFR graphs were overhauled with more consistent axes and better zooming and panning functionality, and under the hood, tweaks were made to graph creation and patient retrieval to increase the application’s overall speed.
However, there’s an aspect of ASSIST-CKD performance which can’t be solved by the application – that is, the performance of the database.
As more and more data is uploaded in reporting runs, the database can become sluggish and slow down the application’s reporting screens. This is frustrating, but it can be solved by rebuilding and reorganising the CKD database – or by rebuilding its indexes – on a regular basis.
A database administrator can set up an automatic scheduled task to perform these types of operations once a week (or, more successfully, coinciding with your site’s data upload schedule). This type of ongoing maintenance will help to ensure that things run smoothly in the long term.
To give you an idea of a performance increase, Mr Nick Whitmarsh (BCUHB – Informatics, Wales NHS) ran some tests, populating only the Start and End date fields in a query.
As you can see from the table above, a database rebuild has significantly improved the application performance – something to keep in mind moving forwards.