11.09.2017 Views

RiskUKSeptember2017

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Lone Worker Security and Safety<br />

worn video’s deployment to be based on<br />

legitimate reasons, particularly in terms of<br />

undertaking a privacy impact assessment.<br />

Deployment scenarios<br />

At the core of BS 8593 is an implicit<br />

understanding that there are four different<br />

deployment scenarios, any one of which might<br />

be appropriate to an organisation seeking to<br />

deploy body-worn video. Each scenario<br />

considers how a body-worn video device shares<br />

and stores its data.<br />

Capturing evidence from body-worn video<br />

devices deployed on members of staff, and<br />

notably those working alone and/or out in the<br />

community, brings with it many other unique<br />

challenges. What if audio is recorded? What if<br />

other, non-incident related individuals are<br />

captured in the video? Is a recording allowed if<br />

it happens in someone’s home or on private<br />

property? These and many other questions will<br />

start to arise – and demand answers – as more<br />

and more deployment scenarios occur.<br />

Current body-worn video solutions tend to<br />

record video and store footage locally to the<br />

body-worn device. That data is then extracted<br />

from the device at a later point in time, typically<br />

to a docking station, by way of the removal of<br />

an SD card or by using a secure Wi-Fi<br />

connection to the employer’s network.<br />

In this current scenario, it’s evident that while<br />

useful visual evidence has been captured, its<br />

use can only occur at a later point in time and<br />

after any actual risk incident has passed. That<br />

being so, to deploy a current body-worn style<br />

device for a lone worker simply wouldn’t help<br />

with ensuring an immediate escalation in the<br />

event of an incident.<br />

Moving to a scenario where the video’s<br />

streamed in real-time via an appropriate<br />

cellular connection clearly provides an<br />

advantage in that it can be used immediately<br />

during an incident. It also helps benefit the<br />

operator based in an Alarm Receiving Centre<br />

(ARC) or Control Room in that they’re far more<br />

likely to be able to ascertain on a swifter basis<br />

the nature and severity of the episode, all of<br />

which further helps with the speed of incident<br />

management and ensures that low level or false<br />

alarm incidents are not passed to the police.<br />

Data protection issues<br />

The current scenario of recording locally to the<br />

body-worn video device brings with it some<br />

significant data protection challenges if, for<br />

example, the lone worker has an ability to view<br />

or replay the recordings made on the device,<br />

and specifically if non-incident related<br />

personal data is captured on that recording.<br />

To date, the majority of deployments of bodyworn<br />

video devices have involved police<br />

officers: individual workers who are honest,<br />

upstanding and able to follow instruction,<br />

process and rules. Even then there have been<br />

incidents whereby body-worn devices have<br />

been removed and stolen by assailants, thus<br />

introducing the potential for data breaches.<br />

If body-worn video devices are to become<br />

commonplace for other lone workers (ie those<br />

who are not police officers), then ensuring that<br />

those devices and their retained video data<br />

remain intact and are used correctly becomes a<br />

challenge for the employer. Moving to a model<br />

whereby the video is streamed live and not<br />

stored locally on the device will help in<br />

ensuring that all employers stick to the GDPR.<br />

One final observation for those employers of<br />

lone workers hoping to use video for when risks<br />

occur during engagement with clients, patients<br />

or service users in their own homes. The<br />

employer will need to make absolutely sure<br />

that there are very clear policy guidelines in<br />

place for those workers if and when they need<br />

to use video to record an incident. Recording<br />

needs to be warranted and the owner/occupier<br />

of the property pre-notified that recording<br />

could occur and under what scenarios.<br />

There must be an open book approach with<br />

clients/patients/service users that such<br />

technology is being used to ensure the safety<br />

of staff members entering personal property. If<br />

a recording occurs which is warranted then it<br />

must be clear to the recorded party that such<br />

recordings will be deleted and details given in<br />

terms of the timeframe for this procedure.<br />

Equally, if recordings are warranted –<br />

because an incident has occurred that causes<br />

concern for the safety of the worker – then it<br />

should be clearly noted that recording is taking<br />

place. Any non-incident related personal data<br />

captured as an aside must be redacted before<br />

that video is used or shared by the employer.<br />

Companies wishing to supply body-worn<br />

video systems need to be investing now in their<br />

ARCs, processes and personnel in order to<br />

ensure they’re better placed to assist their end<br />

user customers in making certain that video<br />

data is perfectly safe. They also need to be<br />

working to ensure that, if a body-worn video<br />

user’s personal safety is at risk, escalation of<br />

the incident in terms of summoning assistance<br />

is the fastest and most effective route possible.<br />

Craig Swallow: Managing<br />

Director of SoloProtect<br />

“The new British Standard 8593 was drawn up to address a<br />

gap in guidance due to the differences between the use of<br />

CCTV and body-worn video”<br />

31<br />

www.risk-uk.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!