I would personally consider an opensource / free software over NO SOFTWARE any day of the week, particularly if this would take the grunt out of the work required.

In the grand scheme of things, the risk management committee would probbably rank this towards the bottom of their plethura of Trustwide problems, there would be I assume a legacy paper based system to fall back upon if it all goes pear shaped.

Many good databases have begun as a one man show, inluding EMAT I believe which has now grown to a fully fledged suite of programs and modules.

Single PC's running databases on a Trust network can be backed up by IT if using shared drive space. Most computers nowadays have limited hard drive space virtually all storage is on the remote server side. Data security and the data protection act are normally comfortably managed by IT folder permissions to remove public view, and by using patient numbers rather than names the documents are desensitised.

Some members of staff might develop or improve software in their own time just for the benefit of the organisation, particularly a small application like the library. I have been fortunate enouge not to loose members of staff to 'development projects' in the past, but I suspect a number of establishments may have.

I would not welcome general development of software during valuable NHS time, however I see that there are times and places for its use in the management of medical devices and improvement in throughput.

Software for example could be the spreadsheet containng automated macros and formula to carry out budget analysis, key performance indicators, work output trends which may be a requirement of the job. I would not pull out my abacus and calculator but I know it could be done that way.

if taken further, software could include a basic library package used to mirror a legacy paperwork system.

So my feelings are that we are paid to manage Medical equipment, but part of that management may be to embrace limited use or minor development of IT based systems (or files in excel / access) to improve efficiency.

I would not allow time to be invested on a project that would not yield at least a time saving and reasonable performance or compliance improvement. Its up to us to draw those lines and stick to them.

Today, I was happily working away on something else whilst msaccess carried out thousands of manual calculatons on our job records to generate key performance indicators for our quality system. There is always a fall back, but would I wish to fall back to it?

- Joe

Last edited by Joe Emmerson; 01/03/07 9:59 PM.