Software change management

#1
Hi,
In this transition period between MDD and MDR, our notified body requires us to submit all our changes and our analysis of these changes (significant/non-significant) before any release of the software product.
This situation leads us to incredible situations where the NB ends up blocking everything under the pretext that it impacts usability. Moreover, they themselves admit that they do not understand everything about our technologies. This leads to numerous exchanges by phone or email that take weeks and weeks. It's impossible to get feedback in less than 2-3 weeks and to have direct contact with the person who reviews our files. It's endless.
On our side, we want to do things right 1/ for our users 2/ for regulatory compliance.
Would you have any advice to unblock the situation please?
 
Elsmar Forum Sponsor

Tidge

Trusted Information Resource
#3
Hi,
In this transition period between MDD and MDR, our notified body requires us to submit all our changes and our analysis of these changes (significant/non-significant) before any release of the software product.
This situation leads us to incredible situations where the NB ends up blocking everything under the pretext that it impacts usability.
Even if you aren't formally required to have prepared/submitted a software architecture because of safety classification (per 62304) or level-of-concern (per FDA), having one allows you to establish traceability to the tests necessary for regression testing... including any usability testing.

I can't make a personal assessment of what you are changing (in specifications or implementations) and have no idea of the level of summative testing that was originally done, so I don't have a "hot take" on whether or not the NB is over-stepping. When it comes to NBs and NRTLs there is a difference between "hand-waving" and "evidence-waving". My experience with NRTLs has been incredibly salty with respect to consensus standards that are not of the 60601-1 family (i.e. collaterals and particulars). I agree that it is quite frustrating to have an outside person at an authority (such as a test lead at a NRTL) ask a specific question in an area that involves a consensus standard like 14971, 62304, 62366-n, and when given the answer they don't know how to process it... because of ignorance and unfamiliarity with the consensus standard in question.

My response/approach has evolved to go something like this: "The thing you are asking about is something we put a lot of critical thought into and have lots of evidence to support our actions. The way you phrased the question inspires us to want to dump a LOT of records on you but we feel like you might need as much time to make your assessment as we took in ours along the path, and that is almost certainly not a good use of time. We aren't intended to fool you, but we realize there is likely a mere handful of documents that would satisfy your request. Do you want to consult with the home office, or would you like our process expert to walk you through the general process at a high level to help you decide which records would be most valuable for you?"

In the specific case of software and user interface questions, I'd have the architecture and project planing documents ready, along with the final reports... and assuming that my team didn't repeat summative testing I would have the past summative testing available, along with any formative testing done specific to the recent change.
 
Thread starter Similar threads Forum Replies Date
S Software Application for Management of Change (API 5.11) Other ISO and International Standards and European Regulations 3
C Management Of Change System or Software - Recommendations and Ideas wanted After Work and Weekend Discussion Topics 2
A Enterprise change management control system software - Medical Devices Quality Assurance and Compliance Software Tools and Solutions 0
dgrainger Informational MHRA's Software and AI as a Medical Device Change Programme UK Medical Device Regulations 0
A For software change - New Channel of interoperability CE Marking (Conformité Européene) / CB Scheme 5
N ISO 13485 7.3.9 Change control in medical device software ISO 13485:2016 - Medical Device Quality Management Systems 6
R Software change control process and defect tracking ISO 13485:2016 - Medical Device Quality Management Systems 1
R SaMD - Software as a Medical Device - Software change control form ISO 13485:2016 - Medical Device Quality Management Systems 3
J PMA Device - Lot # change in New ERP Software - What are the FDA Requirements 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 0
A Software Suggestions for Engineering Change/QMS Design and Development of Products and Processes 2
E Special 510(k) for software change Other US Medical Device Regulations 1
T Class II Medical Device with Software - Change to Computer 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
C Change Control Forms Post Software Validation Medical Information Technology, Medical Software and Health Informatics 2
K Change Control for Software System that Controls Aspects of GMP Quality Assurance and Compliance Software Tools and Solutions 5
E Help with ECR/DCR Document Change Control Software Validation Qualification and Validation (including 21 CFR Part 11) 6
D Question surrounding Special 510(k) in regards to Software Change 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 15
L Engineering Change Control Software Systems - Recommendations? Document Control Systems, Procedures, Forms and Templates 2
R PMA (Parts Manufacturing Approval) Supplement - Labeling Software Change 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
J Looking for a change template related to software change? Document Control Systems, Procedures, Forms and Templates 2
K Software Device "Urgent" Releases? Software Change Control Process IEC 62304 - Medical Device Software Life Cycle Processes 9
A Design Review OR Design Change - Software development company ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
W When to change UCL and LCL - SPC Software Statistical Analysis Tools, Techniques and SPC 4
U Advice on Engineering Change Request (ECR) software Software Quality Assurance 4
Q Global change software where changing one document changes all documents Quality Assurance and Compliance Software Tools and Solutions 1
M Using M-1 Software for Quality - Manual Engineering Change Order Entry Quality Assurance and Compliance Software Tools and Solutions 1
D What constitutes a "significant change" in software AND what does not Software Quality Assurance 7
J Software change control - How should I be controlling software changes? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 6
G PEDYN (Professional Engineering DYNamics) Change Mangement Software Quality Assurance and Compliance Software Tools and Solutions 4
G Software verification vs. system verification IEC 62304 - Medical Device Software Life Cycle Processes 3
S Process Monitoring using SPC software Quality Assurance and Compliance Software Tools and Solutions 3
J Megger MIT520/2 adjustment software? Calibration and Metrology Software and Hardware 0
M Product Acceptance Software (PAS) PROCEDURE (BOEING D6-51991) AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
M 3D Scanner Software validation ISO 13485:2016 - Medical Device Quality Management Systems 7
Y Software to Manage IEC 62304 Traceability Requirement IEC 62304 - Medical Device Software Life Cycle Processes 3
T Software item classification and Detailed Design IEC 62304 - Medical Device Software Life Cycle Processes 4
T Software Unit definition - IEC 62304 - Medical Device Software Life Cycle Processes 3
T Software user interface - definition of hazards ISO 14971 - Medical Device Risk Management 15
T Classification Accessory Software medical device EU Medical Device Regulations 4
G Software Medical Device Classification EU Medical Device Regulations 7
D Software Validation Question ISO 13485:2016 - Medical Device Quality Management Systems 10
C. Tejeda Computer system validation approach for Minitab Statistical software Software Quality Assurance 7
B Can a software that receive data from a MD be classified as Class I?or is not a MD? EU Medical Device Regulations 5
A What JIRA Software workflows you use for your software lifecycle? IEC 62304 - Medical Device Software Life Cycle Processes 4
G IATF 7.1.5.2.1 Calibration/verification records :Program/software verification IATF 16949 - Automotive Quality Systems Standard 7
John C. Abnet ...validation of computer software ISO 13485:2016 - Medical Device Quality Management Systems 14
N Free statistical software Reliability Analysis - Predictions, Testing and Standards 7
T ISO quality system software such as MQ1 (which is what we currently use) Document Control Systems, Procedures, Forms and Templates 8
X Looking for 17025 auditor to perform internal audit on IT software testing laboratory ISO 17025 related Discussions 3
B ERP software validation - risk assessment vs validation scope ISO 13485:2016 - Medical Device Quality Management Systems 11
D Guidance for Medical records software/template ISO 13485:2016 - Medical Device Quality Management Systems 1

Similar threads

Top Bottom