Standalone Medical Device Software Qualification

N

NarK1

#1
Dear All!

Could you please help me to define the qualification of our standalone software.
The intended use of the software is the following:
This is a remote monitoring software solution intended to collect and store data from physiological measurement to use at home. It also allows for the automated transmission of the data to a remote secure server and the storage in a database. Then the data will be available for consultation in the web by the user and clinicians for analysis and intervention. The device can be used as a standalone device or in conjunction with supported patient monitoring devices, such as a glucose meter, weight scale, pulse oximeter, blood pressure monitor and thermometer. All these sensors already have CE marking according with 93/42/EEC and 98/79/EEC directives. One solution of the software provides real-time monitoring and another with emergency monitoring emitting alerts.

1. We have two kinds of solutions. One with storing functions and another with storing and alert functions. Are they both medical devices?
By using figure 1 in MEDDEV 2.1/6 - Qualification and Classification of standalone software, storing is not covered by MDD and storing+alerts is covered by MDD. But in the recommendation NB-Med/2.2/Rec4 ? Software and medical devices, 3.1.1, iii), example 6, the two solutions can be medical devices.
And if I use figure 2 in MEDDEV 2.1/6, storing+alerts is a IVD device ? because of the glucose meter sensor. Which one is right in your opinion?

Kind regards
 
Elsmar Forum Sponsor

bio_subbu

Super Moderator
#2
Dear All!

Could you please help me to define the qualification of our standalone software.
The intended use of the software is the following:
This is a remote monitoring software solution intended to collect and store data from physiological measurement to use at home. It also allows for the automated transmission of the data to a remote secure server and the storage in a database. Then the data will be available for consultation in the web by the user and clinicians for analysis and intervention. The device can be used as a standalone device or in conjunction with supported patient monitoring devices, such as a glucose meter, weight scale, pulse oximeter, blood pressure monitor and thermometer. All these sensors already have CE marking according with 93/42/EEC and 98/79/EEC directives. One solution of the software provides real-time monitoring and another with emergency monitoring emitting alerts.

1. We have two kinds of solutions. One with storing functions and another with storing and alert functions. Are they both medical devices?
By using figure 1 in MEDDEV 2.1/6 - Qualification and Classification of standalone software, storing is not covered by MDD and storing+alerts is covered by MDD. But in the recommendation NB-Med/2.2/Rec4 – Software and medical devices, 3.1.1, iii), example 6, the two solutions can be medical devices.
And if I use figure 2 in MEDDEV 2.1/6, storing+alerts is a IVD device – because of the glucose meter sensor. Which one is right in your opinion?

Kind regards
Hi

It Seems like "Aging in Place" product. Aging in Place is a system for home care monitoring (for care recipients(aged people at home)) uses through Information technology (IT) and mobile telecommunication to monitor the patient’s health remotely. Can you please confirm or provide some additional information?.
 
N

NarK1

#3
Hello,

First of all, thank you for your reply. You are correct, the remote monitoring software is used for all people that need to control their blood pressure, heart rate, temperature, glucose and weight. This software will be implemented in a tablet or pc and connect to this are the respective sensors. This data will then be available for consultation in the web by the user or clinicians. This software has two different solutions, one only stores, represent and transmit the data and the other can to the same plus signal an alert if the physiological values are in critical values. My question is if the two solutions are covered under medical devices directives. If you need more information please just ask.

Kind regards,
 

Marcelo

Inactive Registered Visitor
#4
If any of the monitoring (storage or not) intends to alert for a clinical situation based on the sensors, and then someone has to act upon the monitoring, then it?s a medical device.

The risk class will be based on the risk classes of the monitored parameters (the most strict).

Note that even your mention of "represent" may make it a medical device because your representation, for example, can include some calculation on the data to fit the presentation format.
 
N

NarK1

#5
Obrigado Marcelo. I have a question, when you wrote "The risk class will be based on the risk classes of the monitored parameters (the most strict)" but by the MEDDEV 2.4/1 Rev.9, page 43, Note 1, "Vital physiological processes and parameters include, for example respiration, heart rate, cerebral functions, blood gases, blood pressure and body temperature. Medical devices intended to be used for continuous surveillance of vital physiological processes in anesthesia, intensive care or emergency care are in Class IIb, whilst medical devices intended to be used to obtain readings of vital physiological signals in routine check ups and in self-monitoring are in Class IIa.". So the classification is by the most strict monitored parameter or by the intended use of the device? By the way do you think is class IIa or IIb? By the above note I think is IIa but I'm not sure, if you have another type of guidelines that you can recommend it will be very helpful.

Kind regards,
 

Marcelo

Inactive Registered Visitor
#6
It would be by the intended use of the device that gets the parameters. One way to think about this is that your device is an "extension" of the other device, so if the other device is intended to be used in anesthesia, and due to this it is a class IIb (that comment is just generic anyway, you know), the your device would be a class IIb.
 
Last edited:
I

isoalchemist

#7
:2cents:Although you are talking MEDDEV, take a look at the FDA Medical Device Data System classification. If I understand correctly you are collecting data from "approved" medical devices and allowing that information to be communicated.

That is different than if you are developing or controlling the collection device and software. You are in a very interesting area that walks the line between unregulated, to Class I to Class II depending on the features in the US. The same appears true in the MEDDEV so it is important to really define what your system does and how it does it to make your determinations.
 
Thread starter Similar threads Forum Replies Date
K Standalone software - an accessory to medical device? EU Medical Device Regulations 4
Michael Malis Standalone Software as a Medical Device Other Medical Device and Orthopedic Related Topics 1
T Safety Classification in Medical Device Standalone Software IEC 62304 - Medical Device Software Life Cycle Processes 26
D Research Use Only Medical Device - Standalone software product 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 12
N Application of ISO 14971 to Medical Standalone Software ISO 13485:2016 - Medical Device Quality Management Systems 2
P IMDRF (International Medical Devices Regulators Forum)guidance on standalone software Medical Information Technology, Medical Software and Health Informatics 1
I CE Mark for Standalone Medical Computer Monitoring Software IEC 62304 - Medical Device Software Life Cycle Processes 5
L Regulatory Requirements for Medical Devices (Standalone-software) in Brunei Other Medical Device Regulations World-Wide 3
S Directives for Classifying Standalone Software as Medical Devices CE Marking (Conformité Européene) / CB Scheme 3
P ER13.3 for standalone software CE Marking (Conformité Européene) / CB Scheme 8
K Unique Device Identifier for updates to legacy standalone software Other US Medical Device Regulations 1
D Essential Requirements Checklist for Standalone Software CE Marking (Conformité Européene) / CB Scheme 10
T FDA proposed labeling standalone software cloud based US Food and Drug Administration (FDA) 4
I DMR (Device Master Records) and similar for standalone software device 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
O Should ISO 9001:2008 be treated as a standalone quality standard alongside AS9120A? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
Q UDI and Standalone Software - UDI per installation? Other Medical Device Related Standards 6
N Standalone Corrective Action Procedure or Integrated Nonconformance and Corrective Action 5
T ISO 17025 Standalone or Must Have ISO 9001 Companion ISO 17025 related Discussions 8
D ESD Quantification - Standalone instrument that can log ESD field strength ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 6
B Does FDA Registration QSR need to cover non-medical devices for contract repackager? US Food and Drug Administration (FDA) 0
A Brexit Mandate for EU Authorised Representative for non medical devices CE Marking (Conformité Européene) / CB Scheme 3
A Canadian Safety Labels for medical electrical equipment Canada Medical Device Regulations 0
A Applicability of Photobiological Safety Evaluation for LED used in medical devices Reliability Analysis - Predictions, Testing and Standards 1
M Medical device certificate in Australia - ARTG certificate Other Medical Device Regulations World-Wide 0
Q Software as a medical device vs software not sold as medical device: local regulations for sale? EU Medical Device Regulations 4
H Medical device Product Registration Registrars and Notified Bodies 2
T Google Fit Health datas and Medical devices Application Medical Information Technology, Medical Software and Health Informatics 0
A Can a power Supply be an accessory to a medical device, if it is an 'off-the-shelf' product. IEC 60601 - Medical Electrical Equipment Safety Standards Series 3
B Procedure packs with non-medical devices EU Medical Device Regulations 1
A Medical device labelling Date of manufacture US Food and Drug Administration (FDA) 2
W Non Sterile Medical Device Environmental Tests Other Medical Device Related Standards 4
ebrahim QMS as per ISO 13485, Clause 4.2 Requirements for regulatory purposes for Medical Devices Authorized Representatives. ISO 13485:2016 - Medical Device Quality Management Systems 3
A Clinical assessment sample size - Medical device Class IIb implantable (93/42 directive) EU Medical Device Regulations 2
K 25-year lifetime of medical device - document storage period EU Medical Device Regulations 1
K Relabeling an existing medical device in the field? Other US Medical Device Regulations 6
J Should a Class 1 medical device with an option to measure body weight be considered Class 1m? EU Medical Device Regulations 0
A Reliable sources for following EU medical device regulatory EU Medical Device Regulations 0
T IVDR Medical device software CE Marking (Conformité Européene) / CB Scheme 8
A Customer Approval (Medical Devices) Document Control Systems, Procedures, Forms and Templates 4
N ISO 13485 7.3.9 Change control in medical device software ISO 13485:2016 - Medical Device Quality Management Systems 6
J Requirements as a Distributor for Incoming Inspection of Purchased Finished Medical Device Medical Device Related Regulations 0
S Microwave medical waste disinfectant - A medical device or not? Other ISO and International Standards and European Regulations 3
S Registration of Medical Device in Hong Kong - labeling requirements Other Medical Device Regulations World-Wide 0
D Electrical Medical Devices class I EU Medical Device Regulations 0
J Are complaints applicable to development of medical devices? Customer Complaints 2
V Software as medical device (SaMD) replicated for multiple clients through APIs IEC 62304 - Medical Device Software Life Cycle Processes 5
M Is the output of a device a Medical Device? IEC 62304 - Medical Device Software Life Cycle Processes 5
P Do we need to retrospectively use the "MD" symbol (indicating device is a medical device) on labels, e.g. finished devices within expiration date? EU Medical Device Regulations 2
M Do I need separation in my circuit with a medical charger? IEC 60601 - Medical Electrical Equipment Safety Standards Series 0
L Medical device registration in Iran Other Medical Device Regulations World-Wide 0

Similar threads

Top Bottom