JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DATA-PROTECTION Archives


DATA-PROTECTION Archives

DATA-PROTECTION Archives


data-protection@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DATA-PROTECTION Home

DATA-PROTECTION Home

DATA-PROTECTION  2000

DATA-PROTECTION 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: PVP markers database

From:

David Fleming <[log in to unmask]>

Reply-To:

David Fleming <[log in to unmask]>

Date:

Fri, 24 Nov 2000 09:59:38 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (113 lines)

Excellent checklist, Ian.

One small point.   You talk about "a responsible, high-ranking 
officer".   Dangerous stuff.  Just because some is described so, it does 
not imply that he is being fair or lawful.  Whoever makes the decisions 
MUST do so fairly and lawfully, whoever he is.  If he is a council 
official, he must be empowered to do so, and must follow appropriate 
procedures.  Even Ministers of the Crown get it wrong sometimes (remember 
one Mr Howard, Home Secretary of recent memory).

Regards

David

At 04:11 23/11/00 -0500, [log in to unmask] wrote:
>Dear Nicola/Fiona/All
>
>Suggested PVP marker/database system, with references to Principles or
>legislation (sorry it's in a nutshell):
>
>Your policy to have such a database should be considered at a high level and
>approved by the data controller (P7) and procedures should be in writing
>(general).
>
>You should ensure the purpose for the database is properly notified to the
>ODPC (legal requirement, P2).
>
>Reports from staff or third parties about a person's violent tendancies or
>actual threats should be in writing (P1).  There may be other risks, such as
>aggressive family members, dogs, sexual threats, etc - the report should
>clearly spell out the actual risks to staff visiting or coming into contact
>with this person (P4).  Opinion and circumstancial evidence should be avoided
>if possible but if recorded these opinions should be marked as such, e.g. "X
>felt threatened, although no actual attack or threat took place" (P4).  The
>report writer should be informed that they may be asked to justify their
>evidence in court (P4).
>
>Any witnesses should be asked to support the accusations in writing (P4).
>
>Any CCTV cameras in place for staff security should be clearly signed as to
>the identity of the data controller and the purposes for data collection,
>e.g. "CCTV in operation for security purposes" (P1).
>
>Where it would not be likely to cause harm to any individual, the data
>subject should be contacted to allow them to put their side of the story (P1,
>P4, HRA).
>
>The decision on whether to add the person to the database should be made by a
>responsible, high-ranking officer who should make the based on all the
>information available (P1, P3, P7).
>
>If the decision is made that the person is to be added to the database the
>data subject should be informed unless there is a substantial risk to any
>person in doing this (P1, P6).  The reasons for inclusion should be recorded
>(P4, P6, HRA).
>
>An independent appeals procedure should exist to challenge this decision (P6,
>HRA).
>
>The database should only be accessible on a case by case basis when an
>officer is making a home visit or the data subject is making a visit (P7).
>
>If you need to protect staff on front desks against all attacks (not just
>those on a database) then other methods should be used (screens, CCTV,
>security staff, etc).  It may also be an idea to have a sign up saying that
>as a responsible employer you will assist any staff to prosecute their
>attackers (H&S).
>
>All accesses of the database should be properly authorised (by the nominated
>officer) in advance (P2, P7) and the access should be properly logged (audit
>trails, written reasons for access) (P2, P7).
>
>There should be sufficient information on the record for the officer to make
>a reasoned judgement on the risk involved and not too much information for
>the particular purpose (P3).
>
>The database should be regularly updated to reflect any changes in the data
>accuracy such as address changes, decision to remove after apology, further
>evidence of violence, etc (P4).
>
>There should be a review procedure and each record should have a review date
>when an assessment should be made as to whether the risk from this individual
>is still present (P4, P5, P6).  If the risk is not there the entry should be
>removed from the database by the authorised officer (P5, P6, P7).
>
>The data should never need to be transferred outside the EEA but if it is you
>should ensure the recipient country has adequate DP law or you should have
>the person's informed consent (P8).
>
>There may be more to this issue but the above should give you a start.
>
>Ian B
>MD
>Keep IT Legal Ltd
>
>Please Note: The information contained in this document does not replace or
>negate the need for proper legal advice and/or representation. It is
>essential that you do not rely upon any advice given without contacting your
>solicitor.  If you need further explanation of any points raised please
>contact Keep I.T. Legal Ltd at the address below:
>
>55 Curbar Curve
>Inkersall, Chesterfield
>Derbyshire  S43 3HP
>(Reg 3822335)
>Tel: 01246 473999
>Fax: 01246 470742
>E-mail: [log in to unmask]



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager