Device Change Control: A Five-Market Release Plan for 2026

TL;DR

A device change approved at headquarters can still require a separate local submission, approval or new registration. The useful release decision therefore names the changed configuration, the affected local authorization and the evidence that permits implementation in each market. Singapore, Malaysia, Hong Kong, Australia and Mexico use different categories and processes; a shared label such as minor change provides no common permission to release. ^{1 2 3 4 5 6 7}

Two current-version details deserve particular attention. Singapore’s GN-21 R7 requires approval before implementing Administrative changes under Flowchart 6Aii/6Aiii, whereas older HSA web text still describes an acknowledgement route. Malaysia’s published replacement guidance, MDA/GD/0072, has an implementation trigger tied to the official launch of MeDC@St 3.0; its publication alone does not establish that the replacement process is in force. ^{1 2 8}

The analysis below compares release questions and proposes a record for coordinating the manufacturer with its local registrant, representative or sponsor. It also separates Pure Global’s annual representation fees from government charges and additional technical work. No registry snapshot is used to estimate change-notification incidence, customs delays, distributor behavior or market shares.

Define the change before assigning a route

Start with the approved configuration and a precise before/after description. Identify changes to intended use, design, software, materials, manufacturing, sterilization, labeling, certificates and legal entities. A project described commercially as a factory move can contain a manufacturing-site change, certificate update and label revision; the local assessment must consider the actual components and their combined effect.

Create an authorization map: local product identifiers, registered models, legal manufacturer, local holder, current certificates and reference approvals. Then give the local responsible party the comparison and supporting evidence. Ask for a documented route and implementation condition, including whether a new application is needed. This is a proposed coordination method; each authority’s current rules determine the actual filing.

Sources: current authority guidance and procedures. ^{1 2 3 4 5 6 7} The final column proposes a coordination record; actual filing requirements require a complete market-specific assessment.

Apply current versions to the local release decision

Singapore: distinguish approval from acknowledgement

HSA’s current guidance index lists GN-21 R7 under July 2026; the linked PDF is headed August 2026. Section 2 (printed pages 10–11) states that Technical changes for Class C/D, specified Review changes for Class B, and Administrative changes require approval before implementation. In particular, Administrative changes to public SMDR particulars under 6Aii/6Aiii require approval. Notification changes may be implemented on HSA’s acknowledgement after SHARE submission, subject to the guidance’s conditions, including relevant AE/FSCA reporting. For changes connected to open reportable AEs or ongoing FSCAs, prior HSA approval is required regardless of CN category, unless HSA expressly permits otherwise in written advice (§2.2). ^{1 2}

This distinction matters when teams reuse an older checklist: HSA’s general CN webpage still describes 6Aii/6Aiii implementation on acknowledgement, while R7 expressly requires approval. Use the current specific guidance for that assessment and seek HSA clarification where necessary. For combined categories, HSA applies the most stringent category and its corresponding fee/turnaround basis. ^{1 2 9}

Malaysia: correct the category and confirm the transition

MDA/GD/0020 Fourth Edition distinguishes Category 1 changes requiring new registration, Category 2 changes requiring MDA evaluation and endorsement before implementation and market placement, and Category 3 changes implementable on submission of complete documents through MeDC@St. Category 3 is a complete-submission route, rather than an automatic permission arising from merely sending an incomplete notice. ^{3 4}

MDA’s announcement for MDA/GD/0072 states that the new guidance takes effect following the official MeDC@St 3.0 launch and that GD/0020 remains applicable until that implementation. Before filing, confirm the operative framework and transition instructions with the local representative against MDA’s current notices. Keep the framework version with the route decision. A document’s publication date alone supplies no implementation date. ⁸

Hong Kong: use GN-10:2026 and preserve version traceability

Hong Kong’s MDACS is a voluntary administrative listing scheme. This comparison concerns devices listed under it, rather than a universal statutory market authorization; other applicable legal and procurement requirements remain separate. Its listing scope covers general medical devices in Classes II–IV and IVDs in Classes B–D. ¹⁰ The current GN-10 revision is dated June 26, 2026. It distinguishes Major and Minor changes and adds specified changes that require no reporting, with safety-related conditions. For an MDACS-listed device, a Major Change may be implemented only after MDD approves the relevant Change Application (§3.2). Submission is required at least twelve weeks before planned implementation (§5.1.1); elapsed time alone grants no implementation permission. Minor changes may be implemented before approval, with notification within twenty-four weeks of LRP awareness. A change of manufacturer name requires a new listing application under §7.4.1. ⁵

The document also addresses supply of changed and original versions and their identification. Treat those provisions as conditions of the actual change and transition, rather than a universal six-month sell-through entitlement. Maintain a record that distinguishes the supplied versions. ⁵

Australia: assess the ARTG entry and manufacturer evidence together

TGA’s variation guidance explains when a device’s ARTG entry may be varied and when a proposed change would result in a different kind of device. A manufacturer name/address change also requires attention to whether the legal entity and manufacturing QMS remain the same. A change in QMS control can lead to a new-application requirement. Separate manufacturer-evidence updates from the device-entry assessment and any TGA conformity-assessment certificate obligations. ⁶

Mexico: select the current administrative or technical procedure

COFEPRIS’s device-modification page, updated May 4, 2026, identifies the administrative procedure COFEPRIS-2022-022-003 and the technical modification procedure with assessment, COFEPRIS-2022-022-004-A. Select the procedure from the actual change and current criteria. The labels administrative and technical describe local processes; they should not be translated into another market’s minor/major classification or assumed to carry the same implementation permission. ⁷

Coordinate one change through separate local milestones

Consider a hypothetical manufacturer updating its legal name while retaining the same entity and QMS. Australia’s assessment can consider evidence of that continuity, while Hong Kong GN-10 specifically directs a manufacturer-name change concerning an MDACS-listed device to a new listing. The same corporate event therefore warrants separate route decisions. This hypothetical comparison illustrates the frameworks; an actual manufacturer requires its own authority-specific assessment. ^{5 6}

For a combined technical and labeling project, create one controlled source comparison and separate market decisions. Give the local holder enough time to identify missing evidence before the manufacturing release date is fixed. Keep approval, production implementation, first local supply and stock transition as separate milestones. A reference-market approval may support a local submission while leaving the local implementation condition outstanding.

This proposed record gives quality, regulatory, supply and commercial teams a common set of facts. It avoids a global approval field that hides market-specific conditions. A market-access scope discussion can establish the applicable work before commercial dates are committed.

How much does registration and ongoing representation cost?

Budget three separate layers: government charges, annual in-country representation, and any additional technical/submission work. The table below reports Pure Global’s single-registration annual representation bands from the Pure Global Master Price List, 2026, in US dollars. Local classifications differ, so determine the class separately in each jurisdiction. A service-price band itself creates no registration requirement for an exempt product.

The listed representation scope includes preparation and submission, modifications, renewals and authority correspondence, subject to the country-specific terms. Australia’s included registration preparation is based on CE reference approval. The price list includes translation and importation-related assistance in specified markets, and CAB coordination in Malaysia. Confirm the actual device, filing unit and work covered in the service agreement; external testing, authority charges and additional technical work need their own budget.

The published bands assume a three-year contract. The price list provides multi-registration tiers, early termination with payment of 50% of the remaining contract value, and a 50% first-year increase for annual contracts. Compare equivalent scope and contract terms when budgeting.

For a worked annual example, assume one registration in each of four markets: Australia at US$2,000, Singapore Class B at US$2,000, Malaysia Class B at US$2,000 and Mexico Class II at US$3,000. Annual representation totals US$9,000, before government fees and separately scoped work. These local classes are assumptions for the example, not a cross-market classification determination.

Government fees follow the actual filing. As a change-notification example, HSA lists Administrative CN at S$560, Class C Technical CN at S$1,890 and Class D Technical CN at S$3,120, with target turnaround times of 30, 75 and 90 working days respectively. These targets exclude applicant stop-clock time and are not guaranteed end-to-end project durations. A new registration has its own application and evaluation charges. ¹¹

Additional reference-dossier work is separately scoped. The 2026 price list quotes US 510(k) compilation/submission at US$15,000–20,000 per submission and US regulatory-pathway determination at US$5,000 per project. EU CEP/CER compilation and writing ranges from US$15,000 to US$30,000 per device or device family, depending on class, with expert scope confirmation and listed specialist-location pricing terms. These are optional US/EU service scopes, separate from the five markets’ change-notification charges.

Pure Global can help coordinate local representation and the evidence/filing handoffs. For a useful scope discussion, bring the authorization map, before/after comparison, intended market dates and reference approvals. The resulting quote should identify the registration count, local class, contract terms, government charges and any work beyond the included representation scope.

Methods and limits

This is a primary-guidance comparison checked on November 1, 2026, with version and implementation distinctions retained. The tables are editorial synthesis; the source documents and authority decisions determine actual obligations. No MDA latest-change-date histogram is interpreted as annual notification flow, no name-token heuristic is used to infer corporate ownership, and no registry listing count is treated as distributor performance. Fee examples use the actual 2026 company price list and HSA’s current fee page; currencies, charging units and exclusions remain separate.