EMVO AMS and EAMS Explained for MAHs
If you are a Marketing Authorisation Holder (MAH) operating in Europe, alert management has become a daily operational capability that protects supply continuity, patient safety, and regulatory credibility.
The European Medicines Verification System (EMVS) only works at scale when alerts are handled quickly, consistently, and with high-quality data. A single alert at dispensing can trigger quarantine procedures, investigations, and communication with national verification organizations. When this happens across hundreds of SKUs, multiple CMOs, and many European markets, the operational workload grows rapidly.
This is why many MAHs are shifting toward a structured operating model for alert handling, supported by the European Alert Management System (EAMS) and EMVO’s Alert Management System (AMS) capabilities.
This guide explains:
- What EMVO AMS and EAMS mean in practice
- How they connect to the EMVS ecosystem
- What responsibilities sit with MAHs
- How organizations can build a scalable alert management operating model across markets and partners.
Term | Definition |
FMD / Delegated Regulation (EU) 2016/161 | Defines the regulatory framework for safety features, verification, decommissioning, and incident handling requirements under the EU Falsified Medicines Directive. |
EMVS | The European Medicines Verification System: The end-to-end verification ecosystem composed of the EU Hub and National Verification Systems used to authenticate prescription medicines across Europe. |
EU Hub | The central gateway where Marketing Authorisation Holders (MAHs) upload product and pack data, which is then distributed to national medicines verification systems. |
NMVO / NMVS | National Medicines Verification Organization and National Medicines Verification System connected to the EU Hub, responsible for operating verification infrastructure within each country. |
OBP (On-Boarding Partner) | An entity connected to the EU Hub responsible for uploading and managing product serialization data. This is typically the MAH or a delegated partner such as a CMO or service provider. |
Level 5 Alert | A critical exception requiring investigation within the EMVS network. A Level 5 Alert does not automatically indicate falsification, but it must be investigated according to defined procedures. |
EAMS | The European Alert Management System, designed to streamline alert handling, communication, and documentation across the EMVS ecosystem. |
AMS / AMS Hub | The infrastructure that enables routing and storage of alert-management information between national alert systems and OBP systems. |
Reference: EU Delegated Regulation 2016/161 (EUR-Lex)
Why EAMS Matters for MAHs
For most Marketing Authorisation Holders, EMVS alerts are not theoretical events, they are daily operational incidents managed by serialization and supply chain teams.
A single “red” outcome at dispensing can trigger:
- Product quarantine
- Pharmacy investigation
- NMVO communication
- Internal root-cause analysis
Multiply this across many products, markets, and packaging partners, and alert management quickly becomes a recurring operational workload.
Many organizations initially manage alerts through manual communication between serialization teams, quality departments, affiliates, and CMOs. As alert volumes increase, this fragmented approach becomes difficult to sustain.
This is where EAMS becomes important.
EAMS helps standardize how alerts are documented, communicated, and tracked across European markets, allowing investigations to move more consistently across national verification systems.
A mature approach to alert management typically includes four key ingredients:
- Strong master data governance to prevent avoidable alerts caused by upload or packaging inconsistencies.
- A clear investigation workflow, so alerts move predictably from New to Resolved.
- Cross-functional ownership across serialization operations, quality, IT, affiliates, and packaging partners.
- Structured communication channels with NMVOs, end-users, OBPs, and MAHs — with EAMS integrated into many investigation procedures. See EMVO’s AMS project announcement for background.
For companies operating across multiple European markets, this structure is increasingly necessary to keep investigations consistent, traceable, and auditable.
EMVO AMS vs EAMS and How They Connect to EMVS
EAMS in one sentence
EAMS standardizes alert-handling communication and documentation across Europe, helping stakeholders resolve alerts consistently across national systems.
Where the AMS Hub fits
Many teams assume AMS is simply a portal, but operationally the AMS Hub functions as a routing and data-sharing layer connecting national alert systems and OBP systems. See the EMVO Self-Service Portal: AMS documentation for a full technical overview.
This infrastructure allows alert information to move between MAHs, NMVOs, National Systems and OBP Environments. Treating AMS purely as a user interface often leads to underutilization. In practice, it functions as part of the data and workflow backbone supporting alert investigations.
What “OBP-based” means for MAHs
AMS access is OBP-based, meaning OBPs create MAH users and organize them into teams that control alert visibility by market.
According to the EMVO Self-Service Portal: “The AMS is an OBP based system…”
Operationally, this means the team structure defined during onboarding has a direct impact on investigation speed and ownership. Designing teams, market responsibilities, and daily triage processes is therefore an important part of making alert management scalable.
MAH Operating Model, Roles and Workflow
The Operational Reality
An alert is not just a notification. It is a workflow with a lifecycle. Programs often struggle when alerts are treated like inbox messages instead of structured investigations.
A Scalable 4-Layer Model
Many MAHs structure alert handling around four operational layers:
- Triage: Classify the alert, assign an owner, and start the SLA clock.
- Investigation: Collect evidence, run system checks, and determine the root cause.
- Communication: Coordinate with NMVOs, pharmacies, and internal stakeholders.
- Prevention: Implement CAPA actions and eliminate recurring root causes.
EAMS investigation guidance aligns closely with this flow, including EU Hub transaction checks, NMVO support requests, pack photo analysis and escalation procedures. See EMVO guidance on investigating EU Hub alerts.
Suggested MAH Roles
Across many MAHs, alert management works best when roles remain simple, clearly owned, and consistently applied across markets and partners.
- Alert Duty Officer (Serialization Operations): Daily triage, ownership tracking, SLA enforcement.
- Master Data Owner: GTIN, batch, expiry, and product data validation.
- Packaging / CMO Liaison: Investigation of print and packaging execution issues.
- IT / Integration Owner: EU Hub connectivity checks and system evidence.
- Quality Owner: Deviation logic, CAPA decisions, escalation management.
- Local Affiliate Coordinator: Country-specific procedures and NMVO communication.
- Security / Anti-counterfeit Team: Engaged when investigations indicate elevated risk.
End-to-End Workflow (Compact Version)
While procedures differ slightly across organizations, the core alert investigation process generally follows the same operational flow.
- Alert triggers in NMVS or from EU Hub transaction
- End-user quarantines pack per local SOP if required
- MAH triages alert and assigns investigation owner
- Evidence collection begins (EU Hub logs, pack photos, upload confirmation)
- Root cause identified and documented
- Corrective action executed
- Escalation performed when required
- CAPA actions implemented to prevent recurrence
Seeing recurring A3 or A52 alerts? Our team specializes in root-cause investigations for high-volume MAHs. Let’s look at your alert pattern together. |
Top Alert Types MAHs See Most Often
EMVO’s EMVS Alerts and Notifications reference document defines standardized alert codes. The table below highlights alerts that frequently require MAH investigation.
Alert code | What it means | Typical root causes | First action for MAH |
A2 | Batch not found | Batch not uploaded, upload timing delay, EU Hub issue | Confirm release batch exists, validate upload completeness |
A3 | Pack not found | Upload gaps, mis-scan, client software error | Check 2D data matrix integrity and routing, request pack photo |
A52 | Expiry date mismatch | Wrong expiry printed or uploaded, packaging execution issue | Compare printed vs uploaded expiry, confirm packaging order |
A68 | Batch identifier mismatch | Wrong batch printed or uploaded, line clearance issue | Compare printed vs uploaded batch, check CMO records |
A7 | Pack already in requested state | Previously supplied or decommissioned, cross-market conflicts | Investigate pack state history and end-user steps |
A24 | Status change could not be performed | Conflict with existing pack state | Confirm intended transaction and client business rules |
Operational principle: NMVO guidance emphasizes that an alert does not automatically mean falsification. Your workflow should quickly rule out technical and procedural causes.
Building a Scalable Alert Management Process
Organizations that handle alerts effectively treat alert management as an operational process supported by systems, data, and analytics. To get there, treat it like a product inside your pharma supply chain digital transformation roadmap.
A. Core Systems and Integrations You Need
Typical alert management environments include:
- Serialization L4/L5 platforms
- EU Hub connectivity monitoring
- EAMS / AMS access
- Ticketing systems to manage investigations
- Analytics dashboards
- Knowledge bases with investigation guidance
B. Investigation Data Fields
Standardizing these fields across markets simplifies reporting and helps identify recurring root causes. Typical investigation records include:
- Alert ID, country, NMVO
- GTIN, batch, expiry
- Alert code and classification
- Assigned owner
- Investigation timestamps
- Evidence attachments
- Root cause conclusion
- Corrective and preventive actions
C. High-ROI Automation Ideas
Some organizations reduce manual workload through automation. Examples include:
- Auto-triage rules: Automatically route alert codes to the correct team.
- Evidence RPA: Auto-pull EU Hub upload confirmations, logs, and master data into the case.
- Alert trend dashboards: Track alerts by code, market, CMO, SKU, sites, weekly trends.
- Anomaly detection: Identify spikes in specific alert codes that may signal packaging or upload problems.
Example Trend Chart
Alerts per 10,000 scans
Week | Alert Rate |
Week 1 | 18 per 10,000 scans |
Week 2 | 14 per 10,000 scans |
Week 3 | 10 per 10,000 scans |
Week 4 | 6 per 10,000 scans |
Goal: reduce avoidable alerts through data governance and packaging controls.
Benchmarks, Mini Case and a 90-Day Implementation Plan
Alert Rate Benchmark
A stability rate of 0.05% or lower for total scans is given as a directional benchmark by EMVO in EMVO Best Practice on Alert Handling (EMVO-00306). When alert rates exceed this level, common drivers include:
- Upload completeness issues
- Packaging data inconsistencies
- Client software configuration
- Pharmacy scanning behavior (*)
- Master data errors
(*) EMVO and several NMVOs have repeatedly emphasized that “the vast majority of alerts originate from operational or technical causes rather than suspected falsification.” Common operational behaviors causing alerts are: scanning already decommissioned packs, pharmacy software configuration issues, scanning during returns or stock checks, and incorrect workflow use in pharmacies or hospitals.
Mini Case: A7 Alerts After Pharmacy Stock Check Scans
A spike in A7 “Pack already in requested state” alerts appears in one market. Investigation shows packs were already correctly decommissioned during dispensing, but are being scanned again during pharmacy stock checks. The fix path stays practical and focused:
- Immediate: confirm pack state history and document investigation
- Short-term: validate pattern with NMVO and confirm pharmacy workflow trigger
- Fix: communicate correct scanning procedures with NMVO and pharmacy software providers
- Prevent: monitor recurring A7 patterns and include them in alert trend analysis
90-Day Implementation Plan for MAHs
Days 1–15: Stabilize
- Assign alert investigation owners
- Publish a clear RACI model
- Establish triage SLA (e.g., first response within 24 hours)
- Standardize investigation record templates
Days 16–45: Integrate
- Connect alerts to ticketing systems
- Build dashboards by alert code and market
- Develop knowledge-base guidance for common root causes
Days 46–90: Prevent
- Conduct weekly root-cause reviews with CMOs and affiliates
- Automate evidence collection where possible
- Launch a program focused on reducing avoidable alerts
Closing: What to Tell Leadership
EAMS and EMVO AMS represent a shift toward alert handling that is structured, documented, and measurable across Europe. For MAHs, the practical 2026 strategy is to embed alert management into pharma supply chain digital transformation with clear ownership, strong master data controls, consistent evidence capture, and prevention loops that reduce repeat alerts and protect supply continuity. For the full regulatory foundation, refer to the EMVO Best Practice on Alert Handling (EMVO-00306).
For more information about SCW Consultancy Services;
For additional detail and help, please contact:
Mia Van Allen – Managing Partner – mia.vanallen@supplychainwizard.com
