SaMD - Software as a Medical Device - Software change control form

racglobal

Involved In Discussions
#1
Hello everyone,

For a company that makes SaMD, (software as a medical device), does anyone have a design change control form template? I know in the world of hardware devices, there are engineering change controls and the associated forms where you assess the impact. Does the world of software have difference requirements on the change control form? Can somebody provide some insight and a template they would like to point me to ?


Thanks.
 
Elsmar Forum Sponsor

yodon

Leader
Super Moderator
#2
It's still a medical device so I would suggest you always:
  • [from 13485] assess (and document) the significance of the change to function, performance, usability, safety and applicable regulatory requirements
  • [from 13485 and effectively 820] document what you did regarding review, verification and/or validation, and approval (to make the change)
  • [from 13485] assess (and document) the effect of the changes on constituent parts and product in process or already delivered, inputs or outputs of risk management and product realization processes.
  • [from 62304] assess (and document) the effect on the organization, released MEDICAL DEVICE SOFTWARE, released for intended use, and SYSTEMS with which it interfaces
  • [from 62304] assess (and document) a statement of criticality (for example, the effect on performance, SAFETY, or SECURITY) as well as other information that may aid in the resolution of the problem (for example, devices affected, supported accessories affected)
  • [from 62304]
    1. investigate the problem and if possible identify the causes;
    2. EVALUATE the problem’s relevance to SAFETY using the software RISK MANAGEMENT PROCESS;
    3. document the outcome of the investigation and evaluation; and
    4. create a CHANGE REQUEST(S) for actions needed to correct the problem, or document the rationale for
      taking no action.
  • [from 62304] advise relevant parties of the existence of the problem, as appropriate
You should also consider the impact on usability [62366].

Your form can facilitate driving/capturing all this.
 

Ed Panek

QA RA Small Med Dev Company
Leader
Super Moderator
#3
Also evaluate the user experience change from the software iteration. A 510K alteration review is advice from FDA that should be reviewed with all SW changes. Regression testing deliberation should also be documented.
 

Lokus200

Starting to get Involved
#4
Same change process applies to all medical devices, you will have to follow the same process.
I assume as a software developer you are using tools such as JIRA to document defects, you can adjust your tools to include the change process instead of creating additional paperwork. Just make sure you add regulatory evaluation of every change and document why new 510k is not required.
 
Thread starter Similar threads Forum Replies Date
J Software as a Medical Device - SaMD IEC 62304 - Medical Device Software Life Cycle Processes 7
V Software as medical device (SaMD) replicated for multiple clients through APIs IEC 62304 - Medical Device Software Life Cycle Processes 5
Q Storing and developing SAMD (Software as a Medical Device) in the Cloud IEC 62304 - Medical Device Software Life Cycle Processes 3
F Software as a Medical Device (SaMD) Technical File Requirements Manufacturing and Related Processes 3
A Software as Medical Device (SaMD) definition and its applicability Other Medical Device and Orthopedic Related Topics 4
M Informational TGA – Submissions received: Regulation of software, including Software as a Medical Device (SaMD) Medical Device and FDA Regulations and Standards News 1
M Informational TGA – Webinar: An update on the consultation for the Regulation of Software, including Software as a Medical Device (SaMD) Medical Device and FDA Regulations and Standards News 0
J Qualification of a Software as a Medical Device (SaMD) guidance under MDR EU Medical Device Regulations 9
M Informational TGA Consultation: Regulation of software, including Software as a Medical Device (SaMD) Medical Device and FDA Regulations and Standards News 0
M Medical Device News Health Canada - Scientific Advisory Panel on Software as a Medical Device (SAP-SaMD) - Record of Proceedings – January 26, 2018 Canada Medical Device Regulations 0
K Registering a Software medical device (SaMD) in China China Medical Device Regulations 5
C How to place software version for SaMD product in HIBC secondary data structure (UDI-PI)? Other US Medical Device Regulations 4
I Software (SaMD) mobile application verification testing: objective evidence Medical Information Technology, Medical Software and Health Informatics 2
A SaMD: Metric for release frequency EU Medical Device Regulations 4
A SaMD: Post Market Surveillance after Decomissioning EU Medical Device Regulations 2
R SaMD Performance Testing US Medical Device Regulations 5
R Cloud-based SaMD Validation IEC 62304 - Medical Device Software Life Cycle Processes 8
Ed Panek Consultant Request SaMD AI "Expert" FDA US Food and Drug Administration (FDA) 2
K SaMD and Customer Integrations Medical Information Technology, Medical Software and Health Informatics 3
R SaMD Verification & Validation IEC 62304 - Medical Device Software Life Cycle Processes 6
T IEC 62304 : Risk control for SaMD IEC 62304 - Medical Device Software Life Cycle Processes 8
Z PMS Data collection for SAMD SaaS from clients EU Medical Device Regulations 3
L Essential Design Outputs for SAMD 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
A SaaS SaMD - Impact QMS ISO 13485:2016 - Medical Device Quality Management Systems 2
H ISO 13485-paragraphs for a SaaS SAMD needed or not? ISO 13485:2016 - Medical Device Quality Management Systems 3
H Customer Specific Change in a SaaS SAMD IEC 62304 - Medical Device Software Life Cycle Processes 1
I Multiple Indications in SaMD Other US Medical Device Regulations 8
Y SaMD Verification and Validation SOP and Plan IEC 62304 - Medical Device Software Life Cycle Processes 8
R SaMD - Placing on the Market before DoA EU Medical Device Regulations 2
D CE SaMD modular approach CE Marking (Conformité Européene) / CB Scheme 5
K Regulatory requirement of SaMD with machine learning component IEC 62304 - Medical Device Software Life Cycle Processes 3
Y Distributor for a SaMD Medical Information Technology, Medical Software and Health Informatics 3
Sravan Manchikanti How to interpret '8.3 Control of nonconforming product' for SaMD device while implementing ISO 13485 & MDSAP ISO 13485:2016 - Medical Device Quality Management Systems 7
A Demonstration of Equivalence - Need for comparing biological characteristics for an SamD EU Medical Device Regulations 1
N Servicing for SaMD ISO 13485:2016 - Medical Device Quality Management Systems 6
N Agile SOP for SaMD IEC 62304 - Medical Device Software Life Cycle Processes 3
D Not a SaMD - How to be submitted for marketing authorization in EU and USA CE Marking (Conformité Européene) / CB Scheme 5
T Medical device or not - SaMD Other Medical Device and Orthopedic Related Topics 3
C Supplier Assessment for Hardware supporting SaMD ISO 13485:2016 - Medical Device Quality Management Systems 1
T MEDDEV 2.7/1 r4 vs. IMDRF/SaMD WG/N41 Other Medical Device Related Standards 3
M IMDRF document - Application of QMS to SaMD ISO 13485:2016 - Medical Device Quality Management Systems 2
W IEC 62304 vs. IMDRF SaMD Guideline Risk Class IEC 62304 - Medical Device Software Life Cycle Processes 5
J Document Control of Online Management Software ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 10
S Functionality of software in countries with different legal requirements IEC 62304 - Medical Device Software Life Cycle Processes 2
J Using an online software to maintain your QMS Quality Assurance and Compliance Software Tools and Solutions 7
R Quality System Software AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 8
V Software license key regulatory requirements Medical Information Technology, Medical Software and Health Informatics 2
I Request for information regarding remote medical monitoring software (its technical documentation and the IUD system) IEC 62304 - Medical Device Software Life Cycle Processes 2
M Software Validation SAP B1 for ERP ISO 13485:2016 - Medical Device Quality Management Systems 2
P Computer Software Assurance Software Quality Assurance 2

Similar threads

Top Bottom