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: Ethnic Origin Collection

From:

"Dave Wyatt" <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Sat, 12 Feb 2000 20:06:16 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (99 lines)

As Racial Ethnic Origin data is defined as a sensitive data catagory in part
1 Section 2 of the Act then principle 1 requires processing conditions to be
met. In addition to both lawful and fair processing.

Sensitive data processing requires both a schedule 2 and schedule 3
condition to be fufilled.

I would be interested in which conditions one from schedule 2 and one from
schedule 3 are to be argued where a patient does not give or withdraws
consent to the 'processing' of any Racial or Ethnic origin data. Clearly one
way individuals tend to protect themselves from potential misuse of data is
not to supply such data or supply incorrect data.

Schedule 3 has a variety of conditions which may apply to such data but the
tests are reasonably strict and have to be set in the context of the persons
processing and appropriate statutes .

a) Schedule 3  Section 2 links the processing as necessary for employment
law

b) Schedule 3  Section 3 links to life threatening circumstances where
consent cannot be obtained

c) Schedule 3  Section 8 links to medical purposes by a health professional
or equivalent and required for medical research if this is the argued use.
Note that  medical research was not referenced in the directive (See Article
8 Sub Section 3) and appears to be an addition by the UK government in
transposing the Act (some say unlawfully).  This I believe leaves any
processing justified by this activity open to challenge by individuals by
reference to the underlying directive.

d) Schedule 3  Section 9 Necessary for equality to be maintained but must be
processed with appropriate safeguards. Secretary of state can define the
limits of appropriate safeguards by Order.

e) Schedule 3 Section 10 processing where defined in a seperate order.

In the DOH example
Which processing condition in schedule 2 and 3 are to be argued?
Will all NHS offices without central guidance argue these consistently?
Is the data retained after passing to the DOH? If so what is its registered
purpose and the justification that it is being retained no longer than is
necesary for its purpose?

If the only reason for any processing is because a body is obliged by
statute to collect on behalf a person who is authorised by statute to hold
such data, and they have no reason of their own to collect, then are they
only a processor. (A person only becomes a controller under the DPA 98 if
they control both the purpose and the manner of processing).

To work these thing out an understanding of the legal status of persons in
the processing chain is required and their relationship to each other. No
easy task for either the persons collecting or the data subject who may feel
a breach is occuring in processing without consent.

Id be interested in any views posted?

Dave Wyatt

----- Original Message -----
From: <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, February 08, 2000 9:09 AM
Subject: Re: Ethnic Origin Collection


> Comments received are as  I expected.  However, I only asked the
> question since I have been passed some documentation which are comments
> derived from the NHS Management Executive letter (dated 25 Oct 93),
> which states this:
> Breaching the Data Protection Principles
> The Unit would need to ensure that the following data protection
> principles are not breached;
> First principle: Information should be obtained fairly i.e. patients
> should be given notice of the uses and disclosures of their personal
> data (A small section in the patients handbook informs the patient of
> access to that information but not on it uses and disclosures)
> Fourth principle: Information held on that patient should be sufficient
> and not more than sufficient for the purpose for which the data is
> held.  Holding information in relation to ethnic origin as part of the
> CMDS (or CDS) must be justified in terms of the use the Unit will or
> intends to make of it.  The Unit will be breaking the Data Protection
> Act by collecting ethnic origin solely because it forms part of the CMDS
> (CDS).
> I have no problems in collecting the data, I do not want to be awkward.
> However,  I do not want to find that the Trust has to stand alone if
> there is a complaint.
>
> Su Clarke
> Glenfield Hospitals
> Leicester
>
>
>



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

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