ASSIST

ASSIST is a project being run by Hugh Gallagher ( Hugh.Gallagher@esth.nhs.uk ). The gist is that a new SQL database is installed at a unit and a feed of creatinine results is setup from the lab system. Software produced by the project analyses the results and produces a graph showing their current/predicted deterioration in kidney function. Staff in the labs are funded by the project to review the graphs and to suggest referral to the renal unit if appropriate. The theory is that this will result in earlier referral of patients with deteriorating kidney function and hence better outcomes. The interfaces were built by Paul Copping ( paul.copping@blueyonder.co.uk ) with the exception of St. Hellier who have built something themselves.

The data about who has been the subject of a graph and what decision was made is to be sent to the UKRR for analysis.

See https://assist-ckd.org/demo/software/

 

I (George) was asked to look at this when they were having delays getting permission to install databases and lab links setup. My suggestion was to build the feature on top of the LIMS/ICE directly and had some brief discussions with those suppliers about this. The project decided to stick with their current approach but this could be revisited if the project was to be expanded to other sites.

Systems Team Involvement

Some of these files are sent via SFTP (only Epsom at the moment). The files are uploaded to the N3 SFTP server /data/assist/uploads/  typically on the 1st of the month. These files are downloaded by rr-storage-live daily at 2.00 am to K:\workrequest/externdata/WR373 assist-CKD RCT the SASCode drive. Anna Casula then analyses the files. Most files are sent by email.

There are sensu monitors in place to monitor uploads and transfers due to some of the uploads not always triggering the transfer process probably because of the upload software used. A simple touch of the file in the upload folder will trigger the process.

JIRA

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.