Showing posts with label medical device development. Show all posts
Showing posts with label medical device development. Show all posts

Sunday, January 9, 2011

Biocompatibility Testing - Needles

A reader asks:

I am new at medical devices biocompatibility. I've been asked to perform a MEM cytotoxicity assay on an arteriovenous fistula needle. I am not really clear on how to perform the extraction of the device; as I've been asked to do it on the final device which has the needle plus the tube. Would it be appropriate to calculate the volume for the extraction based on surface for the tube and weight for the needle, and sum up both volumes, and submerge the device in that volume?
You want to test the fluid pathway of the device and any other part of the device that is inserted into the body, i.e. the route the fluid would take as it enters the body and exterior of the needle.  As you said, in your case it sounds like the area comes from the interior of the tube (and plunger surface), the needle, and some extra for the exterior portion of the needle that is inserted into the body. I would stick to the ISO 10993 standard and just use the surface area calculation, I'm not sure if the standard allows a combination of the weight and surface area calculations.



It sounds like you may be performing the testing yourself, but the easiest way for me to get answers or at least some direction for medical device biocompatibility testing (assuming you end up using them) is to call Nelson Laboratories, NAMSA, Pacific Biolabs, or WuXi Apptec.  If this is your first time getting testing done- call all four (or at least the first two) and see which one you like, if this is not the first time, generally someone in the company has some strong opinions on which one is best. 



Good luck with your testing.

Enhanced by Zemanta



Sunday, January 2, 2011

510(k) Approval Timeline Part 2

My original 510(k) approval timeline is my post popular post ever!  I didn't even follow up with my latest project information.  We extended the disposable product line and it was 30 day FDA review, no questions asked / response required, approval in April to May 2010.  We justified not doing sterilization, biocompatibilty, shelf life, and packaging.  All in all it was about as good as it can get time wise.  Timeline went something like this:

  • August to December 2009: Concept and prototype to design

  • Jan to March 2010: Product build and verification / validation testing

  • April to May 2010: 510(k) Approval

Our validation was an animal study using a physician, who filled out a questionnaire like one to ten, how much is this better than the predicate device after he or she used it, oh boy did I learn something there, I'll go over that some other time.



Now we just have to sell them...



Friday, November 26, 2010

The Attribute Gage R&R

There is not that much information about the attribute gage (gauge) R&R readily available online (that I was able to find), so I thought I'd cover what I've done.  First the basics, an attribute is something you can't quantify, generally a visual inspection- is this part "red" or something like that.  While it generally seems simple, especially to the technical leads, operators can often get tripped up trying to pass or fail parts based on a description or a couple pictures.  In the red example, can operators compare against the Pantone effectively and is this repeatable?  You want to have your acceptance criteria and how you are proposing to test it with trained operators set up beforehand.



Your gage R&R should mimic what you do on the line and should be set up that way.  If the operator does an inspection on the attribute before passing the part, then a final QC does that same inspection, you have two inspections and this should be part of your testing.  You should present this as the entire package when possible.  QA types tend to freak out when they hear you would accept a 10% possibility of passing a bad part, when in reality its 0.1%.  Having the two (or more) inspections will be really helpful when you get to the acceptance criteria portion.



Test Method: You need to determine the number of operators, parts and trials.  Trials is easy, just use three, everyone does, obviously more is better, but three is generally good enough and you don't want to be looking at parts all day.  For operators, you need two, but if you have three or more lines or shifts, you can include those easily enough.  The number of parts is where it gets tricky and you're going to have to make a judgment call.  Generally medical device companies rely on some sort of confidence and reliability based on the severity or RPN of the potential failure, however, in the case of gage R&R everyone seems to follow auto industry guidelines which are usually a smaller quantity, 30 is generally defensible either way.



The Acceptance Criteria:  The key one medical device companies are concerned with is the probability of a miss, which is defined as:

  • Probability of a Miss = (# times a bad part was passed) / (# of opportunities) [i.e. number of inspections]

You need to base this on what is acceptable and preferably tie this back into your risk analysis (you may have to increase sample size).  The good news is, if you're doing two of the same inspection, you can set it up so that your acceptance criteria can be something like:

  • Probability of a Miss (2 inspections) = (# of times a miss by one operator that were missed by another operator) / (# of opportunities)

In that way you can argue that different types of misses will be caught by different operators, but you are only concerned with the fact that it is caught at some point in the process.  Setting it up this way significantly lowers the likelihood of a miss and allows you some flexibility.



Other Information:  I recommend keeping it simple and only requiring a certain probability of a miss in your protocol (maybe effectiveness as well).  You'll want the rest of the information you can collect documented, but that is a business decision, not a safety decision.  You can cover:

  1. Effectiveness - (# of parts correctly identified) / (# of opportunities) [a low effectiveness indicates your process is probably not robust and will give you trouble over time, greater than 70% is generally acceptable]

  2. Probability of a false alarm = (# times a good part was rejected) / (# of opportunities) [waste]

  3. Repeatability = (# agreements) / (# parts inspected) [calculate per operator and total, if an operator has low repeatability, less than 80% or so, he or she needs retrained]

  4. Reproducibility = (# agreements among all operators) / (# parts inspected)

  5. Bias = (Probability of a false alarm) / (Probability of a miss) [calculate per operator and total]



The Test Setup:  For this you'll need two experts in the attribute being inspected, the experts will sort out the good parts from the bad, label them in some fashion, and randomize them.  In my experience you should have at least 25% bad parts, even though your process isn't likely to have 25% reject rate (hopefully).  It is nice to include some very marginal parts, but those can be hard to find and agree on.  Don't have the operators performing the test make the parts if you can avoid it.



The Test:  You want to set it up so an operator makes a determination and someone else records it, don't let the operators know the sample being given to them, previous results, or talk amongst themselves.  Do the testing on the line and try to keep the production pace.  During a gage R&R I find the operators tend to err on the cautious side.



The Results:  There you go, you can now say your test method is qualified and have the data to back it up.  You can also make operator decisions based on the results, maybe move one around to catch things earlier in the process, which one is the go to person, etc.  I find the attribute gage R&R easier to perform than the variable one, yet it is generally more important than a dimensional one from a safety perspective because there are more things I can't measure easily.

Enhanced by Zemanta



Tuesday, August 10, 2010

Latex Free Labeling

For a new device we spent a bit of time working on "Latex Free" labeling.  From the FDA point of view (801.437), the key point is natural rubber.  The term "natural rubber" includes natural rubber latex, dry natural rubber, and synthetic latex or synthetic rubber that contains natural rubber in its formulation.  So while your label coatings may contain latex to give them that glossy look, its most likely synthetic latex (although not always), and you're off the hook.



ASTM D6499 (LEAP assay) can be used to determine if your device tests positive for natural latex and is reasonably cheap insurance that your product is safe.



Recently BS EN980 added a Latex symbol for devices that contain latex.  However, there isn't a corresponding recognized symbol for latex free, so the words Latex Free seem like the way to go.  Many companies, including GE and 3M, use the Latex symbol with an X through it.



While it is easy enough to lay off the latex gloves in your assembly area, what are your suppliers or their suppliers doing?  Although it seems far fetched, a polymer resin handled with someone wearing latex gloves could make its way into your molded part.  I can assure you, tracking down this information is a pleasant way to spend a week.  Updating your Certificate of Conformance requirements from the product development seems like the easiest way to go.



Tuesday, April 27, 2010

The perception of risky process changes

Now that we have an approved device we're spending at least some time on process improvement instead of all out research and development. Unfortunately, even though everything is fairly new some of it is already difficult to change.

We have a piece of test equipment that displays pass or fail, prints out a page of results, and writes them to a database. The operator runs the test, marks pass or fail in the traveler, then staples the results to it. During a sort of related process change I suggested we take out the print out of the results. This was met with quite the uproar and doubt about how we could ever do it.

Apparently removing a redundant step that no one ever looked at was a big deal. Engineering and complaints thought it might be useful, even though they never used the printouts two years in- but someday they might. The change would save some minimal amount of money on supplies, transferring of materials into and out of the clean room and storage, along with associated labor. I was able to finally make headway when I pointed out that we do plenty of visual inspections that do not have another record and in this case we still had a record in the database. Everyone initially thought it sounded like a risky change based and we could be out of compliance, but it was all our own perception.

While this isn't the most impactful example, I think I may have learned the value of taking time up front to set this all up efficiently, but I'm not sure I'll be able to convince anyone to add extra time for these activities the next time around. "We can take care of that stuff during validation!"



Sunday, April 25, 2010

Annual review of received parts' dimensions

Many companies perform an annual review of every dimension or 100% inspection on all received parts. While this may serve as a halfway decent preventive action, I'm not convinced it is worth it. If you have automated inspection methods, maybe then it is not too much effort, but we're still using hand tools or manual adjustments for the majority of our parts.

You could argue that you have a critical device, we have to check for dimension drift. Well why aren't you checking for that anyway? And if it is so critical shouldn't you have insured that the supplier's process was capable before you even signed up with them? If it is truly critical and you're not checking it but once a year, good luck with that.

Additionally, if you do find something out of specification, nine times out of ten it is going to be on a non-critical dimension, or else you would have caught it in receiving inspection or manufacturing anyway. Once you find the out of spec item, you have to go back to your inventory, check it, then justify why it is either okay and change the specification, or send it back, and jump through hoops to justify why it was okay to use on the ones sold, but not okay to use going forward, or whatever other contortions QA wants.

In my experience these generally boil down to unclear or unnecessary specifications or measurement issues, where to start measuring a curve, a hole over specified, etc. Another argument for doing it right the first time and checking your supplier's process.

However, this if often a difficult battle, as new parts are generally part of R&D efforts and the team from R&D is behind schedule and they always try to make up schedule time by trying to get either quality or manufacturing to compromise on one issue or another (I *may* have pointed this out at a meeting once). If this happens and you don't have time to ensure supplier process capability, it is not the worse thing in the world, you can always blame the vendor and shop around for a new one that has no familiarity with the part and uses the same process that can't meet the specification. Sometimes the best you can do is make the risks clear.



Friday, August 14, 2009

Why do clinical trials in the US?

I'm searching for a reason and here is the one I came up with:
  • The world expert resides in the US and you really need her on your team
I couldn't come up with any more concrete reasons. Maybe you don't know the regulations oversees, but that can be easily taken care of, search the web or buy a book, it will save you in the long run. Even if most of your sales are in the US, I don't think a foreign trial hurts you (as long as your sponsor is halfway respected of course).

If you have a standard device, almost anywhere will do. If you have a new device, find a well respected doctor in Europe and see what kind of magic you can work there at half the regulatory burden and less lawsuit liability.

(Photo from Karen Horton)



Tuesday, July 14, 2009

Separation of powers

As a "project engineer" I've come to appreciate why larger companies put R&D in a different building- so they can get something done. Anytime part of your duties include supporting manufacturing, you have a very hard time setting aside enough time to accomplish significant design goals. Instead the manufacturing support gets done and the development that can be done reasonably quickly gets done in spare time, research a new fitting-sure. Seriously, there is nothing I can do about part Z getting here 3 weeks late, yet I am dragged into those discussions all the time.

So if you're running a company or managing engineers, keep your functions separate, or else realize that someone working 25% on manufacturing support is in reality going to spend 75% of his time on it. Don't even drag them into it, you might help in the short run, but in the long run you're worse off if the entire company is running around putting out the fire of the moment.



Sunday, May 10, 2009

Solvent bonding, polycarbonate to polycarbonate using cyclohexanone

Medical Devices Blog (clever name!) has a couple posts on solvent bonding of polycarbonate, something which composes the bulk of the happy medical device company's assembly, well that and PVC tubing to polycarbonate fittings (see the well done descriptive picture). He is using cyclohexanone to bond the polycarbonate and getting 20 lbf tensile strength. This seems about right to me depending on geometry, and is industry standard for this type of bonding. We took efforts to design out most of the polycarbonate to polycarbonate bonds out by designing custom molded parts, which saves on assembly time and gives a superior product. If the cyclohexanone is still tacky after 18 hours you're probably using too much cyclohexanone.

We use a couple different solvent dispensors (one from Ventrex) and fixtures to get the application right and ran a few quick studies to determine the ideal amount to apply. Ventrex may be able to help you out with your application, this is one thing I enjoy and think I do well at- letting vendors do the bulk of work for me.

Also industry standard is the ETO sterilization with polycarbonate. At a previous company we tried to gamma sterilize Polycarbonate and that doesn't work well, the fittings became brittle and discolored to varying degrees- that didn't stop us from using them though...

Update, yeah I screwed up the title originally, that should be polycarbonate to polycarbonate.



Sunday, May 3, 2009

Patching Microsoft Windows on medical devices

Law Firm IT has an interesting post on installing the latest Windows patches on medical devices, including this:
"...because the machines were running an unpatched version of Microsoft's operating system used in embedded devices they were vulnerable.

Normally, the solution would be simply to install a patch, which Microsoft released in October. But the device manufacturer said rules from the U.S. Food and Drug Administration required that a 90-day notice be given before the machines could be patched."
I'm not sure if that is completely correct about a required 90 day notice to the FDA before patching Windows. I'll leave that to a regulatory expert.

I do know that any changes to Windows and the medical device software has to be revalidated, at least the potentially affected parts anyway. The revalidation is obviously going to take time and effort and the rewards are often low, especially if you label your device to not be connected to the internet. You want your software guys putting in new features, not screwing around with Windows compatibility for people who are using the device off label. Additionally, the Windows patch needs to be installed, no small feat for a device that is not supposed to be connected to the internet. All of this time adds up and the bottom line is you're never going to be a step ahead of software virii on a medical device, which is why they almost all say do not connect them to the internet.

That being said, Windows with the help of one of several off the shelf software programs, such as Clean Slate, Rollback Rx, and Deep Freeze, can be fairly easily configured so that the chances of a virus are minimized, meaning that you wouldn't have to update Windows with every patch. In fact, this seems like a halfway decent mitigation (along with the aforementioned labeling) to your "device connected to the internet" hazard as part of your risk management.

(Picture by Alexander Fediachov)



Sunday, April 19, 2009

Getting contract manufacturers in line

I've spent a great deal of time recently corresponding with our US based main contract manufacturer on various quality issues, mostly paperwork. These guys assemble the electronic/computer part of the device and they're used to consumer electronics assembly. Using this company is about 40% cheaper than a company that specialized in medical device electronics and was ISO 13485 certified.

We basically came along, sent them our documentation SOP and told them to follow it while doing any work for us. This didn't happen so we have a bunch of Manufacturing Process Instructions (MPIs) that don't work as device history records (DHRs) and have a few dozen errors such as scribble outs, blanks, no calibration dates, etc that don't fly in the medical device industry. So we've rewritten everything for them and trained their line on what we require and made good progress. I've learned my lesson though and will hand hold the next group through the documentation requirements.

We also ended up providing them with calibrated test setups to make it easier to track equipment used and match what we expected. Now we're ready to go though and will be making thousands of these in no time! Or maybe closer to a dozen and then make a bunch of improvements, we'll see what happens.