STK
Article

Software or devices: what causes more friction in clinical trials?

Source: STK
By STK

One question for clinical operations teams. What causes more friction, software or devices?

This week, we have been talking about the journey from STK X3 to STK Helix and what we have learned from building devices for clinical research.

Software understandably gets a lot of the attention in clinical trials. But the device layer can have just as much impact on whether a study runs smoothly.

For sponsors, CROs and clinical technology providers, device strategy can influence:

  • Deployment speed — how quickly devices can be configured, provisioned and put into participants' hands.
  • Global scalability — whether the same device strategy can be deployed consistently across countries, networks and study sites.
  • Lifecycle continuity — whether the device will still be available, supported and replaceable throughout a multi-year study.
  • Data capture consistency — reducing unnecessary variation in hardware, operating systems, screen sizes and configurations.
  • Patient usability — giving participants a simple, consistent experience regardless of their own personal technology.
  • Security and control — enabling applications, permissions, configurations and device policies to be managed appropriately.
  • Connectivity — ensuring participants can reliably transmit data across different regions and network environments.
  • Support burden — reducing the number of device-specific problems clinical operations and support teams need to troubleshoot.
  • Reliability — ensuring the device underneath the application works when the participant needs it.

And perhaps most importantly, reliability.

A beautifully designed clinical application is only useful if the device underneath it works when the participant needs it. That is why we believe device strategy should be considered much earlier in clinical trial planning.

It is a commercial and operational decision that can affect everything from study deployment and participant experience to support costs and data continuity.

That thinking has been central to the evolution from STK X3 to STK Helix. We are not trying to build another consumer smartphone. We are building the device layer around the realities of modern clinical trials.

So, clinical operations teams, where do you see the biggest device-related friction today? Provisioning? Connectivity? Lifecycle? Patient support? Global deployment? Or something else entirely?

Connect with the STK Life team

Discuss your next provisioned-device programme.

Get in Touch

Want to discuss how STK devices can support your trial?

Talk to our engineering team about device provisioning, global logistics and ePRO deployment.

Talk to engineering