Stanford Health Care UDI Capture Work Group Case Study
WORK GROUP TITLE:
UDI Capture Work Group
CASE STUDY PARTICIPANTS:
Jim Booker, Manager of Master Data Management, Supply Chain, Stanford Health Care
CASE STUDY ORGANIZATION:
Based in Stanford, Calif., Stanford Health Care is part of Stanford Medicine, a leading academic health system that includes the Stanford University School of Medicine, Stanford Health Care, and Stanford Children’s Health, with Lucile Packard Children's Hospital. Stanford Medicine is renowned for breakthroughs in treating cancer, heart disease, brain disorders, and surgical and medical conditions. Stanford Health Care has 613 licensed beds, 49 operating rooms and over 15,000 staff members and volunteers.
Accurately and efficiently capturing product information at the point of use for patient billing, inventory management, adverse event reporting, and recall management is critical to improving cost, quality, and outcomes in healthcare, but it is no easy task. Today at Stanford Health Care, clinicians use various query tools to manually identify and document items used in a procedure within the organization’s EPIC electronic health record (EHR) system. Because most items do not feature barcodes, clinicians must manually search for them in the EHR system using product descriptions. As a result, there is the distinct possibility that a clinician will document the wrong item in the patient record or miss an item completely, which presents patient safety and financial risks to the organization.
The supply chain team at Stanford Health Care has piloted a project whereby clinicians scan barcodes on product packaging to electronically capture product data standardized on the device identifier (DI1) portion of the UDI in the organization’s EHR system. They have worked with their counterparts in the Stanford information technology (IT) department to integrate the organization's Infor Lawson enterprise resource planning (ERP) system with the EHR system so that product DIs are fed nightly into the EHR. This ensures the supply chain, clinical, and financial departments are all using the same standardized product information for the DI-enumerated items.
DATE INITIATIVE WAS IMPLEMENTED:
July 2016 - November 2016
CHALLENGES TO IMPLEMENTING A UDI CAPTURE SOLUTION:
According to Jim Booker, Manager of Master Data Management, Supply Chain, for Stanford Health Care, the greatest challenge to implementing a unique device identification (UDI) capture solution is gaining access to medical device suppliers’ DIs.
To populate and enhance their item master, Booker and his team have attempted to use the U.S. Food and Drug Administration’s (FDA) AccessGUDID website to find supplier DI information in the FDA’s Global Unique Device Identification Database (GUDID) but have discovered the information they need cannot always be found.
“My biggest challenge is taking the 60k products in my item master, finding DI information for each product’s unit of measure and getting the data into our item master so that when a clinician scans a barcode on a package, the information is correctly interpreted by the EHR system,” said Booker.
Booker and his team have tried finding DIs on individual supplier websites, and contacting suppliers directly to request DIs for the products they use. He said while some suppliers have on their websites specific instructions to providers on how they can request/access their DIs, most do not have this type of resource.
“I’ve found several challenges and barriers to getting consistent data in a format where we can load it into systems without having to go to the package or perform one-off type research,” said Booker. “Suppliers need to make their DI data more available and easier to access in GUDID or data based upon GUDID (e.g. GS12 GDSN, supplier websites) as a source of truth to various populations.”
Another challenge that Booker and his team have faced is storing DIs within their ERP system. He explains how their system has separate subscreens and corresponding databases in which to store each of the issuing agency’s DI portion of UDI, including two databases/subscreens for HIBCC Labeler Identification Codes (LICs), one for the GS1 GTINs, two for Universal Product Codes (UPCs) (UPN 1 and UPN 2), one for National Drug Codes (NDCs), and yet another for stock-keeping units (SKUs). Booker says it is unclear where they need to store HIBCC LICs, and plans to have a conversation with the ERP vendor to discuss this issue.
- Supply chain
The supply chain team at Stanford Health started with a select group of implant-related products already enumerated by the supplier with DIs and for which the packaging features barcodes containing the DI information. System configurations required collaboration between supply chain, and individuals within Stanford’s IT group who support the ERP and EHR systems.
Stanford already had in place a nightly product data feed coming from its ERP system into its EHR, and the EHR system had a pre-configured field for DIs. The IT team created a separate database table to store the DI in its ERP system and an interface to pull the DIs from this table into the EHR system as part of the nightly product data feed.
Stanford’s EHR system features a barcode scanning module so the IT team leveraged this for the DI barcode scanning. They trained clinicians on how to scan the barcodes on product packaging at the point of use to capture DI information into the EHR. If a clinician is closing out a case in the EHR and he/she scans a product barcode and does not find the DI data, he/she can manually look up the product number and get the required information to drop the charge and then manually enter the data into the EHR system.
The results of a pilot where clinicians used barcodes to electronically capture surgical mesh product data standardized on DIs showed automation of this kind reduces the clinician’s time to capture and record the mesh in the EHR from one-to-two minutes, down to just one-to-two seconds. Booker and his team are in the process of documenting other benefits as well, such as improved accuracy in the product capture and billing process. They are also expanding this work to more item-intense implant procedures where they will document the time savings achieved from electronically capturing product information via barcode versus manually finding/recording it.
TECHNOLOGY USED OR IMPLEMENTED AS A RESULT OF THIS INITIATIVE:
- Infor Lawson ERP system
- EPIC EHR system with barcode scanning module
- Data feed configured to pull DIs into EHR as part of nightly data feed from ERP system
- Access to clean, normalized data in a clear, readable format
- Access to data elements required by different stakeholders – those in supply chain need different data attributes than those in clinical areas
- Ability to access supplier DIs through GUDID
- A “UDI starter kit” for healthcare providers that includes instructions on how to access supplier DIs
- A clear understanding of who within a supplier organization a provider needs to contact for questions regarding the company’s DIs and the data in the GUDID
- A correlation between supplier divisions and products, where a division’s GLN aligns with its product GTINs so providers know which divisions produce which products
- Supplier DIs are not readily available or easily accessible
- It is not always possible to find the product data required by supply chain within the AccessGUDID
- Within AccessGUDID, it is a challenge to find DIs for a specific unit of measure (UOM). While clinical staff members need DIs for a product “each,” supply chain needs DIs for all UOM, for example, “case”, “box” and “each”
- In some cases, when suppliers publish data to a GDSN-certified data pool, providers must pay a fee to access it
Booker notes how clinicians have been very receptive to this pilot. He and the team are planning to expand it into the main operating room (OR) area with other DI-enumerated barcoded products as this data becomes available. The ability to exchange this data to support coordination of care would help Stanford Health Care meet meaningful use certification (MU3) requirements.
Furthermore, linking the DI to patient records and including data from GUDID in the EHR would benefit charge capture. Booker and his team are working to demonstrate a return on their investment (ROI) related to this.
“Our decision support team in finance wants to know the actual total cost of a procedure, all the way down to the sponges and sutures being used,” said Booker. “Giving clinicians the ability to scan these products instead of having to translate and enter finite 14-digit numbers for them would go a long way in supporting this.”
Once Stanford has the majority of its medical-surgical products enumerated with DIs, Booker says they would like to expand the use of standardized product data into other functional areas of the organization. He notes how capturing product DIs via barcode scanning in receiving could help Stanford with inventory management, as would using DIs to put unused items back into inventory following a procedure. Manufacturer’s entry of the catalog number within the GUDID would provide significant benefits to providers, creating a crosswalk from the catalog number to the DI.
Additionally, Booker says the use of DIs in electronic data capture (EDI) transactions with distributors and manufacturers would drive greater accuracy and efficiency in the procure-to-pay process and help ensure products are available to clinicians when needed.
“Instead of having all of these different versions of catalog numbers where we send out a PO asking for a case and a manufacturer sends us a box – all of those errors that normally occur with EDI transactions – we can communicate and get exactly what we need,” said Booker. “Once we have all of this data collected we can work on making this a more efficient process.”
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: