Desired Outcome

We consider here the possible remedy of a matter concerning  primarily the disclosure of F’s HIV+ status, without his knowledge/consent, whilst RBKC were in NO way compelled/ordered to do so.

It must be remembered at all times, that there  is NO documentary evidence that an official complaint or a legal case  were ever brought against anyone, for the serious breach of CONFIDENTIALITY, Statutory Restrictions on data handling and Article 8 of the Human Rights Act, for the disclosure of individual’s  HIV+ status without his consent.  It is without  a PRECEDENT.  It is UNIQUE.

Taking into consideration all of the contributing elements of this saga, it is clear that RBKC chose to ignore with impunity,  not only a raft of  guidelines relating to the processing of individual’s personal data,  conduct of assessments for social care, but also important pieces of legislation.  This is addressed in some detail on the relevant pages of this Blog.

Surprising to some may be that a line  of text, appearing  as innocuous  words, could have turned out to have such a serious effect on the matter and be a “trigger” for subsequent actions by F.  A line in a signature block used by undefined number of Social Workers, contained the words “Physical Disabilities and HIV Team“,  Every time this was used, it inferred  that the individual named in the email,  may be Physically Disabled, but most importantly, have some dealings with the HIV Team.  This is a blatant breach of basic Confidentiality, Statutory Restriction on data handling and Article 8 of the Human Rights Act.  Looking at this event in the context of the Soho HIV Clinic incident in September 2015,  this inference may have caused unwarranted anxiety and distress to undefined number of individuals, whose name may have been used in these emails during 2008.

RBKC’s claim that they were  not made aware by anyone of this problem, may be true.  However, it would be unlikely for RBKC to admit this and not having done anything about it until F’s complaint.  It is quite possible that some individuals were aware of this  blatant breach, but chose not complain, for  fear of dragging their identity into the “spotlight” and perhaps getting involved. 

Dr Zohra in her recent, confused and perhaps intentionally, confusing  intervention to resolve the impasse, claimed that the LGO’s Request for F’s information was treated as a “routine request”. This statement in itself is an admission that she does not know what she is talking about.   Routine as a what?   Pesky traffic fine, unwelcome Planning decisions, or oher routine infraction of local rules?

Far from this erroneous assumption.  There is NOTHING ROUTINE  about this  Request.  Any Request for information from “service users” file, held by their Social Worker, is deemed to be CONFIDENTIAL, and must be treated as such.  This of course includes access to information.  This must be restricted ONLY to those who are involved in F’s care, which in fact is NOT a single person in RBKC. as addressed elsewhere.

RBKC told HCPC that there was a “formal request” for F’s information, which rendered F’s Social Worker impotent from preventing access to F’s file.

Until  14th January 2013,  when F received Ms Maclean’s justification for the disclosure, claiming that it had to happen, in order to preserve RBKC’s REPUTATION,  F assumed that the disclosure  of his HIV status was a result of a mistake, poor understanding of the matter and more importantly, inability/unwillingness  to consult relevant guidelines, or seek proper advice.  It is clear that the nameless, faceless  RBKC clerk,  indiscriminately culled whatever information he/she felt fit, or perhaps of “interest”. 

Surprisingly, NONE of the 146 documents  provided answers to F’s allegations of non-compliance with  DHSC Guidelines, all local authorities MUST comply with.  Unsurprisingly,  the LGO conveniently  failed to ask RBKC for this justification.  Merely, a  Request was made for  a copy of F’s “assessment documents”, which provided NO answers for the  dereliction in compliance.

Ms Maclean’s statement  could be regarded as a “trigger” in F’s increased concern, anxiety and unwelcome distress, realising that RBKC were aware of this mistake all along.   To  this date they have NOT provided a justification for anything – simply unable to do so.

F suffered unnecessary concerns, anxiety and distress, as addressed  on the deterioration of health page.  This must be taken into consideration when contemplating any retribution and/or compensation.

In respect of: the

Assessment for Adult Social Care, RBKC  have been unable to provide a credible evidence that F’s October 2010 Assessment for Social Care was conducted in accordance with the DHSC Guidelines and  provide  VERIFIED and SIGNED Assessment document by F,  confirming  that the assessment had actually taken place and the assessment form submitted to the LGO, was actually used.  As it stands, the UNSIGNED Assessment document could have been and perhaps was, completed by whomever, wherever and whenever, scoring the answers in such a way, to arrive at a predetermined outcome –  and to deprive F of  RBKC’s contributions towards the cost of his domestic help.  The document, as it stands, has NO legal worth and should NOT have been used in any decision making process.  F conducted some research  regarding the legal requirement to sign documents. The only written comment he received was from well known legal authority on HIV/AIDS legislation.

  1. Therefore, RBKC’s contributions should be re-instated  from the date they  were stopped  in January 2011, to current date.   It should be paid as not requiring any accounting for it, in a lump sum.
  2. F should be paid a SUBSTANTIAL COMPENSATION for breach of CONFIDENTIALITY,  STATUTORY RESTRICTIONS ON DATA HANDLING, PARAGRAPH 10 OF THE DPA, ARTICLE 8 OF THE HUMAN RIGHTS ACT and other relevant REGULATIONS, CODES OF PRACTICE AND GUIDELINES, RBKC are obliged to follow as a provider of Social Care and the Controller or Fs CONFIDENTIAL INFORMATION.  In the process causing F substantial distress, anxiety and damage to his general health, wellbeing, quality of life, as described on the Deterioration of Health page.

Consideration should also be made of the fact that  there is no evidence that neither of these events have occurred in the past.  They are unique, without  a PRECEDENT.  Especially, in respect of the disclosure of F’s HIV related information.  This is not to say, that disclosure did not occur.   The perpetrators  had enough sense and decency to ameliorate the consequences by attending to it without any undue delay,  illustrated  as recently as 2015 in the Soho HIV Clinic case.   

In this case, the ICO imposed a MPN of £ 180,000 on the Clinic,  in compliance with  section 55A.  For non-compliance with  the 7th  data protection principle, as provided for in Part I of Schedule 1 of the DPA and paragraph 9 of Part II of Schedule 1 of the DPA.  The ICO was  also concerned  about the mere inference  that the recipients of the Newsletter may be HIV+, thus having  suffered unwarranted distress, anxiety and concern over this reckless  behaviour by the Clinic.

Of interest is the Brent Council High Court action v N P. in 2005  The Council was not sure whether they could disclose ONE PERSON’s  HIV+  status to ANOTHER INDIVIDUAL.  The Council sought a decision from the High Court.

Whereas, in F’s case, RBKC were in NO way compelled to disclose his HIV+ status.  it was disclosed willfully, wantonly,  in  very graphic clinical details, without F’s consent or even knowledge.

Fatima Zohra

On 9th August 2019: Ms Tasnim Shawkat, WCC’s “Director of Law” (another unregulated fancy job title, without any clout) decided that she could not let F know what she would like to discuss.  She withdrew her assistance, leaving her “legal team” to cope. with the case  It seems she gave up.

Whilst waiting for RBKC’s response to his Request for a copy of RBKC’s response to 2nd part of F’s Amendment,  due by 10th December, 2019,  on 3rd December 2019, Dr Fatima Zohra  chimed in, offering a review of  F’s concerns.  Yet another poorly informed person tried to obfuscate the matter.  

Her missive appears at first glance to be confused, despite the fact that she had seen these comprehensive pages and F’s various requests to RBKC.   However, at a closer look, it is a clever way to obfuscate the matter and steer it in a different direction. 

She cleverly avoided replying to F’s requests for a copy of documentary evidence that RBKC replied, as they were legally obliged to do, to the 2nd part of F’s  May 2010 Amendment to his  Information sharing Agreement.  This dealt with instructions for RBKC to delete ALL HIV relevant information from F’s file.

RBKC replied ONLY to the 1st part, relating to the requirement of a  explicit consent  when RBKC contemplated disclosure of this information.

Events  IN 2000 and before 2010, are deftly glossed over. She introduces nothing but flippant, cavalier attitude to the way RBKC handled the response to the LGO, to cover up the unbelievably unprofessional way they managed the reply.  It is a clear example that the customary RBKC arrogance and an attempt to fuck the enquirer’s mind, are applied with usual impunity.   In other words, as cited on “Victoria Derbyshire’s” programme “business as usual”…

It also confirms that the long standing findings by the Law Commissions, that local authorities have poor understanding of data protection legislation; due to poor training and lack of proper legal advice.

Dr Zohra claims that RBKC treated the   response as a “routine” request from the LGO.  How on Earth, did Ms Hussein  and perhaps others,  gained access to F’s CONFIDENTIAL  file held by his Social Worker? Paragraph  6.22 of the DH’s guidance clearly states that the organisation MUST have the powers to ORDER such information and HAD ORDERED such information.  No such thing has ever happened.  In fact, RBKC were asked on many occasions  to produce documentary evidence of this ORDER, which permitted unrestricted access to F’s CONFIDENTIAL file, and permit a wholesale cull of his  information, which included  details about his HIV condition. 

Dr Zohra proposes that F’s HIV related information could be treated as a pedestrian PARKING FINE.

She claims that LGA 1972, paragraph 224 applied to F’s data; therefore it could NOT have been removed, as it would compromise the “integrity of the transaction”. 

Yet, later she states that RBKC, in order to move forward, could “expunge” the data, if simply absurd.  It is meant  to demonstrates, and succeeds  in doing so, to confuse the issue.  “Expunge” from where?  She has NO access to all of the backups that RBKC is obliged to make.  This process was clearly evident  post GRENFELL tragedy. It is not necessary to dwell on backups held by other organisations,  and  all sorts of individuals, who have become AWARE of F’s HIV condition.  This, by the way, CANNOT be easily “EXPUNGED”, as suggested.

F promptly replied on the same day, drawing Dr Zohra’ attention to the fact that HIV relevant information is subject to NHS STATUTORY RESTRICTIONS.

Therefore, Dr Zohra’s arguments do not hold water and her “Remedies” are nothing but a way of wriggling out of a  serious “breach of Confidentiality”, as para 35(2) is irrelevant.

On 6th December 2919, F replied to Dr Zohra, before the DHSC response was to hand.

.It is of critical importance of what happened in 2000, when RBKC  overtly asked  for F’s medical information on THREE separate occasions; on two occasions, from the same source, St Mary’s hospital.  .

This was in contravention of Department of Health rule that “local authorities are NOT entitled to ask for, or routinely receive individual’s confidential medical records, including person’s details of his HIV status.”

Two of those asked, provided RBKC with details of F’s HIV condition, in breach of NHS Statutory Restrictions on data handling, the NHS(Venereal Regulations)1974, which are crystal clear as to who may be given the highly confidential and sensitive information about person’s HIV status.

As RBKC were NOT entitled to receive  F’s HIV related information, were RBKC legally entitled to record this highly sensitive information and eventually make it available to UNKNOWN  number of individuals.  Likewise, it is UNKNOWN how many people have become AWARE of F’s HIV+ status.

Dr Zohra MUST realise that unauthorised  handling of F’s highly sensitive, confidential medical information  relating to his HIV+ status is at the heart of this saga.  

Re-consideration of F’s concerns 2019

The ICO  does not keep records of cases beyond a two year period.  Therefore, he is unaware of F’s request for advice in 2011, regarding the legality of the disclosure of his HIV+ status.

We have decided, to start from the very beginning, that being May 2010, when F presented his amended Information Sharing Agreement.  He received NO reply.   RBKC should have realised that his amendment was in fact a NOTICE, in line with paragraph 10 of the DPA 1998.  Although obliged to reply, RBKC chose to ignore this undertaking and did nothing at all.

On 9th August 2019, F submitted a Request to RBKC  for a copy of the “confirmation” requested in the amendment and of RBKC’s response to para 10.  

On 14th August 2019,    RBKC confirmed receipt of F’s request. An interesting point arose from this message. F was told that he may NOT be given some information.  This is curious, as he asked for copies of letter(s) issued in 2010, addressed to him, confirming understanding of his  Amendment to his Information Sharing Agreement.

On 16th August 2019, F submitted a request to RBKC to reconsider Ms Parker’s suggestion made in 2014, to delete his information.  He suggested that RBKC should come up with a new solution, which should include a good settlement.

On 21st August 2019, F asked the ICO for clarification of DPA’s paragraph 10, in respect of what should happen next, if the data controller, FAILS to reply, as he is legally obliged to do.   His response is still awaited.

2019 ICO review

On 19th March 2019, the Information Commissioner, ICO  replied to F’s lengthy message relating to disclosure of information,  He told  F that “Whilst I understand the substantial body of your complaint took place before the implementation of the General Data Protection Regulations (GDPR), any request made to further understand this will now be covered by the updated data protection legislation.”

On 9th May 2019, we had a new look at the very first event in this saga: F’s May 2010 Amendment to his Information Sharing Agreement.

On 9th August 2019, F submitted a Request to RBKC  for a copy of the “confirmation” requested in the amendment and of RBKC’s response to para 10.

On 14th August 2019,    RBKC confirmed receipt of F’s request. An interesting point arose from this message. F was told that he may NOT be given some information.  This is curious, as he asked for copies of letter(s) issued in 2010, addressed to him, confirming understanding of his  Amendment to his Information Sharing Agreement.

15th August 2019: ICO  told F that he would prepared to re-consider F’s concerns about the disclosure, in light of the new 2018 DPA/DGPR.

The Information Commissioner, the ICO  does NOT keep records of cases beyond a two year period.  Therefore, he is unaware of F’s request for advice in 2011, regarding the legality of the disclosure of his HIV+ status.

We have decided, to start from the very beginning, that being May 2010, when F presented his amended Information Sharing Agreement.  He received NO reply.   RBKC should have realised that his amendment was in fact a NOTICE, in line with paragraph 10 of the DPA 1998.  Although obliged to reply, RBKC chose to ignore this undertaking and did nothing at all.

On 16th August 2019, F submitted a request to RBKC to reconsider Ms Parker’s suggestion made in 2014, to delete his information.  He suggested that RBKC should come up with a new solution, which should include a good settlement.

On 21st August 2019, F asked the ICO for clarification of DPA’s paragraph 10, in respect of what should happen next, if the data controller, FAILS to reply, as he is legally obliged to do.   His response is still awaited.

On 14th January 2019, F advised RBKC, as a matter of courtesy,  that this Blog has gone “public“, its content available worldwide,  to view and comment on.

Unexpectedly, on 23rd January 2019,   F received an unsolicited reply from Ms   Tasnim Shawkat,  Westminster City Council’s  “Manager of Law.”  Another, fancy unregulated Job Title, that any Tom, Dick, Harry or an itinerant bottle washer,  could be given.  Obviously, to bamboozle the unsuspecting “general public” to believe that  it has some mythical gravitas.  Whereas, it has NONE.  Surprised by her mere referral  to his complaint to the LGO,  on 23rd January 2019,  he submitted a clarification.

In her response dated 24th January 2019, Ms Shawkat advised F that she was “unable” to view the Blog.  F responded on 30th January 2019, suggesting to Ms Shawkat what she should ask RBKC to do.  This gave F the opportunity to reiterate, in an abridged way,  RBKC’s failures, rather than refer to the Desired Outcome referred to below.

It was assumed, obviously quite foolishly, that RBKC would take note of F’s reiteration of his request for copies of documents. 

As of 9th March 2019, there has not been a peep from RBKC.    Perhaps the time has come to again request these documents, this time in accordance with the Data Protection Act 2018.

Ms Shawkat replied to F on  18th February, 2019, that she had re-read his message and offered to meet F, rather than continue to correspond by email.  She assumed, quite rightfully, that her messages would  be published here.  F replied on the same day, advising Ms Shawkat that he is awaiting  response to two questions raised on the Blog and will contact her soon.   It should be interesting to find out what she has to  discuss with F.

In the meantime, F is submitting to the ICO, a Request for Clarification of a suggestion made by the Ministry of Justice, that the ICO should be  asked the origin of the  “formal request”.

 

Formal Request for documents

During HCPC’s “investigation” into F’s complaint about his Social Worker, HCPC told F on 25th July 2013, that RBKC told HCPC:

at “c) if a formal request was made by the legal team for information contained in a Service User’s file, it would be the Service Manager within the team, who would have authorised the sharing of information with the legal department, not Mr Leak.”

at “d) Mr Leak was not in a position to obstruct  the legal team from obtaining information from your files.”

Before considering the “”formal request“, let’s consider Mr Leak’s professional as well as legal obligations to F:  Mr Leak was obliged, by the terms of his licence, to keep F’s “information SAFE and CONFIDENTIAL at all times.”

These obligations are clearly defined in HCPC’s “Guidance on Confidentiality” where the “responsibilities” and “the law and consent” are clearly addresses.  It would appear that HCPC chose to ignore their own Guidelines to obfuscate F’s concerns.

Sceptical about the RBKC’s statement about  a “formal request” and “access to his file“,  on 10th September 2013, F sent an FOI Request to many local authorities,

In their replies, NONE endorsed the statement made by RBKC.

The HCPC requested information from the ICO, LGO and RBKC, who are NOT registered with the HCPC and therefore NOT obliged to follow any of the HCPC’s guidelines. 

There is NO evidence that Mr Leak was ever  contacted to provide his version of events, as he should have been, as he ALONE is the REGISTRANT, obliged to follow HCPC’s  guidelines,  he himself responsible for his actions.  

Furthermore, there  is NO evidence  that RBKC or Mr Leak were ever asked for a copy of the  “formal request”, which had such a powerful legal force, to compel Mr Leak to forget his responsibilities and permit a wholesale cull,  by whomever,  of 146 confidential documents from F’s file, in Mr Leak’s custody and under his responsibility.

In respect of contacting the LGO, the request should ONLY be for a copy of the “formal request”.  We will never know, as HCPC refused to provide copies of correspondence between HCPC and the LGO, addressed below.

F requested RBKC to let him have a copy of this crucial document.  To this date, RBKC have been unable to provide it.

This topic is discussed in detail on the HCPC page.

Later in the year, F wanted to know what  information the HCPC sought as evidence from  those who were involved in the matter.

On  10th October 2013, F sent a Request to HCPC, asking them for copies of all correspondence exchanged between HCPC and  the LGO, RBKC, Mr Leak.  He also asked for HCPC’s definition  of “Misconduct” and “Lack of Competence“, which feature in the HCPC’s “Guidance on Confidentiality“, as reasons for further action.

HCPC replied on 5th November 2013.

HCPC’s Claire Gascoigne told F that” disclosure of any information would prejudice HCPC’s conduct  its fitness to practise process”   However, as early as  23 July 2013, Mr Kebir told F that the case will remain closed.  Therefore, there was no process of anything underway.

She goes waffling on about what has NOTHING to do with the complaint and the request for copies of documents.  Obviously, wholeheartedly  hoping to baffle F’s brains with  what was nothing but “bullshit”, hoping that he will swallow it all, hook, line and sinker and shut up.

Her ranting had  ABSOLUTELY NOTHING of CONFIDENTIAL OR CONTROVERSION nature, to do with F’s request, unless HCPC had something to hide; uneasy with disclosing this to F. 

In fact, the ONLY document/information, HCPC should have asked all of those cited above, was to provide a copy of this powerful “formal request”, which compelled Mr Leak to toss aside his professional and legal responsibilities to F.

It can be assumed that HPC failed to ask anyone for a copy of this important documents; perhaps because they were well aware of its NON-EXISTENCE.

The ONLY document issued, PUBLICLY,  by the LGO, is  the Request for documents from RBKC, dated   24th August 2011.  F will never know of any other correspondence, exchanged in PRIVATE, as HCPC refused to provide it.

However, more seriously, it can be alleged that by the refusal to produce the requested information,  HCPC had conspired with  RBKC, to absolve Mr Leak of any  wrongdoing, thus perverting the  course of proper investigation, by making F believe that a “formal request” existed, therefore Mr Leak was at no fault whatsoever.  Hoping that F would NOT take the matter any further.  

This is addressed in some detail on the “perverting the course of justice” page.

.

 

  

Perverting the course of justice

On 19th February 2013,  F complained to the Social Worker’s new regulators, the Health Care Professional Council, HCPC, for  permitting access to F confidential file without consent, as defined in F’s May 2010 Amendment to his Information Sharing Agreement, which he failed to follow.

The details of F’s complaint  are described on the HCPC page.

However, the following merits separate mention:

HCPC told F on 25th July 2013,  that RBKC had confirmed at (a) to them that “Mr Leak was not directly responsible for the disclosure  of you information to the legal  team.”  

at (b)  F is told that ” it has been explained to us (by RBKC) that the legal team have access to all documentation which they require for their role”.

at (c) RBKC states  that “if a FORMAL REQUEST was made by the legal team for information contained in a Service User’s file, it would be the Service Manager within the team, who would have authorised the sharing of your information with the legal department, NOT Mr  Leak”.

(d) Mr Leak was NOT in a position to obstruct  the legal team from obtaining information from your files”.

.A FORMAL REQUEST must have existed, as  F’s 146 Confidential documents, were culled from his file in Mr Leak’s custody.  Some documents containing not only explicit disclosure of his HIV+ status, but also full clinical details about his condition’s progress, the life-saving medication he must take and the inevitable side effects he suffers as a consequence.

The ONLY  “formal request”  that F  was made aware of was made by the LGO to RBKC was on 24th August  2011, for “all the assessment documents for this matter (F’s complaint) and general comments.”  This is addressed in detail on the LGO page.

As F’s HIV relevant information was disclosed to the LGO, the “formal request”, must have contained an explicit request for this information.  Taking into consideration  the nature of the information, this could ONLY be disclosed under certain circumstances, satisfying the NHS Statutory Restrictions of data handling.

On a number of occasions, F asked RBKC to provide him with a copy of the “formal request”,  which would in fact, render Mr Leak impotent from preventing access to F’s confidential file and permit a wholesale  removal of 146 documents, sent to the LGO by Ms Parker, RBKC’s Chief Solicitor and a Monitoring Officer.

RBKC told F that they do not have a copy of this document.  Obviously, RBKC does not consider the LGO’s Request as  the “formal request” quoted to the HCPC.

The question now arises:

F cannot understand why HCPC failed to ask RBKC, during their “investigation” for a copy  of this crucial document,  so powerful to remove  Mr Leak’s legal obligations in respect of F’s confidential information..

It can be alleged that RBKC dreamt up the above narrative regarding Mr Leak’s powers, to perhaps initially convince HCPC of their right to disclose F’s HIV status and clinical information.  However,  it may have become convenient for the HCPC to accept this explanation, as it would get Mr Leak off the hook, bamboozle F and wholeheartedly  hope that he would accept this explanation, shut up and go away.

HCPC told F that they have asked  for information from various parties, including the LGO.  However,  there is NO evidence that Mr Leak was ask for his version of events, or even made aware of F’s complain to the HCPC.

It is quite possible, due to RBKC bad controls over access to personal information, that Mr Leak was NOT  aware of the cull of 146  documents from F’s file, as stated in HCPC’s response dated 23rd July 2013..

It can be alleged that RBKC manufactured of the notion that a “formal request”  existed, could be construed as an attempt by RBKC  at  “Perverting the course of justice“.  .

We understand that “the word pervert can mean “alter” but the behaviour does not have to go that far – any act that interferes with an investigation or causes it to head in the wrong direction may tend to pervert the course of justice.

(This information is based on public sector information licensed under the Open Government Licence v2.0. The original information can be found here; https://www.cps.gov.uk/legal-guidance/public-order-offences-incorporating-charging-standard).

In order to properly understand the allegation of “perverting the course of investigation/justice”, On 24th May 2018,  F asked  the Ministry of Justice for clarification.  In their reply dated 29th May 2018, F was referred to the Information Commissioner.   F replied on 30th May 2018.

As of 1st March 2019 F has not contacted the ICO.   But will do  very shortly. 

Law Commission

The :Law Commission published two reports, which are of interest, as they address F’ concerns.

  1. Adult Social Care – Consultation analysis published in March  2011.  This publication addresses in some detail the process of establishing individual’s “eligibility for Adult Social Care”.

2. Data Sharing Between Public Bodies – scoping report, published in July 2014.  This report publishes actual conversations with various organisations and highlights the many problems local authorities have with the interpretation of the various  legislation dealing with data protection.  It confirms that there is a  poor understanding of data handling legislation, due to non-availability of proper legal advice from the “in-house” legal professionals. 

However, this ignorance is not an excuse for not seeking proper legal advice from external sources; for  example,  from the many legal professionals local authorities have on confidential retainers.  Some to ensure that they do not assist anyone in a case  against the local authority, or provide any advice; others to provide legal advice on how get out from a compromising situation.

Few HIV related legal cases

We wanted to find out if a complaint/case  has ever been brought against anyone for disclosure of person’s HIV+ status not only without consent, or informing the individual that the disclosure was about to happen, but also without having any legal reason to do so.

When we asked the NHS, Department of Health and the  Information Commissioner, they all confirmed that THEY HAVE NOT RECEIVED A COMPLAINT/CASE for this specific matter.

A search through the BILII, the legal cases index, did not bring up a single case  brought for this specific matter.

On the internet we found a posting by  Ms Lisa Webley, published in “The Litigator” magazine in 1997. 

It concerns the discrimination against individuals with HIV in respect of assistance with bringing  legal action against  those who have breached the legislation.

We can claim that throughout our investigation and search for legal assistance,   DISCRIMINATION exists on the grounds that F is the affected person.

Had F been a persistent thief, rapist, child molester, illegal immigrant, or anything else,  he could avail himself of proper legal advice, often for free, from many sources.  However, as soon as  HIV+ status matter was mentioned, there  was a deathly silence, or refusal to get involved in the matter.

The matter, is NOT at all that COMPLEX.   In the first instance, disclosure of person’s HIV+ status without his consent, or even knowledge, is a breach of COMMON LAW CONFIDENTIALITY.  In addition, there is the NHS Statutory Restriction on data  handling and Article 8 of the Human Rights Act.

However, nobody would touch the matter with a second hand barge pole.  We can claim that this is an example of OPEN DISCRIMINATION on the grounds that the complainant is HIV+.

We tried to contact Ms Webley who has  since 1997 climbed up the legal ladder.   She did not  respond to our enquiry.

 

Article 8 – Human Right Act 1998

Article 8 of the Human Rights Act also individual’s information.

During our research we came across  two cases in front of the ECHR,  relating to the disclosure of individuals’  HIV+ status without their consent.  Both cases, the Z v Finland and I v Finland happened some time ago in Finland.

More recent case, the Brent Council v  N  P  refers to the Article.

When F considered  handling his case as an LiP,  on 13th October 2016, he asked for advice from the Ministry of Justice Legal Aid Department.

He was told that his case would qualify for Legal Aid and should he wish to apply for it, it must be through a Legal Aid Solicitor.

As he could not find  such a professional, he decided to publish his concerns in this Blog and seek information, advice or just a comment  from the Social Media.

Dept Communities and Local Government

F became aware  that local authorities were obliged to follow the Department of Health’s “Confidentiality – NHS Code of Practice‘,  In order to get a  reassurance of this information, on 25th November 2013, F contacted the DCLG, as it was then.

He was very happy when the Department replied on 19th December 2013, confirming that what he  assumed, was actually true,

The DCLG’s reply is very clear in respect of handling of HIV related information.  It refers to the NHS Code of Practice, where paragraph 46 addresses  this point.   

Therefore, RBKC should have been guided by the provisions of this paragraphs, when considering the disclosure of F’s HIV related information.

F also contacted LIBERTY, the organisation allegedly concerned with individual and the Human Right Act.  F was  told that the “Confidentiality  NHS Code of Practice” applied ONLY to the NHS.   The statement above would  certainly contradict Liberty’s assumption.