Health Authorities in many markets require medical device manufacturers to register Unique Device Identification (UDI) data. While RIM Registrations supports generating submission XML for specific markets, the Export Generic UDI Data action allows users to export the UDI data tracked on a Marketed Device Product Registration in a general Excel format, for transformation, validation, and submission outside of Vault. This allows your organization to keep Vault as the single source of truth for UDI data in every market.

For example, you can use the export file as:

  • A reference when entering data in a Health Authority’s web form.
  • A source file for copying data into a Health Authority’s Excel or CSV template.
  • Input for a third-party solution that transforms (for example, to XML or JSON), validates, and/or transmits the data.

Exporting UDI Data

To export general UDI data:

  1. Navigate to a Registration record with a Registration Type field value of Marketed Device Product Registration.
  2. In the Registration record’s Actions menu, select Export Generic UDI Data.
  3. Optional: In the dialog, select a Regulatory Objective to limit the export to the products and packagings impacted by that Regulatory Objective.
  4. Click Continue.

Vault exports the UDI data in the background. When finished, you’ll receive a Vault notification and email. When the export succeeds, the notification includes a link to download the export file. Vault also attaches the file to the Registration record.

About General UDI Data Exports

Vault exports all active UDI details on the Registration. For objects with a Use for UDI field, Vault only includes records where Use for UDI is Yes. For objects without the field, Vault includes all active records.

The export includes the following objects and object types:

  • Registered Active Substance (registered_active_ingredient__rim)
  • Registered Authorization object: Device Certificate, Device Listing, and Device Premarket Submission object types, combined in one tab.
  • Registered Clinical Study
  • Registered Nomenclature Code (registered_product_classification__v)
  • Registered Packaged Product (registered_packaged_medicinal_product__v)
  • Registered Packaging Characteristic object: UDI Attributes and UDI Clinical Size object types
  • Registered Product Characteristic object: Basic UDI Attributes object type
  • Registered Regulatory Text object: Device Intended Use, Device Description, and Device Trade Name object types
  • Registered Shelf Life or Condition object (registered_shelf_life_and_storage__v): Device Storage and Handling Condition and Device Critical Warning object types

The export file uses a single format that includes every UDI data element Vault supports, regardless of market. Columns for data you do not track on the Registration are blank. We recommend tracking only the details each market requires on its market-specific Registration.

Vault includes all in-scope UDI data on the Registration, including records you may not otherwise have permission to view, so that the export is complete.

Filtering by Regulatory Objective

When you select a Regulatory Objective, Vault first finds the active UDI details on the Registration that reference that Regulatory Objective, then identifies the Products and Packagings those details relate to. Vault then exports all UDI details for those Products and Packagings, including details that do not reference the selected Regulatory Objective.

Vault relates each UDI detail to a Product or Packaging as follows:

Object Object Type Related By
Registered Active Substance (registered_active_ingredient__rim) All Packaging, through the referenced Active Substance record’s Product Variant Active Substance records and their Product Variant
Registered Authorization Device Certificate Product
Registered Authorization Device Premarket Submission, Device Listing Packaging
Registered Clinical Study N/A Product, through the referenced Clinical Study record’s Clinical Study Product records
Registered Nomenclature Code (registered_product_classification__v) N/A Packaging if populated, otherwise Product
Registered Packaged Product (registered_packaged_medicinal_product__v) All Packaging
Registered Packaging Characteristic UDI Attributes, UDI Clinical Size Packaging
Registered Product Characteristic Basic UDI Attributes Product
Registered Regulatory Text Device Intended Use Packaging if populated, otherwise Product
Registered Regulatory Text Trade Name, Device Description Packaging
Registered Shelf Life or Condition (registered_shelf_life_and_storage__v) Device Storage and Handling Condition, Device Critical Warning Packaging

About the Export File

Vault names each Excel file export-udi-data-{Registration record ID}-{timestamp}, where the timestamp is in UTC and uses the format YYYY-MM-DD-HH-mm-ss.

When a Registration includes more than 300 Device Identifiers (Basic UDI-DIs and UDI-DIs), Vault splits the data into multiple export files.

If the export fails, the notification explains why:

  • No data found: The Registration has no active in-scope UDI details, so Vault didn’t create a file. If you selected a Regulatory Objective, check that UDI details reference it.
  • An unexpected error occurred: Try the export again, and contact your Vault Admin if the issue persists.

Limitations

  • General UDI data export requires the Enable enhanced UDI attribute locations setting, and therefore does not support the UDI data model used before 23R3.
  • When a Registration includes more than 300 Device Identifiers (Basic UDI-DIs and UDI-DIs), Vault splits the data into multiple export files.
  • The Export Generic UDI Data action is only available on Registrations with the standard Marketed Device Product Registration object type.
  • When exporting generic data, Vault does not apply country-specific logic or validate data against Health Authority business rules. You must transform and validate the data outside of Vault before submitting.
  • Vault does not create UDI Submission or Registered Device Identifier records or UDI Submission documents, and does not track submission status for exported data.

Vault runs the Export Generic UDI Data action as the system user, so the export file includes all UDI data on the Registration, regardless of the initiating user’s record access. This means that any user with the appropriate object action permissions can run the Export Generic UDI Data action to view all UDI source data.