Netherlands Adopts US FDA-based UDI System for Medical Devices
A voluntary agreement (link in Dutch) was consummated by the Dutch Ministry of Health, industry, and hospitals. According to an Emergo blog post, under the terms of the agreement, the Netherlands will adopt the US Food and Drug Administration’s Unique Device Identification (UDI) system.
According to the post, Dutch hospitals agreed to use UDI codes exclusively for identification and traceability of medical devices, and industry promised to place only UDI codes on device labels. According to the Emergo post, this means that every manufacturer that wants their devices used in Dutch hospitals now needs to provide UDI codes on those devices.
An article from Securing Industry cites to the the Dutch Ministry of Health as saying that the decision to use the FDA’s UDI system was made to avoid adding complexity for manufacturers by requiring a separate system. According to the article, the Netherlands is the first in the EU to adopt the FDA’s UDI system, a decision that some believe may increase the chances of the UDI system being adopted elsewhere in the region.
In 2013, the US published the rule requiring UDI codes to be assigned by device manufacturers to each version or model of a device. Under the published rule, the codes must be in both human and machine readable formats. According to the FDA, implementation of UDI codes improves patient safety, modernizes device postmarket surveillance, and facilitates medical device innovation.
FDA Releases Draft Guidance for Unique Device Identifiers
The FDA has just released draft guidance for unique device identifiers (UDIs) tracking medical devices from their manufacturers to the end users. Specifically, the FDA is providing guidance to device the content and form of UDIs that was lacking (or at least unclear) in the original FDA UDI rule which was published on September 24, 2013.
UDI laws are currently listed under 21 CFR 801.20, and every medical device in commercial distribution is required to have a UDI, unless an exception or alternative applies (for example if the UDI is not technologically feasible). They must be given by an official UDI Issuing Agency that is in line with international standards for medical devices.
The UDI rule began applying to Class III devices in 2014 and implantable, life-supporting and life-sustaining devices in 2015. Class II devices will be in compliance this year, and Class I and non-classified devices will need to have them in 2018.
In this updated draft guidance, the FDA has clarified what forms that the UDI are required to be on medical device packaging. Specifically, the guidelines clarify that the UDIs must be present in two forms on the label and device packing: 1) “easily readable plain-text” and 2) automatic identification and data capture (AIDC) technology. The UDI then must be submitted to the Global UDI Database.
The guidelines provided further information on a number of other topics as well. For example, the guidelines clarified the AIDC technology should be read by a barcode scanner or similar technology, and the UDI may be split into multiple segments on medical device packaging. Moreover, multiple types of AIDC technology can be used on a device label, both representing the same UDI. However, if the UDI is not visible to the human eye, the packaging must disclose that there is the presence of AIDC technology.
The guidance further discussed the specific content of the UDIs, including device and product identifiers as well as data delimiters, and the particular ordering of such information on the packaging.
The FDA providing guidance to the UDI Rule is not uncommon, as a number of other guidances have been issued, such as the guidance issued on June 27, 2014 regarding the Global Unique Device Identification Database and the general guidance issued on August 20, 2014. As this is a complex and important issue, the FDA contains FAQ pages for any questions medical device manufactures may have.
The draft comments will be open for comment for 60 days, and both written and electronic comments are accepted.