The EMA released updated technical registration requirements for the PMS public API, mandating MAHs to review and ensure system compatibility with these requirements for effective data submission.
Compliance with the new API requirements is necessary for accurate pharmacovigilance reporting, including vital ICSR/E2B identifiers, impacting the integrity of regulatory data management.
MAHs and technical teams must review the revised API registration requirements and implement necessary system updates to comply by the established timelines.
Regulatory Intelligence Lead
Review in the next regulatory intelligence cycle.
Release of technical specifications for public PMS API registration; Annex B updates for ISO IDMP implementation; registration requirements for beta and production environments for substance and product data management.
Marketing Authorization Holders (MAHs) and technical teams responsible for regulatory data management must review the new registration requirements to ensure their systems can integrate with the PMS API. This affects the submission of master data which is critical for pharmacovigilance reporting (e.g., ICSR/E2B identifiers).
MAHs and technical teams must review the revised API registration requirements and implement necessary system updates to comply by the established timelines.
The EMA has updated the technical registration requirements and API documentation for the PMS public API beta release. Marketing Authorization Holders (MAHs) must review these requirements to ensure their systems are compatible with the API, which is critical for pharmacovigilance reporting, particularly regarding ICSR/E2B identifiers.
What changed: The EMA released updated technical registration requirements for the PMS public API, mandating MAHs to review and ensure system compatibility with these requirements for effective data submission.
Why it matters: Compliance with the new API requirements is necessary for accurate pharmacovigilance reporting, including vital ICSR/E2B identifiers, impacting the integrity of regulatory data management.
Practical implication: MAHs and technical teams must review the revised API registration requirements and implement necessary system updates to comply by the established timelines.
Published from the Firecrawl policy change extraction pipeline.
Implement a gap analysis for 505(b)(2) applications to identify safety data needs and adjust safety monitoring systems as necessary to accommodate new product characteristics.
MAHs and sponsors must enhance their pharmacovigilance systems to monitor microbiome-specific safety issues, comply with established safety standards, and address concerns related to antimicrobial resistance.
Stakeholders, including manufacturers and clinicians, must review and potentially revise their post-market vigilance and safety monitoring protocols in response to the FDA's proposed regulatory approaches for generative AI devices.
Developers of MBMPs must align their safety assessment protocols with the MHRA's expectations and are encouraged to engage with the MHRA early to establish appropriate regulatory strategies.
