University Health Network UDI Capture Work Group Case Study
WORK GROUP TITLE:
UDI Capture Work Group
CASE STUDY PARTICIPANTS:
Wendy Watson, OR Supply Chain Manager at University Health Network
CASE STUDY ORGANIZATION:
University Health Network (UHN) serves the residents of Toronto, Ontario, Canada’s largest city, and the surrounding communities. UHN is comprised of 10 program areas spread across four hospitals and eight sites. It has $2B in revenues, 1,200 patient beds and its surgeons perform 24,000 surgical procedures each year.
Affiliated with the University of Toronto, UHN has the largest hospital-based research program in Canada, with major research in cardiology, transplantation, neurosciences, oncology, surgical innovation, infectious diseases, genomic medicine, and rehabilitation medicine. The scope of research and complexity of cases at UHN has made it a national and international source for discovery, education, and patient care.
UHN initiated a supply chain technology transformation project throughout its 40 operating rooms (ORs) and two sites with a goal to achieve clinical time efficiencies, patient safety and surgeon cost data for improved decision making and savings. The system provides surgeons with their real-time procedure cost data for all surgical supplies used per patient, per procedure. This real time data captures the intraoperative supplies, as well as the pick and returns from the sterile processing department (SPD), which is used to update procedure cards.
In the background, the system automates clinical patient charting. When the nurse vends an item or scans an implant serial number in the Pyxis OR point of use (POU) inventory system, the patient chart is populated via the interface with the item manufacturer part number, the hospital proprietary number, the description, expiration date, and serial or lot number. This solution reduces the time and steps required for the nurse to select inventory and manually chart the information. It moves the nurse closer to the patient and away from managing supplies, thereby improving patient care quality and safety.
The background technology is an automated supply chain foundation, with item master, orders interface, implant tracking, and analytics. This level of integration enables the enterprise resource planning (ERP) system, the POU, the ORSOS clinical charting system, and the electronic patient record (EPR) to all talk to one another. UHN has conducted three Lean events to measure the transformation from manual to automated processes. The organization has realized $14M in both hard and soft dollar savings over five years.
According to Wendy Watson, OR Supply Chain Manager at UHN, her organization’s interest in implementing unique device identifiers (UDIs) is driven by its desire to continue enhancing patient safety. She notes that unlike proprietary product identifiers, the UDI device identifier (DI1) is a meaningful number in the patient chart that serves as a “universal language” so that if that patient travels, other healthcare provider organizations will know what products were used in that patient’s treatment. This is particularly important in the case of implantable devices. Although UHN currently captures the UDI production identifier (PI) this is seen as the next step in patient safety.
Watson and her team are in the process of conducting a UDI implementation trial, which involves:
1. Evaluating adoption feasibility from a systems and data perspective within the existing integrated technology framework.
2. Assessing the scalability for all class items, with minimal cost or clinical workflow impacts.
3. Implementing a test set of items in the live environment to identify successes and challenges.
UHN’s group purchasing organization (GPO) maintains a translation table that cross-references the enterprise resource planning (ERP) system item number to an identifier of UHN’s choosing. This gives UHN the ability to use the DI for product identification in the patient’s chart. UHN is currently testing this concept with DIs from a heart valve vendor. The vision would be to phase in the DI for all item class codes with the end goal of capturing every DI used in the patient chart.
“We have contributed to this feasibility study to determine ease of UDI adoption,” said Watson. “We hope that some of the opportunities we have identified will provide visibility to the provider adoption perspective. We are committed to patient safety and see the value in the concept of one universal DI number and language.”
Although Health Canada has not yet announced a UDI adoption date, Watson sees the value of the ONCs Meaningful Use 3requirement that the Common Clinical Data Set (CCDS) include the UDI, and CMS’ requirement that providers share the CCDS for implantables with one another. The go-live date for both of these requirements currently is January 2018. The long-term benefits include improved global adverse events tracking and recall, more timely real word evidence collection for quality evidence-based sourcing, timely feedback for enhanced performance design, and global access to information about the right item for the patient and provider over time and location. At this time the working groups in Canada have largely focused on assessing adoption at the GPO level. Participation in the U.S. study has provided Watson with shared learnings from U.S. sites, as well as a forum to contribute her findings.
DATE INITIATIVE WAS IMPLEMENTED (MONTH/YEAR): November 2016
CHALLENGES TO IMPLEMENTING A UDI CAPTURE SOLUTION:
UDI access. UHN’s GPO is the very early stages of using the Global Data Synchronization Network (GDSN) to access GS12 Global Trade Item Numbers (GTINs), so to obtain the DI numbers for the implant trial the UHN team searched directly on vendor websites. A quick search identified that not all vendors have their websites populated with UDI information. To conduct the first test case of UDIs within their technology infrastructure (heart valves), Watson secured the product DIs directly from the vendor. Although manufacturers populate their DI records in the FDA’s Global UDI Database (GUDID), Watson explains that when they searched the database the DIs did not match the numbers provided directly from the vendor.
Watson also checked the GDSN for this vendor’s DIs but the information contained within this database did not match what was contained within the GUDID. Furthermore, the GDSN contained only one of the two DIs registered for this vendor’s product.
The GDSN and GUDID are repositories that hospitals can use to access vendor DIs, but in Watson’s experience the information contained within these databases is inconsistent and/or incomplete. Therefore, beyond the study sample size of data, the collection and validation of data for UHN’s 9,000 unique items would require a more strategic method.
Furthermore, in Canada, there is no single source for DIs because the GDSN contains only GS1 GTINs, and the GUDID does not contain complete information for medical devices sold in Canada. One challenge is that a supplier’s target market often determines which country’s database they will populate with their DIs. These “target market DIs” are often based on the regulatory agency that approved the device. For example, a supplier that secured approval for a product from the U.S. FDA would populate the FDA’s GUDID with its DIs, but if Health Canada approved the product then the supplier would not populate the product’s DIs in the GUDID, unless the device was also sold in the U.S. For medical devices that also contain a pharmaceutical element, the supplier’s target market might also be based on the product’s packaging language. For example, Canada is a French and English speaking country so some packaging and DIs may differ for this reason.
Another challenge that Watson and her team have faced during the heart valve trial is the issue of leading zeros. UHN’s ERP system would drop the leading zero in a DI because of an existing interface rule. The hospital IT team and the clinical charting system engineer modified the interface so that it would retain the leading zero and UHN configured all integrated systems (POU, clinical charting system) so that the leading zeros would flow all the way through to the patient chart.
Products featuring multiple barcodes or various barcode formats make it challenging for clinicians to know which barcode to scan. Watson notes that ideally all vendors would label their products with the same barcode format for UDIs and there would not be so much variation in the number of barcodes. In the meantime, to overcome this challenge, Watson’s team has identified to clinicians the correct barcode to scan on a product by marking it with a small red dot sticker.
Multiple Countries of Origin
A major challenge to widespread UDI implementation is the issue of multiple countries of origin for the same product size and description. When Watson and her team secured DIs from their heart valve vendor, they discovered that the same product could have different DIs based on its country of origin. Having multiple DIs for one item based on county of origin prevents clinical system adoption, as the exact product DI used must be documented in the patient record. The integrated clinical systems’ item master and workflow require one DI per unit of measure be associated to one unique item.
“Using the device identifier in the place of the ERP system item number is a challenge at this point in time because of the multiple countries of origin, manufacturers using the DI as part of their inventory control processes, and other factors that we are currently uncovering as we proceed down the path to adoption,” said Watson. “It is an issue that requires further discussion among the FDA, hospitals and the vendor community to allow for easy adoption. This working group with AHRMM and the FDA, as a participating member, is a great opportunity to address these early bumps in the road that UHN and other hospitals have encountered.”
System Implementation Workload
UHN’s GPO can only associate one item number to a description in the cross-reference table. When the new item is sent across the interface, it must be immediately set up in the downstream systems so that orders do not fail. The POU and clinical charting systems both require that the new DI numbers be flagged for class code, and lot, serial and expiration capture. The items then have to be physically unloaded and reloaded in POU stations with the new DI, and the lot and serial barcodes must be scanned in and associated to the new DI.
Because of this challenge, Watson said UHN will need to take a “slow-phased in” approach to using DIs in place of the hospital proprietary numbers. She notes how collaboration between UHN and its GPO is necessary to understand the downstream system implementation workload. To ensure a smooth transition, they will need to work together to changeover small batches of items at a time. This will also ensure additional full time employees (FTEs) are not required for implementation, and all orders will flow through the interface so that patient safety is not compromised.
Cross Discipline Internal and External Teams, including:
- OR Supply Chain Manager and Site Supervisors
- Surgical Information Site Specialists
- Shared Information Management Services (SIMS) IT Engineer
- Group Purchasing Organization (GPO) or Operating Room Data Analyst
- Data Governance and Management
- BD Carefusion Pyxis Engineers
- ERP System IT Analyst
- McKesson ORSOS Technical Advisor
Watson and her team are working to leverage their existing technology infrastructure to facilitate the capture of DIs. The goal is to replace the hospital’s ERP system item numbers with the manufacturers’ DIs. The DI would flow through all of the integrated systems so that, at the point of care, the POU system would send the DIs for all products used in the procedure to the clinical charting system for documentation in the patient’s chart.
Within the existing infrastructure, all items Class I, II and III are captured in the patient’s chart as they are managed through the POU system. This also triggers product replenishment through the interface with the ERP system. As ERP system ID numbers are replaced with DIs, this information could be used in the requisitioning/replenishment process with vendors as well. Recognizing that DI numbers are also unique to the packaging unit of measure (UOM), this would work for implants that are ordered and used in a UOM of “one”. All other items are used in the OR in a UOM of “each,” however the ordering would need to be converted by the GPO system to the box DI.
TECHNOLOGY USED OR IMPLEMENTED AS A RESULT OF THIS INITIATIVE:
- SAP enterprise resource planning (ERP) system
- BD CareFusion OR Pyxis Supply Line system
- McKesson ORSOS clinical charting system
- Existing infrastructure, roles and processes are in place and easy to build on
- Strong teamwork, commitment to patient safety
- High functioning team – quick delivery with minimal meeting time and no project leadership or executive escalation required
Watson and her team believe it would be best to implement a phased approach to DI adoption, starting with those vendors that have correctly associated one DI to one product /unit of measure (not using country of origin) and that are accurately populating this data in the GDSN and GUDID repositories.
Watson says, “We are hopeful our findings can be reviewed with FDA and the vendor community to help hospitals with this important initiative for easy adoption.”
“We will continue our work to embrace adoption with the goal of improving patient safety,” said Watson. “We look forward to engaging with the FDA and other members of the Learning UDI Community on our findings to date so that we can all work collaboratively to ease UDI adoption throughout the industry.”
1 An FDA-accredited issuing agency (IA) is an organization that operates a system for assignment of UDIs according to the UDI Rule. FDA has accredited three issuing agencies – GS1, HIBCC and ICCBBA.
2 Each issuing agency has an alternative name (aka) for the DI of UDI. The aka name used by each issuing agency is listed below:
- GS1 - Global Trade Identification Number (GTIN)
- HIBCC - Universal Product Number (UPN)
- ICCBBA – Processor Product Identification Code (PPIC)