One goal of the Product team at Lindus Health is to help sponsors, clinicians, and clinical operations staff manage trials more efficiently.
The reality is that every clinical trial is unique in its objectives. Every therapeutic area and the corresponding clinical trial will have custom requirements, and each site staff engaged in a trial will want our product to fit the habits and quirks of their research practice. As sponsors will know, with many CROs configuring an existing feature (let alone implementing a new one) can take months and cost a pretty penny.
At Lindus Health, we pride ourselves in our ability to move fast and add new functionality without causing any trial delays. Implementing a new feature across our products to accommodate a slight change in trial configuration requires a thorough understanding of the existing codebase and the implications of adding that feature. So how do we ensure our suite of products is ready at a moment's notice to accommodate the changes required by the protocol?
Well, there are several viable solutions. One solution is to specialise in a small subset of complementary therapeutic areas, for example, in trials that require only ePRO patient diaries collected remotely. A tempting but unfavourable approach that goes against our mission statement – to accelerate trials for ALL healthcare pioneers.
Another is to build a productised offering to serve a specific industry segment, for example, patient recruitment and onboarding - a solution which prevents us from delivering end-to-end clinical trials in-house.
At Lindus Health, we’ve decided to go the path that ultimately delivers the most value to Patients and Sponsors alike. We’ve decided to build our products so that they minimise the amount of time from onboarding a new Sponsor to preparing a regulatory submission. To deliver this across the entire trial lifecycle requires intense prioritisation.
Our chosen strategy requires us to be flexible by design and ruthlessly prioritise what we will build. Our approach is to assign guiding principles to how we prioritise features in our roadmap. This framework has three levels.
These features typically take precedence over others, and we are more likely to deploy time, people and resources to ensure our ClinOps team can comfortably prepare for the trial to start.
We recognise that we will have to rewrite and rethink these over time. For example, we’ve built an ePRO scheduling tool that tracked which patients were overdue on surveys and withdrew them if patients were unresponsive for a long time. We used the overdue logic but removed the automatic withdrawals based on ClinOps feedback.
We identify these features as relevant and applicable to the broader clinical trial management. These include mainstay features like adverse event reporting that we will use in virtually every clinical trial we run.
An upcoming clinical trial does not necessarily require these features, but they are essential to our product functionality. We use this prioritisation level to be creative and experiment with building great user experiences. You can read more about a specific feature in a blog post by one of our software engineers.
Of course, frameworks are only helpful if we use them. We want to strike the right balance between forcing a framework and having a valuable mechanism to help us make better decisions. Over time we’ve observed that the boundaries between these levels are often blurred - but having a framework on which we can build helps us to guide our decisions during planning and roadmap meetings.
All of this helps us build one product to rule all clinical trials, and deliver on our mission of accelerating trials for biotech and healthtech pioneers.
Why I joined Lindus Health - Hannah Swayze, Senior Trial Manager
To overcome the current barriers to clinical research; To develop innovative technology that will deliver clinical trials more efficiently; To be a part of a supportive, flexible and growing team.
Product Clinic #3: Embedding software engineering efficiency hacks into our clinical trial platform
Heard of dogfooding? No, not feeding your pet! The practice of using your own software to understand how it performs in the real world and catch any issues. Read about this and other software engineering hacks we are using to build better products.
A Fireside Chat with Paul Wicks: How can we make clinical research for digital therapeutics more patient-friendly?
Digital Therapeutics are still a relatively new treatment area and there is a lot to learn about conducting clinical research on them. Find out how Paul Wick's, Digital Health expert, thinks research companies can put the patients first.
Product Clinic #2: Using feedback loops to build better products
Lindus Health's objective is to build better products that hit non-negotiable clinical standards and challenge outdated conventions. How do we do this? Read more here
Why I joined Lindus Health? Ece Kavalci, Machine Learning Engineer
Working towards a good cause. Innovative approaches to solving problems in clinical trial design. Every contribution is valued.
Why I joined Lindus Health? Van Zyl Engelbrecht
The mission to accelerate clinical trial. The focus on making clinical research more patient-centric. The ability to support innovative health companies bring their product to market at a lower cost.
Product Clinic #1: Turning boring technology into exciting products
Don't be put off by the blunt use of the word "boring" to describe our technology. It's one of our guiding principles allowing us to make rapid progress while maintaining high quality standards. Read more here.
James Lind and the Mafia
The story of how James Lind's trial for scurvy led to the formation of the mafia.
What actually improves diversity in clinical research?
We’ve all seen the evidence of ethnic minority underrepresentation but what is actually going to have an impact in the future? Read Lindus Health’s action plan here
Vaccine Trials and Tribulations
Read co-founder Meri’s experience of a Covid-19 vaccine trial that left him frustrated (but vaccinated), and led to the creation of Lindus Health.
Stagnation, Drugs and Eroom's law
Why does the cost of clinical trials continue to increase? Meri Beckwith, Lindus Health co-founder discusses why stagnation has prevailed and how technology is the answer
Cure Scurvy with this one weird trick…! Doctors hate him
In 1747 James Lind conducted the first clinical trial, proving that oranges and lemons were a cure for scurvy. Given that we’re named after him we felt it was about time we wrote a post about the history of scurvy, Lind, and the first ever clinical trial! We believe that in 100 years current health outcomes will seem just as ridiculous and intolerable as 50% of sailors dying of scurvy seems now, and that’s why we’re named Lindus Health.
Why I joined Lindus Health? Luke Twelves, Medical Lead
To help make trials more accessible to patients and clinicians. To help bring novel and innovative treatments to the frontline of care faster. To stretch myself and work as part of a really exciting team.
A success story: Lindus Health recruiting prediabetes patients for the ASPIRE-DNA clinical trial
Lindus Health used its multi-channel strategy to accelerate DnaNudge's trial recruitment. Read more about the challenges they faced and our results here.
Lindus Health launches with $5m seed round to revolutionise health research
Lindus Health publicly launched today, announcing $5m in seed funding from leading technology and healthcare investors including Firstminute Capital, Presight Capital, Seedcamp, Hambro Perks and Amino Collective.
Why I joined Lindus Health? Nik Haldimann, CTO
A worthy mission. Personal challenge & growth. To create a dream environment for engineers.
Optimising trial recruitment with our Primary Care Network
Primary care organisations are responsible for patient care but are not yet set-up for research. What do we mean by Lindus Health’s Primary Care Network and what are its advantages? Learn how primary care can turbocharge your trial recruitment.