Medical Device Software Level of Concern Determination

S

Silvertabb

#1
If you have Device A that has its own software, but you decide to connect it to a standalone software installed on a PC which just extract data/information from Device A and provides reports and other data management related function. When submitting a 510k for the stand alone SW, one is required to indicate the Level of Concern for the SW based on FDA 2005 for Devices containing SW.
Since the Standalone SW is an accessory, one would need to answer the following (Q3). Is the Level of Concern in this case related to the SW(installed on the Device A and not the standalone SW) pre-mitigation hazards- meaning does one have to look up the Hazard Analysis for the Device A and if pre-mitigation hazard Severity is "Potential death or serious injury" then the level of concern for the standalone SW is "Major"? Or other aspect of Device A need to be considered as well.
If the answer to any one question below is Yes, the Level of Concern for the​
Software Device is likely to be Major.

3. Is the Software Device an accessory to a medical device that has a Major Level of​
Concern?
 
Elsmar Forum Sponsor

yodon

Staff member
Super Moderator
#2
I think your assertion that the stand-alone software is an accessory is incorrect. The stand-alone software has its 510(k) based on its functions. The software happens to receive data from a device. I would assess the level of concern of the stand-alone software without consideration of the input source (consider it a black box).

Does that help?
 
S

Silvertabb

#3
yodon,
this standalone SW has a 510k and its own hazard analysis. However, the guidelines as I stated in my first post asks whether or not this standalone device is connected to a device that has a major level of concern. In my case, both class II and Class III can use this SW. So to determine the SW concern level I need to know whether or not I should consider on the pre-mitigation SW hazard of the device to which this standalone SW will be connected to extract data or all hazards associated.
 
G

George Weiss

#5
The FDA has 510K database(s) for similar items. A search through these databases might give some common sense guidance. Depending on the application, this software could be the remote output of vital information.
The degree of seriousness or device class would influence the level of software validation. The application could be a few lines of code, (indicating on/off), or a suite of seriously manipulated data graphics.
YEP! in short I would follow the other 510K filers..............
 

yodon

Staff member
Super Moderator
#6
yodon,
this standalone SW has a 510k and its own hazard analysis. However, the guidelines as I stated in my first post asks whether or not this standalone device is connected to a device that has a major level of concern. In my case, both class II and Class III can use this SW. So to determine the SW concern level I need to know whether or not I should consider on the pre-mitigation SW hazard of the device to which this standalone SW will be connected to extract data or all hazards associated.
Maybe I'm not understanding the system. Is the stand-alone software required to use the device? Does the stand-alone software operate while the device is in use? My original thought was that the device does its thing, gathering data. Then you plug it into a PC (or whatever) and pass the data gathered to the stand-alone software. In this case, even though it connects to the device, it can't have an impact on the device use and so I wouldn't consider it in device hazard analysis.

If, however, the device is connected while it's being used or can influence the device then you should consider potential hazards with the device coupled with the software. I think that's what the guidance is driving at (potential influence on the device).

On the stand-alone software side, I still would consider the device as a black box that just provides inputs.
 

sagai

Quite Involved in Discussions
#7
It is only my impression is that the case is that these two devices in the reality is one medical device and the company (there could be several professional or other reasons) decided earlier to clear the monitoring device first, but now, facing with this issue.
br.
Sz.
 
S

sl344

#8
Hello everyone,

I'm also very confused by the software classification in IEC 62304. here is my situation. We have a product, a class III medical device, that contains a very simple piece of software do control the device to start/stop. Lets say the software can't cause any harm to the patient. Can the software be classified as Class A? Thanks.
 
S

sl344

#10
yes, what the software does is to start and stop the device. the rest of the device is electro/mechanical. If the software fails to start, there is no harm to patient; if it fails to stop, it may cause some discomfort, but there is no possibility that the patient will get hurt. with this said, do you think the software can be classified as Class A?
 
Thread starter Similar threads Forum Replies Date
Q Software as a medical device vs software not sold as medical device: local regulations for sale? EU Medical Device Regulations 4
T IVDR Medical device software CE Marking (Conformité Européene) / CB Scheme 8
N ISO 13485 7.3.9 Change control in medical device software ISO 13485:2016 - Medical Device Quality Management Systems 6
V Software as medical device (SaMD) replicated for multiple clients through APIs IEC 62304 - Medical Device Software Life Cycle Processes 5
R Medical Device Software Certification IEC 62304 - Medical Device Software Life Cycle Processes 1
Q Storing and developing SAMD (Software as a Medical Device) in the Cloud IEC 62304 - Medical Device Software Life Cycle Processes 3
MDD_QNA Medical Device Software - Is a Help Button required? IEC 62304 - Medical Device Software Life Cycle Processes 1
F Software as a Medical Device (SaMD) Technical File Requirements Manufacturing and Related Processes 3
A Software as Medical Device (SaMD) definition and its applicability Other Medical Device and Orthopedic Related Topics 4
T First 510(k) submission - Class II software as medical device US Food and Drug Administration (FDA) 4
Z Software Library - could it be a medical device? ISO 13485:2016 - Medical Device Quality Management Systems 5
M Informational TGA – Submissions received: Regulation of software, including Software as a Medical Device (SaMD) Medical Device and FDA Regulations and Standards News 1
D Requirements for the dimensions / color of medical device labels - Software as a Medical Device IEC 62304 - Medical Device Software Life Cycle Processes 2
D Software as an accessory to a Class I medical device EU Medical Device Regulations 4
R Medical device software without user interface Other Medical Device and Orthopedic Related Topics 3
R Validation of Medical Device Hardware containing Software - How many to Validate ISO 13485:2016 - Medical Device Quality Management Systems 1
Ed Panek Rule 11 Question - CE approvals for software as well as the medical device EU Medical Device Regulations 7
D IEC 60601 for a Software only Medical Device? IEC 60601 - Medical Electrical Equipment Safety Standards Series 5
S Software Release Note - Class A stand alone software medical device IEC 62304 - Medical Device Software Life Cycle Processes 2
M Professional Use Medical Software French Labeling for Canada -- Not Considered Medical Device Canada Medical Device Regulations 2
S Medical Device Software Distribution for a CE-marked medical device via a USB memory stick EU Medical Device Regulations 8
M Informational TGA – Webinar: An update on the consultation for the Regulation of Software, including Software as a Medical Device (SaMD) Medical Device and FDA Regulations and Standards News 0
J Qualification of a Software as a Medical Device (SaMD) guidance under MDR EU Medical Device Regulations 9
P Software requirement and design specifications - Medical device contains both hardware and software IEC 62304 - Medical Device Software Life Cycle Processes 2
M Informational TGA Consultation: Regulation of software, including Software as a Medical Device (SaMD) Medical Device and FDA Regulations and Standards News 0
N Medical Device Accessory Classification - Software as a Medical Device Other Medical Device Regulations World-Wide 5
R SaMD - Software as a Medical Device - Software change control form ISO 13485:2016 - Medical Device Quality Management Systems 3
G EU MDR 2017/745 Rule 11 interpretation - Re-classification of a Software as Medical Device Other Medical Device Related Standards 0
M Medical Device News TGA – Regulation of Software as a Medical Device Medical Device and FDA Regulations and Standards News 0
S Two Questions about Medical Device Software 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
K Medical Device Software Update in Field of AIMD IEC 62304 - Medical Device Software Life Cycle Processes 1
M Medical Device News Health Canada - Scientific Advisory Panel on Software as a Medical Device (SAP-SaMD) - Record of Proceedings – January 26, 2018 Canada Medical Device Regulations 0
R Online / Cloud Based Software as Medical Device EU Medical Device Regulations 8
S DMR (Device Master Record) for Medical Device Software IEC 62304 - Medical Device Software Life Cycle Processes 3
S Labelling in Medical Device Software IEC 62304 - Medical Device Software Life Cycle Processes 8
S What is considered the complete software medical device? Medical Information Technology, Medical Software and Health Informatics 6
JoCam Medical Device Software - Apps which can control medical devices EU Medical Device Regulations 13
L Software Medical Device - 7.3.8 - Design and Development Transfer ISO 13485:2016 - Medical Device Quality Management Systems 4
A SOP for software validation of software in medical device IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 5
K Registering a Software medical device (SaMD) in China China Medical Device Regulations 5
N Medical Device Software - Switch from Waterfall to Agile methodology Medical Information Technology, Medical Software and Health Informatics 4
V Software medical device labelling EU Medical Device Regulations 5
I Medical Device Software Risk Analysis ISO 14971 - Medical Device Risk Management 4
S If a piece of software receives approval as part of a medical device system Canada Medical Device Regulations 5
C Controlling Software Versions that are part of a medical device IEC 62304 - Medical Device Software Life Cycle Processes 2
S Cloud-Based Stand Alone Software - Software Medical Device (Class II) US Food and Drug Administration (FDA) 2
Q QMS Software for Startup Medical Device Company Other Medical Device and Orthopedic Related Topics 7
B CQC oversight of Medical device software? EU Medical Device Regulations 3
H Identifying Guidance on Medical Device Software Level of Concern for the EU EU Medical Device Regulations 2
B Is IEC TR 80002-1:2009 applicable to stand-alone medical device software? ISO 14971 - Medical Device Risk Management 1

Similar threads

Top Bottom