IEC 62304 vs. General Principles of Software Validation

M

michel71

#1
Hi all,

I'm new in the cove,
We are a small company that are selling in US and around the world.
In the US we are medial device class 2, 510k exempt. We are NOT medical in the rest of the world.
We are ISO 13485 certificated and comply with 21 CFR 820.

Our product is integrating with software, so we are developing our software system in compliance with IEC 62301 norm.
I just read FDA General Principles of Software Validation and i think that i still don't comply with FDA with IEC 62301.

Please can someone help
 
Elsmar Forum Sponsor

yodon

Staff member
Super Moderator
#2
Where, specifically, do you think you don't comply with FDA guidelines or requirements? I think it will be easier to address specific questions rather than to consider generalities.
 
M

michel71

#3
Hi yodon,

Thank for quick response.

To be more specific. IEC 62304 field of application stipulate "This standard does not cover validation and final release of the MEDICAL DEVICE, even when the MEDICAL DEVICE consists entirely of software".

My question is: Since IEC 62304 doesn't cover validation, do i have to use the FDA general principles validation to validate my Medical Device?
 

glork98

Involved In Discussions
#4
My question is: Since IEC 62304 doesn't cover validation, do i have to use the FDA general principles validation to validate my Medical Device?
Yes. Exactly.

Use of the V&V terms is often perplexing. Software testing determines that the software does what it is supposed to do. (Often called "Verification"). Then system-level testing and use-level testing is the "validation" that show it accomplishes its purpose.

If your product was pure software, having verified the software have you validated the product? I'd say you were almost there. The full product would include manuals and training materials that the software verification wouldn't address. If you've got good requirements above the software level (E.g., Customer Requirements) then you'd test against those.
 

yodon

Staff member
Super Moderator
#5
glork98 is spot on, but let me just reinforce from another angle.

If you're selling a medical device in the US, you are compelled to follow the QSR (21 CFR 820). This is law. So you can follow 62304 but you are still required to meet all applicable aspects of the law first. Hopefully that puts it in perspective.
 

sagai

Quite Involved in Discussions
#7
Actually, the one of the nicest confusion in the FDA guidances, what they consider software validation and what is per definition the design validation. These two are far not the same by definition, however it can be when there is a software only medical device.
br
Sz.
 

rothlis

Involved In Discussions
#8
I know this is an old thread but I ran across this and felt the need to vent. To expand on Sagai's comment, I personally dislike the language in the FDA's "General Principles of Software Validation" because it implies that nearly every facet of the development life cycle is part of validation. Reliance on this guidance has led to a lot of confusing language in our quality system where it pertains to software. The bulk of the guidance discusses activities that are not normally considered validation - planning, requirements, design, design review, implementation, code review, verification, etc... These are all adequately addressed in IEC 62304.

To further complicate this, when the guidance actually does address validation, it blends it into two distinct ideas - system testing and user site testing. It defines system testing as occurring at the target environment and potentially under an IRB or IDE approval. Then it goes on to define "user site testing" as "any other testing that takes place outside of the developer’s controlled environment". Don't these sound like the same thing? The rest of the "user site testing" section is actually clearly addressing installation activities, not design validation.

In the real world, System Testing should be viewed as it is described by 62304. This is a verification activity to show that everything works when you put all the pieces together (did we build the software system right). 62304 does not address the next step, which is where you put the software into the users hands and evaluate whether it meets their needs (did we build the right software system). The FDA guidance does allude to this step but it does so in a very confusing way, as noted above. You're better off learning what validation means in the context of a product and relying on that understanding (see section G of the Design Control guidance).

OK, I'm done venting.
 

Pads38

Trusted Information Resource
#9
Annex C of 62304 shows it's relationship with other standards.

Figure C.2 shows which parts of the "V" model of verification and validation are part of 62304 and which have to be additionally addressed. It's not very clear when you first look at it but is worth having a look at.
 
Thread starter Similar threads Forum Replies Date
M Risk Analysis Flow - Confusion between ISO 14971 and IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 7
D IEC 62304 Risk Classification - With and without hardware control IEC 62304 - Medical Device Software Life Cycle Processes 2
M IEC 62304 Class A Project IEC 62304 - Medical Device Software Life Cycle Processes 15
B Clause 5.1.12 of Technical Standard IEC 62304/A1 IEC 62304 - Medical Device Software Life Cycle Processes 4
P IEC 62304 - evaluation of integration and system testing IEC 62304 - Medical Device Software Life Cycle Processes 4
P Risk acceptability alignment between ISO 14971 and IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 6
D Required Checklist Showing Compliance to IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 11
P Proposed revision of IEC 62304 - 2019 IEC 62304 - Medical Device Software Life Cycle Processes 6
S Relationship between IEC 62304 problem resolution and ISO 13485 IEC 62304 - Medical Device Software Life Cycle Processes 8
P IEC 62304:2006 A1:2015 - Software from the early 1990s IEC 62304 - Medical Device Software Life Cycle Processes 4
B IEC 62304:2015 vs IEC 62304:2006 + AMD1 IEC 62304 - Medical Device Software Life Cycle Processes 4
F IEC 62304 - Segregation and communication between software items IEC 62304 - Medical Device Software Life Cycle Processes 1
B Class IIB Device - IEC 62304 Software Classification IEC 62304 - Medical Device Software Life Cycle Processes 13
B IEC 62304 - Update Checklist IEC 62304 - Medical Device Software Life Cycle Processes 2
L Connection between IEC 62304 and Chapter 14 of IEC 60601-1 IEC 60601 - Medical Electrical Equipment Safety Standards Series 2
M IEC 62304 - Develop an Architecture for the Interfaces of Software Items IEC 62304 - Medical Device Software Life Cycle Processes 8
S Does IEC 62304 require documenting unresolved anomalies for all safety classes? IEC 62304 - Medical Device Software Life Cycle Processes 4
A SOP for software validation of software in medical device IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 5
T I need to make test reports according IEC 62304 & IEC 62366 IEC 62366 - Medical Device Usability Engineering 2
D Changing software classification via software - IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 3
D Software as risk control - Confused on one aspect of IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 20
K Trying to figure out what satisfies a few aspects of IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 2
Y IEC 62304 Section 4.3(a) - 100% probability of failure IEC 62304 - Medical Device Software Life Cycle Processes 3
Y Application of IEC/EN 62304 at an advanced stage of software development IEC 62304 - Medical Device Software Life Cycle Processes 4
T Is there any requirement to be compliant with IEC 62304 while implementing ISO 13485 ISO 13485:2016 - Medical Device Quality Management Systems 5
L Documentation Planning - IEC 62304 Clause 5.1.8 IEC 62304 - Medical Device Software Life Cycle Processes 2
C Software for Medical Devices - Requirements Content for compliance with IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 1
W CPU BIST IEC 62304 - Embedded code has CPU instruction tests IEC 62304 - Medical Device Software Life Cycle Processes 2
K IEC 62304 Amd 1 2015 - Figure 3 – Assigning Software Safety Classification IEC 62304 - Medical Device Software Life Cycle Processes 11
K Risk Reduction by Risk Control: IEC:62304-Class C ISO 14971 - Medical Device Risk Management 15
C Per IEC 62304, are DHF documents Configuration Items? IEC 62304 - Medical Device Software Life Cycle Processes 5
P IEC 62304 AMD1:2015: What's new vs.the 2006 Edition? IEC 62304 - Medical Device Software Life Cycle Processes 4
F FDA PMK 510(k) - IEC 62304 Software Components Segregation Other US Medical Device Regulations 3
M IEC 62304 Applicability - GUI Control Software IEC 62304 - Medical Device Software Life Cycle Processes 3
B Our NB says that IEC 62304 is an ISO 14971 Requirement ISO 14971 - Medical Device Risk Management 1
B Clarification on interpretation of some EN ISO 14971:2012 & IEC 62304:2006 req's ISO 14971 - Medical Device Risk Management 46
H ISO 14971 vs. IEC 62304 vs. 98/79/EC vs. ISO 13485 (Software Medical Device) ISO 14971 - Medical Device Risk Management 1
D A desperate call for help - IEC 62304 software IEC 62304 - Medical Device Software Life Cycle Processes 5
B IEC 62304:2006/AMD1:2015 Changes for Class A Software IEC 62304 - Medical Device Software Life Cycle Processes 3
M IEC 62304, ISO 14971 and FDA Medical Device SW Guidance 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
K IEC 62304 - Compliance steps IEC 62304 - Medical Device Software Life Cycle Processes 2
K ISO 14971 and IEC 62304 - Medical Device Software House ISO 14971 - Medical Device Risk Management 9
S Software Test Report including IEC 62304 classification IEC 62304 - Medical Device Software Life Cycle Processes 4
A Mapping of IEC 62304 artefacts (SRS, SAD, etc) to the 820.30 phases IEC 62304 - Medical Device Software Life Cycle Processes 5
W IEC 62304 vs. IMDRF SaMD Guideline Risk Class IEC 62304 - Medical Device Software Life Cycle Processes 5
C New IEC/TR 80002-3 Guidance for IEC 62304 - June 2014 IEC 62304 - Medical Device Software Life Cycle Processes 2
R IEC 62304 was brought up during an FDA Inspection/Audit IEC 62304 - Medical Device Software Life Cycle Processes 6
O Electronic Fever Thermometer - Why not IEC 62304 Class C? IEC 62304 - Medical Device Software Life Cycle Processes 7
R IEC 62304 - Medical Device Wi-Fi Radio Requirements IEC 62304 - Medical Device Software Life Cycle Processes 5
A Dental Laser Certification IEC 62304 for a Firmware IEC 62304 - Medical Device Software Life Cycle Processes 1
Similar threads


















































Top Bottom