Digital health
Apps and platforms that patients and care teams can actually use.
A patient wants to fill something in quickly. A healthcare professional needs an overview. A researcher wants usable data. The product has to work for each of them.
Experience with KU Leuven & UZ Leuven, Ectosense and Project Sleep. Based in Leuven.
What is a digital health product?
Zenjoy designs and builds apps and platforms for digital health: from patient questionnaires and coaching to research management and device integrations. We bring user roles, sensitive data and the everyday context of use together in the design. With clear agreements on privacy, validation, publication and maintenance.
Health products with different kinds of users
A working app is only the beginning.
A short action, at the right moment, in plain language. We design from the situation in which someone actually uses the app.
Patients, researchers and administrators have different permissions. Data flows, access and retention periods are among the first design questions.
App stores, hosting and support remain necessary. We put the management and costs after the first launch on the table up front.
We align measurement moments and questions with the research protocol, and the user experience with the participants’ context. Scientific validation stays with the research team.
Usability, data management and continuity all help decide whether a health product can keep working in practice.
What we build for digital health
Testing the user experience with patients, healthcare professionals or participants. With a clear scope and agreements on what still needs to be validated.
Questionnaires, logging, coaching and device integrations. Easy to use, with offline operation when the situation calls for it.
Registration, roles, management, dashboards, content and export. The right information for the right user, according to the agreed access rules.
Hosting, monitoring, app store updates and further development. With an agreed owner, budget and availability.
We do not build systems that autonomously diagnose, triage or make treatment decisions. We do support the product experience, administration, communication and data quality, always with human review where it is needed.
We first check whether an existing package such as REDCap or m-Path is enough. Custom development may be needed for your own user experience or a device integration. Obligations around research and medical software are scoped together with your qualified experts.
Does your question start mainly from a research model or fieldwork? Research. For the build: Mobile apps · Web platforms · Care.
From patient questionnaire to wearable
LARS after rectal surgery, measured longitudinally
KU Leuven & UZ Leuven wanted to measure bowel symptoms after rectal surgery over a longer period. Zenjoy built an app with a short questionnaire per toilet visit, QR enrolment and an admin environment for researchers. Personal data and measurement data are kept separate. The first version was ready in under three months.
A sleep intervention schools can run themselves
From an offline programme to a public information platform and a restricted school portal. The goal was to make the intervention scalable, not simply to digitise a leaflet.
Medtech spin-off: wearable + app + data layer
For a medtech spin-off working on sleep disorders, we worked on brand and product design and a software prototype for web, mobile and wearables. The app connects the user with the device.
Research software outside healthcare: see Research, with Phonebox / MeBioS.
Exploring your health product
We map the users, data flows, roles, device integrations and the first usable version. We discuss which review your project needs and who is responsible for it. Scope, planning and management follow from there.
Get started directly via contact, no mandatory intermediate step.
Budget and timing depend, among other things, on the backend, hardware, data processing and validation. We plan for app store review and external assessment, but we cannot guarantee them.
Questions we often get
Yes, provided roles, data minimisation, storage, access and responsibilities are clear early on. We draw the data flow first and only then the features. No empty ‘GDPR-proof’ sticker.
That depends on the features, backend, data flows, hardware and required validation. We estimate a clearly scoped first version and the recurring maintenance separately. With project funding, we look at what is feasible within that budget.
Yes. You bring the clinical content, the protocol and the applicable requirements. We take on product design and technology, and coordinate with the people responsible for IT, privacy and validation.
We plan from the first necessary version and treat external reviews as a dependency. For S.Tool, that first version was ready in under three months. That is one case, not a standard lead time or a guarantee of approval.
No autonomous diagnosis or triage. We provide logging, clear boundaries and human review. If the project does require autonomous decisions, we are not the right partner.
A health app or care platform that needs a next step?
Who will use it, which data is needed and what timeline is at play? Tell us what already exists. Then we plan the next step together.
You talk to someone who thinks along on substance. No obligation, no standard pitch.