What Data Protection Is, and Why It Matters Now
Korea's pharmaceutical data protection system bars regulators from relying on the safety and efficacy data submitted for a new drug approval when reviewing follow-on products, for a defined period. It prevents later entrants from riding on the originator's dossier and gives innovators time to recover the cost of generating that data.
The critical point is that this system runs entirely separately from patents. A patent grants exclusive rights over a substance, indication, or formulation; data protection is an administrative barrier to the approval dossier itself. Even after a patent expires, a follow-on company cannot file for approval while the protection period is still running. In practice, development planning now has two clocks, not one.
Korean pharmaceutical companies have historically struggled to factor this in, because there was no reliable way to confirm which products were covered or when protection started and ended. With the scope of designated data-protected drugs and the disclosure items now set out in regulation, follow-on developers finally have a documented basis for calculating when their own pipeline can enter the market.
Where Patent-Only Planning Breaks Down
The standard approach in generic and biosimilar development is to take the originator's patent expiry as the anchor and work backwards. Launching at expiry typically requires 10–14 months for regulatory review, 6–18 months for bioequivalence studies or comparative clinical trials, and 6–12 months to secure and validate an API supplier — which effectively fixes the start date.
The flaw is that this calculation has only one anchor. If the data protection period ends after the patent expires, a company can complete its entire data package and still find the filing window closed — a dead interval in which secured API contracts, maintained study batches, and idle staff generate cost and nothing else. For a biosimilar where comparative clinical work runs into the billions of won, a year of that is not a rounding error.
Before signing off on a development start, three items should be confirmed in writing:
A development schedule built without these three is a schedule with only half its evidence in place.
Reading and Using the Disclosed Information
Start by separating what the disclosure confirms from what still has to be inferred. Ingredient name, designation status, and the start and end points of the protection period are fixed dates that can be entered directly into a schedule. The originator's plans for additional indications, ongoing post-approval trials, and competitors' development stages are not visible in the disclosure and require separate intelligence work.
The data also supports forecasting competitor entry. Because the protection end date applies identically to every follow-on developer, it functions as a common starting line — and ingredients approaching that date are likely to attract several companies at once. If you observe API suppliers fielding a surge of inquiries for a given molecule, or CRO comparative-trial slots filling quickly, you should rebuild your profitability model on the assumption of immediate post-launch price competition.
There is also a useful inverse move: identifying product groups outside the protection scope and re-ordering development priorities around them. Products not covered leave only a patent to manage, which makes timing far more predictable. Moving a smaller but schedule-certain product ahead of a large one is often the better call for cash cycle, compared with tying up staff on a major product and absorbing a dead interval.
RMP and Variation Procedures, Revised in Parallel
The same round of revisions reworked risk management plans (RMP). With the scope of products subject to risk management and the procedures for preparing and submitting an RMP now clarified, post-approval obligations are more clearly defined than before. Organizations need to internalize that approval is not the finish line but the start of post-marketing safety obligations.
There is also relief on the administrative side. A basis for filing product variation applications (notifications) in bulk when company-level information changes has been established, easing the burden of processing products one by one after a site relocation or a merger. For a mid-sized manufacturer holding dozens of products, this is a tangible saving.
For a company running regulatory affairs with one to three staff, the practical build order is:
A Pipeline Review Plan, and How KITIM Helps
We recommend sorting your pipeline into three tiers:
Tier A does not mean abandoning the program. Rescheduling the start and redeploying capital to another project, differentiating into an indication or formulation outside the protected scope, and switching paths by generating your own data for an incrementally modified drug are all viable responses. The incrementally modified route is particularly worth examining: paired with a government R&D program, a substantial share of the data generation cost can be funded, turning a dead interval into a period of technical differentiation.
KITIM supports pharmaceutical and biotech companies by combining regulatory strategy advisory with government R&D project planning. We review data protection risk across your pipeline, help re-order development priorities, and identify and structure R&D programs suited to an incrementally modified drug strategy. If you are facing a schedule revision, please [request a consultation](/en/contact).