Validation of COTS Equipment plus Software

S

satwiks51

#1
#1
Hi,

I am to validate an COTS analytical instrument for laboratory. The instrument is controlled by an user interface and data is stored in the instrument after the run. The data is now transferred to a computer where it is analyzed by a COTS software and the results are saved into repository.

Should the validation be done considering (Instrument + analyzing software) as a system or validation of Instrument and software should be separate.
 
GAGEpack- Gage Management Made Easier
Elsmar Forum Sponsor
Ninja

Ninja

Looking for Reality
Trusted Information Resource
#2
#2
Howdy, (I am not in Pharma...so take all further comment with that in mind).

COTS analytical instruments do things.
COTS Software does stuff.
You need to accomplish something...and you need to validate how you did it to make sure it's OK. (The Test method, which includes both the equipment, tools, and how you choose to use them.)

Your validation should be on your "test method", which will unavoidably include the tools and equipment you use during the operation of your test method.
You aren't validating the COTS equipment.
You aren't validating the COTS software.
You are validating your test method and showing that it is adequate to meet the stated need.

HTH
 
Ninja

Ninja

Looking for Reality
Trusted Information Resource
#4
#4
LOL, thanks yodon...
FWIW, validating the test method validates the gage and the software at the same time, no?
 
Y

yodon

Leader
Super Moderator
#5
#5
You can almost certainly get some lift for the software validation off of the other validation activities but, as noted, software validation is more than just test. Confirmation of full lifecycle control is expected (the expectations assume, rightly, that software will change)
 
Ajit Basrur

Ajit Basrur

Leader
Admin
#6
#6
satwiks51 said:
Hi,

I am to validate an COTS analytical instrument for laboratory. The instrument is controlled by an user interface and data is stored in the instrument after the run. The data is now transferred to a computer where it is analyzed by a COTS software and the results are saved into repository.

Should the validation be done considering (Instrument + analyzing software) as a system or validation of Instrument and software should be separate.
Click to expand...
GAMP 5 Category 3 software (for COTS) and USP 1058 would be a good start.
 
S

sreekiran14

Starting to get Involved
#7
#7
I validated a COTS GAMP3 data analysis software by keeping the instrument software that generates data out of scope and planned to validate that separate to make things easy and clear.
 
S

sreekiran14

Starting to get Involved
#8
#8
yodon said:
You can almost certainly get some lift for the software validation off of the other validation activities but, as noted, software validation is more than just test. Confirmation of full lifecycle control is expected (the expectations assume, rightly, that software will change)
Click to expand...
I feel that you have good experience around the software validation,Can you please explain what do you mean by full life cycle control?
Thank you.
 
Ajit Basrur

Ajit Basrur

Leader
Admin
#9
#9
sreekiran14 said:
I feel that you have good experience around the software validation,Can you please explain what do you mean by full life cycle control?
Thank you.
Click to expand...
In short, from cradle to grave ... so in this case, refers to all the phases of a software throughout its planning, development, use, change control, through its eventual retirement
 
Y

yodon

Leader
Super Moderator
#10
#10
sreekiran14 said:
I feel that you have good experience around the software validation,Can you please explain what do you mean by full life cycle control?
Click to expand...
Sure. Things change with software: either the software itself, the OS under which it runs, the hardware platform, 3rd party software incorporated, use models (more users, different use cases, and so forth. Any of these *potentially* impacts the validation status. All changes are ideally controlled but that's not always practical; e.g., OS security patches. Changes directly to the software absolutely need to be controlled. As @Ajit Basrur notes, cradle-to-grave management. This includes an ongoing (periodic) review of the validation status. You may likely re-do validation if the software is directly updated but will you do so if the use changes or an underlying database engine (for example) is changed? It *may* warrant additional validation work (whether it be testing or analysis).
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
S COTS (commercial off-the-shelf) Validation FDA Requirements Software Quality Assurance 4
K COTS Validation: Should we validate Windows after each Update? IEC 62304 - Medical Device Software Life Cycle Processes 3
R Only Commissioning Software? COTS, GAMP Category 3 Software Validation Requirements IEC 62304 - Medical Device Software Life Cycle Processes 7
B Transport Validation For Non-sterile Medical Devices ISO 13485:2016 - Medical Device Quality Management Systems 4
D Software Validation Question ISO 13485:2016 - Medical Device Quality Management Systems 10
G Pad Printing Validation OR Verification ISO 13485:2016 - Medical Device Quality Management Systems 4
A ETHYLENE OXIDE STERILIZATION VALIDATION Manufacturing and Related Processes 4
C. Tejeda Computer system validation approach for Minitab Statistical software Software Quality Assurance 7
D 8.5.1.2 Validation and control of special processes requirements for Heat Treat External Processor AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
S Performance Qualification and Process Validation ISO 13485:2016 - Medical Device Quality Management Systems 5
L ISO 11607-1 Packaging system validation Design and Development of Products and Processes 8
John C. Abnet ...validation of computer software ISO 13485:2016 - Medical Device Quality Management Systems 14
D Machine rebuilds versus process re-validation IATF 16949 - Automotive Quality Systems Standard 1
R Cloud-based SaMD Validation IEC 62304 - Medical Device Software Life Cycle Processes 8
G Process Validation Before/After Sterilization? Design and Development of Products and Processes 3
D Laboratory Refrigerator Validation ISO 13485:2016 - Medical Device Quality Management Systems 2
T SQL Server 2019 - Master Data Services - Validation needed? ISO 13485:2016 - Medical Device Quality Management Systems 4
G Shipping Validation of Non-Sterile Parts? Other Medical Device and Orthopedic Related Topics 9
J Hardware Validation Qualification and Validation (including 21 CFR Part 11) 1
B ERP software validation - risk assessment vs validation scope ISO 13485:2016 - Medical Device Quality Management Systems 11
blackholequasar Validation of new ERP system ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 6
G How to Record Informal Testing (Not Verification/Validation) Other Medical Device and Orthopedic Related Topics 15
B Clean room shut down and re-validation or re-qualification? Other Medical Device Related Standards 6
B Vision system process validation Manufacturing and Related Processes 1
R Validation of Software used in Verification Testing ISO 13485:2016 - Medical Device Quality Management Systems 2
D Glassware cleaning validation Qualification and Validation (including 21 CFR Part 11) 3
M Do i need to have equipment validation if 100% testing is completed? Qualification and Validation (including 21 CFR Part 11) 6
R SaMD Verification & Validation IEC 62304 - Medical Device Software Life Cycle Processes 6
B SPECIAL PROCESS VALIDATION & REVALIDATION Qualification and Validation (including 21 CFR Part 11) 4
R Validation of processes Oil and Gas Industry Standards and Regulations 2
L Guidance for validation - mixing homogeneity Qualification and Validation (including 21 CFR Part 11) 0
E DESIGN VALIDATION, USABILITY AND CLINICAL EVALUATION request Medical Device and FDA Regulations and Standards News 0
S In Field Validation Requirements Other Medical Device Related Standards 1
L Validation of mixers Capability, Accuracy and Stability - Processes, Machines, etc. 2
L Validation of mixers Qualification and Validation (including 21 CFR Part 11) 0
B How to satisfy clause 5.7.1.5 process validation for valve production API 6D Oil and Gas Industry Standards and Regulations 13
A Applying agile model for Computer system Validation Medical Device and FDA Regulations and Standards News 3
H Production Validation- CE Mark ISO 13485:2016 - Medical Device Quality Management Systems 3
Watchcat Software validation vs design V&V? Other US Medical Device Regulations 27
M Initial Importer/Distributor and Software Validation IEC 62304 - Medical Device Software Life Cycle Processes 1
P Test Method Validation (TMV) for all Measurement Methods in Rec/Inspection Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 1
M Validation of Data verification tool per 21 CFR 820 Quality Assurance and Compliance Software Tools and Solutions 1
G Number of Destructively Tested Devices Needed for Ethylene Oxide Validation Other Medical Device Related Standards 4
E ISO 13485 software validation ISO 13485:2016 - Medical Device Quality Management Systems 7
R SAP B1 Computer System Validation Qualification and Validation (including 21 CFR Part 11) 0
A GAGE R&R Binomial with master list (for method validation) Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 0
Y ISO 13485:2015 Software Validation IQ/OQ/PQ ISO 13485:2016 - Medical Device Quality Management Systems 13
N Validation of special processes - thread closed Oil and Gas Industry Standards and Regulations 3
L Validation without Tolerance Qualification and Validation (including 21 CFR Part 11) 0
shimonv Test Method Validation ISO 13485:2016 - Medical Device Quality Management Systems 10

Similar threads

Top Bottom