Wireless medicine and mobile health

April 4th, 2011 Posted by Software Lifecycle Management 0 thoughts on “Wireless medicine and mobile health”

Some links on this subject:
http://mobihealthnews.com/10495/fda-promises-regulatory-guidance-this-year

The wireless future of medicine: http://www.ted.com/talks/eric_topol_the_wireless_future_of_medicine.html

Risk Management, FMEA and ISO 14971

April 3rd, 2011 Posted by ISO 14971, Risk Management 0 thoughts on “Risk Management, FMEA and ISO 14971”

The risk management standard required by medical device manufacturers is ISO 14971.

The ISO14971 talks about risk management plan, risk management file, risk analysis, risk evaluation, risk control, production and post production, verification methods and more.

The FMEA (Failure Mode Effect Analysis) or FMECA (Failure Mode Effect Cause Analysis) is an acceptable risk management application that supports some parts described in ISO 14971.

Safety classification and level of concern

March 15th, 2011 Posted by FDA, Medical Device Directive 93/42/EEC 0 thoughts on “Safety classification and level of concern”

Software safety classification required by the CE (According to IEC 62304) is based on the product type. The classification is 1, 2a, 2b, 3 (major).

The FDA safety classification is called level of concern, and it talks about the potential harm to the patient/user. There is Class I, II, III.

There is a list of questions to ask in order to determine the safety classification, such as “Is the software part of a product with high risk”

The risk management is on system level and is not related to the level of concern

What is FMEA Technic for Risk Management

March 15th, 2011 Posted by ISO 14971, Risk Management 0 thoughts on “What is FMEA Technic for Risk Management”

FMEA – Failure Mode and Effect Analysis

Definition

A methodology to identify, quantify, prioritize and evaluate potential failure mode

Terms

Failure mode: What could go wrong

Effect analysis: How would it happen, how likely is it to go wrong, how bad would that be

Goals

  1. Reduce risk of failure
  2. Ensure failures are detectible
  3. Prevent failure from happening.

Prevention: A way to figure out what can go wrong and what can be done in order to avoid it

When

Ahead of time or during the project lifecycle when a potential risk is discovered

We do FMEA for procedures that can be risky or costly

Why

Preventing problem is cheaper than cleaning it

Some things are too risky or costly to incur mistakes

How

Gather all relevant participants from several verticals to give their insight of potential risks

  1. Analyze risks
  2. Define the most critical and include them in the control plan

Define potential failure mode for each Process (can have several failure modes)

  • Cause of failure (Root cause) – what might cause this failure mode
  • Effect of failure (Impact of failure)
  • Current control – what is done today in order to prevent the failure
  • Hazard Score (RPN=Risk Priority Number, is the product of Severity, Occurrence, and detection rating)
    • Occurrence/Probability (how likely to occur) [F]
    • Detection [D]
    • Severity [S]
  • Prevention/Mitigation/Control (recommended actions)
  • Revised RPN – after hazard mitigation

IEC 62304 main processes

March 9th, 2011 Posted by IEC 62304 0 thoughts on “IEC 62304 main processes”

IEC 62304 addresses the following main processes:

  • Software development plan
  • Software development
  • Software requirements analysis
  • Software architectural design
  • Software detailed design
  • Software unit implementation and verification
  • Software integration and integration testing
  • Software system testing
  • Software release
  • Software maintenance
  • Software risk management (refers to ISO 14971)
  • Software configuration management
  • Software problem resolution

Time consuming activities in medical device documents management

March 9th, 2011 Posted by Software Lifecycle Management 0 thoughts on “Time consuming activities in medical device documents management”

Following are activities that consume most of the time in maintenance and preparation of the documents for submission:

  1. Manual Signatures
  2. Traceability maintenance
  3. Document audit trail
  4. Manual management of changes and comments

I will discuss each on my next posts

The challenge of 510(k) De Novo submission decision

March 8th, 2011 Posted by Software Lifecycle Management 0 thoughts on “The challenge of 510(k) De Novo submission decision”

There is a real challenge for a medical device company whether to go for 510 (k) De Novo submission.

First – lets understand some facts :

  • For some historical reason – there is a dependency between risk level (Class I, II and III) and submission required  (510(k)/PMA)
  • For risk level of class I and II – the medical device company is required to be 510(k) cleared
  • For risk level of class III – a PMA submission is required

But what is the case when the product is not based on exisitng product and the risk level is not Class III?

If the company succeeds to prove this claim – a 510(k) De Novo submission is allowed

This submission process expose the comapnies to competition. Once the company is 510(k) De Novo cleared – it means that their product is an existing product…. now the competitors can create a competitive product and submit the 510(k) based on the “existing” company product. Another issue is the efforts need to be invested in order to convince the FDA that the risk level is not class III.

and finally – there is a risk in the exposure of the company IP by the FDA during the risk level re- evaluation process.

Due to these reasons the medical device company sometimes choose to go for the PMA.

What standards are required for medical device software?

March 2nd, 2011 Posted by 21 CFR part 820, IEC 62304, ISO 13485, ISO 14971 0 thoughts on “What standards are required for medical device software?”

There are lots of standards, and I sometimes find it confusig, where people dont really know what is the acceptable standard for software lifecycle in medical device, acceptable by the FDA and CE. Some vendors also claim t support specific standards, such as 21CFR 820, which has nothing to do with softwaare lifecycle in specific.

I came to the final conclusion:

The acceptable standard for software lifecycle management is IEC 62304, you can find some data about it in this blog

The ISO 14971 talks about risk management

The 21 CFR part 820 is more or lessthe same as ISO 13485 and they don’t talk about software lifecycle in particular (see this link for reference: http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=820 ). The software lifecycle is only one part.

The FDA guidelines for software lifecycle managemnt are specified in the General Principles of Software Validation, and they are very hard to understand. Thats why it is recommended to use the IEC 62304 guidelines.

Quality Management System (QMS)

March 2nd, 2011 Posted by Software Lifecycle Management 0 thoughts on “Quality Management System (QMS)”

A quality management system (QMS) is the organizational structure, processes, data management, product quality procedures and resources needed to implement for quality management.

ISO 13485 For Medical Device

March 2nd, 2011 Posted by ISO 13485, Software Lifecycle Management 0 thoughts on “ISO 13485 For Medical Device”

SO 13485:2003 specifies requirements for a quality management system where an organization needs to demonstrate its ability to provide medical devices and related services that consistently meet customer requirements and regulatory requirements applicable to medical devices and related services.

Source: http://www.iso.org/iso/catalogue_detail?csnumber=36786

Page 16 of 17
1 14 15 16 17
Orcanos

Contact

8 Tozeret Ha'aretz Street
Tel Aviv, Israel
+972-3-5372561
info@orcanos.com

Copyright © Orcanos, All rights reserved. | Privacy policy | Terms of use