Standardized numeric or alphanumeric code for medical devices that enables adequate identification and traceability of medical devices used in healthcare settings (including inpatient, outpatient, and home health care) or implanted in patients. This code generally consists of the Device Identifier (DI) and one or more Production Identifiers (PI).
Usage notes (optional)
Availability of UDI in human readable and machine readable/Automatic Identification and Data Capture (AIDC) technologies (e.g., barcodes, 2D Matrix, RFID, etc.) on device labels and packages facilitates multiple ways to capture UDI information in electronic health record at the point of care. UDI can be scanned and data can be parsed via APIs available on AccessGUDID and OpenFDA, the two GUDID public portals.
Applicable standard (if applicable)
FDA's Unique Device Identification System final rule (https://www.federalregister.gov/documents/2013/09/24/2013-23059/unique-device-identification-system)
Rationale for Separate Consideration
Proposed Data Element Description: Standardized numeric or alphanumeric code for medical devices that enables adequate identification and traceability of medical devices used in healthcare settings (including inpatient, outpatient, and home health care) or implanted in patients. This code generally consists of the Device Identifier (DI) and one or more Production Identifiers (PI).
Usage notes (optional)
Availability of UDI in human readable and machine readable/Automatic Identification and Data Capture (AIDC) technologies (e.g., barcodes, 2D Matrix, RFID, etc.) on device labels and packages facilitates multiple ways to capture UDI information in electronic health record at the point of care. UDI can be scanned and data can be parsed via APIs available on AccessGUDID and OpenFDA, the two GUDID public portals.
Applicable standard (if applicable)
FDA's Unique Device Identification System final rule (https://www.federalregister.gov/documents/2013/09/24/2013-23059/unique-device-identification-system)
We propose that the current “Unique Device Identifier – Implantable” be replaced by a broader “Unique Device Identifier” element that incorporates all medical devices subject to the FDA UDI Rule. This will also remove the need to include the data elements proposed in Level 2, Test Kit Unique Identifier, and Level 1, Instrument Unique Identifier from the Laboratory Data Class. Both of these would fall under the “Unique Device Identifier” data element in the Medical Device Class.
Use Case Description(s)
Use Case Description
The main use case is for patient safety and the ability to reliably identify medical devices that have been used by patients, used for patient care, or implanted in the patient during a healthcare encounter regardless of the setting.
Availability of the device identifier in the electronic medical record enables the following improvements in healthcare:
Effective reporting and evaluation of adverse events involving medical devices: electronic recording of UDI at the point of care enables providers to specifically identify the device(s) involved in adverse events, to allow for device specific post market surveillance, such as ability to identify potential safety signals and performance issues. Availability of the UDI in the EHR enables unambiguous linkage of a specific device to patient outcomes for longitudinal evaluation and real-world evidence.
Implementation of device-related recalls: specific device information enables healthcare organizations and manufacturers to efficiently and comprehensively identify relevant patients affected by device recalls and take corrective measures as necessary.
Coordination of care: UDI information can ensure that caregivers in distributed care systems have the device-related information they need to make correct decisions about patient care.
Electronic Source Data: With the increasing use of real-world data (which may originate in health information systems – specifically electronic health records, and associated health records and transactions) it is imperative that the data collected about devices is standardized across the healthcare ecosystem so that it may be used for interoperability. Secondarily, it may be used for real-world world evidence for regulatory decision making.
Interoperable device communication and accurate data interpretation: precise device information in the EHR can enable system developers to implement device-specific communications and allow increasingly prevalent software algorithms and AI/ML models to interpret device-dependent data more effectively when the device source of measurement data is specified.
Accurate and efficient inventory management: availability of the UDI in the EHR enables healthcare organizations to efficiently maintain device inventory
Estimate the breadth of applicability of the use case(s) for this data element
All medical devices to which the UDI rule applies could be applicable to this use case.
The unique device identifier is intended to be the key identification data for all devices used by patients or providers, or implanted in patients in a healthcare or medical context to include but not limited to: identification of reusable devices when they are causing infection in patients (e.g., endoscopes-associated pathogen transmission); identification of recalled devices in healthcare inventory to limit the use of recalled devices during procedures; identification of medical devices implanted in a patient when components need to be replaced (e.g., pacemaker leads, infusion pumps catheters); identification of diagnostic devices used during a procedure or test; and identification of devices when there may be a software defect or interface issue (e.g., point of care devices – infusion pumps, vital signs monitors, ventilators, imaging devices, etc.).
Restrictions on Standardization (e.g. proprietary code)
Not applicable. Standardized unique device identifier information is available for use on device labels and packages and in two public portals of the GUDID, AccessGUDID and OpenFDA.
Restrictions on Use (e.g. licensing, user fees)
Not applicable. No restrictions. There is no licensing requirement or user fees associated with the UDI.
Privacy and Security Concerns
Not applicable.
Estimate of Overall Burden
Given that the UDI for implantable devices is already in USCDI, there is limited additional burden for EHR vendors or SDO to broaden the scope to all devices subject to the UDI rule.
As most medical devices will be accounted for in the patient’s record for billing purposes, it should be straight forward as to the value of capturing the UDI at point of care. This requirement has been in place for the past decade. Efficient capture of the device identifier requires barcode scanning capability to minimize impact on normal clinical workflow. Effective implementation of UDI capture requires coordination between the hospital unit management, technical staff, and device inventory and supply chain management (e.g., Transition was estimated by Duke to require capital cost of less than $20,000 and 500 person-hours for their records).
Other Implementation Challenges
The identification of a medical device could help to improve the reliability of the data being generated in the healthcare setting and used as real-world data.
ASTP Evaluation Details Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1 Maturity - Current Standards
Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2 Maturity - Current Use
Level 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3 Maturity - Current Exchange
Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
Criterion #4 Use Case(s) - Breadth of Applicability
Level 2 - Use cases apply to most care settings or specialties.
Expand the types of devices to apply Unique Device Identification to all devices subject to the Unique Device Identification Rule. This includes the Level 2 concepts of Test Kit Unique Identifier and Level 1 Instrument Unique Identifier that should be available for use in combination (i.e., a test kit may be run on an instrument and not including both would limit the value of the data).
Please consider making the GUID available to ancillary staff in the form of a barcode or QR code for checking against other systems or reconciliation of inventories (Ex an LTC Nurse doing rounds and seeing a pacemaker on the careplan, making sure if the resident goes out to another hospital, that device is listed on their transfer form in case the receiving hospital was not part of the Exchange of original hospital where device was implanted).
The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.
If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.
If you are only commenting on a single data class or element, you may leave this field blank.
2. Select the Data Class
To specify which data class your comment addresses:
In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
Note that the Data Class field will automatically populate based on your current location in the platform:
If you are on a data class page, the field will be set to that specific data class
If you are on a data element page, the corresponding data class will be pre-selected
3. Select the Data Element
To specify which data element your comment addresses:
In the "Data Element" drop-down menu, select the specific data element you want to comment on.
The drop-down menu will display only the elements available under the data class you selected in the previous step.
You can use the search function within the drop-down to quickly locate a specific data element.
If you are commenting on the data class itself rather than a specific element, you may leave this field blank.
Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.
4. Optional: Propose New Data Class or Element
If you cannot find the appropriate data class or element for your comment:
Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.
5. Complete the Comment Form
Fill out the required fields in the comment form:
Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.
Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.
6. Optional: Add Additional Comments
If you need to comment on multiple data classes or elements:
After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
A new comment section will appear, allowing you to enter details for your additional comment.
For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
Complete the Subject and Comment fields for your additional comment.
Repeat this process for each additional comment you wish to submit.
Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.
7. Optional: Upload Supporting Files
The platform allows you to upload supporting documentation to enhance your comment:
Locate the "File Upload" section at the bottom of the comment form.
Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.
Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.
Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.
8. Optional: Save and Exit
If you need to pause your work and return to complete your comment later:
Click the "Save and Exit" button at the bottom of the form.
Your comment will be saved as a draft that you can access and complete later.
When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
Click this button to continue working on your draft.
You will be taken to a review page where you can:
Select "Submit Comment" to officially submit your feedback.
Click "Edit" to return to the comment form and make changes
Select "Discard Draft" to delete the saved draft and start fresh
Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.
9. Review and Submit
Once you have completed your comment:
Click the "Review and Submit" button at the bottom of the form.
This will take you to a review screen displaying your comment(s) in full.
Review all information for accuracy and completeness.
On this review screen, you have three options:
Click "Submit Comment" to officially submit your feedback
Click "Edit" to return to the comment form and make changes
Click "Discard Draft" to delete the comment and start fresh
The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by marti.velezis on
Expand UDI for all Medical Devices
Expand the types of devices to apply Unique Device Identification to all devices subject to the Unique Device Identification Rule. This includes the Level 2 concepts of Test Kit Unique Identifier and Level 1 Instrument Unique Identifier that should be available for use in combination (i.e., a test kit may be run on an instrument and not including both would limit the value of the data).