WHO GMP TRS 1044 (2022)

WHO GMP TRS 1044 is an informal reference to the GMP-related material in WHO Technical Report Series 1044, the 56th report of the WHO Expert Committee on Specifications for Pharmaceutical Preparations. It is a search phrase, not the publication’s official title. The WHO TRS 1044 publication record identifies it as a meeting report published on 22 December 2022.

For WHO international guidance on pharmaceutical products, the separate main-principles GMP guide is TRS 986, Annex 2. Keep that document identity distinct from TRS 1044: the report number is not an alternative identifier for the main-principles guide. For the broader manufacturing concept rather than a particular publication, see cGMP.

A practical citation hierarchy for a pharmaceutical quality system is:

1. Report identity: record the WHO Technical Report Series number and report title.
2. Individual guidance-text title: identify the particular text relevant to the question.
3. Document locator: record the annex identifier and relevant section or page from that text.
4. Applicable edition: identify the version used for the assessment rather than relying on a shorthand label.

This is suggested bibliographic control, not a WHO citation requirement. Check the particular guidance text for its scope and annex identifier; do not assign a report-wide annex number. In a review record, a reference to TRS 1044 alone identifies the collection but leaves the technical basis unclear. A complete citation lets another reviewer find the same passage before assessing its relevance to a site decision.

For international medical-product guidance, the TRS 1044 overview lists the texts below as included in the report and recommended for implementation. Read this as a guidance map, not a universal legal checklist. Start with the decision under review, then locate the individually titled text that addresses it.

The reader assignments and routing questions are suggested reading aids, not descriptions of detailed WHO provisions. They distinguish manufacturing questions from product-specific testing, submission and regulatory-system questions without assigning annex numbers.

After selecting a text, read its scope and relevant passage before using it in a technical assessment. Topic titles alone do not establish a site-specific acceptance criterion: a water heading does not supply a sampling limit, and an HBEL heading does not supply a cleaning limit.

For a record-focused reading path, use ALCOA+ and audit trail review workflow as companion terminology, not substitutes for the selected WHO text. Keep the reading note narrow: identify the decision, the relevant document and the question that still needs technical interpretation.

For WHO international medicines-quality guidance, the TRS 1044 overview describes the listed texts as adopted and recommended for use. Treat that recommendation as the starting point for an applicability assessment, not proof of local adoption. Check the current national text for scope before assigning a legal obligation.

Keep these assessment categories distinct:

• Binding legal authority: for each claimed obligation, record jurisdiction, product classification, current authority text and applicable provision.
• Official guidance: identify the relevant WHO text and why it informs the decision.
• Site-selected industry practice: document the technical rationale for the chosen approach without presenting it as law.
• Supporting software: identify the records and routing needed to support accountable decisions.

Use a decision register like this. Topic entries are candidates for assessment, not conclusions that WHO guidance applies.

In this proposed operating model, regulatory affairs evaluates applicability with product and process specialists. The designated quality authority approves a site change; the designated product-disposition authority makes any release, rejection or hold decision, subject to the confirmed market-specific role. Record these responsibilities in site cGMP procedures. Software records and routes information; accountable people review and approve decisions.

Use this comparison as a navigation tool, not an equivalence test or compliance assessment. Start with the decision being made; similar GMP terminology does not make references interchangeable.

For WHO international guidance on pharmaceutical products, the TRS 986 Annex 2 overview describes the main-principles guide’s use in assessing manufacturing-authorization applications and as a basis for inspecting manufacturing facilities. For the same WHO pharmaceutical-product guidance, the overview says it may also be used as training material for government medicines inspectors and industry production, QC and QA personnel.

For example, when reviewing a cleaning task, choose the individual technical text for the topic assessment, the applicable legal provision for a legal conclusion, and the approved procedure for the operator’s task. Use a cGMP overview for orientation and the relevant batch record to connect execution evidence to that task—not as substitutes for those references.

For a pharmaceutical manufacturer assessing a relevant TRS guidance text, the following is a suggested implementation lifecycle—not a WHO-mandated quality-system architecture. Use the site’s change-control process to connect the assessment to an owned proposal, reviewable evidence and a recorded decision.

1. Identify the exact document. Record its title, version and relevant passage so reviewers can distinguish the report from the particular guidance text being considered.
2. Assess applicability. Regulatory staff document market and product relevance in an applicability rationale, using the distinctions covered above. Identify the affected operations and explain any exclusions.
3. Compare the process. The process owner describes current operations, including existing controls and records. Turn the comparison into a gap statement identifying a decision or control to improve, rather than copying a guidance title.
4. Define the proposal. Open a change record describing the intended modification, affected procedures, dependencies and owner. Technical specialists evaluate whether the proposed control addresses the identified gap.
5. Establish acceptance criteria. Before evaluating results, specify what evidence would support implementation and how exceptions will be handled. Assess training impact alongside procedural and technical changes.
6. Review the evidence. Quality reviewers compare results with the acceptance criteria and assess unresolved exceptions through the site’s quality-assurance process. Record whether the evidence supports the proposal or further work is needed.
7. Record the implementation decision. Route the evidence to the decision authority established above. Document the decision, its rationale, any conditions and the closure evidence linking completed actions to the approved change.

Keep these handoff artifacts connected: applicability rationale, current-state process description, gap statement, change record, acceptance criteria, training impact and closure evidence. A useful record lets the next reviewer follow why the change was proposed, what was tested and how the final decision followed from the results.

For pharmaceutical quality assurance, the WHO report overview lists Points to consider when including Health Based Exposure Limits (HBELs) in cleaning validation. Use that topic, discussed above, to navigate the guidance; the following cleaning-validation review illustrates site-specific technical reasoning, not a WHO calculation method.

Assume a pharmaceutical manufacturer uses shared equipment, proposes a different product sequence and already has a site-approved HBEL assessment. The HBEL is expressed in mg/day; the analytical residue result is expressed in µg/swab. No exposure value or residue acceptance limit is assumed.

1. Identify the product pair and boundary. Record the preceding product, following product and shared product-contact equipment. Compare the proposed sequence with the sequence covered by the existing rationale, including the relevant cleaning step at campaign changeover.
2. Locate the approved exposure assessment. Check that its substance identity, scope and approval correspond to the residue being evaluated; an assessment for another substance does not establish this link.
3. Trace the site’s exposure model. Identify how measured residue informs estimated carryover and potential patient exposure. mg/day and µg/swab are not directly interchangeable: converting mass units alone does not connect a sampled surface to daily exposure.
4. Examine sampling and recovery. Review sampled locations, represented surface area, extraction and recovery assumptions, and whether recovery correction is already included in the reported result. Identify assumptions that the proposed sequence could invalidate.
5. Assess the sequence change. Decide whether the existing rationale still covers the product pair, equipment boundary and cleaning conditions, or whether additional technical assessment is needed for the proposed campaign changeover.

If the exposure-to-residue link remains unresolved, retain that question in the change assessment and obtain appropriate toxicological, cleaning-validation or analytical review before deciding whether to implement the sequence. Closure evidence links the approved rationale, affected equipment, analytical method and reviewer decision, including how the unresolved question was answered. A passing swab result alone does not resolve a missing exposure rationale.

Assume a pharmaceutical-water system has undergone maintenance. A conductivity result is reported in µS/cm, while a comparison result uses a different temperature-reporting condition. No numerical acceptance limit is assigned here. This is an illustrative site review, not a WHO test method or sampling instruction.

Start with the maintenance record: identify the work performed, its timing and the affected sampling point. Link the post-maintenance result to its sample identity, collection time, analytical method and original laboratory record. Confirm that the comparison result represents a relevant location and operating state rather than merely a nearby date.

Next, examine the reporting conditions: measurement temperature, whether temperature compensation was applied, and the basis used to report each result. Check the method and site-approved criteria for the applicable reporting basis. Identical units alone do not establish comparability. Avoid an improvised conversion simply to place both results on the same trend chart; obtain a method-supported comparison or document why comparison remains unresolved.

Keep uncertainty about measurement conditions separate from a confirmed water-system finding. A difference awaiting clarification is not yet evidence of deterioration, but neither does that uncertainty establish acceptable system performance. Once comparability is established, assess the result against the applicable site-approved criteria and relevant history.

• Reporting discrepancy: follow the record-correction process, retaining the original result, correction reason and review history; use the established audit-trail review workflow.
• Genuine process concern: route the finding to the appropriate investigation, linking maintenance, sampling and analytical evidence.
• Use decision: document the evidence considered, unresolved questions, any restrictions and the accountable approval under the authority model covered above. A result upload is evidence for review, not a system or product release decision.

Assume an original laboratory report expresses a concentration in mg/L, while the imported record displays mg/mL. No result value is assigned, no numerical correction is inferred, and neither record is presumed accurate. The following is a suggested pharmaceutical quality-review workflow, not a WHO-prescribed procedure.

Recover the meaning before correcting the record

1. Identify the source report, its version, sample identity and import event. Retain the original report and the affected imported representation so the discrepancy remains reconstructable.
2. Compare the reported value and unit alongside the method context, including any dilution or reporting basis. A unit-label mismatch alone does not establish whether the value needs changing.
3. Determine whether the discrepancy originated in the laboratory source, the mapping or the display. Use the audit trail review workflow to trace relevant changes rather than choosing whichever record appears more plausible.
4. Document the justified correction and assess decisions that used the affected data. Identify downstream records requiring reassessment, including calculations, summaries or quality decisions.

Link evidence without merging record roles

A proposed data-integrity-by-design model links these records while keeping their purposes distinct:

The authoritative source result, its imported representation and the review decision are not interchangeable. A corrected display is evidence about the representation; it does not by itself establish the validity of the laboratory result.

For closure, record the discrepancy’s origin, correction rationale, affected downstream records, verification of the corrected representation and the reviewer’s conclusion. The human reviewer evaluates whether that evidence resolves the discrepancy and its consequences; a successful edit alone is not closure.

For outsourced testing and water-system maintenance, define the handoff around the assessment that uses the work. The following are proposed coordination arrangements, not requirements attributed to TRS 1044.

• Laboratory testing: name a laboratory contact to supply source results and supporting records, explain methods and reporting units, communicate corrections, and route technical questions to the analyst or method specialist.
• Water-system maintenance: name a contractor lead to supply work records, identify affected components, explain measurements and units, communicate corrected service reports, and answer technical questions. Link the work to the relevant maintenance record and post-maintenance assessment.

A proposed agreement can identify record access, change notification, discrepancy escalation, responsible contacts and the site decision that depends on the work. Distinguish the supplier’s deliverable from the manufacturer’s assessment: a test report or completed service record is information for review, not the site’s conclusion about suitability. For approval ownership, refer to the decision-authority discussion above.

When a supplier record is missing or ambiguous, identify the affected assessment and request the specific missing information. Record the resulting limitation or resolution in the associated change or deviation investigation, including whether the unanswered question prevents the dependent decision.

A proposed handoff connects document control, the laboratory system and quality change management. This is an integration design pattern, not a WHO requirement or a claim about available application features. For laboratory interfaces, see MES to LIMS integration.

Exchange stable document, revision, sample, result and change-record identifiers, source links, units, status and review references. Document control identifies the latest approved revision; a newer uploaded file does not replace it merely because its timestamp is later. The laboratory handoff references the applicable revision, and the change record links the results and their review.

Route each exception with its affected record identifiers and a named owner, rather than leaving it only in a technical log. Use exception-based review to organise unresolved handoffs.

Recovery follows reconciliation against the source, a justified correction and controlled reprocessing. Preserve the original event and recovery decision, including the owner and review reference. Confirm that downstream records reflect the reviewed state; a successful resend alone is insufficient. A late correction also prompts reassessment of affected earlier reviews, within the human-approval boundary described above.

Use this suggested internal checklist to test decision traceability, not to predict inspection findings. Record gaps against the affected decision rather than treating every gap as an equipment problem.

For ongoing document control, consult the WHO Expert Committee publication page and individual publication records. Check document identity, status, edition and any applicable corrections before revising the site bibliography. Do not infer supersession from a later publication date alone.

Before closing the assessment or associated change control, ask: can a reviewer trace the selected text to the product and market, the affected process, the accepted evidence, unresolved questions and the approval decision? Give open questions an owner and explain their effect on closure. Where no physical change is proposed, retain the documented assessment and rationale; absence of equipment work is not evidence that review is unnecessary.