SBS - The best value in QMS software

Software bug fixes after shipping a product

A

anbknaga

Starting to get Involved
#1
#1
We have developed a mobile application that shows the data in real time from a medical device when paired. Since this app, just shows the flow rate details in real time, we are calling this as a "add-on service".

In future, if the organisation decides to update the UI/UX or make bug fixes, should we inform our customers or regulatory authority by a separate portal? or is it just enough to send a pop-up requiring them to update the app and that will be enough?
 
12 questions to ask before buying a QMS
Elsmar Forum Sponsor
Y

yodon

Staff member
Super Moderator
#2
#2
Probably not enough information to give a complete answer but let me toss out a few things. I don't know for example, if your device (software) requires FDA market clearance.

First, IEC 62304 is the standard for medical device software lifecycle. There is a section on maintenance and postmarket support.

Second, FDA has a guidance on when to submit a new 510(k) when changes are made. I don't know if you are required to submit a 510(k) but it shows their general thinking on the matter. (And do note that you should consider the accumulation of changes, not just each individual change independently.)

If this is considered 'general wellness' software then there's an FDA guidance on that which may give you some insight.

How you deal with your end users for an update is not specifically mandated but actions should be driven by risk. Again, not knowing your device, it's hard to say but if you had a bug that could lead to patient harm (possibly indirectly) then your actions would be elevated as opposed to a change for, say, just aesthetics.
 
mihzago

mihzago

Trusted Information Resource
#3
#3
as yodon said, not enough info to provide qualified response, it really depends on the type of change (e.g. risk involved) and classification of your device. If you're fixing defect to address safety issue (e.g. did you provide incorrect data?) or violation of the act (e.g. your device did not perform as advertised), then you have to consider 21 CFR 806 and possibly 803.
 
dgrainger

dgrainger

Trusted Information Resource
#4
#4
Looks like it qualifies as an accessory to the device. Is this add-on function mentioned in the device's IFU or any promotional materials?
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
A Software Medical Device Bug Fixes: Correction or Corrective Action? Other US Medical Device Regulations 5
R In a software development company: Is every bug reported by the customer a complaint? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 27
S SW (Software) Deferred Bug Fix - FDA Requirements IEC 62304 - Medical Device Software Life Cycle Processes 4
N Ways to avoid injected bugs while Bug fixing (software) Problem Solving, Root Cause Fault and Failure Analysis 5
D Letter to inform customers about software bug ISO 13485:2016 - Medical Device Quality Management Systems 4
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
J Do Software Subcontractors need to be ISO13485 compliant in the EU? EU Medical Device Regulations 3
D Safety data sheets software REACH and RoHS Conversations 2
N What are the software audit and control steps Reliability Analysis - Predictions, Testing and Standards 2
N Validating Software before getting approved as Class 2 device US Food and Drug Administration (FDA) 5
M Clinical Decision Support Software Question 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
P Missing 1m visual alarm signal in case of software/display failure, mitigation? ISO 14971 - Medical Device Risk Management 3
B Software service provider as critical supplier ISO 13485:2016 - Medical Device Quality Management Systems 4
S Asterisk in DOE minitab software Using Minitab Software 23
M Surgical angle measurement guide device with an application software Medical Device and FDA Regulations and Standards News 1
M Advice needed for SEH Compliance Software and ISNETWord Compatabiliy Occupational Health & Safety Management Standards 2
bruceian Software Quality Metrics Software Quality Assurance 11
optomist1 How Secure Are Our Software Systems Software Quality Assurance 7
M 'Active' device? Software/laptop with attached camera 'looking' at passive metal probe EU Medical Device Regulations 3
D Software validation team Misc. Quality Assurance and Business Systems Related Topics 3
O Any info on release date of FDA “Computer Software Assurance for Manufacturing and Quality System Software” document? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 0
L Radiology software Class I exemption Medical Device and FDA Regulations and Standards News 3
O Software for comparing text of PDF files Contract Review Process 2
J Implementing an ISO 13485 QMS Software ISO 13485:2016 - Medical Device Quality Management Systems 6
K Software Updates in the Field and ISO scope ISO 13485:2016 - Medical Device Quality Management Systems 2
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 3
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 1
J Medical software Patient outcome Medical Information Technology, Medical Software and Health Informatics 2
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 7
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

Similar threads

Top Bottom