Tech Talk – Medical Device Particle Test Method Validation
See the previous Tech Talk for Medical Device Particles.
See Part 3: Particulate Testing of Medical Devices.
See the previous Tech Talk for Medical Device Particles.
I previously discussed testing medical devices in blood here (in 2007!), but I think I did a poor job of it and I’d like to revisit it.
Why do you test in blood? Well for one, blood is hard to simulate, it’s a non-Newtonian fluid, and using glycerin and water don’t really do it justice, but these can work depending on the application. For another, a common blood test is to check for hemolysis, sure this is tested during a biocompatibility test, but biocompatibility tests are not performed during actual use conditions. Hemolysis may also be a part of an animal safety study that you want to check out beforehand.
Where do you get the blood from? At a slaughterhouse of course, if you can find a smaller or craft meat location in your area, they’ll probably work with you, one used to sell to us for $40 a week, and we’d take a couple gallon buckets and their workers would fill them up while we waited. They only slaughtered on certain days, so call ahead. You’ll probably find cows easier to find and work with, but there isn’t really a reason you couldn’t use pig blood.
Before we leave for the slaughterhouse we’ll set up a water bath at 37ºC to be ready when we get back. Then we’ll add anticoagulant to the blood collection bucket. We’ll use either heparin or Acid Citrate Dextrose (ACD).
Once we get the blood, we mix the bucket to ensure the anticoagulant is distributed in the blood. Heparin is prescription drug, so hit up your vet consultant or animal lab for some ahead of time. ACD you can make based on USP guidelines from commonly available chemicals (water, citric acid, dextrose, and sodium). We used around 10,000 to 20,000 units of heparin per liter of blood. Of note is heparin is used clinically (on people) more in the U.S. and ACS is used in Europe, so you could maybe argue for the use of one over the other, but you’re using animal blood, so I’m not sure if that really matters. I’ll assume we are using bovine blood for the rest of this post. If you don’t use an anticoagulant, you’ll end up with a clot bucket when you get back to the lab, just throw it away if this happens, it is not recoverable.
Time is generally of the essence so don’t stop by Chili’s on your way back to the lab. Also, just be aware that water will damage your blood cells, so it is preferable to rinse your lab ware with a bit of saline before use.
When we get back to the lab we first check the blood pH and temperature, ideally the pH is between 7.2 and 7.4. We then take a hematocrit (hct) measurement by collecting blood in a capillary tube with clay sealant to stopper the bottom (get blood before using clay). Then we centrifuge the capillary tube for a few minutes at high rpm. Once centrifuged, the capillary tube will look like this:
I've spent the last few weeks dealing with bench tests as we wait for other results to come in. Bench testing or performance testing gets stuck in section 18 of the 510(k), since it is in the back means they don't read it right? You will save yourself a lot of grief if you read the format guidance and make sure your protocols and reports line up nicely with their requirements, although you will need more than what is listed in the guidance, at least a scope.
For a small company there are several challenges to bench testing, all revolving around the number of people that have enough understanding to run the tests. My company has three plus one consultant that can run the majority of the tests, it is preferable to have employees sign off on everything so the consultant is out, and one of the three has the understanding to run the tests, but not the personality type to see it through. That leaves the two engineers, one of which is on vacation this week, so that leaves me for now. MD&DI sums up the who should do the bench testing very well.
The first problem is the protocol, which must be signed off before the test begins, the problem here is that no one besides the engineer authors are likely to really understand what is going on. This means no problems will be caught until the engineer testers try it for real. Sure, we've tested it some previously, but when everything is recorded things change. I wrote a protocol and discovered I couldn't hold a negative pressure I thought I could so had to change it up a bit. This means rewriting and walking around getting signatures to get it approved before I can start again. This is not much of a problem, unless it is after 3:30pm and QA has gone home for the day. Then I'm forced to wait around until they come in at 9 the next day. I have argued that by having my signature on it that the protocol has therefore been predefined and good to go, but I haven't gained much ground with that.
The next problem is that these tests take time, we are shooting for 24 hours of use. I rallied around testing for 26 hours but my boss vetoed that saying 1.5 times is standard, meaning 36 hour tests and every other day I have to come in at an awkward time (do not worry, I am getting my revenge- see below). I am amazed my wife hasn't accused me of cheating on her yet with the late night stops by work. The 1.5 times the maximum limit you're shooting for is a good rule of thumb, and appropriate here, but it doesn't work for everything, like negative pressures.
The last of my whining centers around the sample sizes that will not be high enough to make everyone happy. With limited product and limited resources, running a dozen 36 hour tests could take a month. Unless you are going to manufacture, sterilize, and shipping simulate a batch of samples yourself in the next week, complaining about sample size doesn't accomplish much. Do a reasonable job and if the FDA picks on it the most likely thing that will happen is they'll ask for more testing.
I mentioned in my previous post that the deadline slipped (still not my fault), this has given me time to come up with some additional bench testing to put in motion. I say put in motion because I was so confident I'd meet my part of the original 510k deadline that I planned a two week Hawaii trip starting one day before the deadline. Now all the loose ends will have to be tied up by my boss and the other engineer, I sorta feel guilty now, but about 20 minutes after landing it will be forgotten. I give the extra testing a 40% chance of not being done when I get back. I have to say though that the last year has been a blast and if you're an engineer with a good work ethic that can tolerate the risk of working for a smaller company then go for it.
Here at the happy medical device factory we've moved on from sterilization to our next crisis, the in-vitro test. There are still quite a few outstanding sterilization issues, but we like to make things interesting by panicking about something else before the last crisis completely subsides. The in-vitro test's goal is to obtain data that supports the safety and efficacy of the medical device.
Usually when a test is described as in-vitro it involves using blood outside of a body. Keep in mind when I describe it, I'm an engineer, so as usual- I probably don't know what I'm talking about. In our case, we run down to the local slaughterhouse and pick up gallons of cow blood, add an anticoagulant, heparin for us, (you can also use sodium citrate) and bring it back to use for our test.
When we get the blood in we run it through an arterial filter, add dextrose (to preserve- that is the theory anyway), check the temperature, pH and hematocrit. The pH we want between 7.2 and 7.4, but it depends on temperature somewhat, we're currently in disagreement about what we should do if the blood comes in above 7.6 or so, I'm in the throw it out and try again tomorrow camp, but others have argued for adjusting it. Luckily, we haven't had any pH above 7.6 in years. The hematocrit (hct) we generally get 38-42% and we adjust it down to 32% by adding saline, a small vain attempt to keep at least one thing consistent across tests. Another common tactic is to adjust hct to 25%. A previous incarnation of this test had us removing the buffy coat layer of the blood, but that required a lot of time and effort that did not really improve the results.
The next step is the moment of truth for the whole day, splitting the blood into the sample groups, for us, our device, predicate device, and control. I say it is the moment of truth because once you split it into the three containers or whatever you're testing in, you test the blood variable you're looking at in the test. You hope and pray that these initial readings of whatever blood variable you're testing come out reasonably close together, if not you just wasted half a day. It sounds easy, but blood is not consistent and any number of small factors can mess things up, blood settling, not perfectly clean containers, water in the sample containers, etc.
Once we have that down the test can begin in earnest for the next 5 or so hours. The reasonable life of blood is generally 6 hours. After that is clean up, it makes for a long day. Entertainingly enough now, on a previous 72 hour device I worked on the FDA required us to do an in-vitro test for 72 hours, saline tests weren't good enough for them, the results were predictable, a black, stinky soup that stunk up the place for weeks after it was disposed of, but hey, we got our largely irrelevant results!
My main task after an in-vitro test seems to be discouraging people from comparing results across in-vitro tests, but that is a post for another day.