EMA releases minor eAF 1.28 versions ahead of mandatory-use dates

Several transitions are moving at once

The July file release is small in isolation, but it lands inside a larger regulatory-data transition. Organizations must track the interactive PDF form version, its procedure-specific use dates, the move toward PLM web-based eAF, and dependencies on Product Management Service data. Treating all of that as one generic eAF project can obscure which teams, products, and submission types are actually affected.

EMA says the new MAA forms address structural limitations and improve alignment with the ISO IDMP data model. It also gives separate dates for EMA and national competent authority use. A controlled impact assessment therefore needs procedure, product type, authority, submission date, and form channel—not only a software release number.

Data integrity becomes an operating prerequisite

EMA's preparation guidance for mandatory PLM eAF use tells applicants to verify PMS data integrity and access rights. That moves part of application-form readiness upstream into master-data stewardship, role administration, and exception management. A RIM interface cannot compensate for duplicate, truncated, inaccessible, or poorly governed source data.

Buyers should test how a platform identifies source ownership and prevents an application workflow from silently correcting authoritative product data in the wrong system. They should also examine how technical exceptions are recorded when an interactive PDF is used after the web-based transition.

How to evaluate product claims

A vendor statement that it integrates with EMA or supports IDMP needs decomposition. Useful evidence includes the exact data objects exchanged, supported procedures, write and read behavior, reconciliation logic, exception queues, and the provider's update process when EMA changes a form or interface.

RegQuality Review will not infer complete EMA submission readiness from a product page. Provider profiles will identify whether evidence supports regulatory master data, submission planning, application-form preparation, publishing, or authority exchange, and will mark unresolved boundaries explicitly.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.