Research participation that works in real life.
KARIKA is a clinical intelligence product in development, initially focused on making clinical trial participation more feasible and sustainable.
The intended plug-in approach would bring participation intelligence into compatible clinical and research software. A standalone workflow is also a proposed delivery option.
Prototype development and prospective evaluation are next steps. KARIKA is not available for production deployment, and clinical and commercial performance have not been established.
Clinical fit is only part of the decision.
Someone may meet a study’s clinical criteria and still face practical barriers to joining or continuing. Travel, caregiving, work and changing circumstances can affect the patient experience and the team responsible for delivery.
KARIKA is intended to help teams consider participation feasibility alongside clinical suitability throughout the research journey.
Understand the barrier. Support the next step.
Anticipate participation challenges
Help teams consider practical barriers during study planning and as a person’s circumstances change.
Consider feasible support
Help teams assess support options that could make participation more practical for patients and caregivers.
Coordinate follow-through
Support clearer responsibilities and next steps across research teams, pharmacy and usual care.
A plug-in capability in development.
The proposed embedded approach would let compatible software incorporate KARIKA’s participation intelligence within an existing workflow. Integration requirements, permitted data and responsible users would be agreed with each development partner.
Initial conversations are relevant to sponsors, CROs, research teams, pharmacy organizations and clinical software partners interested in shaping a focused first use case.
Open to development partners, pilot planning and investment discussions.
Define and develop
Agree the first use case, intended users and requirements for a testable prototype.
Plan an evaluation
Define the setting, responsibilities and measures needed to evaluate usefulness, participant burden and operating performance.
Build the investment case
Discuss the team, resources and milestones needed to develop and evaluate the first product.
Intended benefits are hypotheses for evaluation. Integration availability and deployment timing depend on development and partner requirements.
Help shape KARIKA’s first use case.
Tell us the workflow you want to improve and the role your team could play in development or evaluation.