Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Description

Every month AKI Lab submission completion report is put online. RAG stands for Red/Amber/Green. This report looks at the lab submissions and reports back how much missing data they do not submit.

  • Red - when more than 5% of all entries for the month are missing all of the following fields: nhs number, date of birth, gender and post code.
  • Amber - when more than 5% of all entries for the month are missing one or more, but not all of those four fields mentioned with Red.
  • Green is when all four fields are present on 95% or more of all entries for the month.

Report is triggered by email from one of the Data managers (atm mostly from NH/SE) asking to run the report and giving the path to locked AKI progress excel spreadsheet.

Preparation

  • Clone aki_validation repository
  • Create a Python 3.6 venv
  • Install all the requirements
  • run scripts/akiload.py script.

The above steps are required because the build on the R drive has not yet been updated to include the RAG Report.

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Running

Click on the Menu Item "Generate RAG Report" under the "Utils" menu.

That will produce the excel file which needs to be sent back to asking data manager. Normally, just put somewhere under Q:\AKI folder and send back a path to it.

If any of the cells from column 13 onwards (the date ones) aren't actually blank but instead contain spaces the process will crash. There is a ticket Unable to locate Jira server for this macro. It may be due to Application Link configuration. about handling this better. For now you will probably need to use Print statements to find it.

Technical notes

In general, data managers could do this themselves, however the script is a bit fragile and it is not currently released. One assumption it does, that the report needs to be run for "current month - 2". Meaning, that if I run it, for example, on 2nd of May, it will make report for all months up to and including March. Given that I (RK) had no problems running it for more than half a year, it is probably safe to release and allow data managers to run it.

Updates

Sometimes data managers asks to modify/add/remove which lab is submitting for which data. There are two mappings at the top of aki/report.py script. Both need to be modified at the same time, SUBMITTED_BY defines "lab that is not submitting": "lab which is submitting for it", and ALSO_SUBMITS_FOR defines: "lab that is submitting for": [list of labs that the key part is submitting data for].

  • No labels