< 1 min reading time
One of the themes I come across regularly with my medical product manufacturing clients is uneven skills in investigation and determining root cause through a rigorous and adequate Root Cause Analysis (RCA). In some cases, it is newer team members who have not yet been mentored or (preferably) fully trained. In other cases, it flows all the way to the senior staff and process owner levels (including CAPA procedures that only describe a single RCA tool like 5 Whys). The investigation analysis tools used in RCA are not intended to be used in isolation; they are intended to sequence from one to another until RCA is completed and a plan is formed. Recently, I came across this linked article. I think it does a nice, concise job of describing a typical RCA tool flow and how to apply that to corrective and preventive actions. Definitely not the deep dive, but an easy to apply and brief start to the topic. What do you think? Root Cause Analysis, Ishikawa Diagrams and the 5 WhysRoot cause analysis (RCA) may be limited to brainstorming and not fully thought-through ideas. Incorporate Ishikawa diagrams along with the 5 Whys in order to maximize your RCA efforts. source: https://www.linkedin.com/groups/78665/78665-6415205787378937856 Marked as spam
|
Meet your next client here. Join our medical devices group community.
Private answer
Partho Banerjee
We are also working on similar lines for streamlining Technical Services in our Organization. Its an effective tool.
Marked as spam
|
|
Private answer
Beluh Mabasa Ginting
Thank's . interesting article. Technical terms based upon the available data or evidence from FSCA need to be considered as well.
Marked as spam
|
|
Private answer
Antonin Cuc
I am a State investigator for H+S in Medical Devices in the medical workflow, for example by implanting Orthopadic implants in Human Body. The fatal Mass repeated medical mistakes by users - in Orthopadic Clinic, there are facts, when the Orthopads, Radiologists, Forensic Doctors don´t respect Technician requirements of Laws for Users - because their mixed in medical workflow the Technical and Medical acts, without respects Technician legal conditions - for lack of Techical legal knowledges. In the Orthopady Clinics CZ are ignoring Binary Logics - when a likehod mixed partial activitiíes with evaluation True, False derived resulting FALSE - never the Loss of Mass Patients lives could be justified and validated coded as "Unhappy of Patients in usual habits in limits requirements LEGE ARTIS CZ". Yearly there are needless heavy crippled and preliminary dying about 40 thousands Patients CZ with fatal agreements Justice CZ, Criminal Police CZ, Knowing Court Medical Insitutes CZ!
Marked as spam
|
|
Private answer
I had trouble getting past the first paragraph. I would completely disagree that this is a good problem statement: "Customer X reports 2 shafts with part numbers 54635v4 found in customer’s assembly department with length 14.5 +/-2 mm measuring 14.12 mm and 14.11 mm.” Why: 1) Part numbers (plural)? Only one is specified. 2) Were they FOUND with length of 14.5 +/- 2 mm, or with lengths of 14.12 mm and 14.11 mm? (I assume 14.5 +/- 2mm is the acceptance specification, but it says they were "found...with length 14.5 +/- 2 mm") 3) Both 14.12 mm and 14.11 mm are within the (assumed) specification - so what is the problem??
This is actually a horrible problem statement. Accuracy, clarity, and grammar are important! Marked as spam
|
|
Private answer
Salvatore Domenic Morgera
Another example of trying to resuscitate the cat after its been in the bag too, too long. Many medical devices fail (my experience is with medical devices whose focus is neurological dysfunction or neuropathies of different types) is, plain and simple, because the primary phenomena they pretend to address is not sufficiently well known and understood. The methods mentioned here and the many FEMA and ISO 14971 hours spent could be better spent up front in the research cycle. It is even difficult to get medical device manufacturers to understand that there are many POC's, and the most important one is that first, crude design concept that is closely integrated with a carefully thought out research cycle.
Marked as spam
|
|
Private answer
Yi Grace Lin
Agreed that 'uneven skills' may have contributed to the inapt execution of a rigorous and adequate Root Cause Analysis (RCA) however I would also consider the demand on resource including time and people (with proper skills) could potentially impede its adoption. My experience has been that often only high risk issues would warrant an in-depth RCA.
Marked as spam
|
|
Private answer
Christine Zomorodian
Now that we have migrated to the new form space, are there any more questions or insights into the tool selection and basic practice of Root Cause Analysis (RCA)? Marked as spam
|
|
Private answer
Deryk Flood
4 steps how to carry out RCA: https://www.qmswrapper.com/blog/4-steps-how-to-carry-out-rca Marked as spam
|
|
Private answer
Christine Zomorodian
Thank you, Deryk. Yet the link provided contains the same fault being discussed in my link: only suggesting one RCA tool for the analysis phase (5 Whys). Marked as spam
|
|
Private answer
Christine Zomorodian
For everyone on this thread: Marked as spam
|