Global Reconciliation: FDA, EU, PMDA, NMPA and UK Requirements for DHTs
Why the shared requirements carry across markets and the local differences do not — and how to decide when a per-jurisdiction assessment is actually needed.
A DHT accepted in one major market is not, by that fact, deployable in the others: lead-market acceptance is evidence, not a passport.
Three questions decide whether a market needs its own assessment; one yes means local work, no to all three means the work already done can be relied on — if the reliance is written down and dated. Reconcile the differences market by market; do not wait for a harmonization that does not exist.
Three questions decide whether a market needs its own assessment; in-country representation is not one of them
Could the device's regulatory status or class differ here? If yes, this market needs its own classification view.
Does the trial need its own local authorization route? Market access and permission to use the DHT in a study are separate decisions.
Do local data-export, testing or cybersecurity rules apply? They are local by construction and cannot be inherited.
Record a written reliance rationale: what matched, what local work remains, and what would reopen the decision.
US agent, MDR Art. 11 authorised representative, UK Responsible Person, Japanese MAH, Chinese agent: a task to complete, not a question to test.
Only the conduct and evidence layer carries across all five markets
ICH E6(R3) incl. Annex 2, the IMDRF software risk logic and fitness-for-purpose evidence travel. Classification, trial authorization, registration and data export do not.
FDA; notified bodies and national competent authorities under the MDR with Member States authorizing the trial; MHLW with PMDA; NMPA; MHRA. Bar GB’s time-limited CE acceptance, a lead-market clearance binds none.
A symptom-tracking app can be class IIa under MDR Annex VIII Rule 11 in the EU and a lower-risk digital health function elsewhere. Role and function are assessed locally.
Great Britain consults on indefinite CE recognition, the EU AI Act timeline moved in July 2026, Japan extends its SaMD program and China rebuilt its GCP framework in 2026.
Six steps, from shared ground to re-confirmation on change
- 1Anchor on the shared requirements — ICH E6(R3) including Annex 2, the IMDRF software risk logic and fitness-for-purpose evidence.
- 2Locate the local differences — device classification, trial authorization, registration, data export and local testing.
- 3Test materiality — decide which differences actually affect this deployment rather than cataloging all of them.
- 4Decide on local assessment by applying the three tests; where none bites, write and date the reliance rationale.
- 5Satisfy the standing requirement for in-country representation in every market — it never discriminates between them.
- 6Re-confirm on change — when a market is added, a regime moves, or the device's role shifts in one territory.
ICH E6(R3) incl. Annex 2 · IMDRF software risk logic · FDA DHT guidance s.III · MDR Annex VIII Rule 11 and Art. 11 · CTR 536/2014 · 21 CFR 807.40(b) · Regulation (EU) 2026/1744 (AI Act) · PMD Act · State Council Order No. 739 · PIPL · SI 2025/538
© qointa 2026 – Public – Uncontrolled when printed · Not legal advice; this summary does not classify any device.
sales@qointa.com · qointa.com
More from the library
Digital Health Technologies in Clinical Trials — A Regulatory Position-Paper Series
One device, several perimeters: a framework for assessing the regulatory impact of the technologies a trial relies on.
Read more →Who Is the Manufacturer? Economic-Operator Roles in DHT Supply Chains
How provisioning, importing, kitting and modifying a device assign manufacturer, importer and distributor duties — often by operation of law.
Read more →You Can Delegate the Work, Not the Accountability: Vendor Qualification and Oversight under ICH E6(R3)
The sponsor’s duty to qualify and oversee its DHT vendors — distinct from who holds the economic-operator role.
Read more →Talk to a specialist
Bring one device and one protocol — a wearable, a sensor, an app, anything. We will tell you which regulatory perimeters it opens and what it takes to close them.
Book a 15-minute call