Choose one track. Master’s proposals target Spring 2027. Final scope and programme approval are agreed with the supervisor; bachelor scopes are suggested adaptations.
TRACK 01 · IMPLEMENTATION INCLUDED
Technical track
Develop a working solution and test whether it addresses the problem.
Possible research question
Can evidence-linked action extraction and responsibility tracking reduce missed handovers after digital consultations?
Suggested tasks
Read research on follow-up after digital consultations and compare existing solutions.
Identify one problem faced by healthcare staff.
Write a research question and define what the solution should do.
Use scripted consultation notes to identify actions that need follow-up.
Build a task list with links to the notes, a responsible person, a due date and confirmation before tasks are added.
Compare it with a manually maintained list. Measure missed actions, incorrect assignments and time spent checking tasks.
Explain what worked, what did not, and how the results compare with earlier research.
Evaluation, degree scope and deliverables
Study and evaluation
Compare the implemented solution with a manually maintained follow-up list. Combine reproducible technical tests with an appropriate empirical evaluation.
Missed actions and incorrect assignments
Verification effort
Completion of simulated handovers
Degree scope
Bachelor’s
Build a reviewed action list and responsibility tracker using scripted cases. Test extraction and the complete handover journey.
Master’s
Compare evidence-linked extraction with a manual workflow, separating automation errors from coordination failures.
Background
Programming
Text processing or LLM integration
Workflow design
Possible deliverables
A focused literature review, justified problem and research question
A working prototype with source code and setup instructions
A reproducible comparison and an appropriate study of use
A report explaining design lessons, results and limitations
TRACK 02 · NO IMPLEMENTATION REQUIRED
Non-technical track
Study existing systems, information or work practices. You do not need to develop software.
Possible research question
Where do responsibilities become unclear after digital consultations, and what helps staff complete follow-up actions?
Suggested tasks
Read earlier studies of follow-up after digital consultations.
Choose one problem and write a research question the study can answer.
Map the handover from consultation notes to assigned actions using fictional cases.
Interview staff about missed follow-up, ownership and existing coordination routines.
Review how existing task lists or documentation practices make responsibility and completion visible.
Analyse the interviews, observations or documents using a clearly described method. Look for disagreements as well as common patterns.
Explain the findings, compare them with earlier research and suggest practical improvements.
Evaluation, degree scope and deliverables
Study and evaluation
Use a bounded empirical study of follow-up after digital consultations. Justify case selection, recruitment and the analysis method. Distinguish observed behaviour from participants’ perceptions; use triangulation or a comparison where it serves the research question.
Points of lost ownership or ambiguous handover
Practices that support traceability and timely follow-up
Evidence for the findings, conflicting cases and limits of the study
Degree scope
Bachelor’s
Study one case or a small set of existing materials. Agree the interviews, documents or scenario tasks with the supervisor. Describe the method, analyse the findings and give practical recommendations.
Master’s
Use a clear research question and relevant IS theory. Justify the cases, participants and analysis method. Explain what the findings add to earlier research and where they may apply. No software development is required.
Background
Literature review and academic writing
Qualitative or quantitative research methods
Interest in follow-up after digital consultations; no programming prerequisite
Possible deliverables
A literature review and research question
A study plan and approved research material
An analysis supported by interviews, observations, documents or scenario results
A thesis with findings, recommendations and limitations
Scope and access
Use simulated cases with reviewed expected actions. Do not send real care reminders or treat generated actions as clinical advice. These implementation-related limits apply when developing or testing a technical solution. For a non-technical study, agree access to participants or existing materials early, use approved or fictional cases where appropriate, and distinguish perceptions from observed outcomes.
Agree access to data, participants or existing materials and any required ethics or privacy review before committing. A non-technical track needs a systematic study, not a working prototype.
Full academic proposal
Working topic
Reliable Follow-Up After Digital Consultations
Brief outline
This proposal examines follow-up after digital consultations in the work and information needs of healthcare staff. The technical track combines a literature review and justified gap with requirements, design, implementation and evaluation of a bounded solution. The non-technical track investigates practices, experiences or organisational conditions through a systematic study of existing systems, documents or scenarios, without requiring implementation. Choose one track and agree the final research question, degree scope and contribution with the supervisor.
Programme fit
Information Systems. These are suggested research approaches, not a statement of confirmed programme policy. Agree the final title, track, degree scope and contribution with the supervisor and programme.
Shared research foundation
Review the literature; identify and justify a gap; formulate research questions; conduct a systematic study; analyse the evidence; explain the contribution relative to prior research and discuss limitations. The technical track additionally includes requirements, design, implementation and evaluation of an artifact.
