Participant data lives in spreadsheets
Enrolment, status and visit dates sit in shared files that several people edit, with no record of who changed what.
Andolasoft builds the tools a study runs on, such as participant tracking, consent records, participant apps and reporting. We build them around how your lab works, and we keep running them after launch.
Figures describe one platform we built for a US research institute. The client is not named.
Andolasoft builds custom software for research labs and institutes that have no software team. That includes participant tracking, consent and visit records, mobile apps for study participants, coordinator portals and study reporting. The software replaces the spreadsheets and shared drives a study team would otherwise rely on, and Andolasoft hosts and maintains it after launch.
These are common when a study outgrows the tools it started with.
Enrolment, status and visit dates sit in shared files that several people edit, with no record of who changed what.
Someone checks a column of dates before each visit, and re-consent depends on that person remembering.
Each sponsor or committee request means copying numbers into a new sheet.
A custom spreadsheet or small app that nobody else understands, and nobody is paid to maintain.
Start with one workflow. Add more when the first one is working.
Enrolment, consent and visits in one record per participant, with access by role and a log of changes.
See participant trackingiOS and Android apps for participants to log data themselves, with a coordinator portal to review it.
Read the case studyRecruitment and status counts pulled from the records your team already works in, using Apache Superset when a dashboard is the right fit.
See grant reportingLinking the files your lab instruments produce to the participant or sample they belong to. What is possible depends on what the instrument exports.
See instrument dataAdding to REDCap, connecting to it or replacing it, and when to leave it alone. What is possible depends on how your institution runs it.
See REDCap optionsYou decide what the system does. We do the building and the running.
A free 30-minute review. We look at your current spreadsheets, forms and steps with the people who use them.
We pick one study or one workflow and write down what the system must do and how you will check it works.
Your coordinators use the first version on a real study before anything else moves over.
We host, monitor and update the system, and change it when your study changes.
The clients are not named here.
iOS and Android apps for participants, a coordinator portal and a backend API on infrastructure built for protected health information, with Apple HealthKit and Google Fit data read with each participant’s consent.
Read the case studyApplicant tracking and a web application for job seekers to apply smoothly, built for a government-funded research institute.
Read the case studyMembership management, advanced search and an admin interface added to a subscription database of pesticide products with hazard ratings and reviews, run by a firm that does pesticide chemistry and toxicology consulting.
Read the case study
A seven-step guide for research labs with no software team: map your spreadsheets, fix the rules, pick a route, migrate safely and hand the system an owner.
Read article
A ten-point checklist for a research lab to check who can see participant data, whether changes are logged, and what to ask before you trust a study tool.
Read article
A practical checklist for keeping consent and enrolment records that are easy to find and explain. Your IRB still sets the rules for your study.
Read articleWe will look at your current spreadsheets and steps, and tell you what we would build first. You will hear back from a solutions architect within one business day.
We can sign an NDA before the first technical conversation.