Skip to main content
4 February 2026

Clinisys: A strong fit for blood transfusion laboratory workflows

Paul McAnuff

Domain Lead, Blood Transfusion

About

Paul joined Clinisys in 2020 and is an accomplished professional with expertise in the Blood Transfusion domain, specialising in Leadership and team management. He excels in project planning and delivery and is adept at workflow analysis and configuration, with a strong focus on Training and mentoring. Paul is committed to maintaining high standards of Safety consciousness while managing Client Relationship Management.

Blood transfusion is meticulous, well-regulated, and focused on safety. Many vendors have been unable to build systems around the UK’s strict requirements, giving Clinisys an all but unique role in supporting this vital discipline, says Paul McAnuff, blood transfusion domain lead.

Technology to manage blood transfusion is a hot topic right now. Some trusts that have opted to use their electronic patient record to manage most of their laboratory services are still turning to Clinisys to provide them with a blood transfusion solution.

Clinisys is working on some significant go-lives as a result. So, why does blood transfusion require so much specialist knowledge, and what is it about Clinisys WinPath that means it is ideally placed to support this critical service?

Just remind us of the blood transfusion process and where the LIMS is involved?

Paul Mcanuff, blood transfusion domain lead: Blood is made up of red blood cells, white blood cells and platelets in a liquid called plasma. A patient’s blood group is identified by antigens found on a surface of red blood cells. Everybody (or nearly everybody) falls into one of eight blood groups – A, B, AB and O positive or negative.

So, the first step in the blood transfusion process is to establish what blood group a patient has and whether they have any antibodies that could cause a reaction to any blood that they are given. There are four main companies that provide the analyzers that are used to analyze a patient’s blood from a Group and Screen test, and we interface to all of them.

The result will be sent to the LIMS, which holds the blood group and antibody screen result and can trigger specific alerts based on any differences in the blood group and Antibody screen history. The next step is to request blood from the laboratory and to physically match it to the patient’s blood, to see if any immune reaction occurs. If this ‘crossmatch’ doesn’t reveal any problems, the blood bank can release the blood for use.

What is the role of guidance and regulation?

Paul: Like many pathology disciplines, blood transfusion is hard because it’s complex and it’s highly regulated. The British Committee for Standards in Haematology (BCSH) issues guidelines for transfusing patients and the Medicines and Healthcare products Regulatory Authority regulates hospital blood banks and other sites that collect, test and supply human blood and blood components.

The guidance and regulations don’t change very frequently, but they are very strict: for instance, WinPath has thirteen checks that must be passed before the blood bank can issue blood electronically without the need to cross match.

That’s one of the reasons that new entrants to the NHS lab management market have struggled and even the big EPR vendors that have lab modules don’t do blood transfusion. They tend to be coming from other jurisdictions, including the US, where the regulation around blood transfusion is different and, most of us would say, less strict.

Why do laboratories value the Clinisys solution?

Paul: We used to say that our system was built by transfusionists for transfusionists. All of our product specialists have come from the lab, so we have the depth of knowledge that is required to take those guidelines and make sure they can be applied on the ground.

We have a Masterbuild that is based on current BCSH guidelines and covers 80-90% of a lab’s requirements. But when we run a deployment project, we still go through high-level and low-level design. Many of our customers use the introduction of a new system to make changes to their ways of working, because they know the LIMS is based on best practice and years of successful implementations.

But if they want to make variations or additions, we can accommodate that. Pathology networks and multi-site trusts also like that we can provide a single record that shows a patient’s full transfusion history and makes it less likely that important information about previous transfusions will be missed.

Could you outline some of the other features of the system, and explain how it is built for safety?

Paul: Clinisys WinPath is modern. It’s Windows-based, has a colourful front-end, and comes with lots of easy-to-use menus, hotkeys, and features to assist users. For example, there’s a configurable rules base that will auto-request standard group and screen codes, so the biomedical scientist doesn’t have to remember them.

Special requirements can be added via Request rules, based on clinical diagnosis or request entry details. For example, women of childbearing age will automatically be assigned a special requirement of K- to ensure they get blood that is K- to protect from the possibility of producing an antibody. Result rules can also be set up to fire when results are saved and can auto reflex on different comments and add on tests if required.

WinPath also includes a set of hard-coded electronic issue rules that cannot be over-ridden. The system will show users if a sample doesn’t meet those 14 rules for electronic issue. Or, if a user needs to issue a unit of blood that is a different blood group to the patient, there is a set of mismatch tables that will only allow units that are deemed suitable to be issued and won’t allow any clinically dangerous groups to be issued.

Plus, there is a full audit trail for all requests, from initial booking through resulting and final authorisation, and for blood and blood products, from initial entry into the blood bank, to the point at which they are issued or discarded.

What is the future of blood transfusion and technology?

Paul: The process of blood transfusion hasn’t changed too much in the 20-years since I started out in the lab, but the technology side of things has changed. The LIMS has evolved to accommodate new guidelines and it has become integrated with more IT systems.

In recent years, there has been a big focus on fully digitising the blood transfusion process from vein to vein. Electronic blood tracking systems log the movement of blood after it leaves the blood bank, and positive patient identification systems allow staff to match blood to the patient by scanning the blood bag and patient wristband.

Clinisys doesn’t provide these systems, but our LIMS interfaces with them. That improves patient experience and patient safety, which is the most important thing, because blood transfusion is one of the pathology disciplines where getting things wrong can do real harm.

One of the things that I love about working with transfusionists is that they are passionate about making sure that does not happen. They are absolutely committed to getting it right, and we do everything that we can to make sure our solution supports them.

The views and opinions expressed in this blog are those of the author and reflects personal experience and is not representative of all users.

Paul McAnuff, Blood Transfusion Domain Lead, Clinisys

“We have a Masterbuild that is based on current BCSH guidelines and covers 80-90% of a lab’s requirements. But when we run a deployment project, we still go through high-level and low-level design. Many of our customers use the introduction of a new system to make changes to their ways of working, because they know the LIMS is based on best practice and years of successful implementations.”

Related content