CAPA (Corrective and Preventive Action)
CAPA (Corrective and Preventive Action) is a structured quality-system process for addressing the causes of actual or potential problems and checking whether the actions work.

On this page · 12 sections
- 1What CAPA is—and what it is not
- 2Where CAPA fits in pharmaceutical regulatory frameworks
- 3Medical devices: CAPA in the QMSR era
- 4Which signals justify opening a CAPA
- 5The CAPA lifecycle: accountable decisions at each gate
- 6Root cause: evidence before conclusions
- 7What a traceable CAPA record contains
- 8Effectiveness: define success before collecting results
- 9Worked cases: recurrence reduction and preventive control
- 10Integrations and recovery without losing the evidence chain
- 11Trending and review beyond closure counts
- 12CAPA failure modes and an implementation checklist
How does CAPA apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What CAPA is—and what it is not
CAPA is a structured quality-management process for investigating problems or potential problems, addressing their causes, and checking whether the actions work.
Corrective and preventive action and CAPA system are common names for this process. Operationally, CAPA connects a quality signal to an evidence-based decision and a sustained control improvement; it is not simply a task list or a synonym for every deviation.
In pharmaceutical guidance, ICH Q10, section 5, Corrective Action distinguishes corrective action to prevent recurrence from preventive action to prevent occurrence. The comparison below uses practical manufacturing distinctions, not universal legal definitions.
Assume a packaging line has applied an obsolete label version and investigation identifies uncontrolled access to superseded label files.
| Term | Purpose | Example | Boundary |
|---|---|---|---|
| Containment | Limit immediate exposure | Hold potentially affected packs. | Does not remove the cause. |
| Correction | Address the detected problem | Relabel affected packs under an approved instruction. | Fixes packs, not file access. |
| Corrective action | Prevent recurrence by addressing the cause | Restrict label selection to approved current files. | More than replacing incorrect labels. |
| Preventive action | Address a potential problem before occurrence | Remove the same access weakness on an unaffected line. | Based on a credible potential failure. |
| Investigation | Establish what happened and why | Trace file selection, label use and affected batches. | Produces findings, not implementation. |
| Change control | Govern implementation of changes | Assess, approve and test revised file-access controls. | Does not replace the causal investigation. |
| 8D | Structure team problem-solving | Use eight disciplines to work through the label problem. | A method, not the whole CAPA system. |
Complaints, deviations and adverse trends are potential inputs; they are not themselves CAPAs. Root cause analysis supports the causal conclusion, while a CAPA effectiveness check tests the resulting improvement. The CAPA system connects these activities through accountable decisions and linked records. Completing a correction alone therefore does not demonstrate that the cause has been controlled.
02Where CAPA fits in pharmaceutical regulatory frameworks
Map CAPA references by product, jurisdiction and authority before translating them into site procedures. A useful applicability map separates U.S. regulatory provisions from pharmaceutical quality-system guidance, then identifies the operational connection without treating every reference as an identical CAPA mandate.
| Product and jurisdiction | Instrument and status | CAPA connection | Scope boundary |
|---|---|---|---|
| Drug production; United States | 21 CFR 211.192 — U.S. regulation | Requires investigation of unexplained discrepancies and specification failures, extended to associated batches, with written conclusions and followup. | Check the current text of 21 CFR 211.192 for scope. |
| Drug manufacturing procedures; United States | 21 CFR 211.100 — U.S. regulation | Written procedures and deviations are the relevant reference points when mapping procedural controls. | Check the current text of 21 CFR 211.100 for scope. |
| Pharmaceutical quality systems; international guidance | ICH Q10 — guidance | ICH Q10 3.2.2 recommends a pharmaceutical company system for implementing corrective and preventive actions. | Use as a quality-system reference, while assessing applicable jurisdictional obligations separately. |
| Medicinal-product manufacturing; European Union | EU GMP Part I, Chapter 1 — GMP guidance | Chapter 1, paragraph (xiv) connects investigations with identifying and taking appropriate corrective and/or preventive actions. | Assess applicability within the relevant EU GMP context; do not transfer the reference indiscriminately to other sectors. |
For US drug manufacturers, 21 CFR 211.192 requires that any unexplained discrepancy or batch failure to meet specifications “shall be thoroughly investigated, whether or not the batch has already been distributed.” The investigation must extend to other batches and products that may be associated with the failure, and its written record “shall include the conclusions and followup.” Those are binding investigation duties; whether the followup is managed as a standalone CAPA record is a site procedure decision.
These references serve different purposes in an applicability map. Keep the legal basis for a procedure separate from the guidance used to structure the quality system. For broader context, see the ICH Q10 pharmaceutical quality-system framework and the overview of current good manufacturing practice. This section is a reference map, not a general compliance guide.
As a practical documentation method, record why each reference is relevant to the site's products and activities, who owns the applicability decision, and which controlled procedures implement that decision. Keep local form fields, workflow numbering and completion targets identifiable as site controls; do not attribute a standard CAPA form, numbered workflow or fixed completion deadline to the references above.
Pharmaceutical and device references are not a common legal rulebook for supplements, food or chemicals. Readers in those sectors need a product- and jurisdiction-specific applicability assessment rather than a borrowed pharmaceutical CAPA checklist. Device frameworks are addressed in the next section.
03Medical devices: CAPA in the QMSR era
FDA’s QMSR overview identifies February 2, 2026 as the regulation’s effective date and explains that the QMSR incorporates ISO 13485:2016 by reference. The overview provides official explanatory guidance; it is not the regulation itself. For detailed scope, consult current 21 CFR 820.10 and ISO 13485:2016. Our QMSR and ISO 13485 comparison provides context for the device quality-system framework.
For implementation, review device CAPA procedure references and applicability mappings rather than carrying historical citations forward unchanged. Treat this as a controlled-document review, not merely a terminology update:
- Identify legacy references in procedures, forms, training materials and audit checklists.
- Check each reference against the current framework and document the basis for retaining, replacing or removing it.
- Have authorised quality and regulatory personnel review the revised mapping and determine whether procedural changes or training are appropriate.
These are implementation practices, not additional regulatory requirements. The useful output is a clear explanation of which framework applies to the device operation and how its CAPA procedure relates to that framework.
04Which signals justify opening a CAPA
For pharmaceutical quality systems, ICH Q10 section 3.2.2 identifies CAPA inputs from investigations of complaints, product rejections, non-conformances, recalls, deviations, audits, regulatory inspections and findings, and process-performance and product-quality trends. This guidance also recommends scaling investigation effort, formality and documentation to risk.
In practice, an intake signal is not yet an approved CAPA case. Deviation handling can establish the event facts before escalation; for supplements, product complaint investigation provides another intake route. Neither record type should automatically generate a separate CAPA for every event.
Practical escalation considerations include:
- Severity: could the failure materially affect safety or product quality?
- Recurrence: has the issue returned despite previous local action?
- Shared mechanism: do different events point to the same process or system weakness?
- Scope uncertainty: could other batches, products, equipment or sites be affected?
- Control weakness: are existing controls absent, unreliable or unable to detect the failure?
Organisations should define their own applicable decision criteria rather than adopt a universal event-count threshold. Record the reason for opening a new case, linking the signal to an existing case, or handling it locally, with the responsible reviewer identified. Local handling should remain traceable so later recurrence can change the assessment. Keep urgent containment independent of the administrative opening decision: protective action should not wait for a CAPA number.
05The CAPA lifecycle: accountable decisions at each gate
This illustrative manufacturing workflow separates four responsibilities: the case owner coordinates the record and handoffs; the investigator evaluates evidence and proposes causal conclusions; action owners propose and execute assigned work; authorised reviewers approve decisions. Assign these responsibilities explicitly rather than assuming a universal organisational title.
- Capture. The case owner records the signal, affected products or processes, source records and immediate controls. This gives triage a defined problem and traceable starting evidence.
- Triage. The case owner proposes scope, priority and investigation resources from the initial risk assessment. An authorised reviewer approves the route forward; the recorded rationale and unresolved questions pass to the investigator.
- Investigate. The investigator tests explanations against records and observations, then proposes supported causal factors or identified risks. Findings, limitations and the assessed extent of the problem support action planning.
- Approve actions. Action owners propose measures; the case owner assembles the plan. Link every action to a supported causal factor or identified risk, owner, planned completion date, implementation evidence and effectiveness approach. An authorised reviewer approves the plan, including acceptance criteria before outcome data are reviewed.
- Implement. Action owners execute approved work and attach completion evidence. Hand changes requiring controlled implementation into change control, retaining linked approvals and execution records. The case owner checks evidence completeness before assessment.
- Assess effectiveness. Evaluate outcomes against the agreed criteria and record the conclusion, uncertainty and remaining risk. Implementation complete is not effectiveness demonstrated; detailed assessment design belongs in the CAPA effectiveness check.
- Decide closure. The case owner submits the evidence chain and recommendation. An authorised person approves closure or returns the case for further work, recording the rationale and any continuing monitoring.
For extensions or scope changes, preserve the original commitment, reason, interim controls, revised plan and approval history. Authorised people approve actions and closure; product disposition follows its own applicable disposition decision process. A CAPA status is not, by itself, a release decision.
Capture → Triage → Investigate → Approve actions → Implement → Assess effectiveness → Decide closure
- Capture signalLink the event, affected scope and immediate containment.
- Triage RiskAssign ownership and justify escalation or local handling.
- Investigate CausesTest causal hypotheses against records and contrary evidence.
- Approve actionsMatch controls to causes and define success criteria.
- Implement changesRecord approved changes, training and implementation evidence.
- Assess effectivenessCompare results with predefined criteria and review residual risk.
- Decide closureAuthorised reviewers close, extend monitoring or reopen investigation.
06Root cause: evidence before conclusions
A useful CAPA investigation separates what happened from why it happened. As practical investigation discipline, distinguish four levels:
- Observed symptom: the measured failure, such as intermittent underfilled containers.
- Causal hypothesis: a testable explanation, such as unstable feed pressure.
- Supported causal mechanism: evidence shows how pressure loss reduces delivered volume under the operating conditions.
- Contributing conditions: factors that enable or worsen the mechanism, such as a maintenance interval that allows seal deterioration.
In this hypothetical example, more underfills on one shift establish an association, not an explanation. Pressure measurements, seal inspection and controlled testing could support a mechanism that guides equipment or maintenance action; the shift label alone cannot.
For pharmaceutical GMP, EU GMP Chapter 1, paragraph (xiv) guides investigators to consider identifying and addressing the most likely causes when the true root cause cannot be determined. Its human-error caution is equally important: attribution should be justified without overlooking process, procedural or system-based problems.
Record supporting evidence, contrary evidence and unresolved uncertainty. Explain the basis for extending—or not extending—the investigation to similar equipment, materials or processes: shared design, supplier or operating conditions may matter more than location. Keep provisional conclusions visibly provisional. For investigation techniques, see root cause analysis; a completed diagram is not itself proof of causation.
07What a traceable CAPA record contains
Organise the evidence around six connected objects. This illustrative traceability model is manufacturing practice, not a legally prescribed database schema or an exhaustive form template. Give each object a stable identifier.
- Source signal: retain the originating record, event date, affected product and lot identifiers, and the observation that prompted evaluation.
- CAPA case: define the issue, affected scope, risk rationale, accountable owner and reasons for grouping or separating signals.
- Investigation: connect hypotheses, tests and evidence references to causal conclusions, including uncertainty and explanations for rejecting alternatives.
- Action: record the commitment, owner, target date, implementation evidence and any linked change or controlled-document revision.
- Effectiveness assessment: retain agreed criteria, assessment scope, observation period, evidence references, results and the assessor’s conclusion.
- Review decision: identify the authorised reviewer, date, decision, conditions and exact evidence versions supporting approval, rejection or reopening.
Several signals can support one justified case; one case can contain several hypotheses, actions and assessments. A decision records what was approved, not merely that someone clicked approve.
Keep source records distinct from linked controlled-document revisions and attachments. A revised recipe, for example, needs its document identifier and revision in the recipe supersession history; an attached screenshot is supporting material, not the controlled revision itself. Capture attachment provenance and versions so reviewers can reconstruct the decision basis.
Preserve chronology and approval history through attributable changes suitable for audit trail review. Mark withdrawn hypotheses, superseded actions and reopened assessments with their status, reason, author and date. Link replacements to earlier entries rather than silently overwriting the previous account.
Illustrative data-model diagram Several source signals → one justified CAPA case CAPA case → investigation with multiple hypotheses CAPA case → multiple actions and effectiveness assessments Review decision → identified objects and evidence versions approved
Source Signal
Preserves the originating event and affected scope.
- signal_id
- source_type
- source_record_id
- occurred_at
- affected_lot_ids
CAPA Case
Groups justified scope, ownership, risk and status.
- capa_id
- linked_signal_ids
- risk_rating
- scope
- owner_id
- status
Investigation
Connects causal hypotheses with evidence and uncertainty.
- investigation_id
- capa_id
- hypothesis
- evidence_ids
- cause_confidence
Action
Tracks the intervention, commitment and implementation evidence.
- action_id
- capa_id
- action_type
- due_at
- change_id
- implementation_evidence_ids
Effectiveness Assessment
Records predefined criteria, observation basis and result.
- assessment_id
- capa_id
- acceptance_criteria
- observation_basis
- result
Review decision
Preserves who decided what and on which evidence.
- decision_id
- capa_id
- reviewer_id
- decision
- evidence_ids
- decided_at
08Effectiveness: define success before collecting results
For pharmaceutical quality systems, EU GMP Chapter 1, paragraph (xiv) calls for monitoring and assessing action effectiveness in line with Quality Risk Management principles.
In practical CAPA review, implementation evidence and effectiveness evidence answer different questions. An updated procedure shows that a document changed; demonstrated control performance under relevant operating conditions supports the conclusion that the action addressed the intended failure mechanism. Completing tasks alone is not a sound basis for effectiveness closure.
Before collecting results, define the essential decision inputs:
- Measurable acceptance criteria tied to the intended control.
- Exposure or operating opportunities in which the failure could occur.
- Observation conditions relevant to the affected process.
- Data provenance: where results originated and how they were collected.
- Residual risk that would remain if the criteria were met.
No complaints during an arbitrary calendar period is not convincing on its own: little product use, few relevant operations or delayed reporting may leave the control untested. Relate observation to actual opportunities for failure, not elapsed time alone.
The authorised reviewer can accept effectiveness and support closure, continue observation, revise actions or reopen investigation. Record the reasoning. For detailed assessment design and interpretation, see CAPA effectiveness checks.
09Worked cases: recurrence reduction and preventive control
Case one: recurring medical-device pouch-seal defects
This hypothetical case uses one pouch as the counting unit: each pouch is counted once as defective or acceptable. Inspection method, detection sensitivity and relevant operating conditions are assumed comparable before and after the action.
Containment starts with holding potentially affected lots and assessing their boundaries. Inspection results are linked to pouch lots, equipment and setup records. Where serialization and aggregation support packaging traceability, those identifiers also help locate affected packaged units.
The investigation finds that operators set jaw alignment by eye. Recorded measurements vary after changeovers, and controlled trials reproduce weak seals at the observed misalignment. This supports an unstable setup method rather than merely attributing defects to operator error. The selected corrective action introduces a locating fixture, a measurable alignment limit and a documented setup verification.
Implementation evidence includes the approved instruction, fixture installation checks, demonstrated operator competence and completed setup records. The observed results are:
- Before: 12 defective pouches among 24,000 inspected. 12 ÷ 24,000 × 1,000,000 = 500 defective pouches per million inspected pouches.
- After: 3 defective pouches among 30,000 inspected. 3 ÷ 30,000 × 1,000,000 = 100 defective pouches per million inspected pouches.
- Relative reduction: (500 − 100) ÷ 500 × 100 = 80%.
The 80% reduction is an observed comparison, not statistical proof or an automatic closure criterion. Reviewers assess the three remaining defects and apply the earlier effectiveness section’s decision logic; detailed assessment design belongs in the CAPA effectiveness check. Product disposition follows the separate decision gate described in the lifecycle section.
Case two: preventing a recipe–label mismatch
In this hypothetical supplement packaging audit, reviewers identify a potential mismatch between recipe selection and approved label revision before any known labelling failure. Assume six recipes on each of two lines: 6 × 2 = 12 recipe-line combinations. Recipe mappings can retain an obsolete label revision when the approved label changes.
Correcting the current mappings fixes the immediate configuration. Preventive action addresses its future maintenance: assign ownership for revision updates, require approval of mapping changes, preserve recipe change history, and introduce a start check against the approved recipe–label pairing.
Under a defined test protocol, challenge all 12 combinations with valid pairings and deliberately obsolete or mismatched revisions. Record expected and actual responses, configuration versions and reviewer decisions. Successful challenges demonstrate acceptance of valid pairings and blocking of challenged mismatches under those conditions; they do not establish a production defect rate. Subsequent review follows the lifecycle and effectiveness gates covered earlier.
10Integrations and recovery without losing the evidence chain
A practical integration design links each CAPA case to relevant production, laboratory, maintenance, supplier and controlled-document records. For manufacturing-record integration, identify the authoritative source for each record; label copied summaries so they cannot be mistaken for source evidence.
Define stable source-event identifiers, explicit field ownership, document-version references, visible transfer status and a named reconciliation owner. Specify which system may update each shared field rather than allowing the latest message to overwrite it indiscriminately.
- If a transfer fails, retain the originating event and flag the handoff as incomplete.
- Assign recovery ownership and retry using the same source-event identifier, checking for an existing case before creating another.
- Reconcile identifiers, required fields and attachment access before accepting the handoff as complete.
Route duplicate events for linking or documented consolidation. Hold mismatched lot identifiers for resolution rather than guessing a match. Mark unavailable attachments as outstanding evidence, and refer conflicting status updates to the designated field owner. For data integrity, preserve previous values, corrected values, reasons, actors and timestamps so audit-trail review can reconstruct manual corrections.
These are proposed implementation controls, not standalone legal requirements. Software transfers and organises evidence; authorised people retain the approval and disposition decisions described in the lifecycle section.
11Trending and review beyond closure counts
For pharmaceutical quality systems, EU GMP Chapter 1, 1.11 calls for procedures to manage and review actions arising from product quality review, with the effectiveness of those management procedures verified during self-inspection.
A practical management review set separates case flow from control performance. Closure counts and elapsed time show how quickly cases move; neither establishes that controls work. Consider reviewing:
- Recurring failure mechanisms across products, equipment or sites.
- Reopened cases and why earlier conclusions changed.
- Overdue actions grouped by risk, rather than one undifferentiated total.
- Repeat extensions and the constraints behind them.
- Investigation uncertainty, including conclusions still dependent on assumptions.
- Recurrence rates using meaningful denominators, such as affected batches divided by comparable batches produced during a defined period.
These are practical management choices, not universal reporting requirements. Review can prompt broader CAPA scope, resource allocation or investigation of a shared weakness. Record the decision, owner and rationale; choose review timing to suit risk and available exposure data, rather than imposing an arbitrary calendar target.
12CAPA failure modes and an implementation checklist
Use these operational review controls to identify gaps in a CAPA record. They are a self-assessment aid, not a compliance certification or a substitute for applicable requirements.
| Failure mode | Observable warning | Review control |
|---|---|---|
| Unsupported scope restriction | Other potentially affected lots or lines excluded without explanation | Challenge exclusions against exposure evidence. |
| Actions disconnected from causal evidence | Action list lacks links to supported findings | Map each action to its causal target. |
| Uncontrolled changes to commitments | Dates or deliverables overwritten | Retain approved revisions and reasons. |
| Missing implementation evidence | Completion asserted without supporting records | Check executed records and applicable versions. |
| Unresolved integration exceptions | Failed transfers or conflicting statuses remain open | Reconcile exceptions before relying on transferred records. |
For root-cause shortcuts, revisit “Root cause: evidence before conclusions”; for unsupported closure, revisit “Effectiveness”; for misleading metrics, revisit “Trending and review beyond closure counts.”
Questions the record should answer
- Applicability: Which product, jurisdiction and internal procedures govern this case?
- Escalation: What justified opening a CAPA, including the quality risk assessment documented in the quality risk register?
- Scope: Which products, lots, equipment and sites were assessed, and why were any excluded?
- Traceability: Can findings be traced to identifiable source records?
- Linkage: Which supported cause does each action address?
- Ownership: Who owns each commitment and its due date?
- Implementation: What evidence confirms execution under appropriate change control?
- Assessment: Were success criteria defined before results were judged?
- Authority: Who reviewed the evidence and authorised the decision?
- Recovery: What interruptions, retries or reconciliations occurred, and were their effects resolved?
Frequently asked questions
Q.Does every deviation or complaint need a separate CAPA?+
A practical approach is to assess each event without automatically creating a separate CAPA. Record the investigation, immediate correction, risk assessment and escalation rationale in the originating deviation record or complaint record. Repeated failures, serious consequences or a shared control weakness favour CAPA escalation. ICH Q10 §3.2.2 recommends investigation effort proportionate to risk. Define escalation criteria within the quality management system, and trend events handled without CAPA so that individually minor issues do not conceal a recurring problem.
Q.When can related events across products, suppliers or sites share one CAPA?+
As an industry practice, related events can share one CAPA when evidence supports a common failure mechanism and the action plan addresses every affected context. Similar symptoms alone are insufficient. Use root cause analysis to test the connection, then identify affected products, suppliers, sites and linked investigations explicitly. Assign local implementation owners and assess results in each relevant setting. Cross-site learning can support wider application, but separate CAPAs are more useful when causes, controls or acceptance criteria materially differ.
Q.Can a CAPA be closed when the true root cause remains uncertain?+
Uncertainty does not necessarily prevent a defensible closure decision. EU GMP Chapter 1, paragraph (xiv) advises considering and addressing the most likely causes when the true causes cannot be determined. As a practical closure standard, document the hypotheses investigated, remaining uncertainty, actions addressing plausible causes and evidence supporting their adequacy. An authorised reviewer should assess residual risk against predefined closure criteria. Define reopening triggers and a suitable CAPA effectiveness check; completing tasks alone does not resolve causal uncertainty.
Q.Does every CAPA need both a corrective action and a preventive action?+
Do not add a token preventive action merely to fill a form field. ICH Q10 §5 distinguishes corrective action against recurrence from preventive action against occurrence. In practice, correcting an affected label fixes the immediate defect; changing the label-selection control addresses its cause. Extending that control to another process with an identified potential failure may be preventive action. Select actions for the demonstrated problem and risk, using mistake-proofing where appropriate, and document why the selected combination is sufficient.
Q.How should completion dates, overdue actions and extensions be justified?+
As a planning practice, set dates from risk, interim protection, technical dependencies and the time needed to obtain meaningful evidence—not a single arbitrary duration for every CAPA. Separate implementation milestones from effectiveness-review dates. An extension record should preserve the original date, explain the delay, reassess exposure and identify an authorised approver. Link technical dependencies to change control. Escalate overdue high-risk actions and recurring extensions through management review, rather than repeatedly moving deadlines without resolving resource or execution problems.
Q.How should a batch-disposition decision be handled while a linked CAPA remains open?+
As a practical decision structure, maintain separate but linked assessments for batch acceptability and long-term system improvement. An open CAPA is neither permission to release nor, by itself, proof that a batch must be rejected. The authorised disposition decision should address the affected batch, investigation findings, unresolved uncertainty and applicable release criteria. Keep supporting evidence in the batch record and rationale in the QA disposition step. If evidence cannot support acceptability, retain the hold rather than substituting promised future actions.
Q.How should a manufacturer and a contract supplier divide CAPA ownership and evidence responsibilities?+
A practical allocation is to name one coordinating owner while assigning investigation and implementation tasks to the party controlling the relevant process. Define evidence access, notification triggers, review responsibilities and acceptance criteria in the quality agreement and CAPA plan. A supplier corrective action request can track deliverables, but a completion statement alone is weak evidence. Request the records needed to evaluate the cause, implemented controls and results. Each party’s authorised personnel should make decisions within their assigned authority.
Q.Can an 8D investigation be used within a CAPA without creating duplicate records?+
Yes. As a record-design practice, use the 8D report as the investigation and problem-solving record, then map its content to the CAPA workflow rather than rewriting it. Establish requirements traceability between containment, causal evidence, selected actions, implementation records, effectiveness results and approvals. The CAPA record can hold ownership, status and closure decisions while referencing controlled 8D sections. Check for gaps explicitly: finishing the eight disciplines does not, by itself, demonstrate that your organisation’s CAPA acceptance criteria have been satisfied.
Primary sources
Explore this topic
CAPA sits inside 3 overlapping topic clusters in our glossary. Every neighbour is one click away.
Drug-product cGMP rules, ICH Q-series, and the regulators that enforce them.
Root-cause toolkit, SPC, capability and the rest of the QA practitioner's bench.
HCT/Ps, blood cGMP, donor eligibility, ISBT 128 labeling and forward-tracing lookback.
Want to see how CAPA could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
