OfferSomething we do for you. Not yet run on a study’s device data.
Trials that take a measure from a device often change device model or firmware during follow-up, or run different device generations at different sites. An endpoint measured that way can then move for reasons that have nothing to do with the participant.
When a study replaces a device, updates its firmware or changes the software that derives an endpoint, we write the bridging protocol before the change and report afterwards whether the endpoint moved, set against measurement noise. Typical cases: a new device generation in a sponsor study, or a device or operating-system update during a multi-year study.
For each measure the protocol relies on, we hand over:
- the size of the shift between device generations, with its uncertainty;
- how many participants’ readings move across the protocol’s threshold, set against what measurement noise alone would move;
- where participants were measured on both devices for a period, a bridging correction with its uncertainty, fixed before the endpoint data are unblinded.
What it needs: a change record (old and new device model, firmware and settings, and the month of the change) and either a period in which both devices were used or enough participants measured on each device. The analysis can run in the sponsor’s environment, and only aggregates leave it.
Our device-change work has so far been tested on public data only. We describe what it produces, not how it works; method details are shared under a confidentiality agreement.
Holders of study device data can also contribute device-change aggregates to the Analyser-Change Registry.