On May 22, 2026, the National Medical Products Administration, together with the National Health Commission, released the third batch of pilot lists for laboratory-developed tests (LDTs), covering 12 free trade zones and biopharmaceutical cluster areas including Beijing, Shanghai, and Shenzhen. This policy is directly related to the clinical commercialization pathway of in vitro diagnostic (IVD) products and data compliance management requirements, and it sets clear standards for the official websites of Chinese IVD companies conducting business with overseas medical institutions, laboratories, and distributors. Relevant companies need to immediately assess the compliance of their existing digital assets.

Event Overview

On May 22, 2026, the National Medical Products Administration and the National Health Commission jointly released the third batch of LDT pilot lists. The pilot regions include 12 free trade pilot zones and key biopharmaceutical industry cluster areas such as Beijing, Shanghai, and Shenzhen. The document clearly requires that the official websites of Chinese IVD companies serving overseas hospitals, laboratories, and distributors must embed clinical applicability statements and data sovereignty disclosures that comply with GCP and LDT pilot requirements on product pages, solution pages, and FAQ sections. Companies that fail to implement these requirements may affect their product market access review and procurement credibility in the pilot regions.

Which Market Segments Will Be Affected

Direct Trade Enterprises

For companies selling IVD equipment, reagents, or supporting SaaS platforms to overseas end customers, such as overseas hospitals and third-party laboratories, their official websites are the first touchpoint for overseas buyers conducting due diligence. The absence of clinical applicability statements will lead buyers to question the completeness of the product’s clinical validation, directly affecting business negotiation efficiency and contract signing progress.

Channel Distribution Enterprises

Distributors engaged in cross-border distribution and localization services for imported IVD equipment and reagents need to provide downstream customers with compliance support materials. If upstream manufacturers’ official websites do not embed standardized clinical statement modules, distributors will find it difficult to consistently provide technical documentation that meets LDT pilot requirements, increasing customer response costs and the pressure of compliance risk transfer.

Supporting SaaS Platform Service Providers

For SaaS providers offering software services such as LIMS, AI-assisted interpretation, and data governance for IVD companies, if their products involve the collection, storage, or analysis of clinical data, they must also meet data sovereignty disclosure requirements. If the official website does not disclose data processing boundaries, storage locations, and cross-border transfer mechanisms, it will affect the qualification assessment for being recognized as a supporting LDT system.

What Key Points Should Relevant Companies or Practitioners Pay Attention To, and How Should They Respond at Present

Pay Close Attention to Subsequent Officially Released Supporting Implementation Rules and Template Examples for LDT

At present, it is only clearly stated that “clinical applicability statements and data sovereignty disclosures must be embedded,” but the specific text format, level of legal effect, and technical implementation method have not yet been announced. Companies should continuously monitor updates on the official website of the National Medical Products Administration and regulatory platforms in pilot regions, and give priority to referring to the public statement structures already disclosed by institutions in the first and second batches of pilot programs.

Differentiate the Granularity of Statements and Responsible Parties Across Different Website Pages

Statements on product pages should focus on the clinical validation basis for individual product categories, such as whether retrospective clinical evaluation has been completed, applicable populations, and testing limitations. Solution pages should explain the compliant design of data flows in multi-system integration scenarios. FAQ sections should cover common concerns of overseas buyers, such as GDPR compatibility and commitments to localized domestic data storage. The content of such statements should be led by the registration/regulatory affairs department to avoid unilateral wording by the marketing department.

Simultaneously Assess the Consistency Between SaaS Service Agreements and Website Statements

If a company provides both IVD hardware and supporting software, the description of data sovereignty in website statements must be strictly consistent with the user service agreement (SLA), privacy policy, and actual deployment architecture. For example, if it states that “raw testing data does not leave the country,” then the cloud platform architecture must not involve overseas node caching behavior, otherwise it constitutes a substantive compliance conflict.

Launch a Modular Front-End Website Renovation Plan to Avoid Temporary Page Replacements

It is recommended to adopt configurable compliance statement components, such as CMS plugins, to support dynamic invocation of corresponding statement versions by product line, target market, such as the EU/Southeast Asia, and data processing mode, such as domestic-only/hybrid deployment, rather than hard-coding across the entire site. This can reduce repeated development costs caused by subsequent minor policy adjustments.

Editor’s Viewpoint / Industry Observation

Observably, this notice functions primarily as a regulatory signal rather than an immediate enforcement mandate — no implementation deadline is specified, and no penalty mechanism is outlined in the initial announcement. Analysis shows that the requirement targets digital touchpoints as proxies for broader clinical governance readiness: embedding declarations on public websites reflects expectations of transparency, traceability, and pre-emptive alignment with LDT’s evolving evidence standards. From an industry perspective, it signals a shift from post-hoc compliance verification to front-loaded accountability — where digital infrastructure becomes part of the regulatory interface itself. Current focus should be on interpretation consistency across departments (regulatory, legal, marketing), not on technical deployment alone.

Conclusion: The core significance of the release of the third batch of LDT pilot lists lies not in expanding the geographic scope of the pilot, but in extending clinical compliance requirements to companies’ external digital interfaces. It is not an immediately effective market access threshold, but it marks that the regulatory logic is evolving from “product registration compliance” to “credible full-chain communication.” At present, it is more appropriate to understand it as a forward-looking governance signal——reminding companies to use their official websites as an entry point to systematically sort out the matching relationship among clinical evidence chains, data governance architecture, and external communication narratives.

Information source note:
Main sources: announcements on the official website of the National Medical Products Administration, joint issuance by the National Health Commission (May 22, 2026);
Areas for continued observation: supporting implementation rules for the LDT pilot, standard templates for clinical statements, and actual procurement trust feedback from overseas buyers.