Over a year since the EU FMD came into force, false alerts remain a problem preventing the realisation of the full benefits of the directive. Grant Courtney examines the reasons behind these alerts occurring and looks at the action stakeholders must now take.
Over a year since the EU FMD came into force, false alerts remain a problem preventing the realisation of the full benefits of the directive. Grant Courtney examines the reasons behind these alerts occurring and looks at the action stakeholders must now take.
This report addresses the key factors shaping pharmaceutical formulation, including regulation, QC and analysis.
Access the full report now to discover the techniques, tools and innovations that are transforming pharmaceutical formulation, and learn how to position your organisation for long-term success.
What you’ll discover:
Key trends shaping the pharmaceutical formulation sector
Innovations leading progress in pharmaceutical formulation and how senior professionals can harness their benefits
Considerations and best practices when utilising QbD during formulation of oral solid dosage forms
Can’t attend live? No worries – register to receive the recording post-event.
On 9 February 2019, new legislation was introduced within the EU with the aim of increasing patient safety by preventing falsified products from entering the pharmaceutical supply chain. The EU Falsified Medicines Directive (2011/62/EU) or EU FMD as it is known, called for a significant overhaul to the existing pharma supply chain system, requiring the establishment and implementation of new organisations and systems needed to authenticate every medicine distributed across the European market.
Initially most of the stakeholder effort was focused on meeting the compliance deadline. For manufacturers this included upgrading productions lines, putting in new IT systems, establishing new processes and running regulatory pack change programmes. Products were generally ready in time across the industry and from 9 February 2019, as per the directive, all packs which were released onto the market carried a two-dimensional (2D) data matrix barcode with a unique identifier (serial number) encoded, along with a tamper evident feature to ensure the integrity of the pack. However, it would be wrong to believe that hitting the compliance deadline was the end of the journey. In many respects, February 2019 was just the starting point for the EU FMD.
Over 130 million prescribed packs are now scanned every single week. The scale of the systems is impressive and the EU FMD has fundamentally changed the way in which prescription medicines are manufactured and how they are managed prior to dispensing. These changes present an even greater challenge than the technical ones already encountered and the implications and impacts are only just starting to surface a year in.
For most of the millions of packs being dispensed each day, the pharmacists receive positive confirmation that the unique identifier is valid and may allow the pack to be dispensed. When this occurs everything runs smoothly, however, not all scans end with a positive confirmation.
The EU FMD systems are designed to identify any unique identifier on a pack which is not in the system or has a status which means it should not be dispensed. When a pack fails to authenticate, the system generates an alert which is distributed to several stakeholders including an alert to the market authorisation holder (MAH).
[Credit: Grant Courtney/Be4ward].
Alerts generated by the system due to the unsuccessful authentication of a pack are vital as they flag a potential falsified product, allowing action to be taken to address the reason and any potential criminal activity. An alert raises concern over the quality and authenticity of the product, preventing it being dispensed to the patient.
Initially the level of alerts being generated was very high, running at about six percent of all scans. Many of these alerts were false due to two main causes. Firstly, some manufacturers had not managed to upload all the serial numbers into the European Medicines Verification System (EMVS) so missing data was triggering errors. Secondly, the pharmacy systems had not been configured correctly and were introducing errors into the decoded barcode data. These errors included converting upper case characters into lower case and interpreting dates incorrectly.
During the past year, most authorities have taken a lenient view on the alerts, understanding that new software and processes have to stabilise and become embedded. In recognition of this, many operated on a period of stabilisation, whereby packs that triggered an alert could still be dispensed at the discretion of the pharmacist.
Many of these early problems have now been resolved, consequently the level of alerts has reduced to around the one percent mark as an average across EU countries. However, this level is still considered too high with many false alerts continue to take place. It will be progressively more difficult to reduce this further and we can expect this to take many months more to resolve.
With false alerts still in play, if an alert is triggered it is necessary to establish if it is due to a technical or procedural error or if in fact it is due to a suspected falsified product. The need to investigate and resolve alerts is stated as a requirement within the Delegated Regulation and the organisation operating the National Medicines Verification System should provide for the immediate investigation of all potential incidents of falsification (Art 37(d)). Moreover, the EU Q&A document makes specific reference that the National Medicines Verification Organisations should ensure the National Competent Authorities (NCA) are informed as soon as it is clear that the alert cannot be explained by a technical or procedural issue.
The MAH has a role to play in this and must check if it has caused the alert by not uploading the serialisation data or if the data has errors. The expectation is that this resolution should happen within a few days and the relevant NMVO made aware of the outcome of this investigation. In addition, authorities are starting to introduce specific reporting requirements and systems which could vary from country to country.
…EU FMD systems are designed to identify any unique identifier on a pack which is not in the system or has a status which means it should not be dispensed”
The common goal remains that we must reach the point at which an alert prevents a pharmacist from dispensing the medicine to the patient, as dictated by the legislation and with this in mind, several member states have now ended their stabilisation period.
The resolution of alert errors heralds a new phase in the EU FMD journey, where the target is for investigation and resolution of alerts to happen quickly, with the results documented and shared with the NMVOs and authorities. If alerts are caused by technical or procedural issues within the MAH then Corrective and Preventative Actions (CAPAs) need to be executed in alignment with quality procedures and the data uploaded or corrected to resolve the issue before many more alerts are triggered for the same batch. The consequence of not addressing these false alerts is that the flow of goods will stop and product returns could increase.
What should manufacturers be doing and what is coming next?
If manufacturers have not already started, processes and systems must now be put in place to receive, analyse and investigate alerts. The backlog of any alerts that have not been addressed should be cleared and any technical or procedural issues identified and resolved. The regulatory environment should be carefully monitored so that the emerging requirements on alert reporting are captured and built into internal procedures. Regulators are starting to include aspects of the EU FMD within audits and alert management will feature as a topic within these moving forward.
Companies also need to consider how they are going to manage this on an ongoing basis. Tools that have worked for tracking alerts up to now, such as spreadsheets, will reach their technical limit as over time the historical volume of alerts grows. Systems will also have to output to external alert reporting systems operated by the NMVOs and authorities requiring new functionality and potential interfaces.
It is perhaps not surprising that legislation as ambitious as the EU FMD will take some time to achieve its original goal of preventing falsified products from entering the pharmaceutical supply chain. A tremendous start has been made and it is now time to build on this significant foundation and ensure that necessary alert management steps are put in place to allow falsified packs to be correctly identified, only then will the benefits of EU FMD be fully realised.
About the author
Grant Courtney spent 24 years at GlaxoSmithKline (GSK), most recently as its FMD Project Manager and now consults within his area of expertise relating to the interface between patients and healthcare providers and the product, including product coding such as product authentication, patient engagement and mobile health initiatives. Grant also contributes to the shaping of global standards and is an adviser and member of the GS1 Global Healthcare Leadership Team, driving adoption of standards to increase patient safety and lower healthcare costs.
This website uses cookies to enable, optimise and analyse site operations, as well as to provide personalised content and allow you to connect to social media. By clicking "I agree" you consent to the use of cookies for non-essential functions and the related processing of personal data. You can adjust your cookie and associated data processing preferences at any time via our "Cookie Settings". Please view our Cookie Policy to learn more about the use of cookies on our website.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorised as ”Necessary” are stored on your browser as they are as essential for the working of basic functionalities of the website. For our other types of cookies “Advertising & Targeting”, “Analytics” and “Performance”, these help us analyse and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these different types of cookies. But opting out of some of these cookies may have an effect on your browsing experience. You can adjust the available sliders to ‘Enabled’ or ‘Disabled’, then click ‘Save and Accept’. View our Cookie Policy page.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Cookie
Description
cookielawinfo-checkbox-advertising-targeting
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertising & Targeting".
cookielawinfo-checkbox-analytics
This cookie is set by GDPR Cookie Consent WordPress Plugin. The cookie is used to remember the user consent for the cookies under the category "Analytics".
cookielawinfo-checkbox-necessary
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-performance
This cookie is set by GDPR Cookie Consent WordPress Plugin. The cookie is used to remember the user consent for the cookies under the category "Performance".
PHPSESSID
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
viewed_cookie_policy
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
zmember_logged
This session cookie is served by our membership/subscription system and controls whether you are able to see content which is only available to logged in users.
Performance cookies are includes cookies that deliver enhanced functionalities of the website, such as caching. These cookies do not store any personal information.
Cookie
Description
cf_ob_info
This cookie is set by Cloudflare content delivery network and, in conjunction with the cookie 'cf_use_ob', is used to determine whether it should continue serving “Always Online” until the cookie expires.
cf_use_ob
This cookie is set by Cloudflare content delivery network and is used to determine whether it should continue serving “Always Online” until the cookie expires.
free_subscription_only
This session cookie is served by our membership/subscription system and controls which types of content you are able to access.
ls_smartpush
This cookie is set by Litespeed Server and allows the server to store settings to help improve performance of the site.
one_signal_sdk_db
This cookie is set by OneSignal push notifications and is used for storing user preferences in connection with their notification permission status.
YSC
This cookie is set by Youtube and is used to track the views of embedded videos.
Analytics cookies collect information about your use of the content, and in combination with previously collected information, are used to measure, understand, and report on your usage of this website.
Cookie
Description
bcookie
This cookie is set by LinkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.
GPS
This cookie is set by YouTube and registers a unique ID for tracking users based on their geographical location
lang
This cookie is set by LinkedIn and is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.
lidc
This cookie is set by LinkedIn and used for routing.
lissc
This cookie is set by LinkedIn share Buttons and ad tags.
vuid
We embed videos from our official Vimeo channel. When you press play, Vimeo will drop third party cookies to enable the video to play and to see how long a viewer has watched the video. This cookie does not track individuals.
wow.anonymousId
This cookie is set by Spotler and tracks an anonymous visitor ID.
wow.schedule
This cookie is set by Spotler and enables it to track the Load Balance Session Queue.
wow.session
This cookie is set by Spotler to track the Internet Information Services (IIS) session state.
wow.utmvalues
This cookie is set by Spotler and stores the UTM values for the session. UTM values are specific text strings that are appended to URLs that allow Communigator to track the URLs and the UTM values when they get clicked on.
_ga
This cookie is set by Google Analytics and is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. It stores information anonymously and assign a randomly generated number to identify unique visitors.
_gat
This cookies is set by Google Universal Analytics to throttle the request rate to limit the collection of data on high traffic sites.
_gid
This cookie is set by Google Analytics and is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visited in an anonymous form.
Advertising and targeting cookies help us provide our visitors with relevant ads and marketing campaigns.
Cookie
Description
advanced_ads_browser_width
This cookie is set by Advanced Ads and measures the browser width.
advanced_ads_page_impressions
This cookie is set by Advanced Ads and measures the number of previous page impressions.
advanced_ads_pro_server_info
This cookie is set by Advanced Ads and sets geo-location, user role and user capabilities. It is used by cache busting in Advanced Ads Pro when the appropriate visitor conditions are used.
advanced_ads_pro_visitor_referrer
This cookie is set by Advanced Ads and sets the referrer URL.
bscookie
This cookie is a browser ID cookie set by LinkedIn share Buttons and ad tags.
IDE
This cookie is set by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
li_sugr
This cookie is set by LinkedIn and is used for tracking.
UserMatchHistory
This cookie is set by Linkedin and is used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.
VISITOR_INFO1_LIVE
This cookie is set by YouTube. Used to track the information of the embedded YouTube videos on a website.