Product Development

Comprehensive Audit Checklist for Product Development Department

Audit, Product Development, R&D, research & development, research and development, RND

These development-auditor checklists provide a structured, phase-appropriate audit framework for Product Development covering Formulation Development, Analytical Development, and Development QA. They focus on end-to-end traceability from QTPP/CQA/CPP and risk assessments through lab batch records, method development/validation/transfer, stability studies, and tech transfer readiness. The questions are designed to expose common hidden gaps such as weak change control, incomplete documentation, inadequate data integrity/audit trail review, uncontrolled retesting, and insufficient controls for sterile and potent (women hormone) development work.

 

 

Formulation Development (FD) — 50 Points

1) Is there a defined project initiation + governance?

1.1 Is there a project charter with scope (tablet/capsule/eye drops/injection/hormone)?
1.2 Roles/responsibilities (FD/AD/DQA/RA/Production) defined?
1.3 Milestones and decision gates documented (prototype, scale-up, TT)?
1.4 Meeting minutes/action tracker maintained?

2) Is QTPP (Quality Target Product Profile) defined and controlled?

2.1 QTPP includes dosage form, strength, route, container, shelf-life target?
2.2 Patient/safety needs addressed (sterile attributes, hormone potency risks)?
2.3 QTPP revision control exists (who can change and why)?
2.4 QTPP linked to CQA/CPP selection?

3) Are CQA (Critical Quality Attributes) identified and justified?

3.1 CQAs listed for each product type (e.g., dissolution for tablets; sterility for injections)?
3.2 Justification documented (risk assessment / prior knowledge)?
3.3 CQAs linked to test methods and acceptance criteria?
3.4 CQA list updated after learning (new impurities, stability issues)?

4) Is risk management (ICH Q9 / FMEA) used properly?

4.1 Risk assessment done early (materials/process/packaging)?
4.2 Risk scoring logic documented (severity/occurrence/detectability)?
4.3 Risk controls assigned (mitigation plan + owners)?
4.4 Risk review done after failures/deviations?

5) Is API characterization adequate for development?

5.1 API polymorph/PSD/solubility/hygroscopicity data available?
5.2 API variability (supplier/lots) assessed for impact on formulation?
5.3 API storage/handling requirements defined (light/moisture/temp)?
5.4 Potent/hormone API special handling documented?

6) Are excipient selection & justification documented?

6.1 Excipient function and grade justified (compendial/DMF status)?
6.2 Compatibility screening done (binary mixes, stress storage)?
6.3 Supplier variability risk assessed (different grades/vendors)?
6.4 Excipients for sterile products meet sterile-grade requirements where needed?

7) Is compatibility study design scientifically sound?

7.1 Conditions (temp/RH/light) justified and recorded?
7.2 Timepoints planned and met?
7.3 Acceptance criteria defined (impurity increase, appearance, pH shift)?
7.4 Conclusions supported by data (not assumptions)?

8) Are prototype formulations controlled and traceable?

8.1 Each prototype has unique code/version and change history?
8.2 Lab batch record exists for each prototype?
8.3 Raw material lots used are traceable?
8.4 Samples retained for reference/comparisons?

9) Are lab batch records complete (GDP compliant)?

9.1 Weights, equipment IDs, timings, steps recorded contemporaneously?
9.2 Deviations from procedure recorded with reason and impact?
9.3 Yield calculations and reconciliation recorded?
9.4 Review/approval of lab records defined (supervisor/DQA)?

10) Is development equipment suitable and maintained?

10.1 Equipment list (mixer, homogenizer, granulator, etc.) controlled?
10.2 Calibration/verification status (balances, thermometers) current?
10.3 Cleaning records maintained (especially for hormone/potent)?
10.4 Equipment use log supports traceability to batches?

11) Are weighing/dispensing controls adequate in FD labs?

11.1 Material labels include name/code, lot, status, expiry/retest?
11.2 Dispensing area controls mix-ups (one material at a time)?
11.3 Use of controlled balances/verified weights?
11.4 Leftover material return/disposal controlled?

12) Is cross-contamination prevention effective in FD labs?

12.1 Segregation between hormone/potent and non-potent work?
12.2 Dedicated tools/consumables for hormone products?
12.3 Cleaning verification approach defined (visual/swab where needed)?
12.4 Waste segregation and disposal documented?

13) For Women Hormone/potent products, is containment adequate?

13.1 HBEL/PDE awareness translated into lab controls?
13.2 Containment equipment used (downflow booth, negative pressure)?
13.3 PPE requirements defined and followed (double gloves, respirator if required)?
13.4 Spill response and decontamination procedure available?

14) Are process parameters captured during development?

14.1 Mixing speeds/times/temperatures documented?
14.2 Order of addition controlled and justified?
14.3 Hold times documented and assessed?
14.4 Critical steps identified (sieving, filtration, pH adjustment)?

15) Is DoE (Design of Experiments) used appropriately (if used)?

15.1 DoE plan defines factors/responses/ranges and rationale?
15.2 Randomization/replicates included where needed?
15.3 Data analysis documented (model fit, residuals)?
15.4 Conclusions translated into control strategy?

16) Are CPP (Critical Process Parameters) identified and linked?

16.1 CPPs mapped to CQAs (e.g., granulation endpoint → dissolution)?
16.2 CPP ranges justified (prior knowledge/DoE)?
16.3 Monitoring methods defined (in-process tests)?
16.4 CPP changes controlled via change control?

17) Is scale-up strategy defined from lab to pilot?

17.1 Scale-up rationale documented (geometric similarity, mixing energy)?
17.2 Pilot batch plans exist (equipment mapping)?
17.3 Differences between lab and pilot steps identified and controlled?
17.4 Risks at scale noted and mitigated?

18) Is technology transfer (TT) readiness planned early?

18.1 TT checklist exists (process, materials, specs, methods)?
18.2 Critical knowledge captured (what failed, what worked)?
18.3 Process instructions clear enough for Manufacturing?
18.4 TT package review/approval roles defined?

19) For tablets/capsules: is dissolution performance addressed in FD decisions?

19.1 Formulation choices linked to dissolution goals?
19.2 Disintegration vs dissolution relationship evaluated?
19.3 Lubricant level/PSD impact studied?
19.4 Robustness to process variation assessed?

20) For tablets/capsules: is blend uniformity / content uniformity risk addressed?

20.1 Mixing strategy and sampling plan defined?
20.2 Segregation risk evaluated (PSD/density differences)?
20.3 Low-dose/hormone products have enhanced controls?
20.4 Acceptance criteria defined for development stage?

21) For Eye Drops: are pH/osmolality/viscosity targets defined?

21.1 Targets justified for comfort/stability/compatibility?
21.2 Buffer selection and concentration rationale documented?
21.3 Viscosity agent selection justified and controlled?
21.4 In-use performance considerations addressed?

22) For Eye Drops: is drop size/drop rate controlled?

22.1 Dropper/nozzle selection rationale documented?
22.2 Drop weight/volume tested and recorded?
22.3 Container closure compatibility verified?
22.4 Variation across component lots evaluated?

23) For Eye Drops: is preservative selection justified (if multi-dose)?

23.1 Preservative type and level justified?
23.2 Preservative compatibility with formulation and container assessed?
23.3 PET (Preservative Efficacy Test) plan exists (as applicable)?
23.4 Neutralization strategy defined for microbiological tests?

24) For injections: is sterilization strategy defined?

24.1 Terminal sterilization vs sterile filtration rationale documented?
24.2 If sterile filtration: filter selection (0.22 µm) justification?
24.3 Filter integrity test requirements defined (pre/post)?
24.4 Bioburden/hold times assessed?

25) For sterile products: is container closure selection justified?

25.1 Vial/stopper/seal compatibility studied?
25.2 Extractables/leachables risk assessed at dev stage?
25.3 CCIT strategy considered (even if later validation)?
25.4 Component lot traceability maintained?

26) Are in-process tests defined for development batches?

26.1 Which checks are done (pH, viscosity, assay quick checks)?
26.2 Criteria defined (even if wider early-stage)?
26.3 Out-of-range handling documented (rework rules)?
26.4 Results recorded and reviewed?

27) Are rework/reprocess rules defined in development?

27.1 What adjustments are allowed (pH adjust, remix, refilter)?
27.2 Who approves adjustments and documents rationale?
27.3 Limits on number of reworks to avoid “testing into compliance”?
27.4 Impact on stability/quality assessed?

28) Is development stability program set up properly?

28.1 Protocol defines conditions (ICH), pull points, packaging?
28.2 Samples representative (final/closest-to-final pack)?
28.3 Excursions handled with impact assessment?
28.4 Stability data trends reviewed and actions taken?

29) Is in-use stability considered for Eye Drops (if applicable)?

29.1 In-use period target defined and justified?
29.2 Micro risk controls assessed (preservatives/packaging)?
29.3 Study design includes opening/handling simulation?
29.4 Acceptance criteria defined and reviewed?

30) Is photostability considered when relevant?

30.1 Risk assessed (light-sensitive APIs/excipients)?
30.2 Study design and packaging protection evaluated?
30.3 Labelling/storage instruction impact assessed?
30.4 Results drive packaging choice?

31) Are packaging compatibility studies done early enough?

31.1 Interaction with plastics (adsorption, leaching) assessed for liquids?
31.2 Foil/film moisture barrier needs evaluated for tablets?
31.3 Label/ink interactions considered (if relevant)?
31.4 Conclusions documented with evidence?

32) Are hold time studies considered (bulk/solution)?

32.1 Hold times defined for bulk blend/granules/solutions?
32.2 Conditions during hold controlled and recorded?
32.3 Micro risks considered for aqueous solutions?
32.4 Hold time exceed triggers deviation?

33) Is documentation of learning/knowledge management strong?

33.1 Development reports summarize experiments and decisions?
33.2 Failed trials captured (not hidden) with lessons learned?
33.3 Decision rationale traceable (why formula changed)?
33.4 Reports reviewed/approved per SOP?

34) Are outsourced development activities controlled (CRO/CMO)?

34.1 Vendor qualification and quality agreement in place?
34.2 Defined scope and data ownership?
34.3 Raw data availability and review process?
34.4 Sample chain of custody controlled?

35) Are samples managed properly in development?

35.1 Sample inventory log exists (what/where/qty)?
35.2 Sample labeling prevents mix-ups (project/batch/version)?
35.3 Storage conditions controlled (2–8°C/light protection)?
35.4 Sample disposal/retention rules defined?

36) Are deviations recorded for development activities?

36.1 Clear triggers for deviation (missed step, wrong parameter, excursion)?
36.2 Deviations include impact assessment and actions?
36.3 Overdue deviations tracked and escalated?
36.4 Recurrence prevention (CAPA) documented?

37) Are CAPA created when needed (not only “note and move on”)?

37.1 Root cause analysis used (5-Why/fishbone)?
37.2 Actions assigned with owners and due dates?
37.3 Effectiveness check defined (evidence of improvement)?
37.4 CAPA closure approved by DQA?

38) Is change control applied to formulation/process changes?

38.1 Changes recorded with reason and risk assessment?
38.2 Change approval required before execution?
38.3 Impact on specs/methods/stability assessed?
38.4 Change history traceable across versions?

39) Is training/competency maintained for FD staff?

39.1 Training matrix for equipment/processes exists?
39.2 OJT/qualification before independent work?
39.3 Refresher training schedule?
39.4 Training effectiveness checked (errors/trends)?

40) Are computerized systems/ELN controlled (if used)?

40.1 User access controls (unique logins)?
40.2 Audit trail enabled and reviewed?
40.3 Data backup/archival available?
40.4 Template/version control for electronic records?

41) Are raw materials for development controlled like GMP where required?

41.1 Status labels and expiry/retest controlled?
41.2 Approved suppliers preferred and documented?
41.3 Small-lot dispensing traceability?
41.4 Storage conditions monitored?

42) Are sterile development clean practices followed (where applicable)?

42.1 Clean area behavior and cleaning logs maintained?
42.2 Bioburden controls for solutions established?
42.3 Filtration handling prevents contamination?
42.4 Micro interface defined (sampling, testing, release gates)?

43) Is formulation selection decision documented (why final formula chosen)?

43.1 Criteria includes CQAs, manufacturability, stability, cost?
43.2 Comparative data tables available?
43.3 Risk assessment updated with final choice?
43.4 Sign-off by cross-functional team?

44) Are development specifications defined and versioned?

44.1 Interim specs exist for prototypes (stage appropriate)?
44.2 Specs link to analytical methods?
44.3 Change control for spec updates?
44.4 Transition to commercial spec plan exists?

45) Is cleaning and lab housekeeping adequate in FD areas?

45.1 Cleaning schedules and logs maintained?
45.2 Potent/hormone cleaning controls stricter and documented?
45.3 Material segregation and “one at a time” practice?
45.4 Waste bins labeled and removed on schedule?

46) Is data integrity (ALCOA+) maintained in lab notebooks?

46.1 Contemporaneous entries (no rewriting later)?
46.2 Corrections GDP compliant (single line, date, sign, reason)?
46.3 No loose papers without attachment control?
46.4 Supervisor review frequency and evidence?

47) Are project deliverables archived and retrievable?

47.1 Final reports stored in controlled repository?
47.2 Version history retained?
47.3 Retrieval demonstrated quickly during audit?
47.4 Retention periods defined?

48) Is there control for near-miss in development (mix-up, wrong version)?

48.1 Near-miss log maintained?
48.2 Root cause and actions documented?
48.3 Trending of repeated near-misses?
48.4 Training/SOP updated from lessons learned?

49) Are safety/EHS requirements integrated (especially hormone/potent)?

49.1 Hazard assessments available?
49.2 Exposure controls/PPE training documented?
49.3 Spill kit availability and drill evidence?
49.4 Waste disposal compliant with hazardous rules?

50) Is FD ready for tech transfer with a complete package?

50.1 Process description clear and reproducible?
50.2 Critical materials list + supplier info included?
50.3 CPP/CQA control strategy proposed?
50.4 FD sign-off and DQA review recorded?

Auditor 2 — Analytical Development (AD) — 50 Points

1) Is there an Analytical Development strategy per project?

1.1 Target Method Profile (TMP) defined (purpose, sensitivity, speed)?
1.2 Method scope covers assay, impurities, dissolution, KF, GC where needed?
1.3 Stage-appropriate lifecycle plan (dev → validation → transfer)?
1.4 Roles and review responsibilities documented?

2) Are method development records complete and traceable?

2.1 Lab notebook/ELN captures experiments and decisions?
2.2 Failed trials documented (not hidden)?
2.3 Clear rationale for parameter choices (column, pH, mobile phase)?
2.4 Supervisor review evidence?

3) Are reference standards/impurity standards controlled?

3.1 Primary standard traceability (COA, storage, expiry)?
3.2 Working standards qualified and documented?
3.3 Potency/correction factors applied correctly?
3.4 Solution stability/expiry defined for standards?

4) Are critical reagents/solvents controlled?

4.1 HPLC/GC grade verification and labeling?
4.2 Volumetric solution standardization records?
4.3 “Top-up” prohibited and monitored?
4.4 Expired reagents disposal documented?

5) Are instruments qualified for development testing?

5.1 HPLC/GC/KF/Dissolution qualification and calibration status?
5.2 PM and breakdown logs maintained?
5.3 Balance calibration and daily checks?
5.4 Temperature devices (ovens/fridges) verified?

6) Are chromatography system suitability requirements defined for dev methods?

6.1 SST criteria defined (RSD, tailing, plates, resolution)?
6.2 SST failure handling documented?
6.3 Carryover checks and blanks used?
6.4 Standard bracketing strategy defined?

7) Is integration/reprocessing controlled (data integrity risk)?

7.1 Integration guidelines exist?
7.2 Manual integration allowed only with justification?
7.3 Audit trail reviewed (who changed what/when)?
7.4 Deleted injections documented and justified?

8) Are forced degradation studies adequate (stability-indicating proof)?

8.1 Stress conditions cover acid/base/oxidation/heat/light?
8.2 Mass balance considered?
8.3 Degradant separation demonstrated?
8.4 Conclusions documented and approved?

9) Is specificity demonstrated (placebo/interference)?

9.1 Placebo interference checked for current formulation?
9.2 Impurity peaks resolved from API peak?
9.3 Preservatives/excipients interference checked (eye drops)?
9.4 Filter/diluent peaks ruled out?

10) Is sample preparation robust and controlled?

10.1 Extraction time/sonication controlled?
10.2 Filter compatibility/adsorption study available?
10.3 Sample solution stability established?
10.4 Dilution scheme error-proofed (checklists)?

11) Are method validation parameters planned stage-appropriately?

11.1 Accuracy/precision plans defined?
11.2 Linearity/range planned with levels and replicates?
11.3 LOD/LOQ determination approach defined?
11.4 Robustness study plan exists?

12) Are development reports reviewed and approved?

12.1 Protocols and reports controlled by document system?
12.2 Deviations during validation documented?
12.3 Acceptance criteria justified?
12.4 QA/DQA review sign-offs present?

13) Are GC residual solvents methods controlled (if applicable)?

13.1 Headspace parameters locked and justified?
13.2 Leak checks/crimp integrity controls?
13.3 Calibration curve acceptance criteria defined?
13.4 Reinjection policy controlled?

14) Are KF moisture methods controlled?

14.1 Drift/blank limits defined?
14.2 Reagent factorization records?
14.3 Moisture pickup prevention in sample handling?
14.4 OOT trending for moisture?

15) Is dissolution method development scientifically justified?

15.1 Medium selection and sink conditions justified?
15.2 Apparatus (paddle/basket) selection justified?
15.3 Filter compatibility confirmed?
15.4 Discriminatory ability evaluated (process/formulation changes)?

16) Are dissolution equipment controls adequate during development?

16.1 Mechanical calibration evidence?
16.2 Vessel verification/PVT if applicable?
16.3 Timer accuracy and sampling discipline?
16.4 Cleaning/carryover prevention?

17) Are impurity profiles managed and trended?

17.1 Unknown peaks handling SOP?
17.2 Reporting thresholds defined?
17.3 Impurity reference standards controlled?
17.4 Trending across prototypes and stability timepoints?

18) Is method suitable for Women Hormone/potent products?

18.1 Sensitivity/LOQ adequate for low-dose?
18.2 Cross-contamination prevention in sample prep?
18.3 Dedicated consumables or cleaning verification?
18.4 Analyst PPE and safety controls?

19) Are stability sample testing methods consistent and controlled?

19.1 Same method version used across time?
19.2 Reinjection windows controlled?
19.3 Stability OOT trending performed?
19.4 Data packages reviewed and approved?

20) Are OOS/OOT handled correctly in AD work?

20.1 Phase-I lab investigation documented?
20.2 Retesting rules controlled (not testing into compliance)?
20.3 Root cause and CAPA recorded where needed?
20.4 QA visibility on critical OOS?

21) Are deviations recorded for analytical work?

21.1 Triggers defined (wrong standard, instrument issues, late testing)?
21.2 Impact assessment documented?
21.3 Overdue deviation tracking?
21.4 CAPA effectiveness checks?

22) Are method changes controlled via change control?

22.1 Rationale for change documented?
22.2 Impact assessed on past results and stability?
22.3 Training performed before implementing?
22.4 Version history traceable?

23) Is method transfer readiness assessed?

23.1 Transfer protocol template exists?
23.2 Critical parameters identified?
23.3 Acceptance criteria for transfer defined?
23.4 Training plan for receiving lab included?

24) Are raw data packages complete and traceable?

24.1 Sequence, SST, chromatograms, calculations included?
24.2 Audit trail snapshots included where needed?
24.3 Reviewer checklist used?
24.4 Archival and retrieval tested?

25) Is computerized system access controlled?

25.1 Unique user IDs enforced?
25.2 Role-based permissions?
25.3 Audit trail enabled and reviewed?
25.4 Backup/restore process verified?

26) Are Excel templates validated and controlled (if used)?

26.1 Validation report exists?
26.2 Formula lock and access restriction?
26.3 Version control prevents local copies?
26.4 QA approval for changes?

27) Are calculations independently verified?

27.1 Second-person check required?
27.2 Units/rounding rules defined?
27.3 Potency/moisture corrections applied consistently?
27.4 Transcription reconciliation step exists?

28) Are sample/standard storage conditions controlled?

28.1 Fridge/freezer monitoring?
28.2 Light protection where needed?
28.3 Labeling includes prep date/expiry?
28.4 Disposal of expired solutions documented?

29) Are lab housekeeping and segregation adequate?

29.1 Solvent segregation and labeling?
29.2 Waste solvent handling compliant?
29.3 Potent/hormone segregation?
29.4 Cleaning schedules recorded?

30) Are training/authorization controls strong?

30.1 Training matrix per instrument/method?
30.2 Qualification before independent work?
30.3 Refresher training schedule?
30.4 Analyst error trending for retraining?

31) Are outsourced analytical activities controlled (CRO)?

31.1 Vendor qualification and quality agreement?
31.2 Raw data ownership and review?
31.3 Sample chain of custody?
31.4 Deviation/OOS communication timelines?

32) Are reagents/media for microbiological tests in AD scope controlled (if applicable)?

32.1 Labeling and expiry controls?
32.2 Storage conditions monitored?
32.3 Method suitability defined?
32.4 Review/approval defined?

33) Are placebo and formulation changes reflected in method specificity?

33.1 Placebo composition kept current?
33.2 Specificity reassessed after formulation change?
33.3 Forced degradation repeated if needed?
33.4 Change documented via change control?

34) Are carryover and contamination controls adequate?

34.1 Carryover checks included in sequences?
34.2 Needle wash settings controlled?
34.3 Blank acceptance criteria defined?
34.4 Actions taken when carryover observed?

35) Are solution stability studies adequate?

35.1 Standard and sample stability tested across expected run time?
35.2 Storage condition defined (room temp/fridge)?
35.3 Reinjection limits defined?
35.4 Deviations for exceeded reinjection window?

36) Are column and consumables managed?

36.1 Column ID and history tracked?
36.2 Storage conditions for columns?
36.3 Column change impact assessed?
36.4 Lot-to-lot consumable variability considered?

37) Is the method robust to small variations?

37.1 Deliberate variations tested (pH, flow, temp)?
37.2 Acceptance criteria defined?
37.3 Conclusions documented?
37.4 Robustness issues feed back to FD/process?

38) Is reporting consistent and controlled?

38.1 Report templates version controlled?
38.2 Correct units and rounding used?
38.3 Reviewer checklist includes spec comparison?
38.4 Corrections handled via GDP/e-signature?

39) Are development specifications aligned with methods?

39.1 Interim acceptance criteria defined?
39.2 Linked to method performance (LOQ)?
39.3 Updated as product matures?
39.4 DQA review present?

40) Are method lifecycle documents archived?

40.1 Protocols, reports, raw data retained?
40.2 Retrieval demonstrated during audit?
40.3 Retention period defined?
40.4 Obsolete versions archived and access controlled?

41) Do you trend method performance?

41.1 SST failures tracked?
41.2 Analyst/instrument bias trends?
41.3 Drift or recurring issues trigger CAPA?
41.4 Trending reviewed and signed?

42) Are near-misses captured (wrong method version, wrong integration)?

42.1 Near-miss log exists?
42.2 Root cause and lessons learned?
42.3 SOP/training updates done?
42.4 Recurrence monitoring?

43) Are security and confidentiality maintained for development data?

43.1 Access control for project data?
43.2 Controlled sharing with partners?
43.3 Audit logs maintained?
43.4 Data export restrictions?

44) Are sterile product analytical needs addressed?

44.1 Particulate/clarity methods readiness (if applicable)?
44.2 Preservative assay method suitability?
44.3 Leachables screening strategy (as stage appropriate)?
44.4 Micro interface clearly defined?

45) Are transfer packages prepared properly?

45.1 Method description + critical parameters included?
45.2 Sample prep and stability instructions included?
45.3 Troubleshooting guidance included?
45.4 AD sign-off and DQA review?

46) Are ad hoc tests controlled (non-standard experiments)?

46.1 Documented objective and approval?
46.2 Raw data captured properly?
46.3 Results not used for release decisions improperly?
46.4 Archived and reviewed?

47) Are instrument software settings controlled?

47.1 Processing methods locked?
47.2 Time/date settings controlled?
47.3 User privileges reviewed?
47.4 Audit trail review evidence?

48) Is lab safety adequate (solvents, potent)?

48.1 MSDS access and training?
48.2 Fume hood use and maintenance?
48.3 Waste segregation?
48.4 Incident reporting?

49) Is management review done for AD metrics?

49.1 KPIs defined (cycle time, OOS rate, overdue reports)?
49.2 Management review minutes available?
49.3 Action items tracked?
49.4 Improvements documented?

50) Is AD output ready for registration/commercialization?

50.1 Stability-indicating evidence complete?
50.2 Validation/transfer readiness confirmed?
50.3 Data integrity and traceability assured?
50.4 Final method package approved by DQA?

Auditor 3 — Development Quality Assurance (DQA) — 50 Points

1) Is phase-appropriate GMP defined for development?

1.1 Stage definitions exist (research vs development vs pilot vs clinical)?
1.2 Controls proportionate to risk and intended use?
1.3 Clear guidance for what must be documented?
1.4 Staff trained on development GMP expectations?

2) Is there a DQA governance model for projects?

2.1 DQA role in reviews/approvals defined?
2.2 Project quality plan exists?
2.3 Quality gate reviews held (go/no-go)?
2.4 Minutes and actions tracked?

3) Document control system for development

3.1 SOPs/protocols/reports controlled with versions?
3.2 Obsolete documents prevented from use?
3.3 Distribution control (who has access)?
3.4 Archival and retention rules?

4) Control of development SOPs

4.1 SOP list covers key activities (batch records, sampling, data integrity)?
4.2 SOP training completion tracked?
4.3 Deviations to SOP handled formally?
4.4 Periodic SOP review schedule?

5) Review and approval of protocols

5.1 Stability/validation/DoE protocols reviewed by DQA?
5.2 Acceptance criteria justified?
5.3 Risk assessments included?
5.4 Protocol deviations captured and approved?

6) Review and approval of reports

6.1 Development reports reviewed with checklist?
6.2 Raw data traceability verified?
6.3 Conclusions supported by results?
6.4 Report version control maintained?

7) Data integrity program (ALCOA+)

7.1 Data integrity SOPs exist for development?
7.2 Unique logins enforced for systems?
7.3 Audit trail review requirements defined?
7.4 Data integrity incidents managed with CAPA?

8) Computerized system governance (CSV where applicable)

8.1 System inventory exists (ELN, LIMS, chromatography software)?
8.2 Validation status defined for intended use?
8.3 Access control and periodic review?
8.4 Backup/restore evidence?

9) Change control system for development

9.1 Change control applies to formulation, method, equipment, supplier changes?
9.2 Impact assessment required (CQA/CPP/stability/transfer)?
9.3 Approvals required before implementation?
9.4 Change effectiveness reviewed?

10) Deviation management in development

10.1 Clear triggers for deviations?
10.2 Investigation quality (root cause, impact assessment)?
10.3 Overdue deviation tracking?
10.4 QA approval for closure?

11) CAPA system effectiveness

11.1 CAPA initiated based on deviation/OOS/trends?
11.2 CAPA actions are specific and owned?
11.3 Effectiveness checks defined with evidence?
11.4 Recurrence monitored?

12) OOS/OOT governance in development testing

12.1 OOS procedure applied in dev labs?
12.2 Retesting rules prevent testing into compliance?
12.3 OOT trending program exists?
12.4 QA oversight documented?

13) Supplier and vendor qualification oversight (CRO/CMO)

13.1 Vendor qualification procedure exists?
13.2 Quality agreements define responsibilities and data access?
13.3 Audit program for key vendors?
13.4 Vendor performance trending?

14) Material control expectations in development

14.1 Raw materials labeled with status/expiry?
14.2 Use of non-GMP material risk assessed?
14.3 Traceability to lots maintained?
14.4 Storage conditions monitored?

15) Batch record / lab record templates governance

15.1 Standard templates exist and controlled?
15.2 GDP requirements included?
15.3 Review and approval workflow?
15.4 Template changes controlled?

16) Training and competency system

16.1 Training matrix exists for FD/AD staff?
16.2 Qualification before independent work?
16.3 Refresher training schedule?
16.4 Training effectiveness monitoring?

17) Management of potent/Women Hormone risks

17.1 HBEL/PDE risk management included in quality planning?
17.2 Segregation and cleaning verification requirements defined?
17.3 Waste disposal controls and EHS interface?
17.4 Incident reporting and escalation?

18) Cross-contamination prevention governance

18.1 Facility and workflow segregation assessed?
18.2 Cleaning validation/verification strategy defined for dev?
18.3 Dedicated tools/consumables rules?
18.4 Effectiveness checks and audits?

19) Sterile development quality governance

19.1 Sterile development activities have defined controls?
19.2 Micro interface (bioburden, sterility, endotoxin) clear?
19.3 Filter integrity/hold times expectations?
19.4 Deviations escalated appropriately?

20) Stability program QA oversight

20.1 Protocol approval and change control?
20.2 Chamber qualification status reviewed?
20.3 Excursions handled with impact assessment?
20.4 Stability data trending and reporting?

21) Sample retention and traceability governance

21.1 Retention policy for dev samples defined?
21.2 Storage condition controls?
21.3 Access logs?
21.4 Destruction authorization?

22) Tech Transfer (TT) quality oversight

22.1 TT checklist and deliverables defined?
22.2 Cross-functional review of TT package?
22.3 Deviations during TT managed?
22.4 Post-transfer feedback loop exists?

23) Control strategy development oversight

23.1 Link QTPP → CQA → CPP → controls documented?
23.2 Strategy updated with learning?
23.3 Risks and mitigations documented?
23.4 QA approval of control strategy milestones?

24) Design of Experiments (DoE) governance

24.1 DoE protocol approval required?
24.2 Data integrity controls on DoE data?
24.3 Statistical review competence available?
24.4 Conclusions appropriately used (no over-claiming)?

25) Packaging/CCIT oversight for sterile products

25.1 Packaging component changes assessed for impact?
25.2 CCIT strategy considered and documented?
25.3 Supplier qualification for stoppers/vials?
25.4 Complaint/leaker trend readiness?

26) Data review checklists and review discipline

26.1 Reviewer checklists exist for lab records and analytical packages?
26.2 Review independence ensured?
26.3 Backdating controls?
26.4 Findings tracked to CAPA?

27) Audit program for development areas

27.1 Internal audit schedule exists for FD/AD?
27.2 Audit findings tracked to closure?
27.3 Repeat findings analyzed for systemic issues?
27.4 Management review of audit outcomes?

28) Metrics/KPI governance

28.1 KPIs defined (deviation aging, OOS rate, cycle time)?
28.2 KPI review meetings documented?
28.3 Actions assigned and tracked?
28.4 Effectiveness of improvements verified?

29) Control of outsourced data and raw data availability

29.1 Contracts require raw data access?
29.2 Data review performed before acceptance?
29.3 Data integrity expectations defined?
29.4 Audit rights included?

30) Laboratory safety & compliance oversight (QA interface)

30.1 EHS training tracked?
30.2 Incident reporting and investigation system?
30.3 Chemical/solvent waste compliance checks?
30.4 Potent exposure control oversight?

31) Computer access management

31.1 User provisioning/deprovisioning controlled?
31.2 Periodic access review performed?
31.3 Shared accounts prohibited?
31.4 Password policies enforced?

32) Archival and record retention

32.1 Retention periods defined for protocols/raw data/reports?
32.2 Archival storage secure and retrievable?
32.3 Electronic record integrity preserved?
32.4 Retrieval test evidence?

33) Handling of errors/near-misses

33.1 Near-miss log exists?
33.2 Root cause and actions documented?
33.3 Learning shared across teams?
33.4 Trend analysis performed?

34) Labeling and identification control (development samples)

34.1 Sample labels standardized?
34.2 Mix-up prevention controls?
34.3 Relabeling rules GDP compliant?
34.4 Reconciliation rules for samples?

35) Control of interim specs and acceptance criteria

35.1 Stage-appropriate specs exist?
35.2 Specs linked to method capability (LOQ)?
35.3 Spec changes controlled?
35.4 Transition plan to commercial specs?

36) Method lifecycle QA oversight

36.1 Method development deliverables defined?
36.2 Validation/verification readiness review?
36.3 Transfer protocols reviewed?
36.4 Post-transfer performance monitoring?

37) Deviations for stability/TT activities

37.1 Missed pulls handled via deviation?
37.2 Late testing impact assessed?
37.3 TT trial failures investigated?
37.4 Effectiveness checks?

38) Handling of excursions (storage, chambers, transport)

38.1 Excursion logs maintained?
38.2 Impact assessments documented?
38.3 QA approvals recorded?
38.4 Corrective actions tracked?

39) Quality review of development batch records

39.1 Batch record completeness verified?
39.2 Traceability of materials/equipment?
39.3 Deviations documented and assessed?
39.4 Approval prior to using results for decisions?

40) Integration of RA/Regulatory requirements

40.1 Regulatory expectations communicated into development controls?
40.2 Document readiness for submission?
40.3 Change impact assessed for registration strategy?
40.4 Approval workflows include RA when needed?

41) Supplier CoA reliance oversight (development stage)

41.1 Reduced testing risk assessment?
41.2 Periodic verification testing?
41.3 Trend review of CoA vs internal?
41.4 Controls for counterfeit prevention?

42) Quality oversight of potent cleaning verification

42.1 Cleaning acceptance criteria defined?
42.2 Records reviewed?
42.3 Failures trigger CAPA?
42.4 Effectiveness verified?

43) Governance of method integration/data processing

43.1 Integration guidelines approved?
43.2 Audit trail review required?
43.3 Role permissions controlled?
43.4 Deviations for data processing issues?

44) Governance of dissolution equipment and method controls

44.1 Calibration/verification oversight?
44.2 Method discriminatory evidence reviewed?
44.3 OOS investigations quality reviewed?
44.4 Trend monitoring for drift?

45) Governance of KF and GC methods

45.1 Drift/leak controls reviewed?
45.2 Reagent/standard controls reviewed?
45.3 OOT trending reviewed?
45.4 Failures investigated with CAPA?

46) Quality agreement coverage for development partners

46.1 Agreement includes data integrity and record access?
46.2 Change notification required?
46.3 Deviation/OOS communication timelines?
46.4 Audit rights and expectations?

47) Review of final project conclusions

47.1 Final development report reviewed for completeness?
47.2 Decision rationale traceable?
47.3 Risks documented for TT/commercial?
47.4 Approval/sign-off recorded?

48) Quality oversight of sample storage and retention

48.1 Storage monitoring (temp/RH) verified?
48.2 Excursions handled?
48.3 Sample access controlled?
48.4 Destruction authorization?

49) Readiness for inspection (audit readiness)

49.1 Records are retrievable quickly?
49.2 Staff can explain procedures consistently?
49.3 Evidence of review and approvals exists?
49.4 Open issues tracked and visible?

50) Management review of development quality system

50.1 Management review meetings documented?
50.2 Quality risks and trends reviewed?
50.3 Actions assigned and tracked?
50.4 Effectiveness of improvements verified?

Comprehensive Audit Checklist for Product Development Department Read More »

How long do drug patents last?

Product Development, Regulatory, research & development, research and development, RND

A drug patent is one of the most important legal protections in the pharmaceutical industry. It gives a company the exclusive right to make, use, and sell an invention related to a medicine for a limited time. That exclusivity can be worth billions, and it also shapes when lower-cost generic drugs or biosimilars can enter the market.

So, how long do drug patents last? The headline answer is straightforward: most drug patents last 20 years. But the practical answer is more nuanced because that 20-year clock usually starts before the drug ever reaches patients.

 

This guide explains the standard length of a drug patent, why the real “market exclusivity” can be shorter, how extensions work (like U.S. patent term restoration and EU SPCs), and how multiple patents and regulatory rules affect when competition can begin.

The basic rule: a drug patent usually lasts 20 years

In many countries, including the United States and across Europe, the standard term for a drug patent is:

  • 20 years from the earliest effective filing date (often the first non‑provisional application date)

This 20-year term is rooted in international norms under the WTO’s TRIPS Agreement, which harmonized basic patent terms in much of the world.

Important detail: the clock starts at filing, not approval

The biggest misunderstanding is thinking a drug patent lasts 20 years from when the medicine is approved or launched. Typically, it does not.

Pharmaceutical companies often file patents early—sometimes when the compound is newly discovered or when early lab results are promising. Clinical trials and regulatory review can take many years after that.

Why “20 years” often becomes much less in the real world

A new drug usually goes through:

  1. Discovery and preclinical research
  2. Clinical trials (Phase 1, 2, and 3)
  3. Regulatory review (FDA in the U.S., EMA in Europe, etc.)
  4. Manufacturing scale-up and launch

It’s common for this process to take 8–12 years, and sometimes longer.

What that means for effective patent life

If a company files the core drug patent early and it takes 10 years to reach approval, then even with a full 20-year term the company may have only:

  • about 10 years of remaining patent life after approval

In other words, the “effective” patent-protected sales window is often far less than 20 years, unless extensions or other exclusivities apply.

What exactly does a drug patent protect?

A drug patent can cover different aspects of a medicine. Some are broader and more valuable than others. Common patent types include:

1) Compound (active ingredient) patents

This is often the most important patent: it covers the chemical molecule (or, for biologics, certain compositions). If a generic uses the same active ingredient, it can infringe.

2) Formulation patents

These cover how the drug is put together (e.g., extended-release tablets, specific excipients, stable liquid forms). A formulation patent can matter if it’s hard to design around.

3) Method-of-use patents

These cover how the drug is used, such as treating a particular disease, patient subgroup, dosing regimen, or combination therapy.

4) Process/manufacturing patents

These cover methods of making the drug. Generics may avoid these by using a different manufacturing route, but process patents still play a role in enforcement.

Key takeaway: A single product can be associated with many patents, and each can have its own expiration date. When people ask how long a drug patent lasts, they often mean the earliest and strongest patent—usually the compound patent—but in practice there may be a “patent landscape” around the product.

Patent term extensions: can a drug patent last longer than 20 years?

Because regulators require extensive testing before a medicine can be sold, many jurisdictions provide mechanisms to restore some lost time. These don’t usually create indefinite protection, but they can add meaningful years.

United States: Patent Term Extension (PTE) under Hatch-Waxman

In the U.S., a qualifying drug patent may receive a Patent Term Extension to compensate for time spent in clinical testing and FDA review.

General features (simplified):

  • Extension is based on parts of the regulatory review and clinical testing period.
  • The extension is typically capped at 5 years.
  • There is also a cap related to how long the product can remain protected after approval (often discussed as not exceeding 14 years of effective post‑approval patent life for the extended patent, depending on circumstances).

Not every patent qualifies. Usually, only one patent per approved product gets a PTE, and the patent must meet statutory requirements.

European Union: Supplementary Protection Certificate (SPC)

In the EU, a comparable mechanism is the Supplementary Protection Certificate (SPC).

Typical SPC features:

 

  • Can extend protection by up to 5 years
  • In some cases, an additional 6 months is possible for completing approved pediatric studies (often called a pediatric extension)

An SPC is tied to an authorized medicinal product and the patent protecting it, and it begins after the underlying patent expires.

Other countries have similar mechanisms

Many other jurisdictions have their own versions of restoration or supplementary protection, with different rules and limits (for example, Japan has patent term extension provisions for pharmaceuticals). The details vary widely, but the policy goal is similar: restore part of the time consumed by mandatory regulatory processes.

Patents vs. regulatory exclusivity: they are not the same

A drug patent is a property right granted under patent law. But drugs can also have regulatory exclusivity, which comes from drug approval laws and can block certain competitive approvals even if no patent exists (or if the patent has expired or is invalidated).

Why regulatory exclusivity matters

Regulatory exclusivity can delay generic or biosimilar competition because competitors may be prevented from relying on the originator’s clinical data for a certain period.

In practice, a drug’s competitive protection may come from:

  • Drug patent protection
  • Regulatory exclusivity
  • Or both overlapping together

Examples of regulatory exclusivity (high-level)

Rules differ by region and product type, but common frameworks include:

  • United States (small-molecule drugs): a “new chemical entity” (NCE) often receives 5 years of data exclusivity, with other add-ons possible (e.g., for new clinical investigations or orphan indications).
  • United States (biologics): biologics typically receive 12 years of exclusivity under U.S. law.
  • European Union: a widely cited structure is “8+2+1” (data exclusivity + market exclusivity + possible extra year for a significant new indication).

These exclusivities are separate from any drug patent term and can be crucial, especially when patents are weak, narrow, or challenged.

Why one drug may seem “patented” long after 20 years: multiple patents and layered protection

You may hear that a medicine is “still under patent” decades after it was invented. Often, this perception comes from multiple later-filed patents, such as:

  • New formulations (extended release, new delivery systems)
  • New methods of treatment
  • New combinations with other drugs
  • New manufacturing improvements

This is sometimes called “secondary patenting.” Supporters argue it rewards real incremental innovation (better safety, better dosing, better adherence). Critics argue it can be used to delay competition with patents of limited therapeutic value. In any case, it is a common reason a product has a long list of patent expirations.

Patent listings and litigation can influence timing

In the U.S., patent disputes around generic entry often involve the “Orange Book” listing system for small-molecule drugs. When a generic company challenges patents, litigation timelines and regulatory rules can affect when approval occurs. In Europe, patent enforcement and injunction practices also affect market timing.

Bottom line: Even if the original compound drug patent is near expiration, other patents and legal outcomes may still shape the competitive landscape.

Small-molecule drugs vs. biologics: patent and competition timelines differ

Small molecules (traditional drugs)

  • Usually easier to copy exactly
  • Generic competition can be intense and can rapidly reduce price
  • Patents (compound + formulation + method) and exclusivities strongly affect when generics can file and launch

Biologics (large, complex molecules)

  • Harder to replicate; competitors make biosimilars, not identical copies
  • Regulatory pathways and manufacturing complexity can delay competition even after the main drug patent expires
  • Patent disputes can involve larger “patent thickets” (many patents around processes, formulations, and uses)

While the standard drug patent term is still typically 20 years from filing, the real-world competition timeline often differs substantially between small molecules and biologics.

A practical way to estimate how long a drug patent lasts “in the market”

If you want a realistic estimate of how long patent protection may matter commercially, ask these questions:

  1. When was the earliest patent filed?
    The earliest filing date often controls the expiration of the core compound patent.
  2. When was the drug approved?
    Approval date tells you how much of the 20-year term was already consumed.
  3. Was there a patent term extension (PTE/SPC)?
    This can add up to 5 years (and sometimes more with pediatric add-ons in some regions).
  4. Are there additional patents that could block generic/biosimilar entry?
    Formulation and method-of-use patents may matter if competitors can’t easily design around them.
  5. Is there regulatory exclusivity running alongside patents?
    Exclusivity may delay competition even if patents expire.
  6. Are patents being challenged?
    Patents can be invalidated, narrowed, or found non-infringed, which can accelerate competition.

This framework is often more useful than focusing on the 20-year number alone.

A simple timeline example (illustrative)

Imagine a company files a compound drug patent in 2010.

  • Standard patent expiration: 2030 (20 years from filing)
  • The drug is approved in 2018
  • Remaining patent life at approval: 12 years
  • If a PTE/SPC adds 3 years, the effective expiration could become 2033 for that specific extended protection (depending on jurisdiction and rules)
  • Other later patents (e.g., a 2016 formulation patent) might expire in 2036, but only matter if they are valid, enforceable, and actually block competitors

This shows why the answer to “how long does a drug patent last?” is often “20 years from filing”—followed by “but the competitive impact depends on a lot of other dates.”

What happens when a drug patent expires?

When the relevant drug patent and exclusivities no longer block competition:

  • Generic drugs (for small molecules) may enter, often driving substantial price declines.
  • Biosimilars (for biologics) may enter, though market effects can be slower and more variable than with generics.

However, expiration alone doesn’t automatically mean immediate competition. Competitors must still:

  • Obtain regulatory approval
  • Ensure they don’t infringe any remaining patents
  • Navigate legal challenges and launch strategies

Frequently asked questions about drug patent duration

Does a drug patent always last exactly 20 years?

The default term is commonly 20 years from filing, but actual duration can differ due to:

  • Patent term extensions (PTE/SPC)
  • Adjustments for patent office delays in some jurisdictions
  • Early expiry for non-payment of maintenance fees
  • Court decisions invalidating the patent

Can companies “renew” a drug patent forever?

No. Patents are time-limited. A company cannot renew the same drug patent indefinitely. What can happen is that new patents may be filed on improvements (new formulations, new uses, new delivery devices). Those are separate patents with their own 20-year clocks.

Why do companies file patents so early if it reduces market time?

Early filing is often necessary because:

  • Patent systems generally reward being first to file
  • Public disclosure can destroy patentability in many countries
  • Investors and partners often want IP protection early

If a patent expires in one country, does it expire everywhere?

No. A drug patent is territorial. Patent rights and expiration dates depend on:

  • Where patents were filed and granted
  • Local laws on extensions and adjustments
  • Local enforcement and litigation outcomes

Conclusion: the real answer to “How long do drug patents last?”

A drug patent typically lasts 20 years from the filing date, not from the day the drug is approved. Because drug development and regulatory review can consume many years, the effective market exclusivity from patents alone is often much shorter—commonly closer to 8–12 years after approval, though it varies widely.

On top of that, some drugs qualify for patent term extensions (such as U.S. PTE or EU SPCs), which can add up to 5 years (and sometimes an additional pediatric extension in certain places). Finally, regulatory exclusivity and the presence of multiple patents around one product can significantly affect when generics or biosimilars can realistically enter the market.

How long do drug patents last? Read More »

Understanding Stability of Injectable Products

PROD, product, Product Development, Stability, stability study

Quality assurance in pharmaceuticals hinges on stability. For injectable products, where safety, potency, and sterility converge, stability is not just a matter of convenience; it is a scientific and regulatory requirement. Stability determines how the product’s shelf life is established, how recommended storage conditions are ascertained, container-closure compatibility, labelling, and most importantly, patient safety.

This article discusses the fundamentals of stability for injectable products, the design and implementation of stability programs, and the analytical and microbiological considerations separating the different injectable types: small molecules, biologics, and lyophilized products.

 

What Stability Means for Injectable Products

With an injectable formulation, stability means the product will retain its intended physical, chemical, microbiological, therapeutic, and toxicological limitations and characteristics until its expiry date. Stability incorporates several connected subdomains:

Chemical stability — the active ingredient has to retain its potency and purity and not produce dangerous degradants.

Physical stability — clarity, color, and viscosity must be maintained. Precipitation, crystallization, and phase separation must be avoided.

Microbiological stability — for microbiologically sterile preparations, sterility must be maintained. For multi-dose containers, preservative efficacy must be retained.

Particulate stability — no particulate matter, whether visible or sub-visible, must form over time.

Container-closure compatibility — the product and its packaging must not interact significantly through leaching or adsorption.

These aspects collectively determine a product’s shelf life, storage conditions, and in-use stability.

 

Why Injectables Require Special Stability Attention

Injectables go directly into the body’s sterile spaces, like tissues and blood. Any product instability could have immediate and serious consequences.

Toxic Degradants. Degradation products, even in small amounts, can be toxic.

Sterility Maintenance. Loss of preservative activity can lead to the introduction and growth of germs and subsequent infections.

Physical Changes. Precipitation and other physical changes can lead to the formation of emboli and inflammation.

Biological Sensitivity. Structural fragility of proteins and peptides can lead to denaturation through heat, light, and mechanical stress.

Consequently, injectables warrant more detailed data and continuous monitoring, tighter specs, and more comprehensive oversight compared to other forms like tablets and capsules.

 

The Regulatory Framework for Injectable Stability

All injectable stability programs must adhere to internationally harmonized standards and guidelines. The key authorities defining the principles and requirements for stability programs include the:

International Council for Harmonisation (ICH) — with guidelines Q1A(R2) and Q1B on the design, conditions, and photostability of stability studies.

World Health Organization (WHO) — stability testing guidance for APIs and finished products in diverse climates.

U.S. Food and Drug Administration (FDA) — comprehensive design, testing, and documentation expectations for stability programs.

UK Medicines and Healthcare products Regulatory Agency (MHRA) — the incorporation of ICH guidelines into the UK framework.

Pharmaceutical Inspection co-operation Scheme (PIC/S) — embedding stability expectations in the Good Manufacturing Practice (GMP) standards for inspection and compliance.

All together, these frameworks establish and control the global standards for assessing stability of injectable products.

 

Designing a Stability Program for Injectables

For a good stability program, you must have these key parts:

a. Stability-Indicating Analytical Methods

Tests must be proven to show when a product breaks down. Tools like HPLC or UPLC help to split and count the main drug parts and the breakdown products. Other tests, such as looking at pH, how thick a mix is, and checking for tiny bits, add to the chemical checks.

b. Stress Testing / Forced Degradation

Using high stress (like heat, light, adding oxygen, or extreme pH levels) helps find out how and why a product may break down. This also makes sure that the tests used can truly show if a product does remain stable.

c. Selection of Storage Conditions

Picking the right long-term, middle, and fast storage needs is key. Most of the time, long-term settings are 25°C/60% RH or 30°C/65% RH, based on weather zones. For cold items, a range of 2–8°C is normal. For things like shots, how they react to light and heat matters a lot.

d. Batch Selection

Often, tests are run on at least three large-scale batches that show what the making step is like. For things made from living systems, more checks might be needed due to how much they can change.

e. Container-Closure Compatibility

The pack set-up needs to be checked for any parts that might get out, bind, or stick to the drug bits. How they work with glass, plastic, rubber tops, or silicone oil in ready-to-use shots must be looked at with care.

f. Microbiological and Particulate Control

Tests need to show that the product stays clean and the preservatives work. For vials used more than once, the stability after many uses must be checked.

g. Photostability

A lot of injections break down when hit by light. So, these products are put under certain light levels and types to see if they need special packaging or labels.

h. In-use or Dilution Stability

When a product is mixed with other fluids before use, studies have to prove that it stays stable and works well with the tools used to give it.

Special Considerations: Small Molecules, Biologics, and Lyophilisates

a. Small-Molecule Injectables

These are often more firm in their makeup but may face issues like breaking down, reacting with oxygen, or light damage. Efforts on maintaining their stability focus on watching over their purity, acidity levels, and any tiny particles.

b. Biologics (Proteins, Peptides, Vaccines)

These products are very open to harm from their surroundings. They can change shape, stick together, or lose their power even in gentle settings. Hence, tests focused on clumping (with methods like SEC, DLS), checking strength, and maintaining structure are very important. Freeze-drying is a common method used to keep them stable.

c. Lyophilized (Freeze-Dried) Products

For freeze-dried injectables, assessing both the dried form and the mixed solution is crucial. Things like left-over moisture, how quick they mix, and how they hold up after mixing are vital. How well they are packaged is also very important to keep them stable over time.

Particulate Matter: A Critical Quality Attribute

Small bits in items can be a big risk to people. Tests to check how long the product lasts should watch for both big and tiny bits.

  • Visible Particles — If you can see the bits with your eyes, the batch is no good.
  • Sub-visible Particles — Measured by how they block light or how they move in a flow. There are set rules for bits larger than 10 µm and 25 µm in drug standards.

For shots that go in your body made from proteins, clumps of protein can look like bits and might start body defenses by mistake. Because of this, high-level tests are used to tell apart bits from outside and inside.

Bracketing and Matrixing in Stability Studies

Bracketing and matrixing are ways to test efficiently while still keeping data good.

  • Bracketing is when you test only the most and least strong settings (like highest and lowest doses, biggest and smallest boxes).
  • Matrixing is when you test just a few examples at each time.

Both ways need a good reason behind them and must be used with care for risks.

 

Ongoing Stability and Post-Approval Commitments

Stability checks do not stop when a product gets the okay. Makers have to keep doing ongoing stability studies on what they make, all through the product’s live time.

These checks make sure that the way they make things is still good and that the product stays up to its set quality as time goes by.

If there are any changes after approval — like new suppliers, places where they make things, or what they wrap products in — they need extra stability studies to show things are still alike.

 

Temperature Excursions and Cold Chain Management

For many shots, like biologics and vaccines, keeping the right temp during storage and moving them is key. Programs to keep them stable must have:

  • Studies to set clear temperature excursion limits.
  • Checking freeze–thaw cycles to see how tough the product is.
  • Writing down rules for cold chain management, including checked wraps and ways to move stuff.
  • Labelling instructions that tell the do’s and don’ts for temp limits (for example, “Do not freeze” or “Use within X hours after taking out from cold storage”).

Info on how these items are handled and moved in real life should help with what the labels say.

 

Analytical Techniques Commonly Used in Stability Studies

A strong stability program needs good tools that can spot both chemical and physical changes. Often used methods are:

  • HPLC/UPLC — for testing and breaking down products.
  • Mass spectrometry — for making sure of the structure and finding how things break down.
  • Size exclusion chromatography (SEC) — for checking the gathering of proteins.
  • Dynamic light scattering (DLS) — for measuring how big particles are.
  • Microbiological assays — for checking if things are sterile, if there are toxins, and if preservative works.
  • Rheological analysis — for checking how thick things are and if they stay the same physically.
  • Extractable and leachable studies — using tools like GC, LC-MS, and ICP-MS to test for harmful substances.

All these methods must be checked for their aim, how sensitive they are, and if they can be done again, making sure they truly show stability.

 

Risk-Based Approach in Stability Studies

Risk-based ideas are now a big part of making plans for stability. By checking risks, you can focus on key parts, cut down on tests you don’t need, and still stick to the rules.

Key things to think about:

  1. What traits are key for safety and how well the product works?
  2. What breaks down most often?
  3. How do changes in making or packing touch stability?
  4. What could go wrong with the environs during keeping and moving?

Make sure to write down risks and reasons in the stability plans and reports.

Key Expectations from Regulatory Agencies

Regulators want stability plans for injectables to show:

  1. Use of tested, sure methods that can show stability.
  2. Proof of stress tests to know how they break down.
  3. Test batches that show all mixes and pack types.
  4. Meet rules for test conditions (long-term, middle, fast).
  5. Data on stability under light for light-sensitive items.
  6. Proof of how well it fights germs and keeps preservatives working.
  7. Tests for how the container reacts with the content and checking for chemicals leaking.
  8. Keep a steady, ongoing program with info ready for checks.
  9. Check the risks for any grouping or mixing methods.

Common Stability Pitfalls and How to Avoid Them

  1. Non-Stability-Indicating Methods — Methods that can’t split up degradants fail to see when things start to break down.
  2. Ignoring Physical Instability — Biological products might clump together without showing chemical changes.
  3. Inadequate Container Interaction Studies — Not checking early for leachables or sticking can lead to product recalls.
  4. Weak In-use Data — Bottles used many times must prove that their protecting stuff works after each use.
  5. Neglecting Temperature Excursion Studies — Skipping these tests can cause trouble during real-life shipping, making products unusable.

Taking care of these issues early helps in easier reviews and makes sure products are safe.

Integrating Science with GMP

Getting the steadiness right for injectables isn’t just a lab job—it’s a mix of strict science and sticking to GMP rules. Tests need to match up with checked making steps, strong paper work, and data systems you can track.

GMP check groups want makers to keep easy-to-find, full, and traceable steadiness data. If things don’t go as planned or the results are off, you need to look into it and write down what you will do to fix it.

For complex or new injectables, it’s smart to talk to rules setters early. This helps make sure you meet their needs and skips the need for doing the work again, which can cost a lot.

 

The Stability of Injectable Products

The keeping of injectable items steady is a mix of chemistry, tiny life study, pack tech, and rule following. A strong steady plan makes sure the item works as it should, stays safe, and keeps its power all through its life.

Key Aspects:

  • Injectable items, as they are high-risk mixes, need a careful way to look at, test checking, and ongoing watch.
  • Global rules from groups like ICH, WHO, FDA, MHRA, and PIC/S make sure there is a steady science and rule plan all over the world.

In the end, keeping things steady is not just about the tech needs but also about staying true to the safety of the patients and trust in the item. This trust is what makes the base for belief in injectable drugs.

Understanding Stability of Injectable Products Read More »

What is the process of drug development?

development, Product Development, Regulatory, research & development, research and development, RND

Drug making is a hard, closely watched step-by-step process. It turns good science ideas into meds that are safe and work well for people. This long path usually takes 10-15 years and uses up billions of dollars. It has many parts: research, tests, and getting the okay from those in charge.

 

The Foundation of Drug Development

The drug development process starts way before any tests on people. Scientists first find and know about biological targets — key parts like molecules, genes, or cell processes that play a part in sickness. After a lot of study, they figure out how changing these targets could help treat or stop sickness. This key knowledge sets the path for the whole development process.

Today’s drug development depends a lot on new tech like artificial intelligence, computer models, and fast screening systems that can check thousands of bits very quickly. These tools let researchers find good drug options faster than the old ways.

 

Discovery and Early Research Phase

During the discovery phase

Researchers look at many different bits and pieces that might link up with their set target. They check out big groups of molecules, both man-made and from nature, to see which ones work as they want. They might test loads of compounds before they find a few that could be useful for treatment.

Once promising compounds are spotted

Researchers do deep study in labs to learn more about them. They see how the compound acts under various situations, if it stays the same, and how it could be made in big amounts. This first study shows if a compound might really turn into a good drug.

Preclinical Testing: Safety First

Before testing on people can start, building a drug needs a lot of early study.

These studies use lab tests and animal models to look at safety and how the drug works on a bio level. Researchers study how the body deals with the drug, looking at how it’s taken up, sent around, broken down, and thrown out.

Toxicology studies are key in early testing.

Scientists need to find safe dose ranges and see if there are any bad effects. They look at if the stuff might hurt organs, mess up reproduction, or cause cancer. Only stuff that shows it is safe in these tough tests can move to tests on people.

Clinical Trials: The Human Testing Phases

Clinical trials are the big and long part of making a new drug. These well-managed tests happen in clear steps, each meant to check the drug’s safety and how well it works.

  • Phase I Trials:
    This first stage uses a small bunch of healthy folks or ill people, usually from 20 to 100. Main goal here is to check for safety and find the right dose. Scientists watch the people close to see how their bodies deal with the drug and spot any bad effects.
  • Phase II Trials:
    Now, the testing grows to several hundred people who have the sickness the drug aims to fix. At this stage, they check if the drug seems to work and keep an eye on safety. They might try different doses or ways to give the drug to get the best treatment steps.
  • Phase III trials are big studies with hundreds to thousands of people in many places. These key trials match the new drug with old treatments or fake pills, giving clear proof it works. The info from Phase III trials is the main thing used when deciding if a drug should be okayed.

Regulatory Review and Approval

In making drugs, firms join hands with groups that check on drugs, like the FDA in the US or the EMA in Europe. These groups look at info at many points to make sure that the work goes on safe and by the rules.

  • When tests show a drug is safe and works well, firms ask for a green light to sell it.
  • These asks can have loads of pages that cover all parts of making, making sure, and testing the drug.
  • People who know the rules study this info a lot, and it might take months or years to finish their check.

Post-Market Surveillance

  • Continuous Monitoring After ApprovalDrug making does not end when it gets the green light from the ones in charge. After a drug is out for the people to buy, it keeps being watched. This goes on through Phase IV trials and checks after it is on sale. These steps watch how the drug does when it is used in daily life. They look for any bad side effects that did not show up before.
  • Role of Healthcare Providers and PatientsBoth those who give care and those who get it have a role. They tell when bad things happen with a drug. This helps those in charge and the makers know how safe the drug is when used for a long time. This never-ending watch can change the drug’s label, add new cautions, or even, though rarely, pull it from sale if it’s found to be very unsafe.

Manufacturing and Quality Control

Parallel to clinical development, companies must set up trusted manufacturing processes.

  • Drug making means making ways to always make good meds in big amounts.
  • This has making tests to check med quality, setting up supply lines for raw stuff, and making or hiring places to make the stuff.

Quality control steps make sure every batch of meds is up to high purity, strength, and sameness standards.

  • Rules people check the making places and look at quality info to make sure companies keep up these rules all through a drug’s time on the market.

The Economics of Drug Development

The cost of making drugs is a big deal for health care and getting medicine to people. The high price tags are due to successful drugs and many that do not make it through tests. It is said that only one in thousands of hopeful drugs gets the okay from authorities. These money facts steer choices all through the drug making steps. Firms have to weigh the hope held by science against money-making chances. They think about things like how big the market is, other firms making similar drugs, and how much they might charge. Knowing how all this works sheds light on why some sicknesses get more study than others.

Future Directions in Drug Development

The way we make drugs changes fast with new tech and big science wins. Custom medicine plans use gene info to make tight-fit therapies for set groups of people. Gene and cell therapies are whole new ways to treat that need new ways to be made and checked.

Computers that learn on their own are now big help in making drugs by guessing how mixes act, finding new drug spots, and making better test plans. These techs help us make drugs faster and cheaper, which may bring new help to sick folks sooner.

Conclusion

Drug making is one of the hardest and most rules-heavy jobs in today’s science and trade world. From the first find to watching over it after it hits the market, every step has key roles in making sure that new drugs are safe and work well. While this work takes a long time and costs a lot, it runs needed tests to keep public health safe and bring new cures to people who need them. As tech gets better and we learn more about diseases, the way we make drugs will keep getting better, too. This could mean we get new meds out faster but still keep them very safe for folks who use them.

What is the process of drug development? Read More »

Who Sponsors Clinical Trials?

clinical trial, development, Pharma Operations, Pharmaceutics, Pharmacology, Product Development, R&D, Regulatory, RND

Clinical trials are the backbone of medical advancements, bringing new drugs, devices, and therapies to the market. These meticulously designed studies test the safety and efficacy of medical interventions, paving the way for improved healthcare outcomes. But who foots the bill for these complex and often expensive endeavors? Understanding who sponsors clinical trials provides insight into the intricate ecosystem of medical research and the motivations driving innovation. In this article, we’ll dive deep into the world of clinical trial sponsorship, exploring the key players, their roles, and the impact of their contributions.

 

What Are Clinical Trials?

Before we explore the sponsors, let’s briefly define what a clinical trial entails. A clinical trial is a research study conducted with human volunteers to evaluate the effects of a medical intervention, such as a new drug, medical device, vaccine, or treatment protocol. These trials are conducted in phases, each with a specific purpose:

 

Phase I: Tests safety and dosage in a small group.
Phase II: Evaluates efficacy and side effects in a larger group.
Phase III: Confirms effectiveness, monitors side effects, and compares the intervention to existing treatments in large populations.
Phase IV: Post-market studies to gather additional information on long-term effects.

Clinical trials are resource-intensive, requiring significant financial investment, expertise, and time. The costs can range from hundreds of thousands to billions of dollars, depending on the trial’s scope, duration, and complexity. This brings us to the critical question: who sponsors clinical trials, and why?

 

The Key Sponsors of Clinical Trials

Clinical trials are funded by a variety of entities, each with distinct motivations and goals. The primary sponsors include pharmaceutical and biotechnology companies, government agencies, academic institutions, nonprofit organizations, and, in some cases, individual philanthropists or crowdsourcing efforts. Let’s break down each category.

 

1. Pharmaceutical and Biotechnology Companies

The pharmaceutical and biotechnology industries are the largest sponsors of clinical trials worldwide. These companies invest heavily in research and development (R&D) to bring new drugs, biologics, and medical devices to market. According to the Pharmaceutical Research and Manufacturers of America (PhRMA), the biopharmaceutical industry spent over $100 billion on R&D in the United States alone in 2022, with a significant portion allocated to clinical trials.

 

Why Do They Sponsor Clinical Trials?

Profit Motive: Developing a successful drug or device can generate substantial revenue. For example, blockbuster drugs like Humira or Keytruda have earned billions for their manufacturers.
Regulatory Requirements: To gain approval from regulatory bodies like the U.S. Food and Drug Administration (FDA) or the European Medicines Agency (EMA), companies must provide robust clinical trial data demonstrating safety and efficacy.
Market Expansion: Clinical trials allow companies to explore new indications for existing drugs, expanding their market potential.

 

Challenges and Criticisms

While pharmaceutical companies drive innovation, their sponsorship comes with scrutiny. Critics argue that profit-driven motives may lead to biased trial designs, selective reporting of results, or prioritization of lucrative markets over unmet medical needs. To address these concerns, regulatory agencies enforce strict guidelines, and independent oversight bodies, such as Institutional Review Boards (IRBs), monitor trial conduct.

2. Government Agencies

Government agencies play a significant role in sponsoring clinical trials, particularly for research that may not attract commercial interest. In the United States, the National Institutes of Health (NIH) is a leading sponsor, funding thousands of clinical trials annually. Other agencies, such as the Centers for Disease Control and Prevention (CDC) and the Department of Defense (DoD), also contribute.

 

Why Do Governments Sponsor Clinical Trials?

Public Health Priorities: Governments fund trials for diseases with significant public health impacts, such as cancer, infectious diseases, or rare disorders.
Noncommercial Research: They support studies that may not be profitable for private companies, such as trials for neglected tropical diseases or preventive interventions.
Emergency Response: During public health crises, like the COVID-19 pandemic, government agencies rapidly mobilize funding for clinical trials to develop vaccines and treatments.

Examples of Government-Sponsored Trials

What Are Clinical Trials and Why Are They Important?

 

The NIH’s ClinicalTrials.gov database lists thousands of trials funded by federal agencies, covering areas like Alzheimer’s disease, HIV/AIDS, and mental health.
Operation Warp Speed, a U.S. government initiative, provided billions of dollars to accelerate COVID-19 vaccine trials, collaborating with private companies like Pfizer and Moderna.

 

Advantages and Limitations

Government-funded trials are often seen as impartial, prioritizing patient outcomes over profits. However, their budgets are subject to political and economic fluctuations, which can limit their scope compared to industry-funded trials.

 

3. Academic and Research Institutions

Universities, medical schools, and research hospitals frequently sponsor clinical trials, often in collaboration with other entities. These institutions are hubs of scientific discovery, conducting trials to advance medical knowledge and improve patient care.
Why Do Academic Institutions Sponsor Clinical Trials?

Scientific Discovery: Academic researchers aim to answer fundamental questions about disease mechanisms, treatment efficacy, or preventive strategies.
Training and Education: Clinical trials provide hands-on experience for medical students, researchers, and clinicians.
Collaboration: Academic institutions often partner with industry or government sponsors, leveraging their expertise and infrastructure.

Funding Sources

Academic institutions typically rely on grants from government agencies, nonprofit organizations, or industry partners. For example, the NIH’s National Cancer Institute funds numerous cancer-related trials conducted at academic medical centers.

Impact of Academic Sponsorship

Academic-sponsored trials often focus on innovative or exploratory research, such as novel therapies for rare diseases or personalized medicine approaches. They also contribute to the training of future scientists and clinicians, ensuring a steady pipeline of expertise in clinical research.

4. Nonprofit Organizations and Foundations

Nonprofit organizations and charitable foundations are vital sponsors of clinical trials, particularly for diseases that receive limited attention from industry or government. Examples include the Bill & Melinda Gates Foundation, the American Cancer Society, and disease-specific groups like the Cystic Fibrosis Foundation.

 

Why Do Nonprofits Sponsor Clinical Trials?

Mission-Driven Goals: Nonprofits focus on addressing unmet medical needs, such as rare diseases, pediatric conditions, or global health challenges.
Patient Advocacy: Many organizations are founded by patients or their families, driving research to find cures or improve quality of life.
Bridging Gaps: Nonprofits often fund early-stage research or trials that bridge the gap between academic discovery and industry development.

 

Notable Examples

The Cystic Fibrosis Foundation invested heavily in clinical trials for drugs like Trikafta, transforming the lives of patients with cystic fibrosis.
The Michael J. Fox Foundation funds trials to develop treatments for Parkinson’s disease, including studies on disease-modifying therapies.

 

Benefits and Challenges

Nonprofit-sponsored trials are highly focused and patient-centered, but their funding is often limited compared to industry or government resources. They may rely on donations, grants, or partnerships to sustain their efforts.

5. Individual Philanthropists and Crowdsourcing

In rare cases, clinical trials are funded by individual philanthropists or crowdsourcing campaigns. Wealthy individuals may donate to specific causes, while grassroots efforts leverage online platforms to raise funds.
Examples

Philanthropy: High-profile donors like Michael Bloomberg have supported clinical research in areas like public health and cancer.
Crowdsourcing: Platforms like GoFundMe have been used to fund small-scale trials or experimental treatments, particularly for rare diseases.

 

Opportunities and Risks

While these funding sources democratize research, they often lack the scale and rigor of institutional sponsors. Crowdsourced trials may also face ethical concerns, such as inadequate oversight or unrealistic expectations.

 

Collaborative Sponsorship Models

In many cases, clinical trials are sponsored by a combination of entities working together. For example:

Public-Private Partnerships: Government agencies and pharmaceutical companies collaborate to share costs and expertise, as seen in COVID-19 vaccine development.
Consortia: Multiple stakeholders, including industry, academia, and nonprofits, pool resources to tackle complex diseases like Alzheimer’s or cancer.
Contract Research Organizations (CROs): While not sponsors themselves, CROs are hired by sponsors to manage trial operations, ensuring efficiency and compliance.

These collaborative models maximize resources, reduce duplication, and accelerate the pace of research.

 

The Role of Patients and Volunteers

While not sponsors in the financial sense, patients and volunteers are essential to clinical trials. Their participation is invaluable, and sponsors often cover costs like travel, medical care, or stipends to ensure accessibility. Patient advocacy groups also influence trial design and funding priorities, ensuring that research aligns with real-world needs.
The Economics of Clinical Trial Sponsorship
The cost of conducting a clinical trial varies widely based on factors like:

 

Phase: Phase III trials are the most expensive due to large sample sizes and long durations.
Therapeutic Area: Oncology and neurology trials are among the costliest due to complex endpoints and regulatory requirements.
Geography: Trials conducted in multiple countries face higher logistical costs.

According to a 2020 study published in JAMA Internal Medicine, the median cost of a clinical trial is approximately $19 million, with some trials exceeding $1 billion. Sponsors must balance these costs against potential benefits, whether financial, scientific, or societal.

 

Transparency and Ethical Considerations

Sponsorship comes with responsibilities. All sponsors must adhere to ethical standards, ensuring participant safety, informed consent, and data integrity. Transparency is critical, particularly for industry-sponsored trials, where conflicts of interest may arise. Initiatives like ClinicalTrials.gov and the World Health Organization’s International Clinical Trials Registry Platform promote public access to trial information, fostering trust.

 

The Future of Clinical Trial Sponsorship

The landscape of clinical trial sponsorship is evolving, driven by technological advancements and global health challenges. Key trends include:

Decentralized Trials: Digital tools and remote monitoring reduce costs, potentially attracting new sponsors.
Precision Medicine: Trials targeting specific genetic profiles require innovative funding models.
Global Collaboration: International partnerships address pandemics and neglected diseases, pooling resources across borders.

Emerging sponsors, such as tech companies (e.g., Google’s Verily) and patient-driven initiatives, are also entering the space, diversifying the funding ecosystem.

Clinical trials are a cornerstone of medical progress, and their sponsors play a pivotal role in shaping the future of healthcare. From pharmaceutical giants to government agencies, academic institutions to nonprofits, and even individual donors, each sponsor brings unique motivations and resources to the table. Understanding who sponsors clinical trials reveals the complex interplay of science, economics, and ethics that drives innovation. As the field evolves, collaborative and innovative sponsorship models will continue to accelerate the development of life-saving treatments, benefiting patients worldwide.

By shedding light on the funding behind clinical trials, we gain a deeper appreciation for the collective effort required to turn scientific discoveries into tangible solutions. Whether you’re a patient, researcher, or simply curious, recognizing the diverse sponsors of clinical trials underscores the shared commitment to advancing human health.

Who Sponsors Clinical Trials? Read More »

What Are Clinical Trials and Why Are They Important?

clinical trial, Pharma Operations, Product Development, R&D, Regulatory, research & development, research and development, RND

Clinical trials are a cornerstone of modern medicine, playing a pivotal role in advancing healthcare and improving lives. These carefully designed research studies evaluate the safety and effectiveness of new medical treatments, drugs, devices, or interventions. By systematically testing these innovations on human volunteers, clinical trials provide the evidence needed to bring groundbreaking therapies to the public. But what exactly are clinical trials, and why do they matter so much? In this comprehensive guide, we’ll explore the ins and outs of clinical trials, their significance in medical progress, and how they impact patients and society.

 

Understanding Clinical Trials: The Basics

At their core, clinical trials are scientific studies conducted to assess whether a new medical intervention—such as a drug, vaccine, medical device, or treatment protocol—is safe, effective, and beneficial for patients. These trials are meticulously planned and follow strict ethical and scientific guidelines to ensure participant safety and reliable results.
Clinical trials typically involve human volunteers who agree to participate in the study under controlled conditions. Researchers collect data on how the intervention performs, monitoring factors like efficacy, side effects, and overall impact on health. The findings from these studies help determine whether a treatment should be approved for widespread use, modified, or abandoned.
The process of conducting clinical trials is rigorous and often spans several years. It involves collaboration among scientists, doctors, regulatory bodies, and participants. Trials are usually conducted in phases, each with a specific purpose, to gradually build evidence about the intervention’s safety and effectiveness.

 

The Phases of Clinical Trials

Clinical trials are divided into distinct phases, each serving a unique role in the research process. Here’s a breakdown of the four main phases:

Phase I: Safety Testing

Purpose: Phase I trials focus on evaluating the safety of a new intervention in a small group of healthy volunteers (typically 20-100 participants).
Goals: Researchers determine safe dosage ranges, identify side effects, and assess how the body processes the treatment.
Duration: This phase is short, often lasting a few months.
Example: A new cancer drug might be tested to see if it causes adverse reactions at different doses.

Phase II: Efficacy and Side Effects

Purpose: Phase II trials involve a larger group (100-300 participants) and aim to assess the intervention’s effectiveness while continuing to monitor safety.
Goals: Researchers gather preliminary data on whether the treatment works for a specific condition and refine dosage recommendations.
Duration: This phase can last several months to two years.
Example: The same cancer drug might be tested on patients with a specific type of cancer to see if it shrinks tumors.

Phase III: Large-Scale Testing

Purpose: Phase III trials are conducted on a much larger scale (1,000-3,000 participants) to confirm the intervention’s effectiveness, monitor side effects, and compare it to existing treatments or a placebo.
Goals: These trials provide comprehensive data to support regulatory approval.
Duration: This phase can last several years.
Example: The cancer drug is now tested across multiple hospitals to compare its effectiveness against standard treatments.

Phase IV: Post-Market Surveillance

Purpose: Phase IV trials occur after a treatment has been approved and is available to the public. They monitor long-term safety and effectiveness in a broader population.
Goals: Researchers identify rare side effects, assess long-term benefits, and explore additional uses.
Duration: This phase can continue for many years.
Example: The cancer drug is monitored to ensure it remains safe and effective as more patients use it.

Each phase builds on the previous one, ensuring that only safe and effective interventions reach the market. This structured approach is why clinical trials are so critical to medical innovation.

 

Why Are Clinical Trials Important?

Clinical trials are the backbone of medical advancements, driving progress in healthcare and improving patient outcomes. Here are some key reasons why clinical trials are essential:

1. Advancing Medical Knowledge

Clinical trials generate critical data that expands our understanding of diseases and how to treat them. They provide evidence-based insights into what works, what doesn’t, and why. This knowledge shapes medical guidelines, informs clinical practice, and fuels further research.
For example, clinical trials have been instrumental in developing life-saving treatments for conditions like cancer, HIV/AIDS, and heart disease. Without these trials, doctors would rely on guesswork or anecdotal evidence, which could lead to ineffective or harmful treatments.

2. Ensuring Safety and Efficacy

Before any new drug or medical device can be approved for public use, it must undergo rigorous testing through clinical trials. Regulatory agencies like the U.S. Food and Drug Administration (FDA) and the European Medicines Agency (EMA) rely on trial data to evaluate whether a treatment is safe and effective.
Clinical trials help identify potential risks, such as side effects or adverse reactions, ensuring that only treatments with a favorable risk-benefit profile reach patients. This process protects public health and builds trust in medical interventions.

3. Improving Patient Care

The ultimate goal of clinical trials is to improve patient care. By identifying better treatments, clinical trials enhance the quality of life for individuals with chronic or life-threatening conditions. They also contribute to personalized medicine, where treatments are tailored to specific patient groups based on genetic, environmental, or lifestyle factors.
For instance, clinical trials have led to targeted therapies for breast cancer patients with specific genetic mutations, offering more effective and less toxic options than traditional chemotherapy.

4. Providing Access to Cutting-Edge Treatments

Participating in clinical trials gives patients access to new treatments that are not yet available to the public. For individuals with serious or rare conditions, this can be a lifeline, offering hope when standard treatments have failed.
In addition to receiving innovative therapies, trial participants often benefit from close medical monitoring and care from specialized research teams. This can lead to better health outcomes, even for those receiving a placebo.

5. Addressing Unmet Medical Needs

Clinical trials play a crucial role in addressing gaps in healthcare, particularly for rare diseases or conditions with limited treatment options. They drive the development of therapies for underserved populations, ensuring that everyone has access to effective care.
For example, clinical trials have led to breakthroughs in treatments for rare genetic disorders like cystic fibrosis, which previously had few viablea significant portion of the population. These advancements would not have been possible without the structured research provided by clinical trials.

6. Shaping Public Health Policies

The data from clinical trials informs public health policies and guidelines. For instance, clinical trials on vaccines have guided global immunization programs, saving millions of lives. Similarly, trials on lifestyle interventions, such as smoking cessation or dietary changes, have shaped public health campaigns to prevent chronic diseases.

 

How Do Clinical Trials Work?

Clinical trials are complex, involving multiple stakeholders, including researchers, participants, sponsors, and regulatory bodies. Here’s a closer look at how they operate:

1. Study Design

Every clinical trial begins with a detailed study protocol, which outlines the trial’s objectives, methodology, participant criteria, and data collection methods. The protocol ensures consistency and minimizes bias. Common study designs include:

Randomized Controlled Trials (RCTs): Participants are randomly assigned to receive the intervention or a control (e.g., placebo or standard treatment).
Double-Blind Trials: Neither the participants nor the researchers know who is receiving the intervention or placebo, reducing bias.
Crossover Trials: Participants receive both the intervention and control at different times, allowing researchers to compare outcomes within the same group.

2. Participant Recruitment

Recruiting participants is a critical step in clinical trials. Researchers seek volunteers who meet specific eligibility criteria, such as age, medical history, or disease stage. Diversity in trial participants is essential to ensure that findings apply to a broad population.
Participants may be recruited through healthcare providers, online platforms, or community outreach. Informed consent is a key ethical requirement, ensuring that participants understand the trial’s purpose, risks, and benefits before enrolling.

3. Data Collection and Analysis

During the trial, researchers collect data on various outcomes, such as symptom improvement, side effects, or disease progression. Advanced statistical methods are used to analyze the data and determine whether the intervention is effective and safe.

4. Regulatory Oversight

Clinical trials are subject to strict oversight by regulatory bodies and ethics committees. These organizations review study protocols, monitor participant safety, and ensure compliance with ethical standards. In the U.S., the FDA oversees clinical trials, while Institutional Review Boards (IRBs) provide ethical guidance at the institutional level.
Who Can Participate in Clinical Trials?

Clinical trials rely on volunteers, and eligibility varies depending on the study’s goals. Some trials seek healthy individuals, while others focus on patients with specific conditions. Factors like age, gender, medical history, and current health status may influence eligibility.
If you’re interested in participating in a clinical trial, talk to your healthcare provider or visit websites like ClinicalTrials.gov, which lists ongoing trials worldwide. Before joining, carefully review the study’s requirements, risks, and benefits to make an informed decision.

 

Challenges in Clinical Trials

While clinical trials are essential, they face several challenges:

Recruitment Difficulties: Finding enough eligible participants, especially for rare diseases, can be time-consuming.
Diversity Issues: Historically, clinical trials have underrepresented certain groups, such as women, minorities, and older adults, limiting the generalizability of findings.
Cost and Time: Clinical trials are expensive and can take years to complete, delaying the availability of new treatments.
Ethical Concerns: Balancing participant safety with the need for scientific progress requires careful ethical considerations.

Researchers are addressing these challenges through innovative approaches, such as virtual trials, adaptive study designs, and efforts to increase diversity in participant recruitment.

 

The Future of Clinical Trials

The landscape of clinical trials is evolving rapidly, driven by technological advancements and changing healthcare needs. Some exciting trends include:

Digital and Virtual Trials: Wearable devices, mobile apps, and telemedicine are making it easier to conduct trials remotely, improving accessibility and convenience.
Artificial Intelligence (AI): AI is being used to analyze trial data, predict outcomes, and identify suitable participants.
Precision Medicine: Clinical trials are increasingly focused on personalized treatments tailored to individual genetic profiles.
Global Collaboration: International partnerships are accelerating the development of treatments for global health challenges, such as infectious diseases.

These innovations promise to make clinical trials more efficient, inclusive, and impactful in the years to come.

Clinical trials are a vital engine of medical progress, transforming scientific discoveries into real-world treatments that save lives and improve health. By rigorously testing new interventions, clinical trials ensure that patients receive safe, effective, and evidence-based care. They offer hope to those with untreatable conditions, drive innovation, and shape the future of healthcare.
Whether you’re a patient, a healthcare provider, or simply curious about medical research, understanding the importance of clinical trials empowers you to support and engage with this critical process. From developing life-saving drugs to shaping public health policies, clinical trials are at the heart of a healthier, brighter future.
If you’re inspired to learn more or participate in a clinical trial, resources like ClinicalTrials.gov or your healthcare provider can guide you. Together, we can continue to advance medical science and improve lives through the power of clinical trials.

What Are Clinical Trials and Why Are They Important? Read More »

user requirement specification of Equipment

Documentation, Engineering, Product Development, Production

User Requirement Specification is a specific document where end user generally defines needs, target, goal and their expectation for a system, service and product. This is actually blueprint for the development personnel and it help to ensure that the product meet the target for the specific group.

A standard User Requirement Specification includes information about the user group, targeted use of the product, functional requirements, Operational requirements, and performance requirements. It also contains constraints or limitations.

A standard User Requirement establishes a better understanding between the stakeholders regarding a defined outcome; also sets a specific goal for the end-user and helps to save the project, and product delivery time the best thing is its budget-friendly; the user can previously estimate the cost of the specific project.

URS is generally developed by the buyer defining all listed requirements. After the development of a URS, the user sent it to the equipment manufacturer to prepare it as per predefined criteria.

A poorly developed URS is always creating confusion for the manufacturer, you can see the poorly written URS at the manufacturer’s end and If you don’t know how to write URS then you can ask standard URS template from the manufacturer, they are happy to help you. If supplied Template is found near your requirements then you can go with a modified version.

User Requirement Specification when disregarded?

A confusing URS is always disregarded. If the manufacturer can’t read you then the faulty or wrong machine can be developed which can destroy your project and A meaningful and well-written user requirement specification saves time and money; also reduce misunderstanding among the manufacturer.

A series of emails may generate to explain your requirement to the manufacturer which may express your poor level of understanding of the specific requirement also create of the high chance of wrong specification delivery and You have to express the requirement what exactly you are looking for in your User Requirement Specification (URS).

Keep it simple, Specific, and Better user requirement specification creates better outcomes.

Requirements of user and support design, qualification activities, operations, commissioning, and maintenance are mainly present on the URS. It’s good to set your mind at the start of your dream project.

According to Mark R. Smith, MD, Realtech,

“A standard URS shall be clear, jargon-free, easily readable, not hard to understand which helps to software engineer and Designer clearly readable and understandable of the user requirement with minimum cost and maximum output”.

Types of Requirements

There are several types of requirements that are depicted here.
[] Business Requirements
[] Functional Requirements
[] Stakeholder Requirements
[] Non-Functional Requirements
[] Transition Requirements

What thing to consider for user requirement specification (URS)?
Two main things shall be considered during the writing of URS, number one: What shall be included and number two what shall not be included.

What to include:

During the writing of the URS, the actual information shall be included in the URS. More information may require for big projects and less for a small project the basic of all URS shall be specific. Unknowingly including a feature that is not available in the market is the same as knowingly ruining your project.

Knowing then any feature should be included in the URS. The most important thing is to include only those specifications that are necessary. Features that will never be used need not be included but the facility to use updated features can be retained.

What not to include:

Ambiguous words or terms, Features that are not easy to understand, and that no one has yet used, features that are not user-friendly and will never be used, and features that are overpriced but less important shall be avoided.

How to proceed with your User Requirement Specification?

Before proceeding with your URS, define the responsibility of the stakeholders in your URS then collect all stakeholders’ signatures with designation and date. An approved URS shall be procced to the manufacturer to avoid any wanted circumstances. To sign a document means that you are responsible for it.

What should be included in the Introduction section?

In this section, you should describe more briefly about yourself and why this URS has been raised. Give a short description of your organization. Like “We are Startech is a startup organization in west Virginia. We want to install a high tech tablet compression machine to produce almost 6000K tablets per hour. This user requirement specification (URS) documents the user requirements for producing tablet dosage forms in a tablet compression machine.

The objective of the User Requirement Specification

They clearly describe the goal of the project so that anyone understands it. A brief overview of the project shall be included. Mention the actual purpose of the URS.

Who will write the User Requirement Specification?

Anyone can write URS, who has a thorough knowledge of the system, service, product, or machine in question. But you don’t let someone write something they don’t know about, for example, production personnel can’t write the URS of quality control equipment and vice versa.

How to document a User Requirement Specification?

The user will prepare the URS and another SEM will check the URS and Engineering personnel and the head of the user department will Review the document, finally Head of Quality will approve the URS. Always documented hierarchy shall be maintained.

To write user requirement specifications for a pharmaceutical company equipment following points should be included

1. Front Page: URS no., Revision no., Addendum no., Using Facility shall be mentioned.
2. List of revisions: Revision number shall be mentioned (if required).
3. List of addendums: Addendum to be mentioned (if required).
4. Table of Contents: Write the list content of the URS.
5. List of abbreviations: All abbreviations shall be mentioned.
6. Signature page: Signatory page contains all signatures including Approval authority.
7. Scope: The scope of the URS is to define the specific Equipment/Instrument.

8.0 Procedural Document Requirements:

This part gives information about the Equipment / Instrument including the Purpose of the Equipment, Specification, Qualification, etc.
8.1 Name of the Equipment: Name of the equipment to be mentioned here, if possible, and Model No. to be defined here.
8.2 Purpose of the Equipment: Purpose of the Equipment shall be clearly defined here.
8.3 Number of Equipment Required: Require quantity of the Equipment/Instrument shall be defined here.
8.4 Qualification: A list of qualification documents shall be mentioned here.
8.5 Specification of Equipment: All major specifications of the Equipment/Instrument shall be mentioned here.

9.0 Operational Requirements:

9.1 Vendor Scope: The Vendors scope shall include the Supply, Installation, and Documentation including calibration certificates, User training, and Details of service/maintenance contracts available.
9.2 Operation: Basic operative characteristics including Data logging (21 CFR part 11), controlling system, capacity, safety, and protection, the capacity of basic function, etc.
9.3 Options and Ancillaries: The vendor should identify, where applicable, their standard equipment that fits this specification. The vendor shall (where possible) also provide costs including, A range of additional maintenance support and services., Any additional accessories to fulfill the requirements indicated in section 9.2.
9.4 Interfaces: A user-friendly control system is required, that can allow system operation with a minimal amount of training.
9.5 Data and Security: If required, data and security articles are to be clearly defined here.
9.6 Environment: Instruments/Equipment’s operating environment should be clearly defined here. The operating area must fit with the specific Instruments/Equipment in such a way that it can be operated without any difficulty.

10.0 Constraints

10.1 Milestones and Timelines: A projected timeline and milestone may be set here.
10.2 Compatibility and Support: The internal components of the system must be compatible with, and resistant to, the materials used during operation. Operating power to be mentioned here.
10.3 Maintenance Requirements: The manufacturer should supply details of any maintenance/breakdown packages available.
10.4 Procedural Constraints

11.0 Life Cycle

11.1 Development Procedures: Future development procedures are to be mentioned here.
11.2 Testing Requirements: See Section 11 for a detailed matrix of the validation testing requirements.
11.3 Delivery Requirements: On supply, the following documentation should be supplied: Operation and maintenance manual (including manufacturer’s recommendations for maintenance schedules). Calibration certificates. Parts list and spare requirements. System specifications.
11.4 Support: The vendor must supply details of all service and maintenance requirements of the equipment. The vendor must also supply details of any service and maintenance support that they can supply.

12.0 GMP Requirement: A list of cGMP requirements shall be mentioned here.
13.0 Utilities Available at The Site of Installation: Utilities shall be described here including the power supply for the machine/equipment.
14.0 Documentation Requirement: A list of documents shall be described here such as Operation, cleaning, and maintenance manuals for equipment as well as the operation, Installation instructions/ guideline, other drawings (such as Mechanical, electrical, instrumentation, etc.), IQ/OQ documents & operating manual., Instrument calibration / Qualification certificates traceable to the national reference standards, Guaranty/ warranty certificates for the equipment, Shipping checklist, and Hardware design specification.
15.0 Terms and Conditions to Be Included in The Quotation: All the terms and conditions shall be described here.
16.0 All the discussion shall be noted here and contact personnel details shall be mentioned at the end of the discussion details.
17.0 Annexures: Mention annexures if there are any.
18.0 Validation Requirements:
The following details the test requirements for documentation, testing, and the stage of the project at which they must be provided/performed. These requirements are a minimum tariff, and the vendor is required to include any documentation, not already requested here, which is considered necessary to support the successful validation of the system.

Which things to follow to write a Modern User Requirement Specification?

From the discussion till now we know what to add to our URS and what not to add. Ambiguity to be avoided as much as possible should be written clearly so that anyone who reads it can understand it. Ambiguity is the enemy of any project’s success and expressing yourself as accurately as possible is possible. Communication must be done in an unambiguous manner to achieve good results; Your project will be successful when you are able to convey your message to others.

To write a best User Requirement Specification you need to keep the following points in mind:

user requirement specification
user requirement specification

1. Focus on Single Requirement:

Check each requirement to be developed and how it is tested. Project success depends on each effective requirement which is really a demand to the project. Avoid unnecessary requirements which really not essential to the project.

2. Avoid Haziness

Your URS must be clearly written. Use a Simple Sentence. No confusing word. Just say what you want and what not.

A user requirement specification should be clearly written, using simple sentences, and without ambiguity. Examples of ambiguous words are:

[] Easy
[] Strong
[] Improve
[] Fast
[] Slow
[] Enough
[] User friendly

What exactly are you meaning “Fast”? this term is theoretical; you can’t actually express your requirement using the word “Fast”. It is hard to measure. Avoid any abbreviations, acronyms, and jargon words (words and phrases, that are not generally understood).

3. Go with the SMART Approach

[] S for Specific
[] M for Measurable
[] A for Achievable
[] R for Realistic
[] T for Time-bound

SMART [Specific, Measurable, Achievable, Realistic, Time-bound) targets offer a decent way to confirm your URS is well-defined and supportable.
Specific: All requirements mentioned in the URS must be specific, clear, and jargon-word-free. Don’t add any unnecessary requirements like easy and fast. Mention the actual specification.

Measurable: Reequipment must be measurable, don’t state anything which can’t confirm by testing or examination. Always avoid theoretical statements like rapid and swift. It can’t measure, you can’t prove that your requirements just met the specification until it is measurable.

Achievable: Never set a requirement which is can’t achieve with help of current technology. A feasibility study shall be done before setting any requirements. You can’t set any requirement which is technically impossible to achieve. It is wise to study well before adding features that you have no idea about. If even then you cannot be confirmed, then seek an expert for help. It is not right to add any feature without knowing it.

Realistic: It’s important to be realistic when determining the list of requirements. Sometimes technically achievable requirements may not be realistic due to regulatory requirements, time restrictions, Budget constraints, or other limitations.

Time-bound: A specific time frame shall be fixed to obtain your project. Even after finishing everything and if the specified time is not fixed, then any project may fail.

4. Organize

Organize your word choice and think carefully about it. Generally, the word “Shall” and “will” define the actual requirement which must be met. Word like “May” and “Could” use to define goals than are expected but not necessarily requirements. So, when you want the requirement must be met then use shall/will and use may/could for not mandatory cases.

5. Control Changes to the Requirements

Any type of changes may require during creating your list of requirements. Changes to the specification of the specific requirement shall be controlled. If any type of change directly affects the requirement, then the requirement shall be updated and a new version shall be created.

6. Requirements Must be Testable

Requirements shall be written in a such way that they can be tested and Specific requirements shall be traceable through the life cycle of the system/service/equipment/instruments.

7. Structural Products

Two types of products may be used as structural products & custom applications; for custom applications, the manufacturer must describe every process step to the user. For structural products, the process steps must be aligned with their predefined specification.

8. Vendor Audit

Most of the cases Regulated companies are most aware of their vendor for periodic assessment. All types of assessment/re-assessment perform in accordance with the Quality Management System (QMS).

9. Specifications

It is essential for the supplier to thoroughly document both the functionality and design of the system which is a prerequisite to ensure successful product development. Documentation must cover all aspects of the system, including software, hardware, and configuration, to meet all requirements to be established.

10. Training & Documentation

The supplier must agree to provide comprehensive system management documentation and provide instructions for both maintenance and use by the supplier and related issues must be agreed upon prior to system purchase.

11. Eliminate Requirement Redundancy

Avoid overcomplicating the system requirements and there is no need to bulk it up by duplicating it. Avoid duplication. Duplicating your documents may require more testing, documentation, and review time, making the project and time progressively longer Don’t include anything which is related to money or finance.

What is the difference between data and information

12. Embrace the Opportunity to Evaluate Vendors

Conducting audits on suppliers may include asking the following questions:
[] Security
[] Product support
[] End User training
[] Company Overview
[] Use of sub-contractors
[] Service delivery process
[] QMS application at the company
[] Development product life cycle
[] Key products development plans
[] Organization, roles, responsibilities, & training

13. Don’t be intimidated by your vendor comparisons

Utilize your URS to evaluate different vendors & note their advantages and disadvantages. If new information is found during the initial stage, feel free to revise your approved URS accordingly through the change control process. It is acceptable to make modifications or adjustments to the requirements to fit your needs until the final approval of the URS and it shall be revised the approved User Requirement Specification accordingly maintaining proper documentation.

14. What ought to be included in the URS?

The contents of a URS naturally include the following (but are not limited):
[] Functional requirements
[] Operational requirements
[] Technical requirements
[] Interface requirements
[] Data requirements
[] Security requirements
[] Regulatory requirements
[] Maintenance requirements
[] Availability requirements
[] Migration of any electronic data
[] Environmental requirements
[] Constraints to be observed
[] Life cycle requirements

15. Categorize Your Requirements

Categorize Your Requirements as-
[] Mandatory (High)
[] Beneficial (Medium)
[] Good to have it (Low)

16. Subjective Knowledge and Processing Step

To ensure that requirements, your professional knowledge is essential but not mandatory; if require you can seek help from an SME [Subject Matter Expert]. To identify key requirements of the system Process knowledge is required which are related to the manufacturing/servicing process. Look for the following key points-
[] Experience
[] Knowledge
[] Documentation

17. The requirements may be incomplete or not fully specified

Sometimes the requirements are not fully understood at the beginning of the project; Requirements evolve over time. URS shall be developed as per requirements when information is available. Don’t share incomplete User Requirement Specifications to the manufacturer to avoid any unwanted requirements.

Frequently Asked Questions

Are URS always required for validation?

At the initial stage of system/service/equipment/instruments, then URS is a valuable tool for ensuring the asking requirements. When an existing system is being validated then URS consider as a functional requirement. These two documents can’t be considered as single documents.

What is the benefit of good User Requirement Specification?

Requirements gathering is an important part of a good software/hardware/service/product development project. Good estimation, improved customer satisfaction, reduced cost, and project duration can all fail if good requirements are not selected and sufficient knowledge is not introduced in the selection If you are unclear about what you are delivering, no one can expect anything better from you.

There are Five main questions that shall be asked to develop any project:
[] Why we are doing it?
[] What do we need to do it?
[] What is the benefit?
[] How do we do it?
[] What is the timeframe?

If we fail to estimate project requirements or are unable to assume what is the requirement, can lead to a poor outcome of the project, and also lead to extra manpower, longer duration, and project costing.

Download Your

User Requirement Specification (URS) Template

user requirement specification of Equipment Read More »

Forced Degradation Study or Stress Testing Procedure

GMP, Pharma Operations, Product Development, R&D
What is Degradation?

Forced Degradation Study before proceeding on it ,first of all  ”Degradation’‘ to be discuss first, This is the act of lowering to some degree or someone to a less respected state or position. A CEO of a multinational company resigning from his office is a degradation. It’s also a downcast state.

The word degradation is very much related to the degrade, which comes from Latin word Degradare. The word “Degradare” comes from “de”-, meaning “down,” & gradus, meaning “Step.” So, it is very much clear that the degradation as a step down, or feeling as though you’re a step below.

Degradation products

It is the unwanted chemicals which can generate during manufacturing, transportation & storage of pharmaceutical drug products & can affect efficacy of pharmaceutical drug products. A small amounts of pharmaceutical degradation products can affect crucial safety because of the potential to cause adverse effects in end user.

Subsequently, it is crucial to focus on formulation, storage conditions, transportation, distribution channel and packaging to prevent the formation of degradation products which can negatively affect quality, safety and efficacy of the pharmaceutical drug products.

To find out the main cause of degradation of the pharmaceutical product is the crucial point, various software and data tracking system can help in this matter. This system can provide useful information during transportation and storage of pharmaceutical products, the route shall be determined to estimate the main cause.

Presence of a genotoxic degradation product shall tend to more assessment if it identified on due time. The chemical structure of the substance shall be determined to identify the toxic alerting structures associated toxic products, products [Compound] without active structure is marked as ordinary impurities.

A risk/benefit analysis shall be done to evaluate the levels of degradation products and most of the nest pharmaceutical call its mandatory. During the development of any type of product either critical or non-critical drug, critical variable of the drug products shall be follow-up which will control the degree of degradation of impurities.

Now a days the impurity profile has been considered as the key point of the product quality. It is the essential part of the quality parameter for the various competent regulatory authority. The toxicological evaluation and impurity profile become the key point of the degradation products to confirm its certain level of efficacy. Various types of test method have been identified to investigate the degradation products, all of them assay method consider the best to all and it’s highlighted to prove its effectivity.

The purity, safety and efficacy of the product depend on the stability of the product and it is the critical parameter of all the parameter. A product must be stable at a certain period of time to prove its efficacy, potency and safety.

A less stable or changes of stability can create serious toxicological effect by forming toxic degradation products and deliver less active or less effective or less potent drugs to the end user. Under these circumstances, this is very crucial to known the actual behavior of the drug products in various surrounding or environmental conditions.

Dissolution test are considering the most quality control tool for the commercial batch to batch product to monitor its consistency over a certain period of time. It also provides significant information during post approval changes of the certain product as changes made in formulation, manufacturing process and different scale up procedure.

To confirm the quality, safety and efficacy, the chemical stability is very important for a pharmaceutical product. This is very important to know the environmental influences of a certain developed product in specific condition such as Heat [Temperature], Humidity [Relative Humidity] & Light [Photostability] and this also regulatory [ICH & FDA] requirements.

Data acquire from stability study denote the shelf life and storage condition of the specific tested drugs, the container closure system [Protective packaging system] also require to satisfy the regulatory expectation.

Different types of method/instruments are available to determine the degradant compounds which are readily present during the forced degradation study period. HPLC-UV [HPLC with UV detector] and HPLC-PDA [ HPLC with Photodiode Array Detector] is the renowned method and extensively used in pharmaceutical company at the time of degradation study and validation and development of various type of method.

LC-MS [HPLC with Mass Detector], GC-MS [Gas Chromatography with Mass Detector] and NMR [Nuclear Magnetic Resonance] spectroscopy are significant methods to detect the degradants’ structure.

What is Forced Degradation Study?

Go to top

Exposure of specific sample at the unfavorable/stress condition of Heat [Temperature], Humidity [Relative Humidity], Light [Photostability], Oxidation and Acidic/Basic condition; observe/detect the changes of those sample or measure the rate of changes/degradation, mainly in Efficacy, Safety and Potency parameter of drug substance. Forced degradation study is the key point during the development of a specific drug. Determination of the type changes denote the modification or changes of the development process.

Now a days Force Degradation Study become the prerequisite to submit the NDA to regulatory authority and it became the quality parameter for the new product. During the regulatory submission, the Force Degradation Study data shall be submitted to get satisfactory result from FDA. Some of the best application of Force Degradation Study is depicted here-

[][]Developing and validating stability study indicating method as per regulatory guidelines [ICH Guidelines].
[][]To set up specification of degradants or impurities and to identify structure and toxicity.
[][]To set propose shelf life the specific product without performing Realtime stability data.
[][]To avoid incompatibility of drug products and excipients.
[][]Determination of the process related degradation products or impurities.
[][]Provide supporting data to lab investigations/OOS [out-of-specification] analysis.
[][]To provide regulatory compliance documents during submitting of ANDA/NDA to FDA.

It is a useful tool to predict the stability of any Active Pharmaceutical Ingredient (API) or formulation product. It helps to know about the impurities developed during the storage of drug products in various environmental conditions.

Forced degradation is performed by applying artificial methods and a drug is degraded forcefully. It is also known as stress testing. To assume the stability condition of API [Active Pharmaceutical Ingredient] and formulated product Forced degradation study plays an important role. It also helps to identify the impurities generated during storage of drug products in different environment stage.

process flow diagram of forced degradation study

Why Forced degradation study carried out?

Go to top

Its play a vital role to develop and validating of stability study signifying method. At the time of developing phase of a new drug product, force degradation study performs to determine the degradation pathways of drug products & drug substances. It is very important to determine impurities of the degradant product, Forced degradation study quantify the number of impurities present on the specific drug substance. It helps to determine the molecular chemistry. Forced degradation study assure the more stable product. Help to develop the degradation profile. Stability related problem can be solved through Forced degradation study. Forced degradation study also highlight the following point of view-

[][]Evaluation of drug products & drug substance in solution.
[][]Determination of structural transformation of drug product & drug substance.
[][]Determination of the concentration of the degradation products.
[][]To identify the non-relevant impurities in the existence of the desired product.
[][]Separation of the product related degradants derived from intact placebo & excipients.
[][]Describe the degradation pathways of the specific drug substance.
[][]To categorize the degradation products which generate spontaneously during storage & use of products.
[][]To generate product related variants & develop analytical methods Forced degradation studies are performed during accelerated and long-term studies.

During the Forced degradation study, the degradation products may or may not be generate but it will show the degradation pathway of the product. This process will help them develop the analytical method of the relevant product and stability indicating analytical procedure. If any degradation occurs during performing of Forced degradation study, the degradation product shall be evaluated if it significant or minute, to robust the developed formulation.

How Forced degradation Study Conducted?

Go to top

This study of the drug products or substances is generally conducted on the solid and solution stages at the high temperature exceeding accelerated stability condition which is above 40°C. Various condition are consider here as oxidation, hydrolysis, photolysis, polymerization and thermolysis. In Solution hydrolysis condition are investigated in broader pH range and in solid stage high relative humidity taken under consideration.

Control exposure of molecular oxygen or addition of oxidizing agents such as peroxides is use during investigating Oxidation in solution.
Applying heat in solid state effects of thermolysis are usually assessed. Light with wavelengths in the 300-800 nm range are use in Photolysis investigation in solution or the solid state. In an oxygen atmosphere photooxidation can be investigated with light under oxygen atmosphere. Measuring the rate of degradation, Drug substance polymerization can be investigated at the various drug substance concentrations in solution.

List of Analytical Tools to perform Separation & Identification of degradant

A. Sophisticated Techniques

[][]Capillary Electrophoresis- Mass Spectrometry [CE-MS].
[][]Gas chromatography–mass spectrometry [GC-MS].
[][]Liquid chromatography–mass spectrometry [LC-MS].
[][]Liquid Chromatography- Nuclear magnetic Resonance [LC-NMR].
[][]Liquid chromatography-Fourier Transfer Infrared [LC-FTIR].

B. Conservative Techniques:

[][]Thin layer chromatography [TLC].
[][]Solid phase extraction [SPE].
[][]Accelerated solvent extraction [ASE].
[][]Low-pressure LC [LPLC].
[][]Supercritical fluid extraction [SFE].
[][]Mass Spectrometry [MS].
[][]Nuclear Magnetic Resonance [NMR].
[][]High Performance Liquid Chromatography [HPLC].

Extend of degradation

For validation of a chromatographic purity assay, degradation level of 10-15% is adequate to perform the activities. Forced degradation studies are not considered part of the formal stability program though forced degradation studies are a regulatory requirement & scientific necessity during development of a specific product. For conducting studies at the various phases of development the guidance gives various recommendations.

Selection of Forced Degradation Condition

Go to top

In common industry practice, forced degradation is generally performed in different stress conditions, i.e., thermal, acid, alkali, peroxide, and UV, along with a control sample which also comply with ICH guidelines. There no specific range or rate of degradation in current industry practice but 5 to 30 percent degradation shall be taken into consideration and this can be achievable on any one of the above stress conditions.

Through stress testing, the aim of the degradation to be achieved to implement the control room temperature for the stability conditions. The conditions or concentrations of reagent shall be optimized if higher or lower degradations are observed.

During the degradation study Mass balance shall be demonstrated & it shall be around 100%, taking into attention margins of analytical errors. During mass balance evaluations, all the degradants /impurities must be calculated.

Any batch which is not be the part of regulatory submission can be used for the forced degradation study. For multiple strengths of the same placebos and different amounts, the highest ratio of placebo vs. API [Active pharmaceutical ingredient] shall be use.

Forced degradation of all the strengths shall demonstrate if placebos are different. Placebo & API [Active Pharmaceutical Ingredient] must be demonstrated to identify actual degradation pathways during the drug product force degradation study. All the placebos shall be considered for force degradation study if placebos are different for different strengths of drug product.

Various degradation conditions are depicted on the following table which is accepted by the regulatory authority [FDA] at the time of DMF/ANDA/NDA submission-

Degradation TypeReagent ConcentrationConditions to be appliedTimeRemarks
Acid5N HCL80deg.C1 HourConcentration, condition and time can change to optimize degradation
Alkali5N NaOH80deg.C1 HourDo
Peroxide10% H2O280deg.C1 HourDo
Heat/Thermal80deg.C80deg.C1 HourDo
UVExpose under UV light at 254nm wavelengthAmbient Temperature24 HoursTime can change to optimize degradation
ControlN/AN/AN/AN/A

Force Degradation shall be performed in solid or solution form though it is recommended that Force Degradation shall be executed in solution form using the mobile phase/diluent to get a homogeneous effect with better result. Force Degradation studies shall be started with harsh conditions (i.e., high temperature with high concentration of reagent) to shorten time of study.

Milder conditions shall be applied by reducing concentration of reagent with lowering temperature, etc. when degradation found 30% or above. Based on the initial degradation outcome, Degradation conditions can be optimized to achieve a target range.

To extend shelf life of chromatographic column, pH shall be adjusted about 7.0 for acid & alkali degradation. Different reagents & conditions shall be applied, e.g., Zn, H2SO4, etc. If degradation did not find in any of above conditions. A few numbers of molecule designated rock stable molecules as these molecules didn’t degrade any of the above stress condition. During a stability study This kind of molecule will not engender any additional impurities/degradant peaks.

If drug substance or product shows stability for two years at 30 ±2⁰C & 65 ±5% RH & Six months at 40 ±2⁰C & 75 ±5%RH, then the drug substance or product declared stable.
Concentration of the drug that is being tested for the degradation is a great point. For the degradation study 1 mg/ml of drug concentration is recommended though some degradation studies are done at concentration of drug in the final product. Main cause for this type of study is that precise amount of the degradation can be found in final product & their impact can be scrutinized.

types of forced degradation studies

Factors Affecting Forced Degradation Studies

Go to top
Hydrolytic Degradation:

The reaction of chemical with water at different pH values occur in Hydrolysis degradation. In this degradation drug react with water in acidic & basic conditions. According to the stability of the drug substance concentration of the acid or base is selected where pH is 0.1 to 1.0 M HCl [Hydrochloric Acid] or H2SO4[Sulfuric Acid].

HCl & H2SO4 is used to maintain acidic conditions and 0.1 to 1.0M NaOH [Sodium hydroxide] or KOH [Potassium Hydroxide] used to generate basic conditions. Some materials are not readily dissolve/soluble in water freely; in that case other solvent are use to dissolve the water insoluble materials. Solvent shall be selected carefully so that it can’t degrade the selected drug substance.

Descriptive termPart of the solvent require per part of solute
Very solubleLess than 1
Free SolubleFrom 1 to 10
SolubleFrom 10 to 30
Sparingly solubleFrom 30 to 100
Slightly solubleFrom 100 to 1000
Very Slightly solubleFrom 1000 to 10,000
Practically insoluble10,000 and over

Reference: British Pharmacopoeia [BP]

Generally Chemical degradation shall be conduct in room temperature but if no sign of Chemical degradation occur at room temperature then room temperature shall be increase up to 50-60 ⁰C. A seven days timeframe shall be selected to perform the study. To prevent further degradation, Chemical degradation should be terminated using acid, base or buffer solution. Chemical analysis shall be done as soon as possible after completion of the test.

Oxidation Degradation:

in the forced degradation study, H2O2 (Hydrogen peroxide) is a widely used oxidizing agent. Hydrogen peroxide at 0.1% to3.0% solution is used at room temperature for 7 days is the suitable range to perform the activities. When more then20% degradation occur for a certain product, it can be considered abnormal cases.

Photolytic Degradation:

To determine the effect of light on the product during storage in the market Photostability testing of any drug take into consideration. light conditions shall be described during photostability. light source shall be cool white fluorescent lamp & wavelength of light shall be 200-800 nm (UV+ visible) which is also comply ICH guideline. The and the light intensity shall be not less than 200 watt-hours per sq meter and exposure time shall be not less than 1.2 million lux hours. To monitor the condition, a calibrated lux meter shall be use in place.

Result of forced degradation studies

[][]Forced degradation studies help to determine_
[][]Likely/Probable degradants
[][]Degradation paths
[][]Inherent stability of the drug molecule
[][]Validated stability indicating analytical method

forced degradation studies condition

When forced degradation studies to be performed?

Go to top

This is the best practice to perform forced degradation studies at the time of development of new drug substance and new drug product. FDA prefer to perform it at phase III of the regulatory submission which is the best time to do the same. To establish the regular stability study, forced degradation studies can be prerequisite. This study can be done in different pH solution in the presence of light & Oxygen with high temperature & Humidity Level.

Generally, degradation study performs on single batch. There are two types of timeframes are use to perform stability study which Long Term [12 Months] & Short Term [6 Months]. 6 Months are performed at accelerated condition. Moreover, Intermediate Stability Study performed in a condition lesser than accelerated condition.

Force degradation studies are performed at pre-clinical phase or phase I of clinical trial so that sufficient time provides to identifying structure elucidation, degradation products. If forced degradation studies are performed properly, manufacturing process of the new product can be developed properly and stability-indicating analytical procedures can be select more effectively.

What is the regulatory obligation regarding Force Degradation Studies?

Following ICH [International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use] Guidelines has been depicted regarding forced degradation studies but it covers only marketing applications for new products but not for during clinical development.

[][]ICH Q1A: Stability Testing of New Drug Substances and Products.
[][]ICH Q1B: Photo stability Testing of New Drug Substances and Products.
[][]ICH Q2B: Validation of Analytical Procedures: Methodology.

Go to top

What actually says this guideline?

[][]ICH Q1A (Stress testing): Stability Testing of New Drug Substances and Products.

It implies for the performing of forced degradation studies for drug substances and drug products. The recommended condition is that the result shall be observe temperature above accelerated condition [Temperature>500C) and Humidity [75% relative humidity] including oxidation and photolysis. pH range may be wide for the testing of solution or suspension.

[][]ICH Q1B: Photo stability Testing of New Drug Substances and Products.

It implies the photo stability of drug substances and drug products. Section II and Section III describe the forced degradation conditions condition for drug substance and drug product. Exposure levels are not defined in Forced degradation studies. Photo stability testing can be performed both in Solid or in solution/suspension. Stability indicating method is developed based on this sample result. Some non-experiential degradation products may be formed during stability studies which may not be taken under consideration.

[][]ICH Q2B: Validation of Analytical Procedures: Methodology.

Provide guideline regarding analytical meth validation. Gives guidance to validate the analytical methodology. To demonstrate specificity, in section B1.2.2 (impurities not available) there is a recommendation to utilize samples from the forced degradation studies.

Verdict

to develop degradation pathways, Forced degradation studies are the prominent way & Forced degradation studies are the prominent way to develop degradation pathways and to detect degradation products of API [Active pharmaceutical Ingredients], further it simplifies elucidation of degradants structure. Forced degradation studies also simplify the chemical & physical stability analysis of drug substances & drug products. To develop manufacturing conditions, storage conditions & determine expiry date of a new drug formulation Forced degradation studies is considered as key studies.

Forced Degradation Study or Stress Testing Procedure Read More »

Calibration of Friability Tester With Operation & Cleaning

Product Development, SOPs

Calibration of Friability Tester, Purpose :

Calibration of Friability Tester, The purpose of this SOP (Standard Operating Procedure) is to describe the operation, calibration and cleaning of friability tester.

Calibration of Friability Tester, Scope :

This procedure is applicable for friability tester (Model: Electrolab, EF-1W ) used in Product Development Laboratory of XX Pharmaceuticals Limited.

Definitions / Abbreviation:

[][]PD: Product Development

Responsibilities:

[][]The roles and responsibility is as follows:

Executive, PD

[][]To ensure that this procedure is followed.
[][]To maintain the records properly as per SOP.

Sr.Executive, PD

[][]To ensure that this procedure is kept up to date.
[][]To arrange training on the SOP to all concerned personnel.
[][]To ensure implementation of the SOP after training.

Manager, Quality Assurance

[][]Approval of the SOP.

Procedure:

Precaution(s):

[][]Make sure the knob is properly fitted on the shaft to assure the drum is held in position.
[][]Do not hold the drum while they are rotating.
[][]Do not use abrasive, aggressive material or solvents to clean the drum and the tray. If required use mild detergent.
[][]Do not use wet drum. Make sure the drum is dry when in use.
[][]Replace the fuse with the correct rating whenever required.

Operating Procedure:

[][]Turn on the power switch of Friabilator.
[][]After power on, the drum would initialise itself to the loading position and the instrument will initialise the weighing scale and the following display will be shown:

ELECTROLAB
EF 1 W FRIABILATOR

[][]The instrument is then ready for the setting of test parameter and to run the test and following display will be shown on the screen:

ELECTROLAB EF 1 W
SET = menu, START = run
[][]Press SET key to set the test parameter as the following way.
[][]The first parameter for the test is MODE selection. Select the Time or Count mode using the MODE key on the front panel. The desired value for the selected mode can be set using or & DIGIT SCROLL keys. Set Count 100 and Time 4 minutes. Press the ENTER key to go to the next parameter.
[][]The next parameter is RPM setting. The desired value from 20 RPM to 50 RPM can be set using the key or and DIGIT SCROLL keys. Set 25 RPM. Press the ENTER key to go the next parameter.
[][]The next parameter is for drum selection. Using the or keys the Friability or the Abrasion drum can be selected. Select the Friability drum. Press the ENTER key to go the next parameter.
[][]The next parameter is for selecting the Scale Connection Option. This option can be enabled (Y) or disabled (N) using or key. If no printer is connected select disabled (N) mode. Press the ENTER key to go to the next parameter.
[][]The next menu is for Clock setting. The default setting for this menu would be the current time. The Time can be adjusted using or key & DIGIT SCROLL key. Press the ENTER key to go to the next parameter.
[][]The next menu is for Date setting. The default setting for this menu would be the current date. The Date can be adjusted using or key & DIGIT SCROLL key. Press the ENTER key to go to the next parameter.
[][]The next menu is for the selection of the option to the last test result. Select No (N) by using or key. Press the ENTER key to go to the next parameter.
[][]The next menu is for the Sound option. Select Yes (Y) using or key.
[][]Press the SET key to exit from the SET menu.
[][]After weighing the test samples as per specific Standard Test Procedure, slide them gently into the drum through the side slit and press START key, input the weight of tablets, press ENTER to run the test.
[][]After the test is over, the drum rotates in the reverse direction, discharging all the test samples into the tray located below the drum.

[][]The drum would now initialize itself to the loading position. Carefully slide the tray out and remove the loose dust from the test samples, i.e. deduct the test samples. After deducting weight the sample, input the weight of deducted tablets, press ENTER, % friability will be displayed on the screen.
[][]Press SET key for performing a new test.

Calibration procedure:

[][]Ensure that the instrument is clean before use, including surrounding area.
[][]Check and ensure due date of calibration.
[][]Switch ON the power supply.
[][]Set the time 4.0 minutes by selecting TIMER key and start the machine and calibrated stopwatch simultaneously.
[][]Note the actual time shown by a calibrated stopwatch.
[][]Take three such readings and calculate the mean time.
[][]Set 100 counts (rotation) by selecting COUNT key (some tablets may be placed into the drum for ease of counting) and start the instrument.
[][]Record the number of rotation.
[][]Take three such readings and calculate the mean of rotation per minute.
[][]Record the observations in the Calibration report (Annexure –II).
[][]After completion of calibration switch ‘OFF’ the main supply.
[][]After completion of the calibration activity, affix the duly filled and signed calibration status label on the instrument.
[][]Calibration Frequency: Every three-month ±07 days of due date and after maintenance job.

Cleaning procedure:

Remove the knob by pressing gray colored button and open the drum.
Clean the drum with suitable dry duster or cloth.
If required use water and dry in air.
Place the drum properly and replace the knob.

Annexure:

Annexure-I: Log Book Of Friability Tester.
Annexure-II: Calibration Report Of Friability Tester

Calibration of Friability Tester With Operation & Cleaning Read More »

Calibration of Moisture Analyzer with Operation, and Cleaning

Product Development, SOPs

Calibration of Moisture Analyzer, Purpose :

Calibration of Moisture Analyzer, The purpose of this SOP (Standard Operating Procedure) is to describe the operation, calibration and cleaning of Moisture Analyzer.

Calibration of Moisture Analyzer, Scope :

This procedure is applicable for Moisture Analyzer (Model: METTLER TOLEDO, MJ33) used in the Product Development of XX Pharmaceuticals Limited.

Definitions / Abbreviation:

N/A

Responsibilities:

The roles and responsibility is as follows:

Operator / Supervisor, Product Development

[][]To ensure that this procedure is followed.
[][]To maintain the records properly as per SOP.

Executive / Senior Executive, Product Development

[][]To ensure that this procedure is kept up to date.
[][]To arrange training on the SOP to all concerned personnel.
[][]To ensure implementation of the SOP after training.

Manager, Quality Assurance

[][]Approval of the SOP.

Procedure:

Precaution(s):

[][]Keep sufficient free space around the instrument to avoid heat accumulation and over- heating.
[][]Never cover, plugged, taped over or tampered with any way the vent over the sample.
[][]Do not place any combustible material on, under or next to the instrument during operation.
[][]Be very careful to touch sample, sampling pan, sampling pan holder and heating module just after the operation.

Operating Procedure:

[][]Switch on the main power. Instrument shows “OFF” in display.
[][]Press the “ON/OFF” key to switch the instrument on.
[][]The instrument performs a self-test. Wait until the display shown 0.000 g.

Temperature setting

[][]Press the temperature setting key
[][]In display temperature reading shall be blinking.
[][]Select the desire temperature by pressing scroll button
[][]Press enter key to conform the temperature.
[][]Open the heating module (Top lid) for tare and close the heating module.
[][]Again open the heating module and put the sample on sample pan as mentioned in BMR or test procedure.
[][]Close the heating module and wait for buzzed.
[][]Record the moisture content from the display.
[][]Press the “ON/OFF” key to switch off the instrument.
[][]Wait sufficient time to cool down the instrument in ambient temperature before cleaning.

Calibration Procedure:

Balance calibration

[][]Ensure that the sample pan is in position.
[][]Switch ON the power supply. The display shows “OFF”.
[][]Press the “ON/OFF” key to start the instrument.
[][]The instrument performs a self-test. Wait until the display shown 0.000 g.
[][]Select standard weight of 1g, 5g and 10 g for calibration.
[][]Open the heating chamber and place 1g standard weight on the balance pan at center position.
[][]Repeat previous step no.for 5g. & 10 g.
[][]Record the observations in the calibration report (Annexure–II)

Temperature calibration

[][]Press menu key twice. Display shows “Temperature adj.”
[][]Select “Yes” using scroll keys.
[][]Press “enter” key to start process. Display shows “Remove pan holder”
[][]Open the heating chamber and Remove the sample pan holder from the sample chamber.
[][]Display shows “Insert adjustment kit”. Place the temperature adjustment kit (standard thermometer) in the sample chamber.
[][]Close the heating module to start heating to temperature 100deg. C. The display shows the temperature.
[][]Wait 15 minutes, instrument gives audio signal sound.
[][]Note down the actual temperature on standard thermometer in calibration report (Annexure-II)
[][]Press enter key. The heating module automatically starts calibration at 160deg. C.
[][]Again wait for 15 minutes, instrument gives audio signal sound.

Acceptance Criteria

[][]For balance calibration ± 0.1 % & for temperature calibration ± 30 C.
[][]After completion of calibration switch “OFF” the main supply.
[][]After completion of the calibration activity, affix the duly filled and signed calibration status label on the instrument.
[][]Calibration Frequency
[][]Every six month ± 10 days of due date and after maintenance job.

Cleaning Procedure:

[][]Disconnect the instrument from the power supply before cleaning.
[][]Open the heating module and remove the sampling pan by sampling pan holder.
[][]Clean the sampling pan with soft brush.
[][]Clean exteriors of the instrument by clean dry cloth.
[][]Set the parts of weighing pan carefully and close the heating module

Annexure:

Annexure-I: Log Book Of Moisture Analyzer.
Annexure-II: Calibration Report of Moisture Analyzer.

Calibration of Moisture Analyzer with Operation, and Cleaning Read More »