PMDA (Japan): Pharmaceuticals and Medical Devices Agency

PMDA is the Pharmaceuticals and Medical Devices Agency. Its Outline of PMDA describes it as a “Japanese regulatory agency, working together with Ministry of Health, Labour and Welfare”, with the obligation “to protect the public health by assuring safety, efficacy and quality of pharmaceuticals and medical devices.” In practice that means three linked functions: scientific review of marketing-authorisation applications, monitoring of post-marketing safety, and relief compensation for people harmed by adverse drug reactions or infections from pharmaceuticals or biological products.

• Reviews and Related Services covers clinical trials, reviews, consultations, compliance assessments and inspections concerning applications for drugs, medical devices, regenerative medical products and other products within the agency’s stated scope.
• Post-marketing Safety Measures covers collecting and providing post-marketing safety information, together with scientific research and analysis of collected data.
• Relief Services for Adverse Health Effects is the third service area considered here; the homepage identifies relief systems for adverse drug reactions.

These are official service descriptions, not a checklist of binding applicant requirements. Detailed safety activities belong in the dedicated safety section; relief eligibility and operational details are outside this article’s scope.

The three functions are presented as one system rather than three separate offices: information gathered after marketing feeds back into how products are reviewed, and relief cases are themselves a signal about real-world harm. For an overseas company this matters because a single product may touch all three — a review or consultation before approval, safety reporting and information duties after approval, and, if harm occurs, a relief process that patients rather than the company initiate. The questions below keep those threads distinct.

For a separate market reference, see MHRA (UK); keep each jurisdiction’s agency information attached to its own project context.

The most common search question about PMDA is how it relates to MHLW. The official Outline of PMDA answers it in one phrase: PMDA is a Japanese regulatory agency “working together with Ministry of Health, Labour and Welfare.” PMDA performs the scientific work — reviews, consultations, compliance assessments, inspections, safety analysis and relief administration — as an incorporated administrative agency, while MHLW is the ministry. The English outline does not set out which body issues each formal legal decision, so do not infer a reporting hierarchy or a split of approval powers from that phrase alone.

Specific items on PMDA’s English site carry an MHLW attribution — for example, the navigation lists “Strategy of SAKIGAKE by MHLW”, and the safety updates include “MHLW Pharmaceuticals and Medical Devices Safety Information No.431 posted”. These show MHLW-authored material published through PMDA channels; they illustrate the working relationship rather than define legal powers.

The Regulatory Science service description places Japanese Pharmacopoeia and medical device standards within standards development. Keep those technical references distinct from institutional names: a reference to a standard is not an answer to who makes a formal decision.

As an internal working practice, record the organisation, document title and technical question separately. For a device project, distinguish a medical device classification question from a question about the device development phase. Use those distinctions to sharpen the enquiry, not to infer a Japanese route or requirement. For example, an entry reading only “PMDA standard” leaves the team without a precise reference; replace it with the named document and the question the responsible reviewer must resolve.

Start with two separate questions: which jurisdiction is the project addressing, and how is the product described? PMDA’s service synopsis expressly names drugs, medical devices and regenerative medical products. Product-navigation entries provide additional starting points, but should not be treated as complete application instructions.

The US example is deliberately narrow. Section 211.65(a) requires contact surfaces not to be reactive, additive or absorptive so as to alter a drug product’s safety, identity, strength, quality or purity beyond official or other established requirements. It is not a Japanese application requirement or evidence of cross-jurisdiction equivalence. The separate 21 CFR 211 reference provides context for that US framework.

Keep the authority categories distinct: PMDA’s official agency descriptions explain services; the cited CFR provision is binding US regulatory text; the later preparation workflow is proposed internal practice, not a PMDA requirement. Neither a service synopsis nor a navigation label should substitute for a product-specific route decision.

For internal preparation, record the proposed category, jurisdiction, unresolved question and responsible reviewer separately. Leave uncertain classifications open for resolution rather than carrying assumptions into application planning. This reference does not assign Japanese regulatory routes to foods, supplements or general chemicals.

The Outline of PMDA lists the review-side services as: consultations on clinical trials and other issues; regulatory review of drugs, medical devices and regenerative medical products; re-examinations/re-evaluations; GLP/GCP/GPSP compliance assessments for regulatory submission documentation; GMP/QMS/GCTP inspections of manufacturing processes and facilities; inspection of registered certification bodies; and development of standards such as the Japanese Pharmacopoeia. Two distinctions are useful. Compliance assessments look at the studies and documents behind a submission (GLP for non-clinical studies, GCP for clinical trials, GPSP for post-marketing studies), while GMP/QMS/GCTP inspections look at manufacturing processes and facilities — QMS for medical devices and GCTP for regenerative medical products. And inspection of registered certification bodies concerns third-party bodies, not manufacturers directly.

The site’s Reviews and Related Services menu keeps two groupings distinct: GLP / GCP / GPSP Compliance Assessments and GMP / QMS / GCTP Inspections. Preserve those labels when organising questions; do not turn them into assumed assessment criteria or infer that every product follows both groups.

Prepare questions, not an assumed dossier

As an internal preparation method, start with the uncertainty the team needs to resolve. Identify the product, assign a person who can explain the background, and locate relevant internal information. The table suggests working records, not documents PMDA requires.

Use a linked question register

A proposed consultation-question record contains question_id, product_id, service_label, question_text, background_reference_ids, owner_id and status. This is an internal organisational aid, not a PMDA form. Use question_text for the clarification sought, background_reference_ids for traceable context, and owner_id for the person responsible for progressing it. A status such as “open—awaiting assessment” makes uncertainty visible without presenting it as a requirement.

For example, keep a question about how a manufacturing change is described separate from a question about its relevance to product review. Give each its own question_id and owner, retain the same product_id, and cross-reference the two records. Shared background can include a relevant batch record; maintaining its identity and revision through document control helps both owners work from the same context.

Before taking either question forward, the responsible people should assess its wording, supporting information and proposed service label. An unanswered question remains an open issue for human assessment, not a presumed PMDA requirement or an inferred agency decision.

PMDA’s safety activities are described in the Outline of PMDA’s Post-marketing Safety Measures. The detailed list belongs to that safety-service description, not to the review-service synopsis. It identifies six activities:

• Accepting submitted information on precautions.
• Collecting and organising safety information from marketing authorization holders (MAHs) or medical institutions.
• Conducting scientific research and analysis of collected information.
• Providing consultation services on safety measures for MAHs.
• Providing consultation services for consumers.
• Providing safety information on drugs, medical devices and regenerative medical products.

These are official descriptions of PMDA’s activities, not a manufacturer reporting checklist. Keep the named audiences attached to their respective activities: MAH safety-measure consultations and consumer consultations are separate entries. For broader terminology, see post-market surveillance; use PMDA’s own activity labels when describing its services.

The Outline of PMDA breaks post-marketing safety into six services: acceptance of submitted information on precautions; collection and organization of safety information from marketing authorization holders (MAHs) or medical institutions; scientific research and analysis of collected information; consultation services on safety measures for MAHs; consultation services for consumers; and provision of safety information on drugs, medical devices, and regenerative medical products. Read from a manufacturer’s side, two are inbound (information PMDA receives), one is analytical, two are advisory and one is outbound publication. A company planning for Japan should therefore expect a dialogue rather than a one-way filing: its own safety information is an input, PMDA’s analysis and published safety information are outputs it must monitor, and the MAH consultation service is a route for discussing safety measures before acting on them. The exact reporting obligations and timelines sit in Japanese law and notices, not in this outline.

Relief: keep the enquiry narrowly framed

The Outline of PMDA lists five relief services: relief service for adverse drug reactions; relief service for infections acquired through biological products; health allowances etc. for SMON patients; health allowances for HIV-positive and AIDS patients; and financial assistance under the Act on Special Measures concerning hepatitis C infection caused by specified fibrinogen and blood coagulation factor IX products. These schemes serve affected people, not applicants. For an individual enquiry, check the applicable scheme’s current rules before advising on eligibility, amounts, assessment criteria or documents.

Suggested internal separation

For internal organisation, distinguish a safety-information item from an individual relief enquiry. This is a proposed recordkeeping practice, not a PMDA submission format or a determination of reporting obligations.

• Safety-information item: identify the information received and the safety question requiring assessment; assign a responsible safety contact.
• Relief enquiry: record the person’s question about the adverse-drug-reaction relief system and assign responsibility for finding the appropriate official information.

If one communication contains both a safety concern and a question about relief, retain the connection but track the two purposes separately. Answering the relief question should not, by itself, close the internal safety assessment; likewise, assessing safety information should not be treated as an answer about relief eligibility. The practical control is purpose-specific ownership: each question remains visible until the responsible person records its disposition.

This is proposed internal practice, not an official PMDA procedure, mandatory lifecycle or expected review sequence. The same framing governs the suggested record model, worked cases and operational controls that follow. Product context enters the workflow; a documented next action with a named owner leaves it. Choosing an information route does not resolve a product-specific regulatory question.

1. Establish context. The project lead records the product, intended use, Japan-related question and current project state. Use consistent identifiers, as discussed in production context tagging, to keep related records connected.
2. Select the service question. The regulatory lead states whether the immediate question concerns reviews, post-marketing safety or relief, without treating that choice as a classification decision.
3. Locate the relevant official information. The assigned researcher records the official page, its title, access date and the passage relevant to the question.
4. Organise working records. The document owner connects product context, references and correspondence, distinguishing current working versions from superseded material.
5. Separate unresolved issues. The technical lead lists assumptions, conflicting information and unanswered questions separately from supported conclusions, assigning each issue an owner.
6. Record human review. The responsible authorised reviewer documents the interpretation, rationale and limits. Where record history matters, consider an audit trail review workflow as a separate internal control.
7. Track the chosen next action. The action owner records the task, internal target date, dependencies and completion evidence; the project lead checks closure.

Regulatory and quality decisions remain with responsible authorised people. Completing this workflow produces neither agency approval, quality release nor compliance certification.

Use five linked entities to organise internal preparation. This proposed model is neither a PMDA submission schema nor a software specification. It separates published information from the company’s interpretation and assigned work.

One product can have multiple preparation items and safety items. Each item can link to several references and recorded decisions. Use stable identifiers rather than product names or document filenames as connections; names may change without changing the underlying record.

Reuse a reference_id wherever the same publication informs another item, instead of copying the document into every product record. Keep the publication title and URL in Official reference; keep the product-specific question, owner and interpretation in the linked item and Decision record. A company’s proposed next action is not part of the official publication. Record who made that interpretation using attributable recording.

These example values are invented internal entries, not official identifiers or confirmation of an applicable route. “Open” means the internal question remains unresolved.

A simple register or optional document tools can hold this model. Choose the format around clear links, readable context and named human responsibility; the model does not depend on a particular application.

These hypothetical exercises illustrate internal preparation, not official procedures. Quantities and people are illustrative; the outputs are working records for human review, not agency decisions.

Case 1 — Drug-project preparation

• Assumption: The product is already being treated as a drug for this exercise. The team has nine candidate working records: six distinct usable references, two duplicate records and one unresolved item. The unit is records: 9 = 6 + 2 + 1.
• Action: Link each usable reference to the question it addresses. Mark the two duplicates and retain their relationship to the chosen reference rather than counting them as additional support. Assign the unresolved item to Maya, the fictional project regulatory lead, to establish its relevance and intended use.
• Recorded output: A cleaner internal question register distinguishes usable references, duplicates and an open item with an owner. Six usable records describe this exercise only; they are neither a required nor a sufficient dossier.
• Unresolved decision: Maya must decide whether the open item supports an existing question, needs clarification or belongs outside the project. Nothing in the reconciliation establishes submission acceptance, regulatory readiness certification or a predicted review result.

Case 2 — Medical-device manufacturing question

• Assumption: A device team holds an equipment assessment originally prepared for a US drug-manufacturing context. Its reference record identifies that context, including any existing link to 21 CFR 211.
• Action: Preserve the assessment’s original purpose, version and conclusions. Open a separate Japanese product-specific question: which route and manufacturing-related questions need resolution for this device? Assign it to the Japan regulatory affairs lead, with the manufacturing engineer responsible for explaining the assessment’s technical boundaries.
• Recorded output: A linked reference plus an unresolved route question, with named roles responsible for follow-up. Any proposed revision can enter the team’s change control process rather than silently overwriting the original context.
• Unresolved decision: The responsible lead must determine the assessment’s relevance to the Japanese question. The document is not relabelled as a completed Japanese requirement, and no agency outcome is inferred.

Case 3 — Marketed-drug safety intake

• Assumption: A company receives precautions-related information and, separately, a consumer enquiry about adverse health effects involving a marketed drug.
• Action: Apply the service distinctions covered above. Create separate intake items, preserving each message and product context. Assign the precautions item to a safety reviewer and the consumer enquiry to a designated consumer-response reviewer, with safety-team review where appropriate.
• Recorded output: Two distinguishable records, each with an owner, the original communication and an open review question. Link them only if a reviewer establishes a relevant connection.
• Unresolved decision: Authorised reviewers determine the next action. This exercise does not decide clinical causality, reporting obligations or relief eligibility.

These proposed internal controls protect applicant working records; they are not Japanese legal requirements or agency acceptance criteria. Apply them when checking product references, record status and copied project content.

Use product-context tagging to support association checks and an audit trail review workflow to examine corrections. Record what changed, who changed it and why. Repairing a link or identifier corrects the working record; it does not resolve the underlying regulatory question. Keep the decision unchanged unless the responsible person separately reviews and documents a revised conclusion.