What the Trial Needs From the Handset Maker
A companion reading from the phone manufacturer / OEM (original equipment manufacturer) seat — what the trial needs from you, and why none of it is your obligation
REGULATORY OPERATIONSYou hold no clinical-trial obligations — and the trial's regulated evidence is built on what you publish about your hardware.
Where trial software runs on your handset, the software manufacturer answers for your hardware's safety, performance and reproducibility in combined use — and can only do so with what you disclose. An unnotified sensor change invalidates a validated measure mid-study; the study running on your hardware is the one that stops.
Each perimeter is someone else's obligation, discharged with your hardware
| Perimeter | What it means for you | Why it matters to your roadmap |
|---|---|---|
| Endpoint validation (QPP-01) | Sensor specifications feed the V3 evidence chain | Spec stability across SKUs decides whether a validated measure survives a refresh |
| Change control (QPP-07) | Hardware / sensor change-notification lets the trial manage drift | Notification turns model-year updates into managed events, not stranded studies |
| Device status and scope (QPP-00) | Qualification follows the software maker's intended purpose, not your hardware | Capability plus published end-of-sale / end-of-support dates set which studies you can support |
| Interoperability (QPP-14) | Where your handset hubs other devices, its behavior is part of the system | OS / connectivity behavior you ship becomes part of someone's validated system |
Four things you ship decide whether a study can use your range
Performance characteristics per model feed the verification and analytical-validation work a sponsor must complete before a measure supports a claim.
Advance notice of a component or model-year change is what separates a managed event from a study-stranding one, months after it shipped.
Variation across your range decides which participants a BYOD study can enrol at all.
Published end-of-sale and end-of-support dates stop a validated configuration being stranded mid-study.
Four disclosures that cost a published document and a named mailbox
- 1Publish and version sensor specifications so others can cite a stable source in their validation.
- 2Notify measurement-affecting changes in advance so a model-year update is a managed event, not a stranded study.
- 3Map SKUs to sensor stacks and publish lifecycle dates so studies can plan around heterogeneity, end-of-sale and end-of-support.
- 4Name a clinical / regulatory point of contact so sponsors and vendors have a route to ask and get answers.
MDCG 2023-4 (Oct 2023), Option 3 · MDCG 2019-11 Rev. 1 (June 2025) s.3.1 · FDA DHT guidance (Dec 2023) s.III · EMA/INS/GCP/112288/2023 s.6.1.3 · Regulation (EU) 2024/2847 (Cyber Resilience Act) Arts 2(2), 14 · V3 / V3+ (Goldsack 2020; Bakker 2025)
© 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