ausUDID vs. GUDID: Alignment and Key Differences

For medical device manufacturers already complying with the U.S. Food and Drug Administration’s Unique Device Identification (UDI) requirements, Australia’s UDI framework will look familiar. The Australian Unique Device Identification Database (ausUDID) follows many of the same fundamental principles established by the FDA’s Global Unique Device Identification Database (GUDID), including the use of globally unique device identifiers, standardized device data and centralized regulatory submission.

But similar does not mean identical.

Australia has adapted UDI to its own regulatory framework, introducing Australia-specific data requirements, relationships to the Australian Register of Therapeutic Goods (ARTG), different organizational responsibilities and its own business and validation rules.

That distinction has become increasingly important. Australia began mandatory UDI compliance for Class III and Class IIb medical devices on 1 July 2026, with additional device classes phased in through 2029.

For global manufacturers, the opportunity is therefore not to create another independent regulatory data process for Australia. It is to reuse the data, governance and submission capabilities already established for GUDID wherever possible, while managing the requirements that are unique to ausUDID.

The Common Foundation: Where ausUDID and GUDID Align

Australia did not develop its UDI framework in isolation. Like the U.S. system, it is built around globally recognized UDI concepts intended to improve device identification, traceability and access to reliable device information.

Both frameworks use the Device Identifier (DI) as the primary database identifier associated with a device model. Production Identifiers (PIs)—such as lot, serial number, manufacture date or expiration date—may form part of the UDI carried on the product, but the actual PI values are not stored in either GUDID or ausUDID.

Australia also recognizes identifiers issued through internationally established issuing agencies. The TGA currently accepts identifiers including GS1 GTINs, HIBCC identifiers and ICCBBA identifiers as UDI-DIs.

This creates significant overlap for manufacturers already operating UDI programs in the United States.

Core information describing a device—such as its identifier, brand, model or version, manufacturer information, packaging configuration, clinical characteristics and other attributes—can often originate from the same enterprise product data sources used to support GUDID.

The result is an important strategic advantage:

Manufacturers should think of ausUDID as another regulatory destination for governed global device data—not as an entirely new product data initiative.

The challenge is determining which data can be reused and where Australia requires additional transformation, enrichment or governance.

ausUDID vs. GUDID at a Glance

Area	FDA GUDID	Australian ausUDID
Regulatory authority	U.S. Food and Drug Administration (FDA)	Therapeutic Goods Administration (TGA)
Primary database identifier	Device Identifier (DI)	UDI Device Identifier (UDI-DI), submitted as the Primary DI
Production Identifier values stored?	No	No
Public device information	Available through AccessGUDID	Available through ausUDID
Regulatory-market linkage	U.S.-specific regulatory information, including applicable FDA premarket information	Links UDI records to relevant ARTG inclusion(s)
Nomenclature	Supports GMDN information	Uses GMDN within the Australian regulatory framework
Manual submission	GUDID Web Application	ausUDID Portal
Machine-to-machine submission	HL7 SPL through FDA Electronic Submissions Gateway	HL7 SPL machine-to-machine submission
Regulatory data model	FDA-specific data elements and business rules	Australian UDI Data Dictionary and TGA-specific rules
Key responsible party	Device labeler	Australian sponsor has specific compliance responsibilities; manufacturers can also contribute device data
Regulatory rollout	Established U.S. UDI framework	Phased mandatory compliance beginning 1 July 2026

FDA currently supports manual entry through the GUDID web application and bulk HL7 SPL submission through its Electronic Submissions Gateway. The TGA similarly supports electronic ausUDID submissions and requires organizations using HL7 SPL machine-to-machine submission to test in the ausUDID Pre-Production environment before using that method in Production.

The architectural similarities can therefore make existing GUDID capabilities highly reusable, but the differences underneath the architecture matter.

Key Difference #1: ausUDID Connects UDI Data to the ARTG

One of the most significant differences is the relationship between ausUDID and Australia’s existing medical device regulatory framework.

Devices generally must already be included in the Australian Register of Therapeutic Goods (ARTG) before they can legally be supplied in Australia. ausUDID records link UDI information to the relevant ARTG inclusion or inclusions.

This creates an Australian-specific relationship that does not have a direct GUDID equivalent.

GUDID contains U.S.-specific regulatory attributes, including applicable FDA premarket submission information. Australia instead requires manufacturers and sponsors to consider how global device information relates to Australian market authorization information.

For organizations reusing a global UDI master record, the practical implication is clear: the global device record alone may not contain everything required for ausUDID.

Organizations need a data model capable of combining globally governed device information with market-specific regulatory information.

Key Difference #2: The Australian Sponsor Plays a Critical Role

The operating model also differs. In the U.S., FDA places responsibility for GUDID submission on the device labeler. Australia introduces an important additional stakeholder: the Australian sponsor.

The sponsor is responsible for submitting UDI records for devices it supplies in Australia. Manufacturers can also contribute device data, but the TGA distinguishes between device data elements and sponsor data elements.

Manufacturer-submitted information can cover device-level attributes, while sponsor-specific information—such as the ARTG ID and certain commercial information—must be managed by the sponsor. This becomes especially important when a manufacturer works with multiple Australian sponsors.

Rather than creating completely separate copies of the same device information, ausUDID can associate multiple sponsors with a UDI record while maintaining sponsor-specific information separately. Device-level information is intended to remain consistent, while sponsor-specific information can differ.

For global manufacturers, that creates a governance question that may not exist in the same form within their GUDID process:

Who owns each element of the Australian UDI record, and how will manufacturers and sponsors coordinate changes?

That question should be answered before production submissions begin.

Key Difference #3: Similar Data Does Not Mean Identical Data

A common mistake is to assume that because Australia has aligned its UDI framework with international approaches, a GUDID record can simply be copied into ausUDID.

It cannot.

The TGA maintains its own Australian UDI Data Dictionary, defining the data elements, permitted values, update rules and associated metadata required by ausUDID. The TGA explicitly recognizes that different jurisdictions contain regulatory data elements unique to their environments.

For example, Australian-specific requirements include information associated with the ARTG and sponsor, while GUDID contains FDA-specific information such as applicable U.S. premarket submission information.

Even where two fields represent conceptually similar information, differences may exist in:

• terminology and field definitions
• mandatory versus optional status
• permitted values and code lists
• conditional requirements
• validation rules
• editability after publication
• relationships between device and packaging records
• regulatory identifiers and market-specific attributes

This is why field-level mapping is more important than simple record replication.

Key Difference #4: ausUDID Offers More Submission Methods

While GUDID and ausUDID both support manual and automated submission, ausUDID provides manufacturers and sponsors with a broader range of submission methods.

The FDA currently provides two primary options for submitting device information to GUDID:

1. GUDID Web Application – manual entry of individual DI records, generally suited to organizations with smaller submission volumes.
2. HL7 SPL via the FDA Electronic Submissions Gateway (ESG) – electronic submission of XML files using HL7 Structured Product Labeling, designed for organizations managing larger volumes of device records.

The TGA provides four submission methods for ausUDID:

1. ausUDID Online Portal – manual entry of individual UDI records.
2. Australian UDI Bulk Upload Template – an Excel-based option that enables organizations to submit up to 200 UDI records at a time.
3. Machine-to-Machine HL7 SPL – automated electronic submission for organizations managing larger UDI volumes.
4. GS1 National Product Catalogue (NPC) – enables organizations to submit UDI records to ausUDID through the NPC.

The Bulk Upload Template is a particularly important difference for manufacturers that fall between low-volume manual entry and fully automated machine-to-machine integration. GUDID does not provide an equivalent spreadsheet-based bulk upload option. For ausUDID, manufacturers can prepare up to 200 records in the TGA-provided Excel template and upload them through the ausUDID application.

Australia also provides another pathway that GUDID does not: submission through GS1 Australia’s National Product Catalogue (NPC). This may be especially relevant for organizations already publishing healthcare product information through the NPC, allowing existing product-data syndication processes to play a role in UDI compliance.

At the same time, there is significant alignment between the two regulators for enterprise-scale automation. Both support HL7 SPL, and the TGA explicitly notes that its HL7 SPL approach aligns with the method used by the FDA for electronic GUDID submissions. Organizations with an established GUDID HL7 SPL capability may therefore be able to leverage their existing technical architecture and expertise when implementing ausUDID, while still accounting for TGA-specific data, connectivity, and validation requirements.

Key Difference #5: Public Access and Downstream Use of UDI Data

Both GUDID and ausUDID are designed not only to collect regulatory device information but also to make trusted UDI data available for broader use across the healthcare ecosystem. However, the two systems provide access to that information through different platforms and services.

In the United States, device information submitted to GUDID is made publicly available primarily through AccessGUDID, a service developed by the National Library of Medicine in collaboration with the FDA. AccessGUDID enables healthcare providers, patients, researchers, developers and other users to search and access publicly available GUDID device information.

Australia provides public access directly through ausUDID, allowing users to search published UDI records and access device information submitted to the TGA.

For manufacturers, this means UDI submissions should be viewed as more than a regulatory transaction. Once published, the information becomes a public representation of the device and the organization behind it and can potentially be consumed by healthcare providers, supply chain organizations, researchers and other downstream stakeholders.

This makes consistency across regulatory markets increasingly important. Differences in device names, models, identifiers, packaging information or other shared attributes between GUDID and ausUDID may not necessarily indicate a compliance problem, but they can create confusion for organizations consuming UDI information across markets.

Manufacturers should therefore incorporate public-data review into their UDI governance processes by periodically verifying that published records:

• accurately represent the device currently being marketed
• remain consistent with authoritative product information
• reflect approved changes to device information
• maintain appropriate consistency across regulatory databases where the same device is marketed.

The broader objective is trusted product information, not simply successful regulatory submission. As UDI databases become increasingly important sources of standardized device information, manufacturers that govern UDI data consistently across markets can support both regulatory compliance and more reliable downstream use of their product information.

Australia’s UDI Compliance Timeline

Australia is introducing UDI requirements progressively according to device risk.

Device Category	Mandatory UDI Compliance Start
Class III and Class IIb medical devices	1 July 2026
Class IIa medical devices	1 July 2027
Class Is medical devices	1 July 2028
Class 3 and Class 4 IVDs	1 July 2028
Class 1 and Class 2 IVDs	1 July 2029

The TGA also provides specific transitional arrangements and later milestones for certain existing devices and direct marking requirements. Manufacturers should therefore assess requirements at the individual device level rather than treating the dates above as the complete implementation schedule.

For manufacturers of Class III and Class IIb devices, the first mandatory compliance date has already arrived. The focus should now shift from preparing for the regulation to establishing a sustainable process for ongoing compliance.

Five Strategies for Manufacturers Already Submitting to GUDID

Manufacturers already submitting to GUDID have a strong foundation for ausUDID compliance. Rather than building a separate process for Australia, organizations should leverage their existing UDI data, governance and submission capabilities while adapting them to TGA-specific requirements.

Five strategies can help:

1. Reuse Existing GUDID Data – Start with trusted device data already maintained for GUDID rather than rebuilding Australian records from scratch.
2. Map GUDID to ausUDID – Identify reusable, transformable and Australia-specific data requirements.
3. Separate Global and Market-Specific Data – Maintain common device information once while managing regulatory attributes by jurisdiction.
4. Validate Before Submission – Apply ausUDID-specific requirements and business rules before sending records to the TGA.
5. Build for Multiple UDI Registries – Use GUDID and ausUDID as the foundation for a scalable approach that can support additional global UDI databases.