Advancing Patient Safety Surrounding Medical Devices: Barriers, Strategies, and Next Steps in Health System Implementation of Unique Device Identifiers
Received 1 March 2022
Accepted for publication 9 June 2022
Published 21 June 2022 Volume 2022:15 Pages 177—186
Checked for plagiarism Yes
Review by Single anonymous peer review
Peer reviewer comments 2
Editor who approved publication: Dr Scott Fraser
Natalia A Wilson,1 James E Tcheng,2 Jove Graham,3 Joseph P Drozda Jr4
1College of Health Solutions, Arizona State University, Phoenix, AZ, USA; 2Department of Medicine, Duke University School of Medicine, Durham, NC, USA; 3Center for Pharmacy Innovation and Outcomes, Geisinger, Danville, PA, USA; 4Mercy Research, Mercy, Chesterfield, MO, USA
Correspondence: Natalia A Wilson, College of Health Solutions, Arizona State University, Phoenix, AZ, USA, Email [email protected]
Background: The requirement for medical device manufacturers to label their devices with a unique device identifier (UDI) was formalized by the 2013 US Food and Drug Administration Unique Device Identification System Rule. However, parallel regulatory requirement for US health systems to use UDIs, particularly the electronic documentation of UDIs during patient care is lacking. Despite the lack of regulation, some health systems have implemented and are using UDIs. To assess the current state, we studied representative health system UDI implementation experiences, including barriers and the strategies to overcome them, and identified next steps to advance UDI adoption.
Methods: Semi-structured interviews were performed with health system personnel involved in UDI implementation in their cardiac catheterization labs or operating rooms. Interviews were transcribed and analyzed using the framework methodology of Ritchie and Spencer. An expert panel evaluated findings and informed barriers, strategies, and next steps.
Results: Twenty-four interviews at ten health systems were performed. Identified barriers were internal (lack of organizational support, information technology gaps, clinical resistance) and external (information technology vendor resistance, limitations in manufacturer support, gaps in reference data, lack of an overall UDI system). Identified strategies included relationship building, education, engagement, and communication. Next steps to advance UDI adoption focus on education, research, support, and policy.
Conclusions and Implications: Delineation of UDI implementation barriers and strategies provides guidance and support for health systems to adopt the UDI standard and electronically document UDIs during clinical care. Next steps illuminate critical areas for attention to advance UDI adoption and achieve a comprehensive UDI system in health care to strengthen patient care and safety.
Keywords: unique device identifier, FDA, implementation barriers, implementation strategies, information technology systems, device manufacturer responsibilities
There is currently no requirement for US health systems to use the medical device unique device identifier (UDI) in the processes of patient care. In 2013, the US Food and Drug Administration’s (FDA) Unique Device Identification System Rule regulated the critical first step towards UDI adoption, specifying requirements for manufacturer labeling of medical devices with a UDI.1 A UDI includes a device identifier (DI) that identifies manufacturer and model of the device and a production identifier (PI) that identifies lot number, serial number, expiration data, and/or date of manufacture, as available for a device. UDIs must be on the label and packaging of a medical device in a format that can be electronically captured, such as a barcode, as well as human readable.1,2 As a result of this rule, the vast majority of moderate- and high-risk devices and implantable devices are now labelled with a UDI. Lower risk devices increasingly are being labeled with UDIs.3
The FDA’s UDI Rule delineated multiple public health objectives that a UDI system could serve: reduction of medical error, simplification of the integration of device information into health information technology (IT) systems, more rapid identification of devices with adverse events and development of solutions, more efficient recalls, better safety communication, strengthening of patient and provider information on devices implanted in patients, and support of more effective safety surveillance and postmarket studies.1 However, the FDA does not have the authority to require health systems to electronically document UDIs in the patient care setting. Without this requirement UDIs are not available for broad use to identify, track, report on, study and comparatively evaluate medical devices, and fulfill these important public health objectives.
Despite the lack of requirement, some health systems have moved forward on their own to implement UDIs based on their internal projections of return on investment, clinical value, and safety benefits for their patients and health systems. Through internal UDI initiatives they have developed the necessary IT infrastructure and requisite dataflow and workflow processes.4–7 These health systems have particularly discerned the value of having standardized medical device information in their IT systems to support safety and quality surrounding medical device use in patients, to accurately and efficiently manage recalls and device inventory, to augment data availability for device evaluations, and to prepare for future requirements to electronically transmit UDIs.4–8
The aim of this study was to understand the experiences of health systems that had implemented UDIs at the point of care (POC) in order to provide practical information and recommendations for other health systems, build on prior work,5,6,9–11 and advance the field. This report adds to the literature the first collation of experiences across health systems regarding barriers to UDI implementation and use and strategies utilized to address these barriers. The intent of this innovation was to assess and report on commonalities across health system sites, rather than solely on a single health system experience, in order to inform UDI implementation and use. In a prior report, a roadmap for UDI implementation based on these health systems’ leading practices was presented.4 In support of further advancement, this report focuses on barriers, the strategies to overcome them, and next steps to advance UDI adoption in health systems.
Setting and Study Oversight
This project was overseen at Arizona State University and was part of a larger initiative, Building UDI into Longitudinal Data for Medical Device Evaluation (BUILD).12 BUILD was overseen by Mercy and involved investigators from Mercy, Geisinger, Intermountain Healthcare, Duke University Health System, and Arizona State University.
The methodology for data collection has been previously reported.4 Briefly, semi-structured interviews of personnel in health systems that had implemented UDI for implantable devices in cardiac catheterization labs or operating rooms were conducted between June and November of 2018. Qualitative methodology was utilized in order to delve more deeply with interview participants into their experiences. Selection of the health systems was guided by the advisory group for the project, the BUILD Consortium.13 A purposeful sampling approach was utilized so that participants were able to inform the research aim. A contact at each health system identified potential interviewees well-versed in UDI implementation from supply chain management, IT, and the POC. Prior to interviews each health system completed a pre-interview survey (Qualtrics, Provo, UT) to ascertain health system demographics and basic UDI information. Interviewees were orally consented prior to interviews conducted by telephone. Interview topics included reasons for UDI implementation, necessary support and infrastructure, barriers, uses of UDI, and current state in the health system. Interviews were recorded and transcribed. Data were stored on a secure server.
The methodology for data analysis has been previously reported.4 Briefly, survey responses were aggregated using Microsoft Excel. Transcript analysis was guided by the framework methodology of Ritchie and Spencer: familiarization, identifying a thematic framework, indexing, charting, and mapping and interpretations.14–16 Transcripts were reviewed, coded, and an analytic framework was applied to the transcripts. Ten percent of the transcripts were coded by two members of the team and coding was compared to verify agreement. Coded data were reduced by charting into an Excel spreadsheet. Interpretation involved review of charted data to ascertain themes across health systems.
Project results, including barriers, were presented and discussed in detail at an expert panel meeting in April 2019, attended by BUILD Consortium13 and research team members. The iterative work of the expert panel informed the previously published implementation roadmap4 as well as the barriers and the strategies to overcome them. Next steps to advance UDI adoption in health systems were formulated. Further detail has been previously reported.4
The study protocol was approved by the Office of Research Integrity and Assurance at Arizona State University.
Twenty-four semi-structured interviews were conducted in ten health systems. Most participating health systems were non-governmental, not-for-profit, included an academic medical center, and incorporated a health care plan. Diversity of geographic location, health system size, and revenue was captured. All health systems were documenting UDIs in health IT systems, the majority by barcode scanning. Interviewees held executive level, director, manager, and clinical positions. Most had more than one focus area (clinical, supply chain management, IT, operational) along with UDI involvement. More extensive demographics of participating health systems have been previously reported.4
Barriers in UDI implementation are represented in Table 1.
Table 1 Barriers in Implementation of Unique Device Identifiers
Internal barriers refer to those within the health systems.
Lack of Organizational Support: Health system personnel engaged in UDI implementation work often felt a lack of organizational support. They discussed a lack of acknowledgement by supervisors and leadership of the time needed to do the necessary work and to address setbacks and make readjustments. As many interviewees stated, UDI work was generally being done in addition to one’s “day job,” as opposed to a carve out of designated time. In addition, they perceived a lack of prioritization for the necessary resources. An interviewee shared the “struggle of keeping the story alive.”
Information Technology Gaps: Internal IT gaps fell into two main areas: interoperability and variability in IT systems. Health systems faced challenges with closed loop IT systems that were designed to accept but not transfer data. IT systems within health systems and within individual hospitals also had significant variability. Structures and formats of IT systems at the POC could be difficult for clinical staff to efficiently utilize within workflows. An interviewee shared, “No one really has an out-of-the-box [IT] solution … ”.
Clinical Resistance: Clinical challenges were quite common. Staff resisted change and questioned the purpose of introducing a new process into their workflow. They also experienced confusion and frustration with barcode scanning which added to their resistance. Some medical device labels contained multiple barcodes making it unclear what to scan. Some barcode scans were unsuccessful. Some devices, such as sterilized implants (eg, orthopedic screws) could not be scanned. An interviewee shared that staff are facing “scan fatigue.” UDI implementation tended to roll out in increments so barcode scanning of UDIs may only be in certain POC sites or for certain devices. The latter became a problem for staff that rotated between clinical sites and faced inconsistency in the need to scan. An interviewee shared, “When nurses were told [they] could not scan everything …, [their response was], What good is this to me? and they just walked out of the room.”
External barriers refer to those generated by stakeholders outside of the health system.
Information Technology Vendor Resistance: This resistance fell into two main areas: resistance to providing needed IT changes to support UDI implementation and lack of ownership of the IT vendor role and responsibility to advance an overall UDI system. Significant time was required by health system personnel to discuss needed changes with their IT vendors, solutions were slow and often costly, and when solutions were made available, they focused on one health system’s individual needs rather than broad solutions that would benefit many health systems facing the same issues. An interviewee shared,
… we are working with three different [IT] systems … they [vendors] should be doing changes … because everyone in the marketplace needs it … Whoever uses their system needs this.
Limitations in Manufacturer Support: These limitations fell into three main areas: labelling, collaboration, and lack of ownership of the manufacturer role and responsibility to advance an overall UDI system. A gap existed between the labelling by manufacturers and ease of UDI capture at the POC. Labels often contained multiple barcodes, in different formats, and in different locations. Multiple interviewees shared the problem of multiple barcodes. The perception of many interviewees was that manufacturers were “checking the box” to comply with regulation rather than considering the actual scanning done by staff and use of UDIs in health systems. Ascertaining who to talk to about these concerns was difficult and even when a health system was able to work with a manufacturer, approaches and solutions to problems were often individual rather than broad to benefit many health systems facing the same issues. An interviewee shared, “I don’t know that the suppliers understand or appreciate necessarily how the provider side is going to use this data going forward.”
Gaps in the FDA Global Unique Device Identification Database (GUDID): GUDID data were found to have errors and inconsistencies, limitations in depth/breadth of discrete data, and to lack full validation. An interviewee shared, “The GUDID database is not … a good, effective working system … for hospitals.” Another shared, “Do we see some limitations? Yes we do. I don’t think there is always a 100% clear match in the information, but we do find it useful.”
Lack of an Overall UDI System: Policy to drive a comprehensive UDI system was felt to be slow and fragmented. UDI implementation in health systems is not a requirement which impacted priority of UDI initiatives. Robust data to support return on investment for health systems, operationally and clinically, was felt to be lacking. Who is “in charge” of the broader UDI system across health care was perceived as unclear. An interviewee shared,
[The supply chain director] said there were going to be some policy drivers that were going to be placed on device manufacturing companies to standardize the barcodes … but she didn’t say that there would be any implications or any sort of fine or penalty to a hospital who chose not to adopt barcode scanning for the UDI items.
Strategies utilized by health systems to address barriers in UDI implementation are presented in Table 2.
Table 2 Strategies to Address Barriers in Implementation of Unique Device Identifiers
Lack of Organizational Support: Strategies shared were developing relationships and providing information on UDI to build awareness, particularly with leadership and clinicians. Additional strategies included communication of the purposes underlying UDI implementation and of the needed resources. An interviewee shared the importance of “selling small wins to build bigger successes.”
Information Technology Gaps: Early engagement of IT vendors was shared as a needed strategy. Leader–leader relationships were touted as important as well as evaluation of third-party vendors who were generally felt to be more responsive, willing to be innovative, and work towards solutions. As an interviewee shared,
[We have] done a really good job at establishing leadership connections with the software vendors, and [this] has given us the ability to influence their development, future development …
Clinical Resistance: Relationship building, engagement of clinicians in work teams, education, and communication were shared strategies. Clinical staff needed to know why UDI scanning was being done, what to scan so they needed training on barcodes, and who to contact for problems. The latter team members needed to be easily accessible and quickly responsive. A take-home message was that the process needed to work well with quick support. Without those elements, clinical staff members were reticent to change to a UDI-based workflow and may not do it. An interviewee shared, “We developed for ourselves a mobile app … that allows them [clinical staff] to self-report a scanning issue.”
Information Technology Vendor Resistance: Early engagement and leader–leader relationships were shared strategies. Health systems evaluated third-party vendors who were felt to be more responsive and willing to innovate as well as creating or engaging an established internal IT team. In some cases, provisions were made that IT vendors would only receive data in their systems if they also transferred data. An interviewee shared, “We had to go into development with an [IT] company to deal with and deliver on our vision. There was not a company out there. I had to go on 20 site visits.”
GUDID Gaps: Strategies to address this issue were documentation of problems, good communication with the FDA on issues, and engagement internally and externally including in multi-stakeholder workgroups (eg, AHRMM Learning UDI Community) to work towards solutions. An interviewee shared,
… we’re just trying to validate the information that’s in the GUDID database. We’ve asked several of our different manufacturers and vendors that we deal with to get us the information for all the products that we purchase from them and – understand does the GUDID database have everything we’re looking for …
If it doesn’t, where do we go? … we reach back out to FDA and say, hey, this information is not what we’re looking for. It doesn’t have everything we need …
Manufacturer Support: Relationship building, communication, and engagement in multi-stakeholder workgroups (eg, AHRMM Learning UDI Community) were shared as strategies to work towards solutions. In addition, some health systems included contract provisions requiring complete UDIs on purchased devices that could successfully be scanned at the POC and updates on any UDI transitions or changes. An interviewee shared,
There’s nothing in the [UDI] regulation that says, gosh, you gotta implement this efficiently or effectively … We’ve really tried to have a focused effort. Look, you [manufacturers] need to care about this. Your end user, the ones that you’re representing, the clinicians care about this … We’ve really tried to develop it as a partnership.
Another shared: “We now require [that] when the contracts are signed, the suppliers supply us with the barcodes.”
Lack of an Overall UDI System: Health system personnel developed cross-disciplinary relationships, educated themselves about UDI through conferences and articles, and engaged in multi-stakeholder workgroups. They became involved in policy efforts and in some cases in research projects focused on health system UDI implementation and use. An interviewee shared, “We’ve advocated for the DI on the claim.” Another shared, “When the [research] project came along, my team was involved in installing the barcode scanners in … the ORs.”
Needed next steps to address barriers to UDI implementation are represented in Table 3.
Table 3 Needed Next Steps to Address Barriers in Implementation of Unique Device Identifiers
Interviewees shared some important overriding insights:
When you think of retail … they’ve redesigned an entire industry based on using data standards.
[UDI] is an enabler … most people think of it more like a utility. It’s electricity or it’s water. It’s the heating and air conditioning. It’s something that should be there that enables everything else.
The goal was not UDI in isolation, but it was incorporating UDI into a bigger picture of something that was trying to make the care, in an innovative way, more efficient, safer, cost-saving.
By creating this national database with all of these items that are being used, we’re creating and enhancing our existing relationships with FDA for post-market surveillance and patient safety and better recall management. The ROI seems obvious to me.
“Other institutions … become leaders and champions for each other.”
A foundation of evidence and tools for UDI implementation in health systems is being built,4–9,17 despite the gap in current policy requiring health systems to incorporate UDIs in processes of care. UDI implementation in health systems, similar to health IT implementations in general, can be complex due to the significant work required to build the IT infrastructure, the need for interoperability across multiple systems, clinical and administrative resistance to change, and the requisite resources including operational support and funding.4–7,10,18–20 However, health systems that are “early adopters” of UDI implementation have paved the path with tools and information for others, including an implementation roadmap and individual health system cases studies.4–9,17 By tapping into “early adopter” health systems and UDI leaders, this project was able to illuminate common barriers, strategies to overcome them, and needed next steps for advancement of UDI adoption in health systems.
The UDI has a critical role supporting patient safety and quality of care. A documented UDI supports clinician ability to identify a failed device prior to a revision procedure, thus supporting clinical decision-making and preparedness.21,22 Patients’ access to the UDIs of their implanted devices supports patient engagement in their care and safety, particularly in the case of devices that fail or are recalled.23 UDI use by health systems in management of recalled devices supports accuracy and efficiency to remove these devices and find patients that are affected.5,24,25 As a result of the COVID-19 pandemic and supply disruptions impacting patient care, UDI adoption has been recommended to strengthen the health care supply chain.26
The public health objectives of the FDA UDI Rule highlight the role of UDIs in improved adverse event reporting, recall management, safety communication, and more effective postmarket safety surveillance and evaluations.1 The focus on generation of real-world evidence (RWE) for medical devices27–30 and work utilizing UDIs in RWE studies highlights the centrality of UDI for device identification and linkage of real-world data.31–35 The critical step to achieve these goals is UDI adoption in the processes of patient care.
Health systems in the project faced both internal and external barriers, yet commonalities existed in addressing them. Relationship building, relationships between the right level of leadership, and overall engagement of involved people, internal or external, were critical in addressing challenges. Education to advance awareness of what UDI is, why it matters, and how it can be used enhanced responsiveness, support, and involvement. Engagement in multi-stakeholder workgroups17 helped delineate the impact of challenges on different stakeholders and fostered collaboration to address problems. In addition, engagement in multi-stakeholder workgroups, research and/or policy advocacy helped deepen involvement in collective work for change and movement forward.
Building the IT infrastructure was an area that particularly faced challenges, with both internal and external barriers. As a starting point, the concept of using the UDI as the “single source of truth” across all IT systems and processes remains a difficult goal to coordinate and accomplish.7 Issues of interoperability, diverse IT systems within and between health systems, and vendor resistance complicated work. The result was that in different health systems, different IT systems were interfaced, and different IT systems were accepting UDIs at the POC and transmitting them;4 there was complexity in developing the necessary IT infrastructure; and there was a lack of generalizability from one health system to another. In some cases, to address challenges with IT vendors health systems defaulted to contract provisions or transitioned to third-party vendors to get what they needed to advance UDI implementation. Despite the challenges and differences in IT systems, the ultimate goal for health systems were interfaced IT systems that could store and transmit UDIs.4 Dedicated effort to set interoperability and data standards for UDI-related data would likely help accelerate adoption at the individual health system level, so the mix and match of IT systems would become less problematic.
Salient next step recommendations were made for advancement of UDI adoption:
- Education: Advance education through development of durable materials that can be easily accessed and utilized broadly in presentation to health system leaders, clinicians, clinical staff, and other stakeholders.
- Research: Conduct further research including workflow analysis, assessment of IT infrastructure, health system use of the FDA GUDID, vendor relationships, and outcomes.
- Support: Develop supporting measures for UDI implementation including staff barcode training, an IT system functionality catalog, standard contract provisions for external vendors, job description for a UDI initiative leader, and metrics.
- Policy: Collaboratively work to address policy needs and drivers.
Study Limitations have been previously reported.4 Our sample size was small which may limit generalizability. Not all recommended health systems participated in the project; however, a high percentage of those advanced enough in UDI implementation to study did participate. Some potential interviewees that met the desired criteria may not have been recommended, but 24 interviews in 10 health systems were conducted. UDI implementation in the inpatient arena and for cardiovascular procedures had greater representation although other areas and procedures were represented.
Evidence generation has been advancing and contributing to the foundation for UDI adoption in health systems. The delineation of barriers and strategies to overcome them, along with the UDI implementation roadmap,4 support health systems’ ability to develop and operationalize a UDI system to support patient safety and quality of care surrounding medical devices. Next steps lay out four critical areas for attention: education, further research, development of supporting measures, and policy. Effort in these critical arenas should pay high dividends in advancing UDI at scale to realize the public health objectives of the FDA UDI Rule of 2013 and goals for RWE generation for medical devices. Improved device safety and effectiveness for patients depend on it.
This project would not have been possible without significant multi-stakeholder work and support. We thank the BUILD Consortium members for their engagement and support of the project: Dennis Black, Becton, Dickinson and Company; Kevin Capatch, M.S., Geisinger; Jeff Dressler, MBA, Abbott Laboratories; Curtis Dudley, Mercy; Jo Carol Hiatt, M.D. MBA, previously Kaiser Permanente; Theodore Heise, Ph.D., RAC, MED Institute; Kay Hysell, Mayo Clinic; Tom Maughan, DePuySynthes; Bart Phillips, M.S., Medtronic; Terrie Reed, M.S., previously US FDA; Angela Silvestri, RAC, Stryker; Cynthia Shumway, Intermountain Healthcare; Brad Steger, Zimmer Biomet; Paul Varosy, M.D., FACC, FAHA, FHRS, Department of Veterans Affairs Eastern Colorado Health Care System; Kirk Wiedmeier, previously Duke University Health System (Ended involvement before project end: Lesley Kelly Hall, previously Healthwise; Michael Schiller, CMRP, AHRMM). We thank Melina Cox-Ferrera, M.S. and Lara Salvo, M.S. for their project support.
This work was supported by HHS-FDA 1U01FD005476-01 REVISED, 02 REVISED, and 03 as well as grants from Johnson & Johnson and Medtronic, Inc. The funds were received by Mercy.
Natalia A Wilson reports Advisory Committee involvement in the AIM North America UDI Advisory Committee, Association for Health Care Resource & Materials Management Learning UDI Community Steering Committee; Consulting for Arizona State University’s Center for Healthcare Delivery and Policy, Mass General Brigham; Research funding from the National Evaluation System for health Technology Coordinating Center, Patient-Centered Outcomes Research Institute; Purchased stock options in Vitreos Health. James E Tcheng reports being on the Board of Directors of the Regenstrief Foundation, Member of the HL7 Advisory Council, Co-chair of the HL7 Clinical Interoperability Council, Consultant for Lumedx. Jove Graham reports Research funding from Astra Zeneca, Medtronic Inc., Purdue Pharma LP, Patient-Centered Outcomes Research Institute, Pfizer Inc. The authors report no other conflicts of interest in this work.
1. Food and Drug Administration, HHS. Unique device identification system. Fed Regist. 2013;78:58785–58828.
2. U.S. Food and Drug Administration. UDI Basics; 2019. Available from: https://www.fda.gov/medical-devices/unique-device-identification-system-udi-system/udi-basics.
3. U.S. Food and Drug Administration. Compliance dates for UDI requirements; 2020. Available from: https://www.fda.gov/medical-devices/unique-device-identification-system-udi-system/compliance-dates-udi-requirements.
4. Wilson NA, Tcheng JE, Graham J, Drozda JP
5. Drozda JP, Dudley C, Helmering P, Roach J, Hutchison L. The mercy unique device identifier demonstration project: implementing point of use product identification in the cardiac catheterization laboratories of a regional health system. Healthc. 2015;4(2):116–119. doi:10.1016/j.hjdsi.2015.07.002
6. Drozda JP Jr, Roach J, Forsyth T, Helmering P, Dummitt B, Tcheng JE. Constructing the informatics and information technology foundations of a medical device evaluation system: a report from the FDA unique device identifier demonstration. J Am Med Inform Assoc. 2018;25(2):111–120. doi:10.1093/jamia/ocx041
7. Tcheng JE, Nguyen MV, Brann HW, et al. The medical device unique device identifier as the single source of truth in healthcare enterprises – roadmap for implementation of the clinically integrated supply chain. Med Devices. 2021;14:459–467. doi:10.2147/MDER.S344132
8. Krupka DC, Graham J, Wilson NA, et al. Transmitting device identifiers of implants from the point of care to insurance claims: a demonstration project. J Patient Saf. 2021;17(3):223–230. doi:10.1097/PTS.0000000000000828
9. Engelberg Center for Health Care Reform. The Brookings institution. Unique Device Identifiers (UDIs): a roadmap for effective implementation; 2014. Available from: https://www.brookings.edu/wp-content/uploads/2016/06/UDI-Final-12052014-1.pdf.
10. Campion TR, Johnson SB, Paxton EW, Mushlin AI, Sedrakyan A. Implementing unique device identification in electronic health record systems. organizational, workflow, and technological challenges. Med Care. 2014;52(1):26–31. doi:10.1097/MLR.0000000000000012
11. The Pew Charitable Trusts. Implementing unique device identification. recommendations for integrating medical device data throughout the health care system; 2015. Available from: https://www.pewtrusts.org/-/media/assets/2015/09/udiimplementation-report.pdf.
13. BUILD consortium member biographies. Available from: http://mdepinet.org/wp-content/uploads/June-2019-BUILD-Consortium-Member-Biographies-2-1.pdf.
14. Ritchie J, Spencer L. Qualitative data analysis for applied policy research. In: Huberman AMMM, editor. The Qualitative Researcher’s Companion. Thousands Oaks: Sage; 2002:305–329.
15. Srivastava A, Thomson SB. Framework analysis: a qualitative methodology for applied policy research. Joaag. 2009;4(2):72–79.
16. Gale NK, Heath G, Cameron E, Rashid S, Redwood S. Using the framework method for the analysis of qualitative data in multi-disciplinary health research. BMC Med Res Methodol. 2013;13:117. doi:10.1186/1471-2288-13-117
17. AHRMM. Learning UDI community. Available from: https://www.ahrmm.org/resources/learning-udi-community.
18. Kruse CS, Kristof C, Jones B, Mitchell E, Martinez A. Barriers to electronic health record adoption: a systematic literature review. J Med Syst. 2016;40:252. doi:10.1007/s10916-016-0628-9
19. Adler-Milstein J, DesRoches CM, Kralovec P, et al. Electronic health record adoption in us hospitals: progress continues, but challenges persist. Health Aff. 2015;34(12):2174–2180. doi:10.1377/hlthaff.2015.0992
20. Ross J, Stevenson F, Lau R, Murray E. Factors that influence the implementation of e-health: a systematic review of systematic reviews (an update). Implement Sci. 2016;11(1):146. doi:10.1186/s13012-016-0510-7
21. Aston JW, Howarth AL, Wilson NA, Mahabir RC. The value of unique identifiers in plastic surgery. Aesthet Surg J. 2018;38(11):1264–1266. doi:10.1093/asj/sjy210
22. Wilson NA, Broatch J, Jehn M, Davis CM. National projections of time, cost and failure in implantable device identification: consideration of unique device identification use. Healthc. 2015;3(4):196–201. doi:10.1016/j.hjdsi.2015.04.003
23. Wilson NA, Reich AJ, Graham J, Bhatt DL, Nguyen LL, Weissman JS. Patient perspectives on the need for implanted device information: implications for a post-procedural communication framework. Health Expect. 2021;00:1–12. doi:10.1111/hex.13273
24. Kinard M, McGiffert L. Medical device tracking – how it is and how it should be. JAMA Intern Med. 2021;181(3):305–306. doi:10.1001/jamainternmed.2020.7797
25. The Association for Health Care Resource & Materials Management (AHRMM) of the American Hospital Association. Unique Device Identifier (UDI) impacts on recall management. Available from: https://www.ahrmm.org/system/files/media/file/2021/09/UDI-DI-Recall-Impact-Report.pdf.
27. Sherman RE, Anderson SA, Dal Pan GJ, et al. Real-world evidence - what is it and what can it tell us?. N Engl J Med. 2016;375(23):2293–2297. doi:10.1056/NEJMsb1609216
28. U.S. Food and Drug Administration. Real-world evidence; 2022. Available from: https://www.fda.gov/science-research/science-and-research-special-topics/real-world-evidence.
29. U.S. Food and Drug Administration. National Evaluation System for health Technology (NEST); 2019. Available from: https://www.fda.gov/about-fda/cdrh-reports/national-evaluation-system-health-technology-nest.
31. Drozda JP Jr, Graham J, Muhlestein JB, et al. Multi-institutional distributed data networks for real-world evidence about medical devices: building unique device identifiers into longitudinal data (BUILD). JAMIA Open; 2022;5(2):1–11. https://doi.org/10.1093/jamiaopen/ooac035.
32. Timble JW, Concannon TW, Kim AY, Baker L, Gahlon G, Li R. Using real-world evidence to support regulatory decisionmaking for medical devices. interim report on lessons from the national evaluation system for health technology coordinating center (NESTcc) test-cases. RAND Corporation; 2021. Available from: https://nestcc.org/independent-assessment-of-The-nestcc-test-cases-rand-interim-report/.
33. Drozda J, Zeringue A, Dummit B, Yount B, Resnic F. How real-world evidence can really deliver: a case study of data source development and use. BMJ Surg Interv Health Technologies. 2020;2:e000024. doi:10.1136/bmjsit-2019-000024
34. Jiang G, Dhruva SS, Chen J, et al. Feasibility of capturing real-world data from health information technology systems at multiple centers to assess cardiac ablation device outcomes: a fit-for-purpose informatics analysis report. JAMIA. 2021;28(10):2241–2250. doi:10.1093/jamia/ocab117
35. NEST Coordinating Center. NEST collaborative community/device identification and real-world data. Available from: https://nestcc.org/events/collaborative-community-meeting-2021/.
© 2022 The Author(s). This work is published and licensed by Dove Medical Press Limited. The full terms of this license are available at https://www.dovepress.com/terms.php and incorporate the Creative Commons Attribution - Non Commercial (unported, v3.0) License. By accessing the work you hereby accept the Terms. Non-commercial uses of the work are permitted without any further permission from Dove Medical Press Limited, provided the work is properly attributed. For permission for commercial use of this work, please see paragraphs 4.2 and 5 of our Terms.