Regulatory Affairs • Global Registration

Global Device Registration - Country List Maintenance

Duration: 19 months • Role: Regulatory Affairs Specialist

Completing Thailand's registration document and updating the tracker showed that a global registration country list is a moving target - it has to be reconciled against source certificates and government registries on a cadence, not treated as a one-time compilation.

Context

Adding Thailand to the global device registration list surfaced the same reconciliation problem seen across other markets: certificates and country lists drift from the master tracker unless they're actively maintained against the source registry.

Global Registration Thailand Registration Tracker

Primary Risks Identified

  • A country's registration status going stale in the tracker (e.g. certificate expired or a requirement changed) without anyone noticing until a shipment is blocked

Testing Approach

Cross-checked each country's registration status and certificate data against the source registry and Salesforce record, corrected any discrepancies found, and updated the master tracker.

Salesforce Registration Tracker Certificate Review

Outcome

Updated the global device registration list, adding Thailand and reconciling it against current certificates.

Key Lessons

A global registration country list is a moving target - it has to be reconciled against source certificates and government registries on a cadence, not treated as a one-time compilation.

Have a system like this?

If you have no idea of testing your current system, let's talk through what's actually going on.

Contact me