(Company background: Medical devices and aerospace products)
My company is using a QMS software suite that contains CAPA, Document Control, Nonconforming Material Handling, Training, etc. For the previously installed version, a colleague and myself performed a validation on the software. I just recently installed the latest version of the software which had 3 previous releases that I did not install.
The software company provides a "readme" pdf for each revision which goes through the enhancements and bug fixes. I was going to use this information to re-validate the software to the latest revision. However upon reviewing the pdf, some of the bug fixes don't makes sense to me as a user most likely because I am not aware of the problem that required these fixes.
I contacted the software company and to make things even more confusing to me they said that some of the fixes would not even apply to my software as they were system dependent (ex. another customer was using a different server setup that caused the problem on their system only).
I am trying to figure out the best way to re-validate the software. I don't want to go through a whole validation again but it almost looks like that is the most efficient way to address the validation process as it is difficult if not impossible to determine what bug fixes actually apply to my system.
Any suggestions or comments on how to go about re-validating COTS software given what I have laid out above?
My company is using a QMS software suite that contains CAPA, Document Control, Nonconforming Material Handling, Training, etc. For the previously installed version, a colleague and myself performed a validation on the software. I just recently installed the latest version of the software which had 3 previous releases that I did not install.
The software company provides a "readme" pdf for each revision which goes through the enhancements and bug fixes. I was going to use this information to re-validate the software to the latest revision. However upon reviewing the pdf, some of the bug fixes don't makes sense to me as a user most likely because I am not aware of the problem that required these fixes.
I contacted the software company and to make things even more confusing to me they said that some of the fixes would not even apply to my software as they were system dependent (ex. another customer was using a different server setup that caused the problem on their system only).
I am trying to figure out the best way to re-validate the software. I don't want to go through a whole validation again but it almost looks like that is the most efficient way to address the validation process as it is difficult if not impossible to determine what bug fixes actually apply to my system.
Any suggestions or comments on how to go about re-validating COTS software given what I have laid out above?