Design Qualification Document Sample
Design Qualification Document Sample
1 OBJECTIVE .................................................................................................................................................... 1
2 REFERENCE MATERIAL ............................................................................................................................... 2
3 ROLES & RESPONSIBILITIES ...................................................................................................................... 2
4 PRODUCT FUNCTIONAL REQUIREMENTS FOR TRUSCAN RAMAN HANDHELD
SPECTROPHOTOMETER ...................................................................................................................................... 2
4.1 Introduction .............................................................................................................................................. 2
4.2 System Description Overview .................................................................................................................. 2
4.3 Basic Theory ............................................................................................................................................ 2
4.4 Instrument Overview ................................................................................................................................ 3
5 GMP AND ER/ES ............................................................................................................................................ 4
6 TECHNICAL REQUIREMENTS ...................................................................................................................... 4
6.1 Instrument/Basic Operational Design ...................................................................................................... 5
6.2 IT Infra structure (computer hardware, operating system) ...................................................................... 9
6.3 Application software................................................................................................................................. 9
6.4 Methods and parameters ....................................................................................................................... 10
6.5 Data collection / data entry .................................................................................................................... 11
6.6 Report .................................................................................................................................................... 12
6.7 User properties and access ................................................................................................................... 13
6.8 User account and password management ............................................................................................ 14
6.9 Data integrity / audit trail ........................................................................................................................ 15
6.10 Data backup and restore ....................................................................................................................... 18
6.11 Data transfer (export/import) ................................................................................................................. 18
6.12 Safety ..................................................................................................................................................... 18
6.13 Supplier’s quality system ....................................................................................................................... 19
6.14 Documentation requirements ................................................................................................................ 20
6.15 Service and support ............................................................................................................................... 20
6.16 Training .................................................................................................................................................. 21
6.17 Delivery and installation ......................................................................................................................... 22
6.18 Qualification services ............................................................................................................................. 23
7 DEFINITIONS ................................................................................................................................................ 24
8 MODIFICATION / CHANGE CONTROL ....................................................................................................... 25
9 APPROVALS ................................................................................................................................................ 25
1 OBJECTIVE
The objective of the document is to provide the owner of this document with the critical design qualification criteria for
TruScan Raman Handheld Spectrophotometer for design, reliability, performance and compliance. Specifications are listed
in terms of the design specification requirement, a brief summary justification for the need for the requirement and a
summary explanation of how the design specification was implemented in the product.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 2 of 25
2 REFERENCE MATERIAL
The reference materials used to develop the critical design qualification criteria are Ahura Scientific’s internal documents
developed during the initial design of the TruScan such as the User Requirement Document, the System Requirement
Document. These documents are archived under electronic format at an off-site secure location and area available on
demand provided that a non disclosure agreement is signed between Ahura Scientific and the demander.
It’s the responsibility of QC management to insure that all the validation steps have been executed properly and that all the
documentation pertinent to the validation of the TruScan Raman Handheld Spectrophotometer are available for subsequent
inspection.
4.1 Introduction
The TruScan instrument is intended to simplify and secure the receiving goods control of raw materials and packaging
material at pharmaceuticals manufacturing facilities.
The raw materials above are used to produce pharmaceutical products and therefore the instrument must fulfill the
requirements of a pharmaceutical industry. The various physical forms of raw materials to be analyzed consist of:
- Solids (fine powder, micronized powder and granules)
- Liquids (high viscosity and low viscosity)
- Capsule gels (semi-finished product; oil base filled into capsule)
The Ahura Scientific TruScan Raman analyzer is designed for the non-contact analysis of active pharmaceutical ingredients
and excipients for identification purposes. The Raman analyzer is completely self-contained, operating on battery power
(small lithium ion rechargeable cell), and housed within a rugged and sealed enclosure. The unit is constructed with a
stabilized 785-nm solid-state laser source, an integrated imaging module, and a 2048-pixel diode-array-based spectrograph.
All electronics, including a single-board processor, also are fully integrated. The user interface is a simple set of push-
button controls linked to a menu-driven color liquid crystal display. A chemometrics-based spectral search package is
included that provides conclusive identification.
The Raman analyzer system is designed to support process development and production of pharmaceutical products. The
system is a hand-held device and operated through a set a push buttons and configurable to operate through a PC. The
output is through the color liquid crystal display and may be communicated over a network. The Raman analyzer operates
by illuminating the materials in a container with a laser and collecting and analyzing the scattered light.
Raman spectroscopy is a form of vibrational spectroscopy and as such is related to near- and mid-IR absorption
spectroscopy. Similar to the IR absorption techniques, Raman spectroscopy measures the vibrational frequencies of various
parts of a molecule. These frequencies depend on both the bond strength and mass of the bound atoms as well as other
factors such as intermolecular interactions. The 'pattern' of vibrational frequencies from a molecule is, therefore, highly
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 3 of 25
characteristic of a given molecular species and, for solid samples, of the crystalline arrangement of those molecules. Raman
spectra may be readily recorded from gasses, liquids and solids.
While IR spectroscopy is essentially based on illuminating the sample with a broad range of wavelengths of IR light and
measuring which are absorbed, a Raman spectrum is obtained by illuminating the sample with a single wavelength of light
from a laser and collecting and analyzing the resulting scattered light. Briefly, the basic experimental arrangement to
perform Raman spectroscopy includes the following steps:
- To obtain a Raman spectrum the sample is illuminated with light from a laser.
- The molecules in the sample 'scatter' the incident laser light. Some of this scattered light contains detailed
information about the molecular properties of the sample.
- The scattered light is collected and analyzed using a Raman spectrometer to produce a Raman spectrum.
- Raman spectra are generally clear, well resolved and rich in features facilitating detailed and unambiguous
interpretation.
- The spectra contain large amounts of information about chemical composition, intra- and intermolecular
phenomena, and the longer range structure of a sample.
The figure below shows the TruScan instrument. The shaded box in figure 2.1 highlights the parts covered by the Product
Functional Requirement Specifications in this document (the TruScan instrument and its Syncserver application). The user
access levels Admin and Developer need access to a web browser (Internet Explorer – IE).
Network
The TruScan instrument will be used at manufacturing facilities within pharmaceutical organizations, in an area controlled
by Good Manufacturing Practice (GMP) for pharmaceutical production.
The TruScan instrument collects electronic data in GMP environment. The electronic data collected in such environment
must closely follow 21 CFR part 11 Electronic Records & Electronic Signatures (ER/ES) guidance. TruScan complies with
all the 21 CFR part 11 Electronic Records & Electronic Signatures (ER/ES) rules.
Detailed requirements on system and data security are stated in chapter 6 Technical requirements section System and
computer security.
6 TECHNICAL REQUIREMENTS
6.6 Report
ID Requirement description Implementation in TruScan
6.6.1 * Reports must be printable.
The following must be clearly indicated on Reports are stored in .pdf and .jpg file formats, both
every printed page: of which are printable.
Reports include Device serial number, date of
• Instrument identity,
measurement, time of measurement, user identity.
• Page number and total no of pages,
All reports are single page reports, and do not have
• Date and time of measurement
a page number.
• User identity.
6.6.2 * The report must contain identifier, for
example Sample ID; to ensure that report can All reports include Sample ID
be traced to its sample.
6.6.3 Reports include:
Method name
Raw data (spectrum and reference spectrum as
overlaid figures
Result (PASS or FAIL).
Audit trail data in report includes:
User name
User login date and time
Run label
Run calibration test result
Run CCD check result
Run laser power check result
Run date and time
Sample ID
P value
Result (PASS or FAIL)
User note
6.6.4 * The instrumented must log data (time, event,
Data is logged (to report and audit log) on
and user) automatically for every step in a
completion of the measurement.
measurement.
6.6.5 Administrator cannot modify report templates.
Optional. An administrator should be able to Administrator can specify which file formats will be
create, change or remove report templates. stored on Sync (Ahura binary format (.ASO)
compulsory; .pdf, .jpg, .txt. .spc are optional).
6.6.6 * Users must not be allowed to change report User access privilege level cannot modify report
templates. templates.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 13 of 25
The device must ensure that data is securely TruScan also maintains a system configuration
stored to prevent any tempering deleting or audit trail that documents changes made to the
overwriting attempt. Every change to methods system configuration by developers and
should be managed through version handling administrators.
or an audit trail.
Audit trails are delivered to a secure location
(identified by the system administrator in the device
configuration) for permanent storage.
6.9.3 * System administrator cannot change raw data or
The system administrator must not be able to
reports on the system.
change or delete electronic records (raw data,
All changes to configuration (users, methods,
reports etc) without this being automatically
settings, etc) are recorded in audit log with user,
traced to the individual.
date-time details.
6.9.4 * The system clock function of the instrument
that registers time in event logs (for example
Administrator can change system clock function.
access log, audit trail) must not be changeable
by any user.
6.9.5 The unit uses the following date format:
The system clock function must use Windows mm/dd/yyyy hh:mm pm or dd-mmm-yyyy hh:mm
standard format for date and time.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 16 of 25
USER EVENTS:
User lock-out
Successful unit login
Failed unit login
Unit logoff
successful web login
failed web login
web log off
user password change
user modified (any modification)
user added
user delete
SIGNATURE EVENTS
The system must automatically register/log
active signatures import
events in an audit trail, when the user creates,
active signatures export
changes or deletes Electronic Records (raw
active signature add
data, reports etc).
active signature rename
active signature delete
active signature rename
METHOD EVENTS
method added
method modified (any modification)
method run
method delete
OTHER:
configuration import
configuration modified
note list modified
self-test run
6.9.8 * Audit trail should have at least the following Audit trail includes:
contents: Identity of user who performed activity to create,
change, or delete information.
• Identity of user who performed activity to
Date and time of creation, change or deletion of
create, change or delete information.
information.
• Date and time when this happened.
The category of the information created, changed or
• The event that created changed or deleted
deleted (e.g., Method, User, Configuration setting).
the information.
It is not currently possible to record a reason for the
• The reason for the change. change.
6.9.9 * Between Syncs, new events are appended at the end
of the audit log file, and do not overwrite previously
registered events.
New events must not overwrite previously During Sync, after confirmation of successful
registered events in the audit trail. transfer of the existing audit log file to the secure
archive, the existing Sync file is erased and a new
audit log file is created which will be used until the
next Sync.
6.9.10 * No shutoff of audit trail function must be
Audit trail function cannot be switched off.
possible when the system in use.
6.9.11 * It must not be possible for a user to change or The audit log file cannot be amended or deleted in
delete audit trail or parts thereof. the system.
6.9.12 The audit log file is not accessible to users on the
Audit trail should be searchable for records, system. Once transferred to the secure archive, the
users, date, time and for type of event. audit log file is a text file that can be searched using
a text editor.
6.9.13 * Audit trail must be retrievable in electronic The audit log file is an electronic file that can be
form as well as in paper printout. printed once accessed from the secure archive.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 18 of 25
SHE
(Requirements marked with * are GMP requirements)
6.12 Safety
ID Requirement description Implementation in TruScan
6.12.1 The TruScan instrument, mains power and battery
charging transformers, and the battery charging
holder are all CE marked. The instrument is also
All instrument components must be CE
UL913 certified.
marked and UL certified
It is also UL61010-1 and CSA C22.2 No. 61020-2,
EN 616010-1:03/93 +A2:07/95, FDA CDRH
1040.1 certified.
6.12.2 The instrument has a warning label stating that it is
The instrument must have a suitable warning
a CLASS 3B LASER PRODUCT. It also has
label for laser radiation.
generic laser warning labels near the aperture.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 19 of 25
6.16 Training
ID Requirement description Implementation in TruScan
6.16.1 * A basic training on the instrument and the Instrument training on-site is available upon
application must be a part of the delivery. purchase of the instrument.
6.16.2 * Instructions in setting up and administration of Instructions and training in setting up an
user groups for access control in the system must administering user access control is included in the
be a part of the delivery. IQOQ purchase and is performed during the visit.
6.16.3 Training must be performed at the latest one
Training will be provided within one month of
month after approved delivery or at an agreed
approved delivery date or at a mutually agreed time.
time.
6.16.4 All training must take place on-site at
Training will take place at on site.
The purchasing organization manufacturing sites.
6.16.5 * The supplier should give a certificate or equivalent A Certificate of Completed Training will be
of accomplished training to each participant. provided to each trained person.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 22 of 25
7 DEFINITIONS
User/analyst
User is a person using the system. Examples of users are analysts, service and maintenance personnel and administrators.
Audit Trail
A secure, date and time stamped record, which enables reconstruction of course of events for who has created, changed or
deleted an ER and when that has happened. When required, by GxP and/or current SOP, the reason for change should also
be clear.
Hotfix
Something that corrects or fixes an error or a defect in a software or hardware, for example a patch.
Instrument
TruScan.
IT Infrastructure
Hardware and software components that the application is dependent upon to function. Infrastructure includes computer
hardware, servers, network, operating system or other embedded software that the specific application uses or builds on.
Template
A file used to create reports from the measurements performed by the instrument.
Mandatory requirements
Requirements by GMP or requirements critical for operation, which directly or indirectly influence the system function or
fulfillment of regulatory requirements.
Report
Printout of an analysis can be for example:
• text,
• an image,
• a spectrum.
Record
Information created, received and managed by an organization. Records are used as evidence and information for the
organization's business and/or to fulfill legal obligations.
SOP ID:
Design Qualification of TruScan Raman
Handheld Spectrophotometer Revision:
Issue date:
Page 25 of 25
Raw data/Data
All original records (or verified exact copies of these) that are the result of original observations, measurements and
activities. Data collection of spectra and calculated data and result files that are created.
Sync application
The application installed on a PC or server. The application transfers data from the instrument and places them on a
network drive.
System
The system consists of the TruScan instrument and the sync application. The PC/server is not part of the system but is used
both for installation of the sync application and for administrative tasks such as for example user access administration. The
administrative tasks are managed using a web browser.
Any changes or modification to this document must be documented and approved. The likely impact of the change of the
status of the protocol should be evaluated, reviewed, approved and training of those responsible for its execution prior to
implementation.
9 APPROVALS