EAMS Onboarding for MAHs (Access, Teams, Workflows, and Day-to-Day Setup)
EAMS onboarding is where many MAHs unintentionally create future pain. Not because the platform is hard, but because alert management is an operating model, not a login. A mature pharma supply chain digital transformation approach treats EAMS as a structured collaboration layer -- enabling consistent triage, investigation, escalation, and prevention across markets. Less mature setups tend to focus on access and overlook ownership design and daily execution.
The EAMS Handbook for MAHs connects best practices with MAH workflows and country-specific requirements and is the primary reference document for onboarding design.
What good onboarding looks like for MAHs
A well-structured EAMS onboarding becomes visible in operations within the first two weeks. The signals are practical:
- Alerts are visible only to the appropriate roles, within the correct markets
- Triage is performed daily with documented decisions rather than informal communication
- Evidence is requested promptly -- pack photos, end-user clarification, EU Hub checks
- Escalation status is used consistently when needed
The common onboarding failure pattern
Creation of a single global user group with broad access generates a predictable outcome:
- Ownership becomes unclear
- Notifications are diluted and often ignored
- Local NMVO-specific requirements are missed
- Escalations are delayed
A more effective model is based on role-driven teams aligned to market coverage, supported by a defined daily duty workflow. The sections below walk through how to build it.
Step-by-step: EAMS onboarding checklist for MAHs
Confirm OBP model and access path
As AMS is OBP-based, the first step is to confirm which OBP will grant MAH access and how the structure will be defined. EMVO does not have a direct legal relationship with MAHs, so OBPs manage MAH access entirely. Key decisions at this stage include: how access will be coordinated with the OBP (internally or via external partners); whether teams will be structured by affiliate, market, or product family; and identification of the MAH administrator responsible for user lifecycle and governance.
Create users and define access governance
User creation is straightforward -- but governance is what determines long-term sustainability. Recommended practices: use named accounts only (never shared access); perform quarterly access reviews; maintain an access log covering user, role, market scope, and validity. Without governance, initial onboarding stability tends to degrade over time, particularly in multi-affiliate or multi-CMO environments.
Build teams and assign markets correctly
Team and market configuration is the most critical success factor in onboarding. Market assignment directly determines alert visibility. Users may belong to multiple teams with different market scopes, allowing flexibility when structured intentionally. See the recommended team structure in the section below.
Define the daily triage workflow
Access without a defined operating rhythm produces the same outcome as a shared mailbox with no owner. Before going live, document who reviews alerts each day, how classifications are assigned, what constitutes an immediate evidence request, and what triggers escalation. This is the operational layer that determines whether EAMS functions as a tool or as a capability.
Standardize the investigation record template
Define a standard investigation record format before the first alert is processed. Core fields should include alert ID, country and NMVO, GTIN, batch, expiry, serial number, alert type code, triage classification, owner and timestamps, evidence list, root cause, corrective action, and CAPA reference. Standardization enables structured analysis, trending, and future automation -- aligning onboarding directly with broader digital transformation goals.
Recommended team structure for a scalable model
The team structure below mirrors how alerts are actually solved: triage first, then specialized investigation, then escalation and prevention. It is designed to work across multi-market MAH environments without creating access gaps or ownership ambiguity.
| Team | Primary purpose | Typical members | Markets |
|---|---|---|---|
| MAH Global Triage | Daily triage and ownership assignment | Serialization Ops, Alert Duty Officer | All active MAH markets |
| Market Investigation Pods | Local procedure compliance and documentation | Affiliate QA, Local Supply Chain | 1 to 5 markets per pod |
| Packaging and CMO Response | Root cause on print and packaging execution | Packaging QA, CMO liaison | Markets supplied by that CMO |
| EU Hub and IT Diagnostics | Connectivity, uploads, and systems evidence | IT integration lead | All markets (support role) |
| Quality Escalation | Suspected falsification handling and authority route | QA lead, Security | Markets as needed |
Day-to-day operating model inside EAMS
EAMS onboarding does not end with access. A defined daily operating rhythm is what separates organizations that absorb alert volume from ones that are constantly catching up.
Daily triage workflow
- Review new alerts by market and type
- Classify each alert into one of four categories: end-user error; data or upload issue; packaging execution issue; or unclear / requires deeper investigation
- Assign ownership and start the SLA clock
- Request evidence immediately where required -- early evidence collection significantly reduces investigation time and operational impact
Escalation handling
Escalation is a structured signal within EAMS, not an informal handoff. It is typically required when evidence is insufficient to progress the investigation; when patterns suggest systemic issues across batches or markets; or when NMVO or end-user coordination is required. Once escalated, alerts become visible and highlighted to all relevant stakeholders. As the EAMS Handbook makes clear, national authorities should be informed about a suspected falsification as soon as technical reasons can be ruled out -- escalation should not be delayed when approaching that threshold.
The investigation record template
A standardized investigation record should be used across all markets, even where local NMVO procedures differ. Core fields to include:
- Alert ID, country, and NMVO
- GTIN, batch, expiry, serial number (where applicable)
- Alert type code and triage classification
- Owner and timestamps (triage, response, closure)
- Evidence list (photos, logs, screenshots)
- Root cause, corrective action, and CAPA reference
Mini case: market assignment gap creates invisible alerts
A recurring onboarding issue arises when users are created but not assigned to teams with the appropriate market scope -- resulting in alerts that are effectively invisible to the people who should act on them.
Operational impact:
- Alerts remain unassigned
- Local pharmacies quarantine packs longer than necessary
- Investigation SLAs are not met, often without immediate visibility
Corrective approach:
- Establish a central MAH Triage team covering all markets
- Define backup ownership for continuity
- Run a weekly visibility test: pick one alert from each market and confirm correct team visibility
Onboarding maturity scorecard: first 30 days
Use this scorecard to track onboarding progress during the first month of EAMS operations. These five metrics answer whether your operating model is functioning -- or just activated.
| Metric | What it proves | Target after 30 days |
|---|---|---|
| % alerts triaged within 24h | Ownership and daily rhythm | 90% or above |
| % alerts with complete record fields | Documentation maturity | 85% or above |
| Average time to first evidence request | Investigation speed | Under 1 business day |
| % alerts stuck with no owner | Access design quality | 0% |
| Repeat alert rate by SKU or site | Prevention maturity | Downward trend |
A simple week-by-week triage rate progression to target in week one through four:
FAQ: EAMS onboarding for MAHs
How is EAMS different from national alert systems?
EAMS functions as the European coordination layer for alert management, enabling communication between MAHs, NMVOs, end-users, and EMVO across the full EMVS ecosystem. National systems (NAMS) operate at the country level and support investigations inside that country -- and may not always be fully connected to the AMS Hub, meaning MAHs may need parallel communication routes in some markets. In practice, alert handling often requires both centralized coordination through EAMS and country-specific communication pathways for local investigations.
Why is AMS OBP-based and what does that mean for MAHs?
As EMVO does not maintain a direct legal relationship with MAHs, OBPs are responsible for creating users and structuring access. For MAHs, this means onboarding success depends entirely on access governance and segmentation: who your OBP is, how accounts and teams are structured, and whether market coverage and ownership are designed for daily execution -- not just system activation. See the EMVO Self-Service Portal AMS documentation for the full technical overview.
How do teams and markets affect alert visibility?
In the AMS Portal, teams are how you control visibility. Administrators create a team and then assign markets (countries) and members to that team. The market selection under "alerts raised in" determines which country alerts that team can see. If a user is not in the right team, or the team does not include the right markets, alerts become effectively invisible. This is why a scalable model uses role-based teams -- triage, investigation pods, IT diagnostics, packaging QA -- rather than one global group.
When should MAHs escalate an alert?
Escalation is appropriate when standard investigation cannot progress; when patterns indicate potential systemic issues across the same SKU, batch, market, or location; or when NMVO coordination is required to maintain end-user anonymity and move the case forward. Once escalated, the alert is marked "Escalated" and highlighted so all users concerned by the alert can see the status. From a patient safety and compliance perspective, national authorities should be informed about a suspected falsification as soon as technical reasons can be ruled out -- escalation should not be delayed when approaching that threshold.
What evidence should MAHs request first?
Initial evidence should focus on quickly narrowing down the likely root cause -- whether the issue originates from data, system behavior, or packaging execution. An effective first evidence set typically includes:
- A clear photo of the pack, capturing both the 2D Data Matrix and human-readable batch and expiry
- Confirmation of EU Hub upload and data availability, including timing and any retries
- Reference batch master data for the affected SKU (expected batch and expiry values)
- Relevant packaging documentation where applicable -- for example, packaging order or line clearance evidence
How do country-specific requirements affect workflows?
Country-specific requirements can modify or override the standard alert handling flow. In some markets, local procedures differ from the general guidelines, requiring additional steps or alternative communication paths. This is best managed through a modular SOP structure: a single global workflow supported by country-specific appendices. This allows consistent execution while ensuring local requirements are fully addressed. For country-by-country NMVO response timelines, see the SCW blog series on NMVO timelines.
Final thought
EAMS onboarding is often approached as a system activation step. In practice, it defines how alert management will operate on a daily basis -- for every alert, across every market, for every CMO batch that enters the European supply chain.
Organizations that establish clear ownership, structured workflows, and disciplined execution early tend to reduce investigation time, improve consistency, and limit repeated alerts. In most cases, the difference is not driven by the system itself, but by how effectively the operating model is designed and implemented from the outset -- and how well it is embedded into the broader digital transformation of the pharma supply chain.
Need support designing your EAMS operating model?
SCW's serialization consultants have structured EAMS onboarding programs across global MAH networks in Europe, North America, and Asia. From team design to daily triage workflows, we bring frameworks and implementation support -- not just recommendations.
Book a Meeting Explore Track and Trace Services