Royal Preston Hospital scientist made series of blood mistakes

The panel acknowledged Mr Kharporia’s remorse for his actions and “genuine contrition” in relation to the concerns identified.

A biomedical scientist responsible for a number of errors in the haematology and blood transfusion departments at the Royal Preston Hospital has been sanctioned.

A Health Care Professionals Tribunal Service (HCPTS) report has been issued in to the actions of Siddiq Khanporia, who at the time of the incidents, was working as a Band 6 Specialist Biomedical Scientist at Royal Preston Hospital. His role involved processing blood samples for the Haematology and Blood Transfusion departments.

Mr Khanporia started working at the hospital on June 1, 2010, leaving on April 10, 2015 before returning on October 6, 2015. Mr Khanporia resigned from the hospital, and is no longer practising as a Biomedical Scientist, with ‘no intention of returning to the profession’.

The allegations

1) On June 2, 2019, Mr Khanporia issued Service User A who was an Anti-Jka patient, two red cell units which were not antigen negative, Jka, and in the process, he overrode a system prompt without documenting any justification. It was noted in the hearing that the units were not transfused and were returned to the lab, at which point it was noticed that they did not meet the specific requirements for the patient.

2) On or around June 4, 2019, Mr Khanporia released three erroneous FBC (full blood count) results.

3) On or around June 5, 2019, on an insufficient sample, he selected prenatal rather than requesting a sufficient post-natal sample for a Kleihauer test (a maternal blood test that detects and quantifies fetal red blood cells).

4) On January 26, 2021, Mr Khanporia processed a specimen of a family member while not working on shift in his role.

5) On October 5, 2021 he did not detect that there was a discrepancy of Service User E’s date of birth on the samples and request forms when compared to Quadramed (a patient index).

All allegations were proved, apart from allegation 3, where evidence was found to be insufficient.

Royal Preston Hospital signplaceholder image
Royal Preston Hospital sign | submit

Mr Khanporia voluntarily chose to absent himself from the HCPTS hearing last month, but did enter submissions through a Ms Buckle.

He stated in relation to Particulars 1-3, namely the June 2019 incidents, that these occurred during Ramadan when he was fasting and was working long shifts back to back. Ms Buckle told the Panel that he explained the root of these incidents being stress, fatigue, and pressures at work.

In relation to Particular 4, Ms Buckell explained that this allegation related to a governance breach during the COVID-19 pandemic, and in relation to Particular 5, Ms Buckell said Mr Khanporia missed the incorrect date of birth as he was trying to answer the phone whilst booking in the samples as required.

Decision

The Panel found that the Registrant’s actions “fell well below the standards expected of a registered professional”, had the potential to result in serious consequences for patients, and accordingly, determined that the Registrant’s fitness to practise is currently impaired on public interest grounds.

However, members were of the view that the incidents on June 2 and 4, 2019 and October 5, 2021 were isolated events and do not represent a fair or reliable sample of his work. The Panel considered that they amount to “a very small number of incidents over the course of a 19-year career and, in those circumstances, would not provide an appropriate basis upon which to assess his overall competence.”

They took the view that particular 5 when viewed in its proper context, “amounted to an honest mistake”.

Support your Lancashire Post and become a subscriber today.

Enjoy unlimited access to local news, the latest football stories and new puzzles every day.

With a digital subscription, you’ll see fewer ads, get faster load times, and access exclusive newsletters and content. Click here to subscribe.

Remorse

The panel acknowledged Mr Kharporia’s remorse for his actions and “genuine contrition” in relation to the concerns identified.

A report states: “He had been proactive in undertaking training independently and was subsequently signed off as competent. He had worked satisfactorily with colleagues, had fully engaged with both his colleagues and the HCPC prior to this hearing, and had taken full accountability for his shortcomings. The incidents arose in the context of fatigue experienced during Ramadan. He had implemented measures to prevent a recurrence, and during a 12-month performance review no further errors were identified.”

The Panel also took into account the wider context, including the pressures arising during the COVID-19 pandemic and the fact that the Registrant had allowed his emotions to influence his actions. It was satisfied that he had demonstrated insight, understood the seriousness of the consequences of his conduct and the potential impact on patient safety, and that the risk of repetition was low.

Sanction

The panel considered the misconduct to fall at the lower end of the spectrum of seriousness but nevertheless, concluded that a sanction was required in order to uphold the wider public interest and maintain public confidence in the profession and the regulatory process.

Having considered all the circumstances, the Panel determined that a one-year Caution Order was the most appropriate and proportionate sanction. Anyone searching the HCPC Register will see the caution for its entire duration, but it does not restrict work.

Lancashire Teaching Hospitals

A Lancashire Teaching Hospitals spokesperson said: “Although this hearing addresses allegations dating back to 2021, we can confirm that our laboratories have longstanding and robust checks and validation processes in place alongside comprehensive training and competency requirements for all our colleagues in line with national standards.”

News you can trust since 1886
Follow us
© 2026 Iconic Media Group Ltd. All rights reserved.Cookie SettingsTerms and ConditionsPrivacy notice