SBS - The Best Value in QMS software

Is my software an accessory? Telecommunication between HCP and patients

Cali_Kitson

Starting to get Involved
#1
‘accessory for a medical device’ means an article which, whilst not being itself a medical device, is intended by its manufacturer to be used together with one or several particular medical device(s) to specifically enable the medical device(s) to be used in accordance with its/their intended purpose(s) or to specifically and directly assist the medical functionality of the medical device(s) in terms of its/their intended purpose(s);

Hey all, looking for some opinions on a point of contention.

Our software's intended use is for telecommunication between HCP and patients. However it also allows images from our camera device to be viewed and captured. Our hardware can be used with any old tablet, laptop or computer, however it is supplied with an accessory - a docking case integrated with a tablet, which is loaded with our software.

As the software does not "specifically" enable the device to be used, are we safe to say it is not an accessory?

Please fire away with your opinions.
 
Elsmar Forum Sponsor

Cali_Kitson

Starting to get Involved
#3
Hi @shimonv, thanks for your reply!

The device is a handheld endoscope. The device can function without the software, but they are packaged together. The software does not modify the information captured by the camera in anyway.
 

shimonv

Trusted Information Resource
#4
Okay, I don't know enough about it, but it seems you could argue that you software is like a carrying case for the endoscope; it provides secondary services that are not essential for the primary use of the device.
I assume you are heading this way because you would like to classify it separately, and hopefully as class I.

Good luck.
Shimon
 

Cali_Kitson

Starting to get Involved
#5
Thanks Shimon.

Our interpretation of the guidance would lead us to believe that this would not be classified as a stand-alone medical device (SAMD) under the MDR.

The software will become a SAMD in the future (2/3 years down the line), as it will feature diagnostic functions. However, at this point, we are trying to avoid classification as an accessory to prevent unnecessary work whilst we are extremely busy!
 

yodon

Staff member
Super Moderator
#6
Does the tablet (via the software) hold the images taken by the endoscope? Do the HCPs collect any data about the case on the tablet / with your software? How are the communications between HCP and patient facilitated by your software and does it hold those communications?

Given the limited info, it's, as @shimonv says, hard to say for sure but, to me, it sounds more like it IS a SaMD (not an accessory).
 

Cali_Kitson

Starting to get Involved
#7
Thanks for this @yodon - you're input is much appreciated.

The software captures the images taken by the endoscope and they are held in the cloud.

HCPs do not collect any data about the case with the software.

The software allows real time communication between users of the application but those communications are not stored - neither in the cloud or on the tablet (it is just like Skype with a UI geared towards healthcare).

We used the following guidance to make the decision around the software and whether it is classified as an SaMD... https://assets.publishing.service.g.../890025/Software_flow_chart_Ed_1-06_FINAL.pdf
 

yodon

Staff member
Super Moderator
#8
It's a gray area. I know that PACS (Picture Archiving and Communication Systems) are regulated in the US.

In the IMDRF document "SaMD: Possible Framework..." in the examples section in the appendix, they state:

Software that is connected to a hardware medical device but is not needed by that hardware medical device to achieve its intended medical purpose is SaMD and not an accessory to the hardware medical device. For example, software that allows a commercially available smartphone to view images for diagnostic purposes obtained from a magnetic resonance imaging (MRI) medical device is SaMD and not an accessory to MRI medical device.

I guess it all depends on claims. I tend to suggest the conservative route.

If, as you say, you do intend to market the software as a device in the future, you'd probably be well-served by at least doing the development now under 62304. And since you say it will provide diagnosis, that raises the bar considerably.
 

Cali_Kitson

Starting to get Involved
#9
I am also risk-averse @yodon, therefore totally agreed development under 62304 must be adapted sooner rather than later.

The guidance you sent has thrown me off even more! The example in the appendix seems to relate very closely to our situation.
 
Thread starter Similar threads Forum Replies Date
D Software as an accessory to a Class I medical device EU Medical Device Regulations 4
N Medical Device Accessory Classification - Software as a Medical Device Other Medical Device Regulations World-Wide 5
D Software as a Medical Device Accessory Software Quality Assurance 2
K Standalone software - an accessory to medical device? EU Medical Device Regulations 4
D Windows CE Operating System - Implantable Blood Pump and a Software Accessory Device IEC 62304 - Medical Device Software Life Cycle Processes 8
A Software contained in a Medical Device Accessory IEC 62304 - Medical Device Software Life Cycle Processes 3
S USB Cable (an accessory to our data management software) Changes and 510k IEC 62304 - Medical Device Software Life Cycle Processes 2
J Software as a Medical Device - SaMD IEC 62304 - Medical Device Software Life Cycle Processes 3
BeaBea QMS/ Training Management Software Service Industry Specific Topics 4
shimonv Working with a software developer who is not setup for IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 9
R Debug mode in software/device validation IEC 62304 - Medical Device Software Life Cycle Processes 2
Q Gage calibration / tracking software General Measurement Device and Calibration Topics 2
M Software verification and validation AS9100 AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
Y RT-qPCR Software result EU Medical Device Regulations 0
B A.I diagnostic software is considered as medical device in FDA? US Food and Drug Administration (FDA) 5
F WANTED Senior Software engineer Career and Occupation Discussions 2
P Blood establishment computer software EU classification EU Medical Device Regulations 0
S Examples of FDA acceptable Software Design Specification (SDS) Medical Device and FDA Regulations and Standards News 6
D Integrated Management System Software Quality Manager and Management Related Issues 2
B Sampling strategies/techniques for software QA Software Quality Assurance 2
K MDCG-2020-3 (about the software of UI) EU Medical Device Regulations 3
D PFMEA Software search IATF 16949 - Automotive Quality Systems Standard 6
C MDR software classification EU Medical Device Regulations 12
H Class II a vs "software safety class A" IEC 62304 - Medical Device Software Life Cycle Processes 3
Z Software for design control ISO 13485:2016 - Medical Device Quality Management Systems 5
V Medical Device Literature Translation Software ISO 13485:2016 - Medical Device Quality Management Systems 1
D FDA Guidance on Computer Software Assurance versus 21 CFR Part 11 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
P Software verification and validation procedure IEC 62304 - Medical Device Software Life Cycle Processes 6
Aymaneh UDI-PI Software CE Marking (Conformité Européene) / CB Scheme 0
Q Software as a medical device vs software not sold as medical device: local regulations for sale? EU Medical Device Regulations 4
Y Software updates considered servicing (7.5.4) ISO 13485:2016 - Medical Device Quality Management Systems 4
S How to perform verification of the Statistical Analysis Software? Qualification and Validation (including 21 CFR Part 11) 7
I Document Control Software Document Control Systems, Procedures, Forms and Templates 2
E Software maintenance Process Software maintenance Process to IEC 6204? IEC 62304 - Medical Device Software Life Cycle Processes 3
L Micro-Vu InSpec Software Program Qualification and Validation (including 21 CFR Part 11) 6
A For software change - New Channel of interoperability CE Marking (Conformité Européene) / CB Scheme 5
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
C SharePoint Contract Management Software General Information Resources 0
gramps What do you think about automated QA testing For software app industry? Misc. Quality Assurance and Business Systems Related Topics 5
V Software as medical device (SaMD) replicated for multiple clients through APIs IEC 62304 - Medical Device Software Life Cycle Processes 5
U API Spec Q1 - 5.6.1.2 C (3) - Design software Oil and Gas Industry Standards and Regulations 3
B Complaint Records - Accessing records on Easy Track Software Records and Data - Quality, Legal and Other Evidence 3
GreatNate Master Control QMS software Quality Tools, Improvement and Analysis 1
GreatNate Anyone using the Intellect QMS software? Quality Assurance and Compliance Software Tools and Solutions 1
S DHF/DMR/MDF for a software-only, cloud-based, single-instance device Medical Information Technology, Medical Software and Health Informatics 2
H Software Validation for FFS Packaging Machine Qualification and Validation (including 21 CFR Part 11) 1
E Any sample of a full software life cycle IEC 62304 report ( any class )? IEC 62304 - Medical Device Software Life Cycle Processes 1
Q ISO 13485 7.5.6 Validation - Off the shelf Software ISO 13485:2016 - Medical Device Quality Management Systems 3
M ERP / QMS related software standards for Validation IEC 62304 - Medical Device Software Life Cycle Processes 6

Similar threads

Top Bottom