"We cover news and updates from the digital world with information on the latest legislation, high profile cases and changes in the online industry."
We specialise in representing victims for data breach compensation claims.
Information on how we handle your data is available in our Privacy Policy.
We can represent victims for NHS cybersecurity claims. We can offer No Win, No Fee representation, which is important in today’s increasingly digitalised age.
The NHS is a huge target for hackers given that they do not always have the resources in place to be able to fend off attacks. As we saw with the 2017 WannaCry incident where malware specifically targeted older and more outdated systems, the NHS was hit hard.
Victims should never suffer in silence. We fight for the rights of victims for NHS data breach compensation claims that arise from cybersecurity problems.
When there has been an incident of the inappropriate access to medical records that belong to you, you could be entitled to make a claim for compensation with us on a No Win, No Fee basis.
This is a type of case that we deal with commonly. One of the group actions we’re also representing people for is for the Greater Manchester incident where mass snooping was identified.
For the victims, this kind of misuse of personal and sensitive information can be devastating. This can especially be the case when the person who has accessed the information knows the victim, which is commonly the case.
If you’re one of the 2,000 or so Greater Manchester NHS patients whose medical records have been accessed inappropriately, you may be entitled to make a claim for NHS data breach compensation.
The Wrightington, Wigan and Leigh NHS Foundation Trust has written to patients affected by this scandal. An investigation that followed a complaint revealed that thousands of people’s medical records had been accessed by a number of NHS employees without need or authority to do so.
Across an 18-month period, some records had been subject to a single access event, whereas others had been accessed on a number of occasions. It’s yet to be confirmed which staff are responsible for the access events as well.
A 12-month suspension has been handed to a senior nurse caught snooping on medical records during the course of her employment with University Hospitals Coventry and Warwickshire NHS Trust.
It’s understood that a total of 13 charges were brought against Carol Ann Rodda who was found to have been improperly accessing records over a period of nine months. The data she accessed included that of family members and colleagues.
The Information Commissioner’s Office (ICO) has had to deal with a number of cases where healthcare staff have been caught snooping on medical records. It can be a common problem, and it’s one where the victims can be entitled to make a claim for data breach compensation.
An NHS Trust in Blackpool was fined £185,000 when confidential details of staff members were posted online. On top of the breach itself, The Trust also failed to take proper action on the data breach for almost a year.
The information that was posted online by The Trust included names, birth dates, and national insurance numbers, along with other information like sexual orientation, ethnicity, religious beliefs, and pay scales. The information that was posted was of 6,574 both past and present employees.
Read More
A data sharing project called “care.data” was a scheme that allowed GP and hospital data to be stored and shared within the NHS, and possibly with third parties as well. It was supposed to launch in 2014 but has been heavily delayed due to privacy concerns.
Now, the project is being terminated all together, thanks to the Department of Health in England.
So, with all the NHS breaches and leaks – with medical breaches still being far ahead of the tables in terms of breaches by sector – is this a good thing? Have we just dodged a huge data breach bullet?
Read More
Speak to our team now for help and advice.
Fill out our quick claim form below and we’ll contact
you when you’re ready to talk to us.
All fields marked * are required.