The legal framework — "three laws stacked"

  • Personal Information Protection Law (PIPL): protects the personal information of trial subjects, patients and healthcare professionals — health data is "sensitive personal information".
  • Data Security Law (DSL): protects data security broadly; in pharma, large volumes may be "important data" requiring security assessment for export.
  • HGR Regulations: special protection of human genetic resource information and materials — overlapping and stacking with PIPL and DSL.

Processing trial-subject personal information

Subject data is "sensitive personal information"

PIPL Art. 28 lists medical and health information as sensitive personal information. Processing it requires:

  • Specific purpose and strict necessity — not collected for "possible future uses".
  • Separate consent — no bundled consent or pre-ticked boxes.
  • Special notice — explaining necessity and impact.
  • Privacy impact assessment (PIA) — conducted and recorded before processing.

Data-protection clauses in the informed consent form (ICF)

GCP informed consent and PIPL "consent to processing" are two separate but stacked requirements. The ICF must satisfy both:

  • Identify each data processor — sponsor, investigator, CRO, central lab — with contact details.
  • State the scope, purpose and retention period (typically at least 5 years post-trial or longer as required).
  • State whether data transfers abroad (almost inevitable in MRCTs), the recipient's name and contact, the purpose, and how subjects can exercise their rights.
  • State subjects' rights — access, correction, deletion (which may be limited during the statutory retention period) and withdrawal of consent (without affecting prior processing).

Real-world studies (RWS) — a special data-compliance challenge

Real-world studies use real-world data (hospital records, insurance claims, patient registries) to generate real-world evidence for post-market study and indication expansion. They raise distinct challenges:

  • Consent exemption for retrospective data: obtaining consent from every patient is often impractical; PIPL allows research uses without consent under conditions (anonymisation, PIA, low impact on individuals).
  • Multi-source linkage and de-identification: linking data across hospitals, insurers and pharmacies without directly identifying individuals is both a technical and legal challenge.
  • Ownership and use rights: hospital-data "ownership" is legally unclear; using hospital data requires a clear data-use agreement covering scope, de-identification standards and result ownership.

Identifying "important data" and export security assessment

The DSL and the Measures for Security Assessment of Data Export establish a security-assessment regime for "important data" export. Which pharma data may qualify?

  • Large-scale population health data: electronic health records and disease registries above a certain scale.
  • Genetic data: population genomic and mutation-frequency data — almost always "important data" (and HGR-regulated).
  • Aggregated pharmacovigilance safety data: large-scale adverse-reaction data.
  • Healthcare-insurance big data: massive treatment and cost data.

If data is classified "important data" and must go abroad, it requires security assessment by the national cyberspace authority (not mere standard-contract filing) — a slow (6–12 months) and difficult process.

Cross-border transfer of pharmacovigilance data

Global PV systems aggregate adverse-event reports from each country into a global database. Sending China PV data abroad is a data export subject to:

  • PIPL — reports typically contain patient personal information (age, sex, history) and reporter information.
  • DSL — large-scale adverse-reaction data may be "important data".
  • GVP — the transfer is itself a regulatory requirement, providing a "statutory obligation" basis for export.

The compliant path is usually to de-identify / anonymise adverse-reaction data first (removing names, ID numbers and contact details) to reduce the export-compliance burden.

How we help

  1. Data-compliance audit: classify and grade data assets, identify "important data" and "sensitive personal information", and assess export scenarios and gaps.
  2. ICF and privacy-policy drafting: achieving "dual compliance" of GCP consent and PIPL processing consent.
  3. Export-pathway planning: identifying scenarios and choosing security assessment / SCC filing / certification, and preparing submissions.
  4. Impact assessments (PIA/DSIA): benchmarking against PIPL and industry standards.
  5. Breach response: contingency planning and immediate legal support on incidents.