The Handoff Is in Validation Scope
A companion reading from the clinical-systems vendor seat — why the integration boundary, not the device, is where the regulated record is made
REGULATORY OPERATIONSThe source record is the repository, not the device — which puts your integration boundary, not the device, at the center of the evidence.
Under FDA the source data live in the durable electronic data repository and FDA does not intend to inspect individual DHTs; the EMA guideline still expects device-side controls. Either way the interface is in validation scope, not just the systems it connects — provenance, timing and audit context must survive the handoff.
Four perimeters meet at the handoff, and each has an evidence artifact
| Perimeter | What it means for you | Vendor action / evidence |
|---|---|---|
| Data integrity | Provenance, timestamps and audit trail across the handoff | Map and validate provenance fields; reconcile the two audit trails |
| Interoperability | The integration boundary is part of the system | Bring the interface into the validated system boundary |
| Inspection | The handoff is examined as evidence for the record | Hold boundary evidence — mapping, tests, reconciliation — ready |
| Change control | Interface changes on either side are change events | Treat interface changes as change events; revalidate |
Four facts about the handoff decide whether your platform is defensible
The integration between the device and your system must be validated, not only the systems at either end.
Source, original capture time and attribution cannot be lost in transit — and silent metadata loss must be tested for, not assumed away.
In qointa's assessment device-side and system-side records should be reconcilable; no instrument prescribes the method.
A validated platform can still receive data it cannot account for — and the sponsor remains ultimately responsible for the trial data either way.
Six moves, in order of what breaks first
- 1Bring the boundary into validation scope so the interface is validated, not just the endpoints it connects.
- 2Map provenance field by field so source, time and attribution survive the handoff rather than dropping silently.
- 3Test for silent metadata loss with negative tests confirming no drop of timestamps or audit context in transfer.
- 4Reconcile the two audit trails so device-side and system-side records align at the seam.
- 5Treat interface changes as change events so an integration change never breaks provenance unnoticed — revalidate.
- 6Hold the boundary evidence package ready — mapping, tests, reconciliation and change records — for audit or GCP inspection.
FDA Electronic Systems, Records and Signatures Q&A (Oct 2024), Q23 · FDA DHT guidance (Dec 2023), s.IV.G · EMA/INS/GCP/112288/2023, Annexes 2, 4, 5, 6 · 21 CFR 11.10(a), 11.10(e) · ICH E6(R3) s.3.6
© 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