In a clinical investigation, a product defect is any deficiency of an investigational product regarding its identity, quality, shelf-life, reliability, safety, or performance. This includes malfunctions, use errors, and insufficient manufacturer information. In safety reporting, a defect is reportable if, without appropriate measures, intervention, or more favorable circumstances, it could have led to a serious adverse event.
What Constitutes a Product Defect
The term refers to the investigational product and its information, not just a technical fault. Incorrect labeling, unclear instructions for use, a faulty software function, or insufficient shelf-life can therefore constitute a product defect, just like mechanical failure. The assessment must relate to the investigational product actually used and its intended use.
A use error can be relevant as a product defect if the product design or the information provided contributed to it. This does not preclude the need to simultaneously investigate causes in the investigation procedure or handling. For safety assessment, it must remain traceable what role the product, user information, and investigation circumstances played in each case.
Reporting and Follow-up in the Investigation
The sponsor reports reportable product defects in all Member States where the clinical investigation is conducted. The criterion is the hypothetical hazard potential: if the defect could have caused a serious adverse event without a corrective measure or favorable circumstances, it must be reported. New findings regarding an already reported defect also fall within the safety process.
The Clinical Investigation Plan should therefore list the terms for adverse events, undesirable product effects, and product defects, and describe their capture, follow-up, and reporting pathways. For faulty, expired, or returned investigational products, seamless assignment to delivery, storage, application, and return is required. This information helps to investigate the cause and prevent recurrence in study operations.
The initial report does not necessarily have to contain the definitive root cause of the defect. It should capture the suspicion and potential risk in such a way that the sponsor can assess the need for a safety measure. Technical investigation, evaluation of retention samples, or analysis of electronic protocols can only clarify in the follow-up whether it is a manufacturing defect, a storage deviation, or unclear operating information.
Differentiation between an isolated defect and a pattern of similar observations is also important. If defects recur within the same batch, software version, or delivery route, this may indicate a systematic correlation. Product responsibility in the investigation creates the data basis to identify such a correlation early.
Timely securing of the affected product is practically significant. Without the associated labeling, packaging, and use information, it is often impossible to determine later whether the defect was due to the product, a deviation in storage, or the study procedure.
Distinction from an Adverse Event
A product defect is not an adverse event. It describes a deficiency of the product or product-related information, whereas an adverse event concerns an occurrence or condition in the subject. Both can occur together but must be documented separately in the safety assessment and evaluated for causality.
A serious adverse event can arise independently of a product defect, for example, due to the investigation procedure or an illness. Conversely, a defect can be reportable without a subject being harmed, because an intervention prevented the harm. It is precisely this proactive reporting logic that distinguishes a product defect from a mere description of harm.
Relevance for clinical trials
In investigation sites, a suspected product defect must be promptly communicated to the sponsor so that the fact-finding can begin before the loss of device, packaging, or application data. Monitoring checks whether serial number, batch, storage conditions, instructions for use, and event report match. For software-based products, version status and configuration can be crucial to distinguish an isolated operating error from a systematic product problem.
Full-service CROs like Mediconomics establish appropriate reporting channels between investigator, monitoring, safety management, and manufacturer for this term and verify the completeness of case information. They support the creation of safety lists, the traceability of the investigational product, and the coordination of follow-up reports with the competent authorities if a defect could have caused a serious event.
Frequently Asked Questions (FAQ)
Is a missing label on an investigational product a product defect?
A deficiency in identity or manufacturer information can fall under the definition. Whether this leads to a report also depends on the potential serious event.
Must a product defect be reported even without actual harm occurring?
Yes, if it could have led to a serious adverse event without appropriate measures, intervention, or more favorable circumstances.
Who documents the handling of a faulty investigational product?
The investigation plan defines the procedures; the investigation site maintains the product records, and the sponsor organizes assessment, follow-up, and, if applicable, reporting.
Regulatory References
- Regulation (EU) 2017/745, Article 2 Number 59 – defines the product defect of an investigational product.
- Regulation (EU) 2017/745, Article 80 Paragraph 2 – regulates reportable defects in clinical investigations.
- MDCG 2020-10/1 Rev.1 – explains safety reporting in clinical investigations according to MDR.
- MDCG 2024-3 – specifies content elements of the Clinical Investigation Plan for product defects.