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:

Fw: Re[2]: YOT query - Fit for purpose.

From:

"Ian Welton" <[log in to unmask]>

Reply-To:

Ian Welton

Date:

Sat, 14 Oct 2000 21:02:15 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (150 lines)

> From: "Roger Cook" <[log in to unmask]>
> Sent: Friday, October 13, 2000 2:23 PM
> Subject: Re[2]: YOT query
>
> >  I'm not sure whether it's me or the rest of the correspondents on this
> >  subject who are missing the point.
> >  Consider what is meant by "disclosure".  In the example quoted, the
> >  assumption seems to be that the disclosure will be the whole of the
case
> >  history including the court appearance and sentence (assuming guilt).
If
> >  such an example arose, the appropriate response would be to consider
what
> >  might be the minimal amount of data that could reasonably be disclosed.
> >  Note the use of the legal term "reasonable".
> >  Perhaps I an can draw an analogy here.  We keep a computer data base
> about
> >  individuals who might pose a threat to a Council employee or Member.
> That
> >  threat might arise from any number of causes.  The data is kept by the
> H&S
> >  Officer and is highly confidential.  The procedure is that if a member
of
> >  staff is at all concerned about making a home visit, they call the H&S
> >  Officer and quote an address.  His response to the query is limited to
a
> >  simple statement of the risk element, e.g. "advise single females not
to
> >  visit".  The reason why this risk assessment has been made is not
> >  disclosed.  The householder might simply be a misogynist or he could be
a
> >  multiple rapist. The point is that the risk has been assessed and a
> >  measures and appropriate response given.  This is "reasonable" in the
> >  context of the whole transaction.
> >  To come back to the school example, they could be told by the YOTS team
> >  that handling money might be problematic without telling the school
that
> >  their pupil has be done for a bank hold-up!  Similarly, YOTS could
advise
> >  against working in a APH if the pupil had been mugging old ladies.  In
> >  neither case does the school know anything more than is strictly
> necessary
> >  and the pupil's rights have not been infringed.  Not only that but the
> >  YOTS team has carried out its responsibilities to the pupil and to the
> >  community at large.

----- Original Message -----
From: "Ian Welton" <[log in to unmask]>
Sent: Saturday, October 14, 2000 1:55 PM
Subject: Re: Re[2]: YOT query

> Data which is adequate relevant and not excessive for the purpose it is
> provided, with a use known by the data subject, clearly supporting both
> sides of the public v private divide.  Sounds a good data protection fix.
> Timing and accuracy will also be important in such disclosures.
> Consider :
> Young female receiving malicious, sexually explicit and upsetting phone
> calls at home from what sounds like young child.  Calls continue over a
> period of time.  Caller deals in same manner with mother of the house
being
> called.
> Premises phone calls originate from traced.  Proof of individual who
> originated not yet available.  Some information known but disclosure not
yet
> possible to the victim or the victims school.  Victim demanding
information,
> school wanting information.
> Premises phone calls originate from could be home address of offender,
> address of friend of offender, or some other premises the offender has
> access to.
> Only such disclosure as is necessary in order not to significantly
prejudice
> the apprehension and prosecution of the offender, or prevention and
> detection of crime may take place.  That information  will not be all of
the
> file but only that which is necessary to disclose in order not to
> significantly prejudice...
> Timing and accuracy, as well as adequacy, relevance and excessivness are
> dealt with in this situation.
> As Roger intimates above is it not necessary to remove the emotional
values
> from all those involved in the situation as a means of reaching a robustly
> defendable and DP compliant answer?

=

The discussions above, together with KITLegals contribution 14/10/00 08:11
a.m. have firmed out a thought on this. (Apologies for using your e-mail
address in the same way as a name Ian, but to use Ian would just confuse
matters - Ian)

Are we not all actually discussing the wrong issue.
Is the real issue not Principles 3 and 4 but more a matter of Principles 1
and 2.

In the example Roger gives data is collected by a council in an attempt to
assure the Health and Safety (H&S) of its employees.
In the example given by myself data is collected by a police officer during
the investigation of an alleged crime.
The points that KITLegal makes relate to adequacy for purpose.

When attempts to exchange data between different purposes occurs, will
misinterpretations of what that data indicates not always exist?
At a simple level is that not what happens when facts in one area turn up as
misleading gossip in another.

The DPA's have both attempted to deal with this matter by relating the
collection and use of data to a purpose.  The DPA 1998 may even eventually
extend this by the wording of Principle 6 and the impact of the HRA.

Taking it as given that all organisations maintain their warnings on
addresses and individuals to the level that the credit reference industry
do, and that their data are fully fit for the purpose the data is collected
for, is it not possible that some of the conflicts and tensions created when
requests for data exchange or disclosure arise, is as a result of the
different interpretations and differing needs at the point of collection?

Is the individual who has assaulted a police officer in the process of
resisting arrest likely to assault a welfare worker who is attempting to
arrange benefits or other welcome help?
Is a person at an address from which a malicious phone call was made the
person who made that call?
Is the adequacy of information held by the a none legal organisation always
sound enough to support a criminal prosecution?

All organisations can potentially, in many circumstances, disclose
information quite lawfully under the DPA to other organisations and persons
using the data for the same purpose, but we can probably all identify times
when it would be wrong to the data subject to do so.

When to disclose appears to be the important element, that time may well
only be "when, or if the data is fit, for the purpose, and the context, it
is requested."

Hope that is clear.

Have I gone of at a tangent?
Does it explain some of the difficulties we all experience, or is it just
more mud?


Ian






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

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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