Design Lock and Change Control for Korea Submissions

The Frozen-Design Problem

A Korean MFDS submission for Class II or higher can sit in review for 5–8 months. During that window, the manufacturer is expected to keep the device design substantially unchanged from what was submitted. The FDA tolerates significant in-review design evolution via the supplementary file mechanism. MFDS does not. A material design change during review effectively voids the submission and restarts the clock.

For hardware devices this is annoying but manageable. For software-based devices — especially AI/ML SaMD — a 6-month design freeze is genuinely costly. The product team continues to develop; the regulatory team freezes the version under review. The two diverge, and at clearance, the manufacturer must decide whether to launch the now-stale frozen version or refile.

Why Korean Change Control Is Stricter

Three structural reasons:

1. No PCCP equivalent. The FDA's Predetermined Change Control Plan allows manufacturers to pre-authorize specific design changes (parameter ranges, retraining triggers, performance bounds). MFDS has not adopted this framework. Each material change is a new notification.

2. Strict equivalence-product comparison. The Korean review is anchored on a specific equivalent product profile. If the design changes during review, the equivalence comparison changes, and the reviewer treats it as a new submission.

3. Reviewer discretion on materiality. MFDS reviewers have wider discretion than FDA reviewers in deciding whether a change is "material." Conservative reviewers treat minor changes as material; aggressive reviewers may not. Manufacturers cannot rely on a fixed materiality threshold.

The Design Lock Strategy

A workable design lock for a Korean submission separates "submission-frozen" from "development-frozen":

Branch A (submission-frozen):  v1.2.0 → MFDS review → MFDS clearance → launch
Branch B (development):        v1.2.0 → v1.3.0 → v1.4.0 → ... → planned post-clearance update

The development branch continues. The submission branch is treated as a separate maintained release line until clearance, then re-merged into mainline at the next planned material update.

For this to work, three preconditions must hold:

1. Versioned design history. Every change to the design — including code commits, document revisions, drawing updates — must be associated with a version baseline. ISO 13485 requires this; the discipline of actually doing it is often weaker than the procedure suggests.

2. Branch isolation in the QMS. Design changes on the development branch must not propagate to the submission branch's design history file. Some QMS systems make this trivial; others require manual control.

3. Post-clearance update plan in the dossier. The MFDS submission should include a brief description of planned post-clearance updates. Not as a PCCP-equivalent (which Korea does not yet accept), but as transparency that signals to the reviewer the product will continue to evolve.

What Counts as a Material Change

MFDS guidance and our experience handling change notifications:

Material (triggers re-notification or re-review):

• Change to intended use phrasing or target population
• New patient contact materials
• Change to sterilization method
• Software architecture changes affecting performance
• Algorithm retraining that changes performance characteristics
• New accessories or compatible devices added to labeling
• Manufacturing site change

Non-material (informational notification only):

• Cosmetic packaging changes
• Manufacturing process improvements with no specification change
• Software bug fixes that do not affect intended use or performance
• Labeling translation refinements
• Supplier change for non-critical components

The grey area:

• Software UI changes (sometimes material, sometimes not, depending on whether they affect user interaction with safety-critical features)
• AI retraining with same dataset (typically non-material if performance bounds are preserved)
• New accessory that does not change parent device classification

Change Notification Mechanics

When a material change is needed after clearance, the manufacturer files a change notification through the KLH. The notification includes:

• Description of the change
• Rationale (often: safety improvement, regulatory alignment, market feedback)
• Updated technical file sections
• Updated risk file
• Verification/validation evidence for the change
• Updated labeling (if applicable)

Timeline: 30–90 days for non-material; 60–120 days for material. Material changes affecting intended use can trigger a full re-review.

The Korea Design Lock Solution

A standalone change-control framework for the Korean lifecycle of a device, distinct from global change control, addresses the divergence problem. The framework includes:

1. Change classification matrix — Korean-specific materiality thresholds documented as part of the QMS.
2. Pre-submission design freeze — formal handoff from design team to RA, with versioned baseline.
3. Submission-period change protocol — what to do if an unplanned change becomes necessary during MFDS review.
4. Post-clearance update calendar — planned change batches at 6 or 12 month intervals, sized to minimize notification overhead.

Manufacturers running this framework consistently report 30–50% reduction in change-notification cycle time, primarily because the change is correctly classified before it goes to MFDS rather than being reclassified during review.

Three Recommendations

Recommendation 1: Run the design lock early. Lock the design 4–8 weeks before MFDS submission, not at submission. The pre-submission interval lets the team find any last-minute concerns without restarting review.

Recommendation 2: Batch post-clearance changes. Six-month change batches consistently outperform monthly trickles, because each notification is administrative overhead regardless of change size.

Recommendation 3: Document the materiality decision. When the manufacturer decides a change is non-material, document the decision and the rationale. This becomes evidence in surveillance audits if the auditor questions whether a change should have been notified.

Where Leanabl Plugs In

The Korea Design Lock solution sets up the framework for managing the design-lock and post-clearance change calendar. For upstream design control work that feeds clean technical files into the lock, Design Output and Discovery & Design handle the design history file. The change-notification mechanics themselves are handled through Korea License Maintenance.