Learning UDI Community
The FDA has identified the need to actively engage with a coordinated, action-oriented, and early adopter unique device identifier (UDI) community. To answer this call, AHRMM has organized the Learning UDI Community (LUC), a broad-based coalition comprised of healthcare leaders across sectors whose goal is to develop a common understanding and approach to UDI adoption within the healthcare setting. Accelerating UDI adoption across the healthcare field is essential to meeting the call for Cost, Quality, and Outcomes, the Triple Aim, and evidence-based care.
A memorandum of understanding signed by AHRMM and the FDA formally demonstrates both parties' collaborative support of the LUC.
Cross-functional work groups develop progressive practices, proposed solutions, and resources to focus on topics that can accelerate UDI adoption. More work groups will be established as the LUC Community identifies additional topics specific to UDI adoption.
View a summary of each work group’s project scope and charter. Work group progressive practices and resources will be shared below and in the LUC Resource Listing as they are made available.
If you are interested in joining a work group, contact AHRMM at email@example.com.
- Search Criteria for High Risk Implants
The current implantable device list posted at the AccessGUDID website is based upon an FDA product code query of the Global Unique Device Identification database. The query currently returns all devices that are cleared or approved with a product code that classifies the device as implantable. Since product codes are based upon device approval and not device use, the list includes implants and associated medical devices (e.g. instruments) that are together classified as an implant for device approval. This work group is charged with developing a more user-based set of search criteria that would be run against AccessGUDID and return a search result to document implants in health IT – including those working with the automated billing process – and to be shared publicly.
- Device Categorization: GMDN/SNOMED Terminologies
In order for the UDI Program and broader National Evaluation System for Medical Devices in Health IT (NEST) to bring value to the healthcare enterprise, all parties along the medical device spectrum (manufacturer/labeler through end user) need to be speaking the same language and terminology. This work group should review the pro’s and con’s of GMDN and SNOMED terminologies and review findings of preliminary pilot exercises (RAPID), while also recognizing that additional vocabularies for medical devices, such as UMDNS, UNSPSC, or others, may provide value to GUDID device data and NEST priorities.
- UDI Single Use Device (SUD) Packaging Exception and Distributor Low Unit of Measure Programs
This work group will explore cost effective and sustainable solutions around labeling at the lowest unit of measure/unit of use —where technically feasible—devices that meet the UDI final rule’s SUD packaging exception.
Work Groups No Longer Accepting New Participants
- Catalog Number Fields
The mission of the Catalog Number workgroup is to provide the business case and industry value for requiring catalog number in GUDID submissions. In order to use the information in the GUDID, most stakeholders will need to match existing data sets to the GUDID, and manufacturer catalog number is the key data point that has been used historically for identifying product information.
- Clinically Relevant Size
The mission of the Clinically Relevant Size (CRS) workgroup is to provide the framework for the FDA GUDID system to facilitate correction of existing device size data in the GUDID and to accurately capture device size data for new entries into the GUDID
- Medical Devices Containing Human Cells, Tissues, and Cellular and Tissue-Based Products (HCT/P)
Human cells, tissues, and cellular and tissue-based products (HCT/P) are widely used in healthcare. Most of these products are regulated as biologics, but some products fall within the scope of medical devices. An identifier is required to allow tracking from recipient to donor and from donor to recipient. FDA regulation uses the term distinct identification code. The distinct identification code needs to be captured at all point in the supply chain in order to allow rapid tracking and recall of all the products derived from the implicated donor. The UDI Final Rule requires that medical devices containing HCT/P carry a production identifier for the distinct identification code. The 2015 Edition Health Information Technology (Health IT) Certification Criteria Final Rule requires that the distinct identification code be parsed from the UDI when a medical device contains an HCT/P. These requirements have the potential to significantly improve the traceability of medical devices containing HCT/P following distribution from the tissue processor. In addition, improvements in the ability of the supply chain to capture donor related identifiers could help to improve biovigilance and support outcome evaluation. However, the stakeholders involved in handling these particular products need to work together to gain the greatest leverage from the UDI regulation.
- UDI Benefits to Healthcare Supply Chain Processes
While unique product identification is a standard cost management tool for manufacturers and retailers, healthcare executives juggle many priorities and they need a clear map showing how UDI will reduce expense in hospitals both immediately and in the long term. This work group will develop five important work flow processes as they currently work without UDI and then contrast these to future work flows where UDI is incorporated in hospital information systems and operations. Savings opportunities will be discussed for each step where they are found. The work group will author an article to be published in a journal respected by hospital CEOs and CFOs. In addition, the work product will be presented in AHRMM educational materials on line and in the upcoming annual meeting in August, 2017.
- UDI Capture
The ultimate goal of this work group is to identify opportunities for case studies, initiate them and bring answers to the greater Learning UDI Community to foster learning and hopefully, shorten the adoption curve for capturing UDI's within healthcare.
UDI Capture Work Group Case Studies:
- Beaver Dam Community Hospital
- Franciscan Missionaries of Our Lady Health System (FMOLHS)
- Stanford Health Care
- University Health Network
- University of Tennessee Medical Center
- Unit of Use
FDA Global Unique Device Identification Database (GUDID) compliance currently requires manufacturers to provide unique device identifiers at the “Unit of Use” (UOU). Many products have multiple discrete items contained within the lowest packaging level. In those instances, the requirement is to provide unique device identification for items that are not intended to be labeled in the product. These identifiers will only be found in the GUDID itself. This work group will develop recommendations and guidance addressing the issues existing with Unit of Use.
Join the Community
Additional UDI Resources
Alternative names (aka) for the DI of UDI used by each issuing agency: