The narrative of a datix is so important. I am new to the patient safety manager role, so I have limited experience in dealing with the 'back end' of datix. From the small amount that I have seen - you get many (tonnes actually) that are no harm, and you can tell that 'I am going to datix you' type reports.
Datix may not be the best place to report these type of incidents - but where else can you log them?
When reading the narrative you can get a sense of what is going on and the theme of it - communication, frustration with current systems/processes. These reports should not be ignored as, if looked at and themed with others, tell a powerful story about what is happening in that area. It may highlight risk hot spots or a poor culture of speaking up in certain areas, it may be an indicator of a deeper problem at play.
Reporting systems are process driven. What you do with that information is not always process driven. The serious incidents are a process - but the no harm incidents often don't follow a process, so are often left aside.
These small, seemingly insignificant events with a narrative are important.
I am not sure what other patient safety managers do , but I am collecting the themes of all no harm events that happen in my directorates and will be looking at them on a monthly basis to spot trends and hotspots.
We have a process to capture incidents. This is not the problem. The problem is with what we are doing with the information captured. How we interpret the data, who we involve, how we feed back and how we share actions and how we change practice - this is the hard work. It is easy to complain about Datix or any other incident reporting system and its functionality - its not so easy to act on the information it is giving us.
As I mention, I am new to this area - 1 month in.
Naive? Possibly, wanting the best for patients and staff? Definitely