I am FOR electronic databases!
I work in children's social care and I know the current frustrations around admin e.g. duplicating forms amongst siblings, duplicating ID reference numbers and dates of birth on the top of every single piece of paper you touch etc. The current paper based system isn't perfect either.
I know that electronic databases will ultimately lead to better outcomes for children in comparison to sticking with paper files and bespoke Microsoft word templates (especially when considering that paper files have to be kept for 75 years).
Electronic databases are a great tool for case management. However, as with any database (electronic or paper based), the design should be seen as the most important factor if it is to be usable by practitioners and not computer whiz kids. Read on, I'm sure you will agree.
I have seen many of the ICS products available. Unfortunately most of them have been very slow, clunky and unintuitive to a point where as a user I am disappointed and frustrated. Some typical experiences I have had that make electronic databases look bad include: -
* Having to wait more than 30 seconds for a page of information to load
* duplication! e.g. having to add the school at the contact stage, then again as an involvement, then again as a service only to be told the original start date isn't valid and you have to now navigate all over the show to untick a box before you can continue.
* Chronology not in chronological order (what’s that about?)
* Bad navigation e.g. "I'm sorry but that piece of information is in the CLA module, you can't save this page until you have been there to update the legal status... p.s. if you leave this page all of your work so far will be LOST... have a nice day"
* Having to repeat or copy and paste pieces of information from a contact, onto a referral, onto the initial, onto the core, onto the child’s plan etc. etc. etc. and then repeat the same for 4 siblings
I could go on...
These are not electronic database issues, these are fundamental database design flaws. If I had only ever driven a car that had no seats I would say that cars are a bad idea. However a car with seats in comparison is very useful. In this case I don’t have a problem with cars, but I do have a problem with bad car design! Remember a lot of the ICS designers/developers are not practitioners and the DCFS compliancy doesn’t include user satisfaction as scoring criteria against every compliancy e.g. you might be able to copy an assessment but how easy is it to actually do it from a users point of view and then navigate to update it on the sibling’s record. This is where ICS is having difficulty and practitioners are getting cheesed off.
In summary… keep an open mind about electronic databases before jumping on the "NO COMPUTERS" band wagon because there are some very good ones out there.
My most recent ICS experience was using a new system that is very very intuitive. It guided me through the processes as per the book (without me needing the book), promoted thinking outside of the box (e.g. outcome focused planning) and removed duplication allowing me more time for direct work. It is that easy to use that we have managed to progress a case to core without receiving any training what so ever. The system I am talking about is an absolute model of good database design and other providers could learn here about making a usable system that practitioners will embrace. It is like using a “TOMY - My first ICS product”
Thanks for reading