Software Library - could it be a medical device?

#1
Hi all!

Let's suppose that I want to build a software library whose main aim is to transfer data from a medical device to a mobile phone app.
The library will be embedded into the app.

Does the library become a Software as Medical Device (SaMD) even if its only aim is to move data from the medical device to the smartphone app?

Thank you in advance.
 
Elsmar Forum Sponsor

John C. Abnet

Teacher, sensei, kennari
#2
Good day @zippo
ISO 13485 ; 3.11 defines medical device as follows...
medical device
instrument, apparatus, implement, machine, appliance, implant, reagent for in vitro use, software, material or other similar or related article, intended by the manufacturer to be used, alone or in combination, for human beings, for one or more of the specific medical purpose(s) of:
  • — diagnosis, prevention, monitoring, treatment or alleviation of disease;
  • — diagnosis, monitoring, treatment, alleviation of or compensation for an injury;
  • — investigation, replacement, modification, or support of the anatomy or of a physiological process;
  • — supporting or sustaining life;
  • — control of conception;
  • — disinfection of medical devices;
  • — providing information by means of in vitro examination of specimens derived from the human body;
and does not achieve its primary intended action by pharmacological, immunological or metabolic means, in or on the human body, but which may be assisted in its intended function by such means
Note 1 to entry: Products which may be considered to be medical devices in some jurisdictions but not in others include: — disinfection substances; — aids for persons with disabilities; — devices incorporating animal and/or human tissues; — devices for in vitro fertilization or assisted reproduction technologies.

[SOURCE: GHTF/SG1/N071:2012, 5.1]

In short, it may depend on what data is included in your comment..."...aim is to transfer data ..."

Hope this helps.

Be well

J. Abnet
 
#3
Thank you John, it does help.

Aim to transfer data means that the library will facilitate the transfer of measurements (performed by the medical device) and will save them into the mobile phone via a smartphone app.

Given your previous definition and my further explanation, would you convene that the library IS NOT a medical device?
 

John C. Abnet

Teacher, sensei, kennari
#4
@zippo , I would indeed interpret (based on your description) that it is NOT a medical device. The logic is that your data is not making any recommendation (treatment) nor is it diagnosing or monitoring (such as a diabetes glucose meter).

If I understand correctly, your concept would simply make existing data available to the user.

Hope this helps.

Be well.
 

yodon

Staff member
Super Moderator
#5
When you say "library" I think that typically means software that does not stand on its own. For example, a math library might contain a square root function that you can call from your application. It sounds like your transfer software stands on its own so unless I'm misunderstanding, maybe "library" is not appropriate here.

Next, does the phone app require this data transfer software? If so, and the app is considered a device, maybe this becomes more of an accessory (which I think pushes it up into the 'device' category).

Will other applications use the transfer software?

The IMDRF (formerly GHTF) has a number of documents on SAMD. If you look at the one on risk categorization, you could make an argument that it might be, depending on what the phone app is doing.

It's a gray area. I can't argue with @John C. Abnet's logic unless the phone app can't run without the transfer software.
 
#6
@zippo , I would indeed interpret (based on your description) that it is NOT a medical device. The logic is that your data is not making any recommendation (treatment) nor is it diagnosing or monitoring (such as a diabetes glucose meter).

If I understand correctly, your concept would simply make existing data available to the user.

Hope this helps.

Be well.
Exactly, the data merely represents measurements taken from the device, thus, the library will make them available to the App ( the user will use the App and never the library itself).

When you say "library" I think that typically means software that does not stand on its own. For example, a math library might contain a square root function that you can call from your application. It sounds like your transfer software stands on its own so unless I'm misunderstanding, maybe "library" is not appropriate here.
Yes indeed, the library does not stand on its own, it will be called from the application using it.

The IMDRF (formerly GHTF) has a number of documents on SAMD. [removed link because the forum doesn't allow me to post links yet] depending on what the phone app is doing.
Thanks for the link.
The scope of the phone app is not in my scope and it has yet to be defined. If the phone app turns out to be SaMD I guess that they will have to apply their own controls as per current regulations.

I really appreciate your inputs (feel free to add more).
 
Thread starter Similar threads Forum Replies Date
K Software Updates in the Field and ISO scope ISO 13485:2016 - Medical Device Quality Management Systems 0
M Recurrent event analysis software (python) General Auditing Discussions 2
Y UL 1998 Standard: software classes Software Quality Assurance 0
P Need a programmer for QVI's VMS software for optical inspection machine Inspection, Prints (Drawings), Testing, Sampling and Related Topics 0
S IEC 62304 software costs and time Medical Device and FDA Regulations and Standards News 3
S IEC 62304 - Software verification cost IEC 62304 - Medical Device Software Life Cycle Processes 3
Sravan Manchikanti Software Risk Management & probability of occurrence as per IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 8
I Form templates for software (iso9001) Document Control Systems, Procedures, Forms and Templates 0
H Software Interface Translation IVD Regulation EU Medical Device Regulations 0
C 8.5.1.1 Control of Equipment, Tools, and Software Programs - Questions about the extent of control of NC programs AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 5
M IEC 62304 Software changes - Minor labeling changes on the GUI IEC 62304 - Medical Device Software Life Cycle Processes 3
silentmonkey Rationalising the level of effort and depth of software validation based on risk ISO 13485:2016 - Medical Device Quality Management Systems 10
T Do I need a qualified compiler for class B software? IEC 62304 - Medical Device Software Life Cycle Processes 3
S Manufacturing Execution Systems Software Costs Manufacturing and Related Processes 0
E 13485:2016, Sections 4.1.6, 7.5.6 and 7.6 - Validation of Software - Need some Advice please ISO 13485:2016 - Medical Device Quality Management Systems 2
R Medical Device Software Certification IEC 62304 - Medical Device Software Life Cycle Processes 1
S HIPAA-compliant monitoring software (advice needed) Hospitals, Clinics & other Health Care Providers 0
A Software bug fixes after shipping a product EU Medical Device Regulations 3
J Medical software Patient outcome Medical Information Technology, Medical Software and Health Informatics 2
Y We are Looking for EASA LOA TYPE 1 experienced software developer Job Openings, Consulting and Employment Opportunities 0
F Grand Avenue Software, Q-Pulse or Qualio - which for a full eQMS? Medical Information Technology, Medical Software and Health Informatics 1
K SOUP (Software of Unknown Provenance) Anomaly Documentation IEC 62304 - Medical Device Software Life Cycle Processes 2
Q Storing and developing SAMD (Software as a Medical Device) in the Cloud IEC 62304 - Medical Device Software Life Cycle Processes 3
I Old Time Scatter diagrams for defect type and location- software Quality Tools, Improvement and Analysis 3
SocalSurfer AS9100 new certificate, but need QMS software, help Quality Assurance and Compliance Software Tools and Solutions 2
C Is my software an accessory? Telecommunication between HCP and patients EU Medical Device Regulations 10
K Verify Software Architecture - supporting interfaces between items IEC 62304 - Medical Device Software Life Cycle Processes 1
A What are the pros and cons of using an audit software for internal auditing? General Auditing Discussions 4
A Risk Number for each software requirement IEC 62304 - Medical Device Software Life Cycle Processes 7
R Shall a new UDI-DI be required when stand-alone software device's version is updated? EU Medical Device Regulations 1
R MSA for ATE (Automatic Test Equipment Embedded Software) Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 9
S MDR GSPR Clause 17 - Software Requirements EU Medical Device Regulations 2
L Turkish Requirements - Does the Software need to be translated? CE Marking (Conformité Européene) / CB Scheme 2
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 1
D Software User Interface Languages for LVD and IVD CE Marking (Conformité Européene) / CB Scheme 2
A Software as Medical Device (SaMD) definition and its applicability Other Medical Device and Orthopedic Related Topics 4
K Software Validation for Measurement Tools used in Process Validation ISO 13485:2016 - Medical Device Quality Management Systems 2
B ISO 14971 Applied to Software ISO 14971 - Medical Device Risk Management 2
N ERP Software Implementation Manufacturing and Related Processes 3
C NCR (Nonconformance System) Software Nonconformance and Corrective Action 7
U Document Approval - Software company ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
B Risk Assessment Checklist for Non product Software IEC 62304 - Medical Device Software Life Cycle Processes 1
MrTetris Should potential bugs be considered in software risk analysis? ISO 14971 - Medical Device Risk Management 5
S SOP for ISO 13485:2016 Quality related Software validation ISO 13485:2016 - Medical Device Quality Management Systems 9
J Designing new gauge tracking software IATF 16949 - Automotive Quality Systems Standard 4
T First 510(k) submission - Class II software as medical device US Food and Drug Administration (FDA) 4
B Notified Bodies for Software (MDR) EU Medical Device Regulations 1
C MDR - Question around software accesories EU Medical Device Regulations 2
S Software for Supplier Charge back and internal PPM General Information Resources 2

Similar threads

Top Bottom